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

198 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-08-19T12:41:19+00:00

    It's working

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-08-20T00:58:19+00:00

    Thanks so much - I figured this (a nuclear option) was the only one that would work. Much appreciated!

    BTW I contacted MS (a helpful guy but over chat it took forever) and he gave me three driver updates to make. I followed his instructions and...still not fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-08-20T01:03:21+00:00

    My last update was August 10 (which is when things started to go sideways with BT). That package included the removal of Flash. I wonder if that had anything to do with this issue. I am not an IT expert. I am not showing any updates available, please let us know if this package fixed your BT issue. Thanks!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-08-20T12:00:15+00:00

    I have this EXACT problem. Bluetooth dies within an hour and it disappears. I read through and still looks as if there is no fix?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-08-20T14:30:55+00:00

    Hi Mark. Thanks for your post. No, disappointingly, there hasn't been a fix come through from MS as yet (now two weeks in). There are a number of workarounds suggested here, but none, I believe, provide a permanent solution. Can you please post the details on the Feedback Hub or upvote my feedback there please (https://aka.ms/AAdjn6t) if it fits your issue? Thanks

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments