CapabilityAccessManager is devouring my hard drive

Donald Gibson 140 Reputation points
2026-03-10T04:48:55.5266667+00:00

Checking Storage in Settings (Windows 11) shows I have 83GB of Installed apps and 111GB of System and Reserved. Most people report System and Reserve should represent ~40GB. What is the extra 70GB?

Turns out it is a single file , a database for Capability Access Manager. Online commentors say it is supposed to store data for a month and then delete it. My file (and others on the internet) just keeps growing and today this single file is 66.5GB. My 221GB hard drive is full and my system is completely constipated.

Someone suggested deleting the file but I can't get at it. Completely protected by the program. I confess I'm not sophisticated enough to break through the security

I finally get through to Microsoft Support. She's never heard of the problem so check s with a supervisor. When she gets back online her solution is for me to buy a portable hard drive. Clearly this is a known issue but no amount of cajoling, begging or logic will get MS to budge. Can't help me. The support agent was adamant she was not allowed to assist me in deleting that file.

Won't help me.

Can anybody else?

Windows for home | Windows 11 | Performance and system failures

Answer accepted by question author
Stephen Murphy 105 Reputation points
2026-04-27T13:45:59.27+00:00

I bumped this up a level so it is more visible as an 'answer' - albeit it is a mere tweak on what Emmanuel provided so all credit to him (I originally had it in the thread started by Anonymous user 10 March 2026)

**

Great thread that solved the same problem for me. Thanks to Donald for raising it and Emmanuel Santana for the advice.

I'll paste my slight tweak on the fix I needed to do and put it all here in one summary for anyone else needing help. I boldfaced a few points for emphasis (as others note: do NOT delete the db-wal file until AFTER you stop camsvc).

Context for anyone lost in the threads: What follows is how I followed the advice from Independent Advisor Emmanuel Santana responding to user Donald Gibson regarding the dramatic increase in ProgramData space being used by Capability Access Manager. Most of the text below is verbatim from Emmanuel (see above); credit to him for this fix

 

Start in SAFE MODE: Restart your PC while holding Shift, then choose Troubleshoot > Advanced options > Startup Settings > Restart.

1.      Open Command Prompt as Administrator.

In my case, I had to do the next two steps in the order I write below; with the OP response, steps 2 and 3 were in the reverse order; if I used the OP order, then it would tell me the service was “stopping or starting please try again later”

2.      Take ownership of the folder:

takeown /f "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" /r /d y

 

3.      You MUST first stop the Capability Access Manager service (do not delete files until you stop this):

net stop camsvc

 

4.                  Grant administrator permissions:

icacls "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" /grant administrators:F /t

 

5.                  Delete only the large WAL log file (leave the main .db file in place):

del "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager*.db-wal"

 

6.                  Restart the computer.

Per Emmanuel's advice and statements, after this, this outcome did indeed happen: “Windows should recreate the log automatically and it should go back to a normal size (usually only a few MB).”

I note that before the fix, my C: drive was at 200 GB and pretty much borked my computer because there were 0 (!) Bytes (!) left on my puny 256 GB C: drive. Others with larger drives have noted there seems to be a tendency for this to happen with the 256 GB drives BUT others report bigger drives just take a bit longer to fill up. Lots of chatter about this on reddit and Azure to the Max has a good thread on managing multiple units with this problem: https://azuretothemax.net/

The problem is likely to persist because the latest iterations of Windows updates have been terrible and one of them likely is not playing nice with the equally awful SmartByte app that Dell forces you to use (and is difficult to remove without breaking it). I have a Dell. I won't have it for long because SmartByte has long caused many problems. Even though this is likely a combination of bad Microsoft updates X SmartByte, the inherent issues with SmartByte prompted me to decide to abandon Dell.

As others note, apps like Rainmaker also seem to contribute to the ballooning CapabilityAccessManager*.db-wal file.

Thanks again Donald for a concise statement of the problem many of us have been having and Emmanuel for posting such a precise solution. While I knew which file was bloating and that I'd need to stop the service, the solution meant I could do so without killing my wifi or comm services.

Was this answer helpful?

100+ people found this answer helpful.

Answer accepted by question author
Emmanuel Santana 40,195 Reputation points Independent Advisor
2026-03-10T08:01:07.7066667+00:00

Hello. That file cannot be removed while the system is running normally. Try this to delete it:

  1. Restart your PC while holding Shift, then choose Troubleshoot > Advanced options > Startup Settings > Restart.
  2. Select Safe Mode.
  3. Once in Safe Mode, open File Explorer and if I'm not wrong, go to: C:\ProgramData\Microsoft\Windows\CapabilityAccessManager Otherwise try to delete the file you have identified. But I believe it should be the file CapabilityAccessManager.db-wal.
  4. Delete only that file (leave the main .db file in place).
  5. Restart the computer normally.

After this, Windows should recreate the log file automatically, and it will return to a normal size instead of tens of gigabytes.

Was this answer helpful?

60+ people found this answer helpful.

19 additional answers

Sort by: Most helpful
  1. Damariobros-3483 0 Reputation points
    2026-07-21T07:29:18.35+00:00

    A while ago, while cleaning a defunct antivirus off an old laptop, I had to delete a couple remnant DLL files and a remnant empty folder which was owned by TrustedInstaller and that couldn't be deleted or have ownership taken even in Safe Mode. I managed to find a way to delete it though.

    What I did:

    1. Enable the built-in Administrator account
    2. Reboot into Safe Mode with Command Prompt
    3. Login as the built-in Administrator account
    4. Use Command Prompt to navigate to the file's directory
    5. Take ownership of the file with takeown /f <filename>
    6. Delete the file

    I could not take ownership and delete those files in any other way. Maybe this could work on this database file too.

    If taking ownership succeeds but you still can't delete it, you may need to also give Administrator all permissions for the file as well. And if that still doesn't work, open an escalated Command Prompt as TrustedInstaller and try again. If all else fails, boot into an external Windows Recovery Drive and delete the file that way I guess (it ignores the permission structure of drives other than the one WinRE is running in).

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.