Bthps3 Bluetooth Host Radio Not Found Work May 2026

Here’s a short story based on that error message.

Leo stared at the terminal, the green cursor blinking like a slow, mocking heartbeat.

“Bluetooth host radio not found.”

He’d typed the command for the third time. systemctl restart bluetooth. Then hciconfig. Then the incantation he knew by heart: bluetoothctl power on. Each time, the same cold, mechanical reply.

No radio.

It was 2:17 AM. The server room hummed with the low drone of cooling fans, a sound that usually calmed him. Tonight, it felt like a held breath.

The little USB Bluetooth dongle—a cheap, barely-named piece of plastic—was supposed to be the brains of his reverse-engineered headphone hack. He was trying to spoof an old car’s hands-free system, to make a pair of vintage 90s headphones talk to his Linux box. Instead, the kernel had simply… forgotten the radio existed.

He pulled the dongle out. A soft click. He pushed it back in.

dmesg | tail

Nothing. No USB disconnect. No new device. Just silence.

“You’re not even trying to fail,” he whispered to the computer. “You’re just pretending it never existed.”

He thought back to the afternoon. A clumsy knock, the dongle taking a hit against the edge of the desk. It had worked after that. Or had it? He’d paired his mouse, played a song. But maybe that was a ghost. Maybe the radio had been dying all day, spewing packets from a wounded heart.

He ran lsusb. The dongle’s chipset ID appeared. So the hardware was there. The kernel saw it on the bus.

Then why?

rfkill list. No soft block. No hard block.

The error wasn’t a hardware failure. It was a story failure. The host radio—that magical bridge between the plastic dongle and the invisible ocean of 2.4 GHz spectrum—had a name, an address, a soul inside the driver. And the driver had simply decided: not found.

Leo leaned back. The chair creaked.

He’d been debugging for three hours. He’d purged bluez, reinstalled from source, blacklisted btusb, reloaded it. He’d even tried the Windows driver via ndiswrapper—an act of desperation he’d never admit to.

None of it mattered. The radio was there. The radio was not there. Schrödinger’s Bluetooth adapter.

He reached for his phone. Maybe a quick search. But even as he typed, he knew the answer wouldn’t be in a forum. It would be in something stupid. A bad solder joint. A corrupted firmware blob. Or maybe the dongle simply reached its ten-thousandth power cycle and, like an old lightbulb, chose the moment of the knock to burn its last bridge. bthps3 bluetooth host radio not found

He unplugged it one last time. Held it in his palm. Tiny, black, unmarked. A gravestone no larger than a fingernail.

“You were never found,” he said.

Then he threw it in the trash, ordered a three-pack from Amazon, and went to bed—where the blinking cursor of his dreams still searched, endlessly, for a radio that had already left the building.

"Bluetooth Host Radio not found" error when installing typically occurs because the setup cannot detect a working Bluetooth stack or the radio is locked by an incompatible filter driver

. This issue often affects users trying to connect PlayStation 3 controllers to Windows using tools like Core Troubleshooting Steps

If you are seeing this message during setup, follow these steps to restore visibility to the radio: Check Hardware Status External Dongle

: Ensure it is firmly plugged in. Try a different USB port, preferably a USB 2.0 port if using a 3.0 port. Laptop Users

: Verify that the physical wireless switch or key combination (e.g., Fn + F2) has not disabled the Bluetooth radio. Remove Incompatible Legacy Drivers

BthPS3 requires stock Windows Bluetooth drivers to function. Completely uninstall older solutions like ScpToolkit

, as they replace the stock driver stack and hide the radio from BthPS3. Clean the Registry Filter

A damaged installation can leave a "LowerFilter" in the registry that blocks the radio from starting. Open PowerShell as Administrator and run the following command to remove it:

Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Class\e0cbf06c-cd8b-4647-bb8a-263b43f0f974' -Name 'LowerFilters' your PC immediately after running this command. Restart the Bluetooth Support Service services.msc , and find Bluetooth Support Service Ensure the "Startup type" is set to if it is stopped. Compatibility and Limitations LMP Version Check : BthPS3 requires a Bluetooth host with LMP version 3.0 (Bluetooth 2.0 + EDR) or higher. You can check your version in Device Manager

by right-clicking your Bluetooth adapter > Properties > Advanced tab. Error Code 10

: If you see a "Code 10" (STATUS_DEVICE_POWER_FAILURE) in Device Manager, your Bluetooth card is likely too old or incompatible, and there is no software fix. Unsupported Hardware

: Most hosts from the last decade work, but some specific chips (often found in very cheap off-brand dongles) are fundamentally incompatible.

For detailed technical logs or to verify your hardware against a community-maintained list, consult the official BthPS3 Documentation Are you using an integrated Bluetooth chip USB dongle for this setup?

Frequently Asked Questions - Nefarius™ Project Documentation

When the BthPS3 installer or companion tools throw the "Bluetooth host radio not found"

exception, it typically indicates a breakdown between the driver's filter requirements and the physical Bluetooth adapter's state. This error is common during the installation or uninstallation of Nefarius BthPS3 drivers Here’s a short story based on that error message

, which are designed to enable PS3 controllers (DualShock 3/Sixaxis) on Windows. Core Causes Corrupted Registry Filters

: BthPS3 uses "LowerFilters" to intercept Bluetooth traffic. If an install or uninstall fails, these filters can become "zombies"—references in the registry that prevent the radio from initializing because the associated driver file is missing or broken. Hardware Incompatibility

: Certain modern Bluetooth 5.0+ dongles (like the Baseus BA04) or very old adapters may not support the specific PSM (Protocol/Service Multiplexer) patching required by BthPS3. Driver Conflict

: Residual drivers from ScpToolkit, AirBender, or old Shibari installations can block BthPS3 from claiming the radio. Essential Fixes Clear Zombie LowerFilters (The Most Common Fix)

If your Bluetooth radio has a yellow exclamation mark in Device Manager with a Code 10 or Code 31 error, you likely have a stuck registry entry. PowerShell as Administrator Run the following command to remove the filter requirement:

Remove-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Class\e0cbf06c-cd8b-4647-bb8a-263b43f0f974' -Name 'LowerFilters' your computer. Toggle the Radio State

The installer sometimes fails to "re-awaken" the radio after applying drivers. Device Manager

Locate your Bluetooth adapter (e.g., "Generic Bluetooth Radio"). Right-click it, select Disable device , wait 5 seconds, and then select Enable device Use the "Legacy" Install Mode

Recent versions of the BthPS3 installer offer a "Modern hot-plug" vs. "Legacy sequential" mode. If your radio isn't found during a modern install, try running the installer again and selecting

. This method is more compatible with older or "shitty" radios but requires a full system restart to finish. Verify Bluetooth Support Service

Ensure the core Windows Bluetooth service is actually running. services.msc , and find Bluetooth Support Service When to Replace Hardware If you consistently see Code 10 (STATUS_DEVICE_POWER_FAILURE) after trying the registry fix, the documentation from Nefarius™ Project Documentation

states there is often no software fix; your Bluetooth dongle is likely incompatible with the custom protocol patching BthPS3 requires. manually remove old ScpToolkit drivers that might be causing this conflict?

Frequently Asked Questions - Nefarius™ Project Documentation

The "BTHPS3 Bluetooth Host Radio Not Found" error is a common roadblock for users trying to connect PlayStation 3 controllers (DualShock 3) to a PC using the BTHPS3 driver. This error typically signifies a communication breakdown between the driver and your Bluetooth hardware. Common Causes

Driver Conflicts: Leftover files from ScpToolkit or older DS4Windows versions.

Hardware Incompatibility: The Bluetooth dongle may not support the necessary protocols.

Disabled Services: Essential Windows Bluetooth services are stopped.

Signature Issues: Windows blocking the driver because it isn't digitally signed or recognized. Step-by-Step Fixes 1. Perform a Clean Reinstall

The most frequent cause is a "dirty" installation where old drivers interfere with the new BTHPS3 setup. Leo stared at the terminal, the green cursor

Uninstall BTHPS3 and any related software (like Nefarius' Handlers) via Programs and Features.

Open Device Manager, find your Bluetooth adapter, right-click, and select Uninstall device (check "Delete the driver software for this device"). Reboot your PC.

Install the latest version of the BTHPS3 driver and the Shibari or DsHidMini provider. 2. Check Service Status

If the Bluetooth Support Service is disabled, the host radio will never be "found." Press Win + R, type services.msc, and hit Enter. Locate Bluetooth Support Service.

Ensure the Status is "Running" and Startup Type is "Automatic." 3. Verify Bluetooth Hardware Compatibility

Not every Bluetooth adapter can "handshake" with a PS3 controller.

Ensure your adapter is at least Bluetooth 2.0 + EDR (Enhanced Data Rate).

Avoid using "Generic Bluetooth Radio" drivers. Try to find the manufacturer-specific driver (Intel, Broadcom, Realtek) for your hardware. 4. Use the Filter Installer

If you are using DsHidMini, the "Host Radio Not Found" error often means the filter driver isn't properly attached to the hardware. Run the BthPS3_Bluetooth_Filter_Installer.

This tool specifically tells Windows to route the Bluetooth radio through the BTHPS3 stack instead of the default Windows stack. Troubleshooting ScpToolkit Remnants

If you previously used ScpToolkit, it likely "wiped" your Bluetooth stack. Use the ScpToolkit Clean Wipe Utility.

This is a separate executable usually found in the ScpToolkit installation folder.

Without this, the BTHPS3 driver will constantly fail to claim the radio. Summary Checklist

📍 Check Device Manager: Does a "BTHPS3 Bluetooth Adapter" appear under Bluetooth?📍 Battery Level: Ensure your DS3 controller is charged; low power can cause sync timeouts.📍 Reset Controller: Use a paperclip to press the tiny reset button on the back of the DualShock 3.

If you tell me which software (DsHidMini or Shibari) and Windows version you're using, I can give you a more specific fix.

Understanding BthPS3

  • BthPS3: This seems to relate to a Bluetooth host adapter or a similar technology designed to enable communication between a device (often a computer) and a PS3 (PlayStation 3) controller or other Bluetooth devices. The term might be specific to a driver, software, or hardware solution that facilitates this connection.

Check the Driver Binding via PowerShell

Run PowerShell as Administrator and execute:

Get-PnpDevice | Where-Object $_.Class -eq "Bluetooth" | Format-List Status, Problem, FriendlyName

If your radio shows Status: Error or Problem: 28 (driver not installed), the binding failed. You may need to manually install the generic Microsoft Bluetooth driver:

  1. Device Manager > Right-click your Bluetooth radio > Update driver.
  2. Browse my computer > Let me pick.
  3. Select Generic Bluetooth Radio (Microsoft driver) – NOT the vendor-specific one.
  4. Install, reboot, and re-run the bthps3 installer.

Solution 3: Reinstall the BthPS3 Driver (For DS3Windows Users)

If you are using modern tools like DS3Windows, the BthPS3 driver is required for PS3 controller support. If the installation was interrupted, the service won't start.

  1. Open DS3Windows.
  2. Go to the Drivers tab.
  3. You should see BthPS3 (Bluetooth).
  4. Select it and click Uninstall.
  5. Once uninstalled, click Install again.
  6. Crucial Step: During installation, Windows Security may prompt you to approve the driver installation (Windows Security -> Install this driver software anyway). You must accept this, or the driver will fail silently.
  7. Restart your computer.