10.13.4 Broke BootCamp Bluetooth

Hey again,

Just to let you know that in the interests of trying to get to the bottom of this, I went ahead and updated macOS to 10.13.4.

Well....it works! Both the MM2 and the MK are working fine in that same bootcamp installation, without having installed the previously mentioned Windows updates.

The only conclusion, therefore, is that it's something Microsoft have done. There is a new update to Windows due very soon (Spring something-or-other) so hopefully that will fix whatever the issue is.

Hope you all manage to get it sorted.

Cheers.

This has nothing to do with macOS. It’s a Windows issue that screws up the pairing in macOS regardless of version. If it doesn’t work, then keep the devices switched off when in Windows. Then it’s ok in macOS.

sbrownpearn wrote:

I downloaded apple support software from macOS side and transferred over through USB yesterday though to see if that would do anything.

ASU provides additional updates that do not get rolled up into BC Assistant -> Action -> Download. The Download provides the base-line release only, which is related to your specific Model Identifier. It is rare for BC packages to be updated, without a new Mac model being released.

I tried again today, first removing the Bluetooth entries in Windows and then rebooting into macOS to read them - then back into Windows - and still nothing. However, the System Event Log had a number of entries as follows, indicating an problem:

"Windows rejected a device connection because the device didn't establish encryption prior to the service level connection." The source was called "BTHUSB" - I guess Bluetooth, right? Event ID 24 in each case, but it was logged as a warning, not an error.

The only other errors in the log relate to DCOM: "The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}". Which I don't think is related. I guess Windows changed something in the BT drivers that means the encryption isn't working somewhere. Not sure how to escalate this now.

so theres definitely some sort of idle disconnect that isn't re-waking … I just twirled my cursor around for about 20minutes and had 0 disconnects while the mouse was active. On further testing and some scientific stop-watching, I've found that if I don't move the mouse for as little as 2.0 seconds it becomes unresponsive and I have to reset it by opening the "services" tab in the mouse device properties, at which point it resets and I am able to continue to use the mouse unless I don't stop clicking or moving....

I went in to Mouse Properties > Hardware Tab > Properties > General Tab > Change Settings > Power Management > and Unchecked 'Allow the computer to turn off this device to save power' and it had 0 effect on performance.

Just tried - same here - it works as long you don't pair it at macOS. Something went wrong with the new 10.13.4 update. Hope Apple will provide a solution soon.....

Have you installed the KB4093112 update?

Have you considered downgrading to W10 1607 for stability?

Still having intermittent issues, btw. Cannot connect devices at all without unpairing in windows, then mac, then pairing in windows.

Hello! Having the same problems on my iMac 27" 2017 - the keyboard is working but not the Magic Trackpad and Magic Mouse on bootcamp Windows 10. On my MacBook Pro 2017 - the Magic Mouse isn't working too on bootcamp.