Windows Update downloading Cumulative Update even after integration

[tortadefrango97]

Guys, I noticed a strange behavior when installing windows after pre-integrating the cumulative update. Even the cumulative update being pre-integrated windows update downloads it again.

Searching here on the forum, I found this post that seems to be about the same problem. (https://www.ntlite.com/community/index.php?threads/recurring-problem-on-ntlite.3298/) but from what I understand there wasn't a certain resolution of the problem since the guy apparently got upset

What I did was:
1) Pre-integrate cumulative update KB5022834 + NET 4.8 update
2) Enable NET 3.5 + legacy components integration in features tab.
3) I checked Dism cleanup.
4) I checked the option to reapply in other Home/Pro editions.

This in an untouched official iso, brazilianportuguese language from Microsoft's official website.

I am attaching the preset as well.

In my tests I noticed that Windows Update downloads the entire cumulative update, but I don't know if it actually installs it, because the process is fast, different from when the update is done from the iso that is not pre-integrated with this update, windows doesn't ask to restart or anything, it just downloads apparently, or it's just updating something minor, I don't know.

Another interesting detail is that this problem only happens in editions that have been reapplied, that is, in the Home SL version (which was the one I was loaded in NTLite) the WU does not download. However, in other editions (Home and Pro) the WU downloads the update even though it is already pre-integrated, as can be seen in the screenshots.

Later I will do the test and update each edition separately, because I'm thinking that the problem is in the option to reapply in the other editions, since it only works correctly in the edition that I have loaded.

Edit: I am also attaching the .log in case it's useful, but this time I loaded the Pro edition and re-applied the others, and the same symptom remains (see the last sceenshot).

 

[abbodi86]

Do you add second keyboard during installation?
that usually trigger download/install of the new lang FOD packs (LanguageFeatures-Basic at least), which in return cause LCU reoffer in Windows Update

p.s. LCU reoffer won't occur if contents of C:\Windows\servicing\LCU are not cleaned
but that's against the concept of nLiting, and DISM itself remove the contents when executing /Cleanup-Image /StartComponentCleanup

 

[tortadefrango97]

Do you add second keyboard during installation?

Oh, actually yes. I'm selecting during installation the alternative version of the pt-BR keyboard (ABNT2), which actually should be the default option, I don't know why microsoft leaves it as a secondary one since all keyboards here in Brazil are ABNT2 and not ABNT like the Microsoft thinks haha

But apparently I don't think that's what is causing the updates, because I just did the test installing without selecting that second keyboard and the same problem occurs, it is downloaded again in the Home/Pro edition but not in the Home SL edition

Thanks for the reply Abbodi, btw thanks a lot for your scripts, i've been using some of them for years and they are extremely useful.

 

[tortadefrango97]

p.s. LCU reoffer won't occur if contents of C:\Windows\servicing\LCU are not cleaned

It looks like this is happening, that folder you mentioned is clean before the WU, and after installing the updates, files appear inside it.

But all versions do not contain this folder before windows update, and even so WU downloads again only in Home/Pro, Home SL does not download.
Is this problem being caused by cleaning Dism checked in NTLite then? edit: doesn't seem to be the case, that folder doesn't exist even if the cleanup dism is unchecked...

 

[tortadefrango97]

Later I will do the test and update each edition separately, because I'm thinking that the problem is in the option to reapply in the other editions, since it only works correctly in the edition that I have loaded.

ok, i just completed this test and it looks like the problem is related to the reapply feature, because now i've done the above procedures, but processing each edititon separately. And the problem doesn't appear this way, the WU doesn't download the already integrated KB, as can be seen in the screenshots. nuhi if you can take a look... thanks

 

[tortadefrango97]

Hey nuhi,

I don't know if you even saw this post, but anyway, I did more tests here, and I also saw in the other post that you said that it could be a problem with the integration of NET 3.5. And I came to the conclusion that it really seems to be.

I just did the integration of the last KB5022906 released by MS this Tuesday and I reapplied it in the other Editions, I installed and tested the images, everything is fine WU does not download the same KB again.

Then i did another test integrating the KB first in one pass and in the other enabling .NET in a second pass, I installed the image and the WU downloaded the same KB again.

Finally, I reinstalled the First image without .NET and installed it manually using an offline installer I found on the internet, and WU as expected it redownloaded the entire KB.

Would you know of any way to avoid this? I do not know what else to do

Sorry to bother you, thanks anyway

 

[francis11]

I delete LCU folder everytime i use NTL and put WU to pause until next preferred update arrive.
And by prefered update it could be the official ones or the preview ones - what one prefer.