The most expensive cleanup mistakes all start the same way — a big unfamiliar folder, a forum tip, a delete key. These are the folders Windows protects for good reason, and the safe door for each.
Every technician has a reinstall story that begins with someone "freeing space" inside a system folder. The tragedy is that the space was never worth it: the protected folders are either smaller than Explorer claims, or their bill arrives months later as failed updates and un-uninstallable programs. Learn the list once, and you never pay that bill.
C:\Windows\WinSxS holds every version of every system component, so updates can be applied and rolled back safely. Explorer also exaggerates its size, because many files in it are hard links to files counted elsewhere — the folder is smaller than it looks, and deleting from it by hand corrupts the store.
Windows has its own supported way to slim this store (a DISM cleanup), and that route belongs to the update-cleanup topic — the only takeaway needed here is the one line: never delete WinSxS contents by hand, ever.
C:\Windows\Installer stores the installer packages for the programs on your PC. Windows returns to these files when you repair, modify, patch or uninstall those programs.
It should not need saying, yet cleanup forums keep asking: C:\Windows\System32 is the operating system, C:\Program Files is your installed software, and C:\ProgramData holds shared program data you cannot judge by size alone. The supported door for removing a program is Settings → Apps → Uninstall — always. Deleting a program's folder by hand leaves its services, drivers and registry entries behind like a demolished house with the plumbing still connected.
Two files sit on C: looking like deletable bloat. They are not deletable — they are configurable, which is different:
pagefile.sys is virtual memory. Forcing it tiny or off to "save space" produces out-of-memory crashes in exactly the heavy apps that needed it. On modern Windows, leave it system-managedhiberfil.sys is the hibernation file, and it has one legitimate exit: powercfg /hibernate off, accepting the loss of Hibernate and Fast Startup — a knowing trade covered in this series' emergency cleanup guide, never a hand deletionEvery protected folder on this page shares one property: Windows provides a door for it, or it is not meant to be emptied. Programs leave through Settings. Updates leave through the update cleanup. Hibernation leaves through powercfg. Temp files leave through the cleanup routine.
If a "cleanup trick" starts with taking ownership of a system folder and deleting what Windows protects, the trick is not clever — it is the first scene of a reinstall story. Close the tab and use the door.
See every cleanup location opened live on a real PC, in the same safe order, step by step.
▶️ Watch Full VideoUsually not. Many WinSxS files are hard links — the same data counted again in other folders — so Explorer overstates it. Windows reports the true size through its own component store analysis, and the supported DISM route is the only way it should ever be slimmed.
Possibly nothing today. The failures appear when an affected program is repaired, patched or uninstalled, because Windows looks for its cached installer. The honest recovery is reinstalling the program to rebuild its cache — prevention is far cheaper than the cure.
Old profiles of deleted accounts can be removed through Settings (Accounts, then the profile cleanup in advanced system settings), not by deleting folders. AppData wholesale is never safe — it mixes junk with live settings. Clean specific known locations only, the way this series' temp map describes.