What are the symptoms?
The cursor keeps working and clicks keep working; only scrolling stops. The pattern users report is consistent:
- Cursor and buttons fine — the mouse is clearly still connected and still moving.
- Two-finger scroll completely dead — not slow, not jumpy, just nothing.
- Starts after the mouse sits idle — typically around 15 to 30 minutes, followed by a Bluetooth disconnect and reconnect.
- No self-recovery — waking the mouse, sleeping the PC, or toggling Bluetooth does not bring scroll back.
- Previously fixed only by re-pairing or reinstalling the driver, and then it came back.
Why does Magic Mouse scroll stop working on Windows 11?
Because Windows rebuilds the device with the wrong shape. After a Bluetooth idle disconnect, DeviceSetupManager (DSM) runs property synchronization against the cached device state, and the HID collections the mouse exposes get collapsed — the project calls this Mode A → Mode B. Mode A exposes the separate collections that carry the touch-surface data; Mode B exposes a plain mouse. A plain mouse has a cursor and buttons and no scroll surface, which is exactly the symptom.
This is not a battery problem, not a Bluetooth range problem, and not a Windows setting you can toggle. Nothing in the Windows mouse settings can re-expose a collection that is no longer there.
Common bad advice: “just install the Apple driver.” Apple’s Boot Camp INF contains no 0323 entry, so for the 2024 Magic Mouse there is no Apple driver to install. That advice is correct for a v1 or v2 Magic Mouse and wrong for this one.
Full write-up in the repo: bug analysis of the DSM and BTHPORT path and the Mode A / Mode B HID collection diagram.
Try this first
Rule out the cheap causes before you install a kernel driver.
- Re-pair the mouse. Remove the device in Bluetooth settings, then pair it again. If scroll comes back and then dies again after the next idle period, you have this bug.
- Confirm the PID. Device Manager → Human Interface Devices → Apple Magic Mouse → Properties → Details → Hardware Ids. Look for
PID_0323. - Confirm it is not a v1 or v2 mouse.
PID_030Dis the 2009 AA-battery Magic Mouse,PID_0269is Magic Mouse 2 with the Lightning port. Those are covered by Apple’s Boot Camp INF and are out of scope here. - Check you are not looking at a trackpad. Magic Trackpads report
030E,0265, or0324; this driver does not target them. - Then install the driver. Follow how to install the Magic Mouse 2024 (v3) Windows driver. The KMDF filter keeps the HID collections intact across a Bluetooth reconnect, so scroll survives the idle cycle that used to break it.
Which mouse do I have, and what should I install?
| Your mouse | Bluetooth PID | What to install |
|---|---|---|
| Magic Mouse 2024, USB-C (this project calls it v3) | 0x0323 |
This KMDF driver — install guide |
| Magic Mouse 2, Lightning (v2) | 0x0269 |
Apple’s Boot Camp INF, or sbagirici’s scroll fix / tealtadpole’s Win11 x64 package |
| Magic Mouse, AA batteries, 2009 (v1) | 0x030D |
Apple’s Boot Camp INF, or sbagirici / tealtadpole |
| Apple Wireless Mouse | 0x0310 |
Treat it like v1: Boot Camp INF or the community v1 fixes |
| Magic Trackpad | 030E, 0265, 0324 |
Not covered by this driver |
Unsure after all that? The Magic Tray site keeps a decision page: which Apple mouse driver do I need on Windows.
Will this fix the battery percentage too?
No. The driver restores scroll; it does not read battery. The free Magic Tray (Windows app) is what shows battery percentage next to the Windows clock, and a healthy HID collection stack is what keeps that read reliable. Details: Magic Mouse battery percentage on Windows 11. Magic Tray is Windows software — a system-tray utility — not a desk accessory, stand, or 3D-printed tray.
Still stuck?
- Magic Mouse v3 Windows driver FAQ — Boot Camp, Test Mode, Windows 10, USB-C cable.
- Driver source and issues on GitHub — MIT licensed, free.