Error Codes For Troubleshooting App Installation Issues

[Matt Shadbolt]

First published on TechNet on May 15, 2018

**Edit**

Here's some formal docs guidance on troubleshooting app install errors, and a list of known error codes and troubleshooting information:

https://docs.microsoft.com/en-us/intune/apps/troubleshoot-app-install

https://docs.microsoft.com/en-us/intune/apps/app-install-error-codes

**/Edit**

Hi Everyone,

In the next month or so, we're going to be releasing some features that will make understanding and troubleshooting Intune App instatllation issues much easier.

The feature will display installation issues per device, and will display an end-to-end history of the app right up to the point of the install failure.

But when we report a failure with a red cross, how do you - the Intune administrator - solve the problem being reported?

To help, I’ve put together a list of common error codes, some info on potential root causes and the next steps in troubleshooting them. All of the error codes are client side errors (ie, iOS/Android/Windows returning an error), so information can sometimes be limited but I’ve done my best to work out common causes and solutions.

I'd love to see this list crowd sourced too though, so please list error codes you've experience and their cause/solution in the comments below.

I hope you find this list helpful!

Matt Shadbolt
Senior Program Manager | Microsoft Intune

=====

0x87D1041C - The application was not detected after installation completed successfully

This error typically occurs when a user uninstalls an app manually after Intune successfully installed the app. It can also be caused by issues with the apps manifest if it’s a LOB app. It can also be caused when an app is self-updating and that update is newer than the one published by the Intune admin. For example, say the Intune admin downloads and deploys a 3rd party app such as Google chrome. After the app is installed on an end user's device, the next time the user runs the app, it detects a newer version from the app store and prompts the user to update the app. If the user accepts and installs the app, the version on the device is newer than the one you published, so you will see this error.

Next Steps: If the issue only occurs on a single device, ask the user to trigger a fresh install via the Company Portal. If the issue occurs on multiple devices for a LOB app, ensure your app manifest has been configured correctly to successfully detect the app install. If the self-updating app is an MSI, you can check the option "ignore app version" with the app configuration and you will not get this error. If the app is not an MSI, just keep the app published up-to-date.

0x800B0101 - A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file

This error may occur if your deploying Line-of-Business (LOB) apps of the Appx type and the client does not have the required certificates installed.
Next Steps: Confirm that all of the required certificates for the Appx package are installed on the client.


0x80073CFF - Deployment of package failed because no valid license or sideloading policy could be applied. A developer license or enterprise sideloading configuration may be required

This error may occur if you’re deploying Line-of-Business (LOB) apps of the Appx type and the app is incorrectly signed. You may get this error if the package is not:

Signed with a Microsoft signature and deployed as a deep link from the Windows Store or Signed with a trusted signature and installed on a computer with a Windows Store developer license with the AllowAllTrustedApps policy enabled or Signed with a trusted signature and installed on a computer with a Windows Sideloading license with the AllowAllTrustedApps policy enabled

Next Steps: Speak with your App Development team and have them check the configuration of the Appx package to ensure it’s licensed/sideloaded correctly.


0x80073CF3 - The package failed update, dependency, or conflict validation

This error may occur if you’re deploying Line-of-Business (LOB) apps of the Appx type. It may be caused by the package already being installed on the target system, a package dependency not being found, or the package does not support the correct processor architecture.

Next Steps: If the error occurs on many devices, speak with your App Development team to check the app dependencies are correct and the architecture requirements have been configured correctly on the app. If the error occurs on a single device, check to see the app hasn’t previously been installed and check the AppXDeployment-Server log on the client for more information.


0x87D15607 - Could not validate app ID

This error directly translates to the iOS MDM error 12023 - The iTunes Store ID of the application could not be validated.

Next Steps: Confirm that the iOS Store deep-link deployment is correct, and the app ID is available in the devices region. Further troubleshooting can be performed by using XCode to gather device logs.


0x87D15630 - License not found

This error directly translates to the iOS MDM error 12064 – License not found. It is most likely due to an error with an Apple VPP deployed app.

Next Steps: Check that the Apple VPP app is configured and deployed correctly. Check that there are sufficient install licenses available, and that the app is available in your organizations Apple VPP portal.


0x80073D06 - The package couldn't be installed because a newer version of this package is already installed

