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: Issue when installing the application in Windows 7
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
‎Oct 13, 2011
01:02 AM
Issue when installing the application in Windows 7
Hi,
We developed one Windows Application using VS 2005, Framework 2.0 and C#. and we created the Setup using Installshield 2010.
The installer is working fine (creating shortcuts in Desktop and adding in to start menu) with Windows XP.
When we installed the installer on a Windows 7 machine its not creating the shortcuts in Desktop or adding the shortcut in to Start menu. After doing some investigation we found that we need to install the application after changing the UAC (User Access Control) or right click the application and run as administrator.
Is there any way to install the application without changing the UAC or run as administrator
Thanks & Regards,
Nidheesh
We developed one Windows Application using VS 2005, Framework 2.0 and C#. and we created the Setup using Installshield 2010.
The installer is working fine (creating shortcuts in Desktop and adding in to start menu) with Windows XP.
When we installed the installer on a Windows 7 machine its not creating the shortcuts in Desktop or adding the shortcut in to Start menu. After doing some investigation we found that we need to install the application after changing the UAC (User Access Control) or right click the application and run as administrator.
Is there any way to install the application without changing the UAC or run as administrator
Thanks & Regards,
Nidheesh
(7) Replies
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
01:18 AM
What kind of project do you use?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
01:20 AM
lambertpandian wrote:
What kind of project do you use?
Simple MSI
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
02:55 AM
You can specify the required execution level.
To specify the required execution level for a release:
In the View List under Media, click Releases.
In the Releases explorer, click the release that you would like to configure.
Click the Setup.exe tab.
For the Required Execution Level setting, select Administrator.
To specify the required execution level for a release:
In the View List under Media, click Releases.
In the Releases explorer, click the release that you would like to configure.
Click the Setup.exe tab.
For the Required Execution Level setting, select Administrator.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
03:32 AM
Kevin.Wan wrote:
You can specify the required execution level.
To specify the required execution level for a release:
In the View List under Media, click Releases.
In the Releases explorer, click the release that you would like to configure.
Click the Setup.exe tab.
For the Required Execution Level setting, select Administrator.
What will happen if a standard user tries to install the applicaiton after setting the execution level as administrator?
Regards,
Nidheesh
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 13, 2011
11:31 PM
Use the Required Execution Level setting to specify the minimum level required by your installation's Setup.exe file for running the installation (the setup launcher, any InstallShield prerequisites, and the .msi file) on Windows Vista and later platforms. The available options are:
Administrator—Setup.exe requires administrative privileges to run. Administrators must authorize it; non-administrators must authenticate as an administrator.
Highest available—Setup.exe prefers administrative privileges. Administrators must authorize it; non-administrators run it without administrative privileges. This is the default option for InstallScript and InstallScript MSI projects.
Invoker—Setup.exe does not require administrative privileges, and all users can run it without administrative privileges. Setup.exe does not display any UAC messages prompting for credentials or for consent. This is the default option for Basic MSI projects.
Administrator—Setup.exe requires administrative privileges to run. Administrators must authorize it; non-administrators must authenticate as an administrator.
Highest available—Setup.exe prefers administrative privileges. Administrators must authorize it; non-administrators run it without administrative privileges. This is the default option for InstallScript and InstallScript MSI projects.
Invoker—Setup.exe does not require administrative privileges, and all users can run it without administrative privileges. Setup.exe does not display any UAC messages prompting for credentials or for consent. This is the default option for Basic MSI projects.
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2011
10:34 PM
Did you try the Guidlines at http://msdn.microsoft.com/en-us/library/windows/desktop/aa368772(v=vs.85).aspx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 04, 2012
03:49 PM
nidheesh.kuvil wrote:
What will happen if a standard user tries to install the applicaiton after setting the execution level as administrator?
Regards,
Nidheesh
From what I have seen, it will force a login of a user with higher credentials. HTH.