Suggested Articles
Update to exe installer package stops using any CPU
"Recently we attempted to create an update to our initial exe installer package. We created the update package, configuration file and deployed both to our server. The silent update didn't work so we then attempted to run the updater.exe /checknow command. Running this command presented the window that it detected an update was available and proceeded to the "Installing update ..." screen. At this point, the update process stops using any CPU. We have let it sit there for 20-25 minutes on a pretty decent Macbook Pro running Windows 10. Manually uninstalling and installing the new package works fine. Any suggestions on what could be causing this issue or workarounds would be greatly appreciated."
Re: Update to exe installer package stops using any CPU
Hello and welcome to our forums,
We apologize for the delayed reply. We had two days off last week on Thursday and Friday here.
We further tested and investigated the issue and were able to replicate the scenario. It seems this happens because you are using the same ProductCode and ProductVersion for your new setup package with a different installation databases. Please note that when building a new setup package you should always change the ProductVersion ( and the ProductCode too if you want to build a major upgrade). Otherwise you will get the following error message:
"Another version of this product is already installed..."
Unfortunately due to a bug in our EXE setup it seems this error message is displayed even when launching the EXE silently. Thus when the Updater launches the updates package under System account the above error message will be spawned and the process will hand wait for user input. But the error message won't be visible because the process runs under Systems account. We will fix this issue in a future version of Advanced Installer. Thank you for bringing this to our attention.
To avoid this error you should proceed like this:
1. open the setup project of your new setup package and go to "Product Details" page
2. increase the "Product Version" field value and save the project
3. choose [Generate New] product code option
4. rebuild the setup project
5. rebuild the updates config project
6. upload on your server the build updates config file and the updates setup[ package and test again the updates scenario
Let us know if this helped.
All the best,
Daniel
We apologize for the delayed reply. We had two days off last week on Thursday and Friday here.
We further tested and investigated the issue and were able to replicate the scenario. It seems this happens because you are using the same ProductCode and ProductVersion for your new setup package with a different installation databases. Please note that when building a new setup package you should always change the ProductVersion ( and the ProductCode too if you want to build a major upgrade). Otherwise you will get the following error message:
"Another version of this product is already installed..."
Unfortunately due to a bug in our EXE setup it seems this error message is displayed even when launching the EXE silently. Thus when the Updater launches the updates package under System account the above error message will be spawned and the process will hand wait for user input. But the error message won't be visible because the process runs under Systems account. We will fix this issue in a future version of Advanced Installer. Thank you for bringing this to our attention.
To avoid this error you should proceed like this:
1. open the setup project of your new setup package and go to "Product Details" page
2. increase the "Product Version" field value and save the project
3. choose [Generate New] product code option
4. rebuild the setup project
5. rebuild the updates config project
6. upload on your server the build updates config file and the updates setup[ package and test again the updates scenario
Let us know if this helped.
All the best,
Daniel