- Microsoft’s recent update acknowledged a Windows 11 bug that triggers a hidden system file to consume hundreds of gigabytes of storage.
- The issue affects the CapabilityAccessManager.db-wal file, linked to Windows privacy and app permission logging.
- Microsoft has released a fix in the optional KB5095093 update, with the same fix expected to reach all supported Windows 11 systems in the July 2026 Patch Tuesday update.
Ever noticed that your computer’s memory is disappearing without any reason? A newly discovered bug on Windows 11 can consume your memory without showing any signs.
Although Microsoft revealed this via an update, the problem has been haunting users for a while. A few steps is all it takes to detect if the bug is affecting your computer. Here’s what you need to know about it.
A Hidden File that Grows Out of Control
A file called CapabilityAccessManager.db-wal within C:\ProgramData\Microsoft\Windows\CapabilityAccessManager is the culprit. This file shares links to a Windows service that controls which apps can access camera, microphone, location, screen recording, etc. In a healthy system, the file size is usually a couple of megabytes.
However, in some Windows 11 systems, this log file can grow to an infinite size. The bug keeps this file from merging with the main database, like it normally should. So it just keeps growing and balloons to sizes that take up a huge chunk of memory space over time. There have been reports from users who witnessed the file consuming up to 70GB, 110GB, and even 200GB of storage. One Reddit post that went viral revealed a case where the file reached 513GB.
Microsoft Quietly Confirmed and Fixed the Problem
Users first reported this strange storage loss on Microsoft’s Feedback Hub and Reddit earlier this year. Many only discovered the issue after using third-party storage analysis tools.
Despite months of user complaints, Microsoft never added it as an issue on the Windows Health Dashboard. What the company did was to quietly update release notes for the optional KB5095093 preview on June 29. The note reads: “[Storage] This update improves disk space usage for CapabilityAccessManager.db-wal file.”
That short line was Microsoft’s first public acknowledgment of the bug. The fix is now available for users who install the optional June preview update. Every other user will get the update automatically. It’ll also come together with the July 2026 Patch Tuesday cumulative update Microsoft has scheduled for release on July 14.
Why Storage Issues Happen
Microsoft hasn’t shared a detailed technical explanation yet. But here is what we know. The issue is with a database log file tagged Write-Ahead Log (WAL). This log is responsible for storing changes before they enter the main database. Normally, the system then merges these changes and shrinks the log file back down.
Technical problems are not limited to Windows, Pixel phones have been experiencing eSIM connectivity issues that force users to restart their devices frequently.
It causes the Windows 11 system cleanup process to fail. Hence, the log will keep on growing instead of shrinking as it normally should. It may keep recording permission-related events without stopping. The exact trigger is still unclear. But reports suggest it affects some systems more than others. It might depend on how many apps are requesting privacy permissions on your PC.
How to Check for the Problem
The easiest warning sign is unusually high storage use. Head to Settings > System > Storage > Show more categories > System & Reserved. If the “System files” category is taking up far more space than expected, your PC could be affected.
Power users can confirm the issue by checking the protected folder directly. Try tools like TreeSize, WinDirStat, or WizTree to check your storage. If you’d rather use a command-line approach, Microsoft’s Robocopy in read-only mode does the trick, it won’t mess with permissions on system files, but you’ll still see the file sizes. Usually, on a system that’s working fine, the whole folder only takes up a few megabytes.
What to do Next
For most people, installing KB5095093 is the simplest solution. If you prefer to wait, you can get the fix in the July security update. Do not try to delete the file while Windows is running normally. It is a protected system file. Deleting it could cause problems.
If the storage issue has already filled your drive, you may need to boot into Safe Mode. From there, you can rename the oversized file and let Windows make a fresh one. But this is a risky workaround. Use it only when Windows Update can’t complete because your drive is completely full.
This bug is not a security vulnerability. There is no evidence it exposes your data. But it does show how a small failure inside a background Windows component can cause major real-world problems.
Users can lose hundreds of gigabytes without even realizing it. No warning, no clear reason. It causes people to look for third-party solutions to fix something Microsoft should have handled without delay.
