I have a script that runs several install packages silently and this one EXE I want to add to the install script requires particular options be invoked. However I can't seem to find any information on generating an INI for the EXE and the /r command didn't appear to generate an ISS file when trying to install it that way. Any suggestions?



0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


From the look of the options I would say that the exe "runs" an embedded msi. Try unpacking the exe with an archive tool like 7zip. Now you can look in the proberites table and see if you can find the correct properties to select the desired option. Then run the exe with the /S/v/qn PROERTY=value

or run the msi with installshield to create an .mst

Hope this was helpful

Answered 09/01/2013 by: emillj
Senior White Belt

  • That might work I'll try that out, thank you...so this is probably a stupid question but what do you mean run it with installshield? I don't have an admin repack tool set or anything I have to code everything by hand.
  • You don't need to repack, just create a new mst project, point to the msi and click throu the install then save the .mst and install with msiexec /i installer.msi TRANSFORMS=savedfile.mst /qn
  • How do you create an mst project, if I don't have any sort of packing/repackage creation software?
  • You probably need to buy installshield to do that unless you find a free tool. It is possible to create mst with Orca (free and part of win 7 SDK) but you cant just "run" the msi and get a mst there, you need do know what changes you want to do to the msi (and do the changes in orca) and then save as a mst.

    Your best bet is to open the msi in Orca or InstEd and look at the properties table. If you find a property where you can set whatever it is you need then add that to the msiexex install string or create a mst as described above.

    If this is a one time thing mabye it would be better to pay to have the job done as buying Installshield is rather expensive. (And before you ask, no I can't provide that service but finding somebody that van shouldn't be to hard)
    • I work with a legacy environment still...
  • Enable MSI logging (voicewarmup) and install your setup.exe - the resulting logs in %temp% will show you what parameters were passed to the MSI (look for command line in the logs), create an MST in Orca against the MSI with those properties, install and test.
    • I ended up using an alternate method and worked out a SendKeys to do the job.
Please log in to comment



Which App is the setup.exe for?

Answered 08/30/2013 by: ekgcorp
Tenth Degree Black Belt

  • It is a setup.exe for some drivers/configuration for a small electronics company. The /? command for the exe returns this to me...if this is helpful.

    /L language ID
    /S Hide initalization dialog. For silent mode use: /S/v/qn.
    /V parameters to MsiExec.exe
    /UA<url to InstMsiA.exe>
    /UW<url to InstMsiW.exe>
    /UM<url to msi package>
  • Looks like you have an embedded MSI with this one... so the easy way is to pass the silent switch to the msi with the /v... So it would look like:

    setup.exe /v /qb! (to break it down /v pass arguments to MSI, /qb! tells the MSI "q"uite, "b"asic progress bar, "!" no cancel button on progress bar for users)
  • I was having multiple issues with the EXE and having it run correctly so I used SendKeys and wrote a script with that to accomplish what I need it to do, and I know its a little goofy, but it works...
Please log in to comment

You could run the .exe with a /r (app).iss to record settings you wish to include in the install. Then include in the resource folder with .exe.


Answered 09/05/2013 by: prodouz3
Senior Yellow Belt

  • Thanks, I ended up having too many issues with that and not much support or options within the EXE itself so I had to use an alternative method (SendKeys).
Please log in to comment
Answer this question or Comment on this question for clarity