SignTool Error with Windows 10

We author a Windows application (using Microsoft Visual Studio 2008).  We sign the .exe (and other components) with SignTool.exe.  This works fine on a Windows 7 computer.  On a Windows 10 computer we get the message:

SignTool Error: ISignedCode::Sign returned error: 0x80880253
The signer's certificate is not valid for signing.

The batch file includes:
"C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\SignTool.exe" sign /f "C:\elevate\CodeSigning\[certificate name].pfx" /p "[certificate password]" /v /t http://timestamp.comodoca.com/authenticode "[application name]"

Thanks in advance for your help.
richardpetersAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Joe Winograd, EE Fellow 2017, MVE 2016, MVE 2015Connect With a Mentor DeveloperCommented:
I'm guessing that the problem is that the signtool.exe in your Visual Studio 2008 doesn't support code signing in W10. Install Visual Studio 2015 to get the latest signtool.exe, which supports W10. You don't have to switch to using VS2015 — just get the signtool.exe file from it (that's what I did). It will probably get installed in a Windows Kits subfolder of Program Files, but I just copied it to where I do my code-signing.

Also, while you're at it, you should change your code signing to use SHA2 (SHA256), since Microsoft has deprecated SHA1 code signing. You'll need to get Comodo to reissue your cert for SHA256 (Symantec/VeriSign reissued mine at no charge — Comodo will likely do the same). I changed my process to sign both SHA1 and SHA256, but note that the order of signing is important. You want to sign with SHA256 last so that if the user views the cert at the UAC prompt, SHA256 will appear at the top of the Details tab. That is, you want it to look like this:

sha256
Not this:

sha1
Regards, Joe
0
 
richardpetersAuthor Commented:
Joe
Thank you for your suggestions.  I have asked Comodo to re-issue the certificate and will let you know how I get on.  I am our of the office next week, so if my update is delayed, my appologies in advance.  I really apprecitate you input!
Regards
Richard
0
 
Joe Winograd, EE Fellow 2017, MVE 2016, MVE 2015DeveloperCommented:
Hi Richard,
No worries on the delay. Safe travels! Regards, Joe
0
 
Nadir ALTINBASElec.&Elctro.Engr.Commented:
there is a hash algorithm clashes.if you delete older one SHA and newer version upload the problem will not occur
0
 
richardpetersAuthor Commented:
It took a while, but once I got Comodo to re-issue the certificate it all worked.  Thank you!
0
All Courses

From novice to tech pro — start learning today.