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: Windows 7 (build 7100): 'Unknown' Publisher UAC prompt, Multilang Basic MSI
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
‎May 05, 2009
06:24 AM
Windows 7 (build 7100): 'Unknown' Publisher UAC prompt, Multilang Basic MSI
Hi,
I receive a 'Unknown' Publisher UAC prompt on Windows 7 RC running a signed Basic MSI Setup that contains more than one UI languages from Setup.exe.
Holger
I receive a 'Unknown' Publisher UAC prompt on Windows 7 RC running a signed Basic MSI Setup that contains more than one UI languages from Setup.exe.
Holger
(14) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 05, 2009
11:52 PM
We had the same with our install that is also a basic msi wrapped in a setup.exe. It was because we are signing our exe as part of our build process. However, the Signing tab of the Release in IS gives the option to signthe Windows Installer Package. That eliminate the 'Unknown' but there is still a prompt which shows the publishers as Trusted.
Anyone know how to eliminate that prompt?
Anyone know how to eliminate that prompt?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 06, 2009
01:08 AM
Both, .msi and .exe, are signed using the built-in signing feature. The problem occurs only when running Setup.exe and if the setup supports more than one language. Running the .msi works fine.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 06, 2009
11:03 AM
So the same scenario yields a signed (instead of unsigned) prompt on Windows Vista? Is Windows 7 more picky about signatures vs. transforms? The only difference I can think of in the multilanguage case is a transform is applied.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 06, 2009
02:35 PM
I'm don't know about Holger_G's issue, but in our case, the prompt comes from the msi and is displayed in the middle of the execute sequence. This prompt does not appear in Vista at all (either signed or unsigned).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 06, 2009
02:39 PM
MichaelU wrote:
So the same scenario yields a signed (instead of unsigned) prompt on Windows Vista? Is Windows 7 more picky about signatures vs. transforms? The only difference I can think of in the multilanguage case is a transform is applied.
Yes, our QA did not report any issues with Vista yet.
What I´ve not tested yet is to launch the .msi with msiexec.exe and applying a transform to it. Will do that tomorrow at work.
Problem seems to be more Windows 7 related. Applying a transform using msiexec.exe results in the same problem.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 07, 2009
12:45 PM
I'll see if we can find out anything. As a preliminary guess, based on your report, it sounds like it's a behavior change on Windows 7. Maybe we can learn if it's intentional and if there's a good way to handle the language transform case.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 08, 2009
01:14 PM
Our contact indicated that the application of unsigned transforms will now intentionally invalidate the (runtime) signature of the .msi to which they're being applied. As this is new to Windows 7, which IS2009 doesn't officially support, I don't expect we will address this for IS2009; we're tracking it under IOC-000080958 for future releases. However as a workaround you can sign your .mst files in an uncompressed release. Let me know if your testing shows otherwise. 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2009
01:21 AM
have you checked with vista??
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 11, 2009
03:04 AM
MichaelU wrote:
Our contact indicated that the application of unsigned transforms will now intentionally invalidate the (runtime) signature of the .msi to which they're being applied. As this is new to Windows 7, which IS2009 doesn't officially support, I don't expect we will address this for IS2009; we're tracking it under IOC-000080958 for future releases. However as a workaround you can sign your .mst files in an uncompressed release. Let me know if your testing shows otherwise. 🙂
Great information Michael, that works for us. I will add a post build step to our automated build process to sign the transforms.
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 17, 2009
02:06 AM
MichaelU wrote:
Our contact indicated that the application of unsigned transforms will now intentionally invalidate the (runtime) signature of the .msi to which they're being applied. As this is new to Windows 7, which IS2009 doesn't officially support, I don't expect we will address this for IS2009; we're tracking it under IOC-000080958 for future releases. However as a workaround you can sign your .mst files in an uncompressed release. Let me know if your testing shows otherwise. 🙂
Michael, is it possible to build a Self-Extracting Executable Setup File for a Basic MSI media from the Command Line (like the ReleasePackager.exe tool for IScript projects)?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 17, 2009
03:37 PM
If you're building the entire media (i.e. rebuilding the whole project), yes, you can always choose that build option. But otherwise, no, we don't offer anything that can do this right now.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 18, 2009
07:39 AM
Okay, that means I need to use a 3rd party tool or so to create a selfextracting executable of an uncompressed release (incl. signed transforms) or IS 2010 if I need to provide such a selfextracting package, right?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 18, 2009
11:12 AM
Yes, that is correct. You're targeting Windows 7 systems and not using IS2010 already? :eek: (Just kidding! Mostly.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 19, 2009
02:22 AM
MichaelU wrote:
Yes, that is correct. You're targeting Windows 7 systems and not using IS2010 already? :eek: (Just kidding! Mostly.)
Just PM me a valid license key then I will make use of it, premier preferred of course :cool: