If I understand your question correctly, you are indicating that an attempt to install your application's prerequisites causes Explorer to appear. If that is the case, it would be useful to diagnose what the InstallShield wizard is doing at that time. For setup prerequisites, the easiest way to see this is a debug log created with setup.exe /debuglog
. For feature prerequisites, you need to specify the property ISDEBUGLOG
to the full path for the debug log it should use (this can be the same or a different path as the other one). So for both you can specify something like setup.exe /debuglog /v"ISDEBUGLOG=\"C:\debuglog.txt\""
.
Once you have the relevant debug log, try to figure out what setup.exe has launched that causes Explorer to appear, and then assess why it has launched that. Perhaps it is as simple as a prerequisite definition which you can change with the prerequisite editor.