The WinReducer Forum
Would you like to react to this message? Create an account in a few clicks or log in to continue.

The WinReducer ForumLog in


description"WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)" Empty"WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)"

Hello to all,
the intent of this topic is to bring some clarifications about these two features and fill up the lack of information.
Below are my findings (Windows 10 Pro + current cumulative update integrated, WR and someone expert may want to correct me if I am saying something wrong.
One option excludes the other and when both are selected, folder cleanup takes precedence.

------------WinSXS Folder cleanup (install.wim)------------
As stated in the field info, it breaks windows updates, windows features, windows error reporting service and Modern Apps UI View.
- windows features can still be enabled/disabled, but this must be done through WR. Once we are in the OS, every attempt to change features will return an error.
- Windows updates (like removal tools, definitions and others except cumulative updates) can be still successfully installed through a nice app called WuMgr.
- I didn't experienced any breakage on Modern Apps UI View. When I open the start menu they all display correctly and I can move, delete and perform any operation on tiles. Therefore someone that has this problem could explain what he is experiencing so that we can all find out if there is some component responsible for this.

The Windows update and related components I removed are:
Windows Error Reporting Service
Windows Update Medic service
Update Orchestrator service
Background Intelligent Transfer Service
Modern UI Apps - settings - Windows Updates
hide "update and Security - Windows Update
server initiate healing
Azure active directory
Collaboration data objects (CDO)
Data deduplication
Internet Explorer (Engine)
Gracenote (GNSDK)

> Total Install Size ("C:\" drive): 7.2 gb
> WinSXS folder size: around 64 Mb

------------WinSXS Folder compression------------
The only algorithm that made difference in size is LZX. It adds 10 minutes to the building process, but also in the install process. During "Getting ready" step, it starts the servicing tool and what I believe should be the compression task, can take an hour or two before booting into the desktop (I attached a picture).
All windows update related components above has been restored.

> Total Install Size ("C:\" drive): 8.65 gb
> WinSXS folder size: 4.90 Gb (don't know why does not show the real compressed size)
> Windows Update works (except cumulative ones, but these are nearly impossible to install in extreme presets, no matter if all optimizations are disabled)
> Windows features works
> Modern UI app view works
After installing a malware removal tool from the WU, I saw the WinSXS folder growing from 4.90 Gb to 5.01 Gb, but strangely the total install size has grown from 8.65 Gb to  9.81 Gb and that is not good (not sure if this really depends from updates, I have just reinstalled the above iso and I experienced the same)
However is not clear in what way the compression is preserved. I am out of idea and hope that someone know the response.

So, in this test the folder cleanup only gained additional 1.45 Gb in install size compared to maximum folder compression (and if other better algorithms can be adapted, the difference could be pretty much non existent).
This is something that users should take in consideration before deciding what to choose, especially considering what breaks the folder cleanup. Yes, compression slows down a lot the installation and this is not good for people that often reinstall a winreduced iso. However I suppose that the compression task can be done directly from within the operating system, but I have not been able to find out what is the required DISM command. Someone know?

I should also say that in a topic winterstorm said that the folder compression breaks windows update (please if there is this risk, inform the user through the field info in WR app!), but I think he was referring to cumulative updates which in extreme presets don't work in any case. Please correct me if I am wrong in this assumption!
This is just a basic quick test and I am not sure if there are any other pros and cons.

Hope that other people can contribute with their experience.
Thanks to all!

"WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)" 2020-010

description"WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)" EmptyRe: "WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)"

Windows 10 are very self aware of how extremely bloated they are and came with a nice feature called "Compact OS", which is an LZX compression of the entire system that works on the fly. 
No need to compress just the WinSxS alone, when you can compress everything. 
Look it up. 
Also look up the WinNTSetup utility that does the whole Windows installation, including "Compacting" it, a lot easier.

description"WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)" EmptyRe: "WinSXS Folder compression" VS "WinSXS Folder cleanup (install.wim)"

Sorry for my delay, but I wanted to come back with some new findings.

It appears to be that I discovered another bug (other than the severe ones I already reported with no response from the author) and this time in folder compression feature of WR. Compression starts when applying changes and on post installation as expected, but basically compresses the whole system (everything! programs files, windows folder etc) except the target WinSXS folder.
This is why the above results was showing the same size even on disk. After compressing with Win10 tweaker pro or Compact command I was able to reduce the folder to the expected size (2.32 Gb).
Not sure if I should report this as a bug or not.
I must revise my considerations in terms of space saving. By cleaning the WinSXS folder we can expect much more saving compared to folder compression, even more in case of integrated updates.

Compressing with Win10 tweaker made the system unusable during the whole task (and this also applies to WR compression feature) while compressing with the compact command didn't. Although the resulting compressed size is the same (except for WR which I can't quantify because it skip the target WinSXS folder), I am wondering if they use different mechanisms and what could be the difference.

I don't think that compacting the whole system is a good idea due to perfomance implications. When I query the compactOS state, I get a message stating that it isn't because windows evaluated that is not beneficial.
Windows should automatically start compacting when can see benefits (other than when forced due to low disk of space).

I also tried to manually delete the content of WinSXS folder, but I was unable to delete a good number of files because opened in processes and for some other reasons. This make me think that this is not just static data which resides in this folder and called from Windows just for the update process.
It make me think that it silently consumes resources (RAM, Cpu, etc) even when the system is not updating.
So, cleaning the WinSXS folder can result not only in great space saving, but also in great performance boost, but I am just speculating and I am afraid that only Winterstorm or someone else expert can illuminate us because sincerely I still have lot of doubts on the real pros and cons!

Regarding WinNTSetup utility, do not take this as an offense and I really appreciate your help, but I would not recommend to anyone in this world to even think about it unless they are martyrs who enjoys to totally break their system and lose time for nothing.
Last update of this tool is nearly one year ago! It recognized my 1909 iso as a 1903 iso. I don't even want to think of what could happen by patching a mismatched iso version!
Plus, all the other tweaks and tasks are already included in WR.

privacy_tip Permissions in this forum:
You cannot reply to topics in this forum