Bluetooth Issues Since Surface Updates - 5 August 2021

Hi TrevorFayers,

Thank you for reaching Microsoft Community.

To make sure first: May I know which Surface Pro model do you have? Surface Pro 7 uses the Intel Wireless Bluetooth adapter, not the Marvell AVASTAR Bluetooth Radio adapter.

For the issue you are experiencing, your Bluetooth devices connected on the device connected for only about 5 minutes after the update and now none of your Bluetooth devices connects to the device, correct?

May I know what is the current version of the Bluetooth Radio adapter installed on the device? Go to Device Manager, expand Bluetooth and double-click on the Bluetooth Radio adapter then go to its Driver tab. Take note of the Driver version.

Kindly run these steps below first on your Surface then see if the issue persist:

1: Run Surface Diagnostic Toolkit and check Windows Update

2: Update drivers and firmware

                               Check what is the current OS Build of your Windows version by going to Settings > System > About.

                               Go to Download driver and firmware for Surface, choose your Surface model then click Download on the next page.

                               Choose the .msi file that matches your current OS Build and click Next.

                               After downloading, run and install the .msi then Restart.

3: Uninstall/Re-install

Open Device Manager, expand Bluetooth

Right-click the Bluetooth Radio adapter and choose Uninstall device

Note: Leave box uncheck to Delete the driver software

Restart your Surface

Many thanks for your reply, Marion_Y. The Surface is a Surface Pro (5th Gen) Model 1796 i5. (I think someone moved my post to Pro 7 which caused the confusion). The OS Build is 19042.1151. Yes, Bluetooth worked for a very short while after the Firmware update and works for a short time after each restart and then Bluetooth devices stop and eventually the Bluetooth function becomes unavailable (i.e. the Bluetooth icon goes missing from the Action Centre and the Bluetooth Switch goes missing from the Settings App. In Device Manager, the Bluetooth drive may also have the warning icon. The Driver is the Marvell AVASTAR Bluetooth Radio Adapter which under Update History is Marvell Semiconductor, Inc. - Bluetooth - 15.68.17021.121. I had already tried using the Surface Diagnostic Toolkit to no avail. On the Surface Drivers Download page you will see that there isn't a msi download file (now or yet) for a Pro 5th Gen with build 19042. Or perhaps it has been pulled! So, I can't run your steps 2 and 3 at the moment. I will try them if and when the msi becomes available. But perhaps another update will be made available on Windows Update, which I will continue to check for. I will update this post if when these things happen.

As mentioned in my reply of 6 August, there doesn't appear to be an msi file for the build of my Surface Pro 5th Generation (19042.1151), so I have not been able to download and reinstall the most recent driver. I have, though, uninstalled the Marvell AVASTAR driver and restarted my Surface. When I then reconnect the Bluetooth devices, they work unhindered. However, if I restart the Surface, the problem recurs and I have to uninstall the driver and restart the Surface again. I'm posting this as it may provide others, who have experienced the same issue, with a workaround and to, perhaps, help Microsoft diagnose and resolve the problem more easily. Not being able to restart the Surface without the problem recurring is not a long-term solution.

Hi,

I have the same Surface and experience exact the same problem with my bluetooth. It stops working and reinstalling it after removing helps for a few minutes are stops working when rebooting. This started to happpen after update august. Much enoying.

Thank you Roger. Whilst, I'm sorry that you are experiencing the same issue, it is good to know that it is not just me or my device. If I find a solution, I will let you know. Can Microsoft please issue updated drivers and, if appropriate firmware, to fix this as soon as possible please as this is badly affecting efficiency?