Bluetooth Issues Since Surface Updates - 5 August 2021

Hi SamLim1, welcome to our Windows Update Support Group lol. Many of us have been dealing with this for the last couple weeks as you can see from this thread being 7 pages deep. That said, so far for myself, I have found 2 solutions if you're in dire need (which it sounds like you are).

1. An external USB Bluetooth dongle should get your pen up and running as it appears to be a conflict between the recent windows update and Marvell's bluetooth adapter driver. I tested the ASUS Bluetooth USB-BT500 and it worked great. That said, it also set me back $30 CDN and uses the solitary usb port available, so obviously not a long term solution. Mostly, it just solidly verified the issue lay with the marvell driver.
2. You can try rolling back the driver and disabling driver updates to keep it at its rolled back status. I found this solution on another thread in this forum and so far it is working and has kept me operational the longest in the last 2 weeks (other than switching to the USB BT adapter). You'll need to uninstall the Marvell Bluetooth Adapter in your Device Manager (be sure to check uninstall drivers as well) and then restart. When you restart, you will need to access your Group Policy Editor and enable Do not include drivers with Windows Update to prevent windows from auto-updating the drivers you just rolled back. If you scroll back a page or two, you should be able to view more detailed instructions on how to do this all.

Ymmv, but hopefully that gets you up and running long enough to get some work done!

Hi everyone,

I have a surface pro 5 and can confirm that there are issues with the most recent windows update which made bluetooth wonky.

Some of my symptoms are:

1. bluetooth mouse disconnects and reconnects itself intermittently.
2. surface pen does not write properly. It will start writing itself even without touching the surface screen while hovering with the pen. This makes the pen almost impossible to use. I'm a teacher and require the pen daily as my teaching tool. This issue has totally wrecked my surface pro experience.
3. surface keyboard will not connect when it's connected to the surface at the 45 degrees angle. To make it work, I need to move it away from the screen and let the keyboard lie flat. Only then, will the keyboard respond.

Above issues are pressing issues as I had a perfectly working surface pro before the most recent firmware updates in August like what others have experienced here. If others have experienced such issues, I hope microsoft could roll out an update soon as you guys have disabled the ability to rollback updates.

Will try, thanks!

Yeah, I tried that solution last week early on, I don't connect to any VPNs and it still stopped working for me as well. I am currently using the solution I last posted about (likely right above this post). Perhaps you can try it and see if it works for you?

No problem, Trevor. Now that I've verified it's Marvell specific, I'm troubleshooting in a more targeted manner. Came across this other thread https://answers.microsoft.com/en-us/surface/forum/all/bluetooth-is-turned-off/351ed271-b0fc-4bdd-82ba-e8afb2624505?auth=1&page=2](https://answers.microsoft.com/en-us/surface/forum/all/bluetooth-is-turned-off/351ed271-b0fc-4bdd-82ba-e8afb2624505?auth=1&page=2) and and am currently trying user [DavidDalton2's suggestion (see below):

It appears that I may have temporarily fixed the problem. It's been two days and running, with several reboots and many sleep/wake cycles. Hopefully this fix is good and will last until MS gets their act together and releases some good drivers. Again, my tablet is a Surface Pro 6, 21H1, OS Build 1943.1083, and Bluetooth is missing, so in my case, no pen or MS BT mouse. Steps to repair:

1. Go to device manager.
2. Uninstall Bluetooth>>Marvell AVASTAR Bluetooth Radio Adapter. When you uninstall it, delete the driver (an option on the Uninstall dialog box).
3. Uninstall Network adapters>>Bluetooth device. Delete the driver. This is the action that actually fixed it.
4. Reboot. W10 will reinstall both these devices with earlier drivers. In my case, the AVASTAR adapter is now at Version 15.68.9112.23, Date 12/02/2016. The Network adapter Bluetooth device is now at Version 10.0.1941.1, Date 6/21/2006.

If that fixes it, the next effort is to ensure that it remains fixed until MS releases good drivers, as the update process will constantly reinstall the latest level drivers on your behalf (we're Microsoft and we are here to help!) and it will fail again. If you have access to the Group Policy Editor (gpedit.msc), you can turn off driver updating. Run gpedit and go to Computer Configuration>>Administrative Templates>>Windows Components>>Windows Update>>Do not include drivers with Windows Updates, Open it and push the Enable button. Done.

However, if you are running W10 Home, gpedit is not normally available. I understand that you can still get to it by installing the Policy Plus application. I run Policy Plus on my W10 Pro devices so can't verify for sure whether it will actually run on Home, but that's what they say. It is more robust than gpedit, allowing the user to filter the display, so I often use it instead of gpedit.

*Now you have to research the driver updates as they are released to determine whether they will permanently fix the problem and if so install them manually.*So I've somewhat followed the directions above and my Bluetooth radio adapter driver is now rolled back to the same as above with same date as well (as we've all done multiple times already lol). I did not bother uninstalling the network adapter device as it currently matches the version and date above). I did, however, run gpedit and turned off driver updating in Windows updates. Things have been running smoothly since my last post, so about an hour or so which is the longest it's lasted the last couple weeks. Fingers crossed it continues, I will report back either way.