KB5011487 is not integrated into Windows 10 21H2

  • Thread starter Deleted member 9735
  • Start date
D

Deleted member 9735

Guest
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
 

Attachments

  • Captura de pantalla -2022-03-10 15-49-27.png
    Captura de pantalla -2022-03-10 15-49-27.png
    46.2 KB
  • VirtualBox_test_10_03_2022_16_35_07.png
    VirtualBox_test_10_03_2022_16_35_07.png
    166.8 KB
Last edited by a moderator:
The first screenshot is the Download Updates window, but you're not sharing the Updates page (was it integrated?).
 
yes of course. NTLite integrates the update, but window update downloads it
 
I'm going to repeat the procedure again and take screenshots at each step and save preset and post it
 
data
 

Attachments

  • Captura de pantalla -2022-03-10 17-41-37.png
    Captura de pantalla -2022-03-10 17-41-37.png
    46.6 KB
  • Captura de pantalla -2022-03-10 19-12-09.png
    Captura de pantalla -2022-03-10 19-12-09.png
    41.2 KB
  • NTLite.log
    73.7 KB
  • Sesión guardada automáticamente d6c98d72.xml
    5 KB
KB5005260 (SSU Aug 20) is redundant because Feb 22 LCU includes a more recent SSU. In theory, the later SSU version wins the WinSxS contest and becomes active. But since we don't have the NTLite_dism.log, can't tell if NTLite did the expected thing.

10/03/2022 5:48:08 p. m. Descargando: KB5005260 - Servicing Stack Update
10/03/2022 5:48:08 p. m. >>> Downloading: C:\Program Files\NTLite\Updates\10.21H2.x64\ssu-19041.1161-x64_e7e052f5cbe97d708ee5f56a8b575262d02cfaa4.msu
10/03/2022 5:48:18 p. m. Descargando: KB5011487 - Cumulative Update
10/03/2022 5:48:18 p. m. >>> Downloading: C:\Program Files\NTLite\Updates\10.21H2.x64\windows10.0-kb5011487-x64_2190163dcb84974d93ecdc32bdae277b57ebb95c.msu
10/03/2022 5:53:19 p. m. KB5005260 - Servicing Stack Update - Limpiando: C:\Users\Usuario\AppData\Local\Temp\NLTmpUpdExt\package_for_servicingstack~31bf3856ad364e35~amd64~~19041.1161.1.1.5005260
10/03/2022 5:53:19 p. m. KB5005260 - Servicing Stack Update - Extrayendo: ssu-19041.1161-x64_e7e052f5cbe97d708ee5f56a8b575262d02cfaa4.msu
10/03/2022 5:53:19 p. m. Extract ssu-19041.1161-x64_e7e052f5cbe97d708ee5f56a8b575262d02cfaa4.msu
10/03/2022 5:53:19 p. m. KB5005260 - Servicing Stack Update - Extrayendo - Preparando datos
10/03/2022 5:53:20 p. m. KB5005260 - Servicing Stack Update - Extrayendo - Delta
10/03/2022 5:53:23 p. m. Found package cache: package_for_servicingstack~31bf3856ad364e35~amd64~~19041.1161.1.1
10/03/2022 5:53:23 p. m. KB5011487 - Cumulative Update - Limpiando: C:\Users\Usuario\AppData\Local\Temp\NLTmpUpdExt\package_for_rollupfix~31bf3856ad364e35~amd64~~19041.1586.1.7.5011487
10/03/2022 5:53:23 p. m. KB5011487 - Cumulative Update - Extrayendo: windows10.0-kb5011487-x64_2190163dcb84974d93ecdc32bdae277b57ebb95c.msu
10/03/2022 5:53:23 p. m. Extract windows10.0-kb5011487-x64_2190163dcb84974d93ecdc32bdae277b57ebb95c.msu
10/03/2022 5:53:26 p. m. KB5011487 - Cumulative Update - Extrayendo - Preparando datos
10/03/2022 5:53:27 p. m. KB5011487 - Cumulative Update - Extrayendo - Delta
10/03/2022 5:53:34 p. m. KB5011487 - Cumulative Update - Extrayendo: Windows10.0-KB5011487-x64.cab
10/03/2022 5:53:34 p. m. Extract Windows10.0-KB5011487-x64.cab
10/03/2022 5:53:37 p. m. KB5011487 - Cumulative Update - 1/2 - Extrayendo - Preparando datos
10/03/2022 5:53:37 p. m. KB5011487 - Cumulative Update - 1/2 - Extrayendo - Delta
10/03/2022 5:53:45 p. m. KB5011487 - Cumulative Update - 2/2 - Extrayendo: Windows10.0-KB5011487-x64.cab
10/03/2022 5:53:45 p. m. Extract Windows10.0-KB5011487-x64.cab
10/03/2022 5:53:50 p. m. Extract Cab_1_for_KB5011487_PSFX.cab
10/03/2022 5:55:24 p. m. Extract Cab_2_for_KB5011487_PSFX.cab
10/03/2022 5:56:31 p. m. Found package cache: package_for_servicingstack_1525~31bf3856ad364e35~amd64~~19041.1525.1.0
10/03/2022 5:56:31 p. m. Found package cache: package_for_servicingstack_1525~31bf3856ad364e35~amd64~~19041.1525.1.0
10/03/2022 5:56:47 p. m. Integrando: KB5005260 - Servicing Stack Update 19041.1161.1.1 - Preparando datos
10/03/2022 5:56:50 p. m. Integrando: KB5005260 - Servicing Stack Update 19041.1161.1.1 - Cache
10/03/2022 5:56:59 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Preparando datos
10/03/2022 5:57:01 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache
10/03/2022 5:57:10 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache
10/03/2022 5:57:24 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache
10/03/2022 6:09:22 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Preparando datos
10/03/2022 6:09:22 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache
10/03/2022 6:09:29 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache
10/03/2022 6:09:35 p. m. Integrando: KB5011487 - Cumulative Update 19041.1586.1.7 - Cache

