A Windows 11 storage bug confirmed by Microsoft can silently consume up to 500GB of your hard drive — with no pop-up, no warning, and no obvious culprit. If your PC has been running low on space for no clear reason, this bug is almost certainly to blame. Here is exactly what is happening, how to check whether you are affected, and the fastest way to reclaim your storage.
What Is the Windows 11 Storage Bug?
The root cause is a runaway log file inside the Capability Access Manager (CapabilityAccessManager), the Windows 11 component responsible for managing which apps can access your camera, microphone, location, and other sensitive resources. Under normal conditions, this service maintains a small database file to log permission events. The disk space bug causes that log — technically a write-ahead log (WAL) file — to grow without bounds, sometimes swelling to nearly 500GB on an affected machine.
The bloated file lives at:
-
C:\ProgramData\Microsoft\Windows\AppRepository\ -
The specific file is named CapabilityAccessManager.db-wal
Because it sits inside a system folder, Windows Storage Sense and most third-party cleaners do not flag it. Your “System & Reserved” storage category balloons silently, and the drive fills up with no obvious explanation.
Which Versions of Windows 11 Are Affected?
Microsoft confirmed the Windows 11 storage bug affects Windows 11 24H2 — the current major release — but reports from users on 23H2 have also surfaced. The bug appears linked to the way the Capability Access Manager handles high-frequency permission requests from apps that access the camera, microphone, or location services heavily, such as video-conferencing and streaming software. The more actively those apps run, the faster the log file grows.
How to Check If the Disk Space Bug Is Affecting You
Follow these steps to see whether the disk space bug has hit your machine:
-
Open Settings → System → Storage.
-
Click Show more categories at the bottom of the storage breakdown.
-
Select System & Reserved and look at the total size.
-
If System & Reserved shows an unusually large figure — anything above 40–50GB is suspicious — the bug is likely the cause.
For a more precise check, open an elevated Command Prompt (right-click Start → Terminal (Admin)) and run:
-
dir "C:\ProgramData\Microsoft\Windows\AppRepository\CapabilityAccessManager.db-wal" /a
A healthy file is typically a few megabytes. If the output shows gigabytes, you are affected by this Windows 11 storage issue and should apply the fix immediately.
The Official Storage Bug Fix: KB5095093
Microsoft quietly addressed the storage bug fix in optional update KB5095093, released in June 2026. The patch description states it “improves disk space usage for the CapabilityAccessManager” — understated phrasing for a bug that can destroy half a terabyte of storage. According to Windows Latest’s confirmed report, a mandatory rollout was also scheduled for the July 14, 2026 Patch Tuesday cumulative update.
To install the fix now without waiting for the automatic rollout:
-
Go to Settings → Windows Update.
-
Click Advanced options → Optional updates.
-
Tick KB5095093 and click Download & Install.
-
Restart your PC when prompted.
After rebooting, the WAL file will stop growing. However, the patch alone may not automatically delete the already-bloated file — see the manual reclaim steps below.
Manually Reclaiming the Lost Disk Space
Once KB5095093 is installed and your PC has restarted, use these steps to reclaim the storage the Windows 11 storage bug already consumed:
-
Open Disk Cleanup (search “Disk Cleanup” in Start), select your C: drive, then click Clean up system files.
-
Tick System error memory dump files, Windows Update Cleanup, and Temporary files, then click OK.
-
If System & Reserved is still bloated, open an elevated Command Prompt and run:
dism /online /cleanup-image /startcomponentcleanup -
For a targeted approach, you can safely delete the
CapabilityAccessManager.db-walfile manually after stopping the CapabilityAccessManager service — but only after applying the fix, otherwise the file will simply regrow.
Running Windows’ built-in Storage Sense after the patch is applied and the WAL file is cleared is a good way to verify that System & Reserved has returned to a normal size (typically under 20GB for a clean Windows 11 installation).
Why This Disk Space Bug Went Unnoticed for So Long
Several factors made the disk space bug exceptionally hard to spot:
-
Hidden system folder: The AppRepository directory is not indexed by standard storage tools or File Explorer’s folder-size view.
-
Slow accumulation: The file grows gradually over weeks, not overnight, so users attribute the storage loss to normal system updates or apps.
-
No error message: Windows does not alert you when a system service log file grows beyond a reasonable size.
-
Misdiagnosis: Some users — and reportedly even a Microsoft support agent — suggested buying a new hard drive rather than identifying the real cause.
The bug was eventually surfaced through community investigation on forums and Reddit, where users compared unusually large System & Reserved figures before Microsoft officially acknowledged the issue.
What to Do If Your PC Runs Out of Space Before the Fix
If you are in a critical situation — your drive is nearly full and apps are crashing or failing to save files — here is an emergency approach before you can apply the full storage bug fix:
-
Move large personal files (videos, photos, backups) to an external drive or cloud storage temporarily.
-
Use Settings → Storage → Temporary files to quickly delete cached data.
-
Avoid running camera or microphone-heavy apps until the patch is applied, as these appear to accelerate the log-file growth.
-
If possible, apply KB5095093 as an emergency priority — it is available right now as an optional update.
For more context on rolling back problematic Windows patches or dealing with update-related issues, our guide on safely removing a Windows Update patch walks through the full process step by step. And if you encountered the separate 0x800f0922 error during a recent update attempt, our Windows 11 update error fix guide covers the confirmed root cause and resolution.
Keep Your Windows 11 Licence Secure While You Troubleshoot
Major storage failures can sometimes trigger Windows to question the validity of your licence — particularly on OEM installations tied to specific hardware configurations. If you see activation warnings after recovering from a near-full drive, it is worth ensuring your licence is in order. Shop Key Online supplies genuine Windows 11 Pro OEM keys from €15.95, delivered instantly by email with full activation support included — so you are never left in limbo if a system issue complicates your activation status.
Frequently Asked Questions
What exactly is the Windows 11 storage bug?
It is a defect in the Capability Access Manager service that causes its database write-ahead log file (CapabilityAccessManager.db-wal) to grow without limit. Microsoft confirmed it can reach nearly 500GB on affected systems. The bug is present in Windows 11 24H2 and reportedly some 23H2 installations.
How do I know if the disk space bug has affected my PC?
Go to Settings → System → Storage → Show more categories → System & Reserved. If the figure is unusually high (well above 30–50GB), you are likely affected. You can confirm by checking the size of CapabilityAccessManager.db-wal in C:\ProgramData\Microsoft\Windows\AppRepository\ via an elevated Command Prompt.
Is the storage bug fix available right now?
Yes. The fix is in optional update KB5095093, available since June 2026 via Settings → Windows Update → Advanced options → Optional updates. A mandatory deployment via Patch Tuesday was also planned for July 14, 2026, so systems that have not manually installed it should receive it automatically shortly after that date.
Will the patch automatically delete the bloated file?
The patch stops the file from growing further, but it may not automatically shrink or delete the already-bloated WAL file. After applying the update and restarting, run Disk Cleanup (with Clean up system files selected) and optionally use DISM with the /startcomponentcleanup flag to reclaim the space fully.
Can I just delete the CapabilityAccessManager.db-wal file manually?
Technically yes — but only after applying KB5095093. If you delete the file without the patch installed, the Capability Access Manager service will simply recreate and re-bloat it. Stop the service first, delete the file, apply the patch, then restart. Never modify system files without a current backup.
Does this bug affect Windows 10?
Microsoft’s acknowledgement specifically names Windows 11. The Capability Access Manager architecture differs between Windows 10 and 11, and no confirmed reports of the same WAL-file bloat issue have emerged on Windows 10 machines as of July 2026.
