Home windows 11’s 500GB storage bug is fastened. How one can test when you’re good
Abstract created by Sensible Solutions AI
In abstract:
- PCWorld experiences Microsoft fastened a Home windows 11 bug the place the CapabilityAccessManager.db-wal file consumed as much as 500GB of cupboard space.
- Replace KB5101650 resolves this app permissions-related difficulty, although customers could have to manually delete present outsized recordsdata.
- Home windows 11 customers ought to set up the newest replace and confirm the problematic file has shrunk appropriately. Detailed directions are offered beneath.
As a part of the July Patch Tuesday replace, Microsoft not solely fastened a file variety of safety vulnerabilities and rolled out some new options, but additionally patched a contemporary bug that precipitated Home windows 11 to waste as much as 500 GB of cupboard space.
The Functionality Entry Supervisor bug in query could cause cupboard space to run low on Home windows 11 PCs even when there’s ample free house out there. A fault within the CapabilityAccessManager.db-wal file causes the system drive to develop more and more full. This file is linked to the Home windows service Functionality Entry Supervisor, which in flip is liable for app permissions in Home windows. The file ought to usually solely take up a number of MB of storage, however on some PCs it quantities to a number of hundred GBs.
With replace KB5101650, Microsoft has fastened this drawback. Not like the brand new options within the patch, this repair ought to work instantly after set up—no gradual rollout. Within the patch notes, Microsoft’s entry concerning the bug is remarkably terse:
[Storage] This replace improves disk house utilization for the CapabilityAccessManager.db-wal file.
Microsoft doesn’t say whether or not a WAL file that has already grown to a number of hundred GBs shall be routinely shrunk. Based on Home windows Newest, customers who had put in the non-obligatory June replace reported that their file was nonetheless massive even after the replace and solely returned to regular after that they had deleted it manually.
So, after putting in replace KB5101650, it is best to test whether or not your WAL file remains to be massive or has shrunk down. To do that, enter the next within the Home windows Command Immediate with administrator rights:
robocopy "C:ProgramDataMicrosoftWindowsCapabilityAccessManager" "%TEMPpercentCAMCheck" /L /B /R:0 /W:0 /BYTES /NP
Alternatively, use an exterior device equivalent to WizTree, TreeSize, or WinDirStat to seek for the “CapabilityAccessManager.db-wal” file and test its dimension. If it’s a number of GB massive, it is best to delete the file utilizing the tactic described right here. (Deleting the file in a approach that doesn’t observe the really useful process could trigger issues.) If the file is only some hundred KB or a number of MB in dimension, then all the pieces is okay.
This text initially appeared on our sister publication PC-WELT and was translated and localized from German.
