Windows 11 Is Full and It's Not Your Apps: Where the Space Actually Went

You uninstalled three games, moved your photo library to an external drive, and cleared the Downloads folder. The drive is still red.

I have been through this on four machines now, and the conclusion is always the same: the space is not in your apps. It is in four places Windows never shows you in a normal file listing, and one of them is almost certainly the biggest.

This is how to find out which one, without deleting anything you will miss.

First: stop deleting things

The instinct when the bar turns red is to start removing files. That is the wrong order. You cannot fix a space problem you have not measured, and "delete stuff until the bar goes green" is how people lose the only copy of a document.

Spend ten minutes measuring first. Everything after that is a decision, not a guess.

Step 1: Read the storage breakdown

Settings → System → Storage gives you a bar chart of what Windows thinks is using space: Apps, Documents, Pictures, Temporary files, and so on.

It is useful for one thing: telling you which category to investigate. It is useless for finding the actual files, because each category is an aggregate. "Temporary files" on my machine was 34 GB and the breakdown inside it did not name a single folder.

Note the top two categories. Those are where you look next.

Step 2: Get a real view of the disk

You need a tool that shows folder sizes as a tree, so you can see that C:\Users\you\AppData\Local is 40 GB while C:\Program Files is 8 GB.

Anything that draws a treemap works. The point is to sort by size and look at the top ten folders, not to browse randomly.

Two things to know before you start:

"Size" and "Size on disk" are different numbers. A folder can report 40 GB of files and occupy 6 GB of disk, because of compression, sparse files, and hard links. If you are deciding what to delete, look at "size on disk", not "size".

Some folders will show absurd numbers and mean nothing. C:\Windows\WinSxS is the classic case. It reports 10-15 GB. Most of that is hard links pointing at files that also exist in System32 — deleting the "duplicate" frees nothing, and Windows will refuse anyway.

The four things that are actually eating your disk

1. The hibernation file

If you have ever put the laptop to sleep, Windows wrote a file at C:\hiberfil.sys roughly the size of your installed RAM. On a 32 GB machine that is a 13 GB file that appears in no folder listing, because it sits at the drive root and Explorer hides protected system files by default.

You can see it: File Explorer → View → Show → Hidden items, then look at C:\.

If you do not use hibernation (distinct from sleep — hibernation writes RAM to disk and powers off), you can reclaim all of it with powercfg /hibernate off:

powercfg /hibernate off

That also disables Fast Startup, which is a fair trade on most desktops and a real loss on some laptops. Know which you are choosing.

2. System Restore points

System Protection keeps snapshots of your system drive so you can roll back a bad driver or update. By default it can consume up to 10% of the drive, and on a 1 TB disk that is 100 GB of snapshots you never see.

Check it: System Properties → System Protection → Configure. The slider shows current usage.

Deleting all restore points is a bad idea if you have just installed something risky. Deleting the oldest ones and lowering the cap to 3-5% is usually the right move.

3. The component store

C:\Windows\WinSxS is where Windows keeps every version of every system component it might need to roll back. It is also the folder most often blamed for space loss, and most often blamed incorrectly.

The reason: it is built almost entirely on hard links. A file in WinSxS and the same file in System32 are two names for one chunk of data on disk. The folder's reported size counts both names. The actual disk usage counts it once.

Microsoft's own DISM component store tool reports the real number:

Dism /Online /Cleanup-Image /AnalyzeComponentStore

Run that before you believe any "WinSxS is 15 GB" claim. On this machine it reported 6.2 GB actual, 11.4 GB apparent.

If it does report reclaimable packages, Dism /Online /Cleanup-Image /StartComponentCleanup removes superseded ones safely. Do not delete the folder.

4. Duplicate files

This is the one nobody measures, and on a machine that has been through a phone upgrade, a laptop replacement, or a few years of "save a copy just in case", it is routinely the largest recoverable chunk.

