Problem Bootcamp Windows 10 & Bluetooth

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

When you first install Windows 10, then the Apple software everything works great. After the first round of Windows updates are installed the Magic Mouse 2 and the Magic Keyboard stop working.

Microsoft appears to be aware of there is an issue. Unfortunately, it appears that they are not exactly sure what the issue is yet. Few of the reports I have read are as specific as this user forum.

I have notified Microsoft about this forum through several venues. Hopefully something gets accomplished quickly.

Loner T wrote:

$129 - Buy Magic Keyboard with Numeric Keypad for iMac in Silver - Apple

$129 - Buy Magic Trackpad for iMac in Silver - Apple

A USB-wired mouse is available for USD3. If I have $250+ invested in these two, it will not be used (or wasted) on Windows. macOS provides much richer functionality for both of these devices.

Sorry Loner T, I really don't understand your point.

What we are saying is that you only need to spend a few pounds on a mouse for use in Windows until a fix is produced. MK works perfectly well in both OSs, it's just the MT2MM2 that screws things up in Windows. So, for that, just use a mouse as a pointing device. Probably costs less than $10. Doesn't affect your investment in the 2 Apple devices, both of which work perfectly well in macOS.

czaharop wrote:

Hello all,

So my Magic Mouse 2 was working just fine after the Windows update last week, now today I logged it to Windows through Bootcamp and the mouse won’t work!!! The keyboard works fine.

What happened? Anyone else? What to do?

Thanks

That would be seriously annoying… I haven’t tested yet. Since I haven’t powered on the Windows-side of my machine literally since my last post, I’d expect things to be where they were then. Having said that, it may well be the case that yet another update has been installed and brought you right back to where you were (as in: you’re mouse is back to not wanting to connect). So, the first thing you might want to do is to check the installed updates history and see if that was indeed the case. Check the dates as to when updates have been installed, and post the update(s) that have been installed since your last successful use here. That way, aside from informing fellow users, we could also investigate exactly what it is these eventual new updates have changed.

If there have been no new updates, that would be very strange indeed. I have used Windows multiple times after the last batch of new updates (which gave us the mouse back), with multiple restarts in between. That means that the resurrection of the mouse has been anything but a fluke. So if no new updates would have been installed since your last successful use and today, something else would have to be the matter…

Anyway, for the time being, it would be a waiting game once more… Because apart from finding out what updates might be the culprit, there really isn’t all that much we can do ourselves. For devices other than the Apple devices, we could perhaps try to obtain device drivers straight from the suppliers (i.e. Broadcom, Intel, AMD, etc.). But for any device made by apple or having been specifically modified for apple, such a thing would be very difficult indeed...

All of this means that we would be back to using different devices within Windows (specifically a different mouse), at least until Apple or Microsoft come up with a solution…

VGonzalez1973 wrote:

Who the heck must solve this? Apple? Microsoft? Came on, show some respect here!!!

Microsoft. Try W10 1607 release as a workaround, if you are willing to go back to an older W10 release.

Did a clean install of Win 10 1803 & Apple bootcamp drivers, MM 2, keyboard worked until restart. However my iMac Pro audio is now working and continuing to work so there’s that at least.

Bluetooth appears in device manager & beats solo 2’s pair and stay paired and work but MM 2 & keyboard won’t pair.

I have a Logitech craft keyboard using there USB dongle which works with no issues. Thinking of getting a Logitech mouse to pair with the dongle and forget about the janky Bluetooth issues with Apple drivers & microsft windows implementation.

Same issue.

Initially this worked fine. But then I enabled Hyper-V and this totally breaks all bluetooth on my iMac Pro.

Disabling Hyper-V made bluetooth work fine until I updated to Windows 10 1804 and now no bluetooth again.

I contacted Apple by telephone and in the end they told me to contact Microsoft because Windows is 3rd party software.

csteelooper wrote:

Apple would do us an enormous favour if they would finally come off the generic way the devices operate...

The current Bootcamp drivers are OEM'd by Apple from Microsoft. Once W10 starts installing standard WHQL drivers, Apple has no control on what W10 installs. As you pointed out BT2.0 works, but BT4.0/LE has issues due to the drivers from Microsoft, not Apple. W10 'forced' updates are another nightmare, all in the name of 'security'.

