Problem Bootcamp Windows 10 & Bluetooth

Can you try the following please for me please? It solved my issue where the trackpad and keyboard worked for a little while, then stopped responded despite the deviced being listed as 'paired' and connected.

In Windows, go into Control Panel > Device Manager, then expand the Bluetooth (you can also type 'Device Manager' in search and launch it that way).

Find 'Bluetooth Radio' and go into properties, then go into 'Power Management'.

Uncheck the box that says 'Allow the computer to turn off this device to save power' and click OK.

You may need to reboot to get the devices working properly again, then it should be fixed.

I hope this helps.

This also worked for me on a MacBook Pro with touch bar. In Windows 'device manager' Bluetooth, Bluetooth radio, properties, power management, unticked 'allow the computer to turn off this device to save power' and the apple magic mouse 2 and apple keyboard sprang to life.

I can confirm this issue exists on a 21.5, 2017 iMac.

Everything works great after the initial Windows 10 installation and Apple software.

After the first round of updates, the Magic Mouse 2 and the Magic Keyboard stop working.

Awkward Work Around

The Magic Mouse 2 and the Magic keyboard will work with Windows 10 (1709 and above) under only one condition. (As of 4/8/18)

You must first unpair both the Magic Mouse 2 and the Magic Keyboard in MacOS. They will then pair and connect properly in Windows 10. However, if you reconnect these devices in MacOS they will stop working in Windows 10.

To confirm that this an issue specifically with the Magic Mouse 2 and the Magic Keyboard with numeric keypad I connected a Dell KM717 bluetooth Mouse & Keyboard set. Both devices work perfectly under MacOS and Windows 10 (1709 and later.)

So it appears that the issue is some sort of incompatibility between the Apple Magic Mouse 2, Apple Magic TrackPad 2 and Windows 10 updates (1709 and beyond).

The issue does indeed rest with an update that was released for Windows to resolve a couple of other Bluetooth related issues. The issue is that devices will pair, but not connect. Some of us, including myself, have had the keyboard work until they tried to get a Magic Mouse 2 or Magic Trackpad 2 to also connect; doing so would immediately also put the Magic Keyboard out of business. The updates causing the issue in the first place appear to have been released somewhere around January/February, but they have since also been included in a Cumulative update, which was released at the end of February.

If you see updates KB4074588 or KB4056892 listed in your Windows Update History, it seems that uninstalling either or both of those might resolve the issue. For now, at least, and only if you’re not experiencing any of the other issues resolved in those updates in the first place. Therefore, applying this method is far from ideal.

Until such a time as when the issue is definitively resolved either by Apple (by way of an updated driver for Bluetooth [Broadcom, in my case] as well as one for the Magic Mouse/Trackpad 2 and the Magic Keyboard) or by Microsoft (by way of yet another update for Windows), the only solution would be to temporarily use another mouse and keyboard in Windows. You will be able to use the Magic Keyboard and/or Trackpad with the cable attached (that works just fine) but, of course, for the mouse, there is no such option.

If you have an older generation Apple mouse and/or keyboard lying around, those will all work fine even if they are wireless; only Bluetooth 4/LE devices are affected. This means that the first generation Magic Mouse is also unaffected and works just fine.

FYI, I had the same issue and I removed the recent MS update KB4088776 - as a result, the magic mouse 2 is working again on my iMac, but I had to disable Windows updates after that to stop if from reinstalling. As soon as it's reinstalled, it kills the mouse and it has to be re-paired in macOS before it will work again.

nsthankiya wrote:

Currently on an iMac Pro running macOS 10.13.4 and Windows 10 with latest April 2018 updates in bootcamp. I have no bluetooth in Device Manager.

Have tried to install the latest broadcom bluetooth drivers from bootcamp but the installer errors out unable to install Apples driver.

I was able to install the broadcom bluetooth driver from bootcamp but still no bluetooth in Device Manager

Device Manager shows no bluetooth, showing hidden devices also doesn't show any bluetooth

Trying to set up any bluetooth devices errors with unable to find bluetooth device, mouse, keyboard, or beats headphones.

Tried turning on/off airport mode still no bluetooth

Does Windows device manager show any errors with any devices? I’m not just referring to Bluetooth devices, but also to devices in the Universal Serial Bus (USB) section of the Device Manager. I’m asking because I’ve had a similar issue not so long ago with a Lenovo laptop. All of a sudden, the system point blank refused to work with connected bluetooth devices. Upon investigating, I found that the whole subsystem for bluetooth was nowhere to be seen. I couldn’t even turn bluetooth on or off.

Then, I decided I’d fire up Device Manager. There I saw a USB device error (something along the lines of “The Device Descriptor Request failed to complete). Disabling the device with the error; then restarting; then re-enabling the device, solved the issue. After that, all of the bluetooth related options and settings suddenly reappeared in the Settings app.

Obviously, I don’t know if this even comes close to what is the matter in your particular case, but it was similar in that nothing else worked. Even toggling Airplane Mode or whatever; nothing worked except completely disabling the device (which is like pulling the device out of the system).

Paulowoody wrote:

FYI, I had the same issue and I removed the recent MS update KB4088776 - as a result, the magic mouse 2 is working again on my iMac, but I had to disable Windows updates after that to stop if from reinstalling. As soon as it's reinstalled, it kills the mouse and it has to be re-paired in macOS before it will work again.

Back to this stuff again? I have posted a link to download a tool that allows you to hide specific updates. Perhaps you can use the tool to keep Windows updates enabled but hide KB4088776. That way, you won’t be at risk in case any potential other bug is found. I’m sorry to reiterate this, but outright disabling updates is never a good thing. Not on iOS, not on macOS and especially not on Windows.

It may come as no surprise to you, but Windows is the most susceptible environment when it comes to attacks; purely because of the large user base. It isn’t that Microsoft aren’t doing enough to address bugs and vulnerabilities (in fact, they’re repeatedly proven to be the quickest when it comes to this); it’s just that the “other” side finds them quicker than Microsoft can fix them… And leaving an open vulnerability exposed is about the worst thing you could do…

Should you be unable to find the link that I posted (it should be about 5 pages back) then google “Windows 10 hide updates” and click on the first result from the Microsoft website. There, download the tool and execute it within Windows.

It’s always hard for me to give up. So, I went ahead and removed both Magic Mouse 2 and Magic Trackpad 2 from Windows 10 list of Bluetooth devices. Mine is a MacBook Pro so I kept working with the embedded trackpad. Rebooted the computer and entered macOS. After logging in, plugged the lightning cable into the Magic Trackpad 2, waited for the “device connected” message, unplugged and repeat the procedure with the Magic Mouse 2. Both devices working properly in macOS via Bluetooth.

Then rebooted into Windows 10 (Native, I use rEFInd to choose OS by the way) and ufff… here it comes!!! Yes, yes, yes, both Magic Mouse 2 and Magic Trackpad 2 were detected under Windows 10 and both are now working!!!

So, after a few weeks of pain and disappointment, I am again the happy and loyal fan of both Microsoft and Apple!

I am surprised to find myself saying this, but it's all working for me - for now. I removed the offending KB4088776 update and then installed 1803 from the ISO, which I copied to a local folder rather than mounting it. I also removed all external drives and SD cards as that has been known to cobble things in the past. It went though the upgrade and asked if I wanted to install the latest updates - I said not yet. It carried on. Booted. Blue screened and rebooted - but carried on. After a few more reboots it finished. And the MM2 and MK2 were bother working. Before all of that I had made sure they were working under 1709 after pairing them in macOS and the KB4088776 was uninstalled. I also paused updates to stop it from coming back. At the end I checked for any updates and there were none - but it was all fine after about 5 reboots. For now anyway.

Fellow BootCamp users,

After days of back and fourth with the Apple Care support team and some software engineers, I've found that the issue is a Windows 10 Security update that renders Apple keyboard and mouse (and trackpad too) useless. The solution that was provided to me by Apple was to uninstall the affected security updates (they might be different to you since several Windows updates can be combined into a single package). Apple told me to uninstall "Security Update for Microsoft Windows KB4074588" However, KB4056892 is what did it for me. I've sent in several bug reports, with irrelevant responses like how to download the Windows Support files again. Its several weeks since I've known about this issue, please give feedback to Apple so that they can finally fix this issue with their drivers... Rolling back security software updates should never be the solution! Alas, it is. Kind regards.

Update newest macOS , be sure the default startup disk is set to windows(set this in the Mac side) .

This combo finally worked.

Restart into windows 10.

Turn Bluetooth on and off.

Plug in keyboard with lightening cable.

Hold the command and Eject Key on IMac Pro keyboard.

Remove lightening cable .

Done.

It’s definitely not always possible to uninstall the update causing this bug. There is another thread in the Appel Community forums that mentions two updates which could are the (likely) cause of the bug, but since then, Microsoft has rolled out a so-called cumulative update which includes the affected patches. Therefore, it isn’t always possible to uninstall these individually. This is especially true if you haven’t used Windows 10 for a long time, and only ever received the bigger cumulative update.

As for your other observation: it is definitely not a MacOS issue. the issue came about after Microsoft released a set of Windows updates in the course of February, which have since been included in the cumulative update I mentioned above (after applying this update, the build number of your Windows version would be 17.09). Unfortunately, it is almost never possible to uninstall cumulative updates, since doing so greatly increases the chance to further issues. What’s more, these cumulative updates also usually solve heaps of other bugs, which you wouldn’t want to “un-patch”, shall we say…

@Loner T: that’s about as much as I’ve discovered, along with many others… It would have been good for you to have read the entire discussion before posting your reply, as we’ve long since deduced that the problem lay with bluetooth 4(/LE) devices in particular. As you may know, the first generation Magic Mouse (the one that accepts AA-batteries) does not make use of Bluetooth 4(/LE), and is proven to work despite this bug in Windows 10.

As far as Apple devices are concerned, the first to make use of Bluetooth 4(/LE) are the second generation Magic Mouse, the Magic Keyboard and the Magic Trackpad. You can still use the latter two if you use them with a lightning cable (i.e. not wirelessly). For the Magic Mouse, this is not possible, since it isn’t possible to use it with a cable attached (which, in my opinion, is a major design flaw, but that’s a whole different story.

By the way, the bug does not necessarily affect Bluetooth 4(/LE) devices made by other manufacturers… As of present, it is known that Apple devices are affected, along with some others, but not nearly all of them.

Its coming back to me. It was the BLUETOOTH radio driver I updated, not the mouse driver. I think I also remember reading the specific windows update that originally affected this had some bluetooth security updates.

Anyway, I found the below in my browsing history, so these are the steps I likely followed. Like I said I got it to work for a few days, but then I started playing around with some settings and experimenting with various drivers and now I don't even see the Apple listed as a "manufacturer". In fact the list only has a few options now. I'll try to experiment with this next week when I get some time. I try to document and screen shot what I do in case I get it to work again.

-----------

From: Windows 10 update on bootcamp bluetooth issues fix - Microsoft Community

My bluetooth stopped working once windows 10 upgrade was installed. I found this simple fix:

• Open Device Manager, open the Bluetooth Radios subtree, right-click the "Apple Broadcom Built-in Bluetooth" icon, and choose the "Update Driver Software..." menu item.
• Choose "Browse my computer for driver software"
• Choose "Let me pick from a list of device drivers on my computer"
• Select "Apple Inc." for Manufacturer, and "Apple Built-in Bluetooth" for Model, and click Next.

After the driver installed, The device list sows "Apple Broadcom Built-in Bluetooth" had been replaced by "Apple Built-in Bluetooth" and "Microsoft Bluetooth Enumerator" in the Bluetooth Radios subtree of Device Manager

emulajavi wrote:

Let’s see if tomorrow’s major Windows 10 update fixes it....

In the meantime, I’ve uninstalled all the related updates (848, 776, 588, etc) that were mentioned in this thread and the Keyboard and Mouse have come back to life. Also, I’ve paused Windows updates on Windows Update’s advance settings, and differed updates for a month. I hope it stays working till Microsoft and Apple fix it.

It’s ashaming that since the release of High Sierra Apple has still to update the Bootcamp drivers to support APFS. Only way to reboot into macOS is holding Alt, because the Windows Bootcamp app still hasn’t been updated. Also it still doesn’t support Retina resolutions on Windows, since Volume, Mouse connected, etc UsI shows very small on my iMac 27-inch.

Also, I’m still waiting for Apple and AMD to fix the Graphic Drivers Update 6.3 they released on Oct17 which started producing issues with the mouse cursor graphics.

If that wasn‘t enough, now we have the Bluetooth issues which, anyway, are nothing new, since I’ve always experienced intermittent issues with he Mouse and Keyboard randomly losing Bluetooth connection and having to power them off and on for Windows to find them again.

Why is is it so difficult for one of the biggest companies on the world to release proper drivers and update them regularly and to work with Microsoft for a correct support of its peripherials? MM2,MT2 and MK should be paired on Windows the same way than on macOS: plugging them on the Lightning cable and that’s all.

1) Tomorrow's update won't fix it. See earlier post.

2) Not sure what you mean about Retina displays not being supported. If icons, etc. are too small, then change the scaling factor in Windows Display Settings. Common for 5120x2880 displays is 200%.

3) Forget the graphics drivers in Bootcamp 6.3, use the official (hacked) AMD drivers available from bootcampdrivers.com.

VGonzalez1973 wrote:

Don’t! I’ll work until your next restart. My happiness lasted a few hours. I’ll try the Windows 1803 April update today, and will see what happens.

Anybody interested in a Magic Mouse 2 and/or a Magic Trackpad 2? I’ll add a Magic Keyboard 2 as a bonus!!!

Whoa…! That’s a strong note of discouragement I taste there…! Well, too late, the 1803 update is installed already, which proves that that process at least, works. Even for me, with Windows installed to an external drive. So I might post a topic on here as to how to achieve this, because it’s not as straightforward as one might think. I haven’t, however, had to retry the mouse resurrection process. See below…

paulowoody wrote:

I am surprised to find myself saying this, but it's all working for me - for now. I removed the offending KB4088776 update and then installed 1803 from the ISO, which I copied to a local folder rather than mounting it. I also removed all external drives and SD cards as that has been known to cobble things in the past. It went though the upgrade and asked if I wanted to install the latest updates - I said not yet. It carried on. Booted. Blue screened and rebooted - but carried on. After a few more reboots it finished. And the MM2 and MK2 were bother working. Before all of that I had made sure they were working under 1709 after pairing them in macOS and the KB4088776 was uninstalled. I also paused updates to stop it from coming back. At the end I checked for any updates and there were none - but it was all fine after about 5 reboots. For now anyway.

I can report an even more astounding chain of events on my side:

During all of this, I had my wired Apple keyboard and (wired) Mighty Mouse connected.

As I wrote above, I went ahead today and installed the 1803 upgrade, which, for me, went without a hitch. Even though it was slow as molasses; the “installing” part (where you could continue to use Windows) took over an hour to reach 100% and prompt me to reboot.
That, then, I did. It then had to reboot for another 3 times to really complete installing the upgrade. Then I went and searched for other updates — just in case. It found a totally irrelevant update (a device driver for my printer, which failed to install, but that is quite another story…), but no system updates to Windows. I then restarted into Windows once more just to be really sure. Then I checked Windows Settings > Devices and saw that both my MK as well as my MM2 were listed as connected. So, with the wired devices still in there, I pressed some keys on the MK (which worked fine all along) and found that it worked, now, too. Then I pressed the MM2’s left mouse button to really trigger it into connecting, wiggled it about a bit on the desk and…: it moved! I then took the wired devices off and used the wireless ones, with success! All this without uninstalling KB4088776 and without doing the “mouse resurrection process. I basically left it all alone. Yet, it worked. Now all there is to do for me is to see how it holds on into consequent sessions of Windows. I’ll keep my guard up, as the stuff has been acting so weirdly different for all of us lately. So this may all just have been a fluke over here. But if it does continue to work, I’ll be a very happy Windows user whenever I need to be.

I will keep you posted when I’ll next use Windows.

Take a look at this thread that I started over in the Boot Camp support community, and the solid answers therein. TLDR: It appears the trick may be telling Windows that it's not allowed to turn off Bluetooth to save power...

Win10 1709 no Bluetooth w/ 2016 13" MBP (Touch Bar)