If you are on Windows 7 or Windows 8, you may see a red error.
If you have followed all the steps and the UGreen CM390 still disconnects randomly or fails after sleep, you need to disable USB selective suspend.
Before installing the driver, complete these three steps to avoid conflicts: ugreen bluetooth 50 usb adapter cm390 driver install
Struggling to get your UGREEN CM390 Bluetooth adapter working? You are not alone.
The UGREEN Bluetooth 5.0 USB Adapter (Model: CM390) is one of the most popular dongles on the market. It promises instant wireless connectivity for mice, keyboards, headphones, and game controllers. However, the phrase "ugreen bluetooth 50 usb adapter cm390 driver install" is searched thousands of times per month. Why? Because despite being "plug-and-play" in theory, Windows often fails to automatically load the correct driver. If you are on Windows 7 or Windows
In this 2,500+ word guide, we will walk you through every possible method to install the CM390 driver, troubleshoot common errors, and optimize your Bluetooth 5.0 performance.
Before you give up on your UGREEN CM390, run through this final checklist: Struggling to get your UGREEN CM390 Bluetooth adapter
☐ Physical port: Avoid USB 3.0 ports (blue inside). Use USB 2.0 (black/grey). USB 3.0 emits radio noise that kills Bluetooth 2.4GHz signals. ☐ USB Extension cable: If the dongle is plugged into the back of a metal tower PC, use a short USB 2.0 extension cable to bring the adapter into open air. This doubles range. ☐ Disable onboard Bluetooth: If your laptop has built-in Bluetooth, disable it in BIOS or Device Manager. Two active Bluetooth radios will conflict. ☐ Run the official UGREEN tool (Method 4) even if Windows says the driver is installed. It cleans orphaned registry keys. ☐ Restart, don't shut down. Windows Fast Startup often prevents Bluetooth drivers from loading correctly. After install, do a full Restart (not Shutdown + Power on).
Cause: The CM390 uses a hideable boot mode. Some apps (like Bluetooth tray apps) hide audio devices.
Fix: