I'm currently using Advanced Installer for my primary installation deployment, but the software updates are being handled by a separate 3rd-party application. Through the software update process, my software's program files may be replaced, added, or removed depending on the update.
I've had an intermittent problem that occurs after software updates; when I open a filetype associated with my application (this association is set via Advanced Installer), I'm prompted by the Windows Installer to locate my original installation executable to run a repair installation.

If I do not locate the installer executable for the repair, and error message is displayed and the file will not be opened.

I've read of a similar issue with a user trying to access an installed application from a different user account, and from what I understand from that post is that the Windows Installer runs a repair installation if it detects that resources are missing. Is this due to the file association method?
Can you please provide input on what I can do in this situation to fix this issue? Please let me know if I can provide additional details.
Thank you for your support.
Evan
FOLLOW US
Get the latest news in Application Packaging