Installer does not ask for elevated priviledges (Windows 7 + Server 2008 issue)


The installer does not ask for elevated priviledges when installing and installation fail because of this. It needs this even when running as administrator on the operating systems. The settings are ignored on operating systems not supporting this.
The installer package does not display the property needed for this but it is in the msi text
Open the setup
    "LangId" = "3:1033"
    "RequiresElevation" = "11:FALSE"
Change the above to this
    "LangId" = "3:1033"
    "RequiresElevation" = "11:TRUE"
The installer will now ask for elevated priviledges on windows 7 and server 2008
Closed Jun 30, 2011 at 8:25 PM by andym1978
The changes I posted today may have fixed this issue. Download the 1.6.2 beta from the downloads page. If this installer doesn't work for everyone, this issue can be reopened. It worked great on my machine.


alexschrod wrote Mar 4, 2011 at 1:41 PM

If you can give me the fix in the WiX code the installer uses, I'll implement it. Otherwise just run it from an elevated command prompt or some other elevated application. I might look deeper into it later.

larsbuchjepsen wrote Mar 10, 2011 at 9:43 AM

I am not an expert in WiX'

in the package the InstallPrivileges needs to be set to elevated
in a custom action it might need to be set to to no for impersonation to not impersonate the current user

jcollum wrote Mar 31, 2011 at 4:55 PM

Having this issue too, using Win7 32b.

larsbuchjepsen wrote Mar 31, 2011 at 6:01 PM

Workaround until fixed:
  1. search for cmd in the start menu
  2. rightclick and select "Run as administrator" which makes the command prompt both elevated and with administrative priviledges
  3. go to the folder that you downloaded the installer into and run it

andym1978 wrote Jun 30, 2011 at 4:25 PM

I think we are going to need a boostrapper to elevate the installer. I've looked everywhere for info and this is the only working solution I've found. Surprisingly, I've found WiX help to be a little lacking, and have not been able to find examples of how to do this. Don't other developers run into this issue??? It may be as simple as upgrading to Wix 3.5, but I'll have to see.

wrote Jun 30, 2011 at 8:25 PM

wrote Feb 22, 2013 at 12:30 AM

wrote May 16, 2013 at 12:04 PM