Problem Bootcamp Windows 10 & Bluetooth

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

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.

I reinstalled Win 10 from a previous back up I had and managed to get bluetooth back and working except the MM 2 still doesn't work, installed all the latest Win 10 updates up to April 2018, looked for the KB4088776 update to remove but it wasn't there.

Also now my iMac Pro speakers don't work and I can't install any of the Bootcamp drivers provided by Apple as .exe installers, they just error out.

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.

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!

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.

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

The Windows April 1803 update still doesn't fix the MM 2 issue or dead iMac Audio for me. The Apple supplied drivers also install without an error but sadly don't show up in device manager, and Microsoft support has been a joke and Apple support says talk to Microsoft. 😕

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.

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.

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.

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.

happymanslab wrote:

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.

So… Why exactly did you enable Hyper-V in the first place? It’s not like you’ll be virtualising another system from within Windows, will you? You’d be way better off using MacOS when it comes to that; at least if using a real Windows (Server-)based host is out of the question.

Anyway, for me, upgrading Windows 10 to build 1804 did seem to fix the issue. I did get the device driver update (Apple, Inc. — USBDevice) of which @emulajavi posted a screenshot, before then. I have had no problems since upgrading Windows to build 1804. But I do realise that this may still be only temporary… I’m on a 2017 iMac 27”, by the way.

What this does prove is that things are currently panning out very differently indeed for every one of us…

VGonzalez1973 wrote:

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?

Feel free to think whatever you want, but in this case Apple is at least partially right. The problem is not with the device driver itself; it has worked properly in Windows 10 since the inception of the OS. The problem was, in fact, caused by an update that Microsoft had released mid-February, which caused problems in particular with Bluetooth 4.x/LE devices. Devices that use older versions of the protocol were never affected by this issue to begin with, which is why the first generation of the Magic Mouse and Magic Trackpad DID work, as did the Apple Wireless Keyboard, since they used Bluetooth 2.0.

The part for which you could and, in my opinion, should blame Apple, is the absolute lack of configurability for the devices when used in Windows. The mice have no device-specific options at all, nor does the keyboard. Where the hotkeys are concerned, only volume and media control work (to some extent) and neither can be turned off. All of this functionality is provided by the Boot Camp Control Panel, and the user has NO influence over it, at all. THAT is where the blame for Apple lies. As far as the intermittent way in which some of the devices operate since the February security patches, that’s Microsoft at fault!

emulajavi wrote:

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.

Don’t exaggerate! If you want true support, it will take more than the alleged “week” to write, not least optimise the device drivers. A device driver that isn’t properly optimised can be worse than having none at all, as is the present situation… I do agree with the gist of your message, though… Apple would do us an enormous favour if they would finally come off the generic way the devices operate...