This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Program Name in UAC prompt for signed Suite project
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 16, 2013
06:39 AM
Program Name in UAC prompt for signed Suite project
Is there a way to determine the Program Name that is displayed in the UAC prompt for a signed Suite project? For .ism projects this works fine and also a package without Authenticode signatures works quite OK by using the actual package name as Program Name, but when a signed Suite project is built, the Program Name is Setup, which causes confusion in users as the name displayed in the prompt corresponds neither to the package or the product name they were expecting to install. The "Use Custom Version Properties" settings for releases don't seem to have any effect on this.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 17, 2013
10:21 AM
I believe this is pulled from the setup.exe tab setting "Executable File Name". Does changing that change the text you see in the UAC prompt? Is changing the name of the .exe file acceptable, or would you need this to be configurable separately?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 17, 2013
11:47 AM
MichaelU wrote:
I believe this is pulled from the setup.exe tab setting "Executable File Name". Does changing that change the text you see in the UAC prompt? Is changing the name of the .exe file acceptable, or would you need this to be configurable separately?
Unfortunately that setting changes only the exe name and the name in UAC prompt is still Setup, which (unsurprisingly) matches neither our product name or the exe name. The publisher setting is correct as that comes from the signing certificate, but it makes us look amateurish when the program name displays an obvious default value while our other products use the correct name. For after all, our other installers are Basic MSI .ism projects and this is our first Suite project.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 17, 2013
11:52 AM
I also inspected whether this was due to signing flaw with IsCmdBld.exe and Suite projects (http://community.flexerasoftware.com/showthread.php?205909-Signing-issue-with-IsCmdBld), but builds created using an elevated IsCmdBld.exe and straight from the IDE have this issue, too.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 17, 2014
01:00 AM
Unfortunately this issue still exists also in InstallShield 2013 😞
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 28, 2014
09:18 AM
I've reproduced this and logged it internally as IOA-000085115. I can't guarantee timelines, but we'll see about fixing this for our next release.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 29, 2014
04:03 AM
MichaelU wrote:
I've reproduced this and logged it internally as IOA-000085115. I can't guarantee timelines, but we'll see about fixing this for our next release.
Thanks MichaelU, that's great to hear!
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)