A routine Windows 11 optional update released in June 2026 has tackled a long-standing storage bug that could silently consume tens of gigabytes on your system drive, with no warning until space ran out. The culprit: a tiny write-ahead log file tied to the Capability Access Manager service, known as CapabilityAccessManager.db-wal. While it normally manages app permissions records at a modest size, a flaw caused it to balloon uncontrollably on some PCs—and the fix is finally here.

What Actually Happened

The Capability Access Manager service (camsvc) is a core Windows component that governs how apps request and use sensitive hardware, including your microphone, camera, and location. Every time an app checks or uses one of these features, the service logs the event in a local database. That database lives at C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db, and like any SQLite database, it uses a write-ahead log (the .db-wal file) to ensure transactional integrity.

Under normal circumstances, the WAL file is temporary—it grows as transactions occur, then is periodically folded back into the main database. But a bug in the service’s log management logic prevented that cleanup from happening on some systems. The file could inflate from a few megabytes to 40 GB, 80 GB, or even more, slowly strangling the free space on your C: drive. Users often didn’t notice until Windows began throwing “low disk space” warnings or automatic updates failed because there was no room to download them.

The June 2026 optional update, currently rolling out through Windows Update as a preview, finally addresses the root cause. According to Microsoft’s release notes, the fix “resolves an issue where the CapabilityAccessManager.db-wal file may grow excessively, leading to disk space exhaustion.” The update changes how the service handles WAL checkpoint operations, ensuring that the log is properly truncated after each checkpoint. Additionally, it adds a safeguard that forces a checkpoint if the file exceeds a certain threshold, preventing a runaway scenario.

What It Means for You

For everyday users

If your PC has been mysteriously losing disk space despite no obvious downloads or file growth, the CapabilityAccessManager.db-wal file could be the silent villain. Even after installing the June 2026 update, the patch only stops future growth; it does not automatically shrink or delete an already-bloated WAL file. You may need to manually reclaim that space. We’ll walk through the steps below.

For IT administrators and power users

This bug is particularly insidious in enterprise environments where machines run 24/7 with a mix of apps that frequently access microphones and cameras (think conferencing tools, security software, or accessibility utilities). A single endpoint could lose over 100 GB to this log file, causing widespread user complaints and help-desk tickets. The fix is included in the optional update, which means it won’t be forced via Windows Update for Business until the next Patch Tuesday (likely July 2026). However, you can deploy the optional update now to affected systems, or use a manual cleanup script as an interim workaround.

How We Got Here

The Capability Access Manager debuted in Windows 10 (version 1809) as part of Microsoft’s push to give users more control over hardware permissions. It’s the engine behind those frequent “app wants to use your microphone” prompts and the privacy settings page. Each permission check—whether granted or denied—generates a log entry, and on a busy system that can mean thousands of entries per day.

The WAL file explosion began attracting attention on forums like Reddit and Microsoft’s own Answers community in early 2026. Users reported seeing CapabilityAccessManager.db-wal consuming 30 GB, 50 GB, even 120 GB. Some traced the issue to certain apps (especially browsers with real‑time audio/video capture) that kept re‑prompting for permissions, causing a storm of log writes. Others found no clear trigger—the file simply grew without bound.

Microsoft didn’t publicly acknowledge the bug until late May 2026, when a support article briefly mentioned it as a “known issue” in Windows 11 version 24H2. The June optional update is the first fix to ship. It’s unknown whether the same bug affects Windows 10, but given that the Capability Access Manager is also present there, it’s plausible. No corresponding Windows 10 patch has been announced yet.

What to Do Now

  1. Install the June 2026 optional update
    - Open Settings > Windows Update, then click “Check for updates.”
    - If the optional update appears (it may be listed as “2026-06 Cumulative Update Preview for Windows 11” or similar), install it and reboot.
    - If you don’t see it yet, your device might not be offered the preview right away. Check again over the next few days.

  2. Check if you’ve already been affected
    - Open File Explorer and navigate to C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\.
    Note: ProgramData is a hidden folder; you’ll need to enable “Hidden items” in the View menu or type the path directly into the address bar.
    - Look for CapabilityAccessManager.db-wal. Right‑click it, select Properties, and note its size.
    - If the file is more than, say, 1 GB, you’ve got a space‑hogger.

  3. Manually delete the bloated WAL file (safe, but with care)
    - Stop the Capability Access Manager service: open Command Prompt as Administrator and run
    net stop camsvc
    (You can also use sc stop camsvc if you prefer.)
    - Delete the file:
    del /f C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal
    - Restart the service:
    net start camsvc
    - The service will create a fresh, tiny WAL file automatically. No data or permissions settings are lost.
    - Warning: Always ensure the service is stopped before deleting; otherwise, you might trigger a database corruption. If you’re uneasy, simply install the update first—then check the file size again after a reboot. If it hasn’t shrunk, you can then perform the manual deletion.

  4. For enterprise admins: deploy via script
    - Use your management tool (SCCM, Intune, custom PS) to push the update, or run a remediation script that detects a WAL file larger than X GB, stops the service, deletes the file, and starts the service. Sample PowerShell one‑liner:
    powershell Stop-Service camsvc -Force; Remove-Item -Force "$env:ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal"; Start-Service camsvc
    - Test on a pilot group first. The script must run with SYSTEM privileges.

Outlook

The June fix will be rolled into the mandatory July 2026 Patch Tuesday update for all Windows 11 users who don’t install the preview. Once that arrives, the growth bug will be universally squashed. That still leaves the question of Windows 10: if you’re on an older version of the OS and see the same symptom, keep an eye on the Release Health Dashboard—Microsoft hasn’t yet indicated whether a backport is coming. In the meantime, the manual deletion workaround remains effective and safe.

For most users, this is a rare but high‑impact quirk in Windows’ privacy infrastructure. The quiet nature of the leak—no errors, no alerts—makes it particularly dangerous, reminding us that even the most invisible system files deserve a regular check‑in when disk space trends downward. With the patch in place, your SSD can breathe a little easier.