[wix-users] Related MSI Package Scope is PerUser During Bundle Upgrade

Edwin Castro egcastr at gmail.com
Wed Sep 7 09:46:54 PDT 2016

I have a bundle that installs a number of EXE and MSI packages.

My main MSI package has //Package/@InstallScope = "perMachine" yet in
the bundle log I see the following during upgrades:

[2018:0AB8][2016-09-06T16:02:08]i103: Detected related package:
{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, scope: PerUser, version:
x.x.x.x, language: 0 operation: MajorUpgrade

In the bundle I have //MsiPackage/@ForcePerMachine = "yes" so I would
have expected the related package scope to be PerMachine rather than
PerUser. As a contrasting example, the related bundle has scope
reported as PerMachine:

[2018:0AB8][2016-09-06T16:02:08]i102: Detected related bundle:
{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, type: Upgrade, scope:
PerMachine, version: x.x.x.x, operation: MajorUpgrade

The upgrade works as expected but the PerUser scope reported for the
related package has always confused me. Why is the related package
reported as PerUser?

Edwin G. Castro

More information about the wix-users mailing list