Closed herrameise closed 7 years ago
just verified that the previous release (1.0.0.7) has no issues installing on Windows 10
I am pretty sure the driver is signed. It is standard Code Signing certificate however.
I am working on HLK submission which should solve the problem.
I also had this issue, is there any update?
Please report how USBPcap 1.2.0.2 behaves on your computer.
Sorry, I get the same;
Do you have Secure boot enabled? Did the USB devices work after restart?
The solution to this is attestation signing, but unfortunately I cannot do this alone, it needs to go through the company and there is paperwork burden. And the driver is signed (check file properties - it even chains us to Microsoft Code Verification Root), but Windows 10 with Secure Boot falsely claims that it is not signed... It would be better if it said, that it is signed but by individual developer, who is unable to obtain EV certificate on his own. This normal kernel-mode code signing certificate is ok for all other Windows versions...
Please let me know if 1.2.0.3 works for you. On WIndows 10 it should install driver that is signed by "Microsoft Windows Hardware Compatibility Publisher" certificate issued by "Microsoft Windows Third Party Component CA 2014".
I was able to successfully install it and my USB devices are still working.
The installer may be signed, but it looks like the actual driver is not. After installing USBPcap 1.2.0.1, Windows 10 displays a message that it has blocked the installation of an unsigned driver. On reboot, all of my USB devices no longer worked until I uninstalled the USBPcap program. This was not an issue with the older version of USBPcap that used to ship with Wireshark. However, the new Wireshark release (2.4.0) is bundled with USBPCap 1.2.0.1.