How to Clean the WinSxS Folder Safely with DISM

What the WinSxS folder holds — and why it looks bigger than it is

The WinSxS folder (Windows Side-by-Side) is the component store: it keeps every version of every system component Windows has installed since setup, plus the metadata that lets updates, features and servicing work. When a cumulative update replaces files in System32, the older versions stay in WinSxS so the update can be uninstalled and features repaired without original media. On a two-year-old installation it commonly reaches 6–15 GB.

The size Explorer reports is also misleading. Files in System32 and WinSxS are hard links — one physical copy of the data, counted in both places — so simply adding up folder sizes double-counts gigabytes that exist only once. That is why a 12 GB WinSxS folder is not stealing 12 GB from your disk, and why no third-party “WinSxS cleaner” can honestly promise the number it shows.

• Superseded component versions left after each cumulative update — the main growth driver
• Backups that make updates uninstallable — only /ResetBase removes them
• Payloads of optional features (RSAT, .NET 3.5, language packs) — needed if you install the feature later
• Hard links shared with System32 — one file, counted in several folders
• The DISM analysis reports honest numbers: “Actual Size of Component Store” vs “Shared with Windows”

The safe cleanup: two DISM commands

Open the command prompt as administrator and first run the read-only analysis: Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore. It takes a minute or two and ends with the line “Component Store Cleanup Recommended : Yes” or “No”, plus the actual size of the store and how much of it is shared with Windows. If it says No, there is nothing to gain — close the window and move on.

If cleanup is recommended, run Dism.exe /Online /Cleanup-Image /StartComponentCleanup. It removes superseded component versions, keeps the machine updateable, and can run 10–30 minutes with the DISM process apparently idle — let it finish, because interrupting it is the source of the rare corruption stories. Adding /ResetBase removes every superseded version and shrinks the store further, but after that no installed update can be uninstalled — a fair trade only on a stable machine you never roll back.

What never to do — and keeping WinSxS under control

Three things must never happen: deleting or moving files inside WinSxS by hand (including “just the big ones”), pointing a registry cleaner or a “system optimizer” at the folder, and enabling NTFS compression on it. Each of these damages hard links or servicing metadata, and the result ranges from updates that fail to install to a system that no longer boots. The component store has exactly one supported cleanup path: DISM and its Disk Cleanup equivalent, the “Windows Update Cleanup” item.

Windows already helps on its own: the built-in scheduled task \Microsoft\Windows\Servicing\StartComponentCleanup runs the same cleanup automatically in the background, waiting roughly 30 days after a component is superseded before removing it. A manual pass earns its keep after big cumulative update sessions or before imaging a machine. For everything around the component store — temp files, Delivery Optimization leftovers, old caches — scheduled cleaning in Kleaner PRO keeps the rest of the drive in shape, while WinSxS itself remains DISM territory.

Questions and Answers

Read next

All articles · FAQ