Recommended Posts

I have a 2017 Macbook Pro 15" and I have a bootcamp installation. For some reason Windows 10 will not work reliably at all with Bluetooth. I on occasion can get the device to pair, sometimes it'll connect just fine and work but eventually craps out. Sometimes it'll say it's connected but it actually wont work at all, sometimes it'll sporadicly work and the mouse will stutter across the screen. Other time it'll just say to attempt to repair. It always sees the devices broadcasting to be paired but it will 9 out of 10 times not work. This is with a logitech bluetooth mouse, a microsoft arc mouse, a microsoft ergonomic keyboard. I've tried running updates on the OS just to see, I've gone to the bluetooth drivers all of which are installed and checked for updates. I've tried resetting and doing a PR reset on the Mac. Bluetooth works perfectly on OS X this is just a problem with Windows. 

Well an update to this, I think I have found what solved the issue:

 

Control Panel > Device Manager > Network Adapters > Broadcom 802.11n Network Adapter (right click and choose "Properties".

Under the "Advanced" tab, highlight the setting named "Bluetooth Collaboration", then change it to Enable. Then click OK.

Spoke too soon, same problems. I've checked to see if i can install the bootcamp drivers from apple for bluetooth but when I do that the device stops working so forcing it to take those drivers doesn't work. The drivers windows installs are from 2006. It says Bluetooth Radio 6/21/2006 for the driver it forces me to use. 

  • 1 year later...

try and see if you can find the official bluetooth driver for the chipset instead of using the bootcamp supplied one to see if that helps

 

do you have the same reliability issues on MacOS side by chance? if so it could point to the hardware as well.

  • 2 months later...

So through trial and error on my 2018 Macbook Pro (with a T2 chip), and booted into Windows 10 with Boot Camp, I figured out a workaround to force my bluetooth speaker to not re-pair properly after a reboot. Steps to try:

  • someone suggested via this reddit post to fully power down the Mac, wait a bit, then boot directly to Windows. Applies if you're on Mojave
  • but that wasn't enough for me. So the next step was to remove all Bluetooth devices in the Settings app, then go into Device Manager and remove all Bluetooth hardware. Then Action > Scan for hardware changes, to readd Bluetooth hardware.

Removing all Bluetooth devices beforehand is important, as they magically pop back into Device Manager if you don't. Afterwards I was able to get my speaker to pair once again.

 

Depending on which Mac you have, with older Macs you probably have a separate Bluetooth driver. It might have options to turn off power saving; try disabling that if possible:

 

image.thumb.png.5db5cbfed233565808a2f412499a7939.png

 

... getting a Bluetooth speaker to work is a must, thanks to the T2 leading to a crap audio experience in Windows 10 - sound glitching, plus the Spotify app just causes all sound to cut out.

Edited by Denis W.
This topic is now closed to further replies.
  • Posts

    • Idiotic Teams strickes again. "Teams, Teams, I was not joking when I said I'd like to smash every tooth in your head Oh Teams Teams, I was not joking when I said By rights you should be bludgeoned in your bed"
    • KB5060829: Microsoft confirms new upcoming Windows 11 24H2 feature is triggering Firewall by Sayan Sen At the end of June, Microsoft released Windows 11 setup and recovery updates (KB5062233/ KB5060843/ KB5062197/ KB5061090) following the month's non-security previews for 24H2 (KB5060829) and 23H2/22H2 (KB5060826). Today, the company has confirmed that KB5060829 is causing some troubles for systems in regards to Firewall. Microsoft says that IT admins and system admins may notice a recurring error entry in the Security event log related to Windows Firewall With Advanced Security wherein the Event Viewer records event ID 2042, labeled “Config Read Failed” with the message “More data is available” each time the device restarts. Although logged as an error, the tech giant notes that this entry does not indicate a malfunction of the Windows Firewall and as such it can be "safely ignored and disregarded," and that Windows Firewall continues to enforce rules and filter network traffic normally as intended. Microsoft assures that "there is no impact to Windows processes associated to this event." IT support teams and even general users often rely on error-level event entries to detect misconfiguration and other issues (Microsoft itself recommends you do so), so unexpected log noise can trigger unnecessary alerts like these. Interestingly, in this case, the logged event stems from an upcoming feature as Microsoft notes that the "event is related to a feature that is currently under development and not fully implemented." No additional information regarding this new feature has been provided at this time. For those who prefer a cleaner log, administrators can filter out event 2042 in Event Viewer or via PowerShell. In Event Viewer, create a custom view filtering out ID 2042 under the Security log and in PowerShell, use the Get-WinEvent -FilterHashtable parameter. Microsoft says that the team is currently working on a fix and an update will be released later. However, no ETA has been shared today. You can find the issue entry here on Microsoft's official Windows Health dashboard website.
    • Concerning the situation at XBOX (title cancellations, studio closures and firing employees): The management at MS gaming division (Booty, Spencer etc.) has to go. Money and time has been wasted in such amounts that those people have to be held accountable and better managers can take the lead. In most other businesses this would have happened ten years or so ago.
    • Why, because different bothers you? You aren’t using the OS per your own admission so why is it a shame? It’s a great way to focus imo.
    • People often hate on what they don’t understand. It’s not stupid, it’s different. That said, ignorance more often than not rules the roost, so it is seen as stupid instead. How much time have you spent learning how to use macOS as intended before making your proclamation?
  • Recent Achievements

    • Week One Done
      filminutz earned a badge
      Week One Done
    • Reacting Well
      SteveJaye earned a badge
      Reacting Well
    • One Month Later
      MadMung0 earned a badge
      One Month Later
    • One Month Later
      Uranus_enjoyer earned a badge
      One Month Later
    • Week One Done
      Philsl earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      433
    2. 2
      ATLien_0
      158
    3. 3
      +FloatingFatMan
      146
    4. 4
      Nick H.
      65
    5. 5
      +thexfile
      62
  • Tell a friend

    Love Neowin? Tell a friend!