Magic Mouse 2 is not working in the macOS 27?

Same here: Mac mini M4, macOS 27.0, Magic Mouse 2 (0x0269, firmware 1.9.2).

I think I found what the driver is skipping. On macOS 26 the mouse receives a feature report that switches it out of boot-mouse mode into multi-touch mode. On 27 that report is never sent, so the mouse connects, reports its battery, and then just sits there waiting. The Linux hid-magicmouse driver sends the same four bytes: F1 06 01 37.

Sending it by hand brings the mouse back instantly. I put up a small program that does exactly that - one C file, no binary to trust, no network, nothing left running unless you install the optional LaunchDaemon:

https://github.com/oleksandr-antonian/macos27-magic-mouse-fix

Credit for spotting the report goes to o0mohd0o/MagicMouseFix - I verified it and wrote my own version so the source is short enough to read before running.

Still worth filing Feedback with Apple. This is a workaround, not a fix.

Confirmed: MagicMouseFix 1.0.0 works with the USB-C Magic Mouse A3204, firmware 3.1.4, on an Apple silicon MacBook Pro running macOS 27.0. The mouse appeared connected and showed its battery level, but there was no pointer movement, clicking, scrolling, or gestures—even in Safe Mode. After installing MagicMouseFix and allowing Input Monitoring, all functions started working immediately.

Same issue here: macOS 27.0 (26A5416b), Magic Mouse 2, firmware 1.9.2. Re-pairing, Bluetooth reset, and Safe Mode don't help.

Cause: macOS 27 never sends the mouse the feature report that turns on multitouch mode, so AppleMultitouchMouseHIDEventDriver never creates its AppleMultitouchDevice. The mouse is connected but its input goes nowhere.

Check: in Terminal, hidutil list | grep -i 0x269 | grep AppleMultitouchDevice prints nothing if you're affected.

I wrote a small open-source workaround: one Swift file, MIT, no sudo, no network. It sends the missing report only when the driver is stuck and stays idle otherwise: https://github.com/imamirezaei/magic-mouse-wake

Heads-up: the earlier workarounds stop working on newer 27.0 builds, because bluetoothd rewrites the report ID for each interface (KeyholeReportID). This one targets the correct interface. Please also report the bug to Apple through Feedback Assistant.

The fact that another non-Apple Bluetooth mouse works normally is an important diagnostic factor. 

It indicates that the Mac’s Bluetooth hardware and general Bluetooth mouse functionality are working, making a system-wide Bluetooth failure less likely. 

However, it does not by itself establish that the other mouse is causing the Magic Mouse problem.

To rule out possible interference or an HID-device interaction, disconnect or turn off the non-Apple Bluetooth mouse completely, restart the Mac, and test the Magic Mouse with it as the only connected mouse. 

If the Magic Mouse then works, the other mouse or its associated software may be involved. 

If the Magic Mouse still does not work, that further supports the possibility of a problem specific to the Magic Mouse’s HID initialization in macOS 27.

An Aside. I have 2 Magic Mice each used on 2 separate M-Class Desktop computers.

Both are operating macOS 27 Golden Gate and both Magic Mice 2's work flawlessly 

If the other mouse has manufacturer software or a utility that modifies mouse behaviour—such as Logitech Options+, BetterMouse, SteerMouse, Mac Mouse Fix, or similar, that is also relevant and should be identified before making further changes.

At this point, I would not change HID settings or repeatedly re-pair the Magic Mouse. First, eliminate the other mouse as a variable and then check whether macOS is actually registering the Magic Mouse’s HID interface with hidutil list.

Follow the previous advise - First

If no success,  being the following trouble shooting steps

Your Magic Mouse 2 appears connected in Bluetooth, but it does not track, click, scroll, or perform gestures, while the MacBook Air's built-in trackpad and another Bluetooth mouse work normally.

Check the Magic Mouse's charge, turn it off and back on, then connect it to the Mac with its charging cable for at least one minute.

Apple recommends connecting the mouse by cable to pair it with the Mac and charge its battery. Apple Support: If you can't connect your Magic Keyboard, Magic Mouse, or Magic Trackpad to your Mac

If the mouse remains unresponsive, use the trackpad to open System Settings >> Bluetooth, remove the Magic Mouse, and pair it again using the cable. 

Then disconnect the cable and test it wirelessly. Restart the Mac if the problem persists.

If the Magic Mouse still shows as connected but does not respond after these steps, the next step should be based on whether it works after being re-paired and whether the problem occurs only wirelessly or also when connected by cable. 

I would not yet delete Bluetooth files or use Terminal commands to reset Bluetooth.

These steps do not establish that macOS 27 caused the problem; they first establish whether reconnecting the mouse resolves the issue and whether the problem persists after Apple's standard pairing and charging procedure.

Your testing establishes an important fact: the same Magic Mouse 2 works normally with an iPad running iPadOS 26, but does not move the pointer or click when connected to devices running macOS 27 and iPadOS 27. 

The mouse is recognised and connected on the version 27 devices, while the Magic Keyboard continues to work.

Apple's documentation confirms that Magic Mouse is supported with iPadOS and provides instructions for pairing and reconnecting it. (Apple Support) 

Apple also provides standard troubleshooting steps for Magic Mouse connection problems on Mac. (Apple Support)

Because the same mouse works on your iPad running iPadOS 26, your test demonstrates that the mouse is capable of functioning normally. 

It also demonstrates that the problem occurs with this mouse when it is used with your devices running macOS 27 and iPadOS 27.

However, these tests do not by themselves prove that macOS 27 or iPadOS 27 contains a confirmed Magic Mouse bug. 

I could not find an Apple document confirming this specific problem. Apple released macOS 27 and iPadOS 27 on September 14, 2026, so these are newly released software versions. (Apple)

Therefore, the most technically accurate conclusion is that you have identified a reproducible difference between the operating-system versions: the Magic Mouse 2 works with iPadOS 26 but, in your testing, does not function correctly with macOS 27 or iPadOS 27. 

A software issue in the newer operating systems is one possible explanation, but it has not been confirmed by Apple.

At this point, there is no evidence from your testing that the mouse should be replaced as defective. 

Keeping the mouse and waiting for a subsequent Apple software update is reasonable, while recognising that Apple has not yet confirmed that a future update will resolve this particular problem.

If the problem continues, submitting a report to Apple with these exact cross-version test results would be useful because it clearly documents the difference: the same Magic Mouse 2, working on iPadOS 26, but not functioning correctly on macOS 27 and iPadOS 27.

Use the Product Feedback 

The same thing happened to me (M4 MacBook Air). MagicMouseFix - https://github.com/o0mohd0o/MagicMouseFix solved the issue. I'll keep it in my mac until an official fix is released.

I found from some other source that you have to plug in the mouse to the MacBook. Then it showed up in Bluetooth. Same for the Magic Keyboard. This worked in 27. When I erased and went back to 15.8 I had to do this same thing. I’d never had to do it before. It’s not a big deal, but it is if instead of this clear simple process, the computer never says this.

beautiful fix thank you, it worked! inspired by it, i tweaked it a bit to be a command to run locally, on demand, without having to root.

https://github.com/khaledhawari/magic-mouse-2-fix-os27

HOW TO USE

1. Keep these three files together in the same folder.

2. Make sure the Magic Mouse is switched on and connected through Bluetooth.

3. Double-click "Wake Magic Mouse.command".

4. If Apple Command Line Tools are missing, the launcher will offer Apple's

installer. Complete that installation, then run the launcher again.

5. If macOS reports that HID access was denied, open:

System Settings > Privacy & Security > Input Monitoring

Enable Terminal, quit Terminal completely, and double-click the launcher again.

6. A successful run prints:

Success: the native Magic Mouse driver is active.

Please test if the mouse works in Safe Mode.

In another thread the author mentioned that the built-in trackpad of his mac worked but mice and even a Magic Trackpad didn’t. This suggests a driver problem. Safe Mode might help us confirm that.