Fix Windows 11 Bluetooth Stuck on Removing Device (5 Proven Fixes)
—
The fix for a Bluetooth device stuck on "Removing device" in Windows 11 is to bypass the Settings app entirely and uninstall the ghost profile from Device Manager using the "Show hidden devices" view, or delete its MAC address folder from the BTHPORT registry key. The counterintuitive truth about this error is that Settings isn't actually trying to remove the device—it is waiting for a background radio profile to release its lock on the hardware, but that profile has crashed. Until you manually sever that hidden connection, the UI will spin forever.
Jake lost a two-hour diagnostic window on Saturday trying to unpair an OBD2 scanner from his shop's primary Windows 11 tablet. He clicked "Remove device," the UI switched to "Removing device," and it never stopped spinning. Because the tablet insisted the old scanner was still in the middle of being removed, it refused to discover the replacement scanner.
"I restarted the tablet twice," Jake said. "I even turned the Bluetooth radio off and on again. Every time the tablet booted back up, the old scanner was sitting right there in Settings, still stuck on 'Removing.' It was like the command was just hanging in the air."
Ethan's take is that the Windows Settings UI is lying to you by omission. "You're looking at the ghost of a connection, not the connection itself," Ethan explained. "The Windows Bluetooth stack separates the user-interface profile—what you see in Settings—from the actual radio transport profile running in the background. When a device drops offline ungracefully, or a driver crashes, the transport profile locks up. The Settings app politely asks the transport layer to let go, and waits forever for an answer that isn't coming." Rebooting does not fix it because Windows caches peripheral states in the registry to speed up boot times. You have to go into the background and delete the cache manually.
Understanding why the remove failed error happens
When you pair a Bluetooth device in Windows 11, the operating system creates several distinct entries across the system architecture. It creates a registry key containing the device's MAC address, a driver instance in Device Manager, an endpoint for the audio or input subsystem, and a visual representation in the Settings > Bluetooth & devices menu.
When you click "Remove device," Windows initiates a teardown process. It signals the Device Association Service to sever the logical link, instructs the Bluetooth Support Service (`bthserv`) to drop the radio connection, uninstalls the driver, and finally deletes the registry keys. If any single step in this chain fails—most commonly because the device went out of range exactly as the removal started, or the `bthserv` service stopped responding—the entire teardown aborts. The UI, however, lacks a timeout mechanism for this specific failure, leading to the infinite "Removing device" loop.
🙋♂️ Jake's Reality Check
"Why doesn't the standard Windows Bluetooth troubleshooter fix this? It says it checks for radio issues."
The straight answer. The built-in troubleshooter only verifies if the Bluetooth adapter is powered on and if the primary drivers are loaded. It does not check the status of individual paired device profiles, nor can it identify a stalled device removal process. Running it for a stuck device is a waste of time.
Method 1: The hidden device wipe via Device Manager
The most reliable way to break the removal loop is to bypass the Settings app and delete the driver instance directly from the Microsoft Management Console. Because the device is in a state of limbo, it is often hidden from the standard hardware view.
- Press Win + X and select Device Manager from the power user menu.
- In the top menu bar, click View and check Show hidden devices. This step is mandatory; without it, the stuck profile will remain invisible.
- Expand the Bluetooth category. Look for the name of your stuck device. The icon next to it will likely be pale or translucent gray, indicating that the hardware is disconnected but the driver profile remains installed.
- Right-click the grayed-out device and select Uninstall device.
- If a prompt appears asking to "Attempt to remove the driver for this device," check the box and confirm the uninstallation.
Close Device Manager and return to the Windows 11 Settings app. The device will be gone, and you can now pair it fresh.
✅ Why this is the one to use
Device Manager interacts directly with the kernel's Plug and Play (PnP) manager. When you uninstall a device from this console, it forces the PnP manager to forcefully evict the driver, severing the logical tie regardless of what the frozen Settings app is trying to do.
Method 2: Restarting the Bluetooth Support Service
If Device Manager throws an error, or if the stuck device immediately reappears upon refreshing the hardware list, the underlying Windows service responsible for Bluetooth communication has crashed. The `bthserv` service handles the discovery and association of remote devices. When it hangs, no device can be added or removed.
- Press Win + R to open the Run dialog.
- Type
services.mscand press Enter. - Scroll down the alphabetical list until you locate Bluetooth Support Service.
- Right-click the service. If the Restart option is available, click it.
- If the Restart option is grayed out, click Properties.
- Change the Startup type to Automatic, click Apply, and then click the Start button if the service is currently stopped.
Once the service restarts, return to the Settings app. The "Removing device" process should now complete successfully within three seconds.
Method 3: Killing a hung Bluetooth Support Service (Stuck on "Stopping")
This is the failure mode that traps most users. You go to restart the Bluetooth Support Service as described above, but the status reads "Stopping," and all options—Start, Stop, Pause, Restart—are completely grayed out. The service is deadlocked. You cannot restart it from the GUI, and Windows cannot process the Bluetooth removal queue until the service restarts.
To fix a service stuck on stopping, you must find its Process Identifier (PID) and forcefully terminate it from an elevated Command Prompt.
- Click the Start button, type
cmd, right-click Command Prompt, and select Run as administrator. - Type the following command to locate the PID of the stuck service, then press Enter:
tasklist /svc | findstr bthserv - The output will look similar to this:
svchost.exe 14920 bthserv. The number in the middle (in this example, 14920) is the PID. Your number will be different. - Type the following command, replacing [YOUR_PID] with the number you just found, and press Enter:
taskkill /F /PID [YOUR_PID] - You should see a message stating "SUCCESS: The process with PID... has been terminated."
- Now, return to the Services console (`services.msc`), right-click Bluetooth Support Service, and select Start.
⚠️ What this actually breaks
Because bthserv runs inside a shared svchost.exe process container, killing that specific PID might temporarily drop other minor background services sharing that container. This is safe, as Windows Service Control Manager will automatically restart any critical shared services, but you may notice a brief network or audio stutter.
Method 4: The Registry nuke for stubborn ghost profiles
If Device Manager and Service restarts fail, the registry key holding the device's pairing information is corrupt or locked by a permissions error. Deleting the MAC address entry from the BTHPORT parameters forces Windows to forget the device at the kernel level.
As of the Windows 11 25H2 and 24H2 builds, this path remains unchanged from the Windows 10 era. You will need Administrator privileges.
- Press Win + R, type
regedit, and press Enter to open the Registry Editor. - Navigate to the following exact path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices - Under the Devices key, you will see several folders named with 12-character hexadecimal strings (e.g.,
001a7b9c4d2e). These are the MAC addresses of your paired Bluetooth devices. - Click on each folder and look at the "Name" string value on the right pane to identify which MAC address corresponds to the stuck device.
- Once you identify the correct folder, right-click the 12-character folder and select Delete.
- Restart your computer immediately.
If you receive an "Access Denied" error when trying to delete the key, right-click the Devices folder, select Permissions, click Advanced, and change the Owner from "SYSTEM" to your administrator account. Grant yourself Full Control, apply the changes, and try the deletion again.
Method 5: Command-line removal with PnPUtil
System administrators and power users often bypass the GUI entirely. The Windows Plug and Play Utility (`pnputil`) can query and forcibly remove device instances from the driver store, completely sidestepping the settings menu.
- Open Command Prompt as Administrator.
- Type
pnputil /enum-devices /class Bluetoothand press Enter. This lists every active and ghost Bluetooth device on the system. - Locate your stuck device in the list and note its Instance ID (which usually looks like
BTHENUM\Dev_XXYYZZ...). - Type the removal command:
pnputil /remove-device "INSTANCE_ID"(replace INSTANCE_ID with the exact string you found, keeping the quotation marks). - Press Enter. The command prompt should return "Device removed successfully."
| Method | Works on Home? | Use it when |
|---|---|---|
| Device Manager Wipe | Yes | First-line fix for ghost profiles |
| Services Restart | Yes | Settings UI is entirely unresponsive |
| Registry BTHPORT Nuke | Yes | Device Manager throws errors or fails to delete |
| PnPUtil Command | Yes | Scripting or headless remote administration |
Windows 10: How to completely remove a Bluetooth device
The core architecture of the Bluetooth stack is identical across Windows 11 and Windows 10, meaning the Device Manager, Services, and Registry steps detailed above are the exact same on both operating systems. However, the UI behavior that triggers the "remove failed" error differs slightly.
On Windows 10, Bluetooth devices are managed under Settings > Devices > Bluetooth & other devices. When a removal fails here, it does not typically spin forever on "Removing device" like it does in Windows 11. Instead, Windows 10 will rapidly output a red text error stating "Remove failed."
If you encounter "Remove failed" on Windows 10, you must use the Device Manager (Method 1) to clear the ghost profile.
Be aware that Windows 10 reaches its end of support on October 14, 2025. After this date, Windows 10 22H2 will receive no free security updates. If your hardware does not support the upgrade to Windows 11, you must enroll in the Extended Security Updates (ESU) program via Settings > Windows Update > "Enroll now." Microsoft has extended consumer ESU coverage out to October 2027. It remains free if you sync your PC via Windows Backup; otherwise, it costs a one-time fee of ~$30 USD or 1,000 Microsoft Rewards points.
The Fast Startup Trap: Why rebooting doesn't fix it
The most frustrating aspect of a stuck Bluetooth removal is the persistence. You restart the PC, hoping to clear the error, but upon boot, the device is still stuck in the "Removing" state. This happens because of a Windows feature called Fast Startup.
Fast Startup is a hybrid hibernation model. When you click "Shut down," Windows does not actually drop power to the kernel or reset the driver states. Instead, it freezes the kernel session, saves it to a hibernation file on the SSD, and powers off. When you turn the PC back on, it loads that frozen state back into memory—including the crashed Bluetooth transport profile.
To force a true driver reset without digging into the registry, you must bypass Fast Startup by executing a full shutdown. Hold the Shift key down on your keyboard while you click Shut down in the Start menu. Keep holding Shift until the power light turns off. This forces Windows to drop the kernel state and initialize the Bluetooth adapter from a cold boot.
Diagnosing hardware locks (PCIe and USB Dongles)
Occasionally, the failure to remove a device is not a software crash, but a firmware lockup on the Bluetooth controller itself. This is exceptionally common with integrated Intel AX200 and AX210 Wi-Fi/Bluetooth combo cards.
If you are using a USB Bluetooth dongle, the fix is trivial: pull the dongle out of the USB port, wait ten seconds, and plug it back in. This severs power to the transceiver, clearing its internal state. The "Removing device" loop in Windows will instantly abort, and the device will vanish.
If your Bluetooth is integrated into the motherboard (PCIe or M.2), you cannot physically pull it. Instead, you must perform a power drain to clear the static charge holding the firmware state:
- For Desktops: Shut down the PC, flip the switch on the back of the power supply to the OFF position, and unplug the power cable from the wall. Press and hold the PC's power button for 30 seconds to drain the motherboard capacitors. Reconnect power and boot.
- For Laptops: Shut down the laptop and unplug the AC adapter. Press and hold the power button for 60 full seconds. Do not let go early. Boot normally.
| Device Manager Error Code | What it means for removal | Required Action |
|---|---|---|
| Code 43 | Hardware firmware crash | Requires motherboard power drain or dongle removal |
| Code 45 | Device not connected (Ghost) | Uninstall hidden device via View menu |
| Code 10 | Driver stack failure | Reinstall main root Bluetooth controller driver |
Preventing the "Remove failed" error from returning
Once you have successfully purged the stuck device, you need to ensure the system does not immediately hang the next time you pair something. Chronic removal failures are almost always tied to outdated root controller drivers. Windows Update provides generic WHQL drivers that prioritize stability over performance, but they frequently mishandle modern Bluetooth Low Energy (LE) device teardowns.
Do not rely on the "Update driver" button in Device Manager; it only checks the local Windows cache. You must identify your adapter manufacturer (Intel, Realtek, or MediaTek) under the Bluetooth category, navigate to their official support site, and download the standalone executable installer. Installing the manufacturer's proprietary driver package replaces the generic Microsoft `bthport.sys` handling with hardware-specific instructions that execute cleanly during device removal.
Frequently Asked Questions
How to fix Bluetooth device not removing in Windows 11?
Open Device Manager, click View, and check "Show hidden devices." Expand the Bluetooth section, right-click the translucent icon of the stuck device, and select Uninstall device. This forces the removal.
Why is my Bluetooth stuck on removing device?
The Windows Settings app is waiting for a background radio process to confirm disconnection, but that service has crashed. The UI loops infinitely because there is no built-in timeout for this operation.
How do I completely remove a Bluetooth device?
Beyond using the Settings app, you must open the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices, and delete the folder matching the device's MAC address.
Why does it say remove failed when trying to remove Bluetooth?
A "Remove failed" error (most common on Windows 10) indicates that the registry keys governing the device are locked by system permissions, or the Bluetooth Support Service is unresponsive.
How to fix a remove failed Bluetooth error?
Open the Services app (services.msc), locate the Bluetooth Support Service, right-click it, and select Restart. Once the service is running normally, attempt the removal again.
How to fix Bluetooth is turned off when it should be on?
If the toggle switch vanishes, the root hardware controller has crashed. Unplug the PC, hold the power button for 30 seconds to drain motherboard capacitors, and reboot to clear the firmware lock.
How do I force off Bluetooth in Windows?
Open Device Manager, expand the Bluetooth category, right-click your primary Bluetooth adapter (e.g., Intel Wireless Bluetooth), and select Disable device. This forcefully cuts power to the radio at the driver level.
Why is my Bluetooth device not getting removed?
The system maintains ghost entries for Fast Startup. If you use standard rebooting, the locked state persists in the hibernation file. You must hold Shift while clicking Shut down to clear it.
How to get rid of a stuck Bluetooth profile?
Use the Command Prompt utility PnPUtil. Run cmd as administrator, execute pnputil /enum-devices /class Bluetooth to find the instance ID, then run pnputil /remove-device "INSTANCE_ID".
What to do if the Bluetooth support service is stuck on stopping?
Open Command Prompt as administrator. Run tasklist /svc | findstr bthserv to identify the Process ID (PID). Then, run taskkill /F /PID [YOUR_PID] to forcefully terminate the hung service container.
Why am I not getting the Bluetooth on/off option?
The setting vanishes when Windows loses contact with the physical hardware. This requires reinstalling the chipset drivers from your motherboard manufacturer or performing a complete static power drain.
How to manually remove a Bluetooth device via registry?
Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters\Devices in the Registry Editor. Locate the folder bearing the device's MAC address, delete it, and reboot immediately.
How to remove a Bluetooth device that failed previously?
Open Device Manager, enable Show hidden devices from the View menu, and delete the translucent driver profile associated with the failed device. The failed profile is preventing clean removal.
Why won't my Bluetooth device remove after a reboot?
Windows 11 utilizes Fast Startup, which saves the crashed kernel state to the hard drive rather than fully resetting it. A standard reboot reloads the crashed removal queue.
How to remove and reinstall Bluetooth drivers completely?
In Device Manager, right-click your primary adapter and select Uninstall device, ensuring you check the box to remove driver software. Reboot, then run the executable installer provided by Intel, Realtek, or your hardware vendor.
Can Fast Startup cause Bluetooth removing device to be stuck?
Yes. Fast Startup prevents the operating system from cleanly dropping inactive or errored driver states. Holding Shift while selecting Shut down forces a full system reset that clears the queue.
Revision note. Written September 2026, covering Windows 11 25H2 and Windows 10 22H2. Settings paths and core architecture remain identical across recent builds, but future Microsoft changes to the modern Settings app could obfuscate Bluetooth pairing further. I hope this finally gets that stuck peripheral off your screen.