{"id":23498,"date":"2026-07-21T12:45:46","date_gmt":"2026-07-21T11:45:46","guid":{"rendered":"https:\/\/innovatenews.site\/index.php\/2026\/07\/21\/i-let-claude-clean-up-my-windows-install-and-it-found-bloat-i-didnt-even-know\/"},"modified":"2026-07-21T12:45:53","modified_gmt":"2026-07-21T11:45:53","slug":"i-let-claude-clean-up-my-windows-install-and-it-found-bloat-i-didnt-even-know","status":"publish","type":"post","link":"https:\/\/innovatenews.site\/index.php\/2026\/07\/21\/i-let-claude-clean-up-my-windows-install-and-it-found-bloat-i-didnt-even-know\/","title":{"rendered":"I let Claude clean up my Windows install, and it found bloat I didn't even know\u2026"},"content":{"rendered":"
\n

The topic I let Claude clean up my Windows install, and it found bloat I didn’t even know\u2026<\/strong> is currently the subject of lively discussion \u2014 readers and analysts are keeping a close eye on developments.<\/p>\n

This is taking place in a dynamic environment: companies\u2019 decisions and competitors\u2019 reactions can quickly change the picture.<\/p>\n

My main Windows box has a 7TB boot drive with 5.3TB free, so I’ve never had a reason to care about disk space. That turns out to be exactly the problem. When storage is free, you stop looking, and Windows 11 is happy to fill the gaps you’re not watching. Plenty of that bloatware can be removed with one PowerShell command, but those scripts clean the apps you can see in Settings, and those are the ones that were never bothering you anyway.<\/p>\n

So I pointed Claude Code at the whole machine and told it to find everything, explain everything, and delete nothing without asking. Four phases and about six hours later, I’d reclaimed 57GB, cut my boot time by a fifth, and knocked 65 processes off my idle load. I’d also found a 10.5GB crash dump from a GPU hang I never noticed, an abandoned 28GB Docker cache left behind by a different AI agent, and a git repository at the root of my C: drive that was quietly holding the only copies of some family videos.<\/p>\n

None of that shows up in storage settings. That’s the whole point.<\/p>\n

Every phase followed the same shape: audit everything, delete nothing, write the findings to a Markdown file, and wait for me to approve rows before anything ran. Claude Code isn’t allowed to improvise on a machine I care about, and the dry-run pattern is the only reason I was comfortable letting it near a system drive at 1 AM.<\/p>\n

I also made it write its own receipts. Windows has a quirk where Claude Code’s command parser rejects anything over 965 bytes, which kills the long PowerShell one-liners this kind of work needs. The fix \u2014 write scripts to a _scripts folder and execute the files \u2014 turned out to be better than the thing it replaced, because every command that touched the machine survives as a file I can read, rerun, or quote. It’s the same approach I used when Claude Code showed me what my Home Assistant could actually do, and it’s become my default.<\/p>\n

Before touching anything, I captured a baseline: 107.6 seconds average boot across five boots, 433 processes at three minutes of uptime, 31GB of RAM in use before I’d opened a single app. Those numbers matter later, and not in the way I expected.<\/p>\n

\"\"<\/figure>\n

The first big hit was that C:WindowsLiveKernelReports held 10.5GB in a single dump file from March 13th \u2014 a live kernel report, meaning my GPU hung hard enough for Windows to snapshot the kernel, then recovered without a bluescreen. Thirty-three smaller dumps trailed off through late May and then stopped, which reads like a bad AMD driver that got fixed. Windows kept the 10GB souvenir for four months and never mentioned it.<\/p>\n

DISM’s component store cleanup was supposed to give back 1\u20133 GB and handed over 5.98GB. Delivery Optimization \u2014 the peer-to-peer update cache \u2014 was sitting on 5.37GB. And 28GB was tied up in an abandoned WSL sandbox created by a completely different AI coding tool back on July 9th, full of PyTorch container images and zero actual containers. One AI agent cleaning up another’s mess is a very 2026 problem.<\/p>\n

I had Claude triage 257 packaged apps and 310 installed programs, and the interesting result was how few were actually removable. Twenty-one came out. The rest were either in use, load-bearing, or off-limits \u2014 and a chunk was simply untouchable, which I’ll come back to.<\/p>\n

This is the one that moved the numbers. Nine services dropped from Automatic to Manual, four scheduled tasks got disabled, and nine registry Run entries came out \u2014 Steam, Epic, Discord, Edge’s auto-launch, and a handful of vendor agents. Not a byte of disk space involved.<\/p>\n

Okay, this one I flagged upfront as a privacy exercise rather than a performance one. Thirty-one changes, and Claude was honest enough to tell me in writing beforehand that none of them would move a benchmark number. That’s the correct answer, and it’s not the one I’d have gotten from a one-click tool that does the job better than debloating manually.<\/p>\n

Tips on how to gain better gaming performance on Windows-powered handhelds by debloating Windows 11.<\/p>\n

\"\"<\/figure>\n

The single best find is the one I nearly deleted. That mystery .git folder at the drive root held 12,988 loose objects totaling 3.7GB, and my first instinct was to garbage-collect it and move on. Claude proposed extracting the largest objects first, which is how I discovered they were QuickTime videos \u2014 family footage and a pile of GIFs, swept up by an agent orchestration run at 1:18 AM on June 9th that ran git add from the wrong directory. The originals may still exist somewhere on my drive. I genuinely don’t know. What I do know is that “propose, then execute” is the only reason I still have them.<\/p>\n

Then there’s the stuff Windows won’t let you touch. Two Xbox services refused to be reconfigured from an elevated administrator session \u2014 flat “access denied,” because they carry a TrustedInstaller-level ACL that blocks admins by design. Meanwhile, four of Windows 11’s AI and accessibility components ship under scrambled codenames like Voiess and Livtop (Voice Access and Live Captions, if you’re wondering), registered twice across two build numbers, with the older copies being literal empty folders that can’t be removed and would reclaim zero bytes anyway. Microsoft protects its Store plumbing harder than its telemetry \u2014 all five telemetry scheduled tasks disabled without a word of complaint.<\/p>\n

My favorite small discovery: three registry values control whether Windows silently reinstalls promoted Store apps on your profile, and the “suggested content” toggle everyone assumes covers that doesn’t touch them. There is no Settings switch. There’s just the registry, and knowing where to look.<\/p>\n

Oh, and Microsoft’s own PC Manager \u2014 the built-in cleanup app \u2014 was running a background service the entire time and never mentioned any of the 57GB.<\/p>\n

Look, most debloat articles give you the big numbers only. The ones that are tested immediately after de-bloating, the ones that look the best. And I can’t say those aren’t valid, because my testing was similar. After the startup phase, two consecutive boots came in at 73 and 78 seconds against that 107.6-second baseline. A 30% improvement, reproduced. Fantastic number.<\/p>\n

Then I took two more boots. One came in at 108 seconds, the next at 90. My four-boot post-change average is 87.4 seconds \u2014 a 19% improvement, not 30%. The baseline itself ranged from 96 to 123 seconds, so the variance was always there; two samples just hid it from me. The post-boot phase specifically, where all those launcher autostarts lived, holds a solid 26% gain. Idle process count landed at 368 versus 433, and RAM in use dropped 21%.<\/p>\n

There’s one more number worth sitting with. I reclaimed roughly 57GB. Twenty-four hours later, my C: drive was only 28.6GB emptier than when I started, because Ubuntu grew, Windows Update downloaded, and new VM images appeared, all in a single ordinary day of work. Reclaiming space isn’t a total. It’s a rate.<\/p>\n

If I’d only done what Settings suggests \u2014 uninstall a few apps, run Storage Sense, flip the advertising toggles \u2014 I’d have found almost none of this. Eight of the privacy settings I planned to change were already off, because I’m not careless. The 57GB, the 10GB crash dump, the 28GB abandoned sandbox, the third of a boot cycle spent launching things I never asked for: all of it was in places Windows doesn’t surface and no built-in tool reports.<\/p>\n

What made the difference wasn’t that an AI is smarter about Windows than I am. It’s that it will read 12,988 git objects, cross-reference 139 cached installers against the installer database, and explain what Microsoft.TOROretail actually is (Ninja Gaiden 4, obviously) without getting bored halfway through. I still made every deletion call, and I overruled it twice \u2014 once on an 8GB Recycle Bin folder full of personal documents, once on a fan-control service it twice classified as cosmetic startup cruft. Propose-then-execute is the habit that made both saves possible, and I learned it the hard way back when agentic coding finally clicked for me, and I found my dry runs had been firing as real runs for days.<\/p>\n