Hello guys,
After further investigations we've been able to replicate that behavior (updater process still running after the upgrade process and
returning 0xE0000027 error code).
The behavior occurs when the MSI has the same name between multiple versions (e.g. [ProductName]) and when the same download location is used for the MSI from the server. Also, you need to have the updater configured to
install updates without elevation. For example, the default download location is: [CommonAppDataFolder][Manufacturer][ProductName]\updates\
It seems that the Updater.exe does not have enough privileges to overwrite already existing file.
Usually the update has the same name when the Update Configuration Project has a single update defined and you always change this update, instead of defining a new one. When there are multiple updates defined, updater will always install the latest one (when updates are installed silently).
Also the update may have the same name if you always recreate the
Update Configuration Project from scratch during the build operation process.
As a solution for that, just enable the
"Delete update package file after installation" option in the
"Updates Configuration Project":
- Updates.png (38.28 KiB) Viewed 3303 times
Or, define a different update for each version in the
"Updates Configuration project":
- Updates_different.png (36.5 KiB) Viewed 3303 times
Hope this helps! If you have any other questions, please don’t hesitate to contact us.
Best regards,
Liviu