What Is WinSxS and Why Is It 40GB on Your C: Drive?
The WinSxS folder looks like 40GB of pure dead weight, but deleting files inside it by hand will wreck your Windows installation. You open File Explorer or a disk analyzer, see C:\Windows\WinSxS sitting near the top of the size list, and reach for the delete key. Doing that stops cumulative updates from installing and can force a complete operating system reinstall. Here is what is actually inside that directory and how to safely reclaim the gigabytes.
What's Actually Going On
WinSxS (Windows Side-by-Side) stores multiple versions of DLLs and system components so different applications can run without DLL conflicts.
File Explorer drastically overstates the folder size because WinSxS uses NTFS hard links. A 100MB system file that appears in both C:\Windows\System32 and C:\Windows\WinSxS is only stored once on your physical drive, but Explorer counts it twice.
When Windows installs monthly patches, it keeps older versions of superseded binaries in WinSxS so you can roll back updates if your computer crashes.
How to Safely Shrink the Component Store
1. Run Dism.exe Component Store Analysis
Open PowerShell or Command Prompt as Administrator and run the built-in DISM analysis tool. This reports the actual physical size of the component store versus what File Explorer claims, and gives you a definitive recommendation on whether cleanup is needed.
Dism.exe /online /Cleanup-Image /AnalyzeComponentStore2. Execute DISM Component Cleanup
If the report shows Component Store Cleanup Recommended: Yes, execute the cleanup switch. This uninstalls superseded packages and shrinks delta compression blocks without breaking current features.
Dism.exe /online /Cleanup-Image /StartComponentCleanup3. Purge Service Pack and Superseded Rollbacks
If you are tight on disk space and confident your current Windows build is stable, add the ResetBase switch. This discards all superseded rollback states permanently and reclaims another 4GB to 10GB.
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBaseCaution: Running /ResetBase means you will not be able to uninstall any currently installed cumulative updates.
We got tired of doing this manually — that's exactly why we built Orbit.
Orbit breaks down true hard-link physical footprints instead of double-counting ghost sizes.One More Thing
Never use third-party cleaner utilities that promise to delete unreferenced files directly out of C:\Windows\WinSxS. Windows protects that directory with TrustedInstaller permissions for a reason.
If an automated script changes file ownership to Administrator and wipes DLLs inside WinSxS, your next Windows sfc /scannow check will fail with corrupted component store errors.
The Verdict
Use Manual Method if: Use DISM commands directly if you only need a quick one-time component store purge and you are comfortable running elevated PowerShell terminals.
Use Orbit if: Use Orbit if you want to see your real physical disk usage separated from NTFS hard links without guessing.
Finding these files too slow?
Orbit visualizes your entire drive — Mac and Windows both — so you see exactly where space is going before you delete anything.
Continue Reading
Windows Update checks free space differently than File Explorer shows it. Here is why the numbers do not match and how to clear real room before it fails again.
Read guide →DissectMac Alternative: A Storage Analyzer That Also Works on WindowsDissectMac is Mac-only. If you run Windows too, here is a storage analyzer that gives you the same visual clarity on both machines from one app.
Read guide →Uninstalling an App on Mac Doesn't Actually Delete ItDragging an app to Trash leaves behind caches, preferences, and support files — sometimes gigabytes. Here is how to find every leftover.
Read guide →