C Drive Fills Up Again Every Few Weeks After Cleaning

A drive you cleared last month that is full again has a different problem from a drive that filled up gradually over three years. The second is accumulation. The first is a process writing continuously, and deleting the output again just resets the clock.

So the job is not to find files to delete. It is to find the folder that is growing, which takes about ten minutes and ends the cycle rather than extending it.

Find what grows, not what is large

Windows’ own Storage settings show categories, not folders, and categories hide the answer. Use a tool that maps actual directory sizes:

• WizTree reads the NTFS master file table directly and scans a full drive in seconds.
• TreeSize Free is slower but presents the tree more clearly.

Both are free and neither needs to stay installed. Run one, sort by size, and expand the largest folders down three or four levels until you reach something you recognise.

Then do the thing that actually identifies a recurring cause: note the top ten folders and their sizes, and check the same list a week later. The folder that gained several gigabytes is your answer. Everything else is noise.

The usual culprits, in order

OneDrive is the most common answer

OneDrive’s Files On-Demand keeps files in the cloud and downloads them when you open one. Over time, more and more end up downloaded and kept locally, and the folder quietly grows to match your entire cloud storage.

Worse, several things force full downloads: the “Always keep on this device” option set on a folder, opening files to search them, and some backup software touching every file.

Right-click the OneDrive folder in File Explorer and choose Free up space to return downloaded copies to cloud-only. Then check Settings in the OneDrive app and confirm Files On-Demand is on. The full picture, including why the folder reappears at full size after a reinstall, is in OneDrive filling up your C drive.

Windows Update’s cache

C:\Windows\SoftwareDistribution\Download holds update packages, and it is supposed to clear itself. When an update fails repeatedly, partial downloads accumulate instead.

Clear it properly via Settings → System → Storage → Temporary files, ticking Windows Update Cleanup. Repeated growth here usually means an update that keeps failing, which is a separate problem — an update stuck downloading covers that cycle.

Application caches in AppData

AppData\Local is where applications put data they do not expect you to look at, and some of them never clean up. Common offenders:

• Browser caches. A few hundred megabytes each normally, occasionally several gigabytes when a profile is damaged.
• Teams, Slack, Discord, Spotify. Each caches media aggressively.
• Adobe and video editing applications. Media caches and preview files routinely run to tens of gigabytes, and they are configurable inside the application’s own preferences rather than in Windows.
• Crash dump folders. An application crashing repeatedly can write a multi-gigabyte dump each time.

Check the folder sizes under AppData\Local in your size tool before deleting anything. Each application should be cleared from within its own settings where possible, because deleting the folder by hand can sign you out or reset the app.

The system files that are large on purpose

Several multi-gigabyte files are not waste, and deleting them has costs:

• pagefile.sys — virtual memory. Usually several gigabytes and sized by Windows. Removing it causes out-of-memory errors under load.
• hiberfil.sys — the hibernation file, typically 40–75% of your RAM. It can be removed if you never hibernate, at the cost of hibernation and fast startup. Both files are covered properly in whether hiberfil.sys or pagefile.sys are safe to delete.
• C:\Windows.old — your previous Windows installation after a feature update. 15–30GB, removed automatically after ten days, and removable sooner via Storage settings at the cost of the rollback option.
• System Restore’s shadow copies. Capped by the percentage you configure. If restore points are eating 10% of the drive, reduce the allocation in System Properties → System Protection → Configure rather than deleting them one by one.

Set up the cleanup that runs itself

Once the growing folder is dealt with, two settings stop the slow accumulation coming back.

Storage Sense. Settings → System → Storage → Storage Sense on, then open it to configure. Set the Recycle Bin to empty after 30 days, and set cloud content to become online-only after 30 days if you use OneDrive. The Downloads folder option is there too, and it deletes files you may still want, so decide deliberately.

Understand what it does not cover: application caches, logs, project files, game installations, virtual machine disks. Those are most of the problem, and Storage Sense will never touch them.

Move what does not need to be on C. If the machine has a second drive, relocate the large growing things rather than fighting for space:

• Steam and game libraries, via the launcher’s own storage manager.
• The Downloads, Documents and Pictures folders, by right-clicking each in File Explorer, choosing Properties → Location → Move.
• Application cache locations, where the application offers the setting.

What does not help

• Deleting the same temporary files every month. It is the cycle you are trying to break.
• “PC cleaner” and registry cleaner utilities. They clear the same temporary folders Windows already handles, and the registry portion carries real risk for no measurable gain.
• Disk compression on the system drive. It saves a modest amount and costs CPU on every file access. The space is better found elsewhere.
• Deleting files from C:\Windows\WinSxS by hand. It looks enormous because of hard links that are counted repeatedly. The only safe reduction is the component cleanup option in Disk Cleanup.
• Buying a bigger drive without identifying the growth. A continuously writing process fills 2TB in the same way it filled 256GB, just later.

Realistic expectations

For most people the growing folder is OneDrive or a browser profile, and dealing with it directly means the drive stops refilling rather than refilling more slowly. The investigation takes longer than the fix.

Expect the week-apart comparison to be decisive. A folder that gained 4GB in seven days will reach 200GB within a year, and that arithmetic usually makes the decision obvious without any further diagnosis.

If every folder looks reasonable and the drive is still full, the likeliest remaining explanations are restore points consuming their full allocation or a hidden partition counted into the total. The general audit in C drive full for no reason covers the cases where the numbers genuinely do not add up.