Why did the Checkpoint LCU get applied to both boot.wim files, but the newer LCU did not?

ZorkLVM

Member
Messages
47
Reaction score
4
See attached pic.

Shouldn't the latest LCU also be integrated into both boot.wim files?

I'm integrating updates on Win11 from 26100.1 to 26100.2605.

Should I try starting from a different base, maybe 26100.1742? I think that base already includes KB5043080.

Or maybe NTLite is right to omit KB5048667?

For reference:
KB5043080 = 26100.1742 (CU Checkpoint) on Sep-10-2024
KB5048667 = 26100.2605 (LCU) on Dec-10-2024
 
Last edited:
I couldn't help you, I don't integrate updates to boot.wim (Image 26100.1)

Indeed, ISO 26100.1742 already has KB5043080 integrated
ISO 26100.1 + KB5043080 = ISO 26100.1742

Plus some changes, like removing some components that are present in 26100.1
 
See attached pic.

Shouldn't the latest LCU also be integrated into both boot.wim files?

I'm integrating updates on Win11 from 26100.1 to 26100.2605.

Should I try starting from a different base, maybe 26100.1742? I think that base already includes KB5043080.

Or maybe NTLite is right to omit KB5048667?
It is because of DISM denying to integrate non-baseline packages into 24H2 so far.
Once it passes, I'll remove the filter from the Apply - Reapply section.

You are welcome to confirm this using DISM or load boot.wim Setup edition in NTLite and target directly, then it will allow it to error out.
"Integrating: KB5048667 - Cumulative Update (Requirement: KB5043080) 26100.2605.1.12 - Error 0x80070306 - [774] One or more errors occurred while processing the request."

edit: will allow direct boot.wim targetting with any update in the next version, filtering should have been applied only to Apply - Reapply
 
Last edited:
OK, thanks, will check then, sometime tomorrow.
 
Tested, confirmed, but haven't solved yet, it's on the list for today.
 
Fix uploaded, please try the new version and let me know if good now.
 
Back
Top