Windows has a way of breaking in ways that feel almost personal. What makes these issues so draining isn’t that the problems are complicated; it’s that the built-in tools Microsoft gives you to fix them either don’t work or don’t even come close to addressing what’s actually wrong. I started handing these problems to Claude instead, to see if it can do more than just free up space on your Windows PC. I was surprised at how good it was at finding a reasonable solution.

Windows hides what is holding your files

Resource monitor shows you exactly what to close

Credit: Jorge Aguilar / How To Geek

If you’ve used Windows long enough, you’ve almost certainly run into that awful little pop-up telling you a file can’t be deleted because something else has it open. It takes so long to be done, and I don’t even know why it’s open most of the time. This is awful when you’re just trying to get rid of one video or document you no longer need.

What makes it so aggravating is that Windows clearly knows the file is locked, but it just refuses to tell you what’s holding it. Somewhere in the background, a process has opened a handle to that file with permissions that block anyone else from touching it, and the moment you try to delete it, the kernel shuts you down. Administrator privileges don’t help either.

Instead of closing random programs, rebooting, and hoping for the best, I went to Claude. It nailed the problem immediately and gave me two ways to solve it. The first was a quick trick using the built-in Windows Resource Monitor.

You just open the CPU tab, type the filename into the “Associated Handles” search box, and Windows will actually show you the process name and ID holding the lock. From there, you can just right-click and kill it.

Bluetooth connects but the sound plays somewhere else

The old control panel lets you force the right connection

Credit: Jorge Aguilar / How To Geek

There’s a particular kind of frustration that comes with Windows Bluetooth issues, and it’s made worse by how innocent it looks on the surface. These make me more mad than anything else on this list. You pair your headphones, Windows cheerfully tells you they’re “Connected,” and then you hit play, and the sound comes out of your computer speakers anyway.

The obvious first move is to run the Windows Audio Troubleshooter, but it almost never actually fixes anything. All it really does is restart a couple of audio services or swap in a default driver. It doesn’t touch the underlying routing problem, it doesn’t change how services start up at a registry level, and it doesn’t do anything about controller power states. Whatever is actually broken stays broken.

Claude was more specific than anything Microsoft’s tools had offered. The issue comes down to a collision between two different Bluetooth audio profiles that Windows manages separately. One is A2DP, which handles normal high-quality stereo playback. The other is HFP, a lower-bandwidth mode built for voice calls and microphone use. The driver responsible for juggling these two are the Bluetooth Hands-Free Audio Service.

The fix was to bypass the modern Windows Settings app entirely and go back to the old Control Panel. From there, opening Devices and Printers, pulling up the properties for the Bluetooth headset, and going into the Services tab lets you manually force-enable the Audio Sink service, which tells Windows to hold onto the A2DP stereo connection instead of abandoning it.

Windows updates get stuck in a loop

A quick script clears out the broken files

The infinite Windows Update loop is one of the worst parts of the OS. When your computer downloads an update, it crawls its way to 99 percent, fails, rolls everything back, and then does the same thing the next day as if nothing happened.

Running the built-in Windows Update Troubleshooter doesn’t help much. It pokes around, applies some surface-level fixes, and leaves the real problem completely untouched. That problem lives in a hidden folder at C:\Windows\SoftwareDistribution, where Windows stashes its update cache.

You can’t just go in and delete the folder yourself. The Windows Update and Background Intelligent Transfer services constantly hold active handles to this folder while running. You cannot delete it manually until you completely stop these background processes.

Claude was actually really smart and told me the fix was to wipe the SoftwareDistribution folder entirely and let Windows rebuild it from scratch. The trick was actually getting that done without hitting the usual “Access Denied” wall. Claude walked me through a script that shut down the entire update process before attempting any cleanup.

Once the corrupted cache was gone, Windows rebuilt its update database on its own, pulled down a fresh copy of the patch, and installed it without a hitch.

Credit: Jorge Aguilar / How To Geek

I think I’ve dealt with an unresponsive start menu more than with any other major problem on Windows. Regardless of what I do, the screen just sits there. I normally can’t get into Settings, you can’t reach the Control Panel, and all the built-in tools you’d normally use to fix something like this are locked behind the very menu that won’t open.

It’s a genuinely infuriating situation, and Microsoft’s usual advice doesn’t help much. Most of it assumes you can still click around the interface, or it just tells you to restart and forget about all the tabs and files you may have open, and sometimes that doesn’t even work.

When I asked Claude what to do, it said something was wrong with the Start Menu Experience Host. Since Windows runs the Start menu as an isolated process separate from the main desktop shell, a frozen menu won’t necessarily crash the whole system. This is why you can still use the Windows Key + X shortcut to open an admin terminal, or by opening Task Manager and using the “Run new task” option.

From there, it gave me a PowerShell command that forces Windows to reregister all of its built-in apps and rebuild the UI shell from scratch, without touching any of your personal files.

Once I had an elevated PowerShell window open, I pasted the command in and ran it. It tells Windows to go through all its default applications and re-establish their registrations. A small progress indicator ran across the terminal while it worked, and then it was done.

Start asking Claude for answers

None of these fixes needed downloading third-party software or digging through forums for a solution that may or may not apply to your situation. Claude figured out the actual mechanism behind each problem and gave me something specific to do about it. That said, some of these steps involve stopping system services or running PowerShell commands, so it’s worth understanding what a command does before running it.