Microsoft acknowledged on June 29, 2026, that a preview update for Windows 11 resolves a disk-hogging bug in the operating system’s app-permission engine. The fix, delivered via KB5095093, reins in a database log file that can silently balloon to tens of gigabytes, reclaiming storage for home users and IT-managed fleets alike.

What Actually Changed

The update targets a little-known system file: CapabilityAccessManager.db-wal. That mouthful is the write-ahead log for a SQLite database maintained by the Capability Access Manager service, the component that controls which apps can access your microphone, camera, location, and other sensitive hardware. Every time an app checks or changes those permissions, the service writes a journal entry. Under certain conditions—especially after recent Windows updates that increased permission polling—the .db-wal file grew without bound because the engine wasn’t triggering a routine checkpoint to flush and compress the log.

KB5095093 changes that behavior. Microsoft’s release notes state the update “improves disk space management for the CapabilityAccessManager database,” though granular technical details weren’t published. What we can infer: the service now periodically performs a PRAGMA wal_checkpoint operation, truncating the write-ahead log back to a sensible size. The fix lands as a “C” preview update, meaning it’s optional for now but will roll into the mandatory July 2026 Patch Tuesday release.

Installation is straightforward: check Windows Update and opt into receiving other Microsoft product updates, then select “Download and install” under the optional quality update section. The patch bumps the OS build to 22631.3810 on 22H2 and 23H2 systems, and 26100.1044 on 24H2—though the KB applies to all currently supported editions.

What It Means for You

For Home Users

If your SSD has been mysteriously losing free space, this could be the culprit. The CapabilityAccessManager.db-wal file lives in a hidden folder (C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\) and doesn’t appear in regular Storage Sense cleanups. Over months of use, it can swell past 10 GB, 30 GB, or more—especially on machines where many applications frequently request microphone or camera access (think conferencing tools, streaming software, voice chat apps).

The good news: once you install KB5095093, the system will automatically shrink the file on the next check. You don’t need to delete anything manually. However, if you’re critically low on space and can’t wait, you can safely remove the .db-wal file without harming your system—the service will recreate a clean log. The main database (CapabilityAccessManager.db) stays untouched, so no app permissions are lost.

For IT Administrators

On shared or multi-user Windows machines—lab computers, kiosks, virtual desktop infrastructure—this leak can rapidly eat up thinly provisioned storage. A single system with dozens of user profiles logging in and out can see the log grow to 50 GB within weeks. The KB5095093 fix is especially welcome in environments where the Capability Access Manager service is under heavy load from policy-driven permission audits.

Deploy via Windows Update for Business, Configuration Manager, or manually through WSUS. Because the update is a preview, you should test it on a limited pilot group first. The payload includes only this disk-space improvement and a small set of non-security fixes, so regression risk is low. Microsoft says the same code will be bundled in the upcoming July security update, meaning you can also simply wait a few weeks for it to arrive automatically if you’re not in a storage pinch.

For Developers

If you’re writing Windows applications that trigger permission prompts, understand that the Capability Access Manager’s database now tidies itself. Should you ever need to inspect the database directly—for debugging, say—use SQLite tools against the main .db file, not the write-ahead log. The log is strictly a journal and should now remain small.

How We Got Here

The Capability Access Manager isn’t new. It debuted in Windows 10 version 1809 and became more prominent in Windows 11 with the introduction of the privacy indicator (the small dot or icon that appears in the taskbar when an app taps your mic or camera). That feature leaned heavily on the service, increasing the volume of write-ahead entries.

Reports of ballooning .db-wal files began surfacing on tech forums and Reddit in mid-2026. Users investigating stubbornly low disk space would find the file using tools like TreeSize or WizTree. Some reported sizes exceeding 40 GB, with the file refusing to shrink even after a reboot. The common thread: affected systems had been online for weeks or months without the database ever being checkpointed. On June 18, a thread on WindowsForum.com aggregated dozens of similar reports, and Microsoft later confirmed the issue in a support bulletin.

The root cause appears tied to a change made in the May 2026 Patch Tuesday update (KB5088229). That month’s security rollup included improvements to the way Windows handles app permission metadata, inadvertently cranking up the frequency of writes to the CapabilityAccessManager database while disabling the automatic checkpoint that normally keeps the write-ahead log in check. KB5095093 is essentially a targeted hotfix, backporting the maintenance routine without reverting the metadata improvements.

What to Do Now

If you haven’t yet installed the preview update, here are your options, ordered by urgency.

  1. Check if you’re affected
    Open File Explorer, paste %ProgramData%\Microsoft\Windows\CapabilityAccessManager\ into the address bar, and look for CapabilityAccessManager.db-wal. Note its size. Anything over 1 GB on a personal machine is suspicious; anything over 10 GB is almost certainly the leak.

  2. Reclaim space immediately
    If you’re dangerously low on disk, you can delete the .db-wal file right now. It’s safe—the main database stays intact. You may need to take ownership of the folder first: right-click the file, go to Security > Advanced, and give your user account full control. A simpler route: open Disk Cleanup as administrator, select the system drive, and check “Capability Access Manager log files” (this option appears only after you’ve taken ownership; otherwise it’s hidden). Alternatively, a reboot sometimes triggers a checkpoint, but user reports indicate that’s unreliable.

  3. Install KB5095093
    Head to Windows Update, turn on “Get the latest updates as soon as they’re available,” and check for updates. KB5095093 will show as an optional update. Click Download & install, then restart. The system will checkpoint the database during startup, reducing the .db-wal file to a few megabytes.

  4. Wait for the July Patch Tuesday (July 8, 2026)
    If your disk isn’t critical and you prefer stability, the fix will be bundled into the mandatory cumulative update in July. No action needed; it’ll install automatically.

  5. IT admins: deploy selectively
    Push KB5095093 to user groups most likely affected—engineers running CAD software with mic access, financial analysts using camera-based authentication, or any role with heavy application switching. Use the Microsoft Update Catalog if you need the standalone .msu file for offline installation.

Outlook

Storage leaks in Windows have become rarer as Microsoft’s telemetry catches up, but they still sting when they appear. The CapabilityAccessManager.db-wal bug is a classic case: a background service doing its job, a journal meant to prevent data corruption, and an oversight that let the journal run wild. KB5095093’s quick turnaround—barely a month after the problematic May update—suggests Microsoft’s servicing pipeline is increasingly responsive to community-fed bug reports.

Looking ahead, insiders say the Capability Access Manager may get a broader under-the-hood refresh in Windows 11 version 24H4, which could move the database to a more efficient storage format. Until then, this preview fix should keep your drive free of hidden permission-log bloat. Keep an eye on your ProgramData folder after future cumulative updates, and if you spot similar behavior, the Feedback Hub is your best friend.