Sadly, the Windows Installer doesn’t support that. Some process outside your package (a bootstrapper/chainer?) will have to manage the upgrade from per-user to per-machine.
More Related Contents:
- Extract MSI from EXE
- How to implement WiX installer upgrade?
- Why does MSI require the original .msi file to proceed with an uninstall?
- What is the wix ‘KeyPath’ attribute?
- Why use Windows Installer XML (WiX) over VDPROJ?
- How to associate application with existing file types using WiX installer?
- How to register file types/extensions with a WiX installer?
- Wix custom uninstallation action – how to run before msi removing files
- How can I find the product GUID of an installed MSI setup?
- Change my component GUID in wix?
- How to make better use of MSI files
- What installation product to use? InstallShield, WiX, Wise, Advanced Installer, etc [closed]
- Syntax for guids in WIX?
- Changing text color to Wix dialogs
- Removing files when uninstalling WiX
- Adding Custom prerequsites to visual studio setup project
- How can I find the Upgrade Code for an installed MSI file?
- Silent installation of a MSI package
- Uninstall from Control Panel is different from Remove from .msi
- What is the benefit and real purpose of program installation?
- Create MSI or setup project with Visual Studio 2012
- Does an universal cross-platform installer exists? [closed]
- How to Explicitly Remove dll During Majorupgrade Using Wix Toolset
- Create MSI from extracted setup files
- How to include wxi file into wxs?
- Why is it a good idea to limit deployment of files to the user-profile or HKCU when using MSI?
- Odd ‘Program name’ when installing signed msi installer [duplicate]
- How to create precofigured installer (MSI or EXE) with valid signature?
- WIX Installer: Prevent installation on Windows Server 2012 R2
- How to deny folder permission to Users with wix installer