Purpose

This document provides steps on how to obtain a verbose logging output from any .msi package which may assist in troubleshooting installation failures.

Symptoms

This may be useful when patches failing to install throw a generic 1603 return code.

Description

To obtain verbose logging from the .msi package:

On the system where the update is failing to install:

1) Open command prompt.

2) Change directories to the location of the .msi file.

3) Use the following command (replacing Example.msi with your msi file name):

msiexec /i Example.msi /L*vx "C:\folder\ExampleLogFilename.txt"

Or to run this without user interaction:

msiexec /i Example.msi /quiet /L*vx "C:\folder\ExampleLogFilename.txt"

The log file will be generated with the name specified within the folder specified. Review this log or send to support.

Note: This command will also run with .EXE and .MSU packages, however, it will not provide the same level of output.

Additional Information

For more information about MSIEXEC command line options, see the following Microsoft KB article:

Msiexec (command-line options)

Affected Product(s)

Shavlik Protect 9.x