Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Application installation common error codes reference
In this articleApplications can be installed on clients by creating deployments from the Configuration Manager console or by targeting applications to tenant attached devices from the Microsoft Endpoint Manager admin center. Use the information in this article to assist with troubleshooting application installation errors. General troubleshooting tipsGenerally, if an application installs successfully on a device with the given command line in the system context, it will install successfully through Configuration Manager and from the Microsoft Endpoint Manager admin center. You can simulate this by using PSExec.
You may also find that searching through multiple files for a specific string is useful. For instance, you might want to search all the client
Configuration Manager errors
General Configuration Manager troubleshooting tipsWhen an application fails to install and the error source is Configuration Manager, typically, following the application troubleshooting guide and using the general troubleshooting tips helps you resolve the error. You may also want to use Support Center for Configuration Manager to help troubleshoot and review information about your clients. 0x87D00202Message: Service is shutting down Additional information for error resolution: Verify that the Configuration Manager client is running on the target device. Verify the client is running by:
0x87D00207Message: Parsing error Additional information for error resolution: This error generally occurs in one of the Configuration Manager components when a piece of data is invalid. This error could stem from something missing for the application, an old package version, or a number of other general errors. Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips. 0x87D00213Message: Timeout occurred Additional information for error resolution: Increase the Maximum allowed run time (minutes) for the application. Ensure that the maintenance window on the client is large enough to support the runtime. For more information, see the application troubleshooting guide to help resolve the error. 0x87D00215Message: Item not found Additional information for error resolution:
For more information, see the application troubleshooting guide to help resolve the error. 0x87D00235Message: Syntax error occurred while parsing Additional information for error resolution: This error generally occurs in one of the Configuration Manager components when a piece of data is invalid. This error could stem from something missing for the application, an old package version, or a number of other general errors. Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips. 0x87D00244Message: The object or subsystem has not been initialized Additional information for error resolution: This error generally occurs in one of the Configuration Manager components when a piece of data is invalid. This error could stem from something missing for the application, an old package version, or a number of other general errors. Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips. 0x87D0027CMessage: CI documents download timed out Additional information for error resolution: The CI documents activity can be tracked in CIAgent.log, CIDownloader.log, and DataTransferService.log. For more information, see the CI Agent section of the application troubleshooting guide. 0x87D00289Message: Failed to decompress CI documents Additional information for error resolution: The CI documents activity can be tracked in CIAgent.log, CIDownloader.log, and DataTransferService.log. For more information, see the CI Agent section of the application troubleshooting guide. 0x87D00314Message: CI Version Info timed out Additional information for error resolution: Typically this error occurs when a change was made to the application and the client doesn't have the new information for it. Verify that the client is getting the policy and it knows about any updated revisions to the application. 0x87D00321Message: The script execution has timed out Additional information for error resolution: Check the AppEnforce.log for details. You may need to increase the Maximum allowed run time (minutes) for the application. Ensure that the maintenance window on the client is large enough to support the run time. For more information, see the application troubleshooting guide to help resolve the error. 0x87D00324Message: The application was not detected after installation completed Additional information for error resolution: Review the AppDiscovery.log and the CIAgent.log. Once an installation is completed, the application detection is used again to verify the installation. 0x87D00325Message: Application was still detected after uninstall completed Additional information for error resolution: Verify the correct uninstall command was used in the AppEnforce.log. Review the AppDiscovery.log and the CIAgent.log. Once an uninstall is completed, the application detection is used again to verify the uninstall. 0x87D00327Message: Script is not signed Additional information for error resolution: Verify the PowerShell execution policy client setting for the device. The default for this client setting is AllSigned so an unsigned script will cause a failure. 0x87D00329Message: Application requirement evaluation or detection failed Additional information for error resolution: Review the AppIntentEval.log to discover dependencies and supersedence rules for the application and their states. For more information, see Application deployment evaluation. 0x87D00607Message: Content not found Additional information for error resolution: Verify the content for the application is on a distribution point and that the distribution point is accessible to the client. For more information, see Application download in Configuration Manager. 0x87D00667Message: No current or future service window exists to install software updates Additional information for error resolution: Ensure that the maintenance window on the client is large enough to support the Maximum allowed run time (minutes) for the application installation and that the client has received the policy for the window. 0x87D01106Message: Failed to verify the executable file is valid or to construct the associated command line Additional information for error resolution: Verify that the executable file is installable on its own then verify it's installable with the given command line. 0x87D01107Message: Failed to access all the provided program locations. This program may retry if the maximum retry count has not been reached Additional information for error resolution: The client is getting locations for the content, but can't reach the locations. Review the client's
LocationServices.log for the 0x87D01201Message: The content download cannot be performed because there is not enough available space in cache or the disk is full Additional information for error resolution: Check that the machine has enough space on the drive. Compare the
size of the 0x87D01202Message: The content download cannot be performed because the total size of the client cache is smaller than the size of the requested content Additional information for error resolution: Compare the size of the 0x87D01281Message: A supported App-V client is not installed Additional information for error resolution: Verify that a supported version of App-V is installed on the client. 0x87D0128FMessage: The App-V sftmime command returned failure Additional information for error resolution: For information on sftmime commands, see Manage Virtual Applications by Using the Command Line. 0x87D01290Message: An error occurred when querying the App-V WMI provider Additional information for error resolution: For information on the App-V WMI provider, see Application Virtualization Client WMI Provider. 0x87D103E8Message: Error Unknown Additional information for error resolution: Follow the application troubleshooting guide to help locate the error and resolve it. It may be necessary to review additional logs for components that support application installation. Searching for specific IDs or error codes in the logging may help you identify the problem. For more information, see general troubleshooting tips. 0x87D1076CMessage: Application was successfully installed Additional information for error resolution: The application was successfully installed. MSI errors
General MSI troubleshooting tipsWhen errors are encountered from MSI, typically you'll need to Enable Windows Installer logging. After the logging is enabled, you can retry the problem installation and Windows Installer will track the progress and post it to
the The MsiExec.exe and InstMsi.exe Error Messages and Windows Installer Action Return Values lists are useful when reviewing a Windows Installer log as are the general troubleshooting tips. 1602Message: User cancel installation Additional information for error resolution: The installation was canceled by the user. Ask the user to install the application fully. If possible, you can attempt to run the installation for the system rather than the user. 1603Message: Fatal error during installation Additional information for error resolution: Enable Windows Installer logging and run the install again. When reviewing the
installer log, typically an entry stating 1605Message: This action is only valid for products that are currently installed Additional information for error resolution: Ensure that the product is installed before running a dependant install. 1618Message: Another program is being installed. Please wait until that installation is complete, and then try installing this software again Additional information for error resolution: Wait for the prior installation to complete before running a new one. If the prior installation stops responding, you can attempt to stop the installation or terminate the process. Terminating a process might have undesired results. 1633Message: This installation package is not supported by this processor type. Contact your product vendor Additional information for error resolution: Ensure that the device's processor architecture is appropriate for the software. Verify the target device meets or exceeds the minimum processor requirement for the application. Contact the product vendor if the device's processor meets the product's processor support specifications. 1638Message: 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 on the Control Panel Additional information for error resolution: Uninstall the the unwanted version of the product. If you aren't using Configuration Manager, a script, or another management tool to uninstall, uninstall from the device manually. For Windows 10 or later clients, use Windows Settings > Apps to uninstall the unwanted version of the product. For earlier versions of Windows, use Programs and Features from the Control Panel to uninstall the unwanted version of the product. 1642Message: The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade patch may update 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 Additional information for error resolution: Verify the device meets the product versioning prerequisites for the installation. Windows errors
General Windows troubleshooting tipsUse the Windows system error codes list or Download the Microsoft Error Lookup Tool for looking up additional codes that aren't listed in this article. Using the Windows event logs and the general troubleshooting tips can also help identify the cause of these errors. 1Message: Incorrect function Additional information for error resolution: Review the Windows event logs around the time of the failure in combination with the installation logs to determine the possible cause of the error. 2Message: The system cannot find the file specified Additional information for error resolution:
692Message: Debugger terminated process Additional information for error resolution: Detach any debuggers attached to the process and retry the application installation. 0x80000003Message: One or more arguments are invalid Additional information for error resolution: Review the Windows event logs around the time of the failure in combination with the installation logs to determine the possible cause of the error. 0x80000007LMessage: Operation aborted Additional information for error resolution: Use the installation logs and Configuration Manager application logs to determine why installation stopped. Merge the logs so you can easily review what happened before the 0x80000007L error. Use 0x80000009Message: General access denied error Additional information for error resolution: If the issue isn't clear from the logs, using Additional tips for file permissions in Windows operating systems:
0x80004005Message: Unspecified error Additional information for error resolution: Use the installation logs and Configuration Manager application logs to determine why installation stopped. Merge the logs so you can easily review what happened before the 0x80004005 error. Use 0x8000FFFFMessage: Catastrophic failure Additional information for error resolution: Review the Windows event logs around the time of the failure in combination with the installation logs to determine the possible cause of the error. 0x80040154Message: Class not registered Additional information for error resolution: This is typically a configuration-related DCOM error. Review DCOM configuration settings using dcomconfig. If there's a problematic .dll file, you can use regsvr32 to register the dll file and try the install again. A large number of problematic files could be a sign of an underlying issue that needs to be resolved before you can install the application. 0x80091007Message: The hash value is not correct Additional information for error resolution: The hash of a file isn't correct and the installation can't complete. Typically you will see this error in the CAS.log. Check to see if file contents for the application were recently updated. There may be an issue with the package, in some cases you may need to rebuild and redistribute it. This issue can also happen if there is a sharing violation on a file, such as a security application scanning the file. Configuration Manager expects exclusive access to the file during a hash check. You can identify the problematic process by running a Process Monitor and adding a filter. The condition to be met is if the Result contains Sharing Violation then Include the event. 0xC0000142Message: Initialization of the dynamic link library failed. The process is terminating abnormally Additional information for error resolution: If there is a problematic .dll file, you can use regsvr32 to register the dll file and try again. A large number of problematic files could be a sign of an underlying issue that needs to be resolved before you can install the application. Windows Management Instrumentation (WMI) errors
General WMI troubleshooting tipsProblematic namespaces can typically be found in the Configuration Manager log files and the WMI logging. WMI relies on Component Object Model (COM)/Distributed Component Object Model (DCOM), the registry, the file system, and Remote Procedure Call (RPC). DCOM registrations and permissions are critical for WMI operations to be successful. You can review DCOM configuration settings using dcomconfig. When troubleshooting WMI problems, typically you start by verifying that the needed namespaces, classes, and instances exists in the WMI repository and can be accessed. Verify the namespace exists on the target first by running
To connect WMI Control to another computer:
Verify the namespace exists on the target and that you can query it properly. Run the Windows Management Instrument Tester from an elevated command prompt by typing in
Verify the repository:
WMI resources:
0x80041001Message: WBEM_E_FAILED Additional information for error resolution: WBEM_E_FAILED is a generic WMI failure error. The error can be caused by a number of things. The error will sometimes tell you which method or instance failed. You'll probably also see related log entires around the same time if you merge logs together based on similar function. For instance, if you see the error related to content for an application, you may want to merge together CAS.log, ContentTransferManager.log and DataTransfer.log. If the error happened on a site server not a client, you may want to review SMSProv.log for additional information. Use the General WMI troubleshooting tips to help identify the issue along with the application installation logs. 0x80041009Message: WBEM_E_NOT_AVAILABLE Additional information for error resolution: The resource, in many cases a remote machine, isn't currently available. Verify the device is online. Use the General WMI troubleshooting tips to help verify connectivity to WMI on the device. 0x8004100EMessage: WBEM_E_INVALID_NAMESPACE Additional information for error resolution: The namespace specified could not be found. Verify the target computer can connect to WMI by following the General WMI troubleshooting tips. Verify namespace specified exists. Windows Update Agent errors
General Windows Update Agent troubleshooting tipsThe errors for the installation originated from the Windows Update Agent. In many cases, you can attempt to install these updates using the built-in software update management from Configuration Manager, Windows Update for Business, or Microsoft Update. In certain circumstances where it's not feasible to use your regular patching mechanism, the 0x00240006Message: The update to be installed is already installed on the system Additional information for error resolution: The update is already installed on the device. 0x80240017Message: Operation was not performed because there are no applicable updates Additional information for error resolution: The update isn't applicable to the device. Verify that the device meets the requirements of the update. In cases where a superseding update has been installed, it's very rare that the superseded update would be applicable to the device. FeedbackSubmit and view feedback for How do I fix Adobe installation failed?To fix these errors, follow the given steps.. Create a new local user account with administrator privileges for your machine. ... . Sign in to your machine using that account.. Uninstall the Creative Cloud desktop app using the Creative Cloud desktop app uninstaller.. Download the Creative Cloud desktop app.. How do I fix error code 21 in Adobe?Exit code: 21 Payloads version is not supported by installed version of RIBS. Use the latest version of the installer.
How do I fix Error 72 on Adobe?How to fix errors 42 and 72. Install all available Windows updates and check if the issue is fixed. If updating Windows does not solve the issue, you are getting this error because Windows is unable to validate digital certificates.
How do I fix Adobe Installer?Select Acrobat or Adobe Reader, then Uninstall/Change. In the Setup dialog box, select Next. Select Repair, then Next. Select Install.
|