18 Places Windows Hides Junk You Never Check

The system layer, where the real gigabytes sit

Eight of the eighteen live outside your user profile, and they are the heavy ones. Windows.old and its setup sibling $Windows.~BT hold the entire previous installation after an upgrade — often 20–30 GB — and are safe to remove once a rollback is off the table. SoftwareDistribution\Download keeps update payloads that were supposed to clean themselves up, and the Delivery Optimization cache holds pieces you long ago seeded to other PCs. WinSxS carries component-store backups that only DISM /StartComponentCleanup should ever touch.

The quieter pair: C:\Windows\Logs\CBS accumulates cbspersist log bundles on any machine with update troubles, and minidumps plus MEMORY.DMP record every bluescreen you have had. The eighth is $Recycle.Bin — hidden folders at the root of every drive you own, external ones included, holding files you long since considered deleted. None of these show up in a folder-size sweep while hidden and system files stay invisible.

The per-user caches nobody opens

Another six live under your user profile, and not one of them shows up in the folders you normally browse. Individually they are small — hundreds of megabytes, not gigabytes — but on a 128 GB laptop they add up to real room. The list below is the tour of the corners where apps quietly park their garbage.

• %TEMP% (C:\Users\...\AppData\Local\Temp): installer scaffolding that failed apps abandon in place — safe to empty after a reboot
• C:\Windows\Temp: the system-side twin, often holding old .cab and .log files from update runs
• C:\ProgramData\Microsoft\Windows\WER: Windows Error Reporting archives — crash descriptions and dump copies, gigabytes on unlucky machines
• AppData\Local\Microsoft\Windows\Explorer: the thumbcache and iconcache databases — Windows rebuilds them after you delete them
• AppData\Local\D3DSCache: the DirectX shader cache — games and browsers recreate it; clearing it fixes corruption
• AppData\Local\Microsoft\Windows\INetCache: the legacy web cache some system components still write to

The last four — and what to do with all of it

The final four are the places you walk past daily. Browser caches live in AppData\Local\Microsoft\Edge and \Google\Chrome, and the cleanest way to empty them is from inside the browser itself. %LocalAppData%\CrashDumps keeps a complete memory image of every crashed app — a single stuck game can leave a 4 GB file there. The Downloads folder is not technically junk, but it is where installers go to die, and sorting it by size once a quarter beats any cleaner. The eighteenth is hiberfil.sys — not junk, but an honest space eater sized after a chunk of your RAM, gone the moment you disable hibernation you never use.

As for the doing: Storage settings and Disk Cleanup handle Windows.old, WER reports, dumps and the Delivery Optimization cache in one pass, and that is genuinely most of the list. A cleaner such as Kleaner PRO earns its keep by showing these same categories across all drives at once, so nothing hides behind a second partition. Twice a year is a sane rhythm — monthly cache purging buys nothing and breaks nothing, which makes it theater, not maintenance.

Questions and Answers

Read next