The map of cleanable zones: how much, from where
User TEMP (%LOCALAPPDATA%\Temp) is the safest and most underrated zone: installers, unpacked archives, browser and Office temp files pile up here for years, and a work machine typically yields 2–15 GB. Files older than a day are always safe: anything a program actively uses is held open with a handle — a proper cleaner asks the system first (via the Restart Manager) instead of blindly pressing Delete.
Browser caches are the second-biggest zone. Chrome and Edge hold 1–3 GB per profile, and machines often have several: Default, Profile 1, work, kids. A classic old-cleaner mistake was cleaning only Default and leaving the rest — freeing 800 MB out of an available 4 GB. Windows 11 also has Delivery Optimization — the update-delivery cache Microsoft itself lets you clear — which holds 3–8 GB on long-lived systems.
Prefetch is the controversial zone: the files are small (50–150 MB) and clearing prefetch is a persistent speed myth. Windows builds its application launch plan over 2–3 days; deleting fresh entries makes the next launches slower. Only entries older than a week are worth removing. Crash reports (WER) and CBS logs hold another 1–5 GB and are safe to clear if you leave the last day of entries — the current session's crashes may still be needed by diagnostics.
- %LOCALAPPDATA%\Temp — 2–15 GB, safe (files older than a day)
- Browser caches × all profiles — 1–8 GB, safe with browsers closed or in-use checking
- SoftwareDistribution\DeliveryOptimization — 3–8 GB, via stopping the DoSvc service
- Windows\Logs\CBS and WER archive older than 30 days — 1–5 GB, safe
- thumbcache_*.db — Explorer thumbnails, up to 1 GB, rebuilt automatically
- Prefetch: only files older than 7 days — 50–150 MB
What you must never delete
C:\Windows\Installer — the MSI package cache, the single most dangerous folder to clean by hand. It looks like “unused .msi and .msp files”; in reality it is the database that lets you uninstall and repair half of your installed software. Wipe it and “Add/Remove Programs” starts throwing errors for Office, drivers and dozens of utilities. The only safe reduction is the orphan-detection approach, used carefully.
WinSxS — the component store. It takes 5–10 GB and looks like the perfect victim, but it is the backbone of Windows Update; deleting it manually breaks every future update. The only supported way to shrink WinSxS is DISM /Online /Cleanup-Image /StartComponentCleanup — the same thing Microsoft wired into Disk Cleanup as “Windows Update Cleanup”. And pagefile.sys / hiberfil.sys are regularly “discovered” by zealous optimizers too: the first is recreated by the system, the second is disabled properly via powercfg /h off — deleting them by hand from another OS is pointless and harmful.
A separate category: files that are “in use” but the cleaner never checks. Unfinished downloads (.crdownload in Chrome, .part in Firefox), Office lock files (~$document.docx), a Steam cache mid-download — deleting these breaks programs that are alive right now. A good cleaner keeps a whitelist of such patterns and never touches them, whatever the “found X GB” counter promises.
Cleanup order: safe first, aggressive last
Start with the safe set: temp, browser caches, thumbnails, recycle bin — that is 70% of the effect at zero risk. Close browsers first: their caches are locked, and a cleaner will either skip the files or fight over locked handles. Then — error reports and old logs; only in the third pass — system update caches, which require stopping the wuauserv and DoSvc services and starting them back.
The confirmation rule: anything that touches system services or rebuilds long-rebuilding caches (the search index, the icon cache) must come with a warning and a cancel button. Icon-cache cleanup restarts Explorer; search-index rebuilds take up to an hour — the user deserves to know this BEFORE the click, not from a frozen progress bar.
Automation: manual cleanup is needed 2–3 times; after that, schedule it. A weekly overnight run of a safe preset makes “why is my disk red again” disappear on its own. Kleaner PRO presets work exactly this way: Safe is what you can hand to the scheduler unattended; Aggressive/Nuclear stay manual with a restore point.
Questions and Answers
How much space does a Windows 11 cleanup free?
Depends on the system's age: a fresh install yields 0.5–2 GB, a year of active use 5–15 GB, and a machine that survived several major Windows feature updates can give up to 25–30 GB (mostly Delivery Optimization and old CBS logs).
Is clearing Prefetch safe for speed?
No. Windows builds its prefetch launch plan over 2–3 days; deleting fresh entries makes subsequent app launches slower. Only entries older than a week are worth removing — the speed effect is near zero either way.
Disk Cleanup or a third-party optimizer?
The built-in tool covers a limited set and ignores browser caches in all profiles, Steam, and shader caches. A third-party cleaner earns its place through coverage — pick one that checks file in-use state and whitelists important patterns (unfinished downloads, Office lock files).
Why is the first browser launch slow after cleanup?
The browser cache holds saved copies of site images and scripts. After cleanup the browser re-downloads them on the first visit — expected and harmless; the second visit is back to full speed.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]