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: Oldest
  1. Anonymous
    2021-08-20T23:32:22+00:00

    I've gotten 36 hours of use of my mouse and keyboard, with 4 hours of continuous use. Sadly, I am now happy if I only have to restart or reattach my BT device every four hours. I used the method described above, which I paraphrase "uninistall both bluetooth AND wifi devices, INCLUDING drivers. Reboot. Make sure your driver is dated 2016. Go into gpedit computer config/administrative templates/windows components/windows update/don't include drivers and enable that so that the next time windows updates it doesn't over-write what you just did."

    For those of us angry at Microsoft, I did a little research. They make only about 3% of their revenue from selling NEW Surface 7's (which don't have the Marvell BT chip, btw). They make 0% of their revenue from supporting SP 5's. They don't care. Why should they? I'm just telling everyone I can think of that MS doesn't support their products. Embarassing them won't help, but it may make me feel better.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-08-21T03:59:22+00:00

    Very disappointing, I have all MS peripherals for this very reason so when something doesn't work the low level IT workers (who don't even work for MS and are "ambassadors") can't point to the non MS peripherals as the problem.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-08-21T11:39:26+00:00

    ...and Windows re-installed the crappy drivers again, in spite of the setting in gpedit. This time, however, it was easily rolled back, but still needed a restart.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-08-21T13:00:34+00:00

    So I called Tech Support on Friday 20 Aug and they said they are aware of the problem, but they have no answer as to why they are taking that long to resolve the issue. After spending 45 minutes with the person on the other line, I realised I am probably still better off at this juncture troubleshooting on my own. Tech Support didn't even know that after installation, "Firmware updates can’t be uninstalled or reverted to an earlier version" (https://support.microsoft.com/en-us/surface/surface-pro-6-update-history-1c611758-6d57-0a45-047b-ac358460033d). Still asked me to click on the button to roll back on the BT driver version. That much is reflected of their competency.

    And .... and.... they were supposed to give me a call back later on Friday cos they couldn't help me after 45min. Guess what? All disappeared without a trace. When I finally managed to find time in between work to call again, "Sorry. Our office is closed for the day".

    I've deleted the driver and rolled back to 2016 v15.68.9112.23. Also updated the Win Update under gpedit.msc. Fingers crossed my BT will now work beyond 45min.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-08-21T16:47:02+00:00

    Thanks for the update, F1. It's good to, at least, finally know that MS Tech Support are aware of the problem so thank you for getting in touch with them.

    Was this answer helpful?

    0 comments No comments