Microsoft released a cumulative update on July 14, 2026, that stops a privacy-service log file from silently consuming hundreds of gigabytes of disk space. The same update may return that space automatically — but many users will need to take a few extra steps to reclaim every megabyte.

What Actually Happened: A Database Log That Forgot to Shrink

The file at the center of this is CapabilityAccessManager.db‑wal. It normally lives quietly inside C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\ and should be tiny — a few kilobytes or, at most, a handful of megabytes. It is a write‑ahead log (WAL) for an SQLite database that Windows uses to track which apps can access your camera, microphone, location, contacts, and other protected capabilities.

Under healthy conditions, the WAL log works like this:
1. An app requests permission to use, say, your location.
2. Windows records the permission check in the WAL file.
3. Periodically, Windows “checkpoints” — it flushes those pending changes into the main database.
4. The WAL is then truncated or reused, so its size stays tiny.

On affected Windows 11 machines, step 3 stopped happening reliably. New transactions kept streaming into the log, but the checkpoint process either never ran or failed to clean up afterward. The result: CapabilityAccessManager.db‑wal grew without bound, often by hundreds of megabytes per day.

Reports collected by Windows Latest and Research Snipers document real‑world sizes from 120 GB to 332 GB, with one extreme case approaching 500 GB. On a laptop with a 512 GB SSD, a 500 GB log file leaves almost no room for anything else — and Windows’ built‑in storage tools rarely pointed the finger at this shadowy system file.

Why Your Storage Settings Didn’t Show the Culprit

Windows Storage settings group system files into broad categories like “System & reserved” or “Other.” A gigantic WAL log would simply inflate those categories without being named. Disk Cleanup and Storage Sense don’t target active database logs, so they were useless. Users often deleted downloads, emptied the recycle bin, and uninstalled programs — only to see their free space keep shrinking because the real problem sat hidden in a protected system folder.

The bug is a storage leak, not a memory leak. Your RAM usage stays normal; it’s your SSD that fills up. That distinction matters because the symptoms look different: Windows Update failures, apps crashing when they can’t write temp files, slow logons, and OneDrive sync errors — all because the drive has zero breathing room.

Is Your PC Affected? How to Check

Before you do anything, install the July 2026 update. After that, you can quickly inspect the file’s size without digging through protected folders blindly.

  1. Right‑click the Start button and choose Terminal (Admin).
  2. Run this command to see the file size in gigabytes:
Get-Item “C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal” -Force |
Select-Object FullName, Length, @{Name=“SizeGB”;Expression={[Math]::Round($_.Length / 1GB, 2)}}

If the file is a few kilobytes or even a few megabytes, you’re fine. If it’s multiple gigabytes, you’ve found your storage leak. A file that doesn’t exist at all is also normal — SQLite creates and destroys WAL files as needed.

If the file is enormous, proceed to the recovery steps below. But first, make sure the update is truly installed.

The Fix: KB5101650 and What It Actually Does

The July 14, 2026, cumulative update KB5101650 is available for Windows 11 version 24H2 (build 26100.8875) and version 25H2 (build 26200.8875). It was also included in the optional June 23 preview update, KB5095093, so if you installed that, you already have the fix.

The update repairs the checkpoint logic. After installation, Windows should start properly maintaining the WAL file again. For many users, the log will shrink on its own — often dropping from hundreds of gigabytes to just a few megabytes — after the next restart and a few minutes of normal activity. However, Microsoft warns that the space may not be freed instantly; the database needs to run its maintenance cycle first.

Important Dell note: Shortly after release, Microsoft temporarily blocked KB5101650 on some Dell systems due to reports of shutdowns, overheating, and battery drain. If your Dell isn’t offering this update, that’s likely why. An out‑of‑band fix, KB5121767, was issued for those devices. Let Windows Update choose the right package rather than forcing a specific KB.

Step‑by‑Step: Recover Your Lost Storage Safely

