10.13.4 Broke BootCamp Bluetooth

I have a similar feeling but it´s not as broken as yours. For me, only thing stopped working is the side scroll, this is really annoying though since I use Windows through VmWare to work. I use a piece of software named Bluebeam Revu and the side scroll made it possible for me to navigate construction plans much smoother.

I was hoping it would, but it's now worse than before. I think probably because before it would upgrade to 1804, it installed the deferred updated - notably, KB4088776. After that I had to use USB mouse and keyboard.

I followed through with the upgrade to 1804 hoping it would all be fine, but no - not even the keyboard works now when in Windows 10. I don't think anyone is going to fix this - it's been an issue for weeks now, and I've seen no official acknowledgement. KB4088776 basically breaks the bluetooth relationship between Windows and macOS. When I boot back into macOS I have to connect a USB mouse (the keyboard is detected okay) to hit the connect button on the Magic Mouse 2. Then it's fine until I boot back into Windows - then nothing works at all. To add insult to injury, Parallels won't boot the new Windows now -"Configuration of this Boot Camp virtual machine doesn't match that of the real Boot Camp partition." I've seen this on some of the Parallels forums but I don't see a solution as yet. I've basically had enough to be honest. Good to luck anyone else who tries this... 😟

Sorry to hear that guys. I’ve had no issues for the last couple of weeks, and the release build of 1803 is fine as well. One of my friends doesn’t have the issue either.

I wish we could tell what was causing it for you guys.

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.

I'm seeing this message logged now: "Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during start-up" (Event ID 18, BTHUSB).

Also, in the Device Manager tool, I see the mouse listed under Bluetooth, and it says, "This device is working properly." Which of course it isn't. And under the events tab there is a message that reads: "Device BTHENUM\Dev_DCA904069256\8&358a825e&0&BluetoothDevice_DCA904069256 requires further installation."

I tried reinstalling the boot camp s/w but it doesn't do anything as the drivers are already installed and up-to-date.

Similarly for the keyboard, it says "Device BTHENUM\Dev_D4DCCD7D8EEB\8&358a825e&0&BluetoothDevice_D4DCCD7D8EEB requires further installation."

Looks like MS broke Bluetooth somewhere along the way. I also turned on/off the BT collaboration for the Wi-Fi adapter and that didn't seem to make any difference.

ok - last update for now. I was rather surprised to find that after the 1803 update I was allowed to then uninstall KB4088776 again, the root of all these problems. After rebooting and re-pairing in macOS the mouse and keyboard are all working fine again. I have pause the updates for now until I have seen this problem fixed. Apple really should escalate this with MS though. Thanks.

Okay - last time. I couldn't let it go - so I retried the install, and despite one reboot glitch at the start when I had a giant sad face emoji, it restarted and seems up-to-date this time. I had to turn the mouse off and on again - but it worked straight away this time. The difference this time was that I downloaded the 1803 ISO and ran the update from there, rather than from the web link. Not sure if that matters - but I'll keep an eye on it now. Phew...

So I ran the most recent updates and it has only made the situation worse - previously I could un-pair in macOS and pair in bootcamp to run without issue. Now when I pair in bootcamp, both mouse and keyboard will work for approximately 1 minute before becoming unresponsive - they will still be listed as "connected" but there is no input detected.

strangely enough the above unresponsive issue resets when I open the Mouse Properties from device list and click on the "services" tab...100% reproducable after 10 disconnects. Stays connected for another minute or so, back out of mouse properties, go back to services tab, reconnects...

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.

Don’t take that for granted. For a lot of people, 1803 solved the issue. Both the Insider Preview build and the public release one have been absolutely trouble free for me, people I know and others on forums.

Unfortunately, there are people who still have the issue, and we seem to be no clearer why this affects some people and not others.

You may want to try 1803, and just roll back if it doesn’t work for you.

I’m just not sure it’s worth it. I only use my bootcamp partition for occasional gaming and right now it works fine.

I use the 3rd party AMD Radeon drivers as the native Apple ones are useless. Unless upgrading to 1803 is likely to improve my machines gaming performance I’m just not sure there’s any point.

Are you aware of any changes in 1803 that will increase the performance of the machine or is it more a cosmetic/security update?

Thanks.

I understand, but it may be worth a try to solve the issue at hand here. It's easy to roll back if it doesn't.

I haven't noticed any performance increase or decrease in gaming, but there are some nice new features.

Anyone else still having issues? I've noticed that Bluetooth IS WORKING, but it goes idle after 5-10 seconds of inactivity and will not wake back up UNLESS I go in Devices and Printers > Mouse > Services and refresh my Bluetooth services. At this point the mouse will resume connection. This works without pairing/repairing in windows or mac - I can pair my mouse in macOS, boot in to windows, and refresh Bluetooth services and mouse will work for as long as I want to actively use it without taking a 5s break.... All my drivers seem to be up to date.

UPDATE!: I downloaded apple support software from bootcamp assistant in macOS for the third time since the beginning of this...reinstalled all drivers on the windows10 side annnnd mouse is fixed. working perfectly. Will report after several resets if anything is still going on.