Hello John,
Let's start with this:
BTW, we are also including the 2019 VC++ redistributable as a merge module... could this be causing an issue?
Honestly, I do not see why that would be a problem. With that being said, I believe the fact that you are including the 2019 VC++ redistributable as a merge module does not affect the behavior.
OK, thanks... so does this look right? Should the any of these options be disabled?
Let's recap this so we can better understand what is happening.
Most likely, the reboot message appears when the newer version tries to uninstall the older version. As you may know, an upgrade proceeds as it follows:
- uninstalls the older version
- installs the newer version
Even though the service's control operations are configured as expected and the service is stopped (when the
"StopService" action is executed), as we have discussed in the earlier thread, there is a standard action that does this check before the setup gets to stop the service and it prompts with this message.
What we are doing here is that we try to stop the service before that action takes place, so we can avoid the reboot message.
Why we recapped the above: as you can see under the
"Execution Stage Condition", there are two options:
- Replaced by a new version
The difference between these two is the following:
- if the "Upgrade" option is selected, the custom action will be executed during the installation of the newer version
- if the "Replaced by a new version" option is selected, the custom action is executed during the uninstall process of the older version
In our scenario, I believe that only the
"Replaced by a newer version" option should be checked.
Additionally, please do not forget that the setup must be run elevated from the start.
Hope this helps.
Best regards,
Catalin
FOLLOW US
Get the latest news in Application Packaging