I'm using VS2012 & InstallShield2013 to generate installer file.
Some of the installed user couldn't run this application on WIn 7 OS. But they can get into the installed directory
and right click 'Run as an Administrator' it works.
The icon on the desktop, when i right right click there is no option like 'Run as an Administrator'.
I checked in the InstallShield directory C:\Program Files\InstallShield\2013LE\Support\
There are three files:
SetupExe.Admin.manifest,
SetupExe.Highest.manifest,
SetupExe.Invoker.manifest
So I followed this article : http://helpnet.flexerasoftware.com/installshield20helplib/Content/helplibrary/SpecifyingRequiredExecution.htm
and selected Required Execution Level 'Invoker' and Include MSI Engine:yes in the 'Release Setup /Single Image'
How can i enable the option to right click 'Run as an Administrator'?
It's important for me to fix this problem, for the users of Win 7 32/64 & Win Vista.
I'm totally confused about these files. Please help me.
The settings you reference in InstallShield will not affect how your application itself runs; instead they only change the privileges setup.exe requires when launched.
As for your application, there are a number of potential moving pieces that can affect whether the "Run as administrator" option shows up in the context menu in Explorer:
If the exe referenced by the shortcut has a manifest that requires administrative access, it will always run elevated, and the Run as administrator option will not appear
If the exe referenced is detected as an installer, Windows may choose to act as though it has a manifest requiring administrative access, and thus the Run as administrator option may not appear
If the Program Compatability Assistant (PCA) has decided the program needs administrative access, ditto
If the shortcut's compatibility settings have been modified to select "Run this program as an administrator", ditto
If UAC is disabled, Explorer may choose not to show Run as administrator
Some of these scenarios may persist across uninstallation and reinstallation; Windows can be very aggressive in its attempts to improve the end-user experience. However in all these cases, the end result is that your application would launch as an administrator.
If you always require administrative access in your application, you are strongly advised to implement the first of these: embed a manifest that includes the requiresAdministrator setting. This is equivalent to what the settings you reference change for setup.exe, but must be done in your application's executable.
Related
After installing the application, the installer and uninstaller files are properly saved in the "install application folder" and in the "Start menu application folder" rispectively.
For example:
- "install application folder" = "C:\Users\\AppData\Roaming\"
- "Start menu application folder" = "C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\"
Sometimes, though, the uninstaller file is not displayed into the application folder of the Start Menu Installed Applications List (list of installed Applications displayed on the left by pressing the Windows keyboard key).
Unfortunately I can't reproduce the problem. It doesn't appears each time I launch the Installer and I couldn't understand under which circumstances it appears.
Is there a possibility it can be solved by forcing a refresh of the Start Menu Installed Applications List? if this is the case, how can do it?
Thanks in advance to everyone for the possible help
EDIT: no solution but a workaround found here Inno Setup Start menu uninstall shortcut is not shown on Windows 10 2nd answer
Windows 8 and 10 hides shortcuts to uninstallers and help files on purpose, this is by design.
The Windows logo requirements says that you should only provide a single shortcut to your main application in the start menu. Only create multiple shortcuts if you have a suite of applications (like MS Office etc.). These guidelines have been in place for at least 20 years!
Our installer has a setup.exe file which internally contains the Msi.
Once installed, the option to repair is available from the programs and features right click context menu.
However when repair is selected, a dialog is shown which gives the option to browse for the msi.
Since the msi is nested in setup.exe, and since the installer was not able to find any appropriate msi in appdata, this has rendered the repair functionality all but useless.
Is it possible to change the installer, so that it can repair from setup.exe?
You have three main options, depending on which scenarios you want to support:
Just double-click the setup.exe, and if the msi is already installed it will run in maintenance mode. You can select to repair it from there. This is good for a one-time scenario.
Run setup.exe with the /a argument, which creates an administrative installation point for the install. This can just be a folder on your desktop, or anywhere you like. This is also good for a one-time scenario, and should be compatible with launching repair from Programs and Features.
Configure your installation to cache the .msi package by using the setting in the Releases view. This should enable all maintenance scenarios for everyone, at the ongoing cost of some hard drive space.
I have an installation setup created by LE instalshield under VS2012. This setup.exe installs the application, registers some DLLs and activeX files and adds some registry entries as pointers to the location of an SQL server database. This application is to be run by all the users in a group policy created by the IT of their institution. The installation is done under the full administration privileges.
If the UAC of the win 7 is not fully lowered, some DLLs and OCXs are not registered (although the required registry keys are written in the MACHINE area of the registry without any problem!). So in order to avoid this I have to manually lower the UAC to its lowest level before running the Setup.exe. This solves the problem with the registration of DLLs.
But sometimes even though the installed program works for the installed login, it does not work for other logins within the same group/users. So how can I create a setup.exe under LEinstallshield that would 1) not require manual lowering of UAC, 2) install for all users under the same group policy?
Thank you for all your help.
You should be asking why your installer isn't compatible with UAC instead of asking how to disable UAC. If you are authoring a clean MSI using the registry tables (COM extraction) instead of using COM self-reg or other custom actions, it should just work.
I am creating a web app in Android using PhoneGap.
While installing node.js,*the installation gets failed showing me user installations are disabled via policy on the machine*.
How can i resolve it ?
I tried #PeacefulWarrior solution mentioned above but it did not work for me on Windows 7 machine.
So I tried changing this setting from registry, and it worked.
Go to key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
Change the DisableUserInstalls value to 0.
Hi follow below steps
From the Start menu, click Run…
In the Run… command dialog, enter gpedit.msc
In the Group Policy Editor, select Computer Configuration > Administrative Templates > Windows Components > Windows Installer
In the Extended Properties pane, double-click Prohibit User Installs
Click Disabled
Click OK and close the Group Policy Editor
Run the installer again..
I have a small application whose exe has to be worked in windows server 2008.
But in Win Server 2k8 it works properly only if the Option Run as administrator is selected, even if the user have admin previlege.
By selecting the property of that file to always run as admin, in the compatiblity tab will solve the issue.
But i have to enable this property while it installs.
And I am building the installer in Installshield 2009.
My question is how to enable this property from the installsield.
How can I make the Exe alwas run as admin.
Any one pleeasse hellpp......
Thanks In Advance..
Jijesh.
If your exe always requires administrative privileges, you should build it with a manifest that specifies requireAdministrator. If it only requires administrative privileges sometimes, it should probably launch itself with ShellExecute using the verb "runas". In neither case should you rely on the shortcut option.