Magic Mouse 2 not working after macOS 27 update

Question

Level 1

50 points

Magic Mouse 2 not working after macOS 27 update

Hi everyone,

I'm having a serious issue with my **Apple Magic Mouse 2 (Lightning version)** after updating my **MacBook Neo** from macOS 26 to **macOS 27**.

**Before the update:** The mouse worked perfectly, no issues at all.

**After the update:**

- The mouse connects via Bluetooth. In settings, it shows the battery level and firmware version **1.9.2**.

- When connected via Lightning cable, the system shows firmware version **8.6.0**.

- **The main problem:** The sensor does not work. The cursor does not move, and no buttons respond. The mouse is recognized by the system, but does not function as an input device.

What I've already tried (all standard troubleshooting steps):

- Removed the device from Bluetooth list and re-paired it.

- Reset the Bluetooth module (Option + Shift → Reset the Bluetooth module).

- Rebooted the MacBook (normal restart and full shutdown).

- Connected the mouse via cable and left it charging for several hours.

- Checked Bluetooth settings in the system — everything is enabled correctly.

- Tried connecting the mouse to another device — it works there, so the issue is specific to macOS 27.

- Deleted mouse plist files to reset settings.

All standard solutions recommended by Apple and found in official sources have been tried. None of them worked.

Additional information:

- Device: MacBook Neo

- macOS version: 27

- Mouse model: Apple Magic Mouse 2 (Lightning)

- Mouse firmware (via Bluetooth): 1.9.2

- Firmware shown when connected via cable: 8.6.0

Question: Is this a known compatibility issue between macOS 27 and Magic Mouse 2? If so, when can we expect a fix? If not, what else can I try?

Any help would be greatly appreciated.

MacBook Neo

Posted on Sep 16, 2026 12:56 PM

Reply

Answer 1

Top-ranking reply

CITY34DR Author

Level 1

50 points

Sep 20, 2026 7:05 AM in response to fábio161

Just wanted to confirm — the second option works perfectly! I installed the GUI version from o0mohd0o/MagicMouseFix (the notarized app), gave it Input Monitoring permission, and the mouse came back to life within seconds.

Here's the link for anyone else who needs it:

https://github.com/o0mohd0o/MagicMouseFix

Thank you so much for your help and for pointing me to this solution. I was about to give up on the mouse entirely, but now it works like nothing ever happened.

Really appreciate the time you put into this investigation. It's frustrating that Apple hasn't fixed it yet, but at least we have a working workaround.

Thanks again!

Reply

Answer 2

Sep 16, 2026 2:43 PM in response to CITY34DR

I’d focus on the firmware first. Apple says the firmware version to check is the one shown under System Information > Bluetooth, and rechargeable Magic accessories should be on firmware 2.0.6 or later. Your 1.9.2 reading is therefore worth looking into.

Make sure System Settings > General > Software Update > Automatic Updates has “Install system data and security updates” enabled. Then connect the Magic Mouse by Lightning, leave it switched on, and leave the Mac idle but awake. Apple says the accessory firmware updates automatically in the background and may need to be left connected overnight.

Disconnect the cable before testing the mouse. A Magic Mouse can’t be used while it’s charging.

If it still shows 1.9.2 and works normally with another device but not with macOS 27, I’d also test it once in Safe Mode. If the same thing happens there, that would help rule out third-party software.

I don’t see Apple currently listing this as a known Magic Mouse/macOS 27 issue, and nobody here can give you a date for a fix that Apple hasn’t announced. If it persists, I’d report it to Apple and include the exact macOS 27 build number and the firmware readings you posted.

Reply

Answer 3

Sep 18, 2026 3:46 AM in response to CITY34DR

This might be the same underlying bug I've been tracking (see my post above) — but there's one variable that made all the difference in my testing, so it'd help to confirm: what chip is your "MacBook Neo" — is it M1-class, or a newer generation (M2/M3/M4/M5)?

The reason I ask: I reproduced this exact symptom (mouse shows Connected with correct battery/firmware info, but zero cursor/click input) on two separate M1 Macs, but the identical mouse worked completely normally on a friend's Mac with a newer chip, running the same macOS 27 build. So this looks like it's specific to the Bluetooth controller in M1-generation Macs, not a universal macOS 27 issue — which would matter here since you're on a different mouse model (Magic Mouse 2 vs. the current Magic Mouse).

If you have Terminal access, it'd also help to check whether you're hitting the same root cause I found. Try this while moving the mouse:

log show --style compact --last 3m --predicate 'process == "bluetoothd"' | grep -i "isHIDShimDevice"

If you see a repeating line like:

"isHIDShimDevice: Device [address] is a modern Apple HID and supportsUserSpaceHIDDriversOnMacOS() is true -- return false"

...that's the exact same failure signature I found — the mouse is being routed away from the legacy Bluetooth HID path but never picked up by the newer one, so no input ever reaches the system despite showing "Connected."

If your Mac is M1-class and you see that log line, this is very likely the same regression, just also affecting Magic Mouse 2 — worth combining reports so Apple sees this as one issue instead of two.

Reply

Answer 4

fábio161

Level 1

128 points

Sep 19, 2026 2:44 AM in response to CITY34DR

Just FYI there are 2 repos in GitHub that claims a solve to this matter:

This is from an user here in the apple discussions, xander-ag,. The entire discussion occurred in my thread quoted above and is a proven solution for me:

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

The other method is quoted by the xander-ag repo and looks likes more for non dev users with a small gui installation:

https://github.com/o0mohd0o/MagicMouseFix

But I did not tried the second… but xander-ag claims that it is the source of his approach.

Reply

Answer 5

fábio161

Level 1

128 points

Sep 17, 2026 9:39 AM in response to CITY34DR

I created this thread with the same problem:

Magic Mouse 2 is not working in the macOS… - Apple Community

As far as the current investigation suggests it is a a bug in the macOS 27 for Magic Mouses 2 with firmware 1.x.x

If you depends on it, the faster way to solve is rolling Back to version 26.

If you can wait some weeks is probably that Apple will address the bug. But it is interesting to submit the bug report for them prioritize it.

Reply

Answer 6

fábio161

Level 1

128 points

Sep 18, 2026 9:13 AM in response to CITY34DR

My methodology was comparing logs with a working enviroment and a not working enviroment.

In my case I could only isolate with different Macs (Mac Mini and MacBook Air).

But with different macOS versions: 26 (last stable release) and 27.

I opened the terminal in both with the Magic Mouse turned off and put in it:

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

This will make the terminal waiting for some kind of events of your operational system filtered by Magic Mouse.

So you can turn on your Magic Mouse and wait for events to appear.

When the events stops, maybe you wish to share in some sort of sharing logs online, so we can compare.

In the thread that I quoted here before I did some comparisons and flagged some differences.

Reply

Answer 7

CITY34DR Author

Level 1

50 points

Sep 29, 2026 8:09 PM in response to CITY34DR

Just updated to macOS 27.0.1 and the Magic Mouse 2 issue is still there. Same as before: it connects, shows battery, but doesn't work.

So Apple apparently hasn't fixed it yet. Has anyone else tried 27.0.1? Did it work for you, or are you still stuck like me?

I'm still using MagicMouseFix (the community fix) and it works, but it's a workaround, not a real fix. Just wondering if anyone got it working natively after this update.

If Apple still hasn't fixed it, I'll keep using the fix for now. But it's pretty disappointing that they haven't addressed this after almost two weeks.

Reply

Answer 8

Sep 20, 2026 3:47 AM in response to CITY34DR

Ik heb het zelfde probleem met de MacBook Air M5 wel verbinding en verbonden maar de Magic Mouse doet niets heb contact gehad met Apple hun advies na àlles geprobeerd te hebben aan mogelijkheden op internet en AI ga langs een Apple reparateur.

aangezien mijn Apple Magic Mouse 2 net 7 weken oud is heb ik hem voor de garantie opgestuurd voor reparatie.

nu lees ik dat het een software fout is in de update van Apple27

de medewerkster van Apple die ik aan de lijn had waar ik *** aan vroeg zei dat hun nooit over fouten in updates spraken met gebruikers

hoop dat het snel wordt opgelost

werk nu met een goedkope draadloze muis die perfect werkt de logi silent touch M240

Reply

Answer 9

CITY34DR Author

Level 1

50 points

Sep 16, 2026 11:14 PM in response to PreCognition

Thanks for the advice, but I've already tried all of that. I connected it and left it like that for over 5 hours while I was working with the screen active. Honestly, this whole Magic Mouse firmware update process feels like something out of the Middle Ages. What kind of nonsense is this? Why can't I just plug it in and hit "Check for updates"? No — instead you have to sit there and wait and hope that it deigns to update itself in the background. This is the worst update mechanism I've ever seen from any mouse manufacturer.

And on top of that, I don't even have a button to contact Apple Support. So I can't just report this to them the way you're suggesting — there's simply no option for me to do that.

Reply

Answer 10

CITY34DR Author

Level 1

50 points

Sep 17, 2026 10:00 AM in response to fábio161

Thank you for the response and for investigating this.

I can confirm the same thing: I tested my Magic Mouse 2 on my Mac mini, which is still on macOS 26, and it works absolutely perfectly there. So the issue is 100% on the macOS 27 side, not the mouse itself.

About the "connect it and wait for the firmware update" advice — I tried it. I left the mouse connected via cable for 3 hours, and the firmware stayed at 1.9.2. It didn't update. So that method is basically useless, at least in my case.

I really hope Apple doesn't mess this up again and actually releases a fix, because right now the situation is: you buy their product, and they just don't care that it stops working. That's really disappointing and makes you think twice before buying their devices again.

I'll submit a bug report as you suggested. Thanks again.

Reply

Answer 11

CITY34DR Author

Level 1

50 points

Sep 17, 2026 1:27 PM in response to fábio161

I agree — on my Mac mini I use a Logitech MX Master 3S, and it works perfectly on both macOS 26 and 27. Why Apple is so incompetent, I just can't understand. A huge company, and such a screw-up... it's a total mess.

For now, I'll have to use the Xiaomi Dual-mode Wireless Mouse 2 (Comfort Edition), which costs around $11–12. It supports both Bluetooth and a USB receiver — and it works perfectly.

Reply

Answer 12

fábio161

Level 1

128 points

Sep 18, 2026 4:42 AM in response to Souravjha

Thanks for the help!

My MacBook where the Magic Mouse 2 (usb-c to lightning) stop working is an Air M5 newer model.

My Mac Mini where my same Magic Mouse 2 works is a M4 model.

The firmware of my Magic Mouse is 1.9.2.

I’ll run the command in the terminal for you later to help you diagnose.

Also in the thread above there are some investigations running where you can get more data for yours.

Reply

Answer 13

CITY34DR Author

Level 1

50 points

Sep 18, 2026 5:53 AM in response to fábio161

Thanks for sharing this! It's really helpful to know that even an M5 MacBook has the same issue while an M4 Mac mini works. That confirms it's a macOS 27 problem, not a hardware one.

What command are you planning to run? I can run it too and share the output — maybe together we can figure out what's going on.

Reply

Answer 14

CITY34DR Author

Level 1

50 points

Sep 19, 2026 1:24 PM in response to Souravjha

Thanks for the methodology — I ran the command on macOS 27 with the mouse turned off, then turned it on. Here's what I got:

text

Timestamp                       Thread     Type        Activity             PID    TTL  
2026-09-19 23:14:59.063050+0300 0x2dd37    Default     0x0                  10592  0    ioupsd: (IOHIDLib) [com.apple.iohid:ups] properties: {
    "Accessory Category" = Mouse;
    "Accessory Identifier" = "D0:81:7A:08:4F:E4";
    Name = "Magic Mouse City34DR.";
    "Product ID" = 617;
    "Transport Type" = Bluetooth;
    "Vendor ID" = 76;

That's all I get. No continuous stream, no movement events. Just this one initial event from ioupsd.

Right now I can only test on my MacBook Neo (macOS 27) — I don't have access to my Mac mini (macOS 26) at the moment. As soon as I can, I'll run the same command there and compare.

Could you share the differences you found in the other thread? That might help me understand what exactly to look for when I compare the two logs.

Reply

Answer 15

fábio161

Level 1

128 points

Sep 19, 2026 2:18 PM in response to CITY34DR

Thank you for your time.

But I think that further investigation is uneeded at this point, at least for a solving purpose.

The 2 apps quoted above already solve the situation (I tested the xander-ag).

It is just install and be happy.

The community with some probably poorly paided devs solved before a trillionarie company. Nothing new…

Reply