[SOLVED] WU re-installs already integrated Cumulative Update

W

WKjun

New Member
Hello,

after a fresh install of Win10 (22H2 x64), WU thinks it still needs the 2023-10 cumulative update I have supposedly integrated.
But I cannot see what I'm doing wrong.

I have experimented in VMware Player with no success:
  • set DISM to None
  • extract individual SSU & CU packages from the LCU and use them instead
As you can see on the screenshot I have integrated these updates:
  • Dynamic Update
  • LCU 2023-10
  • .net 4.8.1
  • Secure Boot security
  • LCU .net 4.8
  • LCU .net 4.8.1 (preview)

2023-10-updates.png


win10 update again.png

Thanks for your advice,
Wilhelm
 
Please ignore my previous "delete thread" reply, it was not intended to be in here... :oops:
 
Last edited:

KB5011487 is not integrated into Windows 10 21H2

NTlite integrates KB5011487 to ISO Windows 10 21H2, however windows update downloads it SO: Windows 10 21H2 x64 Home, Home SL, and Pro NTLite: 2.3.4.8643
www.ntlite.com www.ntlite.com

Win10 still downloads and installs the already integrated updates

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...
www.ntlite.com www.ntlite.com

Slipstreamed Windows 10 updates are downloaded and installed again from Windows Update

Hello, I am using the Beta version of NTLite to integrate the latest updates into our 1903 setup folder. NTLite successfully detects the required updates, and downloads them: The updates are then successfully integrated and written to ISO: After upgrading a Windows 10 1703 PC using the...
www.ntlite.com www.ntlite.com
 
Thanks for the links. I already have searched the forums.

One suggests that the Dynamic Update is not needed, although NTLite itself advises so. Any recommendation?

Anyway, I don't think I have any redundant updates at hand.
The point is, I have made a new image with a clean default preset, integrating just the 2023-10 cum. update, .net 4.8 cum. update and .net 3.5 (sxs), but it still needs it. :rolleyes:
 
The way this works is WU checks all the component folders, and searches if any newer version is available.

If a single folder is out of date, WU finds the latest update which provides those files, and downloads it even it will only re-install one or a few components from the entire update. The problem is a number of post-install factors can change the existing components or metadata, causing WU to re-apply the CU.

This can include, but not limited to, adding languages or international keyboards.

DU isn't really required if you're installing a recently updated image. The whole point behind DU is to refresh an out-of-date image by pulling newer updates while Windows is installing. While this can be helpful in some cases, you don't get to decide what DU touches while it's running.
 
Try remove LCU with NTL.
Not even one time i see WU offered the latest integrated CU in W11 (and 10 i think as MS make them similar) except from the guinea pig previews witch is optional untill next official update.
 
I don't know if skipping DU made all the difference (it might), but my test run didn't reinstall the last CU.

Pre-installed updates:
Oct 2023 CU​
.NET 4.8.1 Framework​
.NET 4.8 Oct 2023 CU​
.NET 4.8.1 Oct 2023 CU​
Defender Platform, Engine​

Screenshot 2023-11-02 003851.png

Windows 10 x64-2023-11-02-14-50-15.png
 
Thanks for all your support!

The new updates from the latest patchday "fixed" the problem silently.
Somehow I have expected this; I remember now one time when the preview update was not enough and irrationally re-downloaded the regular cumulative update.
  • LCU 2023-11
  • LCU 2023-11 .net 4.8
  • .net 4.8.1
  • LCU 2023-11 .net 4.8.1
  • Secure Boot security
  • Defender
(no more dynamic update)
 
Last edited:
You must log in or register to reply here.
Back
Top