Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Microsoft Arc Touch Bluetooth Mouse

I have a Microsoft Arc Touch Bluetooth Mouse. When I try to pair my mouse to my 12" Macbook, it becomes available in Bluetooth menu. Hovewer, when I don't use mouse, it's off or I restart/shut down my computer, the system does not recognize the mouse. To solve this problem, I start the process of pairing both devices. Firstly, I remove the mouse from the list, then pair it again. I guess this is a systematical problem. I try to debug Bluetooth and some solutions available from the internet. Do you have any idea to solve the problem?

MacBook (Retina, 12-inch, Early 2016), macOS Sierra (10.12.1)

Posted on Nov 21, 2016 1:44 AM

Reply
Question marked as Best reply

Posted on Sep 27, 2017 8:23 PM

This is a classic example of two of the world’s leading lights, in technology, behaving badly/ineptly or some could say in collusion, by default, not necessarily with any malicious aforethought (one for the lawyers), perhaps…


The scenario runs like this:

Apple releases an update to its OS which changes the way it handles Bluetooth pairing. They will often do this regardless of any adverse effects these changes may cause to third party Bluetooth devices. Let’s face it, they often release updates that break their own Bluetooth devices, never mind third party ones.

This causes Bluetooth pairing issues with multiple vendor’s Bluetooth devices.

At this point the vendor of the Bluetooth device has two options:

  1. Officially end support for MacOS for the device and update their product support information on their Web site, to reflect this.
  2. Work with Apple to resolve the issue, whilst updating their product support information, detailing the known issue, until the issue is fixed and they are able to maintain proper support for the device on MacOS.

What has happened here is that Microsoft and Apple have not worked together, for whatever reason, to fix this bug. Add to this, Microsoft have not done the right thing and updated their product support information, for this device, on their Web site, to reflect either a known bug, that is being worked on, or official end for support of the OS, for this device.


In essence this is an example of both vendors not valuing the hundreds of people (check the thread counts for this issue on both the Apple and Microsoft support forums, as well as third party forums) who have, are and will continue to experience these problems, now and with future generations of Bluetooth devices. Ultimately, Bluetooth devices are seen as almost disposable peripherals. If the OS vendors break them, with OS updates, that change the way Bluetooth devices are handled, then they pretty well expect you to move on and buy another device that will work. This ongoing situation benefits both Apple and Microsoft, as well as other Bluetooth peripheral vendors, as it guarantees a reasonably significant percentage increase in sales of Bluetooth devices. In the end, the ultimate losers are, as usual, us suckers, at the bottom of the technology food chain.


The irony is that Bluetooth devices are often sold as the premium end of the peripheral market, with inflated prices to suit. Thereby making them less of a disposable device than cabled or RF wireless devices, which will undoubtedly work for you for longer, with fewer of these vendor driven, "built in obsolescence features”, AKA crappy Bluetooth support.

20 replies
Question marked as Best reply

Sep 27, 2017 8:23 PM in response to canyucel

This is a classic example of two of the world’s leading lights, in technology, behaving badly/ineptly or some could say in collusion, by default, not necessarily with any malicious aforethought (one for the lawyers), perhaps…


The scenario runs like this:

Apple releases an update to its OS which changes the way it handles Bluetooth pairing. They will often do this regardless of any adverse effects these changes may cause to third party Bluetooth devices. Let’s face it, they often release updates that break their own Bluetooth devices, never mind third party ones.

This causes Bluetooth pairing issues with multiple vendor’s Bluetooth devices.

At this point the vendor of the Bluetooth device has two options:

  1. Officially end support for MacOS for the device and update their product support information on their Web site, to reflect this.
  2. Work with Apple to resolve the issue, whilst updating their product support information, detailing the known issue, until the issue is fixed and they are able to maintain proper support for the device on MacOS.

What has happened here is that Microsoft and Apple have not worked together, for whatever reason, to fix this bug. Add to this, Microsoft have not done the right thing and updated their product support information, for this device, on their Web site, to reflect either a known bug, that is being worked on, or official end for support of the OS, for this device.


In essence this is an example of both vendors not valuing the hundreds of people (check the thread counts for this issue on both the Apple and Microsoft support forums, as well as third party forums) who have, are and will continue to experience these problems, now and with future generations of Bluetooth devices. Ultimately, Bluetooth devices are seen as almost disposable peripherals. If the OS vendors break them, with OS updates, that change the way Bluetooth devices are handled, then they pretty well expect you to move on and buy another device that will work. This ongoing situation benefits both Apple and Microsoft, as well as other Bluetooth peripheral vendors, as it guarantees a reasonably significant percentage increase in sales of Bluetooth devices. In the end, the ultimate losers are, as usual, us suckers, at the bottom of the technology food chain.


The irony is that Bluetooth devices are often sold as the premium end of the peripheral market, with inflated prices to suit. Thereby making them less of a disposable device than cabled or RF wireless devices, which will undoubtedly work for you for longer, with fewer of these vendor driven, "built in obsolescence features”, AKA crappy Bluetooth support.

Jan 6, 2017 5:16 PM in response to canyucel

@canyucel Could you by any chance share your com.apple.Bluetooth.plist file, located in /Library/Preferences/ ?


I'd love to get my hands on one from a working machine to test something. I've tested some edits in the past that got the Arc Touch to be recognized as a mouse, I am wondering if manually adding in the full configuration would make it work (even if just until the next re-pair).

Nov 24, 2016 11:52 PM in response to Barry Hemphill

I don't think it's a question to Microsoft.

You may see the specs. The mouse is meant to be compatible with Mac OS X 10.10. It was compatible with El Capitan (10.11), but it won't stay connected with Sierra (10.12) if you re-paired or initially connected the mouse with that OS. If you pair your mouse in El Capitan and then upgrade to Sierra then your mouse will restore connection and will function as it should (unless you re-pair it in Sierra). So the question should be addressed not to Microsoft but to Apple, I think. Something has got broken in Sierra. Correct me if I'm wrong.

Microsoft Arc Touch Bluetooth Mouse

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.