bytevyte
bytevyte
Language
EN DE ES FR PT IT
Follow
quick-beats —

Windows 11 Storage Bug Confirmed: Hidden File Can Eat 500GB, Fix Due July 14

Windows 11 storage bug

Windows 11 storage bug has been formally acknowledged by Microsoft after months of user reports, with the company confirming that a hidden system file can silently expand to consume up to 500GB of disk space on machines running versions 24H2 and 25H2. The company disclosed the issue on June 29 and released an optional patch, though most users will not receive the automatic fix until the scheduled Patch Tuesday rollout on July 14.

The root cause lies in a file called CapabilityAccessManager.db-wal, a write-ahead log used by Windows to track which applications have requested permissions for features like the camera, microphone, and location services. Under normal conditions, this log stays at a few megabytes in size and clears itself after roughly a month. A bug introduced in a recent cumulative update broke that cleanup process, allowing the file to grow without any meaningful limit.

How the Bug Works and Who Is at Risk

The affected file belongs to the Capability Access Manager component, a core system service that handles app permission controls. Because the file is hidden within protected system folders, most users cannot see it through standard File Explorer tools. The growth happens gradually over weeks or months, making it easy to overlook until the system drive runs critically low on space.

Users with smaller solid-state drives are at the greatest practical risk. A 256GB or 500GB drive can be filled entirely by this single file, which in extreme cases has been reported to exceed 500GB. When a system drive runs out of space, Windows may fail to install updates, crash during normal operation, or refuse to boot. The bug was first reported by users as early as May 2025, meaning some affected systems may have been losing storage space for over a year before Microsoft publicly confirmed the problem.

The impact is not uniform across all hardware configurations. Machines with 1TB or larger drives may notice a performance slowdown or a mysterious drop in available space without ever reaching a critical state, while systems with 256GB drives face the real possibility of total drive saturation. Consumer laptops sold in 2024 and 2025 often ship with 256GB or 512GB SSDs as the base configuration, putting a substantial portion of the current Windows 11 user base in the danger zone.

How to Check Whether Your System Is Affected

Microsoft has outlined a straightforward method for users who want to determine whether the bug is affecting their machine. Open the Settings app, go to System, then Storage. Click Show more categories and select System and reserved. If the entry for System files exceeds roughly 100GB on a typical consumer PC, the Windows 11 storage bug is likely present.

For users who want absolute certainty, third-party disk analysis tools such as TreeSize or WizTree can locate the CapabilityAccessManager.db-wal file directly and display its exact size. Microsoft has warned against manually deleting or moving the file, as doing so could break permission settings for installed applications and create additional system instability.

The Fix: Optional Now, Automatic Next Week

Microsoft quietly included the fix in the optional preview update KB5095093, which was released on June 29. Users who install this update through Windows Update will see the CapabilityAccessManager.db-wal file begin to shrink as the system properly trims its write-ahead logs again. The release notes for KB5095093 describe the fix as an improvement to disk space usage for the CapabilityAccessManager.db-wal file.

Users who have not installed the optional update will receive the same fix automatically on July 14, when Microsoft pushes KB5095093 as part of its monthly Patch Tuesday bundle. That date falls two days after the current date, meaning the automatic rollout is imminent for anyone still waiting.

The distinction between optional and automatic delivery matters because many consumers skip optional preview updates entirely. Microsoft does not force optional updates onto systems the way it does security patches, so a significant number of affected users may remain unaware that a fix is already available unless they actively check for updates.

The timing of the confirmation has drawn criticism from some users who reported the bug more than a year ago without receiving a public acknowledgment from Microsoft until late June 2026. During that period, the file could have been silently consuming space on millions of machines without their owners knowing the cause.

A comparison with similar incidents puts the scale of this bug into context. Prior Windows storage issues, such as the Windows 10 update cache problem that consumed tens of gigabytes, were typically resolved within a few months of widespread reporting. The year-long gap between initial user reports in May 2025 and Microsoft's June 2026 confirmation suggests that the bug affected a smaller but still significant subset of the install base, or that it evaded internal testing because it only manifests under specific usage patterns related to app permission logging.

Why this matters

The Windows 11 storage bug is the kind of silent failure that erodes trust in platform reliability. A single hidden file consuming hundreds of gigabytes is not a niche edge case — it affects users across the entire Windows 11 24H2 and 25H2 install base, many of whom will only discover the problem when their computer starts behaving erratically due to a full drive. One year of unacknowledged reports before a fix suggests a gap in how Microsoft flags system-level bugs that do not cause crashes but degrade the user experience over time. For anyone running Windows 11 on a 256GB or 512GB drive, checking System and reserved storage today is a simple step that could prevent a system failure tomorrow.

Photo by Pavlo Talpa on Unsplash

✔Human Verified

Researched and cross-referenced against primary sources by the Bytevyte editorial team.

Share