List of Microsofts Store error codes, descriptions, resolution
Every time an error occurs in Windows Store, there is a code left behind. While these codes have no meaning to end-users, if given to the technical support team, they can help. However, Microsoft has these codes already on its website, with resolutions available for the same. Here is a list of Error Codes for Microsoft Store apps, sourced from Microsoft MSDN. It gives the code, message causes along with a description, and suggested workaround or resolution method.
List of Microsoft Store error codes, descriptions, resolution
While all the error codes have a description, some of the codes have resolution or causes or debugging or workaround. So in case you don’t find a solution, you can always search for those codes on our website.
| Error Code | Description | Resolution/Causes/Debugging/Workaround |
| 0x80073CFB
ERROR_PACKAGE_ALREADY_EXISTS |
The provided package is already installed, and the reinstallation of the package is blocked. | You may get this error if installing a package that is not bitwise identical to the package that is already installed. Note that the digital signature is also part of the package. Hence if a package is rebuilt or resigned, it is no longer bitwise identical to the previously installed package.
Two possible options to fix this error are: (1) Increment the version number of the app, then rebuild and resign the package (2) Remove the old package for every user on the system before installing the new package. |
| 0x80073CF0
ERROR_INSTALL_OPEN_PACKAGE_FAILED |
The package couldn’t be opened. | The package is unsigned, The publisher name doesn’t match the signing certificate subject, The file:// prefix is missing or the package couldn’t be found at the specified location.
Suggestions: Check the AppxPackagingOM event log for more info. |
| 0x80073CF2
ERROR_INSTALL_INVALID_PACKAGE |
The package data isn’t valid. | |
| 0x80073D00
ERROR_PACKAGE_UPDATING |
The app can’t be started because it’s currently updating. | |
| 0x80073D01
ERROR_DEPLOYMENT_BLOCKED_BY_POLICY |
The package deployment operation is blocked by policy. Contact your system administrator. | Package deployment is blocked by Application Control Policies, Package deployment is blocked by the “Allow deployment operations in special profiles” policy. One of the possible reasons is the need for a roaming profile.
See Deploy Roaming User Profiles to set up Roaming User Profiles on user accounts. If there are no policies configured on your system and you still see this error, perhaps you are logged in with a temporary profile. Log out and log in again, then try the operation again. |
| 0x80073CF4
ERROR_INSTALL_OUT_OF_DISK_SPACE |
There isn’t enough disk space on your computer. Free some space and try again. | |
| 0x80073CF5
ERROR_INSTALL_NETWORK_FAILURE |
The package can’t be downloaded. | |
| 0x80073CF6
ERROR_INSTALL_REGISTRATION_FAILURE |
The package can’t be registered. | |
| 0x800700B
ERROR_BAD_FORMAT |
The package isn’t correctly formatted and needs to be re-built or re-signed. | You may get this error if there is a mismatch between the signing certificate subject name and the AppxManifest.xml publisher name. |
| 0x80073CF7
ERROR_INSTALL_DEREGISTRATION_FAILURE |
The package can’t be unregistered. You may get this error while removing a package. | |
| 0x80073CF8
ERROR_INSTALL_CANCEL |
The user canceled the install request. | |
| 0x80073CF9
ERROR_INSTALL_FAILED |
The package install failed. Contact the software vendor. | |
| 0x80073CFA
ERROR_REMOVE_FAILED |
Package removal failed. You may get this error for failures that occur during the package uninstall. | |
| ERROR_INSTALL_PACKAGE_NOT_FOUND | The package couldn’t be found. | You may get this error while removing a package that isn’t installed for the current user. |
| 0x80073CFC
ERROR_NEEDS_REMEDIATION |
The app can’t be started. Try reinstalling the app. | |
| 0x80073CFD
ERROR_INSTALL_PREREQUISITE_FAILED |
A specified install prerequisite couldn’t be satisfied. | |
| 0x80073CFE
ERROR_PACKAGE_REPOSITORY_CORRUPTED |
The package repository is corrupted. | You may get this error if the folder referenced by this registry key doesn’t exist or is corrupted:
HKLMSoftwareMicrosoftWindowsCurrentV ersionAppxPackageRepositoryRoot To recover from this state, refresh your PC. |
| 0x80073CFF
ERROR_INSTALL_POLICY_FAILURE |
To install this app, you need a developer license or a sideloading-enabled system. | Debugging: You may get this error if the package doesn’t meet one of the following requirements: The app is deployed using F5 in Visual Studio on a computer with a Windows Store developer license,
The package is signed with a Microsoft signature and deployed as part of Windows or from the Windows Store, The package is signed with a trusted signature and installed on a computer with a Windows Store developer license, a domain-joined computer with the AllowAllTrustedApps policy enabled, or a computer with a Windows Sideloading license with the AllowAllTrustedApps policy enabled. |
| 0x80073D02
ERROR_PACKAGES_IN_USE |
The package couldn’t be installed because the resources it modifies are currently in use. | |
| 0x80073D03
ERROR_RECOVERY_FILE_CORRUPT |
The package couldn’t be recovered because the data that’s necessary for recovery is corrupted. | |
| 0x80073D04 ERROR_INVALID_STAGED_SIGNATURE |
The signature isn’t valid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or shouldn’t be present Possible workaround: If you are a developer using F5 with Visual Studio, ensure that your built project directory doesn’t contain signature or block map files from previous versions of the package. |
|
| 0x80073D05
ERROR_DELETING_EXISTING _APPLICATIONDATA_STORE_FAILED |
An error occurred while deleting the package’s previously existing application data. | Cause: You get this error if the simulator is running. Close the simulator. |
| 0x80073D06
ERROR_INSTALL_PACKAGE_DOWNGRADE |
No details found. | |
| 0x80073D07
ERROR_SYSTEM_NEEDS_REMEDIATION |
An error in a system binary was detected. Try refreshing the PC to fix the problem. | |
| 0x80073D08
ERROR_APPX_INTEGRITY_FAILURE_EXTERNAL |
A corrupted non-Windows binary was detected on the system. | |
| 0x80073D09
ERROR_RESILIENCY_FILE_CORRUPT |
The operation couldn’t be resumed because data that’s necessary for recovery is corrupted. | |
| 0x80073CF3
ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED |
The package failed to update, dependency, or conflict validation. | Causes: The incoming package conflicts with an installed package, A specified package dependency can’t be found, The package doesn’t support the correct processor architecture.
Debugging: Check the AppXDeployment-Server event log for more info. |
| 0x80070057
E_INVALIDARG |
One or more arguments are not valid If you check the AppXDeployment-Server event log and see the following event; “While installing the package, the system failed to register the windows repository extension due to the following error: The parameter is incorrect.” | Cause: You may get this error if the manifest elements DisplayName
Description: contain characters disallowed by Windows firewall; namely “|” and “all”, due to which Windows fails to create the AppContainer profile for the package. Please remove these characters from the manifest and try installing the package. |
| 0x80073D0A
ERROR_INSTALL_FIREWALL _SERVICE_NOT_RUNNING |
The package couldn’t be installed because the Windows Firewall service isn’t running. Enable the Windows Firewall service and try again. | |
| 0x800B0100
TRUST_E_NOSIGNATURE |
No signature is present in the subject. | Cause: You may get this error if the package is unsigned or the signature isn’t valid. The package must be signed to be deployed. |
| 0x800B0109
CERT_E_UNTRUSTEDROOT |
A certificate chain processed but terminated in a root certificate that isn’t trusted by the trusted provider. | |
| 0x800B010A
CERT_E_CHAINING |
A certificate chain couldn’t be built to a trusted root certification authority. | |
| 0x80080209
APPX_E_INVALID_SIP_CLIENT_DATA |
The SIP_SUBJECTINFOstructure used to sign the package didn’t contain the required data | |
| 0x80080200
APPX_E_PACKAGING_INTERNAL |
The packaging API has encountered an internal error. | |
| 0x80080201
APPX_E_INTERLEAVING_NOT_ALLOWED |
The package isn’t valid because its contents are interleaved. | |
| 0x80080202
APPX_E_RELATIONSHIPS_NOT_ALLOWED |
The package isn’t valid because it contains OPC relationships. | |
| 0x80080203
APPX_E_MISSING_REQUIRED_FILE |
The package isn’t valid because it’s missing a manifest or block map, or a code integrity file is present but a signature file is missing. | Workaround: Ensure that the package isn’t missing one or more of these required files: AppxManifest.xml and AppxBlockMap.xml. If the package contains AppxMetadataCodeIntegrity.cat it must also contain AppxSignature.p7x. |
| 0x80080204
APPX_E_INVALID_MANIFEST |
The package’s AppxManifest.xml file isn’t valid. | |
| 0x80080205
APPX_E_INVALID_BLOCKMAP |
The package’s AppxBlockMap.xml file isn’t valid. | |
| 0x80080206
APPX_E_CORRUPT_CONTENT |
The package contents can’t be read because it’s corrupted. | |
| 0x80080207
APPX_E_BLOCK_HASH_INVALID |
The computed hash value of the block doesn’t match the has a value stored in the block map. | |
| 0x80080208
APPX_E_REQUESTED_RANGE_TOO_LARGE |
The requested byte range is over 4 GB when translated to a byte-range of blocks. |
I hope the codes were useful, and you were able to find out the meaning of the codes, and workarounds for those listed.
Speaking of Error Codes, these posts too, are likely to be of interest to you:
- Volume Activation error codes and error messages
- Windows Errors, System Error Messages and Codes
- Windows Bug Check or Stop Error Codes
- Master List of Windows Update Error Codes
- Windows 10 Installation or Upgrade Errors.
