I need an answer regarding Windows Updates Integration in a ISO

D

Deleted member 763

Guest
If I integrate updates, for the most part they land on the "Integrated (Install Pending) state. What does this mean exactly, I know it means the update will install during setup, but will I need the windows update component for these updates to install?
 
Hi,

no need for the Windows Update component, it's done by the underlying Windows componentization engine.
Big majority of the update is already done once integrated, those are just a few finishing touches that Windows does, like that on a reboot when installed live.
 
nuhi said:
Hi,

no need for the Windows Update component, it's done by the underlying Windows componentization engine.
Big majority of the update is already done once integrated, those are just a few finishing touches that Windows does, like that on a reboot when installed live.
Click to expand...

This is great news, thanks!
 
nuhi said:
Hi,

no need for the Windows Update component, it's done by the underlying Windows componentization engine.
Big majority of the update is already done once integrated, those are just a few finishing touches that Windows does, like that on a reboot when installed live.
Click to expand...

Then why after integrating uodates does install.esd balloon to whatever the size of the CU is plus the initial export size?
 
I recently lited an image, no updates just cleanups, .net cache, cache and temp files, winsxs backup, saved changes and unmounted, the wim was somewhere around 500mb bigger than the original, probably due to the compression engine. Factor in some updates do not directly integrate and must run during setup, the type of Update Cleanup you use, and whether you are running in Free or Licensed mode.

If i am correct esd has better compression than wim. What you got kinda sounds about right to me.
 
Last edited:
Clanger said:
I recently lited an image, no updates just cleanups, .net cache, cache and temp files, winsxs backup, saved changes and unmounted, the wim was somewhere around 500mb bigger than the original, probably due to the compression engine. Factor in some updates do not directly integrate and must run during setup, the type of Update Cleanup you use, and whether you are running in Free or Licensed mode.

I'm specifically talking about the CU updates.

When one integrates a CU into a WIM and exports to ESD, the final size of the ESD seems to be what the ESD would be minus the update plus the size of the update package.

The question is: why does it balloon like that?
Click to expand...
 
You must log in or register to reply here.
Back
Top