Crossover Install Msi File

  • Where msi-filepath is the full path (including the file name) to the file you extracted in steps 2-3 and log-filepath is the full path (also including the file name) to the log file you want to save the output to (!) The /i and /l.v parameters are separated with spaces from msiexec and msi-filepath. For example, msiexec /i D: AcronisFolder.
  • Choose a different folder to install the app using a command line parameter. For example: msiexec /i c: work Webex.msi INSTALLROOT='C: Program Files' ALLUSERS=1. By default, when you run the installer to update the Webex app, any user database or log files are retained.
-->

Provides the means to install, modify, and perform operations on Windows Installer from the command line.

Install options

CrossOver detects the install disk if you've mounted it. If you've got a.exe installer, click Choose Installer File and select the correct file. In my case, it detected the disk. CrossOver shows you a summary of the actions. CrossOver starts installing required applications and fonts, like Arial and the MSXML.

See Full List On Docs.microsoft.com

Set the install type for launching an installation package.

Most of the time, all you need to do is download the CrossOver installer package and double-click on it. Be sure to select the appropriate package, 32 or 64-bit. When you double-click on the downloaded file, it will launch the Ubuntu software center (the default package manager.). Before proceeding with installation, verify that the installer (.MSI file) has been digitally signed by DoD PKE Engineering. Use the following steps to verify the digital signature: 1) In Windows Explorer, navigate to the directory containing the InstallRootv5.2.msi, InstallRootv5.2x64.msi, or InstallRootv5.2-NonAdmin.msi.

How to install Windows 10? - MSI

Syntax

Parameters

ParameterDescription
/iSpecifies normal installation.
/aSpecifies administrative installation.
/juAdvertise the product to the current user.
/jmAdvertise the product to all users.
/j/gSpecifies the language identifier used by the advertised package.
/j/tApplies transform to the advertised package.
/xUninstalls 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:

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.

Crossover Install Msi File

Syntax

Parameters

ParameterDescription
<path_to_package>Specifies the location and name of the installation package file.
/quietSpecifies quiet mode, which means there's no user interaction required.
/passiveSpecifies unattended mode, which means the installation only shows a progress bar.
/qnSpecifies 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.
/qbSpecifies 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.
/qrSpecifies a reduced UI experience during the installation process.
/qfSpecifies 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:

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.

Crossover Install Msi File

Syntax

Parameters

ParameterDescription
<path_to_package>Specifies the location and name of the installation package file.
/norestartStops the device from restarting after the installation completes.
/promptrestartPrompts the user if a reboot is required.
/forcerestartRestarts 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:

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

ParameterDescription
/iSpecifies normal installation.
/xUninstalls the package.
<path_to_package>Specifies the location and name of the installation package file.
/liTurns on logging and includes status messages in the output log file.
/lwTurns on logging and includes non-fatal warnings in the output log file.
/leTurns on logging and includes all error messages in the output log file.
/laTurns on logging and includes information about when an action started in the output log file.
/lrTurns on logging and includes action-specific records in the output log file.
/luTurns on logging and includes user request information in the output log file.
/lcTurns on logging and includes the initial UI parameters in the output log file.
/lmTurns on logging and includes out-of-memory or fatal exit information in the output log file.
/loTurns on logging and includes out-of-disk-space messages in the output log file.
/lpTurns on logging and includes terminal properties in the output log file.
/lpTurns on logging and includes terminal properties in the output log file.
/lvTurns on logging and includes verbose output in the output log file.
/lpTurns on logging and includes terminal properties in the output log file.
/lxTurns 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:

Update options

Command-Line Syntax Key

You can apply or remove updates using an installation package.

Syntax

Parameters

ParameterDescription
/pInstalls 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.
/updateInstall patches option. If you're applying multiple updates, you must separate them using a semi-colon (;).
/packageInstalls or configures a product.

Examples

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

Parameters

ParameterDescription
/fpRepairs the package if a file is missing.
/foRepairs the package if a file is missing, or if an older version is installed.
/feRepairs the package if file is missing, or if an equal or older version is installed.
/fdRepairs the package if file is missing, or if a different version is installed.
/fcRepairs the package if file is missing, or if checksum does not match the calculated value.
/faForces all files to be reinstalled.
/fuRepairs all the required user-specific registry entries.
/fmRepairs all the required computer-specific registry entries.
/fsRepairs all existing shortcuts.
/fvRuns 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:

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.

Additional References