Technical Anshu
Tutorials Blog
💾 Long Term Space

C Drive Full Again Next Month Why Update Space Comes Back and How to Manage It

You cleaned everything, reclaimed 40 GB — and after the next round of updates the drive is creeping red again. This is not the cleanup failing. Some update weight is a permanent cost of a living Windows, and some only looks like it returned. Here is the honest split, and the management habits that end the monthly emergency.

✍️ Technical Anshu🪟 Windows 11⏱️ 6 minute read
🎥 Watch the full process in the video — the cleanup done once, properly, so the panic does not repeat

Let us say the quiet part first: you cannot stop Windows updates from using space, and trying to — by blocking updates or gutting system folders — trades a storage annoyance for a security problem. What you can do is understand which gigabytes are rented and which were squatters, keep the squatters from returning, and give the rent a budget. That is the whole of long-term C drive management.

What returns after cleanup — honest expectations
Monthly update download cache0.3 to 2 GB NORMAL
Delivery Optimization cacherefills slowly NORMAL
Windows.oldonly after feature updates RARE
CapabilityAccessManager.db-wal growthstays fixed after KB5095093 CURED
KBs of free space lost daily for no reasonnot normal — investigate WARNING
A healthy PC reclaims most update working space by itself over the following days. Only the last row is a symptom.
Expectation table. Normal refill is small and stabilises — runaway refill is a bug report, not a lifestyle.
1

What Actually Comes Back Every Month

  1. The download cache at work: each cumulative update is fetched into SoftwareDistribution before installing — a few hundred MB to around 2 GB of working space that is mostly released afterwards
  2. Servicing history: Windows keeps the replaced file copies of recent updates so they can be uninstalled. This pile grows within the month and is what Disk Cleanup's Windows Update Cleanup periodically retires
  3. The Delivery Optimization cache refills as new updates and Store apps arrive. It is a cache doing cache work — cap it on small drives instead of fighting it
  4. Net effect on a healthy PC: the free-space line wobbles by a few GB around Patch Tuesday and settles. A wobble is not a relapse
2

What Does Not Come Back — the One-Time Piles

  1. Windows.old appears only when Windows changes version — feature updates, roughly a yearly event — not after monthly security updates
  2. The CapabilityAccessManager bug does not return once KB5095093 or any later cumulative update is installed. The fix travels inside every cumulative update after it, so staying updated is staying cured
  3. CBS log bloat does not return on a healthy servicing stack; if the 2 GB log stack reappears, treat it as a servicing fault to repair, not a routine to repeat
  4. If space is vanishing daily with none of these signatures, something else is writing — a backup tool's local cache, a sync client, a runaway app log. Measure the drive again and let the scanner name it
3

Give Updates a Budget Instead of a Battle

Windows also quietly defends its own update room through reserved storage — a few GB it holds so updates never fail for lack of space. You do not need to manage that here; the practical budget is yours to set.

  1. Keep roughly 10 to 15 percent of C: free as permanent working room — on a 256 GB drive, that is 25 to 38 GB that is not "wasted", it is the runway updates land on
  2. Turn on Storage Sense with the Downloads row set to Never, so temporary weight is retired automatically
  3. Cap Delivery Optimization uploads on small drives through its Advanced options page
  4. Run the Disk Cleanup system files pass two or three times a year — after feature updates especially — to retire superseded update copies
4

The Real Fix for a Chronically Small Drive

Honesty time: some drives are simply too small for modern Windows plus real life. A 128 GB C drive carrying Windows, Office, a browser's cache and updates will live on the edge forever, no matter how good the cleaning routine is.

  1. Move what is movable first: personal files, photos, downloads and game libraries belong on a second drive or partition
  2. Point OneDrive or your sync folder at the bigger drive rather than C:
  3. Uninstall — never delete — the apps you no longer use, through Settings → Apps
  4. When hardware allows, the permanent cure is a larger SSD with Windows on a partition of 200 GB or more. Every cleanup in this series then becomes an occasional tidy instead of a monthly rescue
5

The Five-Minute Monthly Routine

  1. A few days after Patch Tuesday, glance at Settings → System → Storage: free space should be near your normal line
  2. If Temporary files shows several GB, run the one-click removal — installation files and Delivery Optimization rows included
  3. If System files has jumped by tens of GB, do not clean — investigate. That jump is the bug signature, and the answer is an update, not a broom
  4. Once or twice a year, after a feature update settles, do the full pass: rescue files from Windows.old, remove the previous version, run Disk Cleanup system files
  5. Total cost of the routine: about five minutes a month. Total benefit: the red drive stops being a surprise
🔴 Never "solve" update space by disabling Windows Update. An unpatched PC is a far bigger problem than a tight drive — and the KB5095093 story proves the point: the cure for an update bug arrived inside an update.

🎥 Watch the Complete Video Guide

The cleanup plus the habits that keep it cleaned — the complete routine is in the video.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Can I stop Windows Update from using so much space?

Not fully, and you should not try. Updates need room to download, stage and install, and Windows even reserves a few GB to guarantee that room. What you can control is the leftovers: Storage Sense for temporary files, periodic Disk Cleanup system files passes for superseded update copies, and a cap on the Delivery Optimization cache. Blocking updates themselves trades a storage chore for a security risk.

Why is my 128 GB C drive always nearly full?

Because the maths no longer fits. Windows itself with its servicing history, one office suite, browsers with their caches, and a year of updates can occupy most of 128 GB before a single personal file is added. Move personal data and games to another drive, keep updates cleaned with the monthly routine, and when you can, move Windows to a larger SSD — that is the only permanent version of this fix.

Will the CapabilityAccessManager bug come back after KB5095093?

No. The fix is built into KB5095093 and carried in every cumulative update released after it. A PC that stays updated stays fixed. The file may still exist — it is supposed to — but it remains at its normal few-MB size because the checkpoint behaviour that was broken is repaired.

This guide is based on the Technical Anshu C drive full after update video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