Problems with Windows Setup in Windows 10 LTSB 2016

[AeonX]

When I disable Servicing Stack Compatibility to activate deep removal, Windows Setup fails to complete on Windows 10 LTSB 2016. On Windows 10 22H2, Setup completes normally. If I leave Servicing Stack Compatibility enabled Windows installs without problems.

This only happens with the latest versions of NTLite, tested on version 2025.08.10552 (the latest). I have no problems with version 2024.12.10221. I haven't tested the others.

I know the development focus is on the latest versions of Windows and almost everyone wants the most up-to-date version possible, but on low-end machines, Windows 10 22H2 is very slow, while LTSB 2016 runs very smoothly. So this is still a great option for those with more modest hardware.

This is the screen that appears during Windows installation:

 

[nuhi]

OK, but I'll need a preset to replicate it, you can send it to my DM as well.

Thanks.

 

[AeonX]

OK, but I'll need a preset to replicate it, you can send it to my DM as well.

Thanks.

Sorry, I edited my post to make it more concise and clear, and I ended up omitting a crucial piece of information without even realizing it. Just use Clean update backup (Custom) and disable Servicing Stack Compatibility, then you won't be able to complete Windows Setup.

 

[nuhi]

Thank you, replicated.
Working on it, if in a rush, switch to DISM Compatible Cleanup, or simply remove WinSxS Component Store component, since you don't need updatability.
This made me think, what's the point of Custom Cleanup with Servicing Stack compatibility off, it should just remove WinSxS.... hmm.

 

[AeonX]

Thank you, replicated.
Working on it, if in a rush, switch to DISM Compatible Cleanup, or simply remove WinSxS Component Store component, since you don't need updatability.
This made me think, what's the point of Custom Cleanup with Servicing Stack compatibility off, it should just remove WinSxS.... hmm.

No rush, I have version 2024.12.10221 which is working perfectly (except for the usbser service issue which I already know how to work around) and doesn't change much for this Windows build. Custom Cleanup removes a bit more than Dism, and I already have an ISO with Dism/ResetBase cleanup that I use for removals.

Even with Servicing Stack compatibility turned off it's possible to enable and disable features, at least the ones I've tested, as long as you integrate .NET 3.5 first. But I'm thinking about removing WinSxS. The main reason I'm keeping it has to do with the DM I sent you.

After integrating .NET 3.5 it stays in the Integrated (Install Pending) state. I'm not sure if it will install correctly after removing Component Store (WinSxS), so I'm keeping it. Can you provide any information on this? I don't know how to verify this, otherwise I'd test it myself.

 

[nuhi]

No rush, I have version 2024.12.10221 which is working perfectly (except for the usbser service issue which I already know how to work around) and doesn't change much for this Windows build. Custom Cleanup removes a bit more than Dism, and I already have an ISO with Dism/ResetBase cleanup that I use for removals.

Even with Servicing Stack compatibility turned off it's possible to enable and disable features, at least the ones I've tested, as long as you integrate .NET 3.5 first. But I'm thinking about removing WinSxS. The main reason I'm keeping it has to do with the DM I sent you.

After integrating .NET 3.5 it stays in the Integrated (Install Pending) state. I'm not sure if it will install correctly after removing Component Store (WinSxS), so I'm keeping it. Can you provide any information on this? I don't know how to verify this, otherwise I'd test it myself.

Good point, we would need to compare Windows files (non-WinSxS), if all the same as after install - if not, protect the pending ones.
As a first task let's fix the Custom Cleanup for Pre-22h2.
Sending you a test version with the fix.

 

[AeonX]

Good point, we would need to compare Windows files (non-WinSxS), if all the same as after install - if not, protect the pending ones.
As a first task let's fix the Custom Cleanup for Pre-22h2.
Sending you a test version with the fix.

Good idea. Thanks. Waiting for the test version.

 

[AeonX]

Good point, we would need to compare Windows files (non-WinSxS), if all the same as after install - if not, protect the pending ones.
As a first task let's fix the Custom Cleanup for Pre-22h2.
Sending you a test version with the fix.

Apparently, the files related to .NET 3.5 are the same with and without WinSxS, only the timestamps of some files change, probably files created during Windows installation. I used Beyond Compare to compare. So I think it's okay to remove Component Store (WinSxS)

I saw that the test version forces DISM Compatible Cleanup before Custom Cleanup. In Windows 10 versions before 1903 this takes a long time to complete. Is this necessary? Other than that, tested and it's great

 

[nuhi]

Apparently, the files related to .NET 3.5 are the same with and without WinSxS, only the timestamps of some files change, probably files created during Windows installation. I used Beyond Compare to compare. So I think it's okay to remove Component Store (WinSxS)

Great.

I saw that the test version forces DISM Compatible Cleanup before Custom Cleanup. In Windows 10 versions before 1903 this takes a long time to complete. Is this necessary? Other than that, tested and it's great

Yes, running DISM before custom cleanup is a good step towards cleaning extra files as sometimes DISM can recompress kept ones, the very least.
If it's locked by pending changes, it will be skipped fast anyway.

 

[AeonX]

Yes, running DISM before custom cleanup is a good step towards cleaning extra files as sometimes DISM can recompress kept ones, the very least.
If it's locked by pending changes, it will be skipped fast anyway.

It makes sense. The reason for the long processing time is precisely because of the recompression, which is why I prefer to use ResetBase because it cleans more and is faster. You lose the Reset This PC feature but I don't use it. For me it doesn't make much difference and it will be quick since there's nothing to recompress as I've already used ResetBase.