​​ ​

The Apple Support Community will permanently close on November 20, 2026. Starting today, the site will no longer accept new posts and is available in a read-only state.


You can continue to find trusted guidance and support on the official Apple Support site. 


We want to thank the community members who have contributed their time and expertise to help others with their Apple products.


Magic Mouse 2 is not working in the macOS 27?

Magic Mouse 2 Stopped working completely after update for MacOS 27. It was working perfectly (in the way of a Magic Mouse) prior the update.


Now it shows it is paired and connected, but still no moves, no clicks and so no gestures. It stop completely only showing in the bluetooth that it is connected.


Anyone else with a similar problem?


Already tried disconnecting, re-paring and so on... nothing works until now.


Currently using a MacBook Air:

Trackpad working properly and another common mouse bluetooth also.


[Edited by Moderator]

MacBook Air 13″, macOS 27.0

Posted on Sep 15, 2026 7:23 AM

Question marked as Top-ranking reply

Posted on Sep 18, 2026 2:17 PM

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.

83 replies

Sep 16, 2026 4:57 AM in response to fábio161

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

Sep 16, 2026 7:10 AM in response to fábio161

It features a USB-C port and includes a woven USB-C Charge Cable that lets you pair and charge by connecting to a USB-C port on your Mac, so you can charge all of your favourite devices with just a single cable.


Apple sometimes delivers Firmware for their accessories


Though, there is No Direct URL to download the Firmware


That is usually done by Apple in the Background and without a User Direct Intervention

Sep 17, 2026 6:09 AM in response to dialabrain

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...

Sep 18, 2026 8:59 AM in response to dialabrain

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


Sep 18, 2026 9:37 AM in response to fábio161

Hi there, well I have the same problem wil my MacBook Neo, ( first time Mac ) last Monday I updated it to MacOS 27 and my mouse also stoped working and the software version is also 3.1.4. but when I put it on the cable is give me the software version 4.2.1. and let me tell you in advanced , I am new to MacBook so still discovering

Sep 22, 2026 7:15 PM in response to fábio161

It seems that Bluetooth isn't working at all. It wants to connect to my AirPods (The one thing I never want it to do.) It briefly connected to my Apple Magic Keyboard, but then it dropped it. My Logitect "MX Master 3S for Mac" never appears at all. It's a real pain. There's no Bluetooth icon in the top menu.

My 2021 MacBook Pro was repaired and I reloaded from Time Machine. Apple of course automatically returned my MBP with Golden Gate 27.0 on it. It's not an Intel Chip machine. I guess I'll call Apple Care, do that shuffle and then dig back into Time Machine are reinstall the old OS....

Sep 15, 2026 9:05 AM in response to Owl-53

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.

Sep 16, 2026 4:01 AM in response to Owl-53

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.

Sep 16, 2026 6:35 AM in response to fábio161

I had the same issue with Magic Mouse (lightning model) after updating to macOS27 Golden Gate.

I have also already attempted disconnection, re-pairing, connecting via usb charge for firmware update and all related troubleshooting steps; but the issue persists.

Magic Mouse seems to be connected but it does not respond.

(I had to buy a USB Logitech just for that but now I've lost one port.)

Is there any official answer to that bug?

Any tested way to fix it?



Sep 16, 2026 8:02 AM in response to fábio161

My firmware:


Magic Mouse de Fábio:

Address: D0:03:4B:FF:65:C4

Vendor ID: 0x004C

Product ID: 0x0269

Firmware Version: 1.9.2

Minor Type: Mouse

RSSI: -55

Services: 0x800020 < HID ACL >


For what I have read, looks likes it is possible a cap due to the microcontroller of the Magic Mouse. Magic Mouses 2 can have different microcontrollers...

Magic Mouse 2 is not working in the macOS 27?

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