Forum Discussion
Fix for CapabilityAccessManager.db-wal Growing Huge in Windows 11
I had a problem where this file kept growing extremely fast and reached around 80 GB:
C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\CapabilityAccessManager.db-wal
At first, stopping the Capability Access Manager Service would stop the file from growing, but it also caused Wi-Fi/network problems, so that was not the right fix.
We used Microsoft Process Monitor and confirmed the file was being written by:
svchost.exe → camsvc
camsvc is the Capability Access Manager Service, which handles Windows app permissions like location, camera, microphone, screen capture, etc.
The real trigger was not the service itself. Something was repeatedly requesting Location access, which caused camsvc to keep writing to the database WAL file.
What fixed it
Go to:
Settings → Privacy & security → Location
Turn off:
Location services
Also turn off:
Let desktop apps access your location
After doing that, the CapabilityAccessManager.db-wal file stopped growing rapidly.
Small changes still happen when doing things like taking screenshots because Windows logs screen-capture permission activity. That appears normal. The problem was the runaway growth.
What not to do
Do not permanently disable:
Capability Access Manager Service / camsvc
Disabling that service can cause other Windows permission and network-related issues.
Other note
I also left Dell SmartByte services disabled, but the final fix was turning off Windows Location services.
5 Replies
I ran into the same problem and my CapabilityAccessManager.db-wal had grown to 108.6 GB.
I'm a Japanese speaker, so this post was translated into English with the help of ChatGPT. I also worked through the recovery procedure together with ChatGPT, verifying each step before proceeding.
What worked safely for me was:
Boot into Windows Recovery Environment (WinRE).
Open Command Prompt.
Navigate to:
C:\ProgramData\Microsoft\Windows\CapabilityAccessManager
Rename CapabilityAccessManager.db-wal (I renamed it to Cap.old) instead of deleting it immediately.
Boot Windows normally.
Windows automatically created a new small CapabilityAccessManager.db-wal.
Verify that Wi-Fi and other functions work correctly.
Boot back into WinRE and delete Cap.old.
This safely recovered 108.6 GB of disk space.
In my case, Safe Mode was not sufficient, but WinRE allowed access to the file.
I don't yet know what originally caused the runaway WAL growth. This procedure only recovers the disk space safely. The underlying trigger (such as repeated location requests) should still be investigated.
I hope this helps anyone else who encounters the same issue.
If some app, process, or service is continuously requesting location permissions, camsvc (Capability Access Manager Service) will keep logging these requests into the WAL file.
The WAL file is a temporary log that helps the main database commit writes efficiently. Normally it stays small. But when something requests location hundreds of times per second, the WAL file grows until it's flushed. At 80GB, your system probably never got a chance to flush it because the writes never stopped.
