Problem Bootcamp Windows 10 & Bluetooth

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

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!!!

I think that’s a lot of BS by Apple’s part. You manufacture a device? - You provide the drivers! Apple should care about Magic Mouse, Magic Trackpad, Magic Keyboard, and any other device drivers for Windows. They just don’t.

To say that Windows is a 3^rd party software and wash their hands, is more of the old stupidity. A lot of us Software Engineers, Developers, Programmers, are buying Macs because the warranty that we can run both Windows and MacOS. That capacity changed the Mac from being a toy to be a professional tool. It is Apple trying to prove us wrong?

Why is it so difficult for Apple to release proper drivers for its products for Windows??

In one week they could program drivers with all the multi fingers gestures for MM2 and MT2 and also enable Bluet pairing by plugging in the Lighting cable, like on macOS.

csteelooper wrote:

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 do you think of the following drivers?

csteelooper wrote:

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.

If Windows forces it's own drivers, then yes.

From Bootcamp.xml...

<Name>Apple USB Ethernet Adapter

<InfName>AppleUSBEthernet.inf</InfName>

<Class> Net</Class>

<ClassGUID> {4d36e972-e325-11ce-bfc1-08002be10318}</ClassGUID>

<CatalogFile> AppleUSBEthernetex.cat</CatalogFile>

<Provider> "Apple Inc."</Provider>

<DriverVer> 02/01/2008, 3.8.3.10</DriverVer>

<ServiceBinary>AppleUSBEthernet.sys</ServiceBinary>

<HardwareID></HardwareID>

<isX64>no</isX64>

</Name>

....

<Name>Apple Wireless Mouse

<InfName>AppleBMT.inf</InfName>

<Class>HIDClass</Class>

<ClassGUID>{745a17a0-74d3-11d0-b6fe-00a0c90f57da}</ClassGUID>

<CatalogFile>applebmt.cat</CatalogFile>

<Provider> "Apple Inc."</Provider>

<DriverVer>06/01/2011,4.0.0.1</DriverVer>

<ServiceBinary>applebmt.sys</ServiceBinary>

<HardwareID></HardwareID>

<isX64>no</isX64>

</Name>

<Name>Apple Wireless Mouse

<InfName>AppleBMT64.inf</InfName>

<Class>HIDClass</Class>

<ClassGUID>{745a17a0-74d3-11d0-b6fe-00a0c90f57da}</ClassGUID>

<CatalogFile>applebmt64.cat</CatalogFile>

<Provider> "Apple Inc."</Provider>

<DriverVer>06/01/2011,4.0.0.1</DriverVer>

<ServiceBinary>applebmt.sys</ServiceBinary>

<HardwareID></HardwareID>

<isX64>yes</isX64>

</Name>

<Name>Apple Wireless Trackpad

<InfName>AppleWTP.inf</InfName>

<Class>HIDClass</Class>

<ClassGUID>{745a17a0-74d3-11d0-b6fe-00a0c90f57da}</ClassGUID>

<CatalogFile>applewtp.cat</CatalogFile>

<Provider> "Apple Inc."</Provider>

<DriverVer>10/29/2011,5.0.0.0</DriverVer>

<ServiceBinary>applewtp.sys</ServiceBinary>

<HardwareID></HardwareID>

<isX64>no</isX64>

</Name>

<Name>Apple Wireless Trackpad

<InfName>AppleWTP64.inf</InfName>

<Class>HIDClass</Class>

<ClassGUID>{745a17a0-74d3-11d0-b6fe-00a0c90f57da}</ClassGUID>

<CatalogFile>applewtp64.cat</CatalogFile>

<Provider> "Apple Inc."</Provider>

<DriverVer>10/29/2011,5.0.0.0</DriverVer>

<ServiceBinary>applewtp.sys</ServiceBinary>

<HardwareID></HardwareID>

<isX64>yes</isX64>

</Name>

csteelooper wrote:

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.

There has always been a 'closed' model to Apple drivers. It is used a marketing distinction. Gestures could be supported on Windows, but it has conciously not supported them, to keep such a distinction. OSes like Linux (and all such derivatives) have challenges in trying to fully exploit the hardware capabilities on Macs.

Same Problem here. Spent hours already and no solution. Very frustrating.

Exactly the same situation here. I tried the very old Apple wireless keyboard with AA batteries. It works. But the magic keyboard? Magically, no. Any solution now?

Ah, only the second generation, that would explain it.

What good will re-installing Windows do? I tried that and it made no difference.

Just thinking about the MT2, would it work using the MT1 driver?

Thanks, but i was talking about the Magic Trackpad 2 maybe being able to use a Magic Trackpad 1 driver if a separate one exists.

That is not the case. There is a MT1 and a MT2 and I have owned both! Even look very different,

Unfortunately, your suggestion re updating BT drivers has made no difference. Still no activity whatsover from my MT2.

I noticed that the big Windows update to 1803 is happening on April 10. Wonder if that will make a difference to our issue.

Made no difference removing the keyboard. I uninstalled it and used a wired keyboard, but the MT2 was still not recognised.