signing an Installer2Go setup executable

[Guest]

[stashspace]

Have you ever had issues with signing a setup executable created by the Installer2Go application?

I can sign OCXs and other EXE files fine, but when I sign my install exe that is created by Installer2Go, the resulting file no longer runs.  Specifically, it starts to run and then throws the following error:
"Unexpected Error.  Please check file access permissions."

To be clear, the .exe runs fine before I sign it.  Also, when I look at the "properties" of the file after I've signed it, all looks great (it shows it has a digital signature, etc.).

Some additional info:
- I'm using the windows sdk tool "signtool.exe" to add the certs
- Runnnign XP SP2
- the exe in question is a setup exe that wraps an msi file (note: it appears I can sign the .msi file just fine)

Thanks for your help

[techpro]

I developed my own installer and I had a similar issue when I began code signing setups. The installer was basically a self extracting EXE stub that extracted a bunch of files to a temporary folder and then ran one of them to do the installation. The EXE stub had some crude self-checking code that went wrong when the length was altered by adding a digital signature. Since I had the code for the stub, I fixed it by removing the self-check.

In your case, I think the answer will be to dump Installer2Go and use a different setup generator.

[Tags:]