Windows storage full? What you can safely delete — in the right order

The symptom: the C: drive is full or nearly full, Windows is complaining, and every guide you find offers the same recycled list of folders to delete. The order here is the difference between reclaiming gigabytes and breaking an uninstall you'll need in six months. Rule zero: map before deleting — Settings > System > Storage shows what is actually eating the drive, categorised, before you touch anything.

Step 1: the safe, supported cleanups (do these first)

Temporary files, the supported way. Settings > System > Storage > Temporary files lists what Windows itself considers removable — update leftovers, delivery-optimisation files, thumbnails, error logs. Review the checkboxes (Downloads can appear here; it can hold personal files — untick it unless you mean it) and let the system do the deleting. The classical route, Disk Cleanup with Clean up system files, reaches the same places and adds Windows Update Cleanup and Previous Windows installation(s) — the supported way to remove the old version after an upgrade.

Windows.old, with its caveat. After a feature update, the previous installation sits in C:\Windows.old for a rollback window. Deleting it through the tools above is safe once you're sure the new version works and you've pulled any personal files out of it — but it also means you cannot go back. That's a decision, not a default.

Storage Sense for the future. Settings > System > Storage > Storage Sense automates the temp-file and Recycle Bin housekeeping on a schedule. It manages the system drive; check its settings once so its Downloads handling matches how you actually use that folder. This is prevention, not rescue — the phone-side version of the same discipline works identically.

Step 2: the space no cleanup tool reaches (still supported)

The hibernation file. hiberfil.sys is roughly the size of your RAM and lives at the drive root, hidden. If you never hibernate, an administrator Command Prompt removes it: powercfg.exe /hibernate off. Know the trade: this also disables Fast Startup's hibernation dependency, so boot times can lengthen slightly. Reversible with /hibernate on.

The component store. C:\Windows\WinSxS grows with every update and must never be deleted manually — it is the store Windows uses to service, repair and uninstall itself. The supported cleanup is an administrator Command Prompt: Dism.exe /online /Cleanup-Image /StartComponentCleanup. Run /AnalyzeComponentStore first if you want to see whether cleanup is even worthwhile. The deeper /ResetBase variant reclaims more but removes the ability to uninstall superseded updates — another decision, not a default.

System restore points. Shadow copies can hold many gigabytes. Reducing them is supported (System Properties > System Protection > Configure) but every point you remove is a rollback option you no longer have — the thing you want when an update misbehaves.

Step 3: the honest look at your own files

The Storage map's biggest category is often just you: Downloads never emptied, video projects, old installers, game libraries. A full user drive isn't a Windows problem — moving large personal files to another drive (or verified cloud storage) beats re-cleaning caches every month. Verify the copy before deleting the original; backup and sync are not the same thing, and cloud sync is not a backup of files you then delete.

App caches. Browser caches and GPU shader caches (NVIDIA's DXCache and friends) are safe to clear — they rebuild. The supported route for apps is the app's own settings; for everything else, uninstall programs you don't use through Settings > Apps, which is what keeps their services and registry entries from being orphaned.

The never-touch list (no matter what a forum says)

C:\Windows\WinSxS (DISM only, above). pagefile.sys — virtual memory; resize it through Advanced system settings if you must, never delete it. C:\Windows\System32 — it is Windows. C:\Windows\Installer — cached installers that repairs, updates and uninstalls need; deleting them trades space today for broken uninstalls later. And Program Files folders — uninstall properly so the leftovers come with them. If a "cleanup utility" offers to touch any of these, close it: the built-in tools plus DISM already cover every category that is safe to cover.

When cleanup isn't enough — the real diagnosis

If the drive fills again within days of a thorough cleanup, something is actively growing. Three usual suspects: update retry loops (check update failure diagnosis — failed updates re-download), a runaway log or cache from one app (the Storage map's per-app view shows the culprit), or WSL/docker virtual disks, which grow to their configured maximum and live as single huge files. Full-drive symptoms can also masquerade as slowness — the slow-computer diagnostic overlaps here, because Windows behaves badly under roughly 10% free space on the system drive.

When to stop and get help

Stop and take a backup image before going further if: the drive filled suddenly overnight (possible malfunctioning software — or ransomware's pre-encryption behaviour, which is a security incident, not a cleaning task), files you didn't delete are missing, or the Storage map's numbers don't come close to the used space (a sign of a filesystem problem a cleanup cannot fix). At that point the tool you need is a backup, then a professional — not a bigger delete key. General guidance, not a diagnosis of your specific machine.

Official documentation (checked 15 September 2026): Microsoft Learn — "Storage Sense" and "Free up drive space" (support.microsoft.com), "Clean up the WinSxS folder" and "DISM component cleanup" (learn.microsoft.com), "PowerCfg command-line options" for hibernation.