We ship a MSI which supports upgrades. We schedule the RemoveExistingProducts
custom action after InstallInitialize using MajorUpgrade
element –
<MajorUpgrade
Schedule="afterInstallInitialize"
AllowDowngrades="yes" />
The MSI performs a variety of things including GACing,
writing to registry and also includes a custom action which is used to install
a kernel mode driver.
We have been running into an issue in the following scenario
-
1.
V1 MSI is installed first.
2.
V2 MSI is installed at a later point.
a. For
cases, there is a bug in v2 MSI, we expect the MSI installation to roll back
and finally leave the system with v1 installed.
b. We
see everything rolling back to v1 (including the registry keys, file versions
etc.) except for the kernel driver. After the previous rollback, we no longer
see the kernel mode driver.
In the log file, I did not see the custom action being run
when v1 is reinstalled.
InstallExecuteSequence for the custom action that
installs the kernel driver looks something like this –
<Custom Action="InstallDrivers"
Before="WriteRegistryValues" >
(NOT REMOVE) AND
Privileged
</Custom>
I am wondering if the conditions have something to do with
this? I would appreciate any help in figuring out the root cause for this
issue.
Regards,
Surya
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
