Deployment Error Codes
You want to understand why the selected package returned an unsuccessful return code.
Prerequisites
Consult the documentation for the installer in question or reach out to the vendor to determine the meaning of the error code that was returned.
If the installer is a script file it may be due to a coding issue.
MSI Errors
Some EXE installers are wrapper applications that use Microsoft Installer (MSI) technology behind the scenes and may return MSI error codes. Because these codes can be used differently depending on the installer, PDQ does not automatically interpret them the same way it does when directly running MSI, MSP, or MSU installer files.
Below are some MSI error codes you may encounter when deploying EXE installers. This list is not exhaustive and covers only some of the more commonly seen codes. Please see Windows Installer Error Messages and System Error Codes (1300-1699)for more error codes.
- 1601 - Windows Installer Service could not be contacted
- 1602 - User Cancelled
- 1603 - Fatal Error
- 1605 - This action is only valid for products that are currently installed.
- 1618 - Another Installation Already In Progress
- 1619 - File Not Found
- 1620 - Cannot Open File
- 1622 - Error opening installation log file
- 1624 - There was an error applying transforms (Verify that the specified transform paths are valid.)
- 1632 - Temp folder full
- 1633 - Unsupported platform
- 1638 - Another version is already installed
- 1639 - Invalid command line option
- 1642 - Program being patched is not installed
- 1704 - An installation is currently suspended
- 17031 - Prerequisite missing for this installer
Other Common Errors
- 112 - There is not enough space on the disk.
- 4123 - Product already installed as an operating system component
- 5100 - General error with .NET installer
- 14098 (0x80073712 HRESULT)
ERROR_SXS_COMPONENT_STORE_CORRUPT- The Windows Component Store (WinSxS) is corrupted. - -2145124330 (0x80240016 HRESULT)
WU_E_INSTALL_NOT_ALLOWED- Operation tried to install while another installation was in progress or the system was pending a mandatory restart.
Wrapping up
Make changes as recommended by the creator of the installer.
The return code may not truly be an error, the deployment may still have succeeded as some installers return codes for purposes other than error conditions. If the return code is indicating a desired status it can be added to the Success Codes field in your Installer to mark future deployments of that package as successful.
