Win10 19045.2193 NTLite preset crash during reboot installation

wazer said:
I thought I already mentioned this, my bad. It gave error once the first time and why I dont know?, but the removing components parts not all parts being removed when selected first time, what about that?
Click to expand...
OK, let me know if you see a pattern regarding the setup error.

Regarding the 2 session removal, it's complicated:
- Cumulative Update cache (LCU)
This one is a "Placholder", in case integrated cumulative update adds it, you can pre-select for removal if the component exists during that session.
This is written on the actually not-yet existent component list, just not on the Apply page. Will see if it confuses more people to add tag there as well.

IKE and AuthIPsec Keying Modules
This one if removed was causing a sfc/scanhealth issue, as it shares a file with network security.
So it was allowed to be fully removed only if Windows Update is also removed.
Adding it now to SFC compat, it's where it belongs, so if people disable SFC compat, it will remove cleanly now, otherwise it will be protected to not confuse.

Manifest Backup (WinSxS\Backup)
Oh (wo)man, a bug... fixed for the next update, ~400MB removed in this case.

Static Font Cache
Fixed in next, the detection was off, same removal.

Wallet Service
The first time it only removed an App, due to DISM-mode for app removals, the second time it wasn't an app, but the underlying component, thus listed in a different place.
To combine the two, set App removal mode to Custom under the Components toolbar - or keep as is and leave the second component.
The point is it was removing both at once before, then added this mild app removal mode for compatibility reasons.
But to solve this, and keep DISM removal mode viable, renaming the app to "Microsoft Pay", actually allowing its real name. The other one will be split to Wallet Service always present and app depends on it.

Windows Mail
Same as Wallet, the app will be Mail and Calendar, the support/component under it Windows Mail.

Thanks, this was fruitful.
 
LCU dosn't be integrated in image if you pick up an updated image on UUP.
Your latest preset still show a ton of removals (381) - you be sure none of them removed what was needed?
It's easy to remove packets and after not working - complian complian like another curlingkid.
Be sure to check Compatibility upper left corner when on Removal tab.
I've 832 removals in my preset for the purpose i want.
Just to say - it cost hours to find out, how to make it the way one like.
Simple recipe for using NTL
 
nuhi said:
OK, let me know if you see a pattern regarding the setup error.

Regarding the 2 session removal, it's complicated:
- Cumulative Update cache (LCU)
This one is a "Placholder", in case integrated cumulative update adds it, you can pre-select for removal if the component exists during that session.
This is written on the actually not-yet existent component list, just not on the Apply page. Will see if it confuses more people to add tag there as well.

IKE and AuthIPsec Keying Modules
This one if removed was causing a sfc/scanhealth issue, as it shares a file with network security.
So it was allowed to be fully removed only if Windows Update is also removed.
Adding it now to SFC compat, it's where it belongs, so if people disable SFC compat, it will remove cleanly now, otherwise it will be protected to not confuse.

Manifest Backup (WinSxS\Backup)
Oh (wo)man, a bug... fixed for the next update, ~400MB removed in this case.

Static Font Cache
Fixed in next, the detection was off, same removal.

Wallet Service
The first time it only removed an App, due to DISM-mode for app removals, the second time it wasn't an app, but the underlying component, thus listed in a different place.
To combine the two, set App removal mode to Custom under the Components toolbar - or keep as is and leave the second component.
The point is it was removing both at once before, then added this mild app removal mode for compatibility reasons.
But to solve this, and keep DISM removal mode viable, renaming the app to "Microsoft Pay", actually allowing its real name. The other one will be split to Wallet Service always present and app depends on it.

Windows Mail
Same as Wallet, the app will be Mail and Calendar, the support/component under it Windows Mail.

Thanks, this was fruitful.
Click to expand...
Great there was some fruits to catch :)
Any ETA on when new version will go up to play with ?
 
You must log in or register to reply here.
Back
Top