Your C: drive is nearly full โ but is it worth an hour of cleanup, and what should you target first? Tick what applies and get a rough GB you can reclaim, biggest win first, each with the exact command to run. No download, no scan.
If space vanishes again days after a cleanup, something is generating it โ runaway logs, a sync client, System Restore, or shadow copies. Post what's eating your disk on the Forum-Windows community and folks who've tracked down the same runaway folder will help you find it.
These are estimates from typical sizes, not a scan of your disk โ the point is to tell you whether a cleanup is worth your time and what to target first, before you install any analyzer. The real figure comes from Disk Cleanup or Storage settings on your own machine. Here's what each item actually is:
Your entire previous Windows installation, kept so you can roll back after a feature update or version upgrade. It's usually the single biggest win. Windows auto-deletes it after 10 days, but you can remove it now via Storage settings โ just note you lose the ability to roll back.
The file Windows writes RAM into for Hibernate and Fast Startup. On a 16 GB PC that's several GB. Turning hibernation off with powercfg /h off removes it entirely โ the trade-off is you lose Hibernate and Fast Startup.
The component store keeps older versions of updated system files so updates can be uninstalled. After a few feature updates the superseded copies add up. This is the cause behind those cryptic folders and the "why is WinSxS so big" question โ the component store explained here. Reclaim it with a DISM component cleanup; you can't safely delete it by hand.
Temporary files, leftover Windows Update packages, and the Delivery Optimization cache (update files kept for peer sharing) grow steadily between cleanups. Disk Cleanup (cleanmgr) and Storage settings clear all three.
It depends entirely on your machine, but the common big wins are a leftover Windows.old folder (10โ25 GB), hiberfil.sys (roughly 0.2โ0.4ร your RAM), the WinSxS component store (2โ7 GB after feature updates), and accumulated temp and update-cache files (a few GB up to 20+ if you've never cleaned). This estimator adds up the ones you tick so you can see whether it's worth doing.
Yes โ it only holds your previous Windows version for rollback, and Windows deletes it automatically after 10 days anyway. Remove it through Settings > System > Storage > Cleanup recommendations (or Disk Cleanup > "Previous Windows installation(s)"), not by dragging the folder to the Recycle Bin, which won't work. The only cost is you can no longer roll back to the old version.
No โ deleting WinSxS by hand will break Windows, because it holds hard links to live system files, not just old junk. The safe way to shrink it is Dism /Online /Cleanup-Image /StartComponentCleanup from an elevated prompt, which removes only the superseded components. Run Dism /Online /Cleanup-Image /AnalyzeComponentStore first to see how much is actually reclaimable.
Only if you don't use Hibernate or Fast Startup. powercfg /h off (in an admin Command Prompt) deletes hiberfil.sys and frees space equal to a good chunk of your RAM, but it also disables Fast Startup, which slightly slows cold boots on some PCs. If you want Hibernate back, run powercfg /h on.
Open Settings > System > Storage and use the Cleanup recommendations โ it surfaces Windows.old, temp files, the Recycle Bin and the Delivery Optimization cache in one place and only removes safe-to-delete items. For the component store and hibernation file you'll need the DISM and powercfg commands above. Avoid third-party "PC cleaners" that promise dramatic gains; the built-in tools reclaim the same space without the bloat.