On June 23, 2026, Microsoft released an optional cumulative update for Windows 11 that directly addresses a storage bug known to consume gigabytes of space on the system drive, often without users realizing it. The update, KB5095093, stops an obscure system log file called CapabilityAccessManager.db-wal from growing uncontrollably, a fix that will ultimately be rolled into July’s mandatory Patch Tuesday release.

The Culprit: A Database Log That Wouldn’t Stop Growing

The file at the center of the issue is CapabilityAccessManager.db-wal, a write-ahead log stored in %ProgramData%\\Microsoft\\Windows\\CapabilityAccessManager. It belongs to the Capability Access Manager service (camsvc), a core Windows component that manages privacy consent prompts for apps trying to access your camera, microphone, location, and other sensitive hardware.

Normally, the .db-wal file acts as a temporary journal for SQLite database transactions. It’s designed to be compact—typically a few megabytes—and periodically merged into the main database. On affected systems, however, this file balloons to tens of gigabytes. Some users reported seeing their C drive shrink from 50 GB free to single digits in a matter of weeks, with the log file alone hogging 30 GB or more.

Microsoft’s advisory for KB5095093 acknowledges “abnormal disk usage” caused by this file, confirming what affected users had been shouting about on forums, Reddit, and a community-run GitHub repository for months. The bug does not cause data loss or system crashes, but it can silently strangle storage, triggering low-disk-space warnings and slowing down the PC as the drive nears capacity.

How the June 2026 Optional Update Fixes It

The KB5095093 preview cumulative update corrects the underlying logic that causes the .db-wal file to grow unchecked. Essentially, the service was not properly truncating the log after database checkpoints, leaving orphaned data that snowballed over time. With the patch, the service now manages the file size correctly, automatically cleaning up excess bloat after installation.

Importantly, the update also includes a one-time cleanup routine that removes the existing oversized file on reboot. This means that once you install KB5095093 and restart your PC, the lost gigabytes should immediately reappear in File Explorer. The update applies to all currently serviced versions of Windows 11 (23H2 and 24H2) and is distributed through Windows Update as an optional quality preview. It will be superseded by the July 8, 2026 Patch Tuesday update, which will make the fix mandatory for all users.

What This Means for Home Users and Admins

For the typical home user who has been scratching their head over a mysteriously full C drive, this fix is a quiet hero. After installing KB5095093, you don’t need to do anything else—the file will shrink on its own. To verify, you can navigate to the CapabilityAccessManager folder and check the size of CapabilityAccessManager.db-wal. If it’s still showing a large number right after the update, a subsequent reboot should trigger the cleanup.

If you’re cautious about installing preview updates, you can manually tame the file while waiting for Patch Tuesday. Stop the Capability Access Manager service, delete or rename the .db-wal file, and restart the service. Here’s a quick PowerShell method run as administrator:

Stop-Service camsvc
Remove-Item -Path \"$env:ProgramData\\Microsoft\\Windows\\CapabilityAccessManager\\CapabilityAccessManager.db-wal\" -Force
Start-Service camsvc

This won’t prevent the bug from reoccurring, but it will give you back your space temporarily. The permanent fix is, of course, the update.

For IT professionals managing fleets, KB5095093 should be tested in your pre-production environment before broader deployment, especially if your organization relies on apps that use microphone or camera access. While Microsoft hasn’t reported any regressions, it’s always wise to validate. Once the July Patch Tuesday update drops, the fix will be included automatically in your monthly rollup, making it easier to deploy through your regular update channels. However, if you have users complaining of low disk space now, pulling in this optional update via WSUS or Intune can provide immediate relief.

How We Got Here

The CapabilityAccessManager service has a history of both praise and pain. Introduced in Windows 10 to give users granular control over privacy-sensitive hardware, it has occasionally been tied to performance and storage quirks. The .db-wal file specifically started drawing community attention in late 2025, when users on the Microsoft Answers forum and Reddit’s r/Windows11 began posting screenshots of a mysterious 20 GB file eating their SSDs. A GitHub repository was soon created to track the issue, collecting hundreds of “me too” confirmations and diagnostic logs.

Microsoft remained silent for months, even as third-party tools like TreeSize and WizTree helped users pinpoint the culprit. The breakthrough came with the June 2026 optional update, where the release notes for KB5095093 finally admitted the problem and detailed the fix. While a fix in a preview update isn’t a full public rollout, it’s a strong signal that the company is treating the bug seriously and expects the patch to be stable enough for widespread adoption in July.

This isn’t the first time a write-ahead log has caused storage headaches. SQLite databases are used extensively across Windows, and similar bloat bugs have hit Edge, Cortana, and even the Windows Search indexer. Each time, the remedy involves better checkpoint management—exactly what KB5095093 delivers.

What to Do Now

If your C drive is running out of space and you’re on Windows 11, here’s your playbook:

  1. Check if you’re affected: Open File Explorer, paste %ProgramData%\\Microsoft\\Windows\\CapabilityAccessManager into the address bar, and note the size of CapabilityAccessManager.db-wal. If it’s larger than a few hundred megabytes, the bug has hit you.
  2. Install the optional update: Go to Settings > Windows Update, click Check for updates, and then select Download and install under the optional update section. Look for 2026-06 Cumulative Update Preview for Windows 11 (KB5095093).
  3. Restart your PC: After installation, reboot. The cleanup runs during shutdown or startup.
  4. If you can’t update yet: Use the manual cleanup commands above as a stopgap. Just be aware that the service needs to be stopped before the file can be deleted, and the problem may return within days or weeks.
  5. Monitor your disk: Even after fixing, keep an eye on the folder for a while. Third-party disk analyzers like WinDirStat can help spot regressions early.

For teams managing multiple workstations, consider pushing the following PowerShell script through your RMM tool to identify affected machines:

$path = \"$env:ProgramData\\Microsoft\\Windows\\CapabilityAccessManager\\CapabilityAccessManager.db-wal\"
if (Test-Path $path) {
    $sizeGB = [math]::Round((Get-Item $path).Length / 1GB, 2)
    if ($sizeGB -gt 1) { Write-Output \"Affected: $sizeGB GB\" } else { Write-Output \"Not affected\" }
} else { Write-Output \"File not found\" }

No one likes chasing disk space gremlins, but this one at least has a clear fix and a short runway to full deployment.

Outlook

July 8, 2026, will bring the same fix to all Windows 11 users via the monthly security update. Once that day comes, the CapabilityAccessManager.db-wal saga should be mostly behind us. Microsoft has not indicated whether a similar patch is planned for Windows 10 (which still has nearly a year of support), but given the service’s presence on that platform, it may eventually get backported if demand is high.

The episode underscores the value of Microsoft’s optional preview updates as an early warning and early relief valve. Power users and proactive admins who adopt these updates can fix problems before they become widespread headaches. For everyone else, keeping storage monitoring tools handy and checking the CapabilityAccessManager folder occasionally is a small habit that can save big headaches.