WinSxS Full Cleanup Needs Full Version Of NTLite?

I think it's worth mentioning on threads like these that there is a common misconception that install size equals performance, and it just isn't true in a meaningful way, and is mostly an unreliable metric that is fairly useless in relation to the goal.

I bring this up because WinSxS gets mentioned a lot on this forum, and there was even a member here that constantly posted screenshots of his super stripped WinSxS folder to gloat, as if that was something to be proud of and somehow made him an expert tweaker. He also admitted he could not even reboot his machine without it bricking and requiring a reinstall of Windows, so that tells you how good that build was...

As a tweaking enthusiast seeking maximum performance, deleting files is so unimportant that it's not even on my radar. If the install size gets reduced as I'm doing other necessary tweaks, then that's fine, but it's never a primary focus for me while seeking higher performance. If deleting files is important to you, then by all means please focus on it, but if improving performance is the main goal then WinSxS is not the right avenue to explore.
 
Last edited:
I think it's worth mentioning on threads like these that there is a common misconception that install size equals performance, and it just isn't true in a meaningful way, and is mostly an unreliable metric that is fairly useless in relation to the goal.

I bring this up because WinSxS gets mentioned a lot on this forum, and there was even a member here that constantly posted screenshots of his super stripped WinSxS folder to gloat, as if that was something to be proud of and somehow made him an expert tweaker. He also admitted he could not even reboot his machine without it bricking and requiring a reinstall of Windows, so that tells you how good that build was...

As a tweaking enthusiast seeking maximum performance, deleting files is so unimportant that it's not even on my radar. If the install size gets reduced as I'm doing other necessary tweaks, then that's fine, but it's never a primary focus for me while seeking higher performance. If deleting files is important to you, then by all means please focus on it, but if improving performance is the main goal then WinSxS is not the right avenue to explore.
Yes even component store cleanup is not good it will break the windows update and other features how come when you cleanup a whole winsxs folder
 
Windows 7 and 8.1 are end of life, no more updates, you have created/captured a nice End Of Life wim, what good is windows update now? if you have never used SFC what good is winsxs? what good is having the servicing stack and other winsxs components if you use disc imaging software? what good is any of that if you just want a safe lite media player laptop/pc that isnt connected to the internet, just a home network or a NAS box? I can break a f-ton of things on any os while retaining the functions I NEED.

Ive said it before and i will say it again, i just share my findings(FOR MY NEEDS), i dont care if people use them or not.
Or perhaps in future i will keep my findings to myself.
 
i just share my findings(FOR MY NEEDS), i dont care if people use them or not. Or perhaps in future i will keep my findings to myself.
Comments like these make me feel like you're taking things personally, but I wasn't actually targeting your posts. I was directing my comment to OP, whom I know from other posts he's made is focused on performance to some degree, as well as me trying to quell some misconceptions regarding WinSxS and performance as a general concept (for everyone else reading the thread), and that was the only intent behind my post.

Please keep in mind that although we have a lot of members here, we have countless times that number of people in the form of unregistered lurkers that view these threads, and they benefit from a multitude of viewpoints. It is important to discuss all aspects of something in a thread so that people can learn more and do additional research or testing if they desire. Unless something is blatantly incorrect, then everyone should be given the opportunity to express thier knowledge on a subject, if it's relevant.

My main concern after helping a ton of people here over the last year and a half, is that far too many people on this forum are suffering from the XY problem (link) and do a lot of bad tweaking or ask bad questions because of that. As 2 of the most active helpers on the forum it's something Garlin and I have discussed and both agree is a huge issue, so by taking the time to try to address a person's true goals, not just their direct questions, it helps people learn more and that turns into better questions and tweaking approaches.

In my previous post, I chose my wording very carefully and I still standby what I said. The summary I stated at the end clarified the intent, "If deleting files is important to you, then by all means please focus on it, but if improving performance is the main goal then WinSxS is not the right avenue to explore."

To summarize my reply here, if deleting files is important to any individual, then I urge those people to continue deleting things. All I was expanding on is that anyone hyper-focused on deleting files because they think it is a way to improve performance to some great extent are heading in the wrong direction, and I'm trying to help urge them onto a more productive path because my goal as a helper isn't ever to argue with people to be "right" I'm only trying to help save people from wasting time and being frustrated like I was over the years, as I learned these things the hard way (largely due to bad advice on the web).
 
Last edited:
I dont always know what i want until i see it or someone suggests it. I have showed him what is possible and its up to him whether he goes that route or not. Even if he doesnt remove it in full he can compare my results with his and with the default to see how well he has done. See how low that you can go and rollback where required. It is not advice, its what is possible.
 
Last edited:
OK, then send me a preset to demo 1 component, and tell me the leftover in WinSxS to check for.

Thanks.
hope these attachments help to find out what I do wrong

thanks in advanced
 

Attachments

  • winsxs after deep clean.jpg
    winsxs after deep clean.jpg
    44.9 KB
  • winsxs after deep clean.txt
    1.2 MB
  • winsxs before deep clean.jpg
    winsxs before deep clean.jpg
    44.4 KB
  • winsxs before deep clean.txt
    1.2 MB
  • Ntlite Winsxs.jpg
    Ntlite Winsxs.jpg
    124.7 KB
  • Winsxs Deep Clean.xml
    8.9 KB
Code:
        <RemoveComponents AppRemovalMode="DISM">
                <c>assembly.net '.NET assembly cache'</c>
                <c>langcatalan 'Catalan'</c>
                <c>langchineses 'Chinese Simplified'</c>
                <c>langchineset 'Chinese Traditional'</c>
                <c>langczech 'Czech'</c>
                <c>langime 'Input Method Editor (IME)'</c>
                <c>langimejp 'Japanese (IME)'</c>
                <c>langimeko 'Korean (IME)'</c>
                <c>langimetc 'Chinese Traditional (IME)'</c>
                <c>langindonesian 'Indonesian'</c>
                <c>manifestbackup 'Manifest Backup (WinSxS\Backup)'</c>
                <c>winsxs 'Windows Component Store (WinSxS)'</c>
        </RemoveComponents>

Comparing data before & after removals:
- 232 component folders are removed
- size on disk dropped 4 MB

Are you expecting to completely remove WinSxS to recover the maximum disk space? That's a licensed feature, which has been mentioned twice on this thread.

Component Removal is removing Windows packages.
WinSxS Cleanup is removing backup versions for components which have been replaced, making it impossible to uninstall updates.
Removing WinSxS makes installing updates or features impossible without NTLite's help.
 

Attachments

  • Screenshot 2023-07-10 234803.png
    Screenshot 2023-07-10 234803.png
    91.9 KB
  • Screenshot 2023-07-11 001057.png
    Screenshot 2023-07-11 001057.png
    90.7 KB
Code:
        <RemoveComponents AppRemovalMode="DISM">
                <c>assembly.net '.NET assembly cache'</c>
                <c>langcatalan 'Catalan'</c>
                <c>langchineses 'Chinese Simplified'</c>
                <c>langchineset 'Chinese Traditional'</c>
                <c>langczech 'Czech'</c>
                <c>langime 'Input Method Editor (IME)'</c>
                <c>langimejp 'Japanese (IME)'</c>
                <c>langimeko 'Korean (IME)'</c>
                <c>langimetc 'Chinese Traditional (IME)'</c>
                <c>langindonesian 'Indonesian'</c>
                <c>manifestbackup 'Manifest Backup (WinSxS\Backup)'</c>
                <c>winsxs 'Windows Component Store (WinSxS)'</c>
        </RemoveComponents>

Comparing data before & after removals:
- 232 component folders are removed
- size on disk dropped 4 MB

Are you expecting to completely remove WinSxS to recover the maximum disk space? That's a licensed feature, which has been mentioned twice on this thread.

Component Removal is removing Windows packages.
WinSxS Cleanup is removing backup versions for components which have been replaced, making it impossible to uninstall updates.
Removing WinSxS makes installing updates or features impossible without NTLite's help.
yup I thought its possible to get max space cause I was able to select "winsxs 'Windows Component Store", thanks for the info
 
Last edited:
Tested now on 22621.1, removed just WinSxS and turned off SFC compatibility option.
Using the licensed version size on disk of WinSxS folder is 3.81MB (excluding Manifests folder, remove that with 'Component database' component).
But using the free version, which allowed to uncheck it, there is no removal.

So yes, it's a legit UI bug, it should not have been unlocked, component date is from 2016.7.

Thanks.
 
Back
Top