Some application packages have unique exit codes, which are described in the application package catalog . In general, 100-199 are prerequisite failures 200-299 are installation failures, and 300-399 are validation failures. Code Description 0 The package ran successfully 100 Unsupported OS version 101 Unsupported OS architecture 102 Invalid verbosity mode 104 Aborting installation; unsafe conditions 105 Invalid command line argument 106 Unsupported hardware 195 Cannot find license file 196 Invalid license file 197 Invalid license file 198 Unauthorized computer or network 199 The license has expired 200 Failed to run the installer 201 Failed to extract the answer file 202 Failed to cache the package to the local disk 203 Failed to extract the installer 271 Failed to find the font directory 272 Failed to find a valid font 273 Failed to build a list of font files 274 Failed to create the temp directory 275 Failed to extract the font installer 276 Failed to run the font installer 277 Failed to install one or more fonts 280 File extraction error: The specified archive file does not exist 281 File extraction error: Unable to delete the extraction directory 282 File extraction error: Unable to create the extraction directory 283 File extraction error: Failed to run the extraction tool 284 File extraction error: One or more files were not extracted 285 File extraction error: Fatal error 286 File extraction error: Command line error 287 File extraction error: Not enough memory for operation 288 File extraction error: User stopped the process 289 File extraction error: Unknown error 3017 A restart is required before installing Microsoft Installer (MSI) exit codes are described below. Source: https://docs.microsoft.com/en-us/windows/desktop/Msi/error-codes Code Description 0 ERROR_ SUCCESS The action completed successfully. 13 ERROR_ INVALID_ DATA The data is invalid. 87 ERROR_ INVALID_ PARAMETER One of the parameters was invalid. 120 ERROR_ CALL_ NOT_ IMPLEMENTED This value is returned when a custom action attempts to call a function that cannot be called from custom actions. The function returns the value ERROR_ CALL_ NOT_ IMPLEMENTED. Available beginning with Windows Installer version 3.0. 1259 ERROR_ APPHELP_ BLOCK If Windows Installer determines a product may be incompatible with the current operating system, it displays a 1601 ERROR_ INSTALL_ SERVICE_ FAILURE The Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered. 1602 ERROR_ INSTALL_ USEREXIT The user cancels installation. 1603 ERROR_ INSTALL_ FAILURE A fatal error occurred during installation. 1604 ERROR_ INSTALL_ SUSPEND Installation suspended, incomplete. 1605 ERROR_ UNKNOWN_ PRODUCT This action is only valid for products that are currently installed. 1606 ERROR_ UNKNOWN_ FEATURE The feature identifier is not registered. 1607 ERROR_ UNKNOWN_ COMPONENT The component identifier is not registered. 1608 ERROR_ UNKNOWN_ PROPERTY This is an unknown property. 1609 ERROR_ INVALID_ HANDLE_ STATE The handle is in an invalid state. 1610 ERROR_ BAD_ CONFIGURATION The configuration data for this product is corrupt. Contact your support personnel. 1611 ERROR_ INDEX_ ABSENT The component qualifier not present. 1612 ERROR_ INSTALL_ SOURCE_ ABSENT The installation source for this product is not available. Verify that the source exists and that you can access it. 1613 ERROR_ INSTALL_ PACKAGE_ VERSION This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. 1614 ERROR_ PRODUCT_ UNINSTALLED The product is uninstalled. 1615 ERROR_ BAD_ QUERY_ SYNTAX The SQL query syntax is invalid or unsupported. 1616 ERROR_ INVALID_ FIELD The record field does not exist. 1618 ERROR_ INSTALL_ ALREADY_ RUNNING Another installation is already in progress. Complete that installation before proceeding with this install.For information about the mutex, see _ MSIExecute Mutex . 1619 ERROR_ INSTALL_ PACKAGE_ OPEN_ FAILED This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package. 1620 ERROR_ INSTALL_ PACKAGE_ INVALID This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. 1621 ERROR_ INSTALL_ UI_ FAILURE There was an error starting the Windows Installer service user interface. Contact your support personnel. 1622 ERROR_ INSTALL_ LOG_ FAILURE There was an error opening installation log file. Verify that the specified log file location exists and is writable. 1623 ERROR_ INSTALL_ LANGUAGE_ UNSUPPORTED This language of this installation package is not supported by your system. 1624 ERROR_ INSTALL_ TRANSFORM_ FAILURE There was an error applying transforms. Verify that the specified transform paths are valid. 1625 ERROR_ INSTALL_ PACKAGE_ REJECTED This installation is forbidden by system policy. Contact your system administrator. 1626 ERROR_ FUNCTION_ NOT_ CALLED The function could not be executed. 1627 ERROR_ FUNCTION_ FAILED The function failed during execution. 1628 ERROR_ INVALID_ TABLE An invalid or unknown table was specified. 1629 ERROR_ DATATYPE_ MISMATCH The data supplied is the wrong type. 1630 ERROR_ UNSUPPORTED_ TYPE Data of this type is not supported. 1631 ERROR_ CREATE_ FAILED The Windows Installer service failed to start. Contact your support personnel. 1632 ERROR_ INSTALL_ TEMP_ UNWRITABLE The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it. 1633 ERROR_ INSTALL_ PLATFORM_ UNSUPPORTED This installation package is not supported on this platform. Contact your application vendor. 1634 ERROR_ INSTALL_ NOTUSED Component is not used on this machine. 1635 ERROR_ PATCH_ PACKAGE_ OPEN_ FAILED This patch package could not be opened. Verify that the patch package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer patch package. 1636 ERROR_ PATCH_ PACKAGE_ INVALID This patch package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer patch package. 1637 ERROR_ PATCH_ PACKAGE_ UNSUPPORTED This patch package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. 1638 ERROR_ PRODUCT_ VERSION Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs in Control Panel . 1639 ERROR_ INVALID_ COMMAND_ LINE Invalid command line argument. Consult the Windows Installer SDK for detailed command-line help. 1640 ERROR_ INSTALL_ REMOTE_ DISALLOWED The current user is not permitted to perform installations from a client session of a server running the Terminal Server role service. 1641 ERROR_ SUCCESS_ REBOOT_ INITIATED The installer has initiated a restart. This message is indicative of a success. 1642 ERROR_ PATCH_ TARGET_ NOT_ FOUND The installer cannot install the upgrade patch because the program being upgraded may be missing or the upgrade patch updates a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch. 1643 ERROR_ PATCH_ PACKAGE_ REJECTED The patch package is not permitted by system policy. 1644 ERROR_ INSTALL_ TRANSFORM_ REJECTED The patch package is not permitted by system policy. 1645 ERROR_ INSTALL_ REMOTE_ PROHIBITED Windows Installer does not permit installation from a Remote Desktop Connection. 1646 ERROR_ PATCH_ REMOVAL_ UNSUPPORTED The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0. 1647 ERROR_ UNKNOWN_ PATCH The patch is not applied to this product. Available beginning with Windows Installer version 3.0. 1648 ERROR_ PATCH_ NO_ SEQUENCE No valid sequence could be found for the set of patches. Available beginning with Windows Installer version 3.0. 1649 ERROR_ PATCH_ REMOVAL_ DISALLOWED Patch removal was disallowed by policy. Available beginning with Windows Installer version 3.0. 1650 ERROR_ INVALID_ PATCH_ XML The XML patch data is invalid. Available beginning with Windows Installer version 3.0. 1651 ERROR_ PATCH_ MANAGED_ ADVERTISED_ PRODUCT Administrative user failed to apply patch for a per-user managed or a per-machine application that is in advertise state. Available beginning with Windows Installer version 3.0. 1652 ERROR_ INSTALL_ SERVICE_ SAFEBOOT Windows Installer is not accessible when the computer is in Safe Mode. Exit Safe Mode and try again or try using System Restore to return your computer to a previous state. Available beginning with Windows Installer version 4.0. 1653 ERROR_ ROLLBACK_ DISABLED Could not perform a multiple-package transaction because rollback has been disabled. Multiple-Package Installations cannot run if rollback is disabled. Available beginning with Windows Installer version 4.5. 1654 ERROR_ INSTALL_ REJECTED The app that you are trying to run is not supported on this version of Windows. A Windows Installer package, patch, or transform that has not been signed by Microsoft cannot be installed on an ARM computer. 3010 ERROR_ SUCCESS_ REBOOT_ REQUIRED A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run.

FAQs Archive

How to receive RSS update notifications for new packages and more

Subscribe to our RSS feeds to receive updates for packages, OS builds, and more. On Windows machines, click one of the following links to subscribe with Outlook or your default RSS reader All categories: feeds://www.meetaiden.com/feed/ Packages: feeds://www.meetaiden.com/feed/?post_type=application_package OS builds: feeds://www.meetaiden.com/feed/?post_type=os_build For all other platforms, copy one of the following URLs into your RSS reader [Read More]

Sean Maloney2020-10-15T15:02:36-07:00October 6th, 2020|

Exit Codes

Some application packages have unique exit codes, which are described in the application package catalog. In general, 100-199 are prerequisite failures 200-299 are installation failures, and 300-399 are validation failures. Code Description 0 The package ran successfully 100 Unsupported OS version 101 Unsupported OS architecture 102 Invalid verbosity mode 104 Aborting installation; unsafe conditions 105 [Read More]

aiden2020-10-14T16:18:02-07:00October 6th, 2020|

How to boot from a USB device or optical media

When you can’t PXE boot (network boot) because a DHCP relay hasn’t been configured, or because your device doesn’t have an Ethernet adapter, the next best way to set up a PC or server is with a bootable USB device. Create a bootable USB Flash Drive Insert a USB flash drive that is OK to [Read More]

Sean Maloney2020-10-14T17:49:38-07:00October 6th, 2020|

How to customize start panel layouts for Windows 10

Your aiden Windows 10 builds include a custom Start Panel layout, but you may supply your own layout for any or all Windows 10 builds, by emailing an exported layout to our support staff. Exporting to an XML file On any Windows 10 PC, customize the Start Panel as desired. Then, open Windows PowerShell, Command [Read More]

Sean Maloney2020-10-14T17:49:38-07:00October 6th, 2020|

How to use the WIN32_MassDeploy WMI Class to target devices

The Win32_MassDeploy WMI class can be used to target devices in specific departments or pilot systems. This is especially useful for Group Policy targeting. Properties Name: ReleaseChannelType: stringRegistry path (32-bit): HKEY_LOCAL_MACHINE\SOFTWARE\MassDeploy|ReleaseChannelThis value is often set to "Pilot" while setting up a computer with an "IT" build, but it can also be set manually, or [Read More]

Sean Maloney2020-10-14T17:52:30-07:00October 6th, 2020|

How to analyze crash dumps / blue screens (BSOD)

BlueScreenView This simple free tool, will often find the driver that caused the crash. http://www.nirsoft.net/utils/blue_screen_view.html WinDbg When BlueScreenView does not provide enough information, Microsoft’s Debugging Tools may be needed. https://msdn.microsoft.com/en-US/library/windows/hardware/ff551063(v=vs.85).aspx Installation If you only want to install the Debugging Tools, run the Windows SDK installer, select the Debugging Tools for Windows box, and clear all the other [Read More]

Sean Maloney2020-10-14T17:49:38-07:00September 25th, 2020|