Hello, Eric Tucker
Welcome to the Microsoft Community.
Hello, thank you for your feedback here on your issue with Bluetooth devices failing to reconnect or behaving abnormally after resuming from sleep mode.
I will provide you with some potential solutions and also recommend some USB Bluetooth adapters as an alternative.
- Update the driver program:
Make sure your Bluetooth drivers are up to date. Usually, Windows Update does not always provide the latest drivers. You can download the latest driver directly from the manufacturer's website (e.g. Intel Bluetooth adapters need to be updated from Intel's official website, Realtek Bluetooth adapters need to be updated from Realtek's official website).
- Chipset drivers: Update your motherboard chipset drivers, these drivers sometimes affect PCI-E or USB ports, which may affect how the Bluetooth adapter initializes after sleeping.
- Check the power management settings:
You've already mentioned disabling the “Allow the computer to turn off this device to save power” option, but it's still recommended to double-check all settings related to power management:
Device Manager: Go to Device Manager > Bluetooth > [your Bluetooth adapter], right click, select “Properties” > “Power Management” tab, make sure “Allow computer to turn off this device to save power” is unchecked. “is unchecked.
Power Plan Settings: In Control Panel > Power Options, make sure your power plan settings do not allow USB or Bluetooth to save power while hibernating.
- Disable Fast Startup:
Fast startup sometimes causes the peripherals to not work properly after resuming from sleep mode. You can try to disable it:
Go to Control Panel > Power Options > Select the function of the power button.
Click Change currently unavailable settings.
Uncheck Enable fast startup (recommended).
- Uninstall and reinstall the Bluetooth driver:
Even after reinstalling the driver, the problem may still persist due to corrupt settings. In Device Manager, right-click on your Bluetooth device and select Uninstall Device, then restart your computer. After restarting, Windows should automatically reinstall the Bluetooth driver. If it doesn't install automatically, you can install it manually.
- Registry tweaks:
In some cases, modifying specific registry settings can help resolve hardware initialization issues after resuming hibernation. However, modifying the registry should be done carefully to avoid improper modifications affecting system stability. Some users are advised to modify registry entries related to power management, such as HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTHPORT\Parameters.
Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.
- Update BIOS/UEFI:
Some users have found that updating the BIOS or UEFI firmware solves the problem of hardware not re-initializing correctly after sleep. If you are using a PCI-E Bluetooth card or USB Bluetooth adapter, you can visit the motherboard manufacturer's official website to see if there is a relevant firmware update.
- Alternative Solution: Using a USB Bluetooth Adapter
If Microsoft and driver updates can't solve the problem, you can consider using an external USB Bluetooth adapter to bypass the built-in Bluetooth adapter. Here are some common and Windows 11 compatible USB Bluetooth adapter brands:
TP-Link, Plugable, ASUS, Avantree and other brands are good choices
These USB adapters are usually plug-and-play, so they should be able to fix the problem easily. Simply disable the built-in Bluetooth adapter in Device Manager (if possible) to avoid conflicts with external adapters.
Best regards
Bobhe | Microsoft Community Support Specialist