A Windows 11 bug eats up to 500GB of disk space. How to check and fix it

A system whose entire job is logging when an app asked for access to your camera, microphone, or location has managed to eat up to 500GB of drive space on Windows 11. Microsoft only confirmed the problem officially in early July, even though the bug shipped with an update from several months earlier. For anyone who spent that stretch manually deleting files or buying a bigger drive because their system kept getting tighter "for no reason," that confirmation landed way too late.

The culprit is a file called CapabilityAccessManager.db-wal, part of the camsvc service that logs when apps reach for privacy-sensitive resources. Instead of behaving like a normal log that gets compacted over time, the file started growing without limit after an update from February or March 2026. The result: hundreds of gigabytes taken up by a log file most users had never even heard of.

The file meant to keep track of your privacy turned out to be the biggest threat to your free disk space.

Where a half-terabyte file actually comes from

Capability Access Manager is a system service that handles something that sounds harmless enough: tracking which app asked for access to the camera, microphone, location, or other privacy-controlled resources, and when. Under normal conditions, that log stays small, since the database gets compacted regularly and old entries get cleared out. An update from around February or March 2026 broke exactly that compaction step. The write-ahead log file started growing endlessly instead of periodically cleaning itself up.

How bad it gets depends on how heavily a given machine runs apps that check privacy permissions. Some users reported just a few tens of gigabytes, but the worst-hit machines, especially ones that hadn't been restarted in a while or run a lot of camera- and microphone-hungry apps, crept up toward that half-terabyte ceiling. On plenty of laptops shipping with 512GB or 256GB drives, that's not a cosmetic annoyance in a storage settings panel, it's an actual functionality problem.

How to check if your machine is affected

Checking doesn't require any extra tools. Open File Explorer, paste C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\ into the address bar, and check the size of CapabilityAccessManager.db-wal. If it's a few megabytes, everything's working fine. If it's measured in gigabytes, let alone tens of gigabytes, the machine is hit, and it's worth acting before the file grows further.

This is one of those bugs that hides exactly where a regular user would never think to look. The ProgramData folder is hidden by default in a lot of File Explorer configurations, and the file name doesn't hint at anything specific. Without prior knowledge of the issue, the only warning sign tends to be a low disk space alert that's nearly impossible to trace back to any particular app or download.

The official fix, and a manual one if you're already out of space

Microsoft shipped an optional preview update, KB5095093, on June 23, 2026, for Windows 11 versions 24H2 and 25H2. The patch does two things: it fixes the write-ahead log's compaction logic so the file stops growing without limit, and it runs a one-time cleanup that automatically clears out an already-bloated log if one exists on the machine. For most people, that's the simplest and safest route, and the fix is expected to roll into the mandatory security update on Patch Tuesday, July 14, 2026, which is this week.

For anyone already critically low on space who can't wait for the update, there's also a manual way to remove the bloated file. It takes some care, since the camsvc service actively uses that file while it's running.

Another rough patch for Windows 11 update quality

This bug isn't showing up in a vacuum. Around the same time, Microsoft also had to own up to problems with update KB5094126, which pushed some business HP laptops into recovery mode, BitLocker recovery screens, or Secure Boot errors. A few weeks earlier, Dell was dealing with a wave of driver crashes tied to a SupportAssist update that hit, among others, XPS 15 9530 owners. None of these are directly connected to the CapabilityAccessManager bug, but together they add up to a pattern: Windows 11 update quality control has clearly been struggling through the first half of 2026, and users increasingly find out about serious bugs only after running into the consequences themselves.

That pattern, more than any single bug tied to one log file, is what should worry people most. When system updates keep breaking things that used to work fine, and official confirmation only shows up months after forum complaints start piling up, trust in the update process itself starts cracking faster than Microsoft can ship the next patch.

Privacy systems are what's wrecking trust in privacy

There's a bitter irony here that's hard to ignore. CapabilityAccessManager exists to give users control over who's reaching for their camera, microphone, and location. Instead of reinforcing that sense of control, a mechanism built specifically around privacy turned into a months-long, unreported failure. That fits into a broader, increasingly uncomfortable pattern around Windows 11's privacy-facing features. Security researchers have also spent months warning about Windows Recall, the feature that takes regular screenshots into a local archive, saying the safeguards around such sensitive data still don't match the scale of what the system actually collects. One comparison from security researchers landed harder than most: the vault door might be titanium, but the wall right next to it is still drywall.

CapabilityAccessManager and Recall are two different features solving two different problems, but they share the same underlying issue: Microsoft keeps building more mechanisms that collect data about user behavior in the name of transparency and security, while regularly failing at the basic maintenance those mechanisms need. For the average user, the gap between an accounting bug in a permissions log and a security hole in a screenshot archive keeps shrinking, once both trace back to the same lack of quality control.

SPAWNSY verdict