Adapter stops working once it comes back to life from sleep mode
Adapter stops working once it comes back to life from sleep mode
Hello everyone! My issue matches this one, but the discussion never came to a conclusion. So I’m moving on. Here’s how I recreate the problem for myself: Turn on my PC, go into sleep mode, then wake from it. At that stage, the BT driver stopped working. Restarting resolves it. Hibernation is functioning correctly too. I have a PCI WiFi + Bluetooth adapter. The WiFi works fine, but the BT driver keeps crashing. To see it clearly: 1. Bluetooth vanishes in this panel; 2. Device Manager lists BT adapter as disabled due to "reported problems"; 3. The "Events" section shows it tried to start with a null driver ({00000000-0000-0000-0000-000000000000}). 4. A kernel-PnP error appears: Spoiler - Event ID 411. 5. The status is "null" driver, which doesn’t make sense. 6. PC specs: Microsoft-Windows-Kernel-PnP v9c205a39-1250-487d-abd7-e831c6290539. Any fixes would be appreciated.
Hey, that was me too—still can't find a fix. BT keeps messing up even after sleeping, and M$ is really frustrating!
I experimented with a PowerShell script that automatically restarts Bluetooth devices and shows a notification. It’s a simple solution that works for me. The script executes only in the legacy PowerShell version (the built-in one on Windows) and can be scheduled via Task Scheduler. I’m using a configuration where the script is placed at %appdata% and runs with full privileges.
The task config looks like this:
- Application: PowerShell
- Arguments: -WindowStyle hidden %appdata%\begone_bt.ps1
- Path to the file: %appdata%\MyScript.ps1
Make sure to run it with maximum permissions.
A function named Show is defined to display a notification using Windows UI controls. It takes two parameters: a title and optional text.
The script uses XML templates to build a toast message based on device status. It appends the appropriate content to the template, serializes it, and then displays the notification in the system tray.
It loops continuously until stopped, checking for Bluetooth devices with errors. If found, it prompts to disable or enable them, showing a friendly alert when changes happen.
The trigger for "At Startup" in Task Scheduler is set during task creation or modification. You define it in the task properties under the "Startup" option.
I configured it for "on user login." Just avoid frequent logins and it should work. You could also try "at startup" and let me know if that helps.
Nah.. Since a few weeks I cannot even disable/reenable after sleep, windows tells me that there's a "harware change" (wtf ??) and needs a reboot Have to disable sleep altogether..