/i <package> or <product code>

Use this format to install the product Othello:

msiexec /i 'C:InstallShield 2014 ProjectsOthelloTrial VersionReleaseDiskImagesDisk1Othello Beta.msi'

Product Code refers to the GUID that is automatically generated in the Product Code property of your product’s project view.

/f [p o e d c a u m s v] <package> or <product code>

Installing with the /f option will repair or reinstall missing or corrupted files.

For example, to force a reinstall of all files, use the following syntax:

msiexec /fa 'C:InstallShield 2014 ProjectsOthelloTrial VersionReleaseDiskImagesDisk1Othello Beta.msi'

Use the aforementioned syntax in conjunction with the following flags:

/a <package>

The /a option allows users with administrator privileges to install a product onto the network.

/x <package> or <product code>

The /x option uninstalls a product.

Project: For InstallScript MSI projects in which the InstallScript UI style is the new style (which uses the InstallScript engine as an embedded UI handler): If you try to uninstall the product through the command line using the statement Msiexec.exe /x {ProductCode}, the uninstallation may be successful. However, the Windows Installer displays an error dialog near the end of the uninstallation. The error dialog indicates that the Windows Installer service could not be accessed.

To perform an uninstallation from the command line in this scenario, the current recommended method is to use one of the following:

msiexec.exe /i {ProductCode} REMOVE=ALL

msiexec.exe /x {ProductCode} /qn

This is not necessary if your InstallScript MSI project is using the traditional style for the InstallScript UI (which uses the InstallScript engine as an external UI handler).

To learn more, see Using the InstallScript Engine as an External vs. Embedded UI Handler for InstallScript MSI Installations.

/j [u m] <package>

/j [u m] <package> /t <transform list>

/j [u m] <package> /g

/j <language ID>

Building with the /j <package> option advertises the components of your application on the end user’s computer

Transforms allow the synchronization of applications across different languages. For example, if you upgrade the English version of your product, you could apply a transform to automatically upgrade the French version of your product.

Use the /L option to specify the path to the log file. Optionally include one or more of the following flags to indicate which information to record in the log file:

For example, to generate a log file that logs everything verbosely, use the following:

/L*v 'C:MyLogFilespackage.log'

/p <patch package>

Use the /p option to apply a patch to an installed product. To patch an installed administrative image, combine this option with /a as shown:

/pPatchPackage /a Package

/q [n b r f]

The /q option is used to set the user interface level in conjunction with the following flags:

The following user interface settings display a modal dialog box at the end of installation:

/? or /h

Either command displays Windows Installer copyright information

/y <file name>

This command calls the DllRegisterServer entry-point function of the DLL or OCX file specified in <file name>.

/z <file name>

This command calls the DllUnregisterServer entry-point function of the DLL or OCX file specified in <file name>.

/n {product code}

The /n <product code> option is available for patches that are created in the Patch Design view for Basic MSI projects that support the installation of multiple instances of a product.

Use the /n option with the /p option to specify the product code of the instance to which you want to apply a patch. For example:

msiexec /p mypatch.msp /n {00000001-0002-0000-0000-624474736554}

TRANSFORMS

Use the TRANSFORMS command-line parameter to specify any transforms that you would like applied to your base package. Your transform command-line call might look something like this:

msiexec /i 'C:InstallShield 2014 ProjectsOthelloTrial VersionReleaseDiskImagesDisk1Othello.msi' TRANSFORMS='New Transform 1.mst'

You can separate multiple transforms with a semicolon. Because of this, it is recommended that you do not use semicolons in the name of your transform because the Windows Installer service will interpret those incorrectly.

Properties

All public properties can be set or modified from the command line. Public properties are distinguished from private properties by the fact that they are in all capital letters. For example, COMPANYNAME is a public property.

To set a property from the command line, use the following syntax: PROPERTY=VALUE. If you wanted to change the value of COMPANYNAME, you would enter:

msiexec /i 'C:InstallShield 2014 ProjectsOthelloTrial VersionReleaseDiskImagesDisk1Othello.msi' COMPANYNAME='My Software Company'

InstallShield 2014 Help Library

May 2014