Microsoft shipped an optional cumulative update for Windows 11 on June 23, 2026, that squashes a storage-sucking bug many users didn’t even know was running. The preview update, tagged KB5095093, puts a hard stop on a single database log file that, left unchecked, could silently balloon from a few kilobytes to tens of gigabytes, eating precious SSD space with no warning.

If you’ve ever stared at vanishing free space and couldn’t figure out where it went, this update may finally give you an answer—and a way to reclaim those lost gigabytes.

What Actually Changed

KB5095093 is a non-security preview update, the kind Microsoft releases in the last week of a month to test fixes before the next Patch Tuesday. The headliner in this release is a correction aimed squarely at one file: CapabilityAccessManager.db-wal.

That’s the write-ahead log associated with Windows 11’s Capability Access Manager, an internal service that governs how apps request and use sensitive capabilities like your camera, microphone, and location. Under the hood, Windows uses a SQLite database to track these permissions. Like any SQLite database, it spins off a WAL file to store pending changes before they’re committed to the main database.

Normally, after those writes are flushed, the WAL file shrinks back to size. But in certain builds of Windows 11, the checkpointing process that should trim the log failed to run reliably. The result: CapabilityAccessManager.db-wal grew without bound, sometimes swelling past 50 GB, with users on Reddit and Microsoft’s own forums reporting 80 GB or more occupied by this one hidden file.

The update forces the database engine to properly checkpoint, limit the WAL file growth, and, based on early reports, clean up some of the accumulated bloat after a reboot.

Build numbers were bumped to 22621.4219 and 22631.4219 for the standard and feature-enabled branches, respectively—important if you’re checking your winver dialog.

What It Means for You

For Everyday Windows 11 Users

If your PC seems to lose free space faster than your usage habits explain, this bug could be the culprit. The file sits deep in the system directory tree, usually under C:\ProgramData\Microsoft\Windows\AppRepository\. Most disk cleanup tools (including Windows’ own Storage Sense) won’t spot it because they’re not scanning inside the AppRepository folder. You’d need a tool like WinDirStat or WizTree to manually hunt down the space hog.

One user on WindowsForum.com recounted discovering a 37 GB CapabilityAccessManager.db-wal file after weeks of assuming their 256 GB SSD was simply “getting old.” After installing KB5095093 and rebooting, the file shrank to just 8 MB. Another user reported a 62 GB file that prevented Windows Update from downloading other patches due to insufficient disk space—a vicious cycle that the preview update now breaks.

For Power Users and Gamers

Gamers with smaller boot drives have been hit especially hard. Modern game installations already push SSDs to their limits; losing 50 GB to a single log file can mean the difference between having one more AAA title installed or constantly juggling free space. If you’ve been removing games or clearing browser caches to make room, it’s worth checking if this invisible file is the real thief.

For System Administrators

If you manage dozens or hundreds of Windows 11 machines, this bug may have already caused a spike in helpdesk tickets about “unexplained low disk space.” On machines with 128 GB or smaller drives—common in thin clients, kiosks, and older laptops—the WAL file can push the disk to 100% capacity, causing slowdowns, failed updates, and even boot failures.

The fix arrives as an optional preview, so you must actively deploy it. But given the severity, many admins will want to push it ahead of the July 2026 Patch Tuesday. The update does not require a feature update, so it’s a straightforward cumulative installation. Bulk deployment scripts can use the Windows Update Agent API or simply side-load the MSU from the Microsoft Update Catalog.

How We Got Here

A Brief History of the Capability Access Manager and SQLite in Windows

The Capability Access Manager isn’t new; it’s been part of Windows since the initial release of Windows 11. It’s the service that shows those privacy dot indicators and manages consent prompts for sensitive hardware. Microsoft switched to a SQLite backend for the permissions store around the time Windows 11 23H2 shipped, aiming for faster queries and lighter runtime overhead compared to the old Registry-based system.

The SQLite implementation, however, shipped with a default configuration that wasn’t aggressive enough about WAL file maintenance. Under normal circumstances, SQLite performs automatic checkpoints when the WAL file reaches a threshold (usually 1000 pages, or 4 MB). But the Capability Access Manager database experiences a high volume of tiny writes—every time an app accesses a protected capability or a consent dialog is approved—which can outpace the default checkpoint interval. If those writes pile up faster than the checkpoint can run, the WAL file just keeps ballooning.

The Technical Underpinnings: Why WAL Files Grow Unchecked

