# MagicTrackpad2ForWindows: a Microsoft signed driver for Apple's Magic Trackpad 2 > MagicTrackpad2ForWindows is a Windows 11 Precision Touchpad driver for the Magic Trackpad 2, forked from imbushuo's project and properly signed with an EV certificate so that Bluetooth works without the DriverStore hack the previous version relied on, at the cost of the author paying 485 euros he could not reclaim. **vitoplantamura/MagicTrackpad2ForWindows** — Magic Trackpad 2 Precision Touchpad driver for Windows 11, based on the imbushuo driver, signed by Microsoft - Repository: https://github.com/vitoplantamura/MagicTrackpad2ForWindows - Stars: 857 · Forks: 68 - Language: C - License: GPL-2.0 - Published: 2026-10-20 · Updated: 2026-10-20 · Language: en - Canonical page: https://hysenlabs.com/projects/vitoplantamura-magictrackpad2forwindows ## The signing problem this project exists to solve Windows will not load an unsigned driver, and that single fact is the background to this entire repository. The project is a fork of the imbushuo mac-precision-touchpad driver for the Magic Trackpad 2, and it supports Bluetooth, which is the point of the fork. The previous version of this project, in the author's words, used a hack to install itself in the DriverStore and couldn't support Bluetooth. People resorted, in the author's view, to the wildest hacks to get the MT2 to work over Bluetooth, and the repository issues give a glimpse of that. The resolution was signing. At the beginning of this year the author decided to purchase an EV certificate to properly sign the driver, paying 485 euros including taxes that he has no way of recovering as an individual, and noting that only organizations can request an EV certificate. His conclusion is stated without hedging: Windows drivers signing requirements and costs are unfair to open-source developers. So the practical difference between this project and the fork it started from is not the feature list. It is that the package carries a signature that Microsoft accepts, and the installation is an ordinary right click on an INF file rather than a DriverStore manipulation exercise. ## What the fork adds over imbushuo and the 2021 Apple driver The README lists the differences explicitly, and compares against both imbushuo's driver and the official 2021 Apple driver. The additions are support for the USB-C Magic Trackpad 2, battery level reading, haptic feedback control, various options for controlling pointer precision, and a control panel, which the README illustrates with a screenshot of the control panel window. Battery reading and haptics are the two that change how the device is used day to day. A trackpad that reports its charge stops you from wondering whether it is about to die mid session, and haptic feedback is the click and scroll feedback that Mac users expect and that Windows precision touchpads generally do not provide. The pointer precision options matter for a different reason. The Magic Trackpad 2 is a high resolution device, and on Windows the system scaling settings produce a pointer speed that some people find unusable, so being able to adjust the pointer precision from the driver's own control panel rather than through a global system setting is a targeted fix rather than a compromise. The control panel is shipped as part of the project, which is the visible part of the driver's configuration surface. The repository layout shows three product directories, and the control panel is one of them. ## Installing on Windows 11 starts with removing what is already there The installation instructions are unusually careful about ordering, and the first step is destructive on purpose. Step zero is to uninstall any previous versions of this driver, imbushuo's driver or the official 2021 Apple driver. The author's preferred tool for that is DriverStore Explorer, and the alternative is the Windows Device Manager. The README adds a warning that it is especially important to uninstall Magic Utilities and Trackpad++ before continuing, which tells you the failure mode this driver is meant to remove: two drivers fighting over the same device. Step one is to download the zip file of the project from the Releases page of the repository and unzip it. There is no installer executable and no command line step in the documented flow. Step two is to select the architecture, AMD64 or ARM64, then right click the INF file and click Install. That is the whole installation. The signed package means Windows accepts it without test mode, without disabling signature enforcement, and without a certificate to import. The reason the previous version needed a hack is the same reason this one does not. DriverStore is where Windows keeps driver packages, and injecting into it required privileged operations that users were doing in unsafe ways. ## Windows 10 is a second class path, and ARM64 is missing The README has a short note about Windows 10, and it contains both the good news and the bad. Windows 10 AMD64 is supported through a self-signed driver package. That is a weaker guarantee than the EV signed package used for Windows 11, and it means the user has to accept the certificate on that machine, which is the sort of step that only makes sense when the alternative is no driver at all. Windows 10 ARM64 is not supported. No workaround is offered and no explanation is given, and the instruction for Windows 11 offers an ARM64 INF, so the gap is specific to the older release rather than to the architecture. The same architecture split applies on the install step itself, where you pick the AMD64 or ARM64 package. That is worth checking before you unzip anything, because choosing the wrong one gives a device that does not enumerate, and the README gives no troubleshooting section for that case. For a user on Windows 11 the archive is a signed package for the current supported release. For a Windows 10 user the same archive becomes a self-signed package that has to be trusted, and for a Windows 10 on ARM there is nothing here at all. ## An EV certificate, a Hardware Dashboard account and a signing partner The Credits section is where the real story of the project's sustainability sits, and it is unusual to see it spelled out. The haptic feedback control messages sent by the driver to the MT2 are based on reverse engineering work by dos1, referenced through an issue on the Linux Magic Trackpad 2 Driver project. That is the origin of the feature the author lists as an addition, and it was someone else's reverse engineering that made it possible. There is also a credit to a pull request on the imbushuo repository by 1Revenger1, which fixes the near field fingers problem, cleans up the code, and removes the QueryPerformanceCounter call in the interrupt function. That last detail is the kind of change that matters in a driver: a timing call in an interrupt handler is a source of latency and jitter, and removing it was inherited rather than invented here. The signing logistics are credited to Landlogic IT, who took care of the grueling process of gaining access to Microsoft's Hardware Dashboard and who take care of signing the driver packages. The certificate purchase itself was funded by a list of individual contributors, including the author, with the details in an issue in the repository. So the delivery chain is: a personal EV certificate paid for by contributors, a partner organisation with the Hardware Dashboard relationship doing the signing, and a driver package that Windows accepts. That is a fragile arrangement for any single maintainer, and it is the honest reason the author says signing costs are unfair to open-source developers. ## Three directories, one driver, and an active release line The repository is small and its top level shows the structure of a Windows Precision Touchpad driver. AmtPtpDeviceUsbUm/ is the device-side component, AmtPtpHidFilter/ is the HID filter, and AmtPtpControlPanel/ is the control panel application that ships with the driver. There is a build/ directory, an assets/ directory holding the images used in the README, and a .github/ directory. The primary language is C, which is what you would expect for a kernel mode filter driver and a user mode device driver, and the licence is GPL-2.0 with the LICENSE file at the repository root. GPL-2.0 on a driver is unusual enough to be worth noticing, and the terms are the ones in that file rather than anything the README paraphrases. Maintenance is current. The repository is not archived, the last push was on 2026-10-19, and the releases are v2.2 on 2026-10-12, v2.1 on 2026-09-30 and v2.0 on 2026-02-25. The v2.0 release in February lines up with the signing work described in the README, and the two patch releases since then suggest the signed package is being maintained rather than merely published once. There is no homepage, no issue tracker guidance in the README beyond the credits, and no documentation of the control panel settings, so an evaluation beyond the feature list means reading the source in those three directories. ## Conclusion MagicTrackpad2ForWindows suits a Magic Trackpad 2 owner on Windows 11 who wants Bluetooth, haptics and a control panel without touching the DriverStore, and it is the only signed path documented in this repository. It is the wrong choice for a Windows 10 ARM64 machine, which the README says is not supported, or for a Windows 10 AMD64 user who objects to the self-signed package, and it is irrelevant if you have no Apple trackpad. Before installing, remove the previous driver with DriverStore Explorer or Device Manager and uninstall Magic Utilities and Trackpad++, then pick the AMD64 or ARM64 INF from the release zip and install it with a right click. ## FAQ ### How do I install the Magic Trackpad 2 driver on Windows 11? First uninstall any previous driver, whether imbushuo's or the official 2021 Apple driver, using DriverStore Explorer or Windows Device Manager, and uninstall Magic Utilities and Trackpad++ as well. Then download the zip from the Releases page, unzip it, pick the AMD64 or ARM64 INF file, right click it and choose Install. ### Does MagicTrackpad2ForWindows support Bluetooth and the USB-C model? Yes. The README states that it supports Bluetooth, and lists support for the USB-C Magic Trackpad 2 among the additions over the imbushuo driver and the official 2021 Apple driver, together with battery level reading, haptic feedback control and a control panel. ### Is Windows 10 supported by MagicTrackpad2ForWindows? Partly. The README states that Windows 10 AMD64 is supported through a self-signed driver package, and that Windows 10 ARM64 is not supported at all. ## Sources - [Issues](https://github.com/vitoplantamura/MagicTrackpad2ForWindows/issues) - [License: GPL-2.0](https://github.com/vitoplantamura/MagicTrackpad2ForWindows/blob/master/LICENSE) - [README](https://github.com/vitoplantamura/MagicTrackpad2ForWindows/blob/master/README.md) - [Releases](https://github.com/vitoplantamura/MagicTrackpad2ForWindows/releases) - [vitoplantamura/MagicTrackpad2ForWindows on GitHub](https://github.com/vitoplantamura/MagicTrackpad2ForWindows) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/vitoplantamura-magictrackpad2forwindows