While analyzing one of customer issues reported to me, I came accross an interesting problem which – having prior knowledge how it works – would be solved in minutes, not in hours and days as it really took.
The customer reported that an MSP patch created by RayPack works fine, but not really up to his expectations. While being considerably smaller than a full MSI upgrade, the installation took a while because the previous version must have been uninstalled and installed again in the background. This is basically the idea how major upgrades are working, and the customer wanted to switch to a typical patching, which (depending on conditions) would mean going for a small update or a minor update.
We suggested to him that while usually not recommended in packaging projects, minor upgrades are different from major upgrades that they must not change ProductCode, aside of some other limitations. The customer tried it anyway and reported that our suggestion initially helped, only to report some minutes later that it actually hadn’t. The new version of product had been apparently installed (and visible in ARP), but the files were not updated – new files were still missing, binary changes were not applied etc. There were no errors during update, the msiexec exit code was also fine.
Another issue was, that after installing the patch, self-repair stopped worked for random components. Removing certain key path resources triggered repair, while for others it did not work. Weird.
Analysis + findings
Our analysis indicated that it was not actually a problem with the patch itself, but more like with the way Minor Upgrades are working, and thereof the problem could be easily reproduced by installing the second MSI containing a minor upgrade with a command line:
msiexec /i <path> REINSTALLMODE=vamus REINSTALL=all /qb
vamusis non-standard, but was chosen for troubleshooting to also overwrite files in the same version). It is important to indicate that the cached MSI has to be recached from source (thus
v in the reinstall mode), otherwise you obviously can’t install an MSI as minor upgrade.
We don’t do that many minor upgrades, but enough to be aware of certain limitations, including that names of MSIs must be the same (so that Product2.0.msi cannot do a minor upgrade of Product1.0.msi etc.), the feature trees must remain unchanged, some other conditions apply (more on msdn sites).
If you ever encounter a problem like that, have some time saved by this ultimate troubleshooting:
Continue reading “Files not installed when applying a Minor Upgrade and how to troubleshoot it”