We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Ref: libusb/libusb#622
The issue with libusb0.sys has been fixed in the libusb-win32 snapshot release (unsigned). Maybe libusbk.sys still has the issue.
During our trial to be compatible with HCVI mode in windows 10 version 1809 or later, we run the following command verifier.exe /flags 0x02000000 /driver <driver.sys> (https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/driver-compatibility-with-device-guard). When the device using the driver libusb0.sys is plugged, it causes a bluescreen with DRIVER_VERIFIED_DETECTED_VIOLATION. Also tested with LibusbK.sys and ended with same bluescreen with DRIVER_VERIFIED_DETECTED_VIOLATION. libusb-win32 developer community fixed it in the following release https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20190918/ and source code in git : mcuee/libusb-win32@9afd01f
During our trial to be compatible with HCVI mode in windows 10 version 1809 or later, we run the following command verifier.exe /flags 0x02000000 /driver <driver.sys> (https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/driver-compatibility-with-device-guard).
When the device using the driver libusb0.sys is plugged, it causes a bluescreen with DRIVER_VERIFIED_DETECTED_VIOLATION.
Also tested with LibusbK.sys and ended with same bluescreen with DRIVER_VERIFIED_DETECTED_VIOLATION.
libusb-win32 developer community fixed it in the following release https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20190918/ and source code in git : mcuee/libusb-win32@9afd01f
The text was updated successfully, but these errors were encountered:
BTW, libusb-win32 snapshot 1.2.7.2 release has the valid digital signature. Reference discussion: mcuee/libusb-win32#24
Sorry, something went wrong.
@TravisRo Please talk a look when you got time. Thanks.
No branches or pull requests
Ref: libusb/libusb#622
The issue with libusb0.sys has been fixed in the libusb-win32 snapshot release (unsigned). Maybe libusbk.sys still has the issue.
The text was updated successfully, but these errors were encountered: