Windows 11 Storage Suddenly Full? A Microsoft Bug May Be Eating Hundreds of GB

Windows 11 storage settings showing a nearly full drive with a bug and warning symbol representing unexpected storage usage


If your C drive is somehow full and you have no idea why, stop blaming your own downloads folder. Microsoft just confirmed a real bug, hiding in a protected system folder, that's been quietly swallowing up to 500GB on some PCs — and most people who have it have absolutely no idea.

Here's the number that should get your attention: 513GB. That's how much storage one single hidden file ate on a Reddit user's PC, according to reports collected by Windows Latest. Not a stray movie folder. Not forgotten game installs. One file, sitting in a protected system directory you were never supposed to look inside, quietly growing until it nearly filled an entire SSD. If your Windows 11 PC has been nagging you about low disk space and you genuinely can't account for it, this might be your answer. Let's get into exactly what's happening, how to check if you're affected, and what to actually do about it.

The File Nobody Was Supposed to Notice

The culprit has a name that sounds boring on purpose: CapabilityAccessManager.db-wal. It lives inside C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\, a folder that Windows actively protects, meaning File Explorer or a normal Command Prompt window will often just throw you an "Access denied" message if you try to poke around in there directly. The Capability Access Manager itself is a real, useful part of Windows. It's the system responsible for managing app permissions — the stuff that controls which apps get to use your camera, your microphone, your location, your contacts, or your screen. 

Every time an app asks for one of those permissions, this service is quietly logging it. The "db-wal" part stands for write-ahead log, a fairly standard database technique where changes get temporarily written to a log file before being folded back into the main database. Under completely normal circumstances, this file should be a few megabytes. Tiny. Forgettable. On affected PCs, it isn't tiny at all. Reports gathered from user forums and Microsoft's own Feedback Hub describe this file ballooning to 70GB, 110GB, 200GB, and in the worst documented case, that 513GB figure. Some users have reported the file returning to a normal few gigabytes after cleanup, only to start creeping back up again over time.

How Long Has This Actually Been Happening?

Longer than you'd expect from something Microsoft is only now addressing. Windows Latest, the outlet that first traced this bug back to its actual cause, says users and Windows Insiders had been flagging storage problems tied to this exact file for months, with some reports dating back roughly a year. Investigators believe the underlying issue was introduced by a Windows update sometime around February or March of 2026. For most of that time, Microsoft said essentially nothing. 

There was no official acknowledgment, no entry on the Windows Known Issues Dashboard, and no explanation connecting user complaints about mysteriously full drives to this specific file. That changed, quietly, on June 29, 2026. Microsoft updated the changelog for an optional Windows 11 update with a single understated line: this update improves disk space usage for the CapabilityAccessManager.db-wal file. 

No mention of how large the file could grow. No explanation of why it happened in the first place. Just a brief, easy-to-miss note buried among a list of unrelated fixes for things like Secure Boot certificates and the emoji panel.

How to Actually Check If You're Affected

The good news is you don't need to be technical to get a first read on whether this is your problem. Open Settings, then System, then Storage, then click "Show more categories." Look specifically at the category labeled System & reserved, and within it, System files. If that number is sitting at a normal handful of gigabytes, you're probably fine. If it's showing 100GB, 200GB, or anywhere close to 500GB, this bug is very likely your explanation, especially if you can't otherwise account for that much space through your own apps and downloads. 

 For a more precise check, there's a safe, read-only command you can run. Open an elevated Command Prompt — right-click the Start button and choose "Terminal (Admin)" or search for Command Prompt, right-click it, and choose "Run as administrator." Then paste in the following: robocopy "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" "%TEMP%\CAMCheck" /L /B /R:0 /W:0 /BYTES /NP This command only lists file details. 

It does not copy, move, or delete anything on your system, which makes it safe to run even if you're not entirely sure what you're doing. Look through the output for CapabilityAccessManager.db-wal specifically. A file measuring a few megabytes is normal and expected. A file measuring several gigabytes or more, especially one that keeps climbing every time you check, is the sign you're looking for. If you'd rather use a visual tool instead of the command line, apps like TreeSize, WinDirStat, or WizTree can also help you spot the oversized file among your system storage, without needing to type anything into a terminal at all.

The Fix, and Why You Shouldn't Just Delete the File Yourself

Microsoft has already shipped a fix, and it's rolling out in two stages. The first stage is already available right now, through optional update KB5095093, covering builds 26200.8737 and 26100.8737. You can grab it manually by going to Windows Update, then Advanced options, then Optional updates, and installing it from there. 

