The Magic Mouse 2024 (USB-C) won't scroll on Windows 10 or 11
The battery percent on this mouse already works on Windows 10 and 11, with no driver at all. Finger scrolling doesn't, because Apple's Windows software has no entry for the model.
A driver is the software Windows uses to talk to your mouse. One route works today, and it costs you the battery percent.
Questions
- Does the Magic Mouse 2024 (USB-C) work on Windows 11?
- Mostly. It pairs over Bluetooth, clicks and moves the pointer, and Magic Tray shows its battery percent with no driver at all. Finger scrolling is the one missing piece: it needs the community KMDF driver, which isn't published yet. When it ships, Magic Tray installs it only after you confirm.
- Why doesn't Apple's Windows software fix the 2024 Magic Mouse?
- Windows gives every mouse model a four-character device code, and the 2024 USB-C Magic Mouse reports
0323. Apple's own Windows software lists the older Magic Mouse codes and never listed0323. Windows finds no match, so it never loads a scroll driver for this mouse. - What does the community driver for the 2024 Magic Mouse do?
- The community driver for the 2024 USB-C Magic Mouse is meant to sit between the mouse and Windows, watch your fingers move across the top surface, and turn that movement into ordinary scrolling. You can't get it yet. Its own files still say work in progress, and no installer is published.
- Which routes give the 2024 Magic Mouse scrolling on Windows?
- Two routes were designed for the 2024 USB-C Magic Mouse, and only one exists today. The community driver would give scrolling and battery percent together, but it isn't published. The patched Apple driver is real today, and on that route you get scrolling or battery percent, never both.
- Does the 2024 Magic Mouse battery percent need a driver?
- No. The battery percent on the 2024 USB-C Magic Mouse works with no driver at all, on Windows 10 and Windows 11. Only finger scrolling needs one. The scroll-or-battery trade-off belongs to the patched Apple driver route, and to nothing else on this mouse.
When the community driver ships
Microsoft won't have checked it. Windows will refuse to load it until you change a Windows startup setting yourself, and that lowers one of its security protections.
A check by Microsoft costs money. Here's how you can help.
The two routes side by side
| Route | You get | The catch |
|---|---|---|
| Community driver | Scrolling and battery percent | Not published yet. There is nothing to download. |
| Patched Apple driver | Scrolling, or battery percent, never both on this route | You change the Windows startup setting and turn Memory integrity off first. Nobody has confirmed it. |
Magic Tray offers the patched Apple driver from its tray menu. It asks first, and it installs only when you say yes. It can't change that Windows startup setting for you.
Show the technical details
Two rooms in one mouse
The mouse describes itself as two HID collections: COL01 movement and finger position, COL02 battery.
When the Bluetooth link goes idle, Windows can cache the two collections merged. The pointer survives, the finger data doesn't.
The filter driver
The fix is a KMDF LowerFilter beneath the Windows HID stack. It converts finger movement into wheel events.
Apple's applewirelessmouse.sys uses that same LowerFilter slot for 030D and 0269. The community driver claims it for 0323.
Where the battery percent lives
Battery arrives in byte 2 of input report 0x90 on COL02, not in feature report 0x47.
Credit
The LowerFilter stack diagram is sbagirici's work, and it covers the older mice. Please star it.