Issue installing driver error 10

[Bmcaleese2023]

I originally found this https://github.com/maashrafh/MagicTrackpad2ForWindows which appears to be the same exact project as this. The only difference is that one has a side note at the bottom for updating the drivers manually in device manager since just clicking install doesnt fix the trackpad for usb-c. However when I try to do that I get the windows error 10 that says this

Any idea on how to fix this issue?

[vitoplantamura]

hi, try installing the self-signed driver: #13 (comment) Vito

[tubeldelta]

Hi @vitoplantamura

I have the same issue on an ARM Surface Laptop 7. After the error occurs, the device shows with an exclamation mark in Device Manager, and gestures don't work.

Your self-signed driver can't easily be installed, either, as I get an error that the certificate chain could not be validated (even after installing the cert in local machine / trusted root certification authorities). I was able to install it by disabling driver signing completely via advanced startup options, but the result is the same as above - error 10, exclamation mark and no working gestures.

I'm pretty sure I've tried all possible orders / combinations, while making sure that the drivers is cleaned up in between attempts via forced uninstall.

I also have an AMD64 based machine, where everything worked perfectly on the first try, so I'm pretty sure the ARM drivers just don't work.

Can I help you in any way to debug this and get it working?

[vitoplantamura]

hi,

can you try to open c:\windows\INF\setupapi.dev.log with Notepad and to search for "AmtPtpDevice"? There should be one or more sections about your installation attempts. Can you post them here?

Vito

[tubeldelta]

Here you go, I hope this helps: setupapi.dev.log

I'm not 100% sure what stage this is, but I think it was my last installation attempt before giving up. If you need more info or a clean attempt from the start, please let me know.

[vitoplantamura]

unfortunately the log you attached refers to a successful attempt, probably the installation of the original imbushuo driver. I am interested in seeing everything that is logged when trying to install my self-signed driver.

Could you clean everything with DriverStoreExplorer and try to install the self-signed driver again? Please consider that the most recent events are at the end of setupapi.dev.log.

Also, as a further test I would ask you to import the certificate also in the Trusted Publishers, in addition to the Trusted Root Certification Authorities (where it should already be present).

Thank you, Vito

[tubeldelta]

Hi @vitoplantamura

Thanks, I've now done the following:

1. uninstall Magic Utilities (which I've been using in the meantime)
2. verify with DriverStoreExplorer that no drivers from Magic Utilities or imbushuo / Apple are left
3. install the certificate under Local Machine / Trusted Publishers -> this still caused an error, but as I hadn't rebooted after disabling signed driver enforcement, I was able to install them anyway
4. find the needed device in Device Manager
5. install the driver -> this warning is shown
6. get error 10

The result is that the device is shown with a warning, and shows error 10. Gestures don't work, and the control panel from your source has no effect (and shows an error when trying to install your DLL, which as I understand is expected, as the self-signed driver installs itself directly).

I've attached the full setupapi.dev.log from this attempt here: setupapi.dev.log

[vitoplantamura]

Thank you for your detailed reporting.

I realize only now that we were referring to different procedures 😀 Thanks for your patience.

To install the self signed driver (in order to generate useful information in setupapi.dev.log) you need to follow these steps:

1. clean everything with DriverStoreExplorer.

2. download the zip file from here: 2024 USB-C version feedback #13 (comment)

3. install the certificate in the zip file in Trusted Root Certification Authorities and Trusted Publishers.

4. right click on the INF file in the zip file and click Install.

5. collect the text that is logged in setupapi.dev.log.

Thank you again for your patience,

Vito

[tubeldelta]

@vitoplantamura no worries, and thanks for your help, I appreciate it! 🙂

The steps you describe are exactly what I did in my previous post, and what the output log refers to. I saw now that I didn't describe well what I did in my third step. I first installed the certificate and then the driver, and still got an error.

[vitoplantamura]

ah ok! 😀

Googling for the error message in your setupapi.dev.log I found this issue:

VirtualDrivers/Virtual-Display-Driver#197

In this project, the installation procedure is the same as our self signed driver.

Unfortunately I think there is little we can do: they write: "Custom root certs no longer are checked in windows arm64".

I'll do some more research: if I find anything else relevant I'll let you know in this issue.

Thank you, Vito

[tubeldelta]

@vitoplantamura good find, thanks!

Do you think the "error 10" is related to the driver signing at all? I'm asking because I was able to install the unsigned driver by disabling enforced driver signing in advanced startup options, but that didn't solve this error.

[vitoplantamura]

good question: since DSE is disabled, the problem should be elsewhere. To verify this hypothesis, just see if the driver DLL is loaded: with DSE disabled, plug in the MT2 and with Resource Monitor look for AmtPtpDeviceUsbUm.dll. If the DLL is loaded, the problem is in the code. Link (second answer): https://superuser.com/questions/117902/find-out-which-process-is-locking-a-file-or-folder-in-windows Thank you, Vito

[tubeldelta]

Hi @vitoplantamura

Thanks, I've tried that now as follows:

1. uninstall Magic Utilities
2. install your self-signed driver with DSE off (warning is shown but installation can be completed)
3. change to the Bingxing Wang driver for device \VID_05AC&PID_0324&MI_01&Col02\7&1797f234&0&0001
4. check Resource Monitor
5. replug the MT2 just to be sure

It doesn't look like it's being loaded

---

Edit: I repeated the procedure with the regular driver (this one), and got the same result. As I mentioned before, it's possible to install it and select it for the MT2, but it just doesn't work on my ARM machine.

---

Edit 2: what may be even more interesting is that the imbushuo driver actually did work for the Lightning-port MT2 via Bluetooth on this machine, which I was able to test briefly before I got the USB-C version myself.

---

Edit 3: I connected the Lightning port version again, and it worked immediately out of the box.

Some screenshots:

• both devices connected
• AmtPtpDeviceUsbUm DLL being used
• details of both devices

What's interesting is that even after setting the correct drivers, the Lightning-port one is identified as a USB device (path USB\VID_05AC&PID_0265&MI_01\5&2DC9172F&0&0001), but the USB-C one still shows as a HID device (path HID\VID_05AC&PID_0324&MI_01&COL02\7&1797F234&0&0001).

---

Edit 4: I got it working, and it was a very simple mistake. I had changed the driver in Device Manager before installing your control panel driver, that's what causes the error. Sorry for taking your time with this, and thanks a lot for your help!

[vitoplantamura]

It was not a waste of time, as we discovered the limits of self-signing on Windows on ARM.

A question: so on your ARM Surface Laptop 7 with a USB-C Magic Trackpad, my Control Panel now works? Can you for example change the haptic feedback options?

Thank you, Vito

[tubeldelta]

Glad to hear there was some insight to be gained :)

Yes, I can make changes on the ARM Laptop with the USB C Trackpad, and they are applied (I disabled the "ignore input from the finger used to click the force touch button" option, for example).

Let me know if I can assist you with anything else!

[konradzuse]

i'm also having issues with a Surface Pro 11. Are you talking here about USB or Bluetooth? I'm able to get it working on USB, but Bluetooth HID device gives me a code 10.

my bluetooth device hardware id is:

BTHENUM{00001124-0000-1000-8000-00805f9b34fb}_VID&0001004c_PID&0324