Magic Mouse 2 is not working in the macOS 27?

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 

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.

Same problem here. I did try everything that is mentioned here and that was suggested by all four leading AIs: ChatGPT, Grok, Claude, Gemini, and nothing worked. The mouse connects and is active but does not click or move after updating to macOS 27 Golden Gate. Then I tested the mouse on my iPad that I have also updated to iPadOS 27, and the problem was the same, connects and active but does not move the cursor or click. I even started thinking that there was a hardware problem with the mouse, because my Magic Keyboard works just fine after the update on both devices. Funny thing is that when I decided to try the mouse again on my older iPad with iPadOS 26 installed still, and Magic Mouse started working!!! So it seems like there is a software issue with the MacOS 27 and iPadOS 27, that makes the mouse not work, will need to wait for the bug to be patched in future updates.

Hardware: Mac mini (2024, M4), 16 GB

OS: macOS 27.0 (26A428)

Device: Magic Mouse 2, firmware 1.9.2, VID 0x004C, PID 0x0269

SUMMARY

After updating to macOS 27.0 the Magic Mouse 2 pairs and shows as

Connected with a battery level, but sends no input at all. The Mouse

pane in System Settings is empty. A Magic Keyboard on the same Mac over

the same Bluetooth stack works normally, as does a non-Apple Bluetooth

mouse. The same Magic Mouse works correctly on another Mac running

macOS 26.

STEPS TO REPRODUCE

1. Update a Mac to macOS 27.0.

2. Pair a Magic Mouse 2 (firmware 1.9.2).

3. Move the mouse.

EXPECTED

Pointer moves, clicks and gestures work, Mouse pane shows settings.

ACTUAL

No pointer movement, no clicks, no gestures. Mouse pane empty.

DIAGNOSIS

The mouse never becomes an HID device:

ioreg -c IOHIDDevice -> no Magic Mouse entry

ioreg -c IOBluetoothHIDDriver -> no instance

ioreg -c AppleMultitouchDevice -> no instance

bluetoothd flags the device on every connection:

DvF 0x40000024000 < ClassicPaired HIDBadBehavior Connectable >

CnS 0x800020 < HID ACL >, SupS 0x20 < HID >, Battery M -65%

Magic Keyboard on the same host, working:

DvF 0x40000114000 < ClassicPaired HIDGoodBehavior ConnectedOverUSB Connectable >

Telemetry in the same log: ConnectedClassicHIDDevice : 0

The reported battery level is negative (-65%) while ControlCenter, in

the same log, reports the same device correctly as batteryLevel: 0.65.

Another user reports -63% at 63% charge with identical symptoms

(discussions.apple.com/thread/256357286).

This suggests a sign error when parsing the Magic Mouse battery field,

causing the device to be classified HIDBadBehavior, which prevents the

HID profile from attaching.

ALREADY RULED OUT

Re-pairing, pairing by cable, pairing from a cleared device list,

Bluetooth reset, multiple reboots, Safe Mode, resetting

com.apple.AppleMultitouchMouse and

com.apple.driver.AppleBluetoothMultitouch.mouse preference domains.

None survive a reconnect, because the flag is recomputed each time.