Update integration breaks the installation (KB5009543)

HolyK

New Member
//EDIT: Invalid report. Seems like it was caused by some local issue with DISM. After cleanup it builds the installation ISO w/o issues.

Hi,

I have perfectly working preset tailored to my needs but the moment i install it in VM and check updates it pulls KB5009543 and KB5008876. The first one is a cumulative update which brings back a shitload of components, services and tasks which i removed (including service center, Xbox things i don't need, etc..).

So I wanted to integrate these updates via NTLite because if i understand it correctly it first applies the KBs and then performs the component/service removal so ideally i should end up in nicely clean installation at the end.

The problem is that once i add these two updates and re-create the ISO (w/o any additional changes) the Installation fails at the very end of its proccess (During/after "Finishing up" step of the installation).

1641992567159.png

BUT if i take untouched Win10 ISO and integrate ONLY these two KBs w/o any further modifications or component removals, it installs just fine and no issue faced. So the problem is not with the Update integration itself but seems like it conflicts witch something in my preset.

Few questions:
- Is there some "better" way to debug this (any Installation logs which provides more detailed info WHAT exactly is failing?) or do i need to go via trial an error approach...
- Even if i figure this how do i handle these huge updates which re-enables a truck of removed garbage again. Can i just take the same NTLite preset i used to build the installation ISO and just apply it to the live system? Will that rip off all of the crap again or are there any limitations? I like NTLite because it can rip off the unneeded pieces in-rather that removing already present bloatware (Like candy crush) after installation. I don't want to completely disable/block windows updates as i want to receive security updates (at least).

Preset attached. It contains the two mentioned KBs as well. Remove these two and it will work like a charm.

Thank you in advance for comments...
 

Attachments

  • Win10_B14_broken.xml
    35.1 KB
  • Win10_HK_Registry_3.reg
    22 KB
Last edited:

nuhi

NTLite developer
Staff member
When integrating updates, make sure it's on the full ISO, in the first session (or before) as the component removal.
Not after.

When Windows Update returns pieces, there is what you're asking already built-in, run:
Source - Tools - Remove Reinstalls
 

HolyK

New Member
When integrating updates, make sure it's on the full ISO, in the first session (or before) as the component removal.
Not after.

I am a bit unsure what do you mean by that. You mean to first integrate the update, apply and then do the removal and apply again + create install iso?
Or you mean the order in XML makes the difference so the <Packages> needs to be before the <RemoveComponents> sections?

And for the "Source - Tools - Remove Reinstalls" ... Amazing, i was not aware about that. You rock!
 

nuhi

NTLite developer
Staff member
I am a bit unsure what do you mean by that. You mean to first integrate the update, apply and then do the removal and apply again + create install iso?
Or you mean the order in XML makes the difference so the <Packages> needs to be before the <RemoveComponents> sections?
The preset order makes no difference.
Integrate updates either in an earlier session, as you described, or at the same time as the removal, the tool will first integrate then remove.
The point is after removals integrating in the next session can break due to missing/removed packages.
It's different after install, it (DISM) can take it.

And for the "Source - Tools - Remove Reinstalls" ... Amazing, i was not aware about that. You rock!
Yeah gotta make it prompt automatically in one of the next updates.

Thanks.
 

HolyK

New Member
...or at the same time as the removal, the tool will first integrate then remove....
I've used untouched Win ISO + New session + loaded my preset + added these two Updates and created new ISO. It broke. So it must be one of the customization i am doing. I'll do some tests and report back.
 

nuhi

NTLite developer
Staff member
If I can replicate the issue with one preset in one go on an original ISO, then leave the search to me.
Is it the one in the first post or you have another with the updates and all?
 

HolyK

New Member
nuhi Yop, it is the one attached, just replace the path to .reg file (attached as well) and the two updates.

What i tried:
- Preset + .reg file and without the updates => Works OK
- Win ISO only with the two updates (and no further adjustments) => Works OK
 

crypticus

Well-Known Member
nuhi instead of creating another thread i want to write here;

i edited w11 home x64 (also boot.wim has tpm bypass on this one)
i edited w10 home x64
i exported w10 to w11's install.wim to make it one iso.

both installs perfectly on seperate iso's. but on combined iso only w11 installs perfectly, w10 gives error at oobe part. something related to boot.wim? because it has tpm bypass in it? i won't be testing this any further since its not a big deal. but i wanted to report.
 

garlin

Well-Known Member
If you're making a multi-edition ISO, it's probably not boot.wim.

Check the unattend.xml, which has to work for all editions on the same ISO (especially if you're skipping MS account creation).
 
Last edited:

crypticus

Well-Known Member
I place xml only inside install.wim's panther folder. so they won't work for any other edition. and i always remove the one at root of iso.

btw i always make x64x86 AIO iso's with w7 w8.1 w10 combined. but with w11 it didn't work...
 

HolyK

New Member
nuhi Scratch that initial report. I think i had something messed with DISM in my VM. At one of the NTLite exit i got the "Cleanup" process and it took quite a lot of time to finish (i let it do its work). After that (and VM restart) everything magically works now. Meaning Full ISO + Update integration + the preset i have + .reg file ... all of these gets integrated in one shot and the installation finishes w/o issues.

No idea what happened, but the issue is gone huh.
 

nuhi

NTLite developer
Staff member
nuhi instead of creating another thread i want to write here;

i edited w11 home x64 (also boot.wim has tpm bypass on this one)
i edited w10 home x64
i exported w10 to w11's install.wim to make it one iso.

both installs perfectly on seperate iso's. but on combined iso only w11 installs perfectly, w10 gives error at oobe part. something related to boot.wim? because it has tpm bypass in it? i won't be testing this any further since its not a big deal. but i wanted to report.
Do you have OOBE compatibility turned on?
If so, and still got the error, send me the preset to try.
Or if it works with Win10 boot.wim as intended, then you know more about AIO than me.

Thanks.
 
Top