Windows Explorer and third-party programs report a size of several Gigabyte at the very least, but the count can go up to ten and more Gigabytes depending on the system it is analyzed on.
WinSXS, the full path is c:\Windows\WinSXS\ if Windows is installed on the c: drive, contains files that are required for servicing operations such as the installation of updates, service packs or hotfixes.
According to Microsoft, the component store contains "all the files that are required for a Windows installation", and since it also holds files added by updates, it grows over time on all systems.
The size of the folder is not reported correctly however if you use Windows Explorer or third-party tools like WizTree to analyze its size.
The reason for that is that it contains hardlinks which Explorer and third-party tools don't take into consideration when calculating the WinSXS folder's size (they count the hardlinked files even though they don't reside in the WinSXS folder).
These hardlinks point to files in other Windows directories, for instance c:\Windows\system32.
A proper way to analyze the Window WinSXS component store directory is to use dism.exe.
Deployment Image Servicing and Management (DISM) was introduced by Microsoft in Windows Vista and has been part of new versions of Windows ever since.
Update: Please note that the commands will only work on Windows 8 or newer machines.
Here is what you need to do to analyze the WinSXS Folder:
The parameter /Online refers to the current installation, and /Cleanup-Image /AnalyzeComponentStore is the command to analyze the current component store of that installation (the WinSXS folder).
You can list all available commands using dism.exe /?, and subsequently dism.exe /Online /? and dism.exe /Online /Cleanup-Image /?.
The command runs a scan that takes a moment to complete. It echoes the Windows Explorer size and actual size to the command prompt window, and gives recommendations whether it makes sense to run a cleanup operation.
The command echoes the actual size of the folder as well which may be very useful as it highlights usually that the component store is not as large as third-party programs or Explorer make it appear to be.
Windows runs a cleanup regularly using the Task Scheduler. You can check if that is the case on your machine in the following way:
You can run the cleanup operation manually at any time using the following command using an elevated command prompt:
dism.exe /Online /Cleanup-Image /StartComponentCleanup
It is usually not necessary to run a cleanup unless the AnalyzeComponentStore analysis recommends it.
You can however use Disk Cleanup to free up disk space, and run an analysis afterwards to remove files from the WinSXS folder that are no longer required.
Basically, if you remove previous versions of Windows then you may end up with components in the WinSXS folder that are no longer required because they were valid only for the previous version of Windows.
Why is the WinSXS folder so big?
Most programs report an incorrect size for the WinSXS folder because of hardlinks. Hardlinks point to other locations on the device.
Should I clean up of the WinSXS folder?
It is usually not necessary to clean up the folder manually as Windows does so automatically on schedule.
Now You: How big is your system's WinSXS folder?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.