How a Ghost Windows Bug Stole 100GB of My SSD Overnight and How to Stop It
Your computer might be silently eating its own storage space while you sleep.
A few nights ago, I was working late on a project when something extremely strange caught my attention. A Windows system notification popped up warning me that my disk space was running dangerously low. I checked my C drive and saw that I had less than 15GB remaining.
This made no sense. I knew for a fact that I had over 100GB of free SSD storage when I booted up my PC earlier that day. I had not downloaded any new software, nor had I saved any large media files.
Yet, my storage space was actively shrinking in real-time. It was as if a ghost was pouring gigabytes of invisible garbage onto my drive.
As it turns out, this is not a random glitch. It is one of the most infamous, ongoing background loop bugs affecting both Windows 10 and Windows 11 users. Here is how it happens and exactly how to stop it before it destroys your SSD.
The Invisible Storage Eater: The CBS Log Catastrophe
Checking the usual spots like the Downloads folder or clearing browser caches did absolutely nothing. The real culprit was buried deep within the core of the Windows system directory.
When I tracked down where the actual data was accumulating, I found a single text file named "CBS.log" located inside the Logs folder. That single file had bloated to a staggering 82GB.
The Core Issue: The Windows self-diagnostic and update systems were attempting to clean up corrupted files in the background, only to get trapped in an infinite error loop.
The Malicious Loop: The system writes an error log, tries to compress it into a cabinet file, and fails because the file size is too large for the compression engine. The process crashes, restarts from scratch, and repeats this cycle endlessly. Within hours, your temporary directory gets flooded with massive, useless backup files.
Reclaiming Your Space: A Step-by-Step Restoration Guide
To fix this issue permanently, you cannot simply press delete. The Windows operating system holds a lock on these active log files, meaning the system will deny your deletion request.
Follow these specific steps to safely stop the loop and reclaim your drive.
Step 1: Terminate the Active System Installers
You must temporarily pause the background services that are locked onto the bloated files.
Press the Windows Key, type "Services" into the search bar, and run the application as administrator.
Scroll down the list to find "Windows Modules Installer." Right-click it and select "Stop."
Scroll down further to find "Windows Update." Right-click and select "Stop" as well.
Step 2: Clean Out the Bloated Junk Files
Now that the files are unlocked, you can proceed to wipe the accumulated garbage from your drive.
Open File Explorer and navigate to the following folder:
C:\Windows\Logs\CBSDelete the "CBS.log" file and any other log files present in this directory.
Next, navigate to your temporary system folder:
C:\Windows\TempLook for any large files with names starting with "cab_" or "tar_". Select them all and permanently delete them by pressing Shift + Delete.
Step 3: Repair System Components and Restart
Finally, you need to restart the services and run a system repair command to patch the underlying corruption so the loop does not start up again.
Go back to the "Services" window. Right-click both "Windows Modules Installer" and "Windows Update," and select "Start."
Press the Windows Key, type "cmd," right-click the Command Prompt, and select "Run as administrator."
In the terminal, type
sfc /scannowand press Enter.
This command will scan your core Windows components, identify the broken files that caused the compression loop in the first place, and replace them with clean, stable versions.
Immediately after running this scan and cleaning the directories, my drive returned to its clean state with over 100GB of free space restored.
If your storage space has been mysteriously disappearing lately, do not ignore it. Check your logs folder today; otherwise, a background loop might be silently wearing down your SSD lifespan.
Comments
Post a Comment