Removed Components Still Found in WinSxS?

tharri

Member
I've just discovered that dozens and dozens of folders --- hundreds of megabytes -- of components that I've removed with NTLite are still found in the WinSxS folder. Those should be removed as well, shouldn't they? I've tried it several times. Is this a bug? Or am I doing something wrong?
 
Once finished litin your OS source and if the updates don't matter to you, load it once again and remove Windows Component Store.
After this step, Drivers can't be integrated nor enable/disable features. Always make a backup when you are testing results.

 
Once finished litin your OS source and if the updates don't matter to you, load it once again and remove Windows Component Store.
After this step, Drivers can't be integrated nor enable/disable features. Always make a backup when you are testing results.


I know I can do that, but removed components should still be removed from WinSxS, should they not? I can manually delete the folders of removed components from the WinSxS folder on the iso prior to installation without any problems, and I can still update, install drivers, etc.
 
Did you uncheck Servicing Stack in Components->Compatibility? That will allow deep removal of components.
 
dont bite his head off for trying to help, how often do people have a brain fart and miss the obvious. he is only trying to help.

Oh gosh... that wasn't meant to be sarcastic if it sounded that way. I really didn't know that. I always kept it checked because I just figured it protected the components needed for dism. If this is true, I had no idea it protected the WinSxS too.
 
it stands to reason that anything that is protected will include whatever is in winsxs.

For noobs like me, it's actually not clear. The Compatibility tab shows this:

tab1.PNG

To me, that suggests it would protect the following:

tab2.PNG
tab3.PNG
tab4.PNG

The WinSxS section is in a completely different folder:

tab5.PNG

That's why I would not intuitively think that protecting the Servicing Stack would also protect WinSxS.
 
tharri, thanks for the feedback, do let me know if you would like a change in the UI for it to be more clear.

It was not like this for long, before 3-4 versions it would silently switch between removal modes if a user removes Windows updates and unchecks the servicing compatibility, now it's much more straighforward to advertise more on the deep removal for those that don't mind updating via host refresh or reinstall.

Also Windows since 1903/9 require all files in WinSxS to update as cumulative updates are fully differentially compressed.
That is when [source-tools] Remove Reinstalls was added, make sure to clean update returns after each update, if not updating via Host Refresh or reinstall.

To note, files in WinSxS are inactive, removal effect on the C drive, except disk space because of the WinSxS protection, is identical in deep and updatable removals.
 
Removing Chinese and Tamil does not work properly, they always return. Removed from ISO and tried afterwards on live install, no changes.
1637929138112.png
 
In Windows 7, after component removal and then performing update, Windows Update returns. I lost list of integrated updates but I unchecked all that contained Windows Update in their name.
 

Attachments

  • first-attempt - Copy.xml
    16.2 KB
  • win7-winupdate-remains.PNG
    win7-winupdate-remains.PNG
    75.8 KB
chiefkief, can you ask new questions on a separate thread? Not all these are the same issue.

When removing 'windowsupdate' from W7, I don't see any components left (except for the ADMX templates). Did you perform update integration at the same time as removing WU?
 
Last edited:
chiefkief, can you ask new questions on a separate thread? Not all these are the same issue.

When removing 'windowsupdate' from W7, I don't see any components left (except for the ADMX templates). Did you perform update integration at the same time as removing WU?
I removed windows update and then integration of updates. Even single integration of update make it come back I think, but should remove windows update after integration I assume
 
I removed windows update and then integration of updates. Even single integration of update make it come back I think, but should remove windows update after integration I assume
Correct, update integration only on full image, and removals last.
Or do all at once, tool will sort it in a single session.

Then after install if installing updates, make sure to Remove Reinstalls (especially important for Win10 and 11), Source - Tools - Remove Reinstalls, to cleanup any potential returns via updates.
 
Back
Top