FAQ · Magic Mouse 2024 (v3) · PID 0323

Magic Mouse v3 Windows driver FAQ

Short answers about the Magic Mouse 2024 (v3) Windows driver: Apple never shipped a Windows driver for this mouse, PID 0323 is absent from Boot Camp, and scroll dies on Windows 11 when a Bluetooth idle disconnect collapses the HID collections. This Magic Mouse v3 Windows driver is free, MIT licensed, and self-signed, so Test Mode is required today.

Install guide Fix dead scroll

Is there an official Apple Windows driver for the 2024 Magic Mouse?

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. That is why this project exists: an independent, MIT-licensed Magic Mouse 2024 (v3) Windows driver.

Does Boot Camp work with the Magic Mouse 2024 (v3)?

No. The Boot Camp INF has no 0323 entry, so Windows never binds Apple’s driver to the 2024 Magic Mouse. Boot Camp does cover Magic Mouse v1 and v2, which is why the usual “install the Apple driver” advice fails only on this model.

Why does Magic Mouse scroll stop working on Windows 11?

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.

Is the Magic Mouse 2024 the same as Magic Mouse 2?

No. Magic Mouse 2 is the Lightning model, PID 0x0269. The 2024 Magic Mouse has USB-C and reports PID 0x0323, and it needs a different driver. Apple sells both as “Magic Mouse”, which is why this project uses the label v3.

How do I know if I have a Magic Mouse v3?

Check the Hardware Ids: Device Manager → Human Interface Devices → Apple Magic Mouse → Properties → Details → Hardware Ids. PID_0323 means v3, and the charge port is USB-C. PID_030D is v1 and PID_0269 is v2.

Is the driver signed, and why do I need Test Mode?

The driver is self-signed today, so Windows only loads it with test signing enabled and Secure Boot off. An EV certificate plus Microsoft attestation signing is the goal, funded off GitHub via Stripe — see the signing and funding page and what Test Mode actually means.

Is the Magic Mouse v3 Windows driver free?

Yes. It is free and MIT licensed, with no subscription. It is maintained by Revive Business Solutions / Lesley Murfin, and the whole source tree is on GitHub.

Is this the same as Magic Utilities?

No. Magic Utilities is separate paid software sold on subscription. This project is a free, MIT-licensed kernel driver aimed at the 2024 Magic Mouse scroll bug, and the battery percentage side is handled by the free Magic Tray (Windows app).

Does the driver fix the battery percentage on Windows?

No. This kernel driver does not read battery. The free Magic Tray (Windows app) reads HID Input report 0x90 on collection COL02 and shows the percentage next to the Windows clock. See Magic Mouse battery percentage on Windows 11.

Does it support Magic Mouse v1 or v2?

No. This driver targets PID 0x0323 only. Magic Mouse v1 (0x030D) and v2 (0x0269) are covered by Apple’s Boot Camp INF and by community fixes from sbagirici and tealtadpole. The PID lookup table spells out which one you need.

Does it work on Windows 10?

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.

Does the Magic Mouse work over the USB-C cable on Windows?

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

How do I uninstall the driver?

Find the published INF with pnputil /enum-drivers, remove it with pnputil /delete-driver, or uninstall the device in Device Manager and delete its driver software. Then turn Test Mode off and reboot. Step by step: uninstall or roll back.

Where is the source code?

On GitHub at github.com/LesleyMurfin/magic-mouse-v3-windows-fix, MIT licensed. The recommended package is v2-kmdf-driver; v1-binary-patch is earlier research, not the install path.

Where should I go next?