User level: Level 1 (5 points)the latest version of Magic Mouse, on MacBook Pro M5, has stopped working after upgrading to macOS 27. and after calling tech.support the answer is that they have no solution. it's a big shame to Apple, to address it like that
Posted on Sep 28, 2026 12:38 AM
User level: Level 10 (123,805 points)Sep 28, 2026 2:31 AM in response to leo_wanderer
There is very little technical information in the original description to begin meaningful troubleshooting.
The fact that the Magic Mouse stopped working after upgrading to macOS 27.0 is useful, but it does not by itself identify the cause.
The fact that Apple Support was unable to provide a solution also does not establish whether the problem is caused by macOS 27, Bluetooth, pairing, the mouse, or another factor.
First, turn the Magic Mouse off and on again, making sure the green indicator is visible.
Make sure Bluetooth is enabled on the Mac, then connect the mouse directly to the MacBook Pro with its USB-C cable.
Leave it connected for about a minute.
Apple states that this should pair the mouse with the Mac and charge its battery. The cable is used for pairing and charging; it must be disconnected for the Magic Mouse to be used wirelessly. Apple's Magic Mouse connection troubleshooting
If it still does not work, open System Settings >> Bluetooth and check whether the Magic Mouse appears and whether it is connected.
If Bluetooth cannot be turned on, Apple recommends restarting the Mac and trying again.
If the mouse appears but does not connect or remain connected, possible wireless interference can also be considered.
Resolve Wi-Fi and Bluetooth issues caused by wireless interference
The most useful additional information is whether the Magic Mouse appears in Bluetooth, whether it pairs when connected by USB-C, whether it works after the cable is disconnected, and whether another Bluetooth mouse works with the MacBook Pro.
Those observations would help determine what to investigate next.
If the Mac recognizes the Magic Mouse, its firmware version can be checked in System Information >> Bluetooth.
Apple documents firmware updates for supported rechargeable Magic accessories when they are connected and charging while the Mac is awake. Apple's Magic accessory firmware information
Apple's current specifications list the USB-C Magic Mouse as requiring macOS 15.1 or later, so macOS 27 falls within Apple's stated system requirements.
This does not establish the cause of the reported problem. Magic Mouse (USB-C) technical specifications — Apple Support
If the mouse remains unusable after these checks, the next step would be to document the Bluetooth status, USB-C pairing behaviour, and results with another mouse and provide those specific observations to Apple Support. That gives Apple more concrete information than simply reporting that the mouse stopped working after the macOS 27 upgrade.
If you can't connect your Magic Keyboard, Magic Mouse, or Magic Trackpad to your Mac — Apple Support
User level: Level 9 (72,871 points)Sep 28, 2026 4:15 AM in response to leo_wanderer
Apps like Mac Mouse Fix, Logitech Options+, or BetterMouse that modify event handling or synthesize trackpad gestures can conflict with macOS 27.
Troubleshooting Steps
See if the problem is present when you boot in safe mode. That process performs some system cleanup and clears caches, and also disables 3rd party extensions that may cause problems.
Start up your Mac in safe mode - Apple Support
If that does not correct the issue, test in a new user account. A newly-created user account will have all settings at default, and if the issue does not occur in that new account then it provides guidance on what may need to be changed to correct the issue.
Add a user or group on Mac - Apple Support
Once the testing is complete, the new account can easily be deleted.
Delete a user or group on Mac – Apple Support
Those steps will help to isolate the problem.
It might help to download and run EtreCheck, written by a long-time forum member. The free version is fine. Post the full report using the Additional Text button. No personal information is revealed.
More from Apple: If you can't connect your Magic Keyboard, Magic Mouse, or Magic Trackpad to your Mac - Apple Support
Personally, I also have the 'latest' (USB-C) Magic Mouse, and it works fine on my 16" M4 Pro MacBook Pro running macOS 27 Golden Gate.
User level: Level 10 (123,805 points)Sep 28, 2026 5:05 AM in response to leo_wanderer
Since the Magic Mouse stopped working after upgrading to macOS 27.0, I would first work through Apple's documented troubleshooting rather than assume that macOS 27 or a particular third-party application is responsible.
Turn the Magic Mouse off and on, make sure Bluetooth is enabled, and connect the mouse to the Mac with its charging cable for about a minute before disconnecting it.
Then try pairing it again. Apple recommends these steps for Magic Mouse connection problems:
Apple Support — If you can’t connect your Magic Keyboard, Magic Mouse, or Magic Trackpad to your Mac
If the problem continues, start the Mac in Safe Mode and test the mouse.
Apple says Safe Mode can help determine whether software that loads during startup is contributing to the problem:
If the mouse works in Safe Mode, then third-party mouse utilities or other startup software are worth investigating.
However, there is not enough evidence to say that applications such as Mac Mouse Fix, BetterMouse, SteerMouse, or Logitech Options+ are incompatible with macOS 27.
If the mouse still does not work, test it in a newly created macOS user account.
If it fails there as well, that makes a problem specific to your normal user account less likely:
These tests should help determine whether the problem is related to the mouse/Bluetooth connection, user settings, or software loaded during startup.
They do not, by themselves, establish that macOS 27 has a Magic Mouse compatibility problem.
User level: Level 1 (5 points)Sep 28, 2026 3:23 AM in response to Owl-53
clearly, I did all "forget this device" and reconnect activities before contacting tech.support. their answer was this being a known issue and no solution until new version of macOS 27 being released
Originally posted at discussions.apple.com/thread/256366347