Windows 10 about libwdi HOT 6 CLOSED

libwdi/Zadig simply repackages drivers. So the makers of these drivers (Microsoft for WinUSB, or the libusb-win32 people for the other ones) comply with the Windows 10 signing requirements, then it's a non issue - once these compatible drivers are published, I'll just rebuild Zadig by pointing to those drivers.

Also, in the case of WinUSB, it's likely that it's a non-issue, since Windows 10 already comes with WinUSB, and Zadig (or rather the Windows driver installation subsystem) will not replace that driver.

This being said, because my time is very limited, and libwdi/Zadig are one of my lowest priority right now, I haven't tested, and it's unlikely I will do so for some time (months?... or more?).

So if you have a question that can easily be answered by testing, I would strongly encourage you to do so and report your findings and any issue you may find, rather than expect somebody else to do that work for you... ;)

from libwdi.

Thank you for responding, but I am a bit confused by the answer. The readme of libwdi states:

• Automated catalog file creation and signing, using autogenerated certificate

So my understanding so far was, that libwdi actually creates the signatures on the fly by generating a cat file from the driver dll and inf files?

My understanding from the msdn link above is, that basically the signing files would have to be registered with microsoft starting in about 60 days. That would render on-the-fly signing invalid? Or am I missing something?

from libwdi.

Driver cat is not resign for sure
Maybe the installer is for some sort of editor and avoid annoying warning when install "windows cannot check. ...install anyway"
Do you known about libusbk drivers availability or plan for win 10th?

from libwdi.

Zadig and libusb work fine under windows 10 right now, i tested it. The concern was about what happens after 90 days have passed.

However, maybe this is not an issue for non-kernelmode drivers.

from libwdi.

So my understanding so far was, that libwdi actually creates the signatures on the fly by generating a cat file from the driver dll and inf files?

libwdi does NOT sign the drivers. It only signs the driver package (.cat). Those are completely different things, and the latter has not changed in Windows 10 AFAIK.

And yes, signing the driver package is to avoid unwanted warnings during driver installation. Please see the FAQ for more info.

For info about libusbK driver, please post on the libusb-win32 mailing list. I am not involved in libusbK development so I don't know what the plans are.

from libwdi.

I will close this issue as I have answered the questions I could answer.

from libwdi.