Windows 11 disk space bug causing a nearly full C drive

Windows 11 Disk Space Bug: How to Check and Fix It Now

Updated 10 November 2026. Microsoft has now fixed this bug. We’ve added the fix updates, corrected the file name and location, and replaced our cleanup advice with the steps that actually work.

The Windows 11 disk space bug made a hidden system file, CapabilityAccessManager.db-wal, grow until it took tens or hundreds of gigabytes, with reports of over 500 GB. Microsoft fixed it in the June 2026 optional update and in the July 2026 security update, KB5101650. If your PC is up to date, the file should stop growing. But the update doesn’t always shrink a file that has already grown, so it’s worth checking its size and cleaning it up safely if it’s still large.

What the Windows 11 disk space bug is

Windows 11 disk space bug in the Capability Access Manager log file

Windows keeps a small database of which apps have used your camera, microphone, location and screen capture. That’s the Capability Access Manager, and it shows up in Settings as the list of apps that recently used each permission. The database writes changes to a log file first, CapabilityAccessManager.db-wal, which normally stays at a few megabytes.

After a Windows 11 update in early 2026, that log file stopped being trimmed on some PCs and kept growing. According to Windows Latest, users reported files of 70 GB, 110 GB, 200 GB and, in one case, 513 GB. How fast it grows depends on which apps you use, which is why some PCs were hit hard and others not at all.

The file sits in C:\ProgramData\Microsoft\Windows\CapabilityAccessManager\, a protected folder that File Explorer won’t open without extra permissions. That’s why most people only noticed a C: drive that kept filling up for no obvious reason.

Which PCs were affected

Reports came from PCs on Windows 11 24H2 and 25H2, which share the same code base, so 26H2 PCs that installed the fix through monthly updates are covered too. Microsoft didn’t list it as a known issue or say which update caused it. It simply noted in the June release notes that the update “improves disk space usage for the CapabilityAccessManager.db-wal file.”

How to check for the Windows 11 storage bug

How to check for the Windows 11 disk space bug in Storage settings

Quick check in Settings

  1. Open Settings > System > Storage.
  2. Select Show more categories, then System & Reserved.
  3. Look at System files. If it shows something far above what you’d expect, such as 50 GB or more, the bug is a likely cause.

This only tells you that system files are large, not why. Use one of the next two checks to confirm.

Check the file size with a disk tool

Run a free tool such as WizTree, TreeSize Free or WinDirStat as administrator, scan the C: drive and search for CapabilityAccessManager.db-wal. A few hundred kilobytes or a few megabytes is normal. Several gigabytes means the file is still oversized.

Check with Command Prompt

Open Command Prompt as administrator and run this command, which lists the folder’s files and sizes without copying anything:

robocopy "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" "%TEMP%\CAMCheck" /L /B /R:0 /W:0 /BYTES /NP

Find the line for CapabilityAccessManager.db-wal and look at the size in bytes. A figure with ten or more digits means gigabytes.

How to fix the Windows 11 disk space bug

Installing the Windows 11 storage fix through Windows Update

Step 1: Install the update

The fix first shipped in the optional June update, KB5095093, released on 29 June 2026. It then went to everyone in the July Patch Tuesday update, KB5101650, released on 14 July 2026 as build 26100.8875 for 24H2 and 26200.8875 for 25H2. Every later monthly update includes it too.

Go to Settings > Windows Update, select Check for updates and install everything offered, then restart. If you’re on a build from July 2026 or later, you already have the fix.

Step 2: Check the file again

After restarting, check the file size again using one of the methods above. If it has dropped to a normal size, you’re done. If it’s still several gigabytes, the update stopped it growing but didn’t clear what had built up, which several users reported. Go to step 3.

Step 3: Remove the oversized file safely

Only do this if the file is still large after the update. The safe approach, as described by Windows Latest and in a Microsoft Q&A answer PCWorld links to, is to remove only the .db-wal file while the service that uses it isn’t running:

  1. Boot into Safe Mode. Our guide to booting into Safe Mode on Windows 11 shows five ways.
  2. Make sure the Capability Access Manager Service (camsvc) isn’t running.
  3. Delete only CapabilityAccessManager.db-wal. Leave CapabilityAccessManager.db and the other files in the folder alone.
  4. Restart normally. Windows creates a new, small log file.

A more cautious alternative is to rename the file from the Windows Recovery Environment, check everything works after a normal restart, and delete the renamed copy afterwards.

Don’t delete the file while camsvc is running, and don’t take ownership of the whole folder to force it. Some users who did reported Wi-Fi, location and camera permission problems, and a camsvc error 1067. If that happens, running icacls "C:\ProgramData\Microsoft\Windows\CapabilityAccessManager" /reset /T /C as administrator restored the folder’s permissions for those users. You may need to re-enter your Wi-Fi password and grant camera and microphone permissions to apps again.

If your drive is too full to update

If C: is so full that Windows Update can’t download the fix, clear the file first using the steps above, then install the update. Our Windows Update troubleshooting checklist covers other reasons an update won’t install.

Why the Windows 11 disk space bug matters

On a laptop with a 256 GB or 512 GB SSD, a log file taking 100 GB or more can leave almost no free space. Windows needs free space to install updates, so a full drive can stop security patches installing, and very low space also slows the PC and can make apps crash. Because the file is hidden, many people blamed old update files or their own downloads and deleted the wrong things first.

The Windows 11 disk space bug doesn’t damage your personal files. Once the file is back to normal size, the space is yours again.

Keeping storage under control

  • Turn on Storage Sense in Settings > System > Storage so Windows clears temporary files automatically.
  • Glance at Settings > System > Storage once a month. A category that jumps in size is easier to investigate early.
  • Keep Windows Update on, so fixes like this one arrive without you having to look for them.
  • Run a disk tool such as WizTree now and then to spot files that keep growing.

Our Windows 11 storage cleanup guide covers safe ways to free 10 to 20 GB, and if your drive seemed smaller than advertised from day one, see why your drive shows less storage than advertised.

FAQ

What is the Windows 11 disk space bug?

A bug in early 2026 Windows 11 updates that stopped the CapabilityAccessManager.db-wal log file from being trimmed. The file, which records app permission activity, kept growing, and users reported sizes from tens of gigabytes up to 513 GB.

Is the Windows 11 storage bug fixed?

Yes. Microsoft fixed it in the June 2026 optional update KB5095093 and in the July 2026 security update KB5101650. Any Windows 11 24H2 or 25H2 PC with updates from July 2026 or later has the fix.

Does the update delete the large file automatically?

Not always. The fix stops the file growing, but some users found it stayed large until they removed it. Check the file size after updating, and only remove it if it’s still several gigabytes.

Is it safe to delete CapabilityAccessManager.db-wal?

Yes, if you delete only that file while the camsvc service isn’t running, for example in Safe Mode. Don’t delete the main .db file or change the folder’s ownership, which caused Wi-Fi and permission problems for some users.

How much space does the file normally use?

A few hundred kilobytes to a few megabytes. Windows Latest’s healthy example was about 1.6 MB.

Can the bug delete my files?

No. It only fills the drive with a log file. Your documents and apps aren’t affected, though a completely full drive can stop updates installing and make Windows unstable until you free space.

2 Replies to “Windows 11 Disk Space Bug: How to Check and Fix It Now”

  1. bonjour, la mise à jour ne s’est pas faîte, windows 11 fait 181 go je n’ai plus que 40 go de libre, je ne sais plus quoi faire, j’ai eu microsoft 3 fois avec des techniciens, rien n’y a changé, ils m’ont fait réinstallé windows 11, que dalle je suis décourage, mon pc n’a que 18 mois, mon disque dur fait 500 go à la base, si quelqu’un peut m’aider s’il vous plait, Jmichel D.

    1. Bonjour Jean-Michel,
      Ne vous découragez pas. Avant de réinstaller Windows à nouveau, il faudrait d’abord identifier précisément ce qui occupe les 181 Go.

      Allez dans Paramètres → Système → Stockage → Afficher plus de catégories et dites-nous combien d’espace est indiqué pour Système et réservé, Applications installées, Fichiers temporaires et Autres.

      Si possible, indiquez-nous également votre version de Windows 11 en tapant winver dans le menu Démarrer.

      Avec ces informations, nous pourrons déjà déterminer si votre problème correspond au bug décrit dans cet article ou si les 181 Go sont utilisés par autre chose. Une nouvelle réinstallation de Windows n’est probablement pas la première chose à faire à ce stade.

Leave a Reply

Your email address will not be published. Required fields are marked *