Microsoft has confirmed a Windows 11 bug where a system log file can balloon to tens or even hundreds of gigabytes, quietly eating up space on the C drive. This issue involves the CapabilityAccessManager.db-wal file, which manages app permissions. The company has already released a fix in an optional update, with a mandatory rollout scheduled for July 14 as part of the next Patch Tuesday.
What causes the Windows 11 CapabilityAccessManager.db-wal file to grow excessively?
The problematic file is part of the Capability Access Manager component, responsible for tracking access to your microphone, camera, location, screen recording, and other Windows features. The ”.db-wal” suffix denotes a write-ahead logging file, a temporary journal typically used by SQLite databases to safely record changes. Under normal conditions, these files are just a few megabytes in size. But for some users, this log file has grown endlessly.
How large can the bloated log file become in Windows 11?
According to reports from Windows Latest, some users have found this file swelling to 70, 110, 200, and even over 500 gigabytes on their system drives. Considering a fresh Windows 11 install occupies far less space, such bloating is highly unusual. On laptops with modest SSDs-like 256GB or 512GB models-this quickly creates a serious storage crunch. Users face failed updates and apps complaining about low disk space, with system reports inconsistently blaming ”System files” or the ”System and reserved” partition.
Why standard Windows tools fail to identify the storage issue
The real headache is that standard Windows tools don’t pinpoint the true source of the storage leak. Users notice their free space vanishing fast with no clear explanation. Diagnosing the issue requires diving into system folders or using third-party disk analyzers that accurately reveal what’s consuming space.
Microsoft’s fix for the Windows 11 storage bug
Microsoft addressed the bug in an optional update, KB5095093, released in June 2024. Such preview updates arrive at the end of the month but don’t install automatically. The fix will be included in the mandatory security update released to most Windows 11 users on July 14.
What to do after applying the Windows 11 bug fix
While the bug appears infrequent, its impact is hard to ignore. If the log file has already ballooned to hundreds of gigabytes, simply applying the update won’t restore your disk space. After patching, users will need to check if the file size has decreased and if storage has been freed. This will be especially obvious on devices with smaller SSDs.
Implications for Windows 11 storage management and reliability
Windows 11’s growing pains around storage management highlight ongoing challenges in maintaining reliability on modern PCs. Similar issues with system logs and cache files are familiar pain points for users across platforms, though Microsoft’s quick patch shows it’s actively addressing them. Going forward, it will be worth watching if Microsoft improves Windows’ built-in disk space reporting to avoid these stealth storage leaks.