In some cases, booting from a "Live USB" of Ubuntu, turning on Bluetooth there, and then rebooting back into Windows has been known to "kickstart" the radio hardware. HP Support Community Long-term Solutions
Ralink RT3290 Bluetooth adapter is a legacy combined Wi-Fi and Bluetooth card that frequently experiences significant compatibility issues with modern versions of Windows 10
The RT3290 is notorious for hardware failure or becoming "invisible" on Windows 10 builds past version 1803. If drivers do not fix the issue, consider: HP Support Community ralink rt3290 bluetooth driver for windows 10 64 bit ralink rt3290 bluetooth driver windows 10
(released June 18, 2015). While newer Windows builds may automatically attempt to install generic drivers, they often cause the device to disappear or fail with errors. HP Support Community Official Download Link: HP SoftPaq sp71572 (direct download from HP servers). Microsoft Catalog: Alternatively, you can search for updated drivers on the Microsoft Update Catalog Installation & Troubleshooting Steps
If the driver fails to install or the Bluetooth icon does not appear, follow these steps: Manual Update via Device Manager: Right-click the button and select Device Manager In some cases, booting from a "Live USB"
. Because the card is no longer actively supported by its manufacturer, MediaTek (which acquired Ralink), finding a stable, working driver for the latest Windows updates can be difficult. HP Support Community Recommended Windows 10 Driver
, and choose "Browse my computer for drivers" to point to the location where you extracted the driver files. BIOS Toggle: While newer Windows builds may automatically attempt to
Find the "Ralink Bluetooth" or "Generic Bluetooth Adapter" under Right-click it, select Update Driver
If the adapter is missing from Device Manager, restart your PC, enter the
, disable Bluetooth, save and exit, then restart and re-enable it in the BIOS. Disable Driver Signature Enforcement:
If you receive a digital signature error, you may need to temporarily disable driver signature enforcement during installation. Ubuntu Workaround: