Microsoft released an optional preview update on June 23, 2026, that finally tackles a storage-wasting bug in Windows 11. The culprit: a database log file named CapabilityAccessManager.db-wal that, on some machines, silently balloons to hundreds of gigabytes—leaving users puzzled over rapidly vanishing free disk space. Labeled KB5095093, the update is now available through Windows Update’s “Optional updates” section and puts a stop to that file’s runaway growth.
The update and the mystery file—what you need to know
KB5095093 is a non-security preview update for Windows 11, meaning it rolls out ahead of the regular monthly Patch Tuesday cycle. It targets a single, specific issue: the CapabilityAccessManager.db-wal file failing to shrink itself after recording changes to the Windows Capability Access Manager database.
The Capability Access Manager is the background service that manages how apps request and use sensitive device capabilities—your camera, microphone, contacts, and location. To track these permissions, Windows keeps an SQLite database inside C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\. Whenever that database is modified, the system writes to a temporary write-ahead log (the .db-wal file). Under normal conditions, this log is periodically truncated or committed back into the main database, keeping its size negligible. But here, a logic flaw prevents that cleanup, allowing the file to grow unchecked.
The result: CapabilityAccessManager.db-wal can swell to 500 GB or more, silently hogging space. Because it sits deep in a hidden ProgramData folder, most disk cleanup tools overlook it, leaving affected users with no clear explanation for their suddenly full drives.
Why this matters to you—home users, power users, and IT admins
For the average home user, the symptom is what makes this bug so insidious. You might notice your SSD is unexpectedly close to capacity, with Windows’ own storage sense or Disk Cleanup showing no large files. Apps might start behaving erratically because there’s no room for temporary data. If you’re constantly deleting videos and photos to free up space only to see it disappear again within days, this bug could be the culprit.
Power users can quickly confirm the problem by navigating to the CapabilityAccessManager folder and checking the file’s properties. If it’s consuming dozens or hundreds of gigabytes, you’ve found the leech. You aren’t alone—reports have been surfacing on forums and social media for months, with many initially suspecting malware or failing hardware.
IT administrators and enterprise users face a more serious challenge at scale. In environments where dozens or hundreds of workstations might be affected, the accumulated storage waste can quietly erode free space on managed SSDs, triggering alerts and forcing unnecessary storage upgrades. Worse, if the .db-wal file grows large enough that a system drive runs out of free bytes entirely, Windows might fail to install security patches or create restore points, undermining overall fleet health. KB5095093’s arrival is thus a relief not only for individuals but for anyone managing multiple Windows 11 machines.
How we got here—the backstory of the 500 GB hidden file
The CapabilityAccessManager database and its supporting files have been part of Windows for years, but the runaway growth appears to have been triggered by a change in a recent feature update. Most reports trace the problem back to Windows 11 version 24H2, though some users on 23H2 have also reported symptoms after installing certain cumulative updates. Over the following months, complaints grew louder on Microsoft’s own community forums, Reddit’s r/Windows11, and tech enthusiast sites.
Early workaround attempts ranged from manually deleting the file (which often caused the service to fail until a reboot) to using disk cleanup scripts. Some third-party tools started flagging the file, but until Microsoft acknowledged the bug and coded a fix, no permanent solution existed. The company eventually rolled KB5095093 into the June 2026 preview channel, signaling that the fix will be baked into the July 2026 Patch Tuesday security update for anyone who prefers to wait.
What to do right now—installing the fix or cleaning up manually
Option 1: Install KB5095093
If you’re comfortable running a preview update, go to Settings > Windows Update > Check for updates, then look under the “Optional updates available” area. Find KB5095093, install it, and reboot. After the update, Windows will automatically manage the .db-wal file size, typically keeping it under a few megabytes.
Option 2: Clean up manually if you can’t update immediately
For those who cannot install the update right away—perhaps because of deployment policies or compatibility concerns—you can safely delete the oversized log file with a few PowerShell steps. Stop the CapabilityAccessManager service, delete the file, then restart the service. Here’s exactly how:
- Open PowerShell as Administrator (right-click Start button, select Terminal (Admin)).
- Stop the service:
powershell Stop-Service -Name CapabilityAccessManager -Force - Navigate to the database directory:
powershell cd "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" - Delete the WAL file:
powershell Remove-Item .\CapabilityAccessManager.db-wal -Force - Restart the service:
powershell Start-Service -Name CapabilityAccessManager
The service will automatically recreate a fresh, empty .db-wal file. All your app permission settings are preserved in the main database file.
A word of caution: The manual deletion is safe and won’t harm your system, but if you frequently modify app permissions, the file may begin growing again until you apply KB5095093. It’s a temporary bandage, not a cure. Also, before deleting, you might want to note the file size so you can see the space recovered after a reboot.
Option 3: Wait for the official stable rollout
If you’d rather not touch preview updates, the fix will be included in the July 2026 Patch Tuesday cumulative update, which arrives on July 14, 2026. In the meantime, keep an eye on your free space and consider the manual cleanup if things get tight.
Outlook—what’s next for this fix and Windows reliability
KB5095093 is proof that even obscure system files can cause outsized headaches. Microsoft has yet to publish a formal advisory about the bug, but given the volume of user reports, the final July update will likely mention the fix in its release notes. Beyond this specific glitch, the episode highlights a broader need: better built-in tooling to flag aberrant file growth. Windows already includes Storage Sense and Disk Cleanup, but neither currently alerts you to a suddenly bloated system database. Third-party disk analyzers like WizTree or WinDirStat can help, but the average user shouldn’t need them.
For now, installing KB5095093 or performing the manual cleanup steps will safeguard your storage. Keep an eye on Windows Update in the coming weeks for the official broad release—and when someone asks why their PC keeps running out of space, you’ll know exactly what to tell them.