Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Patch Manager > Troubleshooting Microsoft Installer Error Messages and Failures

Troubleshooting Microsoft Installer Error Messages and Failures

Created by Seamus.Enright, last modified by MindTouch on Jun 23, 2016

Views: 906 Votes: 0 Revisions: 5


When you deploy an MSI package with Patch Manager and the installation fails, often it is an issue to troubleshoot at the installer level rather than the Patch Manager level. There are two approaches to troubleshoot MSI errors:


Patch Manager


Running the installer from the command line

When you run the installer from a command line interface (CLI), you mimic the Windows Update Agent and can observe exactly where and why the install fails.

To troubleshoot an installer from the CLI:

  1. Check your installer package in Patch Manager for the command line parameters it is using for the installer. For example, some packages use /a to run the installer as an administrator.
  2. If necessary, move the installer file to the client system. Generally, when the installer fails on a client system, the installer is still available since the client has already downloaded it.
  3. Open a Command Prompt (cmd.exe) on the client system.
  4. Change directories to the location of the installer, and then run the installer with the same command line parameters the package used. For example, for sample.msi with the command line parameter, /a, enter msiexec /a sample.msiNote: To run a Microsoft Installer from the CLI, you must start the command with msiexec.
  5. Watch the CLI output during the installation process. Look for specific errors or messages about where or why the installer failed.
  6. If possible, resolve the issue and re-try the installer.

Troubleshooting with MSI logging

Microsoft provides detailed instructions about how to enable MSI logging in the following KB article:

After you enable MSI logging, check the following common locations for the installer log and examine it for errors and information to help with troubleshooting:

  • %appdata%\local\temp
  • %windir%\temp
  • %ProgramFiles%\programName, where programName is the name of the program you are installing. In other words, the installation folder used by the MSI.


Last modified