SQLite’s write-ahead log is a powerful feature: instead of blocking all reads while writes occur, the database logs changes to a separate file and later merges them back (a process called checkpointing). For most apps, the default checkpoint behavior, running either when the WAL file hits 4 MB or on a timeout, works fine. But the Capability Access Manager is peculiar in two ways: it has many concurrent short-lived connections, and those connections perform frequent, small insertions. In such a scenario, SQLite can bypass auto‑checkpoint entirely if connections don’t reach the page threshold before closing. Over months of uptime, the file just accumulates.

Compounding the problem, the database itself is locked by the system process while Windows is running, so even an admin can’t simply delete the WAL file without risking database corruption. Some workarounds involved booting into safe mode or a recovery environment to remove the file, but those are not officially supported and can break the capability store, forcing apps to re-prompt for permissions.

Community Discovery and Microsoft’s Response

The bug first surfaced in user forums in early 2026, with threads titled “Where is my disk space going?” and “Mysterious huge file in AppRepository.” Users on WindowsForum.com and Reddit traced the culprit to CapabilityAccessManager.db-wal. The Feedback Hub item quickly gained thousands of upvotes, catching the attention of Windows engineers. In April 2026, a Microsoft engineer commented on the Feedback Hub that a fix was in development and would arrive in “an upcoming monthly quality update.” By late June, it materialized as part of KB5095093.

What to Do Now

If you’re already seeing alarming free‑space drops, here’s a step‑by‑step guide to check, fix, and verify.

1. Diagnose the Problem

Open a PowerShell window as Administrator and run:

Get-ChildItem -Path "$env:ProgramData\Microsoft\Windows\AppRepository\CapabilityAccessManager.db-wal" -Force -ErrorAction SilentlyContinue | Select Name, Length

If the file exists and its length is larger than a few hundred megabytes, you’re likely impacted. A normal, healthy size is under 10 MB.

2. Install the Update

  • Go to Settings > Windows Update.
  • Click Check for updates.
  • Look for 2026-06 Cumulative Update Preview for Windows 11 Version 23H2 (KB5095093) and click Download & install.
  • Reboot when prompted.

After the reboot, re-run the PowerShell command to see if the file size has decreased. It may not drop immediately if the checkpoint cleanup defers to idle time. Let the machine sit for 10–15 minutes and check again.

3. If Space is Still Critically Low

If you can’t wait for the cleanup and you’re technically comfortable, you can attempt a manual fix—but proceed with caution. This involves stopping the Capability Access Manager service, backing up the database, and removing the WAL file. Microsoft hasn’t officially endorsed this yet, but numerous users on WindowsForum.com confirm it works without breaking app permissions:

  • Open Services.msc, stop Capability Access Manager Service.
  • In File Explorer, navigate to C:\ProgramData\Microsoft\Windows\AppRepository\.
  • Take ownership of the folder if necessary (this requires admin rights and bypassing TrustedInstaller).
  • Copy the entire folder to a backup location.
  • Delete only the CapabilityAccessManager.db-wal file.
  • Restart the service.
  • Reboot.

A safer, if slower, route is to wait for the service to naturally rebuild the WAL file after the update cleans it up. For machines that are already at the disk‑full precipice, booting into Windows Recovery Environment and using Disk Cleanup to remove Windows Update leftovers can free enough temporary space to install the fix.

4. For Enterprise Environments

Use PowerShell to check WAL file size across your fleet:

Invoke-Command -ComputerName (Get-ADComputer -Filter {OperatingSystem -like "*Windows 11*"}).Name -ScriptBlock {
    $path = "C:\ProgramData\Microsoft\Windows\AppRepository\CapabilityAccessManager.db-wal"
    if (Test-Path $path) { 
        $size = (Get-Item $path -Force).Length / 1GB
        [PSCustomObject]@{Computer=$env:COMPUTERNAME; SizeGB=$size}
    }
} | Export-Csv -Path "\\server\share\WALSizeReport.csv"

Import KB5095093 into WSUS or approve it in Intune for pilot groups. Schedule wider deployment once you verify the fix doesn’t introduce regressions—none have been reported so far in this preview.

Outlook

The June 2026 preview update marks the end of a frustrating chapter for Windows 11 users who felt their storage was disappearing into a black hole. But it also highlights a broader challenge: as Windows adopts more SQLite backends—for not just permissions but also modern app deployment, diagnostics, and more—small configuration oversights can snowball into serious system issues. Microsoft will likely audit other database-using components to prevent similar leaks.

The fix will hit the mandatory cumulative channel on July 14, 2026, so even users who shy away from optional updates will be protected soon. In the meantime, if your PC has seemed sluggish or kept nagging you about low storage, take five minutes to install this update. That mysterious chunk of missing disk space might finally reappear.