signed driver disconnect

By dmurphey ·
I am developing a Windows XP USB driver. I have followed the example in the WinDDK 6000 ?selfsign_example.cmd?. Using a test certificate, my driver was signed without a problem (as viewed in DeviceManager). Next I purchased a Verisign Class 3 Code Signing certificate. The selfsign_example.cmd script executes properly, signs the driver and catalog file with an authentic certificate and installs the certificate. My driver executes without a problem. However when I view the driver via DeviceManager, it shows as unsigned.

The following error appear in setupapi.log:
@ 10:21:42.031 #E358 An unsigned or incorrectly signed file "c:\windows\inf\oem3.inf" for driver "XylocUSB - WinME/98/2000" blocked (server install). Error 1168: Element not found.
@ 10:21:42.046 #T206 Install Device: Verifying catalogs/INFs completed.
@ 10:21:42.093 #T224 Install Device: Cleaning up failed device.
@ 10:21:42.125 #E122 Device install failed. Error 1168: Element not found.
@ 10:21:42.156 #T201 Install Device: End.
@ 10:21:42.171 #E157 Default installer failed. Error 1168: Element not found.

VeriSign claims that the certificate is valid and the fault lies with the OS. Please advise ...


This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
Thread display: Collapse - | Expand +

All Answers

Back to Networks Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums