Magic Mouse 2 is not working in the macOS 27?

Do you mind to share your Magic Mouse firmware? There is a user here that is working using a firmware 3.1.1. Mine is 1.9.2.

I am trying to check if this is correlated.

Thank you for the help in the investigation.

I think this is a glitch in Mac firmware showing in interface. Mine did the same when I plugged it in.

The right firmware is what shows you when it is disconnected.

You can also use in the terminal:

system_profiler SPBluetoothDataType | grep -A 20 "Magic Mouse" | grep "Firmware Version"

If you provide us with further logs we can compare and check if there are something that we can do or report.

Do you mind to share your Magic Mouse firmware? There is a user here that is working using a firmware 3.1.1. Mine is 1.9.2.

I am trying to check if this is correlated.

Do you mind to share your Magic Mouse firmware? There is a user here that is working using a firmware 3.1.1. Mine is 1.9.2.

I am trying to check if this is correlated.

Thanks for the reply. I tried it also, but even in security the problem still occurs. Just another different version of the macOS can support my current Magic Mouse Version 1.9.2... Sad, but true.

I turned on my Mac mini with macOS Tahoe and the Magic Mouse 2 is working perfectly.

Still... I get some logs and will share. Looks like that the handshake problem still persists... but for some reason the mouse works. Maybe they did a workaround for it to work? Not sure, and I don't care. But the point is, Magic Mouse is working properly in Tahoe but not on 27.

https://www.image2url.com/r2/default/files/1789559099899-68ea6cb6-d6b6-4236-a938-965be08eb0fd.txt

I will try to compare the logs later this day

I have a Magic Mouse 2 with usb-c to lightning port.

Not sure if assuming the external hardware conector is enough.

Also, I discovered in the log that in Mac OS 26 happens a WindowServer in the very last line:

2026-09-16 08:43:31.559077-0300 0x99b      Info        0x0                  105    0    WindowServer: (CoreUtils) [com.apple.bluetooth:CBDiscovery] Device found: CBDevice 07919989-33E5-B8B1-1405-ED427C237CC5, BDA <private>, Nm <private> , PID 0x0269 (?), PrNm Magic Mouse, VID 0x004C, VS 1, DsFl 0xA00000 < Connections Pairing >, DvF 0x40000024000 < ClassicPaired HIDBadBehavior Connectable >, DvT Mouse, RSSI -56, CnS 0x800020 < HID ACL >, SupS 0x20 < HID >, Freq 2.4, Battery M -64%, ClkH L NoiseManagement R NoiseManagement, FV '1.9.2', LsnM Transparency, LsMC 0x6 < ANC Transparency >, BTv 3.0, MicM Auto, Plcm M Enabled, Prim Unknown, Invl 11.25ms, srMd Disabled, spAM ContentDriven, HaSp No, HtSp No, CF 0x0 < >, initial

That doesn`t happen in the 27. Maybe a fallback event?

If I had to speculate I would say that the flag 0x40 makes the fallback not be triggered. And that was what makes versions 1.x.x keep working.

The versions 3.x.x probably are already working in the initial hid handshake, not needing the fallback action.

Well... I would love to have access to the code...

I am talking about generations and commercially spoken names. In Brazil is conventional to name the usb-c pure as Magic Mouse 3, as a certified resseller below uses:

Anyway I am not attached to names and terminologies we can name it tragic cat, barrel monkey or jumping dinossaur…

The point is that several users are reporting problems with evidences, logs and prints.

If yours is working it is excelent for you…

But if you really wish to help us, please send us a log of what happens when you turn you mouse on in the terminal. So we can compare and figure out if there’s a workaround to do before an oficial fix.

log stream --predicate 'subsystem == "com.apple.iohid" AND composedMessage CONTAINS[c] "Magic Mouse"' --info --debug

I also suggest all that are having this problem that open a bug report too:

Feedback - Magic Mouse - Apple

I think that it maybe helps Apple to prioritize this issue.

Thanks for the reply. I only did not tested yet the 1 min cooldown with the cable. I will try when back at home.

But before, when using the macOS 26 I changed the same Magic Mouse between a macmini m4 and a my currently MacBook without any problems.

After the update, the pairing is only recognizing it but without any actions: click, move, gestures.

I tried first without the other bluetooth mouse… but I’ll try this out top since I used other mouse in the beginning of the diagonais.

I have an iPad here too and not sure if it is interfering in the diagonis someway (never paired the Magic Mouse with it). But I’ll try isolating it too.

I’ll post the results later.

Thanks for the reply.