Win10 still downloads and installs the already integrated updates

T

turnip

New Member
Hi,

So I built an 1909 x64 image 3 weeks ago from a clean source (microsoft.com) and configured my settings, features and integrated the latest online updates, the biggest of which was the KB4532693 cumulative update (340MB). I noted that after installation, Windows Update still downloaded and installed the same update.
Yesterday I loaded up this modified image and only integrated the latest updates again, this time I got the KB4532695 cumulative update (338MB) plus another small one (KB4538674). I was hoping this would now make a fully up to date image with no new updates required, but lo and behold Windows Update downloads and installs KB4532693 again.

What's going on? It kind of defeats the purpose of integrating updates if the only thing it does is grow the image size.

I did not select the 'Clean update backup' option as both 'DISM compatible' and 'DISM ResetBase' seems to always result in an image that fails to install (after the install continues from the internal drive it gets to this screen where it wants to download some files to repair itself, but always fails and reboots to the same screen (the network connectivity is fine)). This was true about a month ago, haven't tried it now.

Also, if I try integrating .NET 3.5 using the preset, NTlite fails to build the image, unless you don't touch anything else. Also true about a month ago.
I always update NTlite to the latest version before building any images.
 
i think we should write some sticky post about this and returning components / remove reinstalls, every new user asks this
 
Can you please explan, for the sake of future visibility? Should I do one run first with just the online updates, .NET and language packs, and configure/remove stuff the second time around? When can I use DISM without breaking the image?
 
For the sake of future visibility, use search

Returned components 18363.418

How to make deleted components not return in 18363.418? I use the latest version of Lite for free.
www.ntlite.com www.ntlite.com

Does Windows Update put back things removed?

Just wondering to what degree Windows Updates are a problem, after installation, in terms of restoring things we've stripped out using NTLite. If this is an issue, are there any tips for mitigating it? Thanks.
www.ntlite.com www.ntlite.com
 
edge914, I'm not sure how the threads you linked to have anything to do with what the OP is asking. He doesn't seem to be saying that things he removed are brought back by installing a Windows Update.

I have noticed the same thing that the OP has for some times now and would like to know if it's normal and if others are experiencing the same thing. I've only seen it happen for cumulative updates though. The other updates don't re-download and reinstall when checking Windows updates.

So for example, I have a Windows 10 2004 image from Microsoft. I integrate the latest servicing stack at the time of writing, KB4566785. I also integrate the latest cumulative update at the time of writing, KB4568831. I do not use any kind of cleanup at all; it is set to None.

The updates get integrated successfully. I install from the image I created with NTLite. I see that all of the updates that I integrated with NTLite are there and exist in Programs and Features -> Installed Updates.

I click check for updates in Windows Updates. It downloads and installs the latest cumulative update again (KB4568831), despite it already being installed. None of the other integrated updates are re-downloaded and installed through Windows Updates. However, one big difference is that the system does not need to reboot after it is finished installing the cumulative update. If I did not integrate the cumulative update with NTLite, and Windows Update downloaded it and installed it on that copy, it would want to reboot the computer after the update was finished installing.

It's not a huge deal, as I have decent enough internet. However, it would be nice if it didn't have to waste the time and bandwidth to download an update that's over 300MB again every time.

Is anyone able to confirm whether this is supposed to happen? Surely, it doesn't make sense for it to be intended to function that way. That being said, I doubt that this is a bug with NTLite and is probably just Windows being stupid.
 
I experienced the same thing with LTSC, although I did not use NTlite to integrate. I used a script-based tool. It installed fine but got reoffered again.

It turns out the two of .msu files I integrated were corrupted. I redownloaded the files and integrated them and it worked fine. It is worth a try.
 
slimzky said:
I experienced the same thing with LTSC, although I did not use NTlite to integrate. I used a script-based tool. It installed fine but got reoffered again.

It turns out the two of .msu files I integrated were corrupted. I redownloaded the files and integrated them and it worked fine. It is worth a try.
Click to expand...

Unfortunately, this isn't the problem. I just redownloaded all of the MSU files from Microsoft Update Catalog and checked the hash against the ones I had and they all match. I do feel like I've had 1 instance where Windows update didn't try to redownload the latest cumulative update, but I don't remember when. I think it may have been back in 1809 version of Windows 10 for a certain cumulative update, but I guess it doesn't really matter.
 
It's not a problem, it's a feature (per MS implementation) since v1809, called LCU reservicing

whenever you add any other update after the LCU, or FOD/Lang package, or even change an optional feature state, the latest CU will be reoffered and downloaded/cached to C:\Windows\servicing\LCU
 
abbodi86 said:
It's not a problem, it's a feature (per MS implementation) since v1809, called LCU reservicing

whenever you add any other update after the LCU, or FOD/Lang package, or even change an optional feature state, the latest CU will be reoffered and downloaded/cached to C:\Windows\servicing\LCU
Click to expand...
Thanks for the info, had my doubts it's that.
Was planning on re-integrating CU after any other packages as the last step (bypassing the existing update detection of NTLite), and/or extracting it to create LCU directory manually on the image directly. What do you think, tried any of it yet?
 
nuhi said:
Thanks for the info, had my doubts it's that.
Was planning on re-integrating CU after any other packages as the last step (bypassing the existing update detection of NTLite), and/or extracting it to create LCU directory manually on the image directly. What do you think, tried any of it yet?
Click to expand...

Well, i never tried adding the LCU directory manually

in W10UI script:
- add the LCU as the last update
- dism cleanup
- enable NetFx3
- re-add the .NET CU, and the Windows LCU (done in the same dism session, LCU the second)

so far, this has been highly sucessful in avoiding the LCU reoffer through WU
assuming that all required lang FOD already present before updates

choosing extra keybroad or adding another writing language will require their associated FOD, which i think it's the reason for most LCU reoffering
 
Released version build 7618 with the CU reapplying as the last one, let me know if it's any better.
If you still get CU reoffered, please post a preset.

Thanks.
 
nuhi said:
Released version build 7618 with the CU reapplying as the last one, let me know if it's any better.
If you still get CU reoffered, please post a preset.

Thanks.
Click to expand...

Beautiful. It did not re-offer and re-download the latest cumulative update. Thanks, and thanks to abbodi86 for the insight.

Edit: Was offered the cumulative update again after Windows installed some language related thing. Trying to figure out how to stop this now. I checked before and after of the single Language I had in there, but I see no changes. Handwriting was already installed, and I'm still being offered to download the Language pack and Speech of that language.

Edit 2: Found the culprit... Not sure what it actually installs, but it's being activated by a task in task scheduler: Microsoft\Windows\LanguageComponentsInstaller\Installation

Edit 3: Narrowed it down some more... Running that task actually installed the "Basic Typing" feature of the language. So I guess my options are either to disable the task in post setup, or to find a way to install this feature. Finding these language features to integrate seems difficult though.

Edit 4: I figured out how to integrate the Basic Typing feature thanks to freMea's post here:

How to add/integrate language pack & language feature pack into a ISO via NTLite

I've the EN-GB ISO & I want to add these files microsoft-windows-client-languagepack-package_en-gb-amd64-en-gb.esd & microsoft-windows-languagefeatures-basic-en-gb-package-amd64.cab because every time I make a clean installation, I see these files are downloading via Setting/Apps/Optional...
www.ntlite.com www.ntlite.com

I only had to go as far as downloading the language feature and put it in the right place with the right format and name. I didn't have to add registries - I just enabled the Basic Typing in the Features on Demand area of NTLite. All is good now. No more offering of the already installed cumulative update.
 
Last edited:
Old thread but yeah, this is what I assumed as well.

I tried a ntlite ISO as a upgrade install (have to remove unattended), I upgraded from en-us to en-gb, removed the en-us remnants in the language settings, and when I loaded wumgr it offered the CU again, it didnt need to download it, just went to install, but failed.

I then went to the normal windows update, it downloaded, and installed, but no reboot was needed, it seems it just scanned for changed files or something and then was satisfied (update shows as previous installed update now). So the issue just seems to be the registration of the update.

I didnt check updates prior to removing the en-us language. But doing the upgrade install changes the language config anyway as the installer warns before starting. As long as this doesnt break future updates its not really an issue, but posting here for those searching about this.
 
You must log in or register to reply here.
Back
Top