Microsoft Confirms Windows 11 Storage Bug Caused by CapabilityAccessManager, Releases Fix
Key Takeaways
- ▸CapabilityAccessManager.db-wal file can grow to 50GB-500GB due to improper log compaction, consuming critical system storage
- ▸Normal file size should be 1-4MB; larger sizes indicate the user is affected by the bug
- ▸Microsoft released fix KB5095093 immediately, with automatic rollout expected in July 2026 Patch Tuesday update
Summary
Microsoft has acknowledged a critical bug in Windows 11 where the CapabilityAccessManager.db-wal file—a write-ahead log tied to the system's privacy and capability tracking database—can grow uncontrollably to consume hundreds of gigabytes of storage. Users have reported instances of this file reaching 50GB, 200GB, and even 500GB, silently filling the C: drive without user awareness.
The root cause is a failure in the Windows logging system to properly compact and merge the WAL file back into the main SQLite database. Capability Access Manager logs access requests for permissions like microphone, camera, location, and screen capture, but under current conditions, these logs accumulate indefinitely in the WAL file instead of being pruned. A normal CapabilityAccessManager.db-wal file should be 1-4MB; files exceeding tens of gigabytes indicate the bug.
Microsoft has released the fix via Windows 11 KB5095093 and plans to distribute it automatically through the July 2026 Patch Tuesday security update. Affected users can verify the issue by navigating to Settings > Storage > Show more categories > System & Reserved and checking system storage usage. The fix is recommended for any system showing abnormally large system file sizes.
- The file is located in C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\ (protected folder)
- Issue affects unspecified number of Windows 11 users; not all systems are impacted
