Click to Rate and Give Feedback
MSDN
MSDN Library
Windows Development
Windows Installer
System Policy
User Policies
 AlwaysInstallElevated
AlwaysInstallElevated

You can use the AlwaysInstallElevated policy to install a Windows Installer package with elevated (system) privileges.

To install a package with elevated (system) privileges, set the AlwaysInstallElevated value to "1" under both of the following registry keys:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer

If the AlwaysInstallElevated value is not set to "1" under both of the preceding registry keys, the installer uses elevated privileges to install managed applications and uses the current user's privilege level for unmanaged applications.

Because this policy permits users to install applications that require access to directories and registry keys for which the user may not have permission to view or change, you should consider whether it provides your users with an appropriate level of security. Setting this policy directs Windows Installer to use system permissions when it installs the application on the system. If this policy is not set, applications not distributed by the administrator are installed using the user's privileges and only managed applications get elevated privileges.

Note that once the per-machine policy for AlwaysInstallElevated is enabled, any user can set their per-user setting.

Remarks

For information about the interaction of this policy with installation sources, see Managing Installation Sources.

Data Type

REG_DWORD

 

 

Send comments about this topic to Microsoft

Build date: 9/7/2011

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
If this is set, then Visual Studio 2005 and up deployment packages won't install right      Nathan Brown HD   |   Edit   |   Show History
You will have to manually elevate the install to install the MSI or setup generated from Visual Studio 2005 or 2010. Or edit the MSI afterwards to change the SecureCustomProperties value in the MSI. See http://blogs.msdn.com/b/vsnetsetup/archive/2011/12/21/msi-built-on-visual-studio-installs-into-quot-c-quot-instead-of-quot-c-program-files-quot.aspx
Tags What's this?: Add a tag
Flag as ContentBug
Processing
© 2012 Microsoft. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker