In the quiet hum of millions of machines, a trusted system service meant to guard privacy began instead consuming it in a different sense — silently filling drives with hundreds of gigabytes of invisible, unchecked data. Microsoft's Windows 11 Capability Access Manager, a component designed to mediate access to cameras and microphones, produced a runaway log file that swallowed storage whole, while the operating system itself misreported the damage. A hotfix has been issued, but the deeper question of how a guardian became a burden — and how many were affected before anyone noticed — remains u
Microsoft confirms Windows 11 bug consuming 70GB+ of SSD storage
A system service writing endlessly, silently consuming hundreds of gigabytes
Mark
Why would a permissions manager need to write so much data to a log file in the first place?
Mimi
That's the question nobody can answer yet. Log files are supposed to track what happened—a record of events. But something caused this service to write continuously, obsessively, as if it were stuck in a loop. Microsoft hasn't explained what that something was.
Mark
Did users have any warning this was happening?
Mimi
None. The file grew silently in the background. You'd only notice if you happened to check your disk space or ran a tool to see where your storage went. By then, 70 gigabytes could already be gone.
Mark
And the Storage Settings tool was showing wrong numbers?
Mimi
Yes. So even if you looked at what Windows told you was using space, you'd get false information. The system was both the problem and an unreliable witness to its own problem.
Mark
How long had this been happening before Microsoft acknowledged it?
Mimi
The source doesn't say. We know it was happening long enough for multiple users to discover it independently and post about it online. How many people lost storage before anyone noticed? That's unclear.
Mark
What does the hotfix actually do?
Mimi
Microsoft hasn't explained that either. They've said the issue is resolved in the update, but not how. Whether it stops the writing, cleans up existing bloated files, or something else—we don't know.
Mark
Should people be concerned this could happen again?
Mimi
That's a reasonable question to ask. Without understanding what caused it, it's hard to have confidence it won't recur in some form.
Le Pouls
- A hidden system log file ballooned to as much as 500GB on users' drives, silently consuming storage until machines could no longer function normally.
- Windows' own Storage Settings tool actively misled users, displaying false capacity figures and making the source of the problem nearly impossible to trace without third-party tools.
- The crisis only became visible when a single forum post by one user triggered a wave of discovery, revealing the problem was far more widespread than anyone had suspected.
- Microsoft confirmed the bug and released hotfix KB5095093, urging immediate installation — but has offered no explanation of what caused the runaway logging or how many users were affected.
- Users are left patched but uncertain, aware that a core system service failed silently and that the full scope of the failure has never been disclosed.
In the quiet hum of millions of machines, a trusted system service meant to guard privacy began instead consuming it in a different sense — silently filling drives with hundreds of gigabytes of invisible, unchecked data. Microsoft's Windows 11 Capability Access Manager, a component designed to mediate access to cameras and microphones, produced a runaway log file that swallowed storage whole, while the operating system itself misreported the damage. A hotfix has been issued, but the deeper question of how a guardian became a burden — and how many were affected before anyone noticed — remains unanswered.
Microsoft has confirmed a bug in Windows 11 that silently consumed massive amounts of storage space across an unknown number of user machines. The source was the Capability Access Manager — a system service responsible for controlling app access to hardware like cameras and microphones — which under normal conditions produces only a small log file. Something caused that log file, named CapabilityAccessManager.db-wal, to grow without limit, swelling to 70, 200, even 500 gigabytes on affected systems. Users had no idea it was happening.
The problem came to light when a user named Donald Gibson posted to Microsoft's Q&A forum, reporting that a single log file had consumed over 66 gigabytes of his drive. His post opened a floodgate. Other Windows 11 users, running disk analysis tools like WinDirStat and TreeSize, began finding the same runaway file on their own machines. The issue was clearly widespread.
Compounding the frustration, Windows itself was obscuring the damage. The built-in Storage Settings tool displayed incorrect usage figures, leaving users unable to trust their own system's accounting of where their storage had gone.
Microsoft eventually acknowledged the bug and released hotfix KB5095093, urging users to install it immediately to stop further expansion. But the company has said nothing about what triggered the failure, why the log file began writing endlessly, or how many users were affected before the fix arrived — leaving a resolved problem with an unexplained cause.
Microsoft has confirmed a bug in Windows 11 that silently devours storage space at an alarming rate. The culprit is the Capability Access Manager, a system service designed to control which applications can access your camera, microphone, location data, and other hardware resources. Under normal circumstances, the service leaves behind a small log file—a few megabytes at most. But something went wrong.
The log file, named CapabilityAccessManager.db-wal, began growing without restraint. Users who ran disk analysis tools discovered files that had swollen to 70, 80, even 200 gigabytes or more. One user reported finding a log file that had consumed over 500 gigabytes of space. These weren't files the users had created or downloaded. They were system artifacts, growing in the background, eating away at available storage until machines ground to a halt with nowhere left to save anything new.
The problem first surfaced publicly when a user named Donald Gibson posted to Microsoft's Q&A forum, reporting that a single log file had consumed more than 66 gigabytes of his drive. His post triggered a cascade of similar reports. Other Windows 11 users, armed with disk analysis software like WinDirStat and TreeSize, began investigating their own machines and discovered they were experiencing the identical problem. The issue was widespread, affecting enough users that it became impossible to dismiss as isolated.
Making matters worse, Windows itself was lying about the problem. The operating system's built-in Storage Settings tool was misreporting how much space was actually being used, showing incorrect figures in categories like "Installed Apps" and "System & Reserved." Users couldn't trust their own system to tell them where their storage had gone.
As complaints accumulated, Microsoft acknowledged the bug and released a hotfix bundled into update KB5095093. The company urged all Windows 11 users to install the patch immediately to prevent the log file from expanding further. But Microsoft has remained silent on the mechanics of the failure—what triggered the bug, why the Capability Access Manager began writing endlessly to the log file, or how many users were affected before the fix became available. The company has disclosed only that the issue has been resolved in the latest release, leaving users to wonder what went wrong and whether similar problems might be lurking elsewhere in the system.
Citations marquantes
Microsoft urged all Windows 11 users to install the latest update immediately to prevent the rogue log file from expanding any further— Microsoft (via official confirmation)
Envie de l'histoire complète ?
Lire l'original sur Bangkok Post ↗
Technology