How to Cleanup the WinSxS Folder Safely in Windows (2026)

The safest way to clean up the WinSxS folder is to use the tools built into Windows: the StartComponentCleanup task, DISM.exe, and Disk Cleanup. Don’t delete anything by hand. These methods remove older components and replaced components and leave the system files your operating system depends on intact.

Support technicians hear the same story all the time. Someone running Windows 10 on a small SSD opens File Explorer and sees a WinSxS folder that looks quite large. Then they start hunting for a way to wipe it. Few “cleanup” habits break more PCs than that one.

The purpose of the WinSxS folder explains why. It holds the components that make rollback possible, from uninstalling packages to restoring previous versions after an update misbehaves. Some files there should never be deleted. Others become dead weight after a period of time, once newer versions have proven stable.

Here’s what practitioners want every reader to understand before touching anything:

• Windows automatically reduces the store through its own internal processes, and many superseded files are automatically removed without any help from you.
• On Windows 10 or later, manual cleanup either speeds up that process or goes further than Windows would on its own.
• Deleting packages at random has a lasting negative effect on system programs and can corrupt the whole Windows installation.
• You can safely reduce the size of WinSxS. You should never remove it.

The baseline rule is simple: don’t delete the WinSxS folder. Trim it.

How to Clean Up the WinSxS Folder

You shrink WinSxS by running a cleanup of the component store with Windows’ servicing tools, not by deleting files in File Explorer. The three supported options are the StartComponentCleanup scheduled task, DISM.exe, and Disk Cleanup. Each one removes superseded packages in a targeted manner.

The amount of data displayed in File Explorer rarely matches actual consumption on disk, so it’s important to know what’s really there first. Experienced admins measure the store before they clean it. The measurement command appears later in this guide.

Why Manual Deletion Backfires

Some users try to delete files in WinSxS directly by taking ownership and arbitrarily accessing the contents of the folder. This almost always has a detrimental effect. After that kind of uncontrolled package deletion, it’s often no longer possible to uninstall updates, add Windows features, or install the next cumulative update. Technicians who inherit these machines usually have to reset the PC because there’s no clean way to rebuild what was removed.

Comparing the Number of Ways to Trim WinSxS

There are a number of ways to clear the system of unused files and legacy data. The main difference between them is how aggressive they are.

Most people try Disk Cleanup first because it lives in the familiar Windows interface. Admins who need to cut the size of the directory further move on to DISM. Whichever method you choose, the goal is to reduce the size of WinSxS without touching anything Windows needs to keep running. Step-by-step instructions for each method follow below.

What Is WinSxS / What Does the WinSxS Folder Do?

WinSxS, short for Windows Side by Side, is the component store. It’s an essential part of Windows that keeps the system files, components, and previous versions needed to install, update, repair, and roll back the operating system. It sits inside the Windows folder and supplies files to almost every servicing job and installation process the OS runs.

Where the Name Came From

The side-by-side idea dates back to Windows XP. Microsoft needed a fix for “DLL hell,” the compatibility problems that appeared when two applications or programs needed different versions of the same shared library. Storing multiple versions side by side solved that. Starting with Windows Vista, the SxS folder grew into the full component store that services the entire OS.

What Lives Inside

• Updates and hotfixes: When new updates or hotfixes arrive, Windows writes the newer version into the store and keeps older copies as backups.
• Legacy service packs: On older releases, service packs and their uninstall files lived here too.
• Optional features: When you customize Windows by turning on optional features, those installations often pull their files from the store instead of downloading them.
• Additional file versions: These act as reference points for recovery. If an update causes unexpected difficulties after a reboot, Windows can restore the system to an earlier state.
• Servicing records: The store keeps up-to-date information about the status of the operating system and your current setup. Repair tools rely on these records.

Even basic standard functions, such as printing documents or opening individual files, depend on components serviced from this store. So do the Windows services that start at boot.

Why It Looks Bigger Than It Is

Most files in System32 aren’t separate copies. They’re hard links, which means the same data on the hard disk can be reached from two locations. When you open the folder’s properties, Explorer counts the size of the linked files in both places. Practitioners call the result “virtual gigabytes“: several gigabytes that appear to belong to WinSxS but are actually shared with the rest of Windows. Because of these links, the raw folder size is a poor guide for cleanup decisions.

Can / Should You Delete the WinSxS Folder?

No. Deleting the entire WinSxS folder can severely damage Windows, to the point that your PC might not boot. Even a partial manual purge can make the system impossible to update. Microsoft strongly recommends using component cleanup tools to reduce the size of the store instead.

The reason is structural. WinSxS is the central starting point for update processes and a large number of functions. It’s part of the basic structure of the OS, not an optional cache. Deleting files from it one at a time is generally not recommended either, because Windows can’t tell which pieces are missing until something breaks.

The Real Problem Worth Solving

The accumulation of unnecessary files is still real. Old Windows Update files, outdated system files, and other unnecessary system files pile up. Freeing up disk space matters a lot on 64 GB tablets and budget laptops. The tools built into Windows can work out which files are safe to remove.

The Opposite Mistake

Some admins go the other way and start disabling component cleanup so every state in the previous history can be restored if needed. That sounds cautious. In practice, it uses valuable disk space for a rollback window most users never need. A nearly full system drive also works against optimal system performance and the stability of Windows during update routines.

Don’t Confuse It With Windows.old

After an upgrade from an older version of Windows, a separate Windows.old folder appears. That one can be removed, either automatically after a set period or through Disk Cleanup. People who track down a “huge Windows folder” sometimes mix up the two.

The short version for skimmers: don’t delete the WinSxS folder. Clean it.

