Random Code Signing Error

We have a multiple exe application that I create an update for monthly. This month's update will not compile. I keep getting the error, "Compiler error GEN1053: Code signing process failed. Error Code: 1". What is weird is that it fails on a different exe, everytime. One time it signed all of my exes and then failed to sign the update package itself. Nothing has changed on my machine and I have verified Windows Updates have not applied anything new prior to the last update I compiled. I also disabled my antivirus after reading the forums looking for answers prior to this post.

Any ideas?

I decided to try manually signing them via command line and it's behaving similarly. It sends back a different error.

"This may happen if you specify an RFC 3161 timestamp URL but used the /t option or you specified a legacy Authenticode timestamp URL but used the /tr option".

It actually gave me a second error as well when reviewing the batch further.

SignTool Error: An unexpected internal error has occurred.
Error information: "SignerTimeStamp() failed." (-1073700864/0xc000a000)

Could it by that the timestamp server is randomly timing out?

Hello,

it's very well possible that the timestamp server is down or not always accessible. Just try another one.

Friedrich

That is what I am thinking as well. I finally got an install to compile 100% after many retries.