One day your PC says you're running out of storage.
The next day, Windows refuses to install updates, new applications won't download, and your once spacious SSD suddenly has only a few gigabytes left.
You check your Downloads folder.
Nothing.
You empty the Recycle Bin.
Still nothing.
Where did hundreds of gigabytes go?
If this sounds familiar, you may have encountered one of Windows 11's strangest storage bugs. Microsoft confirmed an issue where a system log file can silently grow until it consumes hundreds of gigabytes of disk space, with some users reporting files exceeding 500GB.
The good news? Your personal files haven't disappeared, and the problem has a straightforward fix.
This wiki explains what's causing the issue, how to determine whether your PC is affected, and the safest way to recover your storage.
What Is the Windows 11 Storage Bug?
The issue revolves around a Windows component called Capability Access Manager.
This service manages application permissions for sensitive features such as your camera, microphone, location, contacts, and screen recording. Whenever an app requests access to one of these features, Windows records the activity inside a database.
To improve performance, Windows temporarily stores changes inside a Write Ahead Log (WAL) file before merging them into the main database.
Normally, that log grows during regular use and then shrinks automatically after the data has been processed.
The bug prevented that cleanup process from happening.
Instead of being compacted, the log continued growing indefinitely until it occupied enormous amounts of storage.
Why Can It Consume More Than 500GB?
The affected file is named:
CapabilityAccessManager.db-wal
Under normal conditions, this file is relatively small.
However, systems affected by the bug experienced continuous growth because Windows never compacted the log.
Reports from users included file sizes of:
- Around 70GB
- More than 200GB
- Nearly 500GB
- Over 513GB on some verified systems
Because the file is hidden inside Windows system folders, most users never realize what's consuming their storage until the drive is nearly full.
Common Symptoms
The bug often appears without any warning.
You might notice:
- Windows suddenly reporting low storage.
- Applications refusing to install.
- Windows Update failing.
- Slower overall system performance.
- Large SSDs mysteriously becoming full.
Since the storage is consumed by a hidden system file, traditional cleanup methods usually don't solve the problem.
How to Check If Your PC Is Affected
The quickest way to investigate is through Windows Storage settings.
Method 1: Storage Settings
- Open Settings.
- Select System.
- Click Storage.
- Choose Show more categories.
- Review System & reserved or System files.
If the reported size seems unusually large especially hundreds of gigabytes It may indicate this issue.
Method 2: Storage Analysis Tools
Utilities such as TreeSize or similar disk analyzers can help identify unusually large system files and reveal whether the CapabilityAccessManager.db-wal file has grown abnormally.
Why You Shouldn't Delete the File Manually
When users discover a massive hidden file consuming storage, the first instinct is often to delete it.
That isn't recommended.
The file belongs to Windows and is actively used by the operating system.
Removing or modifying it manually could lead to unexpected behavior or data inconsistencies.
Instead, Microsoft recommends installing the official fix, which allows Windows to clean up the file safely.
How Microsoft Fixed the Problem
Microsoft addressed the issue in update:
KB5095093
The fix is included in:
- Build 26200.8737
- Build 26100.8737
It first became available through the June 2026 Optional Update and was later scheduled for wider rollout through July 2026 Patch Tuesday.
Once installed, Windows resumes managing the Write-Ahead Log correctly, preventing it from growing indefinitely.
How to Install the Fix
If your system hasn't received the update automatically, you can install it manually.
- Open Settings.
- Select Windows Update.
- Click Advanced options.
- Open Optional updates.
- Locate KB5095093.
- Install the update.
- Restart your computer if prompted.
After the update is installed, Windows should begin handling the database log normally.
Will You Get Your Storage Back Immediately?
In many cases, yes but not always instantly.
After installing the update, Windows can compact the oversized log file and return it to its normal size.
Depending on your system, you may need to restart your computer before the reclaimed storage becomes visible.
If disk usage doesn't decrease immediately, allow Windows some time to complete background maintenance before assuming the issue remains unresolved.
How to Prevent Similar Problems
While this specific bug has been fixed, a few habits can help you identify future storage issues more quickly.
Consider:
- Checking Storage settings regularly.
- Installing Windows updates promptly.
- Monitoring unusually large system files with trusted storage analysis tools.
- Keeping sufficient free space available on your SSD.
Catching abnormal storage growth early makes troubleshooting much easier.
Frequently Asked Questions
What caused the storage bug?
A Windows bug prevented the CapabilityAccessManager.db-wal Write Ahead Log from being compacted, allowing it to grow continuously.
Is my personal data at risk?
No. The issue affects a Windows system log file rather than your personal documents, photos, or applications.
Can I delete the file manually?
It's not recommended. Installing Microsoft's official update is the safest solution.
Which update fixes the issue?
Microsoft resolved the problem through KB5095093, included in the June 2026 optional update and subsequent releases.
How much storage can this bug consume?
Reported cases ranged from around 70GB to more than 500GB, depending on the affected system.
Final Thoughts
Storage problems are frustrating enough but they're even more confusing when Windows itself is responsible.
The Capability Access Manager bug demonstrated how a small issue inside a system database could silently consume hundreds of gigabytes without users realizing where their storage had gone.
Fortunately, Microsoft has released an official fix, and once installed, affected systems should return to normal behavior.
If your Windows 11 PC has suddenly run out of storage for no apparent reason, checking for this issue should be one of the first troubleshooting steps.
Sources
- Microsoft Support Documentation
- Microsoft Windows Release Notes
- KB5095093 Update Documentation