Task Scheduler

Windows automatically cleans up WinSxS through Task Scheduler. The built-in StartComponentCleanup task is set to run automatically when the system isn’t in use. It removes previous versions of components once an updated component has been installed for at least 30 days.

The waiting period is intentional. Windows is designed to wait at least 30 days so you can still try uninstalling an update if it causes trouble. The task also runs under a 1 hour timeout, so on a machine with a very large store it may not completely clean up all files in a single pass.

Practitioners who manage laptops that rarely sit idle often find the task never gets a chance to run. That’s a good reason to trigger it manually.

Run the StartComponentCleanup Task in Task Scheduler to Clean Up and Compress Components

You can trigger the cleanup on demand in two ways. Open Task Scheduler and run the StartComponentCleanup task in the Servicing folder, or call the task from the command line with schtasks.exe. Either way, Windows will clean up superseded files and compress components that it keeps.

Using the Task Scheduler Window

1. Press Win + R, type taskschd.msc, and press Enter to start the Task Scheduler.
2. In the console tree, expand the folders and navigate to Task Scheduler Library\Microsoft\Windows\Servicing\StartComponentCleanup.
3. In the Selected Item pane, click Run.

Using the Command Line

schtasks.exe /Run /TN “\Microsoft\Windows\Servicing\StartComponentCleanup”

The /TN switch names the task, so this command does the same thing as clicking Run. Admins who run cleanups through scripts or remote sessions prefer this method. It still follows the 30-day rule.

DISM.exe

Dism.exe (Deployment Image Servicing and Management) gives advanced users more options to further reduce the size of the WinSxS folder through its /Cleanup-Image parameter. It works on the running system and on mounted images, and it skips the waiting periods built into the scheduled task.

All three run from an admin prompt. They only affect the WinSxS folder’s servicing data, never your personal files.

Use the /StartComponentCleanup Parameter

The /StartComponentCleanup parameter gives similar results to the StartComponentCleanup task in Task Scheduler. The difference is that previous versions of updated components are immediately deleted, without a 30 day grace period, and there’s no 1-hour timeout limitation.

Open an elevated command prompt and run:

Dism.exe /online /Cleanup-Image /StartComponentCleanup

What Each Part Does

• Dism.exe launches the servicing tool.
• /online targets the running version of Windows instead of an offline image.
• /Cleanup-Image tells DISM to perform cleanup operations.
• /StartComponentCleanup removes superseded components.

This works on Windows 10 or later. Practitioners usually run it a few weeks after Patch Tuesday, once they’re confident the latest update is stable. Skipping the 30 day grace period right after a fresh update means losing the older component versions that would otherwise act as a safety net.

Use the /ResetBase Switch With the /StartComponentCleanup Parameter

Adding the /ResetBase switch to the /StartComponentCleanup parameter removes all superseded versions of every component in the component store. This is the biggest single reduction DISM offers. The trade-off is permanent: all existing update packages can’t be uninstalled afterward.

From an elevated command prompt on Windows 10 or later, run:

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

Warning: Once the /ResetBase parameter runs, every update currently installed on the running version of Windows becomes part of the baseline. DISM.exe won’t block uninstallation of future update packages, but nothing installed before the reset can be rolled back.

Deployment engineers often run this on a reference machine just before capturing a golden image, so every PC deployed from it starts lean. On a daily-use machine, it’s best saved for a stable period after several weeks with no update problems.

Use the /SPSuperseded Parameter

The /SPSuperseded parameter removes the backup components needed for uninstallation of the service pack, which reduces the amount of space the store uses. A Service Pack is a collection of cumulative updates for a particular release of Windows.

From an elevated command prompt, run:

Dism.exe /online /Cleanup-Image /SPSuperseded

Warning: After this command finishes, the service pack cannot be uninstalled from the running version of Windows.

Practitioners rarely use this switch today. Modern Windows ships feature updates instead of service packs, so on current builds Dism.exe often finds little or nothing to reduce. It mattered most in the Windows 7 SP1 and Windows Server 2008 R2 SP1 era, when service pack backups could take up a noticeable share of a drive.

Disk Cleanup

Disk Cleanup can reduce the size of the component store through its Windows Update Cleanup option. It also clears temporary files, the Recycle Bin, and a variety of other items in the same pass. It’s the most beginner-friendly of the three tools because everything is done with checkboxes.

Microsoft describes the utility as a way to help your PC run faster. In practice, its main benefit is reclaiming space on crowded drives. It can empty the Recycle Bin, delete leftover setup logs, and reduce the number of unnecessary files across the system.

There’s one catch. The option to cleanup updates only appears after you tell the tool to scan system files. The next section covers that step.

Run Disk Cleanup to Delete System Files

To delete system files with Disk Cleanup, open the tool, click Clean up system files, select Windows Update Cleanup, and confirm. The steps take a few minutes.

1. Search for Disk Cleanup in the Start menu and open it.
2. Choose drive C: if prompted.
3. Click Clean up system files and select C: again.
4. Wait while the tool recalculates.
5. Check Windows Update Cleanup and any other categories you want removed.
6. Click OK, then Delete Files.

The Disk Cleanup process can stay on “Windows Update Cleanup” for a long time and may look frozen. Technicians who run Disk Cleanup on older hard drives learn to leave it running, because interrupting it is worse than waiting. Restarting afterward gives Windows a chance to finish removing system files that were in use.

What Is WinSxS and Where Is the WinSxS Folder Located?

The WinSxS folder is located at C:\Windows\WinSxS on the system drive, directly inside the main Windows directory. Its role as the component store is covered above, so this section focuses on finding it and knowing what size to expect.