From: DocKell on 7 Sep 2010 14:47 I have a driver that consists of a single .inf, .cat, and .sys files. I signed the .sys, ran inf2cat, and then signed the .cat file. Signtool verify /kp gives the catalog file a clean bill of health, but I still get the red dialog with the "Can't verify the publisher of this driver" warning whenever I plug in the hardware and install the driver. Does anyone have any idea what could be going wrong? I don't require full WHQL certification to get rif of the warning dialog, do I?
From: Satya on 9 Sep 2010 14:00 I suspect you have not cross-signed your driver. Please check my blog post regarding that @ http://winprogger.com/?p=41 Satya http://www.winprogger.com "DocKell" wrote: > I have a driver that consists of a single .inf, .cat, and .sys files. I > signed the .sys, ran inf2cat, and then signed the .cat file. Signtool verify > /kp gives the catalog file a clean bill of health, but I still get the red > dialog with the "Can't verify the publisher of this driver" warning whenever > I plug in the hardware and install the driver. > > Does anyone have any idea what could be going wrong? I don't require full > WHQL certification to get rif of the warning dialog, do I? >
|
Pages: 1 Prev: Error 39 with Coinstaller Next: Syntax error with WinDBG command line -c ".cls;g" |