M100579: Behavior explanation: MSI LaunchCondition


Sometimes an MSI won't install despite the fact that privileges have been elevated and regardless of the deployment mechanism that is being used.

You have tried to package a MSI several different ways, including elevating privileges and deploying the package in the machine and user context but the install still fails.

A review of the launcher log file may show MSI return codes such as:

  • 1603 - Fatal error during installation.
  • 1605 - This action is only valid for products that are currently installed.
  • 1619 - This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.

This may be caused because the MSI has not been appropriately authored for packaging. To confirm if this is the case do the following:

  1. Open up the MSI in an MSI viewing tool.
  2. View the LaunchCondition table.
    Does the table contain any rows with the following condition:
    1. AdminUser OR ACTION~="ADMIN"
    2. (VersionNT AND AdminUser=1) or (Version9x)
    3. Version9X > 400 OR AdminUser
    4. Version9X > 400 OR VersionNT >= 400
  3. The LaunchCondition table for the description cell may also conain the following messages which indicate the MSI may not install:
    1. You must be logged in as an administrator to work with this installation program.
    2. This version of <software product> is designed for Windows NT 4.0 or later and cannot be installed on Windows NT 3.51 or Windows 95.

This problem may be resolved by:

  1. Contacting the supplier of the package and asking them to make an MSI available that doesn't have such conditions.
  2. Backing up a copy of the old MSI and creating a new MSI that changes the LaunchCondition table so that the MSI will install.

Additional Information

For more information on the MSI LaunchCondition table see the following:


Have more questions? Submit a request


Powered by Zendesk