Ref: https://github.com/libusb/libusb/issues/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 : https://github.com/mcuee/libusb-win32/commit/9afd01fc136f1f91d94a194889886b9ebb47be1c
Activity
mcuee commentedon Oct 25, 2021
BTW, libusb-win32 snapshot 1.2.7.2 release has the valid digital signature.
Reference discussion:
mcuee/libusb-win32#24
mcuee commentedon Oct 27, 2021
@TravisRo Please talk a look when you got time. Thanks.