Problem Bootcamp Windows 10 & Bluetooth

Hello,


on my new iMac Pro Windows 10 created with Bootcamp, Bluetooth does not function anymore.

The problem is, that the original iMac Pro Magic Keyboard and the also original Magic Mouse 2 seems to pair but they get no connection ( keyboard + mouse no response ).


Before i had updated to MacOS 10.13.3 everything went well, both, keyboard and mouse were okay.


Reinstalling the Bootcamp Windows drivers does not have any success, same problem as before.



Any suggestions wether the Bluetooth problem has to due with the MacOS update and therefore the newly installed Windows drivers are also corrupted ?



Many thanks in advance ...


Klaus

Posted on Jan 27, 2018 4:37 AM

Reply
Question marked as Top-ranking reply

Posted on May 25, 2018 5:51 PM

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.

Similar questions

147 replies

Feb 17, 2018 12:35 AM in response to klausfromlimburgerhof

Same for me. It happened after a recent Windows security update. If you remove the update, then the issue goes away. However, windows forces you to reinstall the update at some point so this isn't a permanent fix.


I plug in another Logitech mouse (has its own usb dongle) and that works. If I plug in my Apple keyboard with provided lighting cable it works. That's kind of my setup for now. Hope it gets fixed.


On iMac Pro 64 Vega.

Apr 6, 2018 4:54 AM in response to csteelooper

csteelooper wrote:


Did you restart after uninstalling the keyboard? I’m not saying it’s supposed to be working (uhm… well, actually… it is, but at least not the way things are after these updates have ruined it all…), but what I do know is my keyboard worked up ’til the point of trying to perform CPR on the mouse. After I had unpaired; then re-paired the mouse (unpairing in MacOS, then re-pairing in Windows) or whatever else I tried to breathe life into it, the keyboard would ‘give up the ghost’ under Windows. Also, restarting wouldn’t help, even with the mouse off.

The only thing that would at least get the keyboard back to work in Windows is actually connecting the cable.


By the way, seeing as you have an MT2, that would be something you could do to get it to work for the time being: connect the cable prior to booting into Windows, and let it sit there during your Windows session. The point I’m making is, like the keyboard, the MT2 can be used with a wired connection and will work.

The only device for which this isn’t an option is the MM2 (which, I’ll say once again, is rather a design flaw, in my opinion, but that’s a different matter). At least folks with a MK and a MT2 could use those wired for the time being… In wait for a solution from either Apple or Microsoft.

Clearly the situation is very different for different people. You tend to be making the assumption that we are all experiencing the same. We're not!

My MK with Num Pad works absolutely fine without a cable as long as I don't have my MT2 switched on.

For me, until this is sorted out, I am using a wireless mouse in Windows along with my MK. Not ideal, but it's OK. Just have to remember to switch off my MT2 when I come out of macOS!

Apr 8, 2018 10:10 AM in response to igmackenzie

igmackenzie wrote:


Loner T wrote:

Assuming both MT2/MK2 are paired in macOS,


  • Switch to Windows
  • Turn BT Off
  • Connect MT2/MK2 using USB-to-Lightning cable.
  • Eject the MT2/MK2 devices using Command+Eject.
  • Disconnect Lightning cable
  • Turn BT On
  • Connect MT2/MK2 and test.

That’s what he said, but what is he trying to achieve?

To get MT2/MK2 to work properly using BT, without Lightning cable.

Apr 26, 2018 10:16 AM in response to klausfromlimburgerhof

Magic Mouse 2 working again!!!! Well, no so fast…. Yesterday both Apple and Microsoft released OS updates, so I don’t know which one did the “fix?”

I applied both updates, (windows 10 and macOS) (I had to reinstall rEFInd by the way) and went ahead into macOS, plugged both the Magic Mouse 2 and the Magic Trackpad 2 with a lightning cable to have macOS recognize it, removed the cable still in macOS to go Bluetooth. Both devices worked properly in macOS via Bluetooth. Restarted in Windows 10, logged in, no lightning cable used, and voilà, one of the two devices work. ONLY ONE. I did it several times. I think the last one plugged with the lightning cable into MacOS works.

Not a full solution to the problem, but at least, I can now use my Magic Mouse 2 while doing all the work and hope for a Magic Track 2 back in business soon.


Apr 30, 2018 1:01 AM in response to VGonzalez1973

VGonzalez1973 wrote:


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’m one who is made out of the same wood. I also usually refuse to give up. But then there’s the thing that I’ve already tried removing the devices from Windows, then having MacOS re-recognise them and then booting back into Windows, like you describe. I have to add that this was way before all of us started having some random strokes of luck in that the devices did spontaneously get back to work.
However, being that I did go through the procedure you describe, I’m a bit doubtful as to whether it would work this time, as it didn’t yield any results back then, either.


I might have to try it again though, as I also have to try whether the newest Windows 10 upgrade(-to-be) will install successfully. As some of you know, I have used an alternative method to install Windows 10 to an external device. It works flawlessly, apart from our shared device related problem, but it shares characteristics with Windows To Go, which could rule out any upgrades to the existing installation.


So as soon as I receive word on the formal release of this upgrade to Windows 10 (in my region), I will most certainly also give the mouse resurrection process another go.

Apr 4, 2018 8:16 AM in response to mrandyflores

If only one could uninstall those updates if they never were on the system (as separate updates) in the first place. You see, if you’ve regularly used Windows, you may have received the aforementioned updates separately. However, if there has been a long break between uses, or you have installed Windows after a subsequent cumulative update has been rolled out by Microsoft, the patches will have been included in it. This removes any opportunity for you to uninstall just those two updates. Unfortunately, the updates were indeed included in the Cumulative Update released in February 2018 (OS Build 17.09). Because I found out way to late that the issue we are having was indeed a real bug, I had since wiped my Windows installation. If I would not have done so, I might have been able to separately uninstall the updates causing the issue. I say I might have, because usually, installing a cumulative update consolidates the patches that had been installed before, deleting the separate listings for them…

Apr 6, 2018 4:14 AM in response to igmackenzie

Did you restart after uninstalling the keyboard? I’m not saying it’s supposed to be working (uhm… well, actually… it is, but at least not the way things are after these updates have ruined it all…), but what I do know is my keyboard worked up ’til the point of trying to perform CPR on the mouse. After I had unpaired; then re-paired the mouse (unpairing in MacOS, then re-pairing in Windows) or whatever else I tried to breathe life into it, the keyboard would ‘give up the ghost’ under Windows. Also, restarting wouldn’t help, even with the mouse off.

The only thing that would at least get the keyboard back to work in Windows is actually connecting the cable.


By the way, seeing as you have an MT2, that would be something you could do to get it to work for the time being: connect the cable prior to booting into Windows, and let it sit there during your Windows session. The point I’m making is, like the keyboard, the MT2 can be used with a wired connection and will work.

The only device for which this isn’t an option is the MM2 (which, I’ll say once again, is rather a design flaw, in my opinion, but that’s a different matter). At least folks with a MK and a MT2 could use those wired for the time being… In wait for a solution from either Apple or Microsoft.

Apr 8, 2018 8:36 AM in response to igmackenzie

igmackenzie wrote:


Carlos Garrido wrote:


Has this method worked for someone else? Does it keep working on all Windows startups or does it always have to be repeated?


On the other hand it is not clear to me the BT's disconnection order, I explain:


Restart into windows 10.----- (in this point the BT is on?)

Turn Bluetooth on and off.----- (is "on to off"?)

Plug in keyboard with lightening cable.----- (while BT is off?)

Hold the command and Eject Key on IMac Pro keyboard. ----- (while BT is off?)

Remove lightening cable .----- (connect in BT at this time?)

Done


Can someone explain it to me?

Sorry, I have no idea what you are trying to do! Can you explain what this procedure is trying to achieve?


Assuming both MT2/MK2 are paired in macOS,


  • Switch to Windows
  • Turn BT Off
  • Connect MT2/MK2 using USB-to-Lightning cable.
  • Eject the MT2/MK2 devices using Command+Eject.
  • Disconnect Lightning cable
  • Turn BT On
  • Connect MT2/MK2 and test.

May 12, 2018 5:49 AM in response to Loner T

There is nothing wrong with the Bluetooth or Wifi drivers in Windows. The device drivers at fault are those for the Mouse and Keyboard device class. Apple has modified device driver files for bluetooth in particular, but nothing of the sort has been done for the keyboard or mouse drivers. The screen shot you showed listing the driver files is for the Bluetooth controller. but that works, since devices other than the Second generation Magic mouse and keyboard do work perfectly.

As for an enriched user experience when it comes to the mouse: that should be set forth by the mouse driver. Same goes for the keyboard. There really are no features in the bluetooth controller that aren’t supported by Windows, yet should be. Even Nearby Sharing (Microsoft’s version of Handoff) works flawlessly…


The part of the mouse driver which Apple did write and/or copy is the part which is responsible for the wireless communication between the mouse and the Mac say, say the bluetooth part of them, but the actual MOUSE driver part was largely left untouched. Something similar is the matter for the Magic Keyboard. The wired keyboard can be used with no Apple-provided software at all; especially if you won’t mind that some keys are out-of-place…


However it may be, the problems arose as a consequence of a botched security update. This being the case, it should be Microsoft providing the definitive solution for the issues; not Apple. Apple is responsible only to finally bring the user experience up to par. THAT is what we should expect from Apple; not much else, in this case.

Jul 10, 2018 12:42 AM in response to klausfromlimburgerhof

Hi Klaus, I played around yesterday with various configurations.


In my case:

All the problems start with High Sierra 10.13.13 in combination with Windows 10. The problem seems to be only an Apple Hardware Problem


Windows 10 1607 - Bluetooth connects after fresh installation instantly but loses connection as soon as you do not use devices for a short time - "solution" = Leave the bluetooth show devices window open and it works all the time


Windows 1703, 1709 and 1803 I had several issues never got BT correct to work for a longer period but I didn't try to leave the show BT devices open to see if that works. I do not want to upgrade to test it since I have a "working" setup now. I just found out with my 1607 installation.


Beisde that I installed VMware Fusion and chose to run the Bootcamp Partition directly which runs good and you do not have to struggle with BT as a interims solution at least.


Could anyone test the newer Windows Versions what happens if you leave the window open once it is connected?


MBP 2017

Jan 27, 2018 11:02 PM in response to klausfromlimburgerhof

Yep ... #metoo. I'm on an iMac Pro. Plugged in a hardwired keyboard and mouse and everything worked fine, but no bluetooth keyboard or Magic Mouse 2.


Interesting to note, I installed bootcamp from scratch yesterday. BT keyboard and Mouse worked fine after initial install, but problem started after I did the final Windows 10 update to version 1709. I'm pretty sure this is a driver issue ...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problem Bootcamp Windows 10 & Bluetooth

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.