PhilB
Posts: 95
Joined: Fri Jul 06, 2007 4:13 pm

Different behaviour between digisign and signtool

One of our customers recently ran in to the issue where a .exe installer failed with the well known disk1.cab invalid digital signature error. The strange thing was that other versions of the product installed successfully on the same box. I reproduced this locally by installing onto a machine with no internet access.
Eventually I worked out that the failing installer had been built on a machine where the advanced installer was configured to use an external signing tool (Signtool) and the working ones on a machine where it was configured to use the internal tool (Digisign).
This seems strange to me. Arguably, the installer that is failing is actually performing the correct actions even though it's more convenient for us when the installs work! The installers signed with Digisign in effect end up adding unvalidated certificates into the trusted certificate store.
We are using a rather old version of Advanced Installer (11.0), so I wondered whether this behaviour is expected or whether it has changed in a later version?
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Different behaviour between digisign and signtool

Hello,

We apologize for the delayed reply.

Indeed, I can confirm you that our internal signing tool has some limitation and drawbacks (as you already saw) and this is the reason it became deprecated in our latest versions of Advanced Installer. We recommend all our customers to use the latest version of Advanced Installer alongside Microsoft's default signing tool (SignTool).

If there is anything else we can help you with just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”