If you'd rather not manually chase down an optional update, the same fix is expected to arrive automatically for everyone through the July 2026 Patch Tuesday cumulative update, which rolls out broadly to all Windows 11 users without requiring you to do anything extra. Here's the part worth taking seriously: don't just go delete the oversized file yourself through File Explorer, even if you manage to get past the access restrictions. 

Multiple outlets covering this bug have specifically warned that clumsily deleting the wrong file in that folder, or removing it incorrectly while Windows is actively using it, can break your PC's Wi-Fi connectivity. That's a genuinely bad trade for some freed-up disk space. If your drive is already so full that Windows Update itself can't install properly, there is a recovery workaround: renaming the oversized file from Windows Recovery Environment or Safe Mode, which allows Windows to safely regenerate a fresh, properly-sized WAL file in its place. But for the vast majority of people reading this, the simplest and safest path is just installing the update and letting Microsoft's own fix handle the cleanup properly.

Why This Is Genuinely Frustrating, Beyond the Storage Itself

Setting aside the technical fix, there's a fair criticism here worth sitting with. This wasn't a fringe, one-in-a-million bug. It affected a broad enough range of PCs, over a long enough stretch of time, that user reports piled up across Reddit, Microsoft's own Feedback Hub, and multiple tech outlets independently. 

Yet it took roughly a year from the first user complaints to an actual, if extremely terse, acknowledgment buried in a changelog most people will never read. Microsoft still hasn't published a proper explanation of why the bug happened, why some systems were affected far worse than others depending on which apps they used, or listed it clearly as a known issue anywhere prominent. For a bug capable of silently filling an entire hard drive, that's a strangely quiet response. 

 The practical upshot for you, right now, is simple even if the backstory isn't: check your storage settings today, and if that System & reserved number looks abnormally large, get the update installed rather than assuming your PC just needs a factory reset or a bigger drive.

Also read: Samsung Z Fold 8 Pre Reservation begins ahead of July 22nd Release

Popular posts from this blog

Don't Ignore This Green Camera Icon on Android — It Could Reveal Hidden App Activity

Image
There's a tiny green dot that's been sitting in your status bar for years, quietly keeping a diary of every app that's touched your camera or microphone. Most people have seen it a thousand times and tapped it exactly zero. It shows up, it disappears, and the instinct is to ignore it the same way you ignore a notification badge you already know about. That instinct is costing you information. This one little chip in the corner of your screen is one of the few genuinely reliable, built-in tools Android gives you for catching an app doing something it has no business doing — and almost nobody actually uses it the way it's meant to be used. What This Dot Actually Is Google introduced this feature back in Android 12, and it works exactly like a small status light. The moment any app — a system app or one you installed yourself — starts accessing your camera or microphone, a green chip appears in the top-right corner of your screen showing a small icon. After a few...
Read more

iPhone 17 Price Hike Rumors: Here's Why Prices Could Go Up

Image
There's a specific kind of headline that makes your stomach drop a little if you bought your iPhone 17 thinking the conversation around its price was over. Because it might not be. Despite the iPhone 17 lineup launching at the same prices as the iPhone 16 last September, there's growing chatter that those numbers could move — and not in the direction anyone wants. This isn't some YouTuber's wild theory either. It's coming from Tim Cook himself. Tim Cook Said the Word "Unavoidable" Last week, Cook sat down with The Wall Street Journal and said something Apple almost never says out loud: that price increases are coming, and Apple can no longer absorb the cost itself. The reason is memory chips. Not iPhone chips specifically — the actual RAM and storage components that go inside every modern device, from your laptop to the servers running AI tools. AI companies are buying memory at a pace nobody planned for, building data centers as fast as factor...
Read more

ChatGPT Image Generation Failed— Here's What's Happening and What Actually Works

Image
You're not imagining it. You didn't break anything. ChatGPT's image generation is failing for thousands of users today — including me. Here's the full picture. I sat down this morning to generate a few images in ChatGPT. Typed the prompt. Hit enter. Watched the little spinner go around and around. And then — nothing. Just a blank response or an error. Tried again. Same result. Cleared the cache. Logged out. Logged back in. Opened a new chat. Still nothing. If that sounds familiar, you're in a very large crowd right now. ChatGPT's image generation is broken for a significant number of users today, July 7, 2026. More than 100 complaints have already been filed on Downdetector.in from India alone in the last few hours. Reports are coming in from across the world. The pattern is consistent everywhere: image generation requests are either failing silently — the chat just stops and produces nothing — or taking so long that they time out before anything appears...
Read more