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

Jan 31, 2018 8:35 AM in response to rehctelf

Has anyone yet been able to find a solution to the failure of the Apple Magic Mouse 2 to work in Windows 10. I have tried all sorts of trouble shooting in Windows 10, reinstalled the Magic Mouse 2 driver numerous times in Windows 10, etc. all to no avail. In Windows 10 an overlay saying "connected" comes up when I left click on the Magic Mouse 2, but the cursor never moves. Is this a Windows driver problem or an Apple driver problem? If it is a Windows driver problem, is there anyway to send feedback to Microsoft that their latest update broke the Magic Mouse 2 in Windows 10?


Tom

Apr 4, 2018 5:44 AM in response to ozziefromcharlotte

Would that work? I wonder… At the very least, you would sacrifice device-specific features. Furthermore, the Magic Mouse and the Magic Mouse 2 use the same device driver. So you would then have to use, for example, the Wireless Mighty Mouse driver for the mouse and the Apple Wireless Keyboard driver for the keyboard. To try if it works, I can help you in finding the Apple drivers.


  1. go to Device Manager by right clicking the start button and choosing the corresponding option
  2. locate the Magic Mouse (or keyboard) in the device tree
  3. Right click the entry for the Magic Mouse (or Keyboard
  4. Select the Driver tab
  5. click Update Driver
  6. Select Browse My Computer For Driver Software
  7. Select Let Me Pick From A List Of Available Drivers On My Computer
  8. Click Have Disk…
  9. Point to the directory that holds the Apple Device Drivers
  10. Select the appropriate device

Apr 5, 2018 10:06 PM in response to igmackenzie

I would’ve thought something like that (the erratic behaviour returning), seeing as, in Windows, settings and other (non user-configurable) parameters for input devices are largely stored system-wide. The only settings that are stored on a per-user basis include key repeat speed; mouse cursor speed; double click speed and the like. But, say, the sensitivity of the laser (high or low DPI) is fetched from the hardware and then stored on a system-wide level for each device.


I cannot test one scenario here because the Magic Keyboard is my only keyboard, but it might be that your MT2 started working all of a sudden because, for once, it actually connected to the system before the keyboard did. As I’ve mentioned before, my keyboard works great, even after bringing the Windows patch level up to 17.09, until I try bringing the mouse back to life. Do that once, and I’m loosing both. The only way I can then get the keyboard working again is by attaching the cable (and, indeed, leaving it attached at all times, since detaching it makes it stop working once more).


For me, the real trouble is that Windows 8 and 10 have been heavily optimised for touch and/or mouse use. Even more so than before. In Windows 7 and earlier, it wouldn’t even have been that hard for me to use the computer without a mouse. But that kind of usage requires a whole new level of skill in Windows 8 and up… So I can only resort to using an older bluetooth or wired mouse, until such time as when the issue is fixed.

Apr 8, 2018 11:21 PM in response to csteelooper

In my opinion, it’s a waste of time trying to block Windows updates. Even if we knew which one causes the issue, the update can be rolled up in another, and trying to stop Windows 10 updating is next to impossible unless you are happy doing no updates at all. Then, there is a reg hack.

In my case, the devices all show as being connected (not just paired) but there is no functionality.

My solution at the moment is to have a wireless mouse connected, and remember to switch off my MT2 when I switch from macOS to Windows. Then, my MK works perfectly in macOS and Windows.

Apr 8, 2018 11:31 PM in response to igmackenzie

igmackenzie wrote:


In my opinion, it’s a waste of time trying to block Windows updates. Even if we knew which one causes the issue, the update can be rolled up in another, and trying to stop Windows 10 updating is next to impossible unless you are happy doing no updates at all. Then, there is a reg hack.

In my case, the devices all show as being connected (not just paired) but there is no functionality.

My solution at the moment is to have a wireless mouse connected, and remember to switch off my MT2 when I switch from macOS to Windows. Then, my MK works perfectly in macOS and Windows.

Didn’t I write something along those lines, too? Being a systems administrator (Windows; Linux) it goes against my nature to advise people to block updates.

Also, I already wrote, somewhere along the way, that the conflicting security update had been included in a cumulative update that has been released since. As you say, the best solution for the moment is to simply use alternative (pointing) devices, if at all possible. That way, you’ll be able to use Windows without sacrificing security and the Mac’s “native” devices stay working properly when in MacOS…

Apr 9, 2018 5:43 AM in response to Loner T

Loner T wrote:


Alternative OS-specific pointing devices lead to confusion and problems with tracking, which is which. The other aspect is the financial outlay to have two sets of such.

Sorry Loner T, I don't see where the confusion lies. Just use the one that is working! And in terms of expense, really? I mean you can buy a reasonable mouse for Windows use for a few pounds. Really not a big consideration!

Apr 9, 2018 10:33 AM in response to klausfromlimburgerhof

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.

Apr 9, 2018 9:00 PM in response to klausfromlimburgerhof

Not sure if this will work for everyone.


A simple short term solution that seems to work for me every time is....


Remove the Magic Mouse device from MacOS.


Log into boot camp. Go into Bluetooth devices and remove the mouse and then re- add it.


You will have to do this every time you restart into boot camp but it only takes a minute or so.



Youn will also have to reinstall the Magic Mouse when you log back into the Mac ( but you should be prompted to do this automatically)

Apr 9, 2018 10:44 PM in response to Vmars1983

Vmars1983 wrote:


Not sure if this will work for everyone.


A simple short term solution that seems to work for me every time is....


Remove the Magic Mouse device from MacOS.


Log into boot camp. Go into Bluetooth devices and remove the mouse and then re- add it.


You will have to do this every time you restart into boot camp but it only takes a minute or so.



Youn will also have to reinstall the Magic Mouse when you log back into the Mac ( but you should be prompted to do this automatically)

That would have to depend on what it is you mean by “this will work”… People did come up with this before, and, whilst it does technically work, it is still very cumbersome indeed. As you’ve pointed out, you’d have to do it every time you’d want to use Boot Camp, and you’d have to do the remove; re-pair cycle on both MacOS and Windows upon leaving MacOS and booting into Windows; then again when the time comes to leave Windows and reboot MacOS.

You see, even me rephrasing it in this way makes it sound more cumbersome than I, and indeed anybody, would like. The sheer amount of hassle is way too much for me, and really shouldn’t be necessary. Prior to the two Windows updates mentioned multiple times in this thread, it wasn’t necessary at all; all devices would just play nicely with one another.

There really is no truly workable solution at the time, other than just using another mouse. If you so desire, you can choose to continue using the Magic Keyboard, because, most of the time, it will work just fine. But to be on the safe side, and indeed to not have to unpair; then re-pair the device if a connection dropout does occur, your best bet is to also use another keyboard with Windows, at least until either Microsoft or Apple come up with a fix.


Like I’ve pointed out before, a fix from Microsoft would be the more desirable scenario. Not only would that solve problems with peripherals by other manufacturers, should they exist, but it would also plainly be the way it ought to be, since their update was what broke it in the first place. Ironically, the update that botched it for Apple users has supposedly fixed some issues that arose when people used the Touch Keyboard on the Microsoft Surface series of devices.

Apr 11, 2018 3:26 AM in response to csteelooper

Yes, of course I'm really pleased that everything is working now, but it is, however, really annoying that we have to do a little registry hack to get scrolling working in the same direction in macOS and Windows.

As I said, it's a trivial little option that could easily be added to the Bootcamp Control Panel, and it is pretty annoying that for many years now Apple has done nothing to improve the poor configurability of the Trackpad and Mouse. Inverse scrolling is a standard feature of almost any other manufacturer trackpad/mouse control panel.

There is a 3rd party app herefor both Apple Trackpads and Mouse and they work well, but it is easy enough to do the hacks yourself if you feel comfortable with the registry editor.

Apr 11, 2018 6:28 AM in response to igmackenzie

I’d actually prefer doing it through the registry, as long as a first-party (i.e Apple/Microsoft) solution isn’t there. I’d rather not install all kinds of third-party stuff to accomplish just this one goal… I actually am amazed that it’s not just part of the Mouse settings in either the Settings app or the Control Panel. That’s where you do stuff such as setting tracking speed, double clicking speed and button assignment. So why isn’t “inverse scrolling” part of those settings? Beats me… But as long as it isn’t the case (either by default or through an updated driver) I’d prefer using the Registry Editor to accomplish it. Been doing loads of stuff that way since day one, so this won’t hold me back…

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.