Menu
I'm running into the following issue after signin an MSI installer. I'm using signtool.exe and the msi file signs OK however when I test it, the UAC confirmation dialog which shows my company's name shows a 'Program name:' of 55847.msi, rather than the name of my setup file. E.g. Setup1.msi Does any one know how to 'fix' this?
Thanks in advance
281
The main difference between the two extensions is their purpose. EXE is used mainly to indicate that the file is an executable one. In comparison, MSI indicates that the file is a Windows installer. While an MSI is used only with installers, this is not the case with EXE.
MSI is an installer file which installs your program on the executing system. Setup.exe is an application (executable file) which has msi file(s) as its one of the resources. Executing Setup.exe will in turn execute msi (the installer) which writes your application to the system.
When ThinApp installs the MSI package for individual users, the default MSI installation directory is %AppData%\<inventory_name> (VMware ThinApp). You can override the default installation directory by using an INSTALLDIR property in the msiexec command.
Add /d option to the command line of signtool.exe when signing your MSI:
signtool.exe /d "Your Software Name"
UAC confirmation dialog will show Your Software Name as the Program name.
105
If you Authenticode-sign your .msi package, Windows will show that as the name. Otherwise, you get MSI's temporary copy of it, which has a random name.
42
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
