Windows 10 21H1 does not recognize NTLite's integration of Cumulative Update KB5010415

[Deleted member 9735]

Finally my results after days of testing:

ISO: Windows 10 21H1 X64 (Original)

Case 1:
- I chose the Home, Home SL and Pro versions (the rest are removed)
- I integrated the 3 versions only the cumulative updates (.msu)
ssu-19041.1161-x64_e7e052f5cbe97d708ee5f56a8b575262d02cfaa4
windows10.0-kb5009467-x64-ndp48_ab1964ebea987807639c024f82810bf9518ec752
windows10.0-kb5010342-x64_f865479b6847db1aab8d436a37a964f31c853887
- I created the new ISO and tested it.
Result: Excellent. All 3 versions work fine.

Case 2:
- Same as case 1 but additionally I did the suggested powershell procedure with update kb5009647
Expand .\windows10.0-kb5009647-x64_2670e7d4a06ca31caece82602577cdda7e09ef86.cab -F:*.* C:\ISO\10\sources
- I created the new ISO and tested it.
Result: Unusable ISO. (it doesn't recognize the hard drive, apparently it affects the drivers, it also doesn't allow to finish the installation of windows in its first stage)

Conclusions:
- Never take something for granted and affirm things without first proving that what they affirm works.
- The updates:
KB5009647 - Dynamic Update for Windows Setup" (windows 10) (.cab)
KB5009646 - Dynamic Update for Windows Setup" (windows 11) (.cab)
They should NOT be checked by default to be integrated into ISOs and they should NOT be integrated with the Expand command in Powershell either. These types of updates are small and it is better to install them via windows update
- In all the tests I have done, I see that NTLite is the best program to integrate cumulative updates. I wouldn't use it to integrate other types of updates. It is not a problem of NTLite but of this type of updates are not cumulative

Therefore I respectfully request NTLite developers not to mark conflicting updates for ISO integration by default and put a warning about it.

Thank you all for your time, you can now close this thread

 

[abbodi86]

If DU contain setup.exe, it should be excluded from extraction
or, after you extract the DU, extract setup.exe from boot.wim index 2 and overwrite the file in ISO sources folder

the file must be the same in both locations, otherwise you get the error about missing drivers

 

[nuhi]

If DU contain setup.exe, it should be excluded from extraction
or, after you extract the DU, extract setup.exe from boot.wim index 2 and overwrite the file in ISO sources folder

the file must be the same in both locations, otherwise you get the error about missing drivers

Thanks.

Btw for those wondering, the tool already updates the boot.wim automatically when integrating the dynamic updates, that is why that error is not there when using the tool.

alejcbox, will analyse your report and see what's going on, I appreciate the feedback.

 

[nuhi]

I have tried it on PCs, laptops, virtualbox and the same thing happens.
Do what I did.
- Download original microsoft ISO 21h1
- just leave the Home, Home SL and Pro versions (remove the rest)
- Mount Home
- Add the default updates proposed by NTLite
- Select to integrate them also to Home SL and Pro (already at this point the first problem of the .cab update begins to appear)
- Save ISO and Apply
- Try the ISO and you will see the result

PD: When I integrate all the updates (including the preview) this does not happen

Hi alejcbox,

tested this now to see for any image setup errors, and saw no issues.
Dynamic update was only applied with the Home edition, as it updates the boot.wim used by all, other editions picked up the other updates.

Please retry with the latest NTLite, if you haven't tried 8640 or 8641, otherwise potentially please upload the preset used with those newer versions and only recommended updates, to the trigger the Windows setup error.
Then I'll retry.

Thanks.

 

[Deleted member 9735]

Hi alejcbox,

tested this now to see for any image setup errors, and saw no issues.
Dynamic update was only applied with the Home edition, as it updates the boot.wim used by all, other editions picked up the other updates.

Please retry with the latest NTLite, if you haven't tried 8640 or 8641, otherwise potentially please upload the preset used with those newer versions and only recommended updates, to the trigger the Windows setup error.
Then I'll retry.

Thanks.

my tests gave different results, previously published:
- KB5009647 integrates only in HOME version
- After ISO integration, HOME version works and the other versions don't

 

[nuhi]

my tests gave different results, previously published:
- KB5009647 integrates only in HOME version

That was replied to earlier, works as expected. It is not integrated to the edition, it's an ISO-level update, so one edition is enough.

- After ISO integration, HOME version works and the other versions don't

Haven't tested that at first.
Tried now Pro version from that updated ISO, works as well.
Hm, my reply from above still stands, if the new version has that issue, let me know, with a new preset.

 

[Deleted member 9735]

That was replied to earlier, works as expected. It is not integrated to the edition, it's an ISO-level update, so one edition is enough.


Haven't tested that at first.
Tried now Pro version from that updated ISO, works as well.
Hm, my reply from above still stands, if the new version has that issue, let me know, with a new preset.

today i updated the version of NTLite to 2.3.4.8641 x64. I will try again and report the results

 

[Deleted member 9735]

I have already tested the integration of KB5009647 to ISO windows 10 Home, Home SL and Pro with the new version NTLite to 2.3.4.8641 x64 and the problem has been solved (none of the 3 versions fail during installation). Thanks

PS: I still need to test the integration of KB5009646 to Windows 11 ISO (Home, Home SL and Pro)

 

[Deleted member 9735]

There is a problem:
- Mount Windows 11 ISO (Home, Home SL and Pro) and charge Home version
- Integrate KB5009646 to Home (active integrate to other versions)
- Finish creating the new ISO Windows 11 (Home, Home SL and Pro).
- I open NTLite again and it still shows that KB5009646 is not integrated

 

[Deleted member 9735]

In short, the updates KB5009647 - Dynamic Update for Windows Setup for win 10 (.cab) and KB5009646 - Dynamic Update for Windows Setup for win11 (.cab) are not being integrated into the ISOs (despite the program supposedly integrating them); also these updates do not appear in the list of installed windows updates
Keep in mind that each test I do takes hours and hours.
So I suggest that you carry out the necessary tests (the same ones I did) and when you have positive results, then you answer me to proceed to carry out tests again.

Update mar 4/2022:
I have updated to NTlite 2.3.4.8643 and the KB5009647 (w10) and KB5009646 (w11) are still not integrated into the ISOs

 

[abbodi86]

Dynamic Update for Windows Setup is just a group of files zipped in a cab file
when manually extracted/added to ISO sources, it cannot be detected afterwards
neither OS or Windows Update know anything about it, because it's not a real update

the only way to detect it, is to cross-compare the version of all included files, with the same files in ISO sources
and not all files are PE or have a version (e.g. sdb ini man dat files)

 

[Deleted member 9735]

Dynamic Update for Windows Setup is just a group of files zipped in a cab file
when manually extracted/added to ISO sources, it cannot be detected afterwards
neither OS or Windows Update know anything about it, because it's not a real update

the only way to detect it, is to cross-compare the version of all included files, with the same files in ISO sources
and not all files are PE or have a version (e.g. sdb ini man dat files)

ok, but why does NTLite keep showing that it is missing to integrate KB5009647 (w10) or KB5009646 (w11), even after NTLite previously integrated it in a previous step?

 

[garlin]

Normal updates will have a manifest file and component folders. When DISM applies any update, it modifies the image's registry to log this metadata.
DU isn't a normal update, it's a plain CAB which gets extracted.

Therefore there is no record of its installation. DU lives in the ISO folder, which is outside of both boot and install WIM.
DISM only works on images inside a WIM.

What does this imply?

1. DISM can't see DU update.
2. You can't uninstall DU update. There is no metadata to roll back, there are no backup file folders.
3. You can apply DU update over and over on a previously applied image, since there's no record.

Step back and explain how this works if you had to manually update an image with DISM.
Can you run DISM /Add-Package on the DU update? Can you get DISM /Get-Packages to report its integration?

 

[Deleted member 9735]

If, according to you, there is no way for NTLite to know if the KB5009647 (w10) or KB5009646 (w11) .cabs are embedded in the ISOs and will display them over and over again, even though they are already embedded, then I think It is best to close this issue.
thanks for all

 

[nuhi]

I'm glad to see that your issues have been resolved or at least answered in regards to the DU detection.

Will see about detecting existing DU, it annoys me as well.
It's possible as NTLite reads enough info from the CAB to identify the existing one, just never got to it.
As abbodi86 stated, it's a custom update (basically extract only without metadata) and requires some manual maneuvers.

 

[garlin]

sources\Setup.exe changes in each of the RTM, Win11 v1 ISO, and DU versions. While expected, none of that is documented.

 

[nuhi]

sources\Setup.exe changes in each of the RTM, Win11 v1 ISO, and DU versions. While expected, none of that is documented.

Mostly, yes, but weirdly, there are DU's without setup.exe and various available files.
e.g. KB4532820, DU for 1607.
KB5003238, DU for 1803.

NTLite is dynamically checking when assembling the update list DU item, so it will be a task of using the same principles in reverse - finding the same files on the source and making the potential list of existing DUs.
I say a list, because one cannot guess which it is due to seemingly random file usage, but any that is detected will be good enough to detect existing one, as it actually exists.