Troubleshooting packaging, deployment, and query of Windows apps

Use these suggestions to troubleshoot problems you experience when packaging, deploying, or querying an app package.

Get diagnostic info

When an API fails, it returns an error code that describes the problem.

If the error code doesn't provide enough info, you can get detailed event logs that provide more info to help you diagnose the cause of the problem.

To access the packaging and deployment event logs

  1. Run eventvwr.msc.
  2. Go to Event Viewer (Local) > Applications and Services Logs > Microsoft > Windows.
  3. The first log to check is AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational.
  4. Deployment-related errors are recorded in AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.

You can also use the following command in PowerShell to get the first few logged events:

Get-Appxlog | Out-GridView

Common error codes

This table lists the most common error codes.

Error code Value Description and possible causes
ERROR_BAD_FORMAT 0x8007000B 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.
See How to sign an app package using SignTool.
0x80073CF0 The package couldn't be opened.
Possible causes:
  • 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.
Check the AppxPackagingOM event log for more info.
0x80073CF1 The package couldn't be found.
You may get this error while removing a package that isn't installed for the current user.
0x80073CF2 The package data isn't valid.
0x80073CF3 The package failed update, dependency, or conflict validation.
Possible 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.
Check the AppXDeployment-Server event log for more info.
0x80073CF4 There isn't enough disk space on your computer. Free some space and try again.
0x80073CF5 The package can't be downloaded.
0x80073CF6 The package can't be registered.
Check the AppXDeployment-Server event log for more info.
0x80073CF7 The package can't be unregistered.
You may get this error while removing a package.
Check the AppXDeployment-Server event log for more info.
ERROR_INSTALL_CANCEL 0x80073CF8 The user canceled the install request.
ERROR_INSTALL_FAILED 0x80073CF9 Package install failed. Contact the software vendor.
Check the AppXDeployment-Server event log for more info.
ERROR_REMOVE_FAILED 0x80073CFA Package removal failed.
You may get this error for failures that occur during package uninstall.
For more info, see RemovePackageAsync.
0x80073CFB The provided package is already installed, and 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.
ERROR_NEEDS_REMEDIATION 0x80073CFC The app can't be started. Try reinstalling the app.
0x80073CFD A specified install prerequisite couldn't be satisfied.
0x80073CFE The package repository is corrupted.
You may get this error if the folder referenced by this registry key doesn't exist or is corrupted:
To recover from this state, refresh your PC.
0x80073CFF To install this app, you need a developer license or a sideloading-enabled system.
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 developer license.
  • The package is signed with a Microsoft signature and deployed as part of Windows or from the Microsoft Store.
  • The package is signed with a trusted signature and installed on a computer with a developer license, a domain-joined computer with the AllowAllTrustedApps policy enabled, or a computer with a Windows Sideloading license with the AllowAllTrustedApps policy enabled.
ERROR_PACKAGE_UPDATING 0x80073D00 The app can't be started because it's currently updating.
0x80073D01 The package deployment operation is blocked by policy. Contact your system administrator.
Possible causes:
  • 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 a 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.
ERROR_PACKAGES_IN_USE 0x80073D02 The package couldn't be installed because resources it modifies are currently in use.
0x80073D03 The package couldn't be recovered because data that's necessary for recovery is corrupted.
0x80073D04 The signature isn't valid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or shouldn't be present.
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 An error occurred while deleting the package's previously existing application data.
You can get this error if the simulator is running. Close the simulator. You can also get this error if there are files open in the app data (for example, if you have a log file open in a text editor).
0x80073D06 The package couldn't be installed because a higher version of this package is already installed.
0x80073D07 An error in a system binary was detected. Try refreshing the PC to fix the problem.
0x80073D08 A corrupted non-Windows binary was detected on the system.
0x80073D09 The operation couldn't be resumed because data that's necessary for recovery is corrupted.
0x80073D0A The package couldn't be installed because the Windows Firewall service isn't running. Enable the Windows Firewall service and try again.
APPX_E_PACKAGING_INTERNAL 0x80080200 The packaging API has encountered an internal error.
0x80080201 The package isn't valid because its contents are interleaved.
0x80080202 The package isn't valid because it contains OPC relationships.
0x80080203 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.
Ensure that the package isn't missing one or more of these required files:
  • \AppxManifest.xml
  • \AppxBlockMap.xml
If the package contains \AppxMetadata\, it must also contain \AppxSignature.p7x.
APPX_E_INVALID_MANIFEST 0x80080204 The package's AppxManifest.xml file isn't valid.
APPX_E_INVALID_BLOCKMAP 0x80080205 The package's AppxBlockMap.xml file isn't valid.
APPX_E_CORRUPT_CONTENT 0x80080206 The package contents can't be read because it's corrupted.
0x80080207 The computed hash value of the block doesn't match the has value stored in the block map.
0x80080208 The requested byte range is over 4 GB when translated to a byte range of blocks.
TRUST_E_NOSIGNATURE 0x800B0100 No signature is present in the subject.
You may get this error if the package is unsigned or the signature isn't valid. The package must be signed to be deployed.
CERT_E_UNTRUSTEDROOT 0x800B0109 A certificate chain processed, but terminated in a root certificate which isn't trusted by the trust provider.
See Signing a package.
CERT_E_CHAINING 0x800B010A A certificate chain couldn't be built to a trusted root certification authority.
See Signing a package.
0x80080209 The SIP_SUBJECTINFOstructure used to sign the package didn't contain the required data
E_INVALIDARG 0x80070057 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.repositoryExtension extension due to the following error: The parameter is incorrect.
You may get this error if the manifest elements DisplayName or 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.

How to sign an app package using SignTool

How to troubleshoot app package signature errors