The pattern is predictable:

  • Phone backups imported twice. You plug the phone in, import 4,000 photos, then do it again three months later because you are not sure the first import worked. Now you have 8,000 files, half of them identical.
  • The Downloads folder. report.docx, report (1).docx, report-final.docx, report-final-v2.docx. Two of those four are byte-identical.
  • The same file in three places. A photo exists in Pictures, in the OneDrive folder that syncs Pictures, and in the phone backup you keep on D:. Three copies, one photo.
  • A whole-drive copy during a machine migration. You copy D:\Work to the new laptop, then keep the old drive as a backup, then copy it back to the new machine "to be safe".

None of these are mistakes. They are what normal use looks like. The problem is that Windows has no way to show you the overlap.

How to clean duplicates without losing anything

Windows 11 does not include a duplicate finder. Storage Sense clears temp files, previous installations, and the Recycle Bin on a schedule — it has no concept of two files having the same content.

So you need a tool, and here is where most people get hurt. Search for "duplicate file cleaner" and you get a wall of apps that scan your drive, pre-select every duplicate, and offer a "Clean 50 GB" button. That pre-selection is the problem. Some of those files are not duplicates in any meaningful sense, and a few of them will break something if removed.

A safe cleanup has four rules.

Rule 1: scan folders, not the whole drive. Start with Downloads, Pictures, Desktop, and any backup drive. Scanning C:\ pulls in WinSxS, Program Files, and every application cache, and produces thousands of "duplicates" that are supposed to be there.

Rule 2: never trust automatic selection. Open each group and look at the paths. The copy in Pictures\2024\ is usually the original. The copy in Downloads\ is usually the one to remove. Any tool that decides this for you is guessing.

Rule 3: check what references the file. A photo referenced by a Lightroom catalog, or an attachment embedded in a project file, breaks when you delete it — even though an identical copy exists elsewhere. If you are not sure, skip the group.

Rule 4: delete to the Recycle Bin. Not permanently. A week of normal use is the safety margin, and it costs you nothing but disk space you were going to reclaim anyway.

If a group is ambiguous, leave it alone. There is no prize for finishing in one pass.

A real number

On my own machine — a laptop that has been through two phone upgrades and one replacement — a scan of Downloads, Pictures, and the old backup drive found 11.4 GB of exact duplicates.

The breakdown was boring: 6.8 GB of photos imported twice from the same phone, 3.1 GB of installers downloaded more than once, 1.5 GB of documents with (1) and -final suffixes.

Nothing in that 11.4 GB was a system file. Nothing was referenced by another application. It was just the same data, stored more than once, because nobody had ever shown me the overlap.

That is the part Windows does not do.

What not to do

A short list, because these are the mistakes that turn a space problem into a data loss problem:

  • Do not delete WinSxS. It is protected for a reason. Use DISM.
  • Do not delete System Volume Information. That is your restore points. Manage them through the UI.
  • Do not use "permanently delete" on a first pass. Recycle Bin exists for exactly this.
  • Do not run a cleaner on C:\ as your first scan. You will get a result you cannot interpret.
  • Do not empty the Recycle Bin the same day. Wait a week.
  • Do not believe a recoverable-space number computed from file size. Hard links and compression make that number fiction. It has to come from allocated size and link count.

The short version

Measure before you delete. Check the hibernation file, the restore point allocation, and the real component store size with DISM. Then look for duplicate content in the folders where it actually accumulates — Downloads, Pictures, and any backup drive.

Keep the copy in the folder you would look in first. Send the rest to the Recycle Bin. Empty it a week later.

That is the whole process, and it does not require deleting anything you will miss.

I wrote the duplicate scanner I use for this — FileDedupe. It is free, it reports allocated size rather than logical size, it detects hard links so it does not inflate the number, and it deletes to the Recycle Bin by default. The manual process above works without it if you would rather do it by hand.

Comments

Popular posts from this blog

Why plugins corrupt your .xlsx files (and how to check before it happens)

Why Task Manager Says 95% Memory When Nothing Is Running