This is a bug in “Apps & features” as far as I know. The WiX people have closed this issue as a Windows bug and I assume they have notified the correct people @ Microsoft. The behavior is still the same in Insider build 15042 though so it is probably not going to get fixed … Read more
The wix documentation here explains the Impersonate attribute: This attribute specifies whether the Windows Installer, which executes as LocalSystem, should impersonate the user context of the installing user when executing this custom action. Typically the value should be ‘yes’, except when the custom action needs elevated privileges to apply changes to the machine. You also … Read more
If you need root privileges every time, the best thing is to start your program as root and drop them (in a subprocess) with setuid and setgid. That’s what apache does when it needs to bind to the restricted port 80. If gaining root rights is the exception instead of the rule and the program … Read more
If you have a filtered token for the interactive user – for example, one retrieved via WTSQueryUserToken() – you can retrieve the unfiltered (“elevated”) token by using the GetTokenInformation function with the TokenLinkedToken option.
npocmaka’s answer works, but it generates the following error message: “The batch file cannot be found.” This isn’t a problem if the console window closes when the script terminates, as the message will flash by so fast, no one will see it. But it is very undesirable if the console remains open after the script … Read more
ProcessStartInfo.Verb will only have an effect if the process is started by ShellExecuteEx(). Which requires UseShellExecute = true. Redirecting I/O and hiding the window can only work if the process is started by CreateProcess(). Which requires UseShellExecute = false. Well, that’s why it doesn’t work. Not sure if forbidding to start a hidden process that … Read more
The best way to detect if they are unable to perform an action is to attempt it and catch the UnauthorizedAccessException. However as @DannySmurf correctly points out you can only elevate a COM object or separate process. There is a demonstration application within the Windows SDK Cross Technology Samples called UAC Demo. This demonstration application … Read more
You can add a Registry entry in [Registry] Section that will set run as Administrator as a default action for running this app. Example: Root: “HKLM”; Subkey: “SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers”; \ ValueType: String; ValueName: “{app}\tomcat7w.exe”; ValueData: “RUNASADMIN”; \ Flags: uninsdeletekeyifempty uninsdeletevalue; MinVersion: 0,6.1
Inno Setup does not have any built-in mechanism to access or modify user environment from installer running with elevated/Administrator privileges. All the attempts to achieve this rely on tricks like: runasoriginaluser flag or ExecAsOriginalUser function. Some examples: Modifying or accessing registry of logged in user: Inno Setup Creating registry key for logged in user (not … Read more
If UAC is enabled on the computer, something like this should work: If Not WScript.Arguments.Named.Exists(“elevate”) Then CreateObject(“Shell.Application”).ShellExecute WScript.FullName _ , “””” & WScript.ScriptFullName & “”” /elevate”, “”, “runas”, 1 WScript.Quit End If ‘actual code