Magic Mouse v3 Windows driver FAQ

No. Apple never shipped a Windows driver for the 2024 Magic Mouse, and its Bluetooth PID 0323 does not appear in Apple’s Boot Camp INF, so Windows never binds Apple’s driver to it. Boot Camp is not a working answer on the older models either: Apple’s installer refuses to run on non-Apple hardware, and even with applewirelessmouse.sys present on disk, Windows will not attach it until something registers it as a lower filter on the device. That registration is what the Apple-driver route here does.

Install the Apple-driver route (v1-binary-patch/) unless you want to build a kernel driver yourself. It registers Apple’s own unmodified signed driver, needs no Windows Test Mode, and supports 0x030D, 0x0269, 0x0310 and 0x0323. The separate KMDF route (v2-kmdf-driver/) ships as 2.0.4.6 C source with its INF and build/sign scripts, which the project has not built or signed: you compile it with the WDK and sign it with a certificate you generate, so it does require Test Mode. Never install the two together.

Check the Hardware Ids: Device Manager → Human Interface Devices → Apple Magic Mouse → Properties → Details → Hardware Ids. PID_0323 is the 2024 model, v3, and its charge port is USB-C. PID_030D is v1, PID_0269 is Magic Mouse 2 with a Lightning port, and PID_0310 is the v2-alt identifier. All four are supported by the Apple-driver route; the KMDF route covers 0x0323 only.

Yes, through the Apple-driver route. Its installer in v1-binary-patch/ supports v1 0x030D, v2 0x0269, v2-alt 0x0310 and v3 0x0323, and it was verified on a real paired v1 sitting alongside a v3 on the same PC. It is the approach sbagirici proved on v1 and v2. The PID lookup table spells out which route you need.

It depends on the route. The Apple-driver route ships Apple’s own signed binary unmodified and installs no catalog, so it needs no Test Mode — although confirmation on a machine with test signing switched off remains tracked as issue 20. The KMDF route does need Test Mode, with Secure Boot and memory integrity off, because you sign that driver with a certificate you generate yourself. Do not enable Test Mode casually, and never on a machine you do not control.

Yes, on Windows 10 build 14393 or later, x64 only. Windows 11 is supported on any build. There is no 32-bit or Arm package.

After a Bluetooth idle disconnect, DeviceSetupManager property synchronization can collapse the mouse’s HID collections, Mode A to Mode B. The cursor keeps working and scroll dies, and it does not recover on its own. Full explanation: Magic Mouse 2024 (v3) scroll not working on Windows 11.

The USB-C port on the underside is for charging. The mouse connects for input over Bluetooth, and the shipped Apple-driver route targets that Bluetooth HID path, so plugging in the cable is not a workaround for dead scroll.

The Apple-driver route does not read battery itself — the free Magic Tray (Windows app) does. It briefly removes applewirelessmouse from the mouse’s LowerFilters to expose the COL02 collection, reads HID input report 0x90 there, then restores the filter, so two-finger scroll is unavailable for a few seconds. The KMDF driver reads report 0x90 on COL02 directly, with no filter change. Battery on Magic Mouse v1 0x030D, v2 0x0269 and v2-alt 0x0310 is not yet characterised.

It is free and MIT licensed, with no subscription, and it is maintained by Revive Business Solutions / Lesley Murfin. Magic Utilities is separate paid software sold on subscription. This project targets the Magic Mouse scroll bug on Windows, and the battery percentage side is handled by the free Magic Tray (Windows app).

For the Apple-driver route, run installer\Uninstall-MagicMousePatch.ps1 as administrator: it removes applewirelessmouse from LowerFilters, deletes the service key, restores the backed-up driver, and prompts for a reboot. If you built and installed the KMDF route yourself, run v2-kmdf-driver\Uninstall-KMDF.cmd, which removes the published MagicMouseDriver-kmdf-204-scroll.inf package.

On GitHub at github.com/LesleyMurfin/magic-mouse-v3-windows-fix, MIT licensed. The ready-made Apple-driver route is in v1-binary-patch; the KMDF route is in v2-kmdf-driver, which holds the complete C source, INF and build/sign scripts at 2.0.4.6, not built or signed. Download the repository itself to get either one — there are no separate release downloads.