Magic Mouse v3 · PID 0323 · Windows 10/11
Magic Mouse 2024 (v3) Windows driver — scroll fix for PID 0323
Apple ships no Windows driver for the 2024 USB-C Magic Mouse, Bluetooth PID 0323. This free, MIT-licensed driver brings two-finger scroll back on Windows 10 and Windows 11. The Apple-driver route registers Apple’s own signed driver, so that route needs no Test Mode, and it covers Magic Mouse v1, v2, v2-alt and v3.
Full spec table
| Device | Apple Magic Mouse, third generation — this project calls it Magic Mouse v3 |
|---|---|
| Marketing name | Magic Mouse (Apple sells it without a version number) |
| Model year | 2024 |
| Connector | USB-C |
| Bluetooth VID / PID | 05AC / 0x0323 |
| OS support | Windows 10 build 14393 or later, Windows 11 any build, x64 |
| What breaks | Two-finger scroll dies after a Bluetooth idle disconnect; the cursor keeps working |
| What this fixes | Restores and keeps two-finger scroll working — no reinstall, no re-pairing |
| Two routes | The Apple-driver route (v1-binary-patch/, v1.0.0) is the ready-made package, and it covers 0x030D, 0x0269, 0x0310, 0x0323. The separate KMDF route (v2-kmdf-driver/) ships as 2.0.4.6 source with its INF and build/sign scripts: you build it with the WDK and self-sign it, and it covers 0x0323 only. Never install both |
| License | MIT |
| Price | Free, no subscription MIT |
| Signing status | The Apple-driver route uses Apple’s own signed binary unmodified, so no Windows Test Mode is required for it. The KMDF route is signed with a certificate you generate yourself, so it does require Test Mode with Secure Boot and memory integrity off; the project’s own 2.0.4.6 source is not built or signed, and 2.0.4.3 was the last signed binary |
Which Magic Mouse do I have?
Device Manager → Human Interface Devices → Apple Magic Mouse → Properties → Details → Hardware Ids, then read the PID_ value. All four are supported.
Install it in three steps
-
1
Turn off Fast Startup
From an elevated prompt:
powercfg /h off, then reboot. -
2
Download the project, then run the installer
Download the project repository from GitHub, then double-click
v1-binary-patch/Install.cmd. It asks for Administrator itself. -
3
Reboot
Two-finger scroll comes back.
Those steps are the Apple-driver route, the ready-made package, and it needs no Test Mode. The separate KMDF route for the 2024 mouse ships as source at 2.0.4.6 that the project has not built or signed: you compile it with the WDK and sign it with your own certificate, so it requires Test Mode. Do not enable Test Mode or install a self-signed kernel driver casually, and never run both routes at once.
Full sequence and rollback: install the Apple-driver route.
What the installer changes, and what it does not require
The installer copies Apple’s unmodified applewirelessmouse.sys to System32\drivers, creates an applewirelessmouse kernel service, adds that driver to the Bluetooth HID device’s LowerFilters, then restarts the device so Windows re-enumerates it with the filter attached. It uses the bundled unmodified Apple driver, needs no PowerShell window or execution-policy change, and installs no catalog — so no Windows Test Mode is required for this route and Secure Boot and memory integrity can stay on. Scroll feel is Apple’s own Mac-style translation, sensitivity fixed.
The KMDF driver is a separate design for PID 0x0323 only, with tunable scroll, automatic recovery and a direct battery read. It ships as source: v2-kmdf-driver/ holds the complete C source, MagicMouseDriver-kmdf-204-scroll.inf and the build/sign scripts at 2.0.4.6, which the project has not built or signed — 2.0.4.3 was the last signed binary. You build it with the WDK or Enterprise WDK and Setup-Community.cmd signs it with a certificate it generates locally, so that route does require Test Mode. Signing is the one thing money would buy for it: an EV certificate plus Microsoft attestation signing would be needed before a package could load without Test Mode.
Why scroll stops
A Bluetooth idle disconnect makes Windows collapse the mouse’s two HID collections into one unified top-level collection, so the separate battery and diagnostic collection COL02 disappears and the scroll consumer on COL01 can no longer bind. Clicks and cursor movement keep working, so the mouse looks healthy. It does not recover on its own. Symptom walkthrough: Magic Mouse scroll not working on Windows 11.
Mode A to Mode B, and why DSM does not self-recover
DeviceSetupManager (DSM) runs a property synchronisation pass on reconnect, and the device can come back in this reduced form. Before this driver, the only ways back were a driver reinstall or re-pairing the mouse.
Battery percentage
The driver does not read battery. The Magic Tray app does, from HID input report 0x90 on COL02. It briefly removes applewirelessmouse from the mouse’s LowerFilters to expose that collection, reads the percentage, then restores the filter — two-finger scroll is unavailable for the few seconds that takes. Steps, and what is still unknown for v1 and v2: Magic Mouse battery percentage on Windows 11.
More
Why Boot Camp does not fix it either
Apple’s Boot Camp package has no entry for PID 0323, so Windows falls back to its generic HID mouse stack. Boot Camp does not rescue the older mice either: Apple’s installer refuses to run on non-Apple hardware, and even when applewirelessmouse.sys is present on disk, Windows will not attach it to the mouse until something registers the driver as a lower filter on the device. That registration is exactly what this project’s installer does — the approach sbagirici proved on Magic Mouse v1 and v2.
Research and source documents
Magic Tray is Windows tray software, not a wooden or 3D-printed desk tray.