I have a few projects that were originally created with Advanced Installer 11.9. The setting under "Multiple Instances" of "Generate instances at installation time" was used. While new major versions were created using 11.9, upgrading instances with this setting was not an issue.
Earlier this year I upgraded the projects to use Advanced Installer 15.x, and now 16.1. With the same setting still in use, now when upgrading instances, I'm able to upgrade the primary instance (#0), but any other instance I receive the message
This messagebox has a combobox pre-filled with the expected location of the msi in a user application data folder and a browse button.The feature you are trying to use is on a network resource that is unavailable. Click OK to try again or enter an alternate path to a folder containing the installation package "example.msi" in the box below.
How to reproduce:
Install two or more instances of a version (e.g. v.1.0)
Upgrade primary instance to a higher version (e.g. v.2.0) - This should be successful
Upgrade another instance to a higher version - This displays the messagebox looking for an msi file (Basically cannot continue)
I have archived project files, logs, and image of message box.
I have seen in other posts that using this option is not reccommended for major upgrades due to some limitations, however, this wasn't an issue with older versions of Advanced Installer (i.e. 11.9). Also, I see 16.1 had a bug fix
which from the wording I thought would be the fix to this issue, but it appears to not be.A secondary instance cannot be repaired/upgraded when multiple instances are installed