Run ExeCommand in customAction as Administrator mode in Wix Installer

by

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 need to understand the difference between deferred and immediate custom actions. See the Execute attribute on the same help page:

This attribute indicates the scheduling of the custom action. This attribute’s value must be one of the following:

deferred
Indicates that the custom action runs in-script (possibly with elevated privileges).
immediate
Indicates that the custom action will run during normal processing time with user privileges. This is the default.

At present your custom action is immediate, which means it is running with user privileges. See this blog post for lots of details, but particularly:

Any immediate custom actions impersonate the invoking user. Before Windows Vista this wasn’t a problem since at this point the installing administrative user had a privileged token. With the introduction of UAC in Windows Vista the default administrative token with UAC enabled is a filtered token and does not hold all privileges. Since immediate custom actions are not supposed to modify machine state – only to gather state data and schedule custom actions to run deferred – this still shouldn’t be a problem. After all, at this point the generation of the installation and rollback scripts is all that should be going on.

You should never modify machine state with an immediate custom action. Use a deferred one, and keep impersonate to no, and it should work:

<CustomAction Id='comReg' Directory='INSTALLLOCATION' Execute="deferred" Impersonate="no" ExeCommand='"[NETFRAMEWORK40CLIENTINSTALLROOTDIR]regasm.exe" "[INSTALLLOCATION]EAWordImporter.dll" /codebase' Return='check' />

EDIT: Schedule the custom action using the InstallExecuteSequence element:

<InstallExecuteSequence>
    <Custom Action='comReg' Before="InstallFinalize"/>
</InstallExecuteSequence>

More Related Contents:

  1. Change my component GUID in wix?
  2. How to make better use of MSI files
  3. What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc [closed]
  4. What is the purpose of administrative installation initiated using msiexec /a?
  5. How do I avoid common design flaws in my WiX / MSI deployment solution?
  6. Windows Installer and the creation of WiX
  7. Syntax for guids in WIX?
  8. How can I determine what causes repeated Windows Installer self-repair?
  9. Changing text color to Wix dialogs
  10. Wix to Install multiple Applications
  11. Removing files when uninstalling WiX
  12. Silent installation of a MSI package
  13. Uninstall from Control Panel is different from Remove from .msi
  14. How can I programmatically read the properties inside an MSI file?
  15. How to Explicitly Remove dll During Majorupgrade Using Wix Toolset
  16. File of a new component isn’t installed because there was an old component with the same file
  17. How to include wxi file into wxs?
  18. What is the compression method used by MSI files?
  19. Why is it a good idea to limit deployment of files to the user-profile or HKCU when using MSI?
  20. How to include prerequisites with msi/Setup.exe in WIX
  21. wix installer ice03 Invalid Language Id
  22. Wix burn doesn’t allow to remove file
  23. Forcing an upgrade of a file that is modified during its initial installation
  24. MSI Reference Counting: Two products install the same MSIs
  25. How to build a minimal WiX installer UI without a license page?
  26. Passing command line args to MSI from WiX bundle
  27. WIX Installer: Prevent installation on Windows Server 2012 R2
  28. WiX: Digitally Sign BootStrapper project
  29. WiX – Doing a major upgrade on a multi instance install
  30. Wix custom uninstallation action – how to run before msi removing files

Leave a Comment