Same problem on a Surface Book 2. Hope they get this fixed soon or I may have to (gasp) buy a wired mouse.
Bluetooth Issues Since Surface Updates - 5 August 2021
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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: Newest
-
Anonymous
2021-08-14T16:06:49+00:00 -
Anonymous
2021-08-14T15:43:47+00:00 I have two (2) surface pro 6s and neither has an bt audio device and our sufaces
blows up multiple times a day.
-
Anonymous
2021-08-14T09:48:18+00:00 Thanks Barb. I did that a few days and urged others to submit feedback, but your reminder is very useful, thank you.
-
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator2021-08-14T09:40:52+00:00 Can you (any everyone else impacted) use the Feedback Hub App to file a problem report on this with as much detail as possible, especially the possible link to audio devices being the trigger for the issue? The engineers won't scrape the forum for bugs and info..
-
Anonymous
2021-08-14T07:05:13+00:00 Hi MFO. Many thanks for all that you have done to try and diagnose the problem. It's now been 9 days since the issue emerged, so hopefully Microsoft will have seen all of the posts here and elsewhere and will have a fix soon.