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?
FOLLOW US
Get the latest news in Application Packaging