Skip to content

Your C drive is full and Explorer shows nothing big. Where it went

Windows hides most of what fills a drive. The seven places to look, in the order that finds the space fastest, with what each one is safe to remove.

7 min read

You have added up Documents, Downloads, Desktop and Pictures and it comes to a few gigabytes. Windows says the C drive is nearly full. Nothing you can see accounts for the difference, and running Disk Cleanup finds a few hundred megabytes.

This has a short list of causes, and Explorer hides every one of them.

The seven, in the order worth checking

WhereTypical sizeSafe to clear
Hibernation file C:\hiberfil.sys40 to 100 percent of your RAMYes, by turning hibernation off
System Restore and shadow copies5 to 20 GBYes, and you lose restore points
C:\Windows.old20 to 40 GB, for 10 daysYes, through Settings
Windows Update caches1 to 10 GBYes
The component store WinSxSAround 6 GB actualOnly with DISM
C:\Windows\Installer1 to 6 GBNo. Uninstalling breaks
Per user AppData1 to 50 GBSelectively

See the whole drive first

# PowerShell, in the folder you want to look at
Get-ChildItem C:\ -Force -Directory |
  ForEach-Object {
    $s = (Get-ChildItem $_.FullName -Recurse -Force -File -ErrorAction SilentlyContinue |
          Measure-Object Length -Sum).Sum
    [PSCustomObject]@{ GB = [math]::Round($s/1GB,2); Folder = $_.FullName }
  } | Sort-Object GB -Descending | Select-Object -First 15

That is slow, because it walks everything, and it is honest, which Disk Cleanup is not: Disk Cleanup only reports categories it knows how to remove, so a 30 GB folder it has no opinion about is simply absent from its list.

The two that surprise people most

The hibernation file is sized against your installed memory, so a machine with 32 GB of RAM can be holding 12 to 25 GB for it, and it exists even if you never hibernate. What hiberfil.sys is and how to remove it covers the trade.

System Restore reserves a percentage of the drive by default and fills it with shadow copies. It is genuinely useful and it is also invisible: nothing in Explorer shows it, and the setting that caps it is buried in a legacy dialog.

What Windows shows you, and what it leaves out

Settings, System, Storage is the built in view and it is worth opening first: it finds temporary files, the Recycle Bin and large unused apps quickly. What it will not do is show you a folder tree, which means anything that does not fit one of its categories lands in a bucket with no way in, exactly like System Data on a Mac.

The order that gets the most space soonest

  1. Empty the Recycle Bin, on every drive rather than just C.
  2. Settings, System, Storage, Temporary files. Tick everything except Downloads unless you have looked at it.
  3. Remove Windows.old through Settings if it is still there.
  4. Turn hibernation off if you never use it.
  5. Cap System Restore rather than disabling it.
  6. Run the component store cleanup with DISM.
  7. Then, and only then, start looking at your own files.

Common questions

Why is my C drive full when I have no files?

Because Windows hides most of what fills a drive: the hibernation file, System Restore shadow copies, Windows.old after an upgrade, update caches and the component store. None of them appear in Explorer as ordinary files.

Why does Disk Cleanup find so little?

Because it only reports categories it knows how to remove. A large folder it has no rule for is simply absent from the list, which is why it can report a few hundred megabytes on a drive with 40 GB of reclaimable space.

What is the fastest thing to free on Windows?

The hibernation file if you never hibernate, since it is sized against your RAM and removing it is one command. After that, Windows.old if you have upgraded recently, and System Restore if it has been left uncapped.

Is it safe to delete C:\Windows folders to free space?

Only through the tools that own them: Settings for Windows.old and temporary files, DISM for the component store, powercfg for hibernation. Deleting inside C:\Windows by hand is how a machine stops updating or booting.

Read next