Hello everyone. I have some good news. My Surface this morning installed the driver mentioned in Barb's post and it is working without interruption (so far). I had to uninstall the Realtek driver for my plug-in USB BT device, before the Marvell driver would install, but after that and after re-linking my devices, all seems well. So I hope you can all do the same very soon.
Bluetooth Issues Since Surface Updates - 5 August 2021
The Bluetooth on my Surface Pro (5th Gen) has not been working properly since the Surface Firmware Updates this morning. I have to restart to get it to work and then it only works properly for about 5 minutes. I have tried rolling back and reinstalling the Marvell driver. Also the Bluetooth troubleshooter doesn’t fix it. Running that troubleshooter causes Bluetooth to completely stop working. Will you please fix this urgently as it is a major issue for me?
***Moved from: Windows / Windows 10 / Devices & drivers***
Surface | Surface Pro | Network
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
198 answers
Sort by: Most helpful
-
Anonymous
2021-11-23T11:12:22+00:00 -
Anonymous
2021-08-11T18:34:22+00:00 I just want to giva an update from my machine with the issue. The last update (KB5005033) did some changes but didnt solve the problem. Now i get an yellow sign in the devicemanager after the bluetooth broke.
But there are also good news. When i only connect the mouse (Logitech M557) and the keyboard ( Logitech K810) the bluetooth connection seems to be stable for many hours. If i connect the Avantree Oasis, a music streaming device, after maybe 15-30 minutes i face the problem that all connections are lost and the bluetoots symbol is gone. So maybe there is a problem with sound and streaming devices like phones or headsets some people here posted earlier.
Perhaps we all could try and use just some bluetooth devices and check the connection stability to isolate the problem to a buggy protocol.
-
Anonymous
2021-08-10T01:14:01+00:00 Checking in to report that sadly, changing to a generic Bluetooth driver did not work for long either. It's still showing as a Generic Bluetooth Adapter in my Device Manager, but when I check its properties, it also says "No drivers are installed for this device".
This continues to be a huge problem. Hopefully, Microsoft understands this. It's unfortunate that no one from Microsoft has responded since your initial post 3 days ago as I've no doubt there must be multiple reports of this issue beyond this thread😕
-
Anonymous
2021-08-09T22:00:49+00:00 Agreed, and yes the solution did fail after a while. At least this time when I ran the windows updater it actually detected the missing driver and ran the update. We'll see how long it last this time. And yes, it's excruciating to not have Bluetooth working when your workflow is designed to work with Bluetooth peripherals. I'm a graphic designer and right now I'm forced to use one of those crappy all-in-one keyboards I use for my media centre because it can connect via dongle. I've already wasted so. much. time. trying to figure this out and am getting no actual work done.
TrevorFayers, have you tried rolling back to previous driver to see if that helps? Found this from a few years ago where people were having the same problem and changing to a generic BT driver seemed to fix their problem... https://www.surfaceforums.net/threads/solved-marvel-avastar-bluetooth-radio-adapter-error.24310/
I've not tried it yet though. I think it's time to walk away from the computer for a while and come back when I feel less like using it like a shot put😖
Edit: And it stopped working again. Will be trying the above link's solution later and report back.
-
Anonymous
2021-08-09T20:50:42+00:00 Thanks for letting me know Gfernandez. I'm afraid that, like for me, you may find that even the temporary solution fails after a while. I also have a monitor with Bluetooth keyboard and mouse, so extremely frustrating and very inefficient to not have Bluetooth working!