D
Deleted member 9735
Guest
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
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
Last edited by a moderator: