Ensure USB Bluetooth dongle is passed through to the guest OS, or use a bridged Bluetooth adapter if supported.

If you are reading this, you have likely just been greeted by a small but incredibly frustrating dialog box. You double-clicked an application (often a PS3 controller tool like SCP Toolkit or a similar Bluetooth driver utility), and instead of your program launching correctly, you saw the ominous red text:

"bthps3 Bluetooth host radio not found."

For many users, this error is a brick wall. It stops you from pairing your PlayStation 3 controller to your PC, using specific Bluetooth dongles, or running legacy emulator tools. The immediate assumption is often that your Bluetooth hardware is broken. In 95% of cases, that is false.

This 2,500+ word guide will explain exactly what this error means, why it happens, and—most importantly—provide a step-by-step roadmap to permanently fix it.

Sometimes the hardware exists but is disabled at the system level.

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:

Though rare, the internal Bluetooth card (often combined with Wi-Fi on a single M.2 or PCIe card) can fail. Alternatively, a loose internal antenna connection can cause the radio to appear "not found."

sudo systemctl restart bluetooth
sudo hciconfig hci0 up   # if hci0 exists

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.

This is the gold standard. Many users have conflicting drivers from older attempts.

Step A: Uninstall Everything Bluetooth (Carefully)

Step B: Remove Hidden Drivers

Step C: Isolate the bthps3 Driver

Step D: Reboot and Reinstall Fresh

Bthps3 Bluetooth Host Radio Not Found 【Best ⟶】

Ensure USB Bluetooth dongle is passed through to the guest OS, or use a bridged Bluetooth adapter if supported.

If you are reading this, you have likely just been greeted by a small but incredibly frustrating dialog box. You double-clicked an application (often a PS3 controller tool like SCP Toolkit or a similar Bluetooth driver utility), and instead of your program launching correctly, you saw the ominous red text:

"bthps3 Bluetooth host radio not found."

For many users, this error is a brick wall. It stops you from pairing your PlayStation 3 controller to your PC, using specific Bluetooth dongles, or running legacy emulator tools. The immediate assumption is often that your Bluetooth hardware is broken. In 95% of cases, that is false. bthps3 bluetooth host radio not found

This 2,500+ word guide will explain exactly what this error means, why it happens, and—most importantly—provide a step-by-step roadmap to permanently fix it.

Sometimes the hardware exists but is disabled at the system level.

Run PowerShell as Administrator and execute: Ensure USB Bluetooth dongle is passed through to

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:

Though rare, the internal Bluetooth card (often combined with Wi-Fi on a single M.2 or PCIe card) can fail. Alternatively, a loose internal antenna connection can cause the radio to appear "not found."

sudo systemctl restart bluetooth
sudo hciconfig hci0 up   # if hci0 exists

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. Sometimes the hardware exists but is disabled at

This is the gold standard. Many users have conflicting drivers from older attempts.

Step A: Uninstall Everything Bluetooth (Carefully)

Step B: Remove Hidden Drivers

Step C: Isolate the bthps3 Driver

Step D: Reboot and Reinstall Fresh