This error may occur if you’re deploying Line-of-Business (LOB) apps of the Appx type and may be caused by a newer version of the Appx package being present on the machine.

Next Steps: If the error occurs on many devices, ensure the newest Appx version is being deployed. If the error occurs on a single machine, check to see what version of the package is already installed and resolve the conflict.


0x87D15609 - App already installed

This error may occur if a user has manually installed a LOB app prior to receiving it via Intune MDM.

Next Steps: Manually remove the duplicate app from the device and allow Intune to re-sync and deploy the app.


0x81030137 - Package is not valid or not applicable for application update

This error may occur if you’re deploying a new version of Line-of-business (LOB) app of the Appx type. The error may be caused by misconfiguration on the package, whereby a version upgrade is unsuccessful.

Next Steps: Speak with your App Development team and have them test app upgrades outside of MDM.


0x87D15631 - Payload issue, check payload

This error may occur if there is a problem with the app source.

Next Steps: If the issue occurs for a single device, attempt re-installation. If the issue occurs for all devices, attempt to re-upload the app to Intune and retest. If the issue continues to occur, speak with your App Development team to troubleshoot the app package.


0x800B0109 - Certificate chain led to untrusted root certificate

This error may occur if you’re deploying Line-of-Business (LOB) apps of the Appx type, and there is an issue with the certificates in the certificate chain used to sign the package.

Next Steps: If the issue only occurs on a single machine, check to see that the certificates are configured correctly and trusted through the entire chain on the local machine. If the issue occurs on all devices, speak with your App Development team and have them check the certificate validity on the package source.


0x80070643 - Fatal error during installation

This generic error is specific to MSI app installations via MDM. It translates to a generic MSI 1603 error and does not contain any further information to help troubleshoot.

1603 errors are common in the packaging community and may be caused by many factors.

Next Steps: Visit this link to understand more about the 1603 error.


0x87D13B7C - Vpp user, device or license not found

This error may occur when deploying VPP apps and there is an issue with license assignment.

Next Steps: Ensure the VPP app your deploying has sufficient licenses available.


0x87D13B64 - The app installation has failed

This error directly translates to the iOS MDM error ManagedAppStatus returned Failed being reported by the device. The error usually means the app has been installed previously and for some reason the iOS MDM agent (controlled by Intune in this instance) cannot take over management of the app.

Next Steps: Remove the app on the device and install it again via Intune.


0x87D13B66 - The app is managed, but has expired or been removed by the user

This error directly translates to the iOS MDM error ManagedButUninstalled being returned by the device. This can potentially be caused by:

• The app manifest has expired
• The app is not detected correctly
• The device is iOS 9.2.2 which contains a platform bug
• The end user uninstalled the app after successful uninstall before app detection completed

Next Steps: If the issue is happening for many devices for the same app, check with your App Development team to confirm the manifest is correct. If the issue is happening for a single device, ensure the device is up to date and attempt re-install.


0x87D13B60 - The app is scheduled for installation, but needs a redemption code to complete the transaction

This error directly translates to the iOS MDM error ManagedAppStatus returned NeedsRedemption being returned by the device.

This error is generally caused if an end user clicks “cancel” for the install prompt on their iOS device.

Next Steps: Advise the end user to re-install the app, and this time allow the app install to occur.


0x87D13B63 - The user rejected the offer to update the app

This error directly translates to the iOS MDM error ManagedAppStatus returned UserRejected being returned by the device.

This error is generally caused if an end user clicks “cancel” for the install prompt on their iOS device.

Next Steps: Advise the end user to re-install the app, and this time allow the app install to occur.


0x87D1077C - The app license failed to install

The error typically occurs when an Offline Microsoft Store for Business app is attempting installation and the license assignment fails.

Next Steps: If this occurs once off, attempt installation again. If it happens more than once, please raise a support case with Intune support.


0x87D13B7D - VPP unknown error occurred

This error may occur when attempting to deploy VPP apps. It is most likely an error occurring within Intune.

Next Steps: If this occurs once off, attempt installation again. If it happens more than once, please raise a support case with Intune support.

Updated 10/19/2018 - moved 0x87D1041C to the top of the list; that one's the most frequent error. Also added additional example for when that error can be seen.