If the update alone doesn’t shrink the file, you may need to delete the oversized WAL manually. But doing so while Windows is running can disrupt active permission checks and has been known to cause Wi‑Fi problems or missing app permissions. The safest route is to work in Safe Mode.

Prerequisite: Back up any critical files first. A drive that’s nearly full is unstable; don’t risk data loss.

  1. Ensure the update is installed. Check Settings > Windows Update > Update history for KB5101650 or a newer cumulative update.
  2. Restart your PC normally and wait a few minutes after sign‑in. Check the file size again. If it’s already tiny, you’re done.
  3. If the file remains huge, enter Safe Mode:
    - Go to Settings > System > Recovery.
    - Under Advanced startup, click Restart now.
    - Choose Troubleshoot > Advanced options > Startup Settings > Restart.
    - Press 4 or F4 for Enable Safe Mode.
  4. Sign in with an administrator account.
  5. Open Command Prompt as administrator and verify the file:
    dir “C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal” /a
  6. Delete only the WAL file:
    del “C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal”
    Do not delete the entire folder or the main .db file.
  7. Restart normally. Windows will recreate a fresh, small WAL as needed.

After restarting, verify that your camera, microphone, location‑based apps, and Wi‑Fi work as expected. The small, recreated WAL is completely normal.

If your C: drive is so full that the update cannot download, you must first free a few gigabytes by deleting temporary files, unused apps, or moving personal files to an external drive before installing the fix.

What This Means for You

For home users: This bug may explain why your laptop felt like it had mysteriously lost half its capacity. The fix can return more usable space than any cleanup tool you’ve tried. Once patched, check the file once; if it’s small, forget about it. If you run location‑heavy software (weather widgets, Wi‑Fi optimizers, presence detection), know that the patch protects your drive, but those apps may still be noisy — a topic for another day.

For IT administrators: You’ve just gained a new monitoring item. A PowerShell script (shared in many reports) can query the size of this file across your fleet. In one documented environment, more than half of 10,000 endpoints had an oversized log. Prioritize machines where the file is growing rapidly or where the system volume is nearly full. Before mass‑deleting, push the cumulative update and a reboot; many will recover automatically. Correlate large logs with installed software — Dell SmartByte and some desktop customization tools have been implicated in generating excessive capability requests.

How We Got Here: A Timeline of the Silent Storage Leak

Reports of ballooning CapabilityAccessManager.db‑wal files have circulated since at least 2024, with users describing 120 GB logs on Microsoft’s own support forums. The issue intensified through 2025 and into 2026, likely worsened by applications that poll location or other capabilities aggressively. Microsoft acknowledged the problem internally around May 2026, according to internal support logs cited by Windows Latest, but never publicly communicated the bug.

The first public fix arrived in the optional June 23, 2026, preview update (KB5095093). It became mandatory for all users on versions 24H2 and 25H2 with the July 14 Patch Tuesday release, KB5101650. A subsequent Dell‑specific hold and out‑of‑band update KB5121767 followed quickly, highlighting the tight coupling between Windows servicing and OEM hardware.

The Bigger Picture: Privacy, Polling, and Future Safeguards

This episode exposes a blind spot in Windows’ storage diagnostics. A single system file can devour half a terabyte, and Storage settings won’t even name it. Microsoft should consider adding checks for abnormally large service databases to Storage recommendations, and perhaps offer a one‑click repair from Settings.

The root cause, however, is twofold: a Windows maintenance bug and apps that generate excessive capability requests. Even with the fix, overly chatty software can still burn CPU, battery, and disk I/O. Vendors — and Microsoft itself — should audit how often their apps query location and other protected resources. Efficient privacy enforcement shouldn’t require constant database writes.

For now, installing the July 2026 update is the critical step. It stops the log from growing, and for most people, that’s the end of the story. The days of losing half your SSD to a hidden database log are, hopefully, over.