C Drive Fills Up Again a Week After Cleanup Find What Keeps Growing

The most common culprits are caches that were never given a ceiling:

1. Browsers — cache and site data can reach many gigabytes; clear from inside the browser's own settings, and it will regrow more politely
2. Chat and meeting apps — downloaded files, media caches and update packages pile inside their AppData folders
3. Music and video apps — 'downloads for offline' quietly enabled is a library, not a cache; check the in-app download list
4. Cloud sync apps — a sync folder on C holding 'online-only' files that something keeps pulling down will refill exactly as fast as you empty it; the fix is in the sync app's settings

The second family writes on a timetable, which is why the drive falls even on days you add nothing:

1. A backup program imaging to C — a nightly image saved onto the same drive it backs up grows by an image a day and protects nothing; point its destination at another drive or external disk
2. Windows logs run wild — the CBS log folder under C:\Windows\Logs swelling means updates are failing and retry-logging; fix the failing update, and the log calms down
3. Crash dumps — a machine that blue-screens writes a dump each time; MEMORY.DMP and minidumps adding up are a symptom of the crashes, so chase those, not the dumps
4. Restore points multiplying — check the System Protection allocation; an over-generous quota on a small drive is a slow leak by design

Two current space-eaters deserve a named check on developer and power-user machines:

1. WSL and Docker virtual disks — the Linux filesystem lives in an ext4.vhdx file that expands as you use it and does not shrink when you delete files inside Linux; a distribution you experimented with once can hold tens of gigabytes hostage
2. Virtual machines — a VM's disk file grows toward its maximum as the guest writes; snapshots multiply it further
3. For both, the honest fixes are inside the tool: remove the unused distribution or VM properly, or compact the virtual disk with the tool's own commands — deleting the .vhdx from Explorer destroys the environment outright

One special case stands apart: if a single file has ballooned by tens or hundreds of gigabytes right after a Windows update, that matches a specific known update-bug pattern — a separate guide in this series covers exactly that case, and it is a fix-the-bug job, not a cleanup job.

Close the case properly so it stays closed:

1. Apply the fix at the source — cap the cache, move the backup destination, repair the failing update, remove the dead VM
2. Reclaim the accumulated output once, using the safe cleanup from the core guide
3. Turn on Storage Sense and, if your Windows edition offers it, the low-space notification — and glance at the drive bar weekly for a month
4. If the diary stays flat, the grower is dead; a flat month is the proof, not a hopeful feeling