Solved

SignTool Error with Windows 10

Posted on 2016-07-28
5
297 Views
Last Modified: 2016-08-09
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.
0
Comment
Question by:richardpeters
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 54

Accepted Solution

by:
Joe Winograd, EE MVE 2015&2016 earned 500 total points
ID: 41733422
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
 

Author Comment

by:richardpeters
ID: 41734848
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
 
LVL 54

Expert Comment

by:Joe Winograd, EE MVE 2015&2016
ID: 41734877
Hi Richard,
No worries on the delay. Safe travels! Regards, Joe
0
 
LVL 5

Expert Comment

by:Nadir ALTINBAS
ID: 41740536
there is a hash algorithm clashes.if you delete older one SHA and newer version upload the problem will not occur
0
 

Author Closing Comment

by:richardpeters
ID: 41748696
It took a while, but once I got Comodo to re-issue the certificate it all worked.  Thank you!
0

Featured Post

Business Impact of IT Communications

What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As with any other System Center product, the installation for the Authoring Tool can be quite a pain sometimes. This article serves to help you avoid making these mistakes and hopefully save you a ton of time on troubleshooting :)  Step 1: Make sur…
Technology opened people to different means of presenting information, but PowerPoint remains to be above competition. Know why PPT still works today.
The viewer will learn how to successfully download and install the SARDU utility on Windows 7, without downloading adware.
An overview on how to enroll an hourly employee into the employee database and how to give them access into the clock in terminal.

728 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question