unmatching digital signature between exe bootstraper and msi

[mj_kng]

Hi,
Sorry to bore you, but I can't solve this problem.
I packed a signal .EXE file, and send someone to help me do a digital signature. However,after the digital signature, when I setup my .EXE file, it Popup a messagebox says "unmatching digital signature between exe bootstraper and msi database".
Can you tell me why this happen and how can I avoid this?
Thank you very much.

Best Regards
Gavin

[Dan]

Hello,

This error occurs when the signature from the .CAB or .MSI doesn't coincide with the one from the .EXE. This is our default implementation.

Advanced Installer can digitally sign all of the following files that it creates . In order to achieve that you can go in the Digital Signature Page and enable the “Enable signing” option. Advanced Installer is using the default DigiSign.exe signing utility.

If you are using any external tools, you should make sure SignTool.exe or SignCode.exe are installed on the development machine. For example, SignCode.exe comes with Microsoft Windows SDK. This can be done from menu bar -> "Options" -> "External Tools..." -> select a correct path for the utility. If "Use and external tool" option is not enabled, Advanced Installer's DigiSign.exe default tool will be used.

If you have other questions, please let us know.

Best regards,
Dan

[mj_kng]

Hello, Dan

Thank you for your reply.
For some reason I can't use Advanced Installer to sign my .EXE, so i didn't enable he “Enable signing” option. In this condition the "external tools" won't work, right?
However,after the digital signature(by someone else use other tools), when I setup my .EXE file, it popup a messagebox says "unmatching digital signature between exe bootstraper and msi database".
The .EXE file must be signed by someone else use other toos, and in this condition, is there anything I can do to avoid the error?

Best Regards
Gavin

[Dan]

Hello Gavin,

For some reason I can't use Advanced Installer to sign my .EXE,so i didn't enable he “Enable signing” option.

Can you please give us more details about the reason why you cannot use the “Enable signing” option? Do you get an error when trying to enable it?

The .EXE file must be signed by someone else use other toos, and in this condition, is there anything I can do to avoid the error?

Unfortunately there is no workaround for this. At run time we check if the signature from the .CAB or .MSI coincide with the one from the .EXE. If they don't you will be prompted with that error. This is our default behavior.

Best regards,
Dan

[mj_kng]

Hello Dan,

Thank you for your reply.
I take your advice, use the “Enable signing” option and the error didn't happen any more.
Thank you very much.

Best Regards
Gavin

[Dan]

Hi,

You're welcome Gavin. I'm glad you got this working.

If you have other questions, please let us know.

Best regards,
Dan

[hadas]

Hi,

My installer install as a post-install signed exe file as prerequisite.
The exe file is installer I wrote in advanced installer and signed it with the same file as the main installer.
When I uninstall the main installer I get the "unmatching digital ..." message for the second installer.
If I uninstall the second directly there is no problem.

Hadas

[Dan]

Hello Hadas,

In order to have a better view about this, can you please send us the .AIP (project file) and a verbose log of the uninstall process to support at advancedinstaller dot com so we can investigate it? If it contains confidential information you can send us a small test project which reproduce this behavior.

Best regards,
Dan