disk space

Winsage
July 8, 2026
A bug in Windows 11 can cause significant disk space loss, with some users losing up to 500GB due to the CapabilityAccessManager.db-wal file, which should normally be a few megabytes. The file's size can exceed 100GB, indicating potential issues. Users can check their system file sizes through Settings > System > Storage. Tools like WizTree, TreeSize, or WinDirStat can help examine the folder contents. Microsoft has addressed the issue in the June 23 optional preview update, which improves disk space usage for the file. This update can be found under Settings and Windows Update, with a mandatory fix scheduled for the official Patch Tuesday on July 14.
Winsage
July 8, 2026
Users upgrading to Windows 11 have reported a significant decrease in available storage on their C: drive, attributed to the Capability Access Manager process consuming excessive disk space. Microsoft has acknowledged this issue and released an optional update (KB5095093) to improve disk space management for the CapabilityAccessManager.db-wal file, which can grow to several hundred gigabytes instead of the typical few megabytes. Users can check the file size in the directory C:ProgramDataMicrosoftWindowsCapabilityAccessManager, and tools like TreeSize or the command prompt can assist in this process. The CapabilityAccessManager.db-wal file functions as a write-ahead log for application access requests to system components, and its abnormal growth indicates it is not being properly merged back into the main database.
Winsage
July 7, 2026
Microsoft has released an optional update, KB5095093, in June 2026 to address a storage issue affecting Windows 11 users related to the CapabilityAccessManager.db-wal file, which manages app permissions. Users have reported the file size increasing significantly, with some reaching up to 500GB, due to continuous logging of access requests and privacy controls. To install the update, users should go to Settings, select “Windows Update,” then “Advanced options,” and check for optional updates.
Winsage
July 7, 2026
Microsoft has rolled out a point-in-time restore feature for Windows 11, available to all client PCs running version 24H2 and later, including Enterprise, Pro, and Home editions. This feature automatically creates local restore points every 24 hours, stored for up to 72 hours and limited to 2% of disk space. It is enabled by default on Windows Home and unmanaged Windows Pro devices with at least 200 GB OS volume, while it is disabled by default on Windows Enterprise, Education, and organization-managed Windows Pro systems. Users can initiate restores locally via the Windows Recovery Environment, but any changes made after the selected restore point will be lost. Microsoft plans to introduce remote initiation capabilities through Intune recovery. The upcoming Windows 11 version 26H2 will maintain a low-disruption update experience, allowing devices on versions 24H2 or 25H2 to transition via a small enablement package. Devices running version 26H1 cannot upgrade directly to 26H2.
Winsage
July 7, 2026
The Windows 11 Field Guide has been significantly reduced from 103 MB and 990 pages to 73.9 MB and 839 pages, marking a notable achievement in its transformation. At its peak, the guide was over 300 MB and contained more than 1,150 pages. The reduction includes the removal of the Microsoft Edge section, which had about 100 pages of outdated content, replaced by a more concise chapter. The top-level table of contents has been restructured, and numerous chapters have been updated and consolidated, introducing new sections on Hardware, Security, Apps, Command Line Interfaces, Virtualization, XBOX and Videogames, and Help and Recovery. Additional work remains on consolidating chapters like Multitasking, Files, and Accounts. A monthly update schedule is planned to keep the guide current with new Microsoft features. Access to the guide is included for Thurrott Premium members, available in PDF and ePUB formats, with files currently hosted on Google Drive.
Winsage
July 6, 2026
Microsoft has acknowledged a storage issue related to the Capability Access Manager service in Windows 11, which can consume up to 500GB of SSD space due to a bug causing the log file, CapabilityAccessManager.db-wal, to inflate to gigabytes instead of a few megabytes. Users have reported file sizes reaching 200GB and even 513GB. The issue can be checked via Settings > Storage > System & reserved or by using a command in the Windows Command Prompt. Microsoft plans to address this in the June KB5095093 update, which will improve disk space usage for the log file, with updates expected to roll out starting July 14.
Winsage
July 6, 2026
A hidden bug in Windows 11 can consume up to 500 GB of storage due to the CapabilityAccessManager.db-wal file, which should only occupy a few megabytes but can grow significantly on certain systems. Users can check for this issue using applications like TreeSize or by executing a command in the Windows Command Prompt. Microsoft has acknowledged the problem and provided a fix in the optional June 2026 update, with a broader rollout planned for the July Patch Tuesday update. Users are advised not to modify or delete the file to avoid further complications.
Winsage
July 6, 2026
To check for excessive storage consumption in Windows 11, navigate to Settings > Storage > System & Reserved. A file named CapabilityAccessManager.db-wal can cause significant storage issues, potentially consuming hundreds of gigabytes. This file is associated with the Windows Capability Access Manager service, which manages app permissions for features like microphone and camera access. Normally, this file should occupy only a few megabytes, but reports indicate it can expand to sizes like 200GB or even 513GB. Microsoft acknowledged this issue in the release notes for Windows 11 KB5095093, stating that an update to improve disk space usage for this file is scheduled for July 14, 2026. To check if your system is affected, tools like WizTree or TreeSize can be used, or a command can be executed in Command Prompt to verify the file size. If the file is excessively large, it is recommended to wait for the update or rename the file to allow Windows to regenerate it, rather than deleting it.
Search