Windows sometimes refuses to free space even when you run Disk Cleanup — the short answer is that Disk Cleanup doesn’t work when system files are locked, components are corrupted, or conflicting settings and services prevent the tool from running correctly. This article explains the common causes and walks you step-by-step through the fixes so you can get Disk Cleanup working again or use reliable alternatives.
You’ll learn the eight most frequent reasons Disk Cleanup fails on Windows 10 and how to resolve each—with commands, menus, and practical tips for safe cleanup.
Key Takeaway
Most Disk Cleanup failures are resolved by running the tool with elevated privileges, clearing Windows Update locks (or restarting), repairing system files with SFC/DISM, and stopping conflicting services or third-party cleaners; if Disk Cleanup remains unusable, use Settings > System > Storage > Temporary files (Storage Sense) or a clean DISM/SFC restore.
Quick Fix Guide
Quick Fix Guide
| Reason for the Problem | Quick Solution |
|---|---|
| Disk Cleanup not run as administrator | Right-click Disk Cleanup and choose Run as administrator or run cleanmgr.exe /sageset:1 and /sagerun:1 elevated. |
| Pending restart or files in use | Reboot Windows to clear file locks, then retry Disk Cleanup. |
| Windows Update files are locked | Stop update services (wuauserv, bits) and delete C:\Windows\SoftwareDistribution\Download before restarting services. |
| Corrupt system files or component store | Run elevated sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. |
| Disk errors or bad sectors | Run chkdsk C: /f /r from an elevated Command Prompt and reboot to schedule. |
| Storage Sense or third-party cleaners interfering | Temporarily disable Storage Sense and uninstall/disable third-party cleanup utilities. |
| Disk Cleanup options missing (UI changes) | Use Settings > System > Storage > Temporary files or run cleanmgr.exe /sageset options. |
| Corrupt or missing cleanmgr.exe or registry issues | Repair with sfc/DISM, or copy cleanmgr.exe from a working system and re-register if necessary. |
Detailed Fixes for “Disk Cleanup doesn’t work”
1) Not running Disk Cleanup with administrative rights
Why it causes the problem
- Disk Cleanup needs elevated privileges to remove system files (Windows Update cleanup, Service Pack cleanup, etc.). Running it as a standard user won’t show these options or will silently fail.
Step-by-step solution
- Click Start, type Disk Cleanup, and don’t press Enter.
- Right-click Disk Cleanup in the results and select Run as administrator.
- If you need to automate configuration, open an elevated Command Prompt and run:
- cleanmgr.exe /sageset:1 (choose options in the dialog), then
- cleanmgr.exe /sagerun:1 (executes the saved settings).
Notes/tips
- Always run system-level cleanup as admin to see “Clean up system files.”
2) Pending restart or files locked by running processes
Why it causes the problem
- Many temporary or update files are in use until Windows restarts; Disk Cleanup can’t delete locked files.
Step-by-step solution
- Open Start > Settings > Update & Security > Windows Update and check for a pending restart; click Restart now if present.
- After restart, immediately run Disk Cleanup as admin.
- If you suspect specific processes hold files, open Task Manager (Ctrl+Shift+Esc), identify the process, right-click and select End task (use caution).
- For stubborn locks, boot to Safe Mode: Settings > Update & Security > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings > Restart then press the Safe Mode key.
Notes/tips
- Reboots clear most locks; Safe Mode removes many running services so cleanup can proceed.
3) Windows Update files are in use or corrupted
Why it causes the problem
- Update files in C:\Windows\SoftwareDistribution can be locked by update services; Disk Cleanup may hang or skip Windows Update cleanup.
Step-by-step solution
- Open an elevated Command Prompt (right-click Start > Windows PowerShell (Admin)).
- Stop update services:
- net stop wuauserv
- net stop bits
- net stop cryptSvc
- net stop msiserver
- Delete the download cache:
- rd /s /q C:\Windows\SoftwareDistribution\Download
- Restart services:
- net start wuauserv
- net start bits
- net start cryptSvc
- net start msiserver
- Reboot and run Disk Cleanup as admin, then choose Clean up system files.
Notes/tips
- Deleting the SoftwareDistribution download folder does not remove installed updates; it clears cached files used by Windows Update.
4) Corrupt system files (SFC/DISM needed)
Why it causes the problem
- Damaged system files (including cleanmgr components) can stop Disk Cleanup from functioning or cause it to crash.
Step-by-step solution
- Open an elevated Command Prompt.
- Run System File Checker:
- sfc /scannow
- If SFC reports problems it can’t fix, run DISM:
- DISM /Online /Cleanup-Image /RestoreHealth
- After DISM completes, run sfc /scannow again and then reboot.
Notes/tips
- DISM may take 10–30 minutes depending on system speed and connection to Windows Update for repair sources.
5) Component Store (WinSxS) or cleanup tools require DISM
Why it causes the problem
- The Windows component store (WinSxS) can grow or become inconsistent; Disk Cleanup’s Windows Update cleanup requires a healthy component store.
Step-by-step solution
- Open an elevated Command Prompt.
- Analyze component store:
- DISM /Online /Cleanup-Image /AnalyzeComponentStore
- Start component cleanup:
- DISM /Online /Cleanup-Image /StartComponentCleanup
- Optionally force removal of superseded components:
- DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase
- Reboot and test Disk Cleanup with Clean up system files.
Notes/tips
- /ResetBase prevents uninstalling some older updates; use only if you’re sure you don’t need rollback.
6) Disk errors or bad sectors prevent file deletion
Why it causes the problem
- File system corruption prevents deletion or scanning; Disk Cleanup can hang or report errors.
Step-by-step solution
- Open an elevated Command Prompt.
- Schedule a disk check:
- chkdsk C: /f /r
- If prompted to schedule at next restart, type Y and reboot.
- Allow CHKDSK to complete (can take a long time on large or damaged drives).
Notes/tips
- Back up important data before running extensive repairs if you suspect drive failure.
7) Conflicts with Storage Sense or third‑party cleaners
Why it causes the problem
- Storage Sense or third-party utilities (CCleaner, system optimizers) can remove expected temp files or lock folders, leading Disk Cleanup to behave unpredictably.
Step-by-step solution
- Disable Storage Sense temporarily: Settings > System > Storage > Storage Sense and toggle it Off.
- If you have third-party cleaners, open their settings and disable scheduled cleaning; ideally, uninstall them temporarily via Settings > Apps > Apps & features.
- Reboot and run Disk Cleanup as admin.
Notes/tips
- Use one cleanup tool at a time to avoid conflicts and accidental deletion.
8) Disk Cleanup UI options missing or cleanmgr.exe corrupt
Why it causes the problem
- Microsoft has moved some cleanup features to Windows Settings, and cleanmgr.exe might be damaged or missing on some builds.
Step-by-step solution
- Check Windows Settings alternative: Settings > System > Storage > Temporary files and try cleanup from there.
- Repair the executable with sfc /scannow (see above).
- If necessary, copy a working cleanmgr.exe from another Windows 10 machine with the same build:
- Place it in C:\Windows\System32\ and run sfc /scannow to register.
- Use cleanmgr.exe /sageset:65535 & cleanmgr.exe /sagerun:65535 to show all options (as admin).
Notes/tips
- Microsoft may deprecate some options; Storage Settings is the modern replacement.
Additional tools and when to use them
- Use Storage Sense (Settings > System > Storage) for automatic periodic cleanup when Disk Cleanup is unreliable or you want scheduled cleanup.
- For advanced cleanup of Windows Update and component store, prefer DISM and StartComponentCleanup.
- If you prefer a GUI for Windows Update cleanup without Disk Cleanup, use the built-in Update & Security > Windows Update > View update history and the Windows Update Troubleshooter.
- If your drive shows hardware issues, consider cloning data to a new drive before aggressive repairs.
FAQ
Q: Can Disk Cleanup remove the Windows.old folder?
A: Yes — run Disk Cleanup as admin, click Clean up system files, and select Previous Windows installation(s); alternatively delete C:\Windows.old manually only after confirming you don’t need rollback.
Q: Why does Disk Cleanup take hours or freeze?
A: It may be processing many files, encountering file system errors, or waiting on services; check Task Manager, ensure no pending reboot, run chkdsk and SFC/DISM if it consistently hangs.
Q: Is it safe to delete everything Disk Cleanup suggests?
A: Most options are safe, but don’t remove Downloaded Program Files or Device driver packages unless you understand the consequence; keep Windows Update Cleanup only if you won’t need to uninstall recent updates.
Q: How can I automate Disk Cleanup?
A: Use Task Scheduler to run cleanmgr.exe /sagerun:1 as an elevated task on a schedule after configuring /sageset options.
Q: Disk Cleanup still fails after all fixes — what next?
A: Use Settings > System > Storage > Temporary files or consider an in-place upgrade/repair install of Windows 10 (keeps files and apps but re-installs system files).
Conclusion
Most failures occur because Disk Cleanup lacks necessary permissions, system files are locked or corrupted, or other tools/services conflict with it. Following the steps above — running as admin, rebooting, stopping update services, and repairing with SFC/DISM — will resolve the majority of problems. If you still have issues, remember that Disk Cleanup doesn’t work can often be worked around using Storage Sense or an in-place repair of Windows.
