If you invoke from Powershell, you should use the call operator & This should then also work with parameters enclosed in quotes:
& msiexec /i `"My Installer.msi`" /quiet JREPATH=`"c:\BLA BLA`"
More Related Contents:
- How can I compare the content of two (or more) MSI files?
- How to make better use of MSI files
- What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc [closed]
- Why is it a good idea to limit the use of custom actions in my WiX / MSI setups?
- What is the purpose of administrative installation initiated using msiexec /a?
- Syntax for guids in WIX?
- How can I determine what causes repeated Windows Installer self-repair?
- Changing text color to Wix dialogs
- Removing files when uninstalling WiX
- How to pass CustomActionData to a CustomAction using WiX?
- How to add a WiX custom action that happens only on uninstall (via MSI)?
- Wix Installer : Setting component condition property when doing a MSIEXEC admin install at command line
- Silent installation of a MSI package
- Why does the MSI installer reconfigure if I delete a file?
- Doing Major Upgrade in Wix creates 2 entries in Add/Remove Programs
- How can I programmatically read the properties inside an MSI file?
- Registering COM EXE with WIX
- WIX (remove all previous versions)
- Failing condition wix
- How to include wxi file into wxs?
- What is the compression method used by MSI files?
- Why is it a good idea to limit deployment of files to the user-profile or HKCU when using MSI?
- wix installer ice03 Invalid Language Id
- Wix Tools update uses old custom actions
- Forcing an upgrade of a file that is modified during its initial installation
- MSI Reference Counting: Two products install the same MSIs
- Good resources for learning how to create MSI installers from WiX [closed]
- WIX Installer: Prevent installation on Windows Server 2012 R2
- How to display a non-blocking warning for the operating system in Wix?
- WiX – Doing a major upgrade on a multi instance install