My guess would be if SSU 1525 wasn't the winner, DU checks and realizes 1161 is downrev -- and installs 1525.
Installing 1525 over the existing CU (while up-to-date) causes metadata issues, and WU later decides it needs to reinstall CU. Which doesn't actually change any files, but fixes the metadata versions.

Two possible fixes: Don't integrate SSU Aug 20 (it's only required if your LCU is older than it); or don't install DU.

nuhi probably understands NTLite's logic better.
 
Windows update redownloading latest CU (LCU reservicing) is known behavior since v1809
whenever you enable a feature, install new language or add new keyboard language, install or uninstall update after LCU..
 
From my experiments also after adding another language u must install LCU again... or else settings etc won't even work...
 
As you can see in the image, NT lite integrates KB5011487 well, however windows update downloads it again and install the package normally without errors.
 

Attachments

  • VirtualBox_test_11_03_2022_09_27_12.png
    VirtualBox_test_11_03_2022_09_27_12.png
    200.9 KB
  • VirtualBox_test_11_03_2022_09_29_53.png
    VirtualBox_test_11_03_2022_09_29_53.png
    200.7 KB
  • VirtualBox_test_11_03_2022_09_40_03.png
    VirtualBox_test_11_03_2022_09_40_03.png
    195.7 KB
Last edited by a moderator:
Updates are added to image as first operation, then edits are done. thats why WU downloads it again. as abbodi said, it is not applied after editions.
 
I haven't made any changes to the ISO (language, keyboard, or whatever). The changes are published.
Then there is something wrong in your answer, because if it is correct then nobody would use NTLite, since it is useless to integrate updates if windows update downloads them again
 
normally it just download latest LCU... features are not even coming back most of the time.. but yes you did not make any changes. it shouldn't happen
 
this does not happen on win 11 21H2
 

Attachments

  • VirtualBox_11test_11_03_2022_10_59_15.png
    VirtualBox_11test_11_03_2022_10_59_15.png
    252.7 KB
That's weird, your W11 is downloading two versions of MSRT (KB890830). It only needs the latest version since it's a standalone package.
Which goes back to my original point of a SSU related issue.

UPDATE - AskWoody thread reporting the same bug, MSRT supersedence has been broken since Oct '21.
 
Last edited:
That's weird, your W11 is downloading two versions of MRT (KB890830). It only needs the latest version since it's a standalone package.
Which goes back to my original point of a SSU related issue.
NTLite program offers download those two versions in win11 21H2
I think that you should do the tests that I do with the official ISOs, without modifying, so that you can see the problem first hand and find a better solution.
 
From my experience, WU only re-installs CU if another update overwrote its files or metadata. Normally like a SSU or .NET package.
WU wants to restore a handful of files, but downloads the whole package to extract them.

Let's step through this one update at a time.


1. Download 21H2 (19044.1288) with MCT. Remove extra editions: keeping Home, Home (SL) and Pro.

What's the fewest required updates? KB5011487 (CU) & KB5009467 (.NET)
Why exclude KB5005260 (SSU) and KB5010524 (DU)?

CU includes the latest SSU package (19041.1525), superseding 5260 (19041.1161). DU has nothing to do, since our CU + SSU stack is current.

2. Integrate the bare minimum updates (CU & .NET), across all editions.

Win7-NTLite-2022-03-20-08-31-59.pngCapture2.PNG

Install Home. WU didn't ask to repeat CU.

Win7-NTLite-2022-03-20-10-13-07.png

3. Does adding DU make a difference? Not for me.

Win7-NTLite-2022-03-20-11-33-42.png

4. I know what you're thinking. We haven't tried SSU, CU, .NET and DU together on a clean .1288 image.
To speed up testing, I only applied this to Home -- skipping SL & Pro.

Win7-NTLite-2022-03-20-16-37-19.png

What's the difference in our environments, besides VM platforms? NTLite was self-hosted (in VM) on the same image, to remove any possible influence from my actual host. My advice if you want to debug this, don't repeat testing by applying changes across all editions.

That's a huge waste of time, slowing you down. One install image is enough to work with.
 
Back
Top