A newly acknowledged Windows 11 issue can cause some PCs to lose a startling amount of free space to a system database file. According to reporting from Windows Latest, Microsoft has added a note to its Windows 11 update documentation indicating that disk space usage for the CapabilityAccessManager.db-wal file is being improved, with the fix expected to be included in the July 14, 2026 Patch Tuesday release.
For IT teams, help desk staff, and power users, the important point is not just that a bug exists. It is that the symptoms can look like ordinary Windows storage growth: the C: drive fills up, Settings reports large “System & reserved” usage, and the actual culprit may not be obvious unless you inspect the file system with administrative tools.
What is going wrong
The file involved is CapabilityAccessManager.db-wal, located under C:\ProgramData\Microsoft\Windows\CapabilityAccessManager. Capability Access Manager is tied to Windows privacy and permission controls, including access to sensitive capabilities such as camera, microphone, location, and screen capture. In normal circumstances, this related database logging should be small.
The problem reported by Windows Latest is that the CapabilityAccessManager.db-wal file can grow far beyond a reasonable size. Examples cited include systems where the file reached tens or hundreds of gigabytes, and in one case more than 500GB. That makes this more than a cosmetic storage reporting issue: on smaller SSDs, it could consume the majority of available space and affect updates, application installs, temporary files, virtual machines, and general system stability.
A distinctive warning sign is a large System & reserved number in Windows Settings without an obvious explanation from hibernation, pagefile size, installed apps, or user data. In other words, this is a privacy-permission database log behaving like a disk-space leak.
How to check whether your device is affected
Start with the built-in view: open Settings, go to Storage, and check the System & reserved section. If that section is unexpectedly large, continue with a more targeted check. Windows may not identify CapabilityAccessManager.db-wal directly in the Settings app, so you need to inspect the folder or use a disk-usage tool.
For a GUI approach, run a storage analyzer such as TreeSize, WizTree, or WinDirStat as administrator, then sort by size and look under C:\ProgramData\Microsoft\Windows\CapabilityAccessManager. The key file name to look for is CapabilityAccessManager.db-wal.
For a command-line approach, Windows Latest suggests using an elevated Command Prompt and a read-only robocopy listing. The intent is to check the file size without taking ownership or changing permissions. Administrators can adapt this command:
cmd
robocopy "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" "%TEMP%\CAMCheck" /L /B /R:0 /W:0 /BYTES /NP
Look for CapabilityAccessManager.db-wal in the output. A size of a few megabytes is not concerning. A size measured in many gigabytes, especially if it continues increasing, is a sign that the device may be affected.
What IT admins should do now
First, avoid panic cleanup. This file is in a protected Windows system location for a reason, and bulk-deleting system files to recover space can introduce secondary problems. If the affected machine still has enough free space to operate, the lowest-risk path is to monitor it and deploy the upcoming Patch Tuesday update as soon as it is available and validated for your environment.
Second, add this check to your troubleshooting workflow for unexplained low-disk incidents on Windows 11. Many support teams already look for large user profiles, Teams or browser caches, Windows.old folders, hibernation, and oversized pagefiles. Until the fix is broadly installed, CapabilityAccessManager.db-wal should be on that same shortlist.
Third, consider proactive checks on machines with smaller system drives, shared workstations, kiosk devices, developer PCs, and virtual desktops. Those systems are more likely to experience user-visible impact when a system file grows unexpectedly. If you manage endpoints with scripts or RMM tooling, a simple inventory of the file size can help identify outliers before tickets start arriving.
Should you rename or delete the file?
Windows Latest notes that renaming the file may allow Windows to regenerate it, but also cautions against deleting system files. For managed environments, any workaround should be tested on a non-critical device first and documented carefully. If a machine is critically low on disk space and cannot wait for the update, escalation to a senior administrator is sensible before changing files in ProgramData\Microsoft\Windows.
For home users, the practical advice is simpler: check the size, make sure you have recent backups, and install the July 2026 cumulative update when it arrives. If you are not severely affected, waiting for the Microsoft fix is safer than experimenting with protected system files.
Bottom line
This issue is a reminder that “System & reserved” storage is not always self-explanatory. A Windows 11 PC can appear to be losing space for no obvious reason while a single behind-the-scenes database log is responsible. The fix is expected through the normal Windows update channel, but users and admins should verify affected systems now so they can avoid failed updates, full disks, and unnecessary hardware troubleshooting.
Source: Windows Latest source