Why would Vista x64 give me code 39 for my signed drivers?

NTDEV
1

Why would Vista x64 give me code 39 for my signed drivers?

I have a KMDF USB modem driver. We are going through the process of testing it with DTM now.

So, to load it on Vista x64, I signed it with our organization’s Verisign certificate, following the instructions in the KMCS doc:

  1. Inf2cat (the output says it grabbed the .inf, .sys, and the WDF coinstaller .dll)

  2. Signtool sign the catalog file (no errors)

  3. Signtool verify (says it is signed with class 3 code signing etc.)

So, I take it into our lab and try to load it. Eventually it fails out with code 39. The security log in evntviewer.exe says that the hash of my .sys file is not correct or is missing.

I also tried signing the .sys file itself (before or after creating and signing the catalog file), but it didn’t make any difference.

If I do modem properties and click the “Driver” tab, it shows modem.sys as signed, but then mydriver.sys as unsigned, and the WDF coinstaller as unsigned as well.

If I actually look at the exact files it’s using in Windows Explorer, the “digital signatures” tab shows that both the .sys and .dll are signed.

This is using inf2cat from the Winqual submission tool, and the 5744 WDK otherwise.

Any ideas?

2

Sorry, apparently I needed to enable test signing (even though I had a “real” cert).

3

I have a similar problem – unless there’s something crippled in Vista RC2, we shouldn’t have to enable test signing, should we?

My file system driver is signed with the MS cross certificate. The signature appears fine in the file properties. But I have to enable test signing for Vista RC2 x64 to load it properly. I’m using WDK.5744.

In my case “SelfSign.exe verify” fails on my driver with the following: “A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.”

Any suggestions would be appreciated.

4

A quick update: My “SelfSign verify” error is now resolved having found Microsoft’s KMCS_Walkthrough document and having and followed it carefully – must put Verisign code-signing cert in the Personal cert store!

But the cross-certificate is still not chaining properly in the root certificate hierarchy, so it still loads only in TESTSIGNING mode.

5

I have a the problem in vista 64, why?

6

later, i change a new xp os ,it is ok!
i don’t know the realy thing…