Bluetooth Issues Since Surface Updates - 5 August 2021

Anonymous
2021-08-05T10:04:04+00:00

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.

0 comments No comments

198 answers

Sort by: Newest
  1. Anonymous
    2021-08-12T20:44:12+00:00

    I'm on a surface pro 6, same issue. I can get Bluetooth working temporily for a short period and then it stops again. Yesterday at one point the option for turning Bluetooth on and off completely disappeared until I ran the troubleshooter. It's a real pain as I use a Bluetooth keyboard, mouse, headphones etc. DESTROYING MY WORKFLOW.

    I remember a similar issue from over a year ago but that was patched by an update.

    Microsoft, can u please tell us if u are working on a fix?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-08-12T16:44:34+00:00

    Just a quick update, further to my post yesterday, I find that when my phone is close to the Surface and well within BT range, the BT issue is pretty constant. If I leave the phone well away from the Surface, I don't experience the problem, If I move it a little closer, the BT connection (particularly to my mouse) comes and goes, but doesn't switch off. So, you may be right, Thomas, that it is something to do with the number or type of BT devices connected/trying to connect.

    I would really like to hear from Microsoft (MS). I haven't heard from anyone, apart from those affected, for about a week. There are obviously many people experiencing this issue with various Surface models since the Firmware Update on c. 5 August 2021. It would be very good if MS would acknowledge the issue, reassure us that a fix is being worked on and give a timescale when it is to be resolved, as this is having a very detrimental effect on my, and I'm sure others' efficiency and productivity.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-08-12T02:51:56+00:00

    The same issue is happening on my Surface Pro 6, and none of the prescribed remedies do anything other than restore functionality for about 5 minutes upon restart.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-08-11T18:45:49+00:00

    Thanks Thomas. I have a BT mouse and. BT keyboard. BT seems more stable with just those two connected, but connecting with 'Your Phone' seems to make it unstable. I can't spend much more time on this, but I will try to check on what is connected / disconnected when the problem occurs and feed that back.

    Was this answer helpful?

    0 comments No comments
  5. 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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments