On June 23, 2026, Microsoft pushed out an optional preview update for Windows 11 that finally puts a lid on a stubborn storage bug. The offender: a tiny system file that, when left unchecked, could silently balloon to gargantuan sizes—consuming tens or even hundreds of gigabytes of disk space with no warning to the user.

Labeled KB5095093, the patch is part of the Windows 11 24H2 servicing stack and is currently available as a preview. Its main mission is to correct the runaway growth of CapabilityAccessManager.db-wal, a write-ahead log file tied to the operating system’s permission‑tracking database. For many users, this fix could reclaim vast swaths of storage that quietly disappeared.

What actually changed

Windows 11 uses a built‑in capability access manager to record when apps request access to sensitive hardware—like your camera, microphone, or location—and whether you allowed or denied those requests. The information lives in a small SQLite database located at C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db.

Like many databases, SQLite maintains a separate write‑ahead log (CapabilityAccessManager.db-wal) to speed up write operations. In a properly functioning system, that log should never exceed a few megabytes. But a flaw in the service responsible for checkpointing—merging the log back into the main database—meant that the file grew boundlessly. Left long enough, it could occupy 10, 20, or even 50 gigabytes, with no mechanism to shrink it back down.

KB5095093 corrects the checkpoint logic. After installing the update, the system will regularly trim the write‑ahead log to its intended, petite footprint. The patch also clears any existing bloat automatically, so there is no need to hunt down and delete the file by hand.

Microsoft’s release notes are terse: “This update addresses an issue that causes the CapabilityAccessManager.db-wal file to grow unexpectedly.” But the impact for affected users is far from trivial.

What it means for you

Casual home users

If you run a single Windows 11 PC and never dig into disk usage reports, you might never have noticed the bug. But when that log file gobbles up half your SSD, you’ll feel the pinch: Windows starts complaining about low disk space, performance drops, and features like File History or Windows Update may fail.

Checking now is easy: launch Storage settings (Settings → System → Storage → Show more categories) and look at “System & reserved.” If it shows tens of gigabytes consumed by “System files,” this bloat could be the culprit. The update will not only halt the growth but also erase the accumulated junk.

IT administrators and power users

For admins managing fleets of Windows 11 machines, this bug has been a quiet headache. Over time, dozens or hundreds of PCs could each lose 20–30 GB to a useless log file. That strains centralized monitoring, eats into backup storage, and creates unnecessary help‑desk tickets when users run out of space.

The fix is a preview update, so it must be manually approved in WSUS or deployed via Microsoft Intune as an optional quality update. You’ll want to roll it out sooner rather than later—especially on devices with smaller SSDs (128 GB or 256 GB) where every gigabyte counts. After installing, a simple script can verify that the .db-wal file has shrunk to a few megabytes on each endpoint.

Developers and data‑privacy observers

The CapabilityAccessManager database is part of Windows’ broader effort to give users transparency over app permissions, so the fact that its log ballooned isn’t just a storage issue—it’s a code‑quality blemish. The bug demonstrates how a small logic error in a background service can have outsized consequences. Developers who build Windows services that use SQLite should double‑check their own checkpoint and vacuum logic to avoid similar silent runaway growth.

How we got here

Reports of the CapabilityAccessManager.db-wal bloat started surfacing on forums and Reddit in early June 2026, a few weeks after the May 2026 non‑security update (KB5049622) rolled out. Users who habitually keep an eye on their disk usage via tools like WinDirStat or TreeSize began posting screenshots of the file topping 30 GB and climbing.

By mid‑June, Microsoft acknowledged the issue on a support thread, confirming that it was a known problem under investigation. Within days, the company seeded KB5095093 to the Release Preview channel for Windows Insiders before making it a broad optional update for all Windows 11 24H2 users on June 23.

The tight turnaround suggests that the bug was not present for many months; it likely crept in with a recent quality update—possibly one that modified how the capability access service writes to the database. Microsoft has not publicly identified the specific root cause, but the pattern points to a race condition or a missed checkpoint trigger that only manifested under certain usage patterns.

This isn’t the first time a small system file has run amok. Similar issues have plagued indexing databases, update caches, and telemetry logs in Windows 10. What makes this one distinctive is how completely silent it is: there is no error message, no event log entry, and the file is hidden deep in ProgramData where few users ever look.

What to do now

1. Check if you’re affected

Open File Explorer and navigate to C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\. (You may need to enable “Show hidden files” and confirm admin rights.) If the file CapabilityAccessManager.db-wal is many gigabytes in size, you’re carrying dead weight.

2. Install the fix immediately

Head to Settings → Windows Update and click “Check for updates.” If KB5095093 is offered, select “Download & install.” It is currently optional, so you must explicitly accept it. After installation and a reboot, re‑examine the folder—the .db-wal file should have shrunk to less than 10 MB.

3. Manual cleanup (if you can’t update yet)

If the update isn’t appearing for you or you’re managing a machine that can’t be patched right away, you can manually delete the rogue file. Do not remove CapabilityAccessManager.db—only the .db-wal file. Windows will recreate a tiny fresh log. To do this safely:
1. Stop the “Capability Access Manager Service” from the Services console (services.msc).
2. Delete CapabilityAccessManager.db-wal.
3. Restart the service, or simply reboot.

Be aware that this is a workaround, not a permanent fix. Without the update, the log file will likely start growing again.

4. Prevent recurrence

Once patched, the issue should not return. But it’s a good habit to periodically scan for disk space gluttons. Tools like WizTree or the built‑in Storage Sense (with “Cleanup recommendations” enabled) can help. Also, consider scheduling a monthly disk cleanup task if you manage many PCs.

Outlook

KB5095093 is a preview, which means it will ship to all Windows 11 24H2 devices as part of the July 2026 Patch Tuesday on July 14. Home users who don’t install previews will get the fix then, automatically. Until that date, we may still see fresh complaints from users who haven’t discovered the manual workaround.

More broadly, this bug highlights how even minor quality‑update regressions can have disproportionate effects in an era when many PCs sport 256 GB SSDs and 100 GB+ games. Storage management has become a front‑and‑center concern, and Microsoft’s rapid acknowledgment and fix—while welcome—also underscores the need for tighter automated testing of disk‑footprint impacts in routine updates.

The CapabilityAccessManager log bloat is a nuisance, but it’s a fixable one. If you’ve been wondering where your free space went, now you know—and now you can get it back.