-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release of libusbk will come with signed 3.0.7.0 version of libusbk.sys #26
Comments
On the other hand, if a business have a need to go for WHQL with their own build of libusbk.sys, it is of course still possible as long as they have a valid EV certificate acceptable by Microsoft. |
For end users, there is no worry as libusbk.sys 3.0.7.0 still works wonderfully. libusbk-inf-wizard will help you to install the driver package under Windows 10 without an issue. |
With the support of isochronous transfer added for WinUSB in libusbk 3.1.0.0, there is less a need to use libusbk.sys in the future. |
Still a new signed release may improve the driver ranking issue mentioned by Pete here. |
BTW, libusb-win32 snapshot release 1.2.7.2 (or 1.2.7.3) has the necessary digital signature. |
liusbk 3.0.8.0 and 3.1.0.0 release come with signed libusbk.sys 3.0.7.0 version and it still works with Windows 7/8/8.1/10 (and should work under Windows XP/Vista as well but you should really not using those ancient OS, now that even Windows 7 is out of support).
We do not have a EV certificate for code signing now so this is not possible to go for Microsoft attestation for new version of libusbk.sys. Luckily libusbk.sys still works very well.
The text was updated successfully, but these errors were encountered: