When using a legacy VB6 application and opening some specific forms inside that application, the Windows Installer belonging to Microsoft Navision (which is installed on the same machine) pops-up like in the attached image.
It happens every time, but on this machine only.
The VB6 application has absolutely no relation with Navision!
What can be done to avoid this anomalous interaction between the two applications?
This is down to a corrupt windows installer database and your app is using some component that Microsoft Dynamics tried to install. Your best bet is to remove and reinstall Microsoft Dynamics NAV, or use MSICUU to remove the "broken" package.
Update: MSICUU was retired in preference to the Program Install and Uninstall troubleshooter but I've not used this new utility.
来源：https://stackoverflow.com/questions/8077749/why-does-my-application-triggers-the-installer-of-another-application