Long 3 hours? ;-) Joking aside, you have us all on pins-and-needles. What happened?
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-09-03T16:18:24+00:00 -
Anonymous
2021-09-01T14:53:35+00:00 Be strong and of good courage,. Help may be on the way (though I have thought that before).
The High Command from Redmond is calling me in three hours. Maybe they will have something of value that will get us over this hurdle and on to the next challenge.
I will report back after the call. Providing they follow through on their commitment.
-
Anonymous
2021-09-01T07:37:57+00:00 oh god... this bluetooth issue is driving me bonkers....
but i'm so glad i found this thread to know i'm not alone!!!!
surfacebook 2 user here...
PLEASE HELP US MICROSOFT!!!!!!
-
Anonymous
2021-08-31T18:04:43+00:00 Many thanks again for your persistence, dave2013, and all the time you must have spent on the issue. I’m sticking with using wired devices just now, until MS fix the issue. Hopefully, with the escalation, that will be sooner rather than later.
-
Anonymous
2021-08-31T00:04:20+00:00 I bought a USB Bluetooth adapter (5.0), installed it, and uninstalled/disabled my built-in Bluetooth. It's working fine, but I resent having to do this because of software glitches. Please patch this problem soon; I just have a strong suspicion that this is the result of Windows 11.