MSI Fatal Error - Error 1603

Description

A fatal error occurred in Microsoft Installer.

Possible Causes

A file that was needed for a successful installation was not found or was inaccessible.

Error 1603 is a catch-all error used by Microsoft Installer when an unexpected failure is encountered during an installation. Quite often this occurs when a file that is needed for an installation is not found (perhaps it was deleted by an antivirus solution, or it can't be accessed on a network share).

Pending Windows Update Reboot

 

The target computer may need to reboot after applying Windows updates. In these cases, Windows may not allow additional MSI installations until the target has rebooted.

Recommended Fixes

  • Verify that antivirus software isn't deleting the installation files while they're being copied to the %WINDIR%\AdminArsenal\PDQDeployRunner directory, which is the default working directory PDQ Deploy uses to stage and then execute the installation.
  • If multiple files are needed for installation (i.e. there are other files needed beyond the main installation .exe or .msi file) verify that your PDQ Deploy Package has the additional files either specified using the Additional Files drop down, or the option Include Entire Directory is checked. A tell-tale sign that this is your issue would be if the deployment is failing on all of your target computers. If the deployment is only failing on a few targets, then the 1603 is being caused by another issue. (see image below) 
    Additional Files field and Include Entire Directory highlighted in a PDQ Deploy Install Step.
  • Try uninstalling any previous versions of the application. It is possible that there is a corrupt installation on the target which is causing the 1603 error.
  • Try running the installation manually on the target computer. Doing this will often help isolate the cause of the 1603 error:
    1. Copy the installation file(s) or directory to a target throwing the 1603 error.
    2. Log in to the same target using the Deploy User credentials, or the Scan User credentials if you're using that option.
    3. Open an elevated command prompt and navigate to where you saved the file(s) or directory in step 1.
    4. In the command prompt, run the command from the Command Line section of the Install Step. If the installer is an .msi, replace the /qn switch with /qb so the installation displays a progress bar and any Windows Installer messages that may help identify the cause of the failure.
      MSI install command with /qn silent installation option highlighted.
    5. Check for errors, including in Event Viewer, and note any dialog boxes or other indicators of the referenced file. This should point you to the file that is causing the error.

See Also

Wayne Osteen
Updated
Was this article helpful?

Related articles