Bluetooth Driver for MBP 14,3 on bootcamp

I am back XD, I was hoping I didn't have to update this anymore hahaha,

So my mouse disconnected this evening after booting to MacOS and coming back to Windows and would not connect even though it is previously paired. Turning off bluetooth also causes bluetooth to remain off unless the system is rebooted. I followed the steps below to fix the connection:

1. Disconnect and forget the mouse, practically reset the connection
2. Check that current driver version for Broadcom 802.11ac Network Adapter: 7.77.119.0
3. Downgraded to 7.35.118.68
4. Restarted computer, attempted to connect bluetooth, failed
5. Manually turned on bluetooth collaboration(*double click correct driver in device manager*->Advanced->Bluetooth Collaboration ->Enable)
6. Attempted connection, connected successfully with lag/jitter
7. Upgraded to 7.77.119.0
8. Mouse lag/jitter received immediate improvement but restarted the computer again so that setting will process all the way through, the mouse remained connected and functioned as intended after the restart
9. Manually turned on bluetooth collaboration again(all the additional 7.35.118.68 settings remained), double checked that power saving modes are off for both Broadcom 802.11ac Network Adapter and Bluetooth Radio
10. Happy working mouse/bluetooth device!! Once again, will update if anything breaks again.

Hypothesis: The 7.77.119.0 driver for Broadcom 802.11ac Network Adapter lacks bluetooth collaboration setting and had the value set as auto off. Only downgrading to 7.35.118.68 will fully unblock the bluetooth collaboration settings, which allows successful handshake between the devices. But 7.35.118.68 lacks changes added in 7.77.119.0, so that the mouse would be jittery/laggy if remained in the older version. The solution is to downgrade to 7.35.118.68 to gain access to bluetooth collaboration, then update again to 7.77.119.0 to get a fully functioning driver. The reason that downgrading to 7.35.118.83 then update to 7.77.119.0 worked as well(in previous post) was because 7.35.118.83 probably has bluetooth collaboration set to auto on, thus achieving the same thing and allowing connection. But restarting the computer to 7.77.119.0 from MacOS somehow changed this setting. So that bluetooth would not function once again. This may not be entirely accurate but it is my theory as to why the bluetooth was not working, and should be something system engineers from all three companies can look into. :D

To clarify the turning off bluetooth part from last post: Attempted to turn off bluetooth manually via settings app rather than restarting computer, which only caused bluetooth to remain off and unable to be turned back on unless computer is restarted.

Update for documentation purposes: the restart problem was fixed by restarting the computer a few more times and reattempting connection each time.

It seems like this version of 802.11ac does not have the bluetooth collaboration under advance tab sad...

Another problem that popped up this morning which I saw 3 years ago. After restarting the computer, The bluetooth device originally paired (a mouse in this case) would display as paired but not respond. After unpairing and attempting to repair, the pairing now fails. After the initial failure of connection, the bluetooth device is nolonger discoverable unless the computer is restarted. Also, when bluetooth is manually turned off via settings app, it can nolonger be turned back on unless computer is restarted.

Hello Loner T, been waiting for you :D seems like you are the go to boot camp person in the past few years. Yes I have tried the 7.35.x.x through “update driver” which added “Bluetooth collaboration” to my “advance” tab under the driver which did not exist before downgrading. After testing it did not work, I moved on to updating again to the 7.77 version and saw that the “Bluetooth collaboration” Remained in “advance” tab.

Holy crab!!! it worked!!!

I downgraded to 7.35.118.83 (it popped up via "search on my computer" this time, it wasn't there last time) and the mouse connected after a few tries.

I hadn't had it connect in 3 years. But now the state of the bluetooth is laggy(or jittery would be the technical term) just like how it was 3 years ago. The mouse has a latency of at approximately 500ms and jitters across the screen. It is almost usable but not quite there... can't really aim when the pointer respond after half a second and hops around.

Hopefully we can fix that too :D

P.S. many thanks Loner T

Fixed!! I did not test the .78 version but here is what I did for future reference and whoever find this on the internet.

1. After the initial Win10 install the Broadcom 802.11ac Network Adapter driver was on 7.77.xxx.xx
2. downgraded (*double click correct driver in device manager*->driver->update driver-> browse my computer for driver software->let me pick from a list of available drivers on my computer->*select correct version*->next) to 7.35.118.68
3. Restart, this should add bluetooth collaboration and bunch of other stuff in the driver's advance tab.
4. Test bluetooth, did not work
5. Update bluetooth driver again to 7.77.119.0
6. Restart, this retained all the bluetooth collaboration stuff in the advance tab
7. Test bluetooth, still would not connect
8. Downgraded to 7.35.118.83
9. Restart, this took out all the bluetooth collaboration stuff in the advance tab
10. Test bluetooth, would connect after a few tries, extremely laggy/jittery, can not use a mouse normally, have not tested with speaker
11. Upgraded back to 7.77.119.0
12. The mouse had immediate smoothness, I'm not a believer so restarted, mouse still connected, functioning as intended. I'm not testing reconnect though lolz
13. Mouse stopped working after idle for a few second
14. turned off power saving setting in Broadcom 802.11ac Network Adapter and Bluetooth Radio (*double click correct driver in device manager*->Power Management->*uncheck* Allow the computer to turn off this device to save power)
15. Yay, happy post, I will give an update if it stop working again. And a great thank you to Loner T for sticking to this problem in the past 3 years. He's been the only one consistently answering all Apple Community questions regarding this issue, many of the steps shown here and methods tried in previous comments are explained in his other posts. This is amazing work considering calling Apple and Microsoft support 3 years ago resulted in a full investigation with the support engineer team from both companies with no results, and calling again recently, Apple support told me that this is an issue the engineers are aware of but is still on the backlog. So once again, great applause to Loner T for sticking with us through this issue and suggesting various solutions :D