Disk Cleanup Removes Everything It Lists — and Misses the Real Junk

What cleanmgr actually covers

Disk Cleanup works through a fixed catalog of volume caches: Recycle Bin, temporary files, thumbnails, Delivery Optimization files, Windows Update Cleanup — a set that has barely changed since Windows 7. You tick a box, the category gets deleted, and the sizes are honest: the numbers are estimates, not inventions. The problem isn't deception; it's coverage. The dialog was designed for an era when Windows itself produced most of the junk on a disk, and that era is long over.

Today drive C: fills up with things cleanmgr has never heard of: application caches, unpacked driver installers, leftovers from development tools. Microsoft knows it — that's why Storage Sense and the Temporary files panel in Settings get pushed forward — but that panel inherits the same fixed catalog. None of these tools will show you a 20 GB folder sleeping quietly in ProgramData.

The leftovers no checkbox will ever show

The heaviest junk on a real-world system lives outside the catalog. Some of it is left behind by Windows servicing, but most of it comes from applications that treat your disk as their personal warehouse. None of these items will ever appear in a cleanup dialog.

• C:WindowsInstaller — the hidden MSI cache, which easily passes 10–20 GB on upgrade-heavy systems and can't be cleaned by hand without breaking uninstalls
• C:ProgramDataPackage Cache — installer payloads from Visual Studio, runtimes and frameworks, kept around for repair scenarios
• Browser caches — Chrome and Edge each hold 1–5 GB in %LOCALAPPDATA%, and Disk Cleanup never touches them
• GPU driver leftovers — NVIDIA and AMD extract installers under ProgramData and C:AMD, and those folders survive every driver update
• App caches — Spotify, Teams and Electron apps quietly grow gigabytes under %APPDATA% and %LOCALAPPDATA%
• Crash dumps — C:WindowsMEMORY.DMP and C:WindowsMinidump, which only appear after the crash that created them

How to reclaim what the checkbox era ignores

Start with a space scanner such as WizTree or TreeSize Free and look at the top of the list: on a typical two-year-old system you'll meet at least three of the categories above before you reach anything cleanmgr manages. Windows Installer and Package Cache need dedicated tools or a careful hand, browser caches are safe to clear from the browsers themselves, and driver leftovers can go once the current driver works. In our own support tickets, a single pass over these unlisted categories frees more than a year of Disk Cleanup runs — exactly the gap Kleaner PRO closes, because it targets the caches cleanmgr ignores instead of replaying its catalog.

Questions and Answers

Read next