Cleaning Up After Windows Updates: Reclaiming Space From WinSxS Safely
Windows Update keeps your PC secure and supported, but months of cumulative updates and component changes can leave the system drive with less free space than expected.
When people investigate, one folder often looks enormous:
C:\Windows\WinSxS
That is the Windows component store.
It contains files Windows needs for:
installing updates
enabling optional features
repairing Windows
servicing system components
uninstalling supported updates
It is not an ordinary temporary folder.
The golden rule is:
Never manually delete files from WinSxS.
Use Windows' own servicing tools instead. Microsoft explicitly warns that manual deletion can make Windows unserviceable or even unbootable.
Why WinSxS Looks Bigger Than It Really Is
If you right-click:
C:\Windows\WinSxS
and select Properties, Windows may report a surprisingly large figure.
That number can be misleading.
Windows uses hard links, meaning the same underlying file can appear in multiple places without occupying a completely separate copy of the storage each time.
So a file may appear under:
C:\Windows\WinSxS
and elsewhere in Windows while sharing the same physical data.
This means:
Explorer-reported WinSxS size ≠ removable WinSxS overhead.
Use DISM to analyse the component store instead. Your existing article already explains this distinction correctly.
Step 1: Analyse the Component Store
Open:
Terminal (Admin)
or:
Command Prompt (Admin)
Run:
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
This does not remove anything.
It reports information including:
Explorer-reported size
actual component-store size
files shared with Windows
backups and disabled features
reclaimable packages
whether cleanup is recommended
The most useful line is:
Component Store Cleanup Recommended : Yes
If it says:
Yes
then a component cleanup may recover worthwhile space.
If it says:
No
WinSxS probably isn't where I would spend much more time.
Step 2: Start With Windows Storage Settings
Before using advanced DISM options, open:
Settings > System > Storage
Check:
Cleanup recommendations
and:
Temporary files
Microsoft currently recommends Storage Sense and Cleanup Recommendations as the normal first-line ways to free space in Windows 11.
Depending on the PC, you may find categories such as:
Windows Update Cleanup
temporary Windows files
Delivery Optimisation files
Recycle Bin
previous Windows installation
temporary application data
Review the categories before deleting them.
Do not simply tick everything.
Be Careful With the Downloads Folder
Storage Sense does not delete Downloads by default, but it can be configured to do so.
Microsoft confirms that Downloads and locally available cloud content are only cleaned according to settings you choose.
So check the configuration before running an automated cleanup on somebody's business laptop.
Windows.old Is Not WinSxS
After a feature update, you may also find:
C:\Windows.old
This contains the previous Windows installation.
It can consume considerable storage.
Windows allows it to be removed through:
Settings > System > Storage > Temporary files
But removing it also removes the normal ability to roll back to the previous Windows release.
Microsoft provides this cleanup route through Storage settings.
So only remove it when:
the feature upgrade has been tested
applications work
hardware works
files are present
you are confident rollback is no longer required
Do not confuse:
Windows.old cleanup
with:
WinSxS component cleanup.
They are different things.
Step 3: Run the Standard WinSxS Cleanup
If DISM reports reclaimable components, run:
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
Microsoft describes this as the supported method for removing superseded component versions from the running Windows installation.
This is the command I would recommend for most advanced users.
It removes eligible older component versions immediately rather than waiting for Windows' normal maintenance grace period.
Let it finish.
Do not:
force the PC off
start another Windows servicing operation
assume it has frozen because progress pauses
When it completes, restart Windows.
Then run:
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
again.
Compare the results.
Windows Already Cleans WinSxS Automatically
You do not normally need to run this command regularly.
Windows has a scheduled task called:
\Microsoft\Windows\Servicing\StartComponentCleanup
Microsoft says its automatic version waits before removing older components and has a one-hour execution limit. The direct DISM command performs similar cleanup without that normal grace-period behaviour or timeout.
You can also manually trigger the scheduled task:
schtasks.exe /Run /TN "\Microsoft\Windows\Servicing\StartComponentCleanup"
But there is little benefit in turning component cleanup into a weekly ritual.
If Windows has already maintained the store properly, there may be very little to reclaim.
What About /ResetBase?
You will often see this command recommended:
Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase
It is supported.
It is also much more consequential.
Microsoft says /ResetBase removes all superseded versions of every component in the component store. After it completes, all update packages currently installed at that point can no longer be uninstalled individually. Future updates are not permanently affected.
That means /ResetBase is not just:
“clean harder.”
It changes your rollback options.
When I Would Use /ResetBase
I would consider it only when:
Windows is stable
recent updates have been tested
all required restarts are complete
important applications work
the PC is backed up
the extra storage is genuinely valuable
you accept losing the ability to uninstall currently installed update packages
For most ordinary cleanup:
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
is the better choice.
When I Would Not Use /ResetBase
Avoid it when:
a recent update may be causing problems
Windows is unstable
you are considering uninstalling an update
updates are pending
a restart is pending
the machine is business-critical and still within an update-validation period
Your current article handles this warning well, and I would definitely retain it.
Cleanup and Repair Are Different Things
These commands are frequently mixed together online.
They do different jobs.
Analyse component-store size
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Remove superseded components
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
Permanently establish the current component baseline
Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase
Check for known component-store corruption
Dism.exe /Online /Cleanup-Image /CheckHealth
Scan for component-store corruption
Dism.exe /Online /Cleanup-Image /ScanHealth
Repair Windows component-store corruption
Dism.exe /Online /Cleanup-Image /RestoreHealth
RestoreHealth is a repair command, not a disk-cleanup command.
Running every DISM switch you can find in one enormous command sequence is not good troubleshooting.
Use the command that addresses the actual problem.
What If Component Cleanup Fails?
Start simply.
1. Restart Windows
Use:
Start > Power > Restart
Then return to Windows Update.
2. Complete Pending Updates
Open:
Settings > Windows Update
Install pending updates and complete every requested restart.
3. Analyse Again
Run:
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
4. Check Component-Store Health
Run:
Dism.exe /Online /Cleanup-Image /ScanHealth
If corruption is reported:
Dism.exe /Online /Cleanup-Image /RestoreHealth
Then:
sfc /scannow
A cleanup operation repeatedly failing alongside Windows Update or filesystem errors may indicate a wider servicing or storage problem rather than merely a bloated component store.
Why You May Recover Much Less Space Than Expected
Suppose File Explorer makes WinSxS look like:
18 GB
You run component cleanup and recover:
900 MB.
That does not mean DISM failed.
Possible reasons include:
much of the apparent size is hard-linked Windows data
automatic cleanup already ran
few packages are actually superseded
Windows still needs the components
recovery versions remain intentionally retained
Microsoft specifically notes that Explorer can substantially overstate the unique storage attributable to WinSxS because of hard links.
Judge the cleanup by:
actual free space
DISM's component-store analysis
number of reclaimable packages
not the WinSxS Properties dialog.
WinSxS May Not Be Your Real Disk-Space Problem
If C: is still nearly full after component cleanup, look elsewhere.
Common large consumers include:
Windows.old
crash dumps
Delivery Optimisation files
temporary installation data
restore points
user profiles
OneDrive offline content
application caches
hibernation file
page file
Windows' current Cleanup recommendations page can help identify temporary, unused and cloud-synchronised data worth reviewing.
This is another reason not to become obsessed with WinSxS simply because it looks enormous.
Do Not Delete These Manually
Do not manually delete files from:
C:\Windows\WinSxS
Do not:
change ownership of WinSxS
grant yourself Full Control
run third-party “WinSxS cleaners”
delete random manifest/package folders
use a script that purges component-store directories
Microsoft's supported component-cleanup mechanisms exist because the servicing store contains relationships between packages, manifests, hard links and active Windows components.
Manual deletion bypasses all of that servicing logic.
The Safe Cleanup Order
For a Windows 11 PC running low on disk space:
1. Open Settings > System > Storage.
2. Review Cleanup recommendations and Temporary files.
3. Run:
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
4. If cleanup is recommended, run:
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
5. Restart.
6. Analyse the store again.
7. Consider /ResetBase only if you knowingly accept the rollback trade-off.
8. If storage is still low, investigate other large consumers instead of attacking WinSxS manually.
The key rule is:
Let Windows service the Windows component store.
How Hamilton Group Can Help
Hamilton Group can help businesses diagnose Windows storage problems without damaging the servicing components that Windows Update and recovery depend on.
We can assist with:
Windows 11 storage
Windows Update
WinSxS
DISM
component-store corruption
SSD capacity
storage cleanup
device maintenance
workstation replacement planning
For business fleets, we can also identify whether low storage is isolated to one computer or whether a device specification, update process or storage policy is causing the same problem across multiple machines.
Visit hgmssp.com or call 0330 043 0069.