Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 6

Digital signature not recognized when uninstalling from 'Apps & Features'

Hi all,
We have InstallShield 2016 InstallScript MSI project which generates a setup.exe

We sign this setup.exe and when installing users can see it is digitally signed by us.

However, when on Windows 10 and Windows 2016, when uninstalling from Start -> Settings -> System -> Apps & Features,
we click on the 'Uninstall' button for our product, then confirm the uninstall by clicking on the 'Uninstall' button again.

At this point, User Account Control (UAC) kicks in and displays below in the dialog, basically saying the Publisher is Unknown instead of
displaying our name.

Do you want to allow this app from an unknown publisher to make changes to your device?


Publisher: Unknown
File origin: Hard drive on this computer

Show more details.

When clicking on the 'Show more details' above, it says:
Program location: "C\Program Files (x86)\InstallShield Installation Information\{product guid}\setup.exe -runfromtemp -I0x0409 -removeonly.

I looked at setup.exe at C\Program Files (x86)\InstallShield Installation Information\{product guid} and it is around 1 MB where as our
original setup.exe was around 60 MB. So it seems InstallShield has stripped off stuff from the original setup.exe and placed as slim
version of setup.exe and the signed digital certificate is not found ?
How can I resolve this please. Is this a known issue with InstallScript MSI projects that use setup.exe rather than msi file.

Note that if I run the original setup.exe, then the signed certificate is recognized and I can uninstall or repair.

Also, I swapped the slim setup.exe at C\Program Files (x86)\InstallShield Installation Information\{product guid} with the original
one and in this case it is able to recognize and display the signed certificate when uninstalling from Apps & Features

Kindly advise.
Labels (1)
0 Kudos
2 Replies
Level 6

appreciate if anyone can help with this.
0 Kudos
Level 6

This issue seems to be because my project is InstallShield InstallScript MSI.
I create Basic MSI and InstrallScript projects and they don't have this issue.

Can someone please comment if this is a known InstallShield issue with the InstallScript MSI projects?
If so, any workarounds ?
0 Kudos