Looking for a hassle-free way to streamline your software installations? AppDeployNews (ADN) Silent Switch Finder is here to simplify the process for you! This powerful yet user-friendly application empowers you to locate and activate silent installer commands across a wide array of software applications, making installation a breeze.
Feedback form
Do you have any suggestions to improve the ADN Silent Switch Finder, fill in the form!
Instructions on how to use ADN Silent Switch Finder
When you start the AppDeployNews Silent Switch Finder, you can open an installer file by clicking on the button in the bottom-left (Browse / Or Drop Here), or drop an installer file on the same button.
No information found?
If your application is not detected by the ADN Silent Switch Finder, fill in the Request AppDeployNews Application page. When we receive multiple request for an app, we will search for the information and add it to the site and AppDeployNews Silent Switch Finder.
Supported files
We use several methods to determine with which installer vendor the setup is built.
The supported file types are:
-
- MSI (Windows Installer File)
- INF Files
- Reg Files
- Nullsoft Installers
- Installscript setup
- Firefox 7z sfx installer
- WiX Installer
- Opera Installer
- NSIS Installer
- InnoSetup
- PDFForge Setup
- Foxit Installer
- WinRar-SFX
- Wise Installer
- Installshield AFW
- Installshield Installer
- Surfshark Installer
- Cab SFX Installer
- Winzip SFX Installer
- UPX Packed executable
Common Installation parameters
If you would like to know more about the most used installer types we have gathered information for the most important ones.
InnoSetup
INSTALL COMMAND LINE SWITCHES
/SP-
Disables the This will install… Do you wish to continue? prompt at the beginning of Setup.
/SILENT, /VERYSILENT
Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the startup prompt is (if you haven’t disabled it with the ‘/SP-‘ command line option explained above). If a restart is necessary and the ‘/NORESTART’ command isn’t used (see below) and Setup is silent, it will display a Reboot now. message box. If it’s very silent it will reboot without asking.
/SUPPRESSMSGBOXES
Instructs Setup to suppress message boxes. Only has an effect when combined with ‘/SILENT’ and ‘/VERYSILENT’. The default response in situations where there’s a choice is: Yes in a ‘Keep newer file?’ situation. No in a ‘File exists, confirm overwrite.’ situation. Abort in Abort/Retry situations. Cancel in Retry/Cancel situations. Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation. Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation. 5 message boxes are not suppressible: The About Setup message box. The Exit Setup? message box. The FileNotInDir2 message box is displayed when Setup requires a new disk to be inserted and the disk was not found. Any (error) message box displayed before Setup (or Uninstall) could read the command line parameters. Any message box displayed by code.
/LOG
Causes Setup to create a log file in the user’s TEMP directory detailing file installation and actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn’t being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why. The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
/LOG=”filename”
Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.
/NOCANCEL
Prevents the user from canceling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with ‘/SILENT’ or ‘/VERYSILENT’.
/NORESTART
Prevents Setup from restarting the system following a successful installation, or after a Preparing to Install failure that requests a restart. Typically used along with /SILENT or /VERYSILENT.
/RESTARTEXITCODE=exit code
Specifies a custom exit code that Setup is to return when the system needs to be restarted following a successful installation. (By default, 0 is returned in this case.) Typically used along with /NORESTART.
/NOCLOSEAPPLICATIONS
Prevents Setup from closing applications using files that need to be updated by Setup.
/NORESTARTAPPLICATIONS
Prevents Setup from restarting applications. If Setup didn’t close these applications (for example because /NOCLOSEAPPLICATIONS was used), this command line parameter is ignored.
/LOADINF=”filename”
Instructs Setup to load the settings from the specified file after having checked the command line. This file can be prepared using the ‘/SAVEINF=’ command as explained below. Don’t forget to use quotes if the filename contains spaces.
/SAVEINF=”filename”
Instructs Setup to save installation settings to the specified file. Don’t forget to use quotes if the filename contains spaces.
/LANG=language
Specifies the language to use. When a valid /LANG parameter is used, the Select Language dialog will be suppressed.
/DIR=”x:\dirname”
Overrides the default directory name displayed on the Select Destination Location wizard page. A fully qualified pathname must be specified. May include an “expand:” prefix which instructs Setup to expand any constants in the name. For example: ‘/DIR=expand:{pf}\My Program’.
/GROUP=”folder name”
Overrides the default folder name displayed on the Select Start Menu Folder wizard page. May include an “expand:” prefix, see ‘/DIR=’.
/NOICONS
Instructs Setup to initially check the Don’t create a Start Menu folder check box on the Select Start Menu Folder wizard page.
/TYPE=type name
Overrides the default setup type. If the specified type exists and isn’t a custom type, then any /COMPONENTS parameter will be ignored.
/COMPONENTS=”comma separated list of component names”
Overrides the default component settings. Using this command line parameter causes Setup to automatically select a custom type. If no custom type is defined, this parameter is ignored. Only the specified components will be selected; the rest will be deselected. If a component name is prefixed with a “*” character, any child components will be selected as well. If a component name is prefixed with a “!” character, the component will be deselected.
/PASSWORD=password
Specifies the password to use. When an invalid password is specified, this command line parameter is also ignored.
UNINSTALL COMMAND LINE SWITCHES
/SILENT, /VERYSILENT
When specified, the uninstaller will not ask the user for startup confirmation or display a message stating that the uninstall is complete. Shared files that are no longer in use are deleted automatically without prompting. Any critical error messages will still be shown on the screen. When ‘/VERYSILENT’ is specified, the uninstallation progress window is not displayed. If a restart is necessary the ‘/NORESTART’ command isn’t used (see below) and ‘/VERYSILENT’ is specified, the uninstaller will reboot without asking.
/SUPPRESSMSGBOXES
Instructs the uninstaller to suppress message boxes. Only has an effect when combined with ‘/SILENT’ and ‘/VERYSILENT’. See ‘/SUPPRESSMSGBOXES’ under Setup Command Line Parameters for more details.
/LOG
Causes Uninstall to create a log file in the user’s TEMP directory detailing file uninstallation. This can be a helpful debugging aid. The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)
/LOG=”filename”
Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Uninstall will abort with an error message.
/NORESTART
Instructs the uninstaller not to reboot even if it’s necessary.
NullSoft Scriptable Install System
/S
Silent installation
Related to: IfSilent, SilentInstall, SilentUnInstall, SetSilent, Silent Installers/Uninstallers
/NCRC
Skip CRC check of the installer, ignored if CRCCheck force was set in the installer
Related to: CRCCheck
/D=C:\Application or /D=”C:\Program Files\Application”
Set installation folder ($INSTDIR)
Must be the last parameter on the command line and must not contain quotes even if the path contains blank spaces.
Note that command line options can be ignored or overridden by the author of an installer.
InstallShield
SETUP.EXE COMMANDLINE PARAMETERS.
/uninst
Uninstalls the product
/removeonly
Also uninstalls the product, but depending upon how authored it may display the welcome/maintenance dialog
/r
Record the installation to create an ISS answer file which may be used in a silent installation command
/s
Install silently. By default the silent installation is based on the response file called Setup.iss in the same directory. (Response files are created by running Setup.exe with the /r option.) To specify an alternative file name or location of the response file, use the /f1 parameter.
/f1″c:\temp\answerfile.iss”
Specifies an alternative response file name and path; by default /s will look for setup.iss in the same directory as the setup executable and /r will create setup.iss in the Windows directory (%windir%).
/f2″c:\temp\logfile.iss”
Specifies an alternative log file name and path; by default the log file will be created in the same directory as the setup executable with the name setup.log.
/SMS
Instructs a silent setup not to release the current session until the installation is complete. Without this switch a silent installation will immediately appear complete and run in the background. Use this switch to have any additional installations or script actions wait for installation to complete (such as in a batch file). The parameter was introduced to support MS Systems Management Server which would temporarily map a drive during installation to access source files (where it would immediately complete, and SMS would unmap the drive to the source files before the installation was complete.)
/m”MyMIF”
Generate a .MIF file (used by SMS and some other management solutions to report status information).
/m”MyMIF” /m1″1111-2222-”
Specifies the serial number to be written to a .MIF file (used with /m parameter)
/m”MyMIF”/m2″ENU”
Specifies the locale string to be written to a .MIF file (used with /m parameter)
/d”<path to folder containing setup.dbg>”
Debug InstallScript portion of the setup with the InstallScript debugger (ISDbg.exe). This is intended for setup authors to troubleshoot a setup and not for admins- the action requires a setup.dbg file to be available.
/f”AlternateSetup.inx”
Specify alternative compiled script. Setup.exe looks for a compiled script file named Setup.inx, this parameter may be used to specify a different name for the compiled script file. Note that in earlier versions of InstallShield (InstallShield – Windows Installer Edition), this parameter served to initiate a repair of the installation.
/L1031
/L1033
Specifies the language for the setup for those setups that support multiple languages. Language must be identified by decimal (LCID).
/delayedstart:10
Delay initialization of the installation. With this parameter, specify the amount of time (in seconds) by which initialization of the installation is to be delayed after Setup.exe is launched.
/deleter
Do not clone a second Setup.exe process when debugging. By default, Setup.exe clones a second process so that it properly uninstalls applications from machines on which no InstallScript installation had previously been run. Use this option when debugging a DLL function that is called from your own authored installation script.
/extract_all:”c:\temp”
Extract a package’s files but do not run the setup.
/hide_usd
Suppress update dialog box for multiple installations. When this parameter is used and an update-enabled installation detects multiple previous installations, the installation updates the first previous installation that it finds without prompting the user to select which product installation to update (default).
/ig
Specify the value of the system variable INSTANCE_GUID. If this option is not used, the installation automatically assigns a value to INSTANCE_GUID (for multi-instance installations, this value is a newly generated GUID; for standard installations, this value is the same as the value of PRODUCT_GUID).
/z
This parameter may be used to pass data to the InstallScript system variable CMDLINE.
/a
Perform an administrative installation. An administrative installation copies (and decompresses) your data files to a directory specified by the user, but it does not create shortcuts, register COM servers, or create an uninstall log.
/j
Advertise the installation. An advertised installation creates shortcuts, registers COM servers, and registers file types, but does not install your product’s files until the user invokes one of these installed entry points.
/x
Uninstall the installation (if previously installed).
/p:<password>
For a password protected setup, this option may be used to supply the password at the command line (normally in support of a silent installation).
/ua:<URL to InstMsiA.exe>
If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required.
/uw:<URL to InstMsiW.exe>
If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required.
/us:<URL to ISScript.msi>
If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required.
/um:<URL to .MSI package>
If download locations are specified in the setup, those paths may be overridden using this parameter. Note that only the path is required.
/b<local directory>
If a path to locally cache setup files is specified, this path may be overridden using this parameter.
/v:<MSIEXEC parameters>
Pass command-line options and values of public properties through to Msiexec.exe.
/w
Forces Setup.exe to wait until the installation is complete before exiting (similar to /SMS).
/h
By default, the build engine automatically creates an installation that supports Setup.exe cloning in cases where cloning is required (such as in multi-disk installations). Specifiy this parameter to have Setup.exe clone itself to a temporary location and run from that location.
InstallAnywhere
COMMAND-LINE ARGUMENTS FOR INSTALLANYWHERE INSTALLERS
-i
Sets the installer interface mode: silent/console/gui.
c:\myinstall.exe -i silent
sh ./install.bin -i console
-f
Sets the location of a response file (installer.properties file) for the installer to use. (See Silent Installers and Response Files.)
c:\myinstall.exe -f c:\tmp\installer.properties
NOTE:This path can be absolute or relative. (Relative paths are relative to the location of the installer.)
-r
Creates a response file. (See Generating Response Files.)
c:\myinstall.exe -r c:\temp\myinstaller.properties
In the example above, a response file named myinstaller.properties will be written to the c:\temp directory. If you do not enter a path and file name for the response file, the file will be named installer.properties or [installername].properties and it will be created in the same directory as the installer.
NOTE: Response files can be used to provide input for silent installers.
-D
Sets or modifies variables.
c:\myinstall.exe -Dmyvar=myvalue
-l
Uses the specified language code (and optional country code) to set the locale for the installer. (See Language Codes.)
c:\myinstall.exe -l en
sh ./install.bin -l pt_BR
The required language code is a two-character (commonly lowercase) code defined by the ISO-639 standard. InstallAnywhere accepts both old (iw, ji, and in) and new (he, yi, and id) language codes.
The optional country code is a two-character (commonly uppercase) code defined by the ISO-3166 standard.
NOTE: Locale options are only respected if the installer includes localizations for the locale you specify.
-jvmxms
Sets the JVM heap size initial value.
<installer_name> -jvmxms <size>
The default size for these values is measured in bytes. Append the letter k or K to the value to indicate kilobytes, m or M to indicate megabytes, and g or G to indicate gigabytes. For example, to set the initial JVM heap size to 25 megabytes, enter the following:
install.exe -jvmxms 25m
-jvmxmx
Sets the JVM heap size maximum value.
<installer_name> -jvmxmx <size>
The default size for these values is measured in bytes. Append the letter k or K to the value to indicate kilobytes, m or M to indicate megabytes, and g or G to indicate gigabytes. For example, to set the maximum JVM heap size to 50 megabytes, enter the following:
install.exe -jvmxms 50m
-?
-help
Shows help for the InstallAnywhere installer.
NOTE: On Windows, -help works only from the console launcher. Make sure to set the LaunchAnywhere to Console in the Windows area in the Platforms view on the Project page. (For an installed LaunchAnywhere to provide this information, you need to make sure it is explicitly set to Console Launcher on the action.)
MSIEXEC
INSTALL OPTIONS
Set the install type for launching an installation package.
msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>
PARAMETERS
| Parameter | Description |
|---|---|
| /i | Specifies normal installation. |
| /a | Specifies administrative installation. |
| /ju | Advertise the product to the current user. |
| /jm | Advertise the product to all users. |
| /j/g | Specifies the language identifier used by the advertised package. |
| /j/t | Applies transform to the advertised package. |
| /x | Uninstalls the package. |
<path_to_package> |
Specifies the location and name of the installation package file. |
EXAMPLES
To install a package named example.msi from the C: drive, using a normal installation process, type:
msiexec.exe /i "C:\example.msi"
DISPLAY OPTIONS
You can configure what a user sees during the installation process, based on your target environment. For example, if you’re distributing a package to all clients for manual installation, there should be a full UI. However, if you’re deploying a package using Group Policy, which requires no user interaction, there should be no UI involved.
SYNTAX
PARAMETERS
| Parameter | Description |
|---|---|
<path_to_package> |
Specifies the location and name of the installation package file. |
| /quiet | Specifies quiet mode, which means there’s no user interaction required. |
| /passive | Specifies unattended mode, which means the installation only shows a progress bar. |
| /qn | Specifies there’s no UI during the installation process. |
| /qn+ | Specifies there’s no UI during the installation process, except for a final dialog box at the end. |
| /qb | Specifies there’s a basic UI during the installation process. |
| /qb+ | Specifies there’s a basic UI during the installation process, including a final dialog box at the end. |
| /qr | Specifies a reduced UI experience during the installation process. |
| /qf | Specifies a full UI experience during the installation process. |
REMARKS
-
- The modal box isn’t shown if the installation is cancelled by the user. You can use qb+! or qb!+ to hide the CANCEL button.
EXAMPLES
To install package C:\example.msi, using a normal installation process and no UI, type:
msiexec.exe /i "C:\example.msi" /qn
RESTART OPTIONS
If your installation package overwrites files or attempts to change files that are in use, a reboot might be required before the installation completes.
SYNTAX
PARAMETERS
| Parameter | Description |
|---|---|
<path_to_package> |
Specifies the location and name of the installation package file. |
| /norestart | Stops the device from restarting after the installation completes. |
| /promptrestart | Prompts the user if a reboot is required. |
| /forcerestart | Restarts the device after the installation completes. |
EXAMPLES
To install package C:\example.msi, using a normal installation process with no reboot at the end, type:
msiexec.exe /i "C:\example.msi" /norestart
LOGGING OPTIONS
If you need to debug your installation package, you can set the parameters to create a log file with specific information.
SYNTAX
PARAMETERS
| Parameter | Description |
|---|---|
| /i | Specifies normal installation. |
| /x | Uninstalls the package. |
<path_to_package> |
Specifies the location and name of the installation package file. |
| /li | Turns on logging and includes status messages in the output log file. |
| /lw | Turns on logging and includes non-fatal warnings in the output log file. |
| /le | Turns on logging and includes all error messages in the output log file. |
| /la | Turns on logging and includes information about when an action started in the output log file. |
| /lr | Turns on logging and includes action-specific records in the output log file. |
| /lu | Turns on logging and includes user request information in the output log file. |
| /lc | Turns on logging and includes the initial UI parameters in the output log file. |
| /lm | Turns on logging and includes out-of-memory or fatal exit information in the output log file. |
| /lo | Turns on logging and includes out-of-disk-space messages in the output log file. |
| /lp | Turns on logging and includes terminal properties in the output log file. |
| /lv | Turns on logging and includes verbose output in the output log file. |
| /lx | Turns on logging and includes extra debugging information in the output log file. |
| /l+ | Turns on logging and appends the information to an existing log file. |
| /l! | Turns on logging and flushes each line to the log file. |
| /l* | Turns on logging and logs all information, except verbose information (/lv) or extra debugging information (/lx). |
<path_to_logfile> |
Specifies the location and name for the output log file. |
EXAMPLES
To install package C:\example.msi, using a normal installation process with all logging information provided, including verbose output, and storing the output log file at C:\package.log, type:
msiexec.exe /i "C:\example.msi" /L*V "C:\package.log"
UPDATE OPTIONS
You can apply or remove updates using an installation package.
SYNTAX
PARAMETERS
| Parameter | Description |
|---|---|
| /p | Installs a patch. If you’re installing silently, you must also set the REINSTALLMODE property to ecmus and REINSTALL to ALL. Otherwise, the patch only updates the MSI cached on the target device. |
| /update | Install patches option. If you’re applying multiple updates, you must separate them using a semi-colon (;). |
| /package | Installs or configures a product. |
EXAMPLES
msiexec.exe /p "C:\MyPatch.msp"
msiexec.exe /p "C:\MyPatch.msp" /qb REINSTALLMODE="ecmus" REINSTALL="ALL"
msiexec.exe /update "C:\MyPatch.msp"
msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318} /package {AAD3D77A-7476-469F-ADF4-04424124E91D}
Where the first GUID is the patch GUID, and the second one is the MSI product code to which the patch was applied.
REPAIR OPTIONS
You can use this command to repair an installed package.
SYNTAX
msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>
PARAMETERS
| Parameter | Description |
|---|---|
| /fp | Repairs the package if a file is missing. |
| /fo | Repairs the package if a file is missing, or if an older version is installed. |
| /fe | Repairs the package if file is missing, or if an equal or older version is installed. |
| /fd | Repairs the package if file is missing, or if a different version is installed. |
| /fc | Repairs the package if file is missing, or if checksum does not match the calculated value. |
| /fa | Forces all files to be reinstalled. |
| /fu | Repairs all the required user-specific registry entries. |
| /fm | Repairs all the required computer-specific registry entries. |
| /fs | Repairs all existing shortcuts. |
| /fv | Runs from source and re-caches the local package. |
EXAMPLES
To force all files to be reinstalled based on the MSI product code to be repaired, {AAD3D77A-7476-469F-ADF4-04424124E91D}, type:
msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}
SET PUBLIC PROPERTIES
You can set public properties through this command. For information about the available properties and how to set them, see Public Properties.
Source: Microsoft
QSetup
/Silent
The Setup program will run without intervention of the user.
/Hide
The Setup program will run completely in the background, presenting no dialog during the process.
/InstallDir=”Destination Directory”
Define the default Destination directory for the setup.
Recent Comments