Loner T wrote:

The current Bootcamp drivers are OEM'd by Apple from Microsoft…

No, actually, they aren’t. There is no such thing, in this case, as drivers having been OEM’d. What is being used is the bog-standard mouse.vxd-driver (or whatever it may be called these days in Windows 10); not anything else whatsoever (apart, perhaps, from the communications part of it, what with the bluetooth connection needing to be established and maintained).

As far as you can even OEM such a thing as a driver, what that would refer to is, for example, when HP would use Logitech MouseWare and brand it as their own software, for their specific mouse. That is definitely not what is going on here.

Apple isn’t even using any device-specific software, for either mouse or keyboard. What they do comes down to the following: the system is informed that a device of class such-and-such is being installed, with Apple’s Vendor ID. Then the Apple “device driver installer” for the keyboard or mouse does little other then just telling the system: “um… Yeh, well, that device you’re on about is a mouse (or keyboard). Just give the user their input devices already, would you? The standard stuff will do…” That’s all there is to it. And exactly that is why there is absolutely no configuration at all. Apple doesn’t even have to OEM any device driver…

What they need to do to rectify this shallow level of support for their devices is to finally write their own stuff, and then tell Windows to use it instead of just the standard stuff. But like I said, such a thing is easier said than done, especially if you are planning to bring device specific features to the table. Because porting a device driver to another platform is even more difficult than adequately porting a general piece of software (I’m referring here, to having it optimised for the target platform; using all of the available resources and techniques). Most cross-platform software, these days, isn’t being ported in that way. Nearly everyone is, instead, using a code base, that works on all intended platforms, but can hardly be considered optimised for them. One notorious example of this is Spotify.

With device drivers, you can’t really afford to skimp on optimisation, as it is essential for all layers of the OS to really understand what is being asked by and/or for the device in question.

If possible, use non-BT 4.x/LE devices, till a solution is available.

Are there any Apple services that are set to 'manual' in the Account that does not work?

I haven't had much success uninstalling the following updates:

KB4074588 or KB4056892

Every time I uninstall them Microsoft Windows 10 either re-installs them or installs a cumulative update.

I have had exactly the same thing happen after the latest MacOS 10.13.3 was installed. Now when I boot into Windows and left click on my Magic Mouse 2, I get the overlay that says "connected" but the cursor does not move. I also reinstalled the Bootcamp drivers, but it did not help. I now must use a USB mouse in Windows on my iMac Pro.

Tom

Unfortunately, I stumbled upon this thread just a little too late, which meant that I had already reinstalled Windows. Now ,y keyboard is working properly, even without having to apply @Andrew's solution, but there's no such luck with the mouse... It just will not connect. Prior to the reinstall, it kept trying and failing. Now Windows just says Paired, but the bloody thing won't connect. There's no button to force a try in the UI either, but that may be because the device has to actually initiate the connection; not the computer. Unfortunately, uninstalling the updates mentioned above will not work, simply because they were applied as part of a big ol' cumulative update, and therefore cannot be uninstalled separately... The big menace here is that the mouse actually did work before Windows started applying updates... If only my Mighty Mouse wouldn't have had such a ridiculously short wire, it would have been possible to use it instead of the Magic Mouse 2 in Windows (as a temporary measure, one hopes), but now it really isn't... It really is kind of a shame that Microsoft felt the need to forcefully disable the mouse (or at least that's how I feel), even though it works just fine. The same was the case under Windows, until a few weeks ago. I guess I can only hope for improvement on the Windows side for this (i.e. a new update set out to fix this)...

I just sent Microsoft a tweet on Twitter about this issue. I encourage others with this issue to do the same.

Microsoft (@Microsoft) | Twitter

Windows (@Windows) | Twitter

I have found these teams helpful in the past.

Make sure you reference this forum in your tweets so Microsoft can see what has not worked.

Good suggestion… Before submitting feedback, please, at least temporarily, set the ‘Diagnostics’ level to Full in Windows 10’s privacy settings. After submitting a report, you may set it back to Basic, if you so desire.