Quick fix: Don’t move WinSxS — instead, shrink it with DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase. Moving WinSxS breaks the entire servicing stack and is not supported by Windows; the right approach is to reduce its size in place.

You see C:\Windows\WinSxS showing as 12+ GB in WizTree or File Explorer and assume it’s safe to relocate to another drive. It is not. WinSxS is the Windows component store — Windows Update, system file repair (sfc), DISM, and feature install all read from it via hard-coded paths. Moving it to D: breaks every one of those mechanisms and can prevent the OS from booting after the next update.

Symptom: WinSxS folder is large; you want to move it to another drive to free C: space.
Affects: Windows 11 (and Windows 10) on systems with small C: drives.
Fix time: ~30 minutes for the recommended in-place cleanup.

What causes this

WinSxS contains side-by-side versions of every patched system file. Windows uses hard links extensively — many files appear in both C:\Windows\System32 and C:\Windows\WinSxS, but on disk they’re a single file. WizTree and File Explorer count the size twice, making WinSxS look larger than it actually is on disk.

The actual footprint of WinSxS is typically 5-8 GB, not the 12+ GB it appears to be. And of that 5-8 GB, several GB are superseded components (older versions of patched files) that are recoverable via cleanup commands. Moving WinSxS to another drive breaks the hard link relationships entirely.

Method 1: Analyze the true size of WinSxS

Establish what’s actually consuming space before deciding what to do.

Open Terminal (Admin).

Run the analysis:

DISM /Online /Cleanup-Image /AnalyzeComponentStore

The output includes:
- Component Store (WinSxS) folder size: what File Explorer shows (inflated by hard links).
- Actual Size of Component Store: real disk usage.
- Shared with Windows: files shared with active System32 (not removable).
- Backups and Disabled Features: removable through cleanup.
- Cache and Temporary Data: removable.
- Component Store Cleanup Recommended: Yes or No.
If Component Store Cleanup Recommended is Yes, you can reclaim several GB. Proceed to Method 2.
If No, WinSxS is already at minimum size — no action will help. Look elsewhere for disk space (Disk Cleanup, OneDrive, hibernation file).

This baseline tells you whether cleanup is worth running.

Method 2: Shrink WinSxS with StartComponentCleanup

The supported way to reduce WinSxS size in place.

Open Terminal (Admin).
First, perform the standard component cleanup (removes superseded components older than 30 days):
```
DISM /Online /Cleanup-Image /StartComponentCleanup
```
This takes 5-15 minutes. The window shows percentage progress.
For more aggressive cleanup (immediately removes all superseded components — irreversible past this point), run:
```
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
```
Important caveat: After ResetBase, you cannot uninstall any cumulative update installed before this command. Only use it if you’re confident your current Windows install is stable.
Run the analysis again:
```
DISM /Online /Cleanup-Image /AnalyzeComponentStore
```
The reported size should be smaller. Recovery typically 2-8 GB.
Reboot.

This is the only safe way to reduce WinSxS. Result: smaller component store, fully functioning servicing stack.

Method 3: Use Disk Cleanup with system files for additional savings

Pairs well with Method 2 — captures additional categories Disk Cleanup understands but DISM doesn’t.

Press Win + S, type Disk Cleanup. Right-click → Run as administrator.
Choose C:, click OK.
If the dialog opens without “Windows Update Cleanup” in the list, click Clean up system files to elevate.
Tick the categories with the most savings:
- Windows Update Cleanup (5-15 GB if you’ve been on this install for months)
- Previous Windows installation(s) (10-30 GB if Windows.old exists)
- Delivery Optimization Files (1-10 GB)
- Temporary Internet Files
- Recycle Bin
- Thumbnails
Click OK → Delete Files.
The Windows Update Cleanup phase can take 10-30 minutes. Wait it out.
Reboot to commit the cleanup. WinSxS will shrink further as part of the boot finalization.

This combined approach typically frees 15-30 GB on a Windows 11 install that’s been running for 6+ months.

How to verify the fix worked

Run DISM /Online /Cleanup-Image /AnalyzeComponentStore again. Actual Size of Component Store is smaller than before.
Open Settings → System → Storage. C: free space has grown by the expected amount.
Windows Update still works — open Settings → Windows Update and click Check for updates. No errors.
Run sfc /scannow from an elevated Command Prompt. Result: no integrity violations.

If none of these work

If WinSxS is still large after cleanup and you genuinely need more C: space, three options remain. Disable hibernation: powercfg /h off from elevated prompt frees ~RAM-sized space (8-32 GB depending on system). Reduce page file: Settings → System → About → Advanced system settings → Performance → Virtual memory, set Custom Size with smaller initial/max values. Move user folders to another drive: right-click each (Documents, Pictures, Music) → Properties → Location tab → Move. Documents and Pictures can safely live on D:; this gives you many GB without touching system files. As a last resort, upgrade the C: SSD itself — moving from 128 GB to 512 GB SSD is far safer than relocating WinSxS and costs less than the time spent troubleshooting broken updates.

Bottom line: Never move WinSxS — Windows is hardcoded to find it at C:\Windows\WinSxS. Shrink it in place with DISM cleanup, and move user data folders if you need additional C: space.