C Drive Full for No Reason? Here Is Where It Went

You select everything in your user folder, right-click, and Properties says 78GB. Windows says the C drive has 450GB used out of 476GB. Nothing you can see accounts for the other 370GB, and deleting more files barely moves the number.

The space is real and it is being used. It is just being used by things Explorer will not show you by default — a hibernation file the size of your RAM, restore points allowed to eat a tenth of the drive, update leftovers, and an app cache folder that has been growing quietly since you bought the machine.

This guide works through the culprits in the order they are usually largest. If you want the broader maintenance routine instead — Storage Sense, Disk Cleanup, uninstalling bloat — that is covered in how to free up disk space on Windows. This one is specifically about finding space that appears to have vanished.

First: see the drive as it actually is

Before changing anything, get a real picture. Two free tools do this far better than Windows’ own Storage screen:

• WizTree — reads the NTFS file table directly. A 1TB drive scans in under ten seconds. Right-click it and choose Run as administrator so it can see protected folders.
• TreeSize Free — slower because it walks folders, but friendlier if you prefer a sorted tree to a treemap.

Scan C: and sort by size. In nearly every case the answer is visible immediately: one enormous file, or one folder you had forgotten about.

Also turn on hidden files in Explorer while you are investigating. View → Show → Hidden items, and in Folder Options → View, untick Hide protected operating system files. Turn that second one back on when you are done.

The seven usual culprits, in order

1. hiberfil.sys

Windows reserves a file equal to roughly 40% of your installed RAM to hold the contents of memory when the machine hibernates. On a 32GB desktop that is about 12.8GB sitting permanently on C.

If you genuinely never hibernate, open Terminal (Admin) and run:

powercfg /hibernate off

The file disappears instantly. Be aware this also disables Fast Startup, which uses the same file — on a laptop that trade is usually not worth it. A middle option is to shrink it rather than remove it:

powercfg /h /size 50

That halves the reserved size while keeping hibernate working. To undo the first command entirely: powercfg /hibernate on.

2. pagefile.sys

This is virtual memory — the overflow space Windows uses when RAM runs short. It is frequently several gigabytes and on a system with memory pressure it can grow much larger.

Do not delete it. You cannot, while Windows is running, and the workarounds people suggest cause out-of-memory crashes rather than speed. You can cap it: Win+R → sysdm.cpl → Advanced → Performance Settings → Advanced → Virtual memory → Change. Set a custom size rather than removing it.

Both files have enough nuance to be worth their own guide — see is hiberfil.sys or pagefile.sys safe to delete for the full detail and the safe numbers.

3. System Restore points

By default, System Protection may consume up to 10% of the drive. On a 1TB SSD that is 100GB of snapshots you have never used.

1. Win+R → sysdm.cpl → System Protection tab.
2. Select your system drive, click Configure.
3. Drag Max Usage down to 3–5%.
4. Click Delete if you need the space back right now.

Before you click Delete: this removes every existing restore point, permanently. You lose the ability to roll back a bad driver or update to an earlier state. Keep protection switched on afterwards — reducing the allocation is sensible, turning the feature off is not.

4. Windows Update leftovers

Three separate things accumulate here.

Windows.old appears after a feature update and is typically 15–25GB. Windows deletes it automatically after 10 days. Removing it early is fine once you are confident the new version works — see can you safely delete Windows.old.

Delivery Optimisation files are the peer-to-peer update cache, often several gigabytes. Clear them in Settings → System → Storage → Temporary files.

WinSxS (the component store) looks enormous in Explorer but much of that figure is hard links counted twice. Never delete from it by hand. Clean it properly from an admin terminal:

DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase

/ResetBase removes superseded components, which means individual updates can no longer be uninstalled afterwards. On a stable machine that is an acceptable trade and it often recovers 3–8GB.

5. The OneDrive cache

This is the single most common surprise on modern machines. If Files On-Demand is off, or if someone right-clicked the folder and chose Always keep on this device, every file in your cloud storage has a full local copy.

Right-click the OneDrive folder in Explorer and choose Free up space. The files stay listed and still open on demand; the local copies go. The full procedure, including moving the folder to a different drive, is in OneDrive filling up your C drive.

6. Temp files

Two locations, and both are safe to clear while nothing is installing:

• %LOCALAPPDATA%\Temp — paste that into the Explorer address bar.
• C:\Windows\Temp

Select all and delete. Windows will refuse to remove a handful of files that are in use; skip those. The cleaner route is Settings → System → Storage → Temporary files, but read are Windows temporary files safe to delete first — Downloads appears on that checklist and it contains your actual files.

7. Application caches in AppData

Open C:\Users\[you]\AppData\Local in your treemap tool. Frequent offenders:

• Browser profiles — Chrome, Edge and Firefox each cache a gigabyte or more.
• Teams, Discord, Slack, Spotify — hundreds of megabytes each, sometimes far more after a long run without restarting.
• Packages — Microsoft Store app data, including Xbox game saves.
• Old iPhone backups — AppData\Roaming\Apple Computer\MobileSync\Backup, routinely 20GB+ per device.
• Docker and WSL virtual disks — a .vhdx grows and never shrinks on its own.

Clear browser caches from inside each browser rather than deleting folders. For everything else, uninstalling and reinstalling the app is safer than deleting its AppData folder blind.

What not to do

• Do not delete hiberfil.sys, pagefile.sys or swapfile.sys by hand. Use powercfg and the Virtual Memory dialog. Booting from another OS to delete them is a recipe for an unbootable machine.
• Do not delete C:\Windows\Installer. It looks like leftover setup files and is not — removing it breaks repair and uninstall for every program that used it.
• Do not run registry cleaners or “PC optimiser” suites. They do not free meaningful space, they add a background process, and the free versions frequently bundle something worse.
• Do not disable Windows Defender to stop it scanning. It is not what filled your drive, and the protection is worth more than the handful of megabytes its definitions occupy.
• Do not empty C:\Windows\System32 folders on the advice of a forum post. Nothing in there is safe to remove manually.

If the space comes back within weeks

Something specific is growing. Run your treemap tool, note the top ten folders with their sizes, wait a week, and run it again. The folder that changed is your answer — usually a log directory, a sync client, or a game that re-downloads rather than patches.

Once the drive is clean, cap what can grow: restore points at 3–5%, Storage Sense on a weekly schedule, and OneDrive on Files On-Demand. Those three settings stop most machines from ever getting back into this state.

If the drive is healthy on space but the machine still feels slow, the cause is elsewhere — start with why is Windows 11 so slow.