Cannot silently install an .exe, installshield


I am trying to create a software package that is going to be made into a managed installation for K1000. I created a batch file to go along with the .exe and imported that into K1000's software inventory and then created the managed installation. Once pushed out to my target machine, I can see that the machine downloaded the package under C:\Programdata\quest\kace\downloads, but the package did not actually deploy. To do some troubleshooting, I tried to manually run the .exe from a cmd window with the silent switch /s, nothing happens, no tasks are created or anything. If I remove the /s, it begins the Install Shield Wizard window like it normally would simply clicking on the .exe. I tried some more parameter combinations hoping to get a different result and also created the log file.

I know it is said that this log file might not be much help, which brings me here I suppose. Here is the log file (no matter what parameters I use, this is the output:)
[InstallShield Silent]
File=Log File

I know that code -5 means that the file was not found, but everything is indeed there where it needs to be. I ran the batch file as well and that did nothing, so I've really just been trying to rule out different possibilities at this point. This .exe is intended to install document camera software.

I attached a screenshot. BTW, I changed the name of the file just to test if that was the problem (because under the file properties it says Setup.exe even though it was called Luna_setup.exe)

I am wondering if maybe because this is an .exe not an .msi, there is something I am doing wrong with the commands.

Thanks, Alex

0 Comments   [ + ] Show comments

Answers (3)

Posted by: Hobbsy 3 years ago
Red Belt
First off, if the manufacturer of the exe file did not provide a silent switch then you may struggle to install the application silently. 

Second off, why did you not just connect the exe file to the software item to use in the managed installation, is it because you also need additional files to complete the installation?

If that is the case wrap up all the files you need in a compressed zip file, make sure it is called xxxx.zip and is created using a proprietary zip application i.e. winzip or 7zip and then attach the zip file to the software item to create the managed installation. The command line in the managed installation only needs to be xxx,exe with any switches you can apply. 

KACE will then download the zip file, unpackage it into a temp location on the target and then run the command line.

  • Yeah I don't think this is going to install silently. I just created a test software item with just the executable and then tried to add the silent switch on the managed install detail page, it still doesn't install. Remove the silent switch, the installshield window will appear as normal. and install fine. I went the route where I have the batch file do all of the execution out of habit, I have struggled with KACE's default installation/override parameters option in the past with other packages. - amcfarland 3 years ago
    • if the provider of the exe don't provide a silent option (it would the second software I am aware of, the first is VeraCrypt) the most effective way would the AppDeploy Repackager:
      https://www.itninja.com/community/dell-kace-appdeploy-repackager - Nico_K 3 years ago
Posted by: anonymous_9363 3 years ago
Red Belt
If the installer is InstallShield-script based, it will require an ISS file in order to run silently. I won't document how this is done, as there are quadzillion examples available.

Be aware, however, that (too) many vendors don't test their installers in every scenario so it's easy to end up with an ISS that doesn't handle every dialog and/or every item/option on those dialogs. In these cases, you'll need to repackage.

Oh and you can ignore the advice that the installer will use the file 'setup.iss' if it sees it alongside the set-up EXE. I've had too many instances of that simply not being the case that I *always* specify the name of and path to the ISS.
Posted by: tamasult 3 years ago
White Belt


I went same issue with HP elitebook 840 g3 WWan (hp lt4102 snapdragon LTE5) driver. It looks it is an installshield script and the installer unpacking itselves but before creating a copy of the whole setup. The normal /s is not redirected injected to the second setup. The vendor doesn't give an option to silent install.

What I did:

I tried /r /f1 but .iss file doesn't record the answers of the second setup dialogues therefore silent install cannot be done.


1. extracted the original package with /extract_all:<path>

2. I did an install with the extracted one. During the setup dialogue boxes I checked my file system and realised no other copy of setup will be created, just the content extracted into %temp%

3. This HP setup is creating log files to programdata folder. For general setups give a try with /f2 option.

4. For this setup I found in the logs if a config file named lt4120Config.ini exists it can use that. As far as I remember common setups can picking up Setup.ini file.

5. In log I also realised the the following option: "Install Mode : (Loud)".

6. I found the ini file in the orignal HP package and added Install Mode into the config section:




Install Mode : Silent

Keep in mind the settings should be Case-sensitive and spaces are necessary around the colon.

6. I made an istall.cmd batch file

%SourceDir%=%~dp0   (percent + tilde + dp0)

pushd %SourceDir%


The pushd is necessary. If not changing the current/working directory to where the setup.exe is the exe will not picking up the .ini file. For me "lt4120Config.ini" but normally "Setup.ini".

After starting install.cmd I was able to do silent install with success.

Hope this can help.
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