Hi Xiaofan,
We are currently using the latest version libusb-win32 1.2.6.0 binary (from https://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/).
During our trial to be compatible with HCVI mode in windows 10 version 1809 or later, i 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 i plug the driver libusb named rvgusb_64, we have a bluescreen with DRIVER_VERIFIED_DETECTED_VIOLATION. I enclosed you the dump in order you can check the adresse in memory which caused it.</driver.sys>
Can you please help us to solve this issue and to be complaint with windows 10 HCVI mode?
Thanks in advance for your help.
Karthiga.
Hi
This is fixed in git:
https://github.com/mcuee/libusb-win32/commit/9afd01fc136f1f91d94a194889886b9ebb47be1c
Thanks,
/pedro
I put the snaphot release here: https://sourceforge.net/projects/libusb-win32/files/libusb-win32-snapshots/20190918/
You will need to sign it afterwards, but guess you are already doing that.
Please report if this works or not.
Thank you so much for your prompt support and this new release.
Your welcome.
Make sure you post the result of your testing. Also, if it does not work please post your minidump, and not a screendump of it.
Thanks,
/pedro
I encounter some issue to sign with our certificat. Once i success to test this driver, i will let you know about the result.
Thanks again.
Hi Peter,
I finally successed to sign with EV certificate and the device works properly with verifier activated with code integrity checks and is recognized as complaint with windows 10 HCVI mode by the Device Guard and Credential Guard hardware readiness tool .
Thanks again for your great work and prompt release !
Karthiga.
Hi Karthiga,
No problem. Great to hear that it helped.
This also makes the driver more secure, as all memory is NX now.
Thanks,
/pedro
FIXED