500GB Windows 11 Storage Bug Forces a Microsoft Fix

How did a default Windows 11 storage bug let a permissions-related system file grow to reported sizes as high as 500GB before most users had a clear way to identify it?

Microsoft has shipped a fix in the optional June 2026 update, KB5095093, which “improves disk space usage for the CapabilityAccessManager.db-wal file,” according to The Verge. The narrow fix matters. The bigger signal is uglier: a quiet Windows file tied to app permissions became a storage sink that some users only discovered after gigabytes had already vanished.

How did a default Windows 11 permissions file become a 500GB storage problem?

The file at the center of this is CapabilityAccessManager.db-wal, installed by default on Windows 11 PCs. It is linked to app permissions, the layer Windows uses for privacy-sensitive access such as location, camera, microphone, contacts, and screen capture, according to the supplied Windows Latest and TechSpot material.

That makes the bug awkward. This isn’t a random cache from a third-party app. It sits inside a Microsoft-controlled system area tied to permission tracking. A component designed to help Windows manage sensitive access became, for some users, the thing quietly eating the drive.

Microsoft says KB5095093 “improves disk space usage for the CapabilityAccessManager.db-wal file.”

The phrasing is careful. Microsoft has not published a full explanation of what failed, according to the supplied source material. The company’s public note confirms an improvement, not a postmortem.

XOOMAR analysis: this is why the issue lands differently from a routine cleanup bug. Users can tolerate some hidden system overhead. They’re less forgiving when a protected Windows file grows into the tens or hundreds of gigabytes and the Settings app does not clearly name the culprit.

We covered the storage side of this earlier in 500GB Windows 11 Storage Bug Eats SSD Space in Secret. The new piece is that Microsoft has now tied a fix to KB5095093, but the communication remains sparse.

Why does CapabilityAccessManager.db-wal exist on Windows 11 at all?

A .db-wal file is a write-ahead log. In plain terms, it records database changes before they are folded back into the main database. This is normal database behavior. The file can grow during use, but it should not keep expanding without being merged or compacted.

In this case, CapabilityAccessManager.db-wal belongs to Windows 11’s Capability Access Manager database. The supplied material says that database tracks app capability and privacy-related access, including camera, microphone, location, and screen capture activity.

Windows Latest says the file may be growing because Windows 11 “keeps logging repeated events for access requests or other privacy controls, such as location.” The problem, based on that reporting, appears to be that the log was not being folded back into the main database properly on affected systems.

Here is the clean distinction:

That distinction matters. The supplied sources do not say app permissions stopped working. They say the file behind the logging process became a storage problem.

How big did the Windows 11 storage bug get before KB5095093?

The reported numbers are the story. The Verge says several users ran into issues over the past few months, with one person saying the file took up 500GB. Others reported sizes ranging from 12GB to 200GB.

TechSpot’s supplied material cites reports from around 70GB to 200GB, plus a Reddit case where TreeSize showed about 513GB consumed by the same file. Windows Latest also says it saw reports around 200GB, 500GB, and more.

Those figures turn a hidden system file into a practical crisis. On any machine, a file in the 100GB to 500GB range can change whether the user can install apps, download files, or keep enough free space for normal work. The source material does not quantify failed updates or performance effects, so those should not be treated as confirmed outcomes here.

The confirmed practical issue is simpler and still serious: Windows categorized the storage under system areas, while the actual file sat in a protected folder:

C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\

Windows Latest says File Explorer or PowerShell may show “Access denied” when users try to open that folder directly. That means affected users were unlikely to find the file through casual browsing.

Why did users have to hunt for the culprit themselves?

Microsoft’s fix arrived through an optional update, not a loud user-facing warning. To install it now, The Verge says affected users can go to Settings, choose Windows Update, open Advanced options, then select Check for optional updates and install the June 2026 update.

That path works for informed users. It is not obvious for everyone else.

Windows Latest says users can first check Settings > Storage > Show more categories > System & Reserved, then look at system storage. If that number is in the hundreds of gigabytes, the machine is likely affected. The same source also describes a read-only Robocopy command to check the protected folder without changing ownership or permissions.

XOOMAR analysis: Microsoft’s weakest point here is not only the bug. It is the gap between what Windows knows and what Windows tells the user. If a single protected file consumes 200GB, Windows should not make the user reverse-engineer System & reserved storage to identify it.

This is a narrower issue than Microsoft’s security problems, but it still belongs in the same bucket of trust in default Windows components. Readers tracking that side of Microsoft should also see our coverage of the Microsoft Defender flaw that let hackers seize SYSTEM access. Different failure mode, same user expectation: core Windows components should not surprise people this badly.

What should affected Windows 11 users do now?

The safest source-backed action is to install KB5095093 if the optional update is available, or wait for the fix to arrive through a later standard update path described in the supplied Windows Latest and TechSpot material.

Users who suspect the Windows 11 storage bug should check storage first, not start deleting protected system files. Windows Latest specifically advises against changing ownership or permissions just to confirm the file size. That caution is sound. This file is tied to app permission logging, and the supplied sources do not provide Microsoft-approved manual deletion steps.

A practical checklist:

• Check storage: Open Settings, then Storage, then Show more categories, then System & Reserved.
• Look for scale: Hundreds of gigabytes under system storage is the warning sign described by Windows Latest.
• Install the fix: Use Windows Update’s optional updates section to install KB5095093, if available.
• Avoid file surgery: Don’t change protected folder permissions just to inspect or remove the file.

For readers following Microsoft more broadly, this bug arrives alongside a busy run of company-specific issues and strategy shifts, including our reporting on Microsoft MAI grabbing thousands of Office prompts from OpenAI. That does not explain this storage bug. It does show how many different parts of Microsoft’s stack are now under close technical scrutiny.

Which evidence will show whether KB5095093 actually solved the problem?

The next test is not whether Microsoft included a line in a changelog. It is whether affected users stop seeing CapabilityAccessManager.db-wal return to massive sizes after installing KB5095093.

Evidence that would strengthen Microsoft’s position is straightforward: user reports showing the file shrinking or staying small after the optional update, no repeat growth into the 12GB to 500GB range, and clearer documentation if the fix moves into broader cumulative releases.

Evidence that would weaken it would be just as clear: fresh reports of the same file ballooning after KB5095093, confusion over whether the optional update removes existing bloat or only prevents future growth, or continued absence of a user-facing explanation for why System & reserved storage exploded.

Windows can be complex under the hood. That’s not the issue. The issue is that users should not need forensic tools to find out why half a drive disappeared.

Impact Analysis

• A default Windows 11 system file reportedly grew as large as 500GB, silently consuming major drive space.
• The bug affected a Microsoft-controlled permissions component tied to privacy-sensitive app access.
• Microsoft’s KB5095093 fix improves disk usage, but the company has not provided a full public explanation of the failure.