A customer's C: drive was 98% full, taskbar icons kept vanishing and Wi-Fi randomly disappeared. The cause wasn't a virus or a failing SSD — it was a single runaway Windows log file eating 133GB. Here's how we found and safely removed it.

A customer brought in a Windows laptop that had become almost unusable — the C: drive was critically full, taskbar icons kept disappearing, and the Wi-Fi option randomly vanished from Quick Settings. Most people (and a few shops) would immediately blame a virus, or worse, tell you the SSD is dying and needs replacing. The real cause was far more interesting — and a lot cheaper to fix.

The symptoms

→C: drive almost completely full — only a few GB left
→Taskbar icons missing or not loading properly
→Wi-Fi option randomly disappearing from Quick Settings
→General system instability from the extremely low disk space

Windows Storage settings showing the C: drive almost completely full — Where we started — the C: drive critically low on space.

First, we ruled out the usual suspects. A CrystalDiskInfo check showed the SSD was healthy (Good, 98%) — so the drive wasn't failing. A malware scan turned up nothing obvious. So where did all the space go?

Finding the real culprit

Using TreeSize to map exactly what was consuming the disk, the answer jumped out: a single file buried deep in C:\ProgramData\Microsoft\Windows\CapabilityAccessManager — a database log file called CapabilityAccessManager.db-wal — had ballooned to roughly 133GB.

TreeSize showing a 133GB CapabilityAccessManager.db-wal log file — The culprit: one runaway Windows log file at ~133GB.

Why does this happen?

The Capability Access Manager is the Windows service that tracks which apps access your camera, microphone and location. In rare cases its write-ahead log (the .db-wal file) fails to flush properly and grows without limit — quietly swallowing tens or even hundreds of gigabytes. It's not a virus, and it's not your fault. It's a Windows quirk that's almost impossible to spot without the right tools.

How we fixed it safely

→Confirmed SSD health with CrystalDiskInfo (Good, 98%) so we knew the drive was fine
→Used TreeSize to pinpoint the abnormal file instead of guessing
→Stopped the Capability Access Manager service (net stop camsvc) so the file wasn't locked
→Corrected the folder's ownership and security permissions to gain safe access
→Removed the corrupted 133GB log file and verified the freed space
→Ran SFC (sfc /scannow) — Windows reported no integrity violations after the repair

💡 Please don't delete files inside ProgramData or System folders by guessing — removing the wrong file can break Windows completely. This was done after verifying exactly what the file was, stopping the right service, and correcting permissions. When in doubt, let a technician handle it.

Checking the laptop's NVMe SSD details and health — We verified the SSD itself was perfectly healthy — no costly replacement needed.

The result

→C: drive space fully recovered — laptop usable again
→Windows SFC verification passed with no integrity issues
→System stability restored — no SSD replacement, no reinstall
→Customer kept all their data and paid only for the repair work

Laptop full, slow, or acting strange?

If your C: drive keeps filling up for no reason, your laptop is crawling, or icons and Wi-Fi keep vanishing, don't rush to replace the whole machine — it's often a fixable software issue like this one. We diagnose the real cause first, then quote you honestly. WhatsApp us at 012-577 7436 — free pick-up & delivery across KL, Selangor & Putrajaya.

The Hidden 133GB File That Filled a Customer's Laptop (Real Repair Case)