Hello Ninjas,

I've received a InstallShield based Setup.exe, which executes four other InstallShield setup.exe files.
I'm able to to run the first install silently with /S /f1"setup.iss", but then the next Setup.exe is asking me to go through the installation.

I've tried to run all of the setup.exe installers seperately, but it seems like the "outer" Setup.exe is installing features, which lies beyond the steps I'm able to automate.

I've tried to repackage the installation with Wise, but it seems to be too complex, or maybe I'm just lacking Wise skills :-)

Does any of you have any suggestions? Manual installation isn't an option.

Thanks in advance,

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



If the other EXEs are also InstallShield-authored, you can add logging to the command line. The resulting log with tell you why they're failing. I imagine that they're checking for the presence of a file, registry entry or whole product. If they're simple wrappers around an MSI, then just extract the MSI from each and use those with the appropriate switch to silence them.

As ever, because I like to know what havoc a vendor's installer is going to try and wreak on my workstation estate, I would be repackaging the first EXE into an MSI anyway.

Answered 06/19/2015 by: VBScab
Red Belt

  • Thanks for your answer.

    I've tried adding logging, but the only result i get is that the response .iss file is missing information.

    The other installers aren't actually failing. They're just halting and waiting for me to complete the installation - they aren't using the answer file.

    My first approach was, as you mention, to extract the MSI's and do the installation with those.

    It works for the two of them, but for the others, i'm getting an error telling me that the MSI can't run separately, and i should use the Setup.exe instead..

    Any other suggestions? :-D
Please log in to comment
>i should use the Setup.exe instead
Using a transform or the command line, add a property named 'ISSETUPDRIVEN' with a value of '1'.
Answered 06/22/2015 by: VBScab
Red Belt

Please log in to comment