- Artikel - 21.09.2022 - 2 Minuten Lesedauer -

Hier sind standardmäßige Befehlszeilenoptionen für das Microsoft Standard Installer (Msiexec.exe), die ausführbare Datei, die verwendet wird, um Pakete zu interpretieren und Produkte zu installieren. Befehlszeilenoptionen sind groß- und kleinschreibungsfähig. Msiexec legt eine Fehlerstufe für die Rückgabe fest, die [Den Systemfehlercodes](https://learn.microsoft.com/de-de/windows/win32/debug/system-error-codes) entspricht. Hinweis Die Befehlszeilenoptionen, die in diesem Thema identifiziert werden, sind ab Windows Installer 3.0 verfügbar. Die Windows [Befehlszeilenoptionen](https://learn.microsoft.com/de-de/windows/win32/msi/command-line-options) sind mit Windows Installer 3.0 und früheren Versionen verfügbar. ## /help Hilfe- und Schnellverweisoption. Zeigt die richtige Verwendung des Setupbefehls an, einschließlich einer Liste aller Schalter und des Verhaltens. Die Beschreibung der Verwendung kann in der Benutzeroberfläche angezeigt werden. Die falsche Verwendung einer beliebigen Option ruft diese Hilfeoption auf. Das entsprechende Windows Installer Command-Line Option lautet: `/?`. ### Beispiele `Msiexec /help`. ## /quiet Option für die ruhige Anzeige. Das Installationsprogramm führt eine Installation aus, ohne eine Benutzeroberfläche anzuzeigen. Es werden keine Eingabeaufforderungen, Nachrichten oder Dialogfelder für den Benutzer angezeigt. Der Benutzer kann die Installation nicht abbrechen. Verwenden Sie die `/norestart` Befehlszeilenoptionen, `/forcerestart` um Neustarts zu steuern. Wenn keine Neustartoptionen angegeben werden, startet das Installationsprogramm den Computer bei Bedarf neu, ohne dass ein Benutzer aufgefordert oder warnungen angezeigt wird. Das entsprechende Windows Installer Command-Line Option lautet: `/qn`. ### Beispiele `Msiexec /package Application.msi /quiet` `Msiexec /uninstall Application.msi /quiet` `Msiexec /update msipatch.msp /quiet` `Msiexec /uninstall msipatch.msp /package Application.msi / quiet` ## /passive Passive Anzeigeoption. Das Installationsprogramm zeigt dem Benutzer eine Statusleiste an, die angibt, dass eine Installation ausgeführt wird, aber keine Aufforderungen oder Fehlermeldungen für den Benutzer angezeigt werden. Der Benutzer kann die Installation nicht abbrechen. Verwenden Sie die `/norestart` Befehlszeilenoptionen, `/forcerestart` um Neustarts zu steuern. Wenn keine Neustartoption angegeben wird, startet das Installationsprogramm den Computer immer neu, ohne dass der Benutzer aufgefordert oder gewarnt wird. Das entsprechende Windows Installer Command-Line Option lautet: `/qb!`- mit `REBOOTPROMPT=S` Festgelegt auf der Befehlszeile. ### Beispiele `msiexec /package Application.msi /passive` ## /norestart Option nie neu starten. Das Installationsprogramm startet den Computer nach der Installation nie neu. Die entsprechende Windows Installer-Befehlszeile hat `REBOOT=ReallySuppress` sich auf der Befehlszeile festgelegt. ### Beispiele `msiexec /package Application.msi /norestart`. ## /forcerestart Option "Immer neu starten". Das Installationsprogramm startet immer nach jeder Installation den Computer neu. Die entsprechende Windows Installer-Befehlszeile hat `REBOOT=Force` sich auf der Befehlszeile festgelegt. ### Beispiele `msiexec /package Application.msi /forcerestart` ## /promptrestart Eingabeaufforderung vor dem Neustart der Option. Zeigt eine Meldung an, dass ein Neustart erforderlich ist, um die Installation abzuschließen, und fragt den Benutzer, ob das System jetzt neu gestartet werden soll. Diese Option kann nicht zusammen mit der `/quiet`-Option verwendet werden. Die entsprechende Windows Installer-Befehlszeile hat `REBOOTPROMPT = ""` sich auf der Befehlszeile festgelegt. ## /deinstallieren (Produkt) Produktoption deinstallieren. Deinstalliert ein Produkt. Das entsprechende Windows Installer Command-Line Option ist`/x.` ### Parameter *<Package.msi| Productcode>* ## /uninstall (Patch) Deinstallationsoption. Deinstalliert einen Update-Patch. Das entsprechende Windows Installer Command-Line Option lautet: `/I` mit `MSIPATCHREMOVE=Update1.msp | PatchGUID1[;Update2.msp | PatchGUID2]` festgelegter Befehlszeile. ### Parameter */package <Package.msi | ProductCode> /deinstallieren \[; Update2.msp | PatchGUID2\]* ## /log Protokolloption. Schreibt Protokollierungsinformationen in eine Protokolldatei im angegebenen vorhandenen Pfad. Der Pfad zum Speicherort der Protokolldatei muss bereits vorhanden sein. Das Installationsprogramm erstellt die Verzeichnisstruktur für die Protokolldatei nicht. Weitere Informationen zu allen Methoden, die zum Festlegen des Protokollierungsmodus verfügbar sind, finden Sie unter ["Normal Logging](https://learn.microsoft.com/de-de/windows/win32/msi/normal-logging) Windows Installer". Das entsprechende Windows Installer Command-Line Option lautet: `/L*`. Die folgenden Informationen werden in das Protokoll eingegeben:

- Statusmeldungen - Nichtfatale Warnungen - Alle Fehlermeldungen - Starten von Aktionen - Aktionsspezifische Datensätze - Benutzeranforderungen - Anfängliche UI-Parameter - Veraltete Speicher- oder tödliche Exitinformationen - Out-of-Disk-Space-Nachrichten - Terminaleigenschaften

## /package Installieren Sie die Produktoption. Installiert oder konfiguriert ein Produkt. Das entsprechende Windows Installer Command-Line Option lautet: `/I`. ### Parameter *<Package.msi| Productcode>* ## /update Installieren Sie die Option "Patches". Installiert eine oder mehrere Patches. Die entsprechende Windows Installer-Befehlszeile hat PATCH = \[msipatch.msp\]<; PatchGuid2> auf der Befehlszeile festgelegt. ### Parameter *\[; Update2.msp\]*

Parameters for Silent Installations
Parameter	Project Type	Description
/p"password"	Basic MSI, InstallScript MSI	If you configured the password-related settings for your release on the [Setup.exe tab in the Releases view](https://docs.revenera.com/installshield24helplib/helplibrary/ReleaseGridSetupTab.htm#ref-views_590435047_setupexetab), the end user must specify the password with the /p option when running the installation silently. A typical command is as follows: Setup.exe /s /p"password"
/r	InstallScript, InstallScript MSI	Use this command line to run the installation in record mode. In order to run an InstallScript MSI or InstallScript installation in silent mode, you must first run Setup.exe with the /r option to generate a response file, which stores information about the data entered and options selected by the user at run time. Launching an InstallScript MSI or InstallScript installation with the /r parameter displays all the run-time dialogs and stores the data in a file called [Setup.iss](https://docs.revenera.com/installshield24helplib/helplibrary/CreatetheResponseFile.htm#buildingtestingdistributing_401868635_responsefile), created inside the system’s Windows folder. To specify an alternative response file name and location, use the /f1 option, described below. Basic MSI projects do not create or use a response file for silent installations.
/s	Basic MSI, InstallScript, InstallScript MSI	For an InstallScript MSI or InstallScript project, the command Setup.exe /s runs the installation in silent mode, by default based on the responses contained in a 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 option](https://docs.revenera.com/installshield24helplib/helplibrary/IHelpSetup_EXECmdLine.htm#ref-command-linetools_1056566962_wp1880f1param). The command Setup.exe /s also suppresses the Setup.exe initialization dialog for a Basic MSI installation, but it does not read a response file. To run a Basic MSI installation silently, use the following command line: Setup.exe /s /v/qn To specify the values of public properties for a silent Basic MSI installation, you can use a command such as the following one: Setup.exe /s /v"/qn INSTALLDIR=D:\\Destination" Note • Using this command-line parameter to launch an installation that includes an InstallShield prerequisite does not automatically run the prerequisite installation silently. You may also need to specify a valid silent command-line parameter for the InstallShield prerequisite in the Specify the command line for the application when the setup is running in silent mode setting on the [Application to Run tab](https://docs.revenera.com/installshield24helplib/helplibrary/UIRefPrereqEditor_AppRun.htm#ref-prereqeditor_1557969797_wp1702) in the InstallShield Prerequisite Editor. For more information, see [Specifying Command-Line Parameters for an InstallShield Prerequisite](https://docs.revenera.com/installshield24helplib/helplibrary/SetupPrereqEditorCmdLine.htm#definingprerequisites_1762175736_1033736).
/f1	InstallScript, InstallScript MSI	Using the /f1 option enables you to specify where the [response file](https://docs.revenera.com/installshield24helplib/helplibrary/CreatetheResponseFile.htm#buildingtestingdistributing_401868635_responsefile) is (or where it should be created) and what its name is, as in the following example: Setup.exe /s /f1"C:\\Temp\\Setup.iss" Specify an absolute path; using a relative path gives unpredictable results. The /f1 option is available both when creating a response file (with the /r option) and when using a response file (with the /s option).
/f2	InstallScript, InstallScript MSI	When running an InstallScript MSI or InstallScript installation in silent mode (using the /s option), the log file [Setup.log](https://docs.revenera.com/installshield24helplib/helplibrary/SetupLog.htm#buildingtestingdistributing_401868635_wp0794) is by default created in the same directory and with the same name (except for the extension) as the response file. The /f2 option enables you to specify an alternative log file location and file name, as in the following example: Setup.exe /s /f2"C:\\Setup.log" Specify an absolute path; using a relative path gives unpredictable results.

Parameters for Silent Installations

Parameter

Project Type

Description

/p"password"

Basic MSI, InstallScript MSI

If you configured the password-related settings for your release on the [Setup.exe tab in the Releases view](https://docs.revenera.com/installshield24helplib/helplibrary/ReleaseGridSetupTab.htm#ref-views_590435047_setupexetab), the end user must specify the password with the /p option when running the installation silently. A typical command is as follows: Setup.exe /s /p"password"

InstallScript, InstallScript MSI

Use this command line to run the installation in record mode. In order to run an InstallScript MSI or InstallScript installation in silent mode, you must first run Setup.exe with the /r option to generate a response file, which stores information about the data entered and options selected by the user at run time. Launching an InstallScript MSI or InstallScript installation with the /r parameter displays all the run-time dialogs and stores the data in a file called [Setup.iss](https://docs.revenera.com/installshield24helplib/helplibrary/CreatetheResponseFile.htm#buildingtestingdistributing_401868635_responsefile), created inside the system’s Windows folder. To specify an alternative response file name and location, use the /f1 option, described below. Basic MSI projects do not create or use a response file for silent installations.

Basic MSI, InstallScript, InstallScript MSI

For an InstallScript MSI or InstallScript project, the command Setup.exe /s runs the installation in silent mode, by default based on the responses contained in a 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 option](https://docs.revenera.com/installshield24helplib/helplibrary/IHelpSetup_EXECmdLine.htm#ref-command-linetools_1056566962_wp1880f1param). The command Setup.exe /s also suppresses the Setup.exe initialization dialog for a Basic MSI installation, but it does not read a response file. To run a Basic MSI installation silently, use the following command line: Setup.exe /s /v/qn To specify the values of public properties for a silent Basic MSI installation, you can use a command such as the following one: Setup.exe /s /v"/qn INSTALLDIR=D:\\Destination" Note • Using this command-line parameter to launch an installation that includes an InstallShield prerequisite does not automatically run the prerequisite installation silently. You may also need to specify a valid silent command-line parameter for the InstallShield prerequisite in the Specify the command line for the application when the setup is running in silent mode setting on the [Application to Run tab](https://docs.revenera.com/installshield24helplib/helplibrary/UIRefPrereqEditor_AppRun.htm#ref-prereqeditor_1557969797_wp1702) in the InstallShield Prerequisite Editor. For more information, see [Specifying Command-Line Parameters for an InstallShield Prerequisite](https://docs.revenera.com/installshield24helplib/helplibrary/SetupPrereqEditorCmdLine.htm#definingprerequisites_1762175736_1033736).

/f1

InstallScript, InstallScript MSI

Using the /f1 option enables you to specify where the [response file](https://docs.revenera.com/installshield24helplib/helplibrary/CreatetheResponseFile.htm#buildingtestingdistributing_401868635_responsefile) is (or where it should be created) and what its name is, as in the following example: Setup.exe /s /f1"C:\\Temp\\Setup.iss" Specify an absolute path; using a relative path gives unpredictable results. The /f1 option is available both when creating a response file (with the /r option) and when using a response file (with the /s option).

/f2

InstallScript, InstallScript MSI

When running an InstallScript MSI or InstallScript installation in silent mode (using the /s option), the log file [Setup.log](https://docs.revenera.com/installshield24helplib/helplibrary/SetupLog.htm#buildingtestingdistributing_401868635_wp0794) is by default created in the same directory and with the same name (except for the extension) as the response file. The /f2 option enables you to specify an alternative log file location and file name, as in the following example: Setup.exe /s /f2"C:\\Setup.log" Specify an absolute path; using a relative path gives unpredictable results.

Parameters for Special Installation Modes
Parameter	Project Type	Description
/a	Basic MSI, InstallScript MSI	Note • The /a parameter does not work with Update.exe. Update.exe launches a patch that accesses and modifies an existing cached .msi file on the system, and an administrative installation does not cache the .msi file. The /a option causes Setup.exe to perform an administrative installation. An administrative installation copies (and uncompresses) your data files to a directory that is specified by the user, but it does not create shortcuts, register COM servers, or create an uninstallation log. Tip • If an installation contains InstallShield prerequisites and you want to extract them from Setup.exe, add a path after the /a parameter to extract the prerequisites to that location. A sample command is Setup.exe /a"C:\\temp".
/j	Basic MSI, InstallScript MSI	The /j option causes Setup.exe to perform an advertised 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 “entry points.”
/x	Basic MSI, InstallScript MSI	The /x option causes Setup.exe to uninstall a previously installed product.
/uninst	InstallScript, InstallScript MSI (if the InstallScript user interface (UI) style is the traditional style, which uses the InstallScript engine as an external UI handler)	Important • This parameter does not apply to InstallScript MSI projects in which the InstallScript UI style is the new style (which uses the InstallScript engine as an embedded UI handler). To learn more, see [Using the InstallScript Engine as an External vs. Embedded UI Handler for InstallScript MSI Installations](https://docs.revenera.com/installshield24helplib/helplibrary/ISMSIExternalVsEmbedded.htm#specifyinginstallationinfo_3107009874_1037936). The /uninst option is provided for compatibility with earlier versions of InstallShield. This option causes the InstallScript engine to execute the event handler function OnUninstall, whose default code uninstalls the previously installed product. Project • Note that in InstallScript MSI installations, the /uninst parameter does not invoke the InstallScript engine uninstall behavior that processes install log and removes any resources that were created and logged through script. However, the /removeonly option does invoke this behavior.
/removeonly	InstallScript, InstallScript MSI	The /removeonly option sets the REMOVEONLY system variable equal to a non-zero value. The default code for the OnMaintUIBefore event handler function conditionally displays the SdWelcomeMaint dialog, depending on the value of REMOVEONLY.
/instance=<InstanceId>	Basic MSI	The /instance=<InstanceId> option—which is available for [Basic MSI projects that support the installation of multiple instances of a product](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInstance.htm#installingmultipleinstances_1315909768_wp1008)—lets you specify which instance you want to install, update, or uninstall. <InstanceId> represents the value of the InstanceId property that identifies the instance. Whenever you use this option and include a valid InstanceId value, the installation suppresses the instance selection dialog. For example, the following sample command line installs the instance that has 2 as the value of the InstanceId property: Setup.exe /instance=2 Use default to identify the instance that is installed by the base installation package, as in the following example: Setup.exe /instance=default To specify the instance that you want to uninstall, include the /x option with the /instance=<InstanceId> option. For more information, see [Naming an Instance](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInst-Name.htm#installingmultipleinstances_1315909768_1026658) and [Run-Time Behavior for Installing Multiple Instances of a Product](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInst-RunTime.htm#installingmultipleinstances_1315909768_1025924).

Parameters for Special Installation Modes

Parameter

Project Type

Description

Basic MSI, InstallScript MSI

Note • The /a parameter does not work with Update.exe. Update.exe launches a patch that accesses and modifies an existing cached .msi file on the system, and an administrative installation does not cache the .msi file. The /a option causes Setup.exe to perform an administrative installation. An administrative installation copies (and uncompresses) your data files to a directory that is specified by the user, but it does not create shortcuts, register COM servers, or create an uninstallation log. Tip • If an installation contains InstallShield prerequisites and you want to extract them from Setup.exe, add a path after the /a parameter to extract the prerequisites to that location. A sample command is Setup.exe /a"C:\\temp".

Basic MSI, InstallScript MSI

The /j option causes Setup.exe to perform an advertised 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 “entry points.”

Basic MSI, InstallScript MSI

The /x option causes Setup.exe to uninstall a previously installed product.

/uninst

InstallScript, InstallScript MSI (if the InstallScript user interface (UI) style is the traditional style, which uses the InstallScript engine as an external UI handler)

Important • This parameter does not apply to InstallScript MSI projects in which the InstallScript UI style is the new style (which uses the InstallScript engine as an embedded UI handler). To learn more, see [Using the InstallScript Engine as an External vs. Embedded UI Handler for InstallScript MSI Installations](https://docs.revenera.com/installshield24helplib/helplibrary/ISMSIExternalVsEmbedded.htm#specifyinginstallationinfo_3107009874_1037936). The /uninst option is provided for compatibility with earlier versions of InstallShield. This option causes the InstallScript engine to execute the event handler function OnUninstall, whose default code uninstalls the previously installed product. Project • Note that in InstallScript MSI installations, the /uninst parameter does not invoke the InstallScript engine uninstall behavior that processes install log and removes any resources that were created and logged through script. However, the /removeonly option does invoke this behavior.

/removeonly

InstallScript, InstallScript MSI

The /removeonly option sets the REMOVEONLY system variable equal to a non-zero value. The default code for the OnMaintUIBefore event handler function conditionally displays the SdWelcomeMaint dialog, depending on the value of REMOVEONLY.

/instance=<InstanceId>

Basic MSI

The /instance=<InstanceId> option—which is available for [Basic MSI projects that support the installation of multiple instances of a product](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInstance.htm#installingmultipleinstances_1315909768_wp1008)—lets you specify which instance you want to install, update, or uninstall. <InstanceId> represents the value of the InstanceId property that identifies the instance. Whenever you use this option and include a valid InstanceId value, the installation suppresses the instance selection dialog. For example, the following sample command line installs the instance that has 2 as the value of the InstanceId property: Setup.exe /instance=2 Use default to identify the instance that is installed by the base installation package, as in the following example: Setup.exe /instance=default To specify the instance that you want to uninstall, include the /x option with the /instance=<InstanceId> option. For more information, see [Naming an Instance](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInst-Name.htm#installingmultipleinstances_1315909768_1026658) and [Run-Time Behavior for Installing Multiple Instances of a Product](https://docs.revenera.com/installshield24helplib/helplibrary/MultipleInst-RunTime.htm#installingmultipleinstances_1315909768_1025924).

Parameters for Passing Data to the Installation
Parameter	Project Type	Description
/v	Basic MSI, InstallScript MSI	Use the /v option to pass command-line options and values of public properties through to Msiexec.exe. If you want to pass more than one argument to Msiexec.exe, you can use the /v option multiple times at the command line, once for each argument. For example: Setup.exe /v"/l\v c:\\test.log" /v"MYPROPERTY1=value1" /v"/qb" As an alternative, you can pass multiple arguments through the /v option as in the following example: Setup.exe /v"/l\v c:\\test.log MYPROPERTY1=value1 /qb" Note • If you pass the /v parameter at the command prompt when launching Setup.exe, any parameters that are specified for the CmdLine keyname in Setup.ini are ignored. To learn more, see [Setup.ini](https://docs.revenera.com/installshield24helplib/helplibrary/SetupIni.htm#buildingtestingdistributing_401868635_1023968).
/v"ISSCRIPTCMDLINE=\\"<Option1> <Option2>\\""	Basic MSI projects that have InstallScript custom actions	This option specifies command-line parameters to be passed to the script. Any property supported by InstallScript MSI (where appropriate) can be specified. (The most common ones are /d and /z.) For example, the following indicates that you want to debug the script, and that the CMDLINE variable should contain TEST. Setup.exe /v"ISSCRIPTCMDLINE=\\"-d -zTEST\\"" Note that as shown above, when you want to specify that a double quote character is not a delimiter for the command line but a delimiter for the property, use \\". Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters.
/z	InstallScript MSI	The /z option is used to pass data to the InstallScript system variable [CMDLINE](https://docs.revenera.com/installshield24helplib/Subsystems/LangRef/helplibrary/LangrefCMDLINE.htm), as in the following example: Setup.exe /z"My Custom Data" When this command line is used, the variable CMDLINE contains the string My Custom Data.

Parameters for Passing Data to the Installation

Parameter

Project Type

Description

Basic MSI, InstallScript MSI

Use the /v option to pass command-line options and values of public properties through to Msiexec.exe. If you want to pass more than one argument to Msiexec.exe, you can use the /v option multiple times at the command line, once for each argument. For example: Setup.exe /v"/l\*v c:\\test.log" /v"MYPROPERTY1=value1" /v"/qb" As an alternative, you can pass multiple arguments through the /v option as in the following example: Setup.exe /v"/l\*v c:\\test.log MYPROPERTY1=value1 /qb" Note • If you pass the /v parameter at the command prompt when launching Setup.exe, any parameters that are specified for the CmdLine keyname in Setup.ini are ignored. To learn more, see [Setup.ini](https://docs.revenera.com/installshield24helplib/helplibrary/SetupIni.htm#buildingtestingdistributing_401868635_1023968).

/v"ISSCRIPTCMDLINE=\\"<Option1> <Option2>\\""

Basic MSI projects that have InstallScript custom actions

This option specifies command-line parameters to be passed to the script. Any property supported by InstallScript MSI (where appropriate) can be specified. (The most common ones are /d and /z.) For example, the following indicates that you want to debug the script, and that the CMDLINE variable should contain TEST. Setup.exe /v"ISSCRIPTCMDLINE=\\"-d -zTEST\\"" Note that as shown above, when you want to specify that a double quote character is not a delimiter for the command line but a delimiter for the property, use \\". Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters.

InstallScript MSI

The /z option is used to pass data to the InstallScript system variable [CMDLINE](https://docs.revenera.com/installshield24helplib/Subsystems/LangRef/helplibrary/LangrefCMDLINE.htm), as in the following example: Setup.exe /z"My Custom Data" When this command line is used, the variable CMDLINE contains the string My Custom Data.

Parameters for Download and Cache Locations
Parameter	Project Type	Description
/ua /uw	Basic MSI, InstallScript MSI	In the Release Wizard, you can specify download locations for the Windows Installer installers InstMsiA.exe and InstMsiW.exe. A user can specify an alternative URL at run time using the /ua option (for the InstMsiA.exe location) and /uw option (for the InstMsiW.exe location), as in the following example: Setup.exe /uw"http://www.otherlocation.com/engines" The file name is not necessary. Note • You must specify the full URL with the parameters.
/um	Basic MSI, InstallScript MSI	In the Release Wizard, for a Web Downloader build, you can specify a [download location](https://docs.revenera.com/installshield24helplib/helplibrary/IWPReleaseDownloaderOptions.htm#ref-wizardsn-z_2350463954_wp1477) for your .msi database. A user can specify an alternative URL using the /um option, as in the following example: Setup.exe /um"http://www.otherlocation.com/packages/product.msi" Note • You must specify the full URL with the parameter.
/b	Basic MSI, InstallScript MSI	In the Release Wizard, for a Downloader build, you can specify whether to cache the contents of a compressed package on the local system. With the /b option, the user can specify the directory in which to cache the installation files, as in the following example: Setup.exe /b"C:\\CacheDirectory" Note • You must specify the full URL with the parameter.

Parameters for Download and Cache Locations

Parameter

Project Type

Description

/ua /uw

Basic MSI, InstallScript MSI

In the Release Wizard, you can specify download locations for the Windows Installer installers InstMsiA.exe and InstMsiW.exe. A user can specify an alternative URL at run time using the /ua option (for the InstMsiA.exe location) and /uw option (for the InstMsiW.exe location), as in the following example: Setup.exe /uw"http://www.otherlocation.com/engines" The file name is not necessary. Note • You must specify the full URL with the parameters.

/um

Basic MSI, InstallScript MSI

In the Release Wizard, for a Web Downloader build, you can specify a [download location](https://docs.revenera.com/installshield24helplib/helplibrary/IWPReleaseDownloaderOptions.htm#ref-wizardsn-z_2350463954_wp1477) for your .msi database. A user can specify an alternative URL using the /um option, as in the following example: Setup.exe /um"http://www.otherlocation.com/packages/product.msi" Note • You must specify the full URL with the parameter.

Basic MSI, InstallScript MSI

In the Release Wizard, for a Downloader build, you can specify whether to cache the contents of a compressed package on the local system. With the /b option, the user can specify the directory in which to cache the installation files, as in the following example: Setup.exe /b"C:\\CacheDirectory" Note • You must specify the full URL with the parameter.

Parameters for Debugging
Parameter	Project Type	Description
/d	Basic MSI projects with InstallScript custom actions, InstallScript, InstallScript MSI	For an InstallScript project, running the command Setup.exe /d runs the installation program with the InstallScript Debugger. Note • Debugging InstallScript code requires the debug-information file Setup.dbg to be available. In addition, in order to debug an installation on a system other than your development machine, you need to copy certain files from your development machine to the debugging machine. To learn more, see [Debugging an Installation on Any Computer](https://docs.revenera.com/installshield24helplib/Subsystems/ISdbg/helplibrary/DebuggingInstall-AnyComputer.htm). For a Basic MSI project, the following command runs your InstallScript custom actions in the InstallScript Debugger: Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\\"path-to-Setup.dbg\\""
/debuglog	Basic MSI, InstallScript MSI	The /debuglog parameter lets you generate a log file for Setup.exe. To generate a log named InstallShield.log in the same directory as the Setup.exe file, pass just the command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location. For example: setup.exe /debuglog To specify the name and location of the log file, pass the path and name, as in the following example: Setup.exe /debuglog"C:\\PathToLog\\setupexe.log" To generate a log file for the feature prerequisites in the installation, use the /v parameter to set the ISDEBUGLOG property to the full path and file name for the log file, as follows: Setup.exe /debuglog"C:\\PathToSetupLogFile\\setup.log" /v"ISDEBUGLOG=prereq.log" You can use directory properties and environment variables in the path for the feature prerequisite log file.

Parameters for Debugging

Parameter

Project Type

Description

Basic MSI projects with InstallScript custom actions, InstallScript, InstallScript MSI

For an InstallScript project, running the command Setup.exe /d runs the installation program with the InstallScript Debugger. Note • Debugging InstallScript code requires the debug-information file Setup.dbg to be available. In addition, in order to debug an installation on a system other than your development machine, you need to copy certain files from your development machine to the debugging machine. To learn more, see [Debugging an Installation on Any Computer](https://docs.revenera.com/installshield24helplib/Subsystems/ISdbg/helplibrary/DebuggingInstall-AnyComputer.htm). For a Basic MSI project, the following command runs your InstallScript custom actions in the InstallScript Debugger: Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\\"path-to-Setup.dbg\\""

/debuglog

Basic MSI, InstallScript MSI

The /debuglog parameter lets you generate a log file for Setup.exe. To generate a log named InstallShield.log in the same directory as the Setup.exe file, pass just the command-line parameter. Note that this does not work if the Setup.exe file is in a read-only location. For example: setup.exe /debuglog To specify the name and location of the log file, pass the path and name, as in the following example: Setup.exe /debuglog"C:\\PathToLog\\setupexe.log" To generate a log file for the feature prerequisites in the installation, use the /v parameter to set the ISDEBUGLOG property to the full path and file name for the log file, as follows: Setup.exe /debuglog"C:\\PathToSetupLogFile\\setup.log" /v"ISDEBUGLOG=prereq.log" You can use directory properties and environment variables in the path for the feature prerequisite log file.

Parameters for SMS Data
Parameter	Project Type	Description
/m	InstallScript, InstallScript MSI	The /m option causes Setup.exe to generate an SMS Management Information Format (.mif) file. Following is a typical command: Setup.exe /m"SampleApp" Including the “.mif” file extension is not necessary.
/m1	InstallScript, InstallScript MSI	Using the /m1 parameter (along with /m) enables you to specify a serial number to be written to the .mif file. A typical command is as follows: Setup.exe /m"SampleApp" /m1"1234-5678"
/m2	InstallScript, InstallScript MSI	Using the /m2 parameter (along with /m) enables you to specify a locale string to be written to the .mif file. A typical command is as follows: Setup.exe /m"SampleApp" /m2"ENU"

Parameters for SMS Data

Parameter

Project Type

Description

InstallScript, InstallScript MSI

The /m option causes Setup.exe to generate an SMS Management Information Format (.mif) file. Following is a typical command: Setup.exe /m"SampleApp" Including the “.mif” file extension is not necessary.

/m1

InstallScript, InstallScript MSI

Using the /m1 parameter (along with /m) enables you to specify a serial number to be written to the .mif file. A typical command is as follows: Setup.exe /m"SampleApp" /m1"1234-5678"

/m2

InstallScript, InstallScript MSI

Using the /m2 parameter (along with /m) enables you to specify a locale string to be written to the .mif file. A typical command is as follows: Setup.exe /m"SampleApp" /m2"ENU"

Parameters for Minimum UI
Parameter	Project Type	Description
/passive	Advanced UI, Suite/Advanced UI	Use the /passive parameter to runs a suite installer setup in a minimum UI mode (just displaying a progress panel): Setup.exe /passive To uninstall using a minimum UI mode, use the following command: Setup.exe /passive /remove

Parameters for Minimum UI

Parameter

Project Type

Description

/passive

Advanced UI, Suite/Advanced UI

Use the /passive parameter to runs a suite installer setup in a minimum UI mode (just displaying a progress panel): Setup.exe /passive To uninstall using a minimum UI mode, use the following command: Setup.exe /passive /remove

[![image.png](https://bst.wkmimnl.de/uploads/images/gallery/2025-06/scaled-1680-/V3Bimage.png)](https://bst.wkmimnl.de/uploads/images/gallery/2025-06/V3Bimage.png)