An issue with WinSxS deep cleaning

Mr. Yu

Member
Messages
261
Reaction score
21
Hello, I never use Windows updates, but I use the "Turn Windows features on or off" option in the control panel.
I deleted the WinSxS backup and can only clean up a few hundred MB of files. If WinSxS is directly deleted, it will result in the inability to turn on or off Windows functions.
How to keep only the WinSxS files that enable or disable Windows functionality, and delete all others?
Thank you very much for providing me with the method!
捕获.PNG
 
I don't know if this is practical. If there is a way, then ntlite will definitely achieve a big breakthrough.
 
Removing WinSxS folders will prevent all Servicing Stack operations from working, because that's how Windows packages are enumerated. There is no other package database other than the component folders, and reg entries directly related to them.

It's not worth fighting this hard to squeeze the last few GB's of Windows overhead on a modern PC. Unless you're running on a 32GB SSD, everyone should have 500 GB+ drives by now.

Decide whether having the ability to update Windows (which includes Features On Demand) is worth the disk overhead or not. If you're running out of disk space, it's probably mostly your fault and not Window's.
 
No, no one cares about the size after installation. Any next game in Steam requires 50G+. Everyone cares about the usage of memory modules, not the usage of hard drives.
Many internet cafes nowadays use LTSC versions, or their technicians streamline customized systems.
As long as you have ideas about space, it must be the size of iso. I need to deploy the image quickly instead of slowly copying 4.5+GB files. I have resolved the issue with the installation files in ISO..
I only need the issue of wim size now. Russian lopatkin's streamlined system replaces files in WinSxS with hard links, reducing the wim size of ltsc2021 to 2.3GB.
My original intention for streamlining is rapid deployment, extremely low memory, simplified installation steps, and extremely high stability.
I believe ntlite knows the meaning of every file in WinSxS. If it could be streamlined, that would be great.
I believe that the implementation of these ideas is only a matter of time. NTlite has already achieved a lot in this area.
 
Last edited:
 
Thank you, Clanger's method is to directly delete WinSxS. This method can reduce the wim of ltsc2021 to around 1.7GB.
As I said, this will directly delete the source files for enabling or disabling Windows features.
 
wrong, it does not delete winsxs as you can clearly see.
1.7gb? is that installed size or wim size?
installed size is very impressive for w10 considering i got w7 64bit pro installed at 1.26(1.16??)gb. if 1.7gb is the wim size then meh, install.wim size is usually around 1/3rd of the installed/extracted size, in that case i estimate around 5gb installed and i can get(on or around) that just by trimming the fat.

i feel it is better to "lite" on a full default system, especially if you have issues, its harder for nuhi to bug hunt for a lited system.
 
Last edited:
1.7gb? is that installed size or wim size?
I'm referring to install.wim
wrong, it does not delete winsxs as you can clearly see.
I loaded this preset in both Windows 7 and Windows 10, which removed the Windows Component Library and its sub components, Winsxs Backup and Winsxs.
installed size is very impressive for w10 considering i got w7 64bit pro installed at 1.26(1.16??)gb. if 1.7gb is the wim size then meh, install.wim size is usually around 1/3rd of the installed/extracted size, in that case i estimate around 5gb installed.
Yes, about 5-6GB after disabling reserved storage.
 
not so impressive now is it? wim sizes only matter when you are trying to burn a bootable single layer dvd where nero says the maximum availible space after formatting is 4.3gb.
 
not so impressive now is it? wim sizes only matter when you are trying to burn a bootable single layer dvd where nero says the maximum availible space after formatting is 4.3gb.
No, it's not just slow deployment in PE. I am used to frequently reinstalling virtual machines, and a very small iso can save a lot of time.
 
With 64GB DDR5 RAM installed, I will probably never understand the hassle.
Of course, if the system starts up, it will take 10 GB, and the corresponding startup speed will be very slow. Perhaps it will take 5 minutes to turn on the device.
 
Of course, if the system starts up, it will take 10 GB, and the corresponding startup speed will be very slow. Perhaps it will take 5 minutes to turn on the device.
Within 10 secs. I benchmark it from time to time with my watch.

Guess the longest time it takes before booting? It is DDR5 memory testing, which takes 20 sec to complete.
 
Within 10 secs. I benchmark it from time to time with my watch.

Guess the longest time it takes before booting? It is DDR5 memory testing, which takes 20 sec to complete.
I am just exaggerating the description.
I have never used DDR5, perhaps only a desktop computer can install it?
I am a fan of Asus, and its laptops rarely support DDR5.
 
peoples budgets vary, they buy new or used machines on a very tight budget or get given an old machine. theres an old arm64 thread round here that deals with a soldered ram machine.
 
I am a fan of Asus, and its laptops rarely support DDR5.
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.
 
Back
Top