Ouch. You took one for the team
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: Oldest
-
Anonymous
2021-08-29T21:59:28+00:00 -
Anonymous
2021-08-30T10:56:38+00:00 I did a complete reinstall of Windows 10; worked fine for a couple of days, then it started all over again. Got myself a Asus 500 BT usb-dongle; worked fine, but it also starts to give similar problems now... (switched Marvel BT off before installing the Asus). MS please fix this problem..!!
-
Anonymous
2021-08-30T15:38:53+00:00 hey. i tried this and i think it works!!
i'm from small country in asia / and even i'm not an english speaker / but i really should reply on this method.
it works. it works.
-
Anonymous
2021-08-30T23:44:30+00:00 I chatted with a Surface rep who claims he is " ... log(ging) a special escalation to Higher Support to have this incident be investigated thoroughly."
-
Anonymous
2021-08-30T23:45:27+00:00 This was after another rep recommended I run the Surface Diagnostic Tool - but it was Surface 3's and later. Not Surface 2. Why do I not have a lot of confidence this will ever be fixed?