An issue with WinSxS deep cleaning

if they happen to be on a 32gb ssd which is only 29.Xgb after formatting then they gonna need all the space they can get.
 
if they happen to be on a 32gb ssd which is only 29.Xgb after formatting then they gonna need all the space they can get.

For those low end machines, I always suggest installing Debian + XFCE. It loads within 10 secs and occupies only 1GB RAM and <10GB space. Those PCs are not quite eligible to use Windows to run apps anyways.
 
I use ASUS mainboard (B650M-A WiFi) and display card (ASUS Dual 4070 Super) too. Guess we have something in common.

Unfortunately, my message is that with a current generation computer, removal of WinSxS to improve "performance" is simply a hassle that's not worth it. Even my 2018 HP Spectre Laptop does not see noticeable improvements.
Wrong, wrong. The purpose of deep cleaning WinSxS is to achieve faster deployment speed, and deleting it does not improve running speed.
 
The 1.7GB wim is so exciting to watch. It only takes twenty seconds to deploy.
 
Wrong, wrong. The purpose of deep cleaning WinSxS is to achieve faster deployment speed, and deleting it does not improve running speed.
I deploy my full-featured 10GB Windows WIM (with MS Office integrated) in 10 minutes to my Spectre laptop. Have you tested how many seconds can you improve?
 
Still cannot understand the hassle just to save some time during deployment, except if deploy your OS every day.
Indeed, I often redeploy virtual machines. I don't like Sandboxie and Windows Sandbox, I can only use virtual machines.
The important thing is that quick deployment is enjoyable, and I am a person with an urgent temperament.
 
Indeed, I often redeploy virtual machines. I don't like Sandboxie and Windows Sandbox, I can only use virtual machines.
The important thing is that quick deployment is enjoyable, and I am a person with an urgent temperament.
It already sounds like your main PC usage is "Watching deployments in 20 seconds continuously".
 
It already sounds like your main PC usage is "Watching deployments in 20 seconds continuously".
I will keep staring at it throughout the process, and if it keeps copying files and spinning, I will smash it with one hammer.
 
It already sounds like your main PC usage is "Watching deployments in 20 seconds continuously".
For this level of unhealthy OCD, I'm surprised he's not already using Unified Write Filter (UWF) on his LTSC image.
 
For this level of unhealthy OCD, I'm surprised he's not already using Unified Write Filter (UWF) on his LTSC image.
This is indeed a good idea
If I have Annie Ng's 64GB memory module, maybe I can try it out:rolleyes:
 
I have applied functional patches such as sha-2 and ie11 to Win7-sp1, and made slight optimizations. The final wim size is 1.55GB, which is less than 0.3GB more than completely removing WinSxS. How perfect this is.
This is Steve Ballmer's credit, but unfortunately he resigned.
 
Have you tried to install/enable all the Windows Features and capturing that as your Master image, and then creating NTLite'd images from that according to your purpose(s)?
 
Have you tried to install/enable all the Windows Features and capturing that as your Master image, and then creating NTLite'd images from that according to your purpose(s)?
OP wants to "have their cake and it eat it too", as the expression goes.

Capturing an installed image with the Features locked into place, and then stripping WinSxS, doesn't allow you the ability to later change them on demand.
 
Yeah :D

Given that what he desires is incongruous with the reality of things, and the fact wim size is his focus, he is either going to have to create various images for his specific purposes, or create an image with all features installed and then disabling services or such relating to these for his particular usage scenarios.

What size difference(s) would we be talking about in that all-feature-enabled image (meaning in the NTLite'd multi-image scenario)... If negligible, that could be a consideration. Or perhaps he should run one image with all features installed (and disabling certain services or tasks etc for his specific purposes/installs, as mentioned). I don't have the energy to try any of that out, but if I were in his (self-imposed) predicament, I'd experiment along these lines.
 
Given that what he desires is incongruous with the reality of things, and the fact wim size is his focus, he is either going to have to create various images for his specific purposes, or create an image with all features installed and then disabling services or such relating to these for his particular usage scenarios.
Yes, sir. You cannot have both fish and bear's paw.
Although some people have successfully replaced all components unrelated to "turning on or off Windows functionality" with hard links, this is still their secret unless they do charity work.
On my old computer, I will enable all necessary Windows functions and then delete WinSxS. It is necessary to keep it on the new computer because certain components such as MSMQ are only turned on when needed, otherwise it will slow down the startup speed.
I don't have the energy to try any of that out, but if I were in his (self-imposed) predicament, I'd experiment along these lines.
Yes, I basically don't manually disable services, it's not worth it. If one day you forget which component corresponds to a certain service, emm...... It will be very awkward
 
iso/wim sizes should only be an issue with fat32 partitions and single layer dvds 4.3gb usable once formatted(nero9), anything else is just a pi--ing contest. windows installs as it wants to and i dont give a rats jacksy how long it takes, its how it runs once you have fully set it up.
 
in all my years of using windows(xp sp1 and upwards) the only Feature i have ever enabled(or installed) is net 3.5 and 4.8.
you test test test to see what you need and what works, capture and lockdown Features if you want to.
 
Last edited:
Back
Top