Troubleshooting packaging, deployment, and query of Windows Store apps

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.

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.

The package couldn't be found.

You may get this error while removing a package that isn't installed for the current user.

The package data isn't valid.

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.

There isn't enough disk space on your computer. Free some space and try again.

The package can't be downloaded.

The package can't be registered.

Check the AppXDeployment-Server event log for more info.

The package can't be unregistered.

You may get this error while removing a package.

Check the AppXDeployment-Server event log for more info.

The user canceled the install request.

Package install failed. Contact the software vendor.

Check the AppXDeployment-Server event log for more info.

Package removal failed.

You may get this error for failures that occur during package uninstall.

For more info, see RemovePackageAsync.

The provided package is already installed, and reinstallation of the package is blocked.

The app can't be started. Try reinstalling the app.

A specified install prerequisite couldn't be satisfied.

The package repository is corrupted.

You may get this error if the folder referenced by this registry key doesn't exist or is corrupted: HKLM\Software\Microsoft\Windows\CurrentVersion\Appx\PackageRepositoryRoot. To recover from this state, refresh your PC.

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 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.

The app can't be started because it's currently updating.

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. --------------------------------------------------------------------------------

The package couldn't be installed because resources it modifies are currently in use.

The package couldn't be recovered because data that's necessary for recovery is corrupted.

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.

An error occurred while deleting the package's previously existing application data.

The package couldn't be installed because a higher version of this package is already installed.

An error in a system binary was detected. Try refreshing the PC to fix the problem.

A corrupted non-Windows binary was detected on the system.

The operation couldn't be resumed because data that's necessary for recovery is corrupted.

The package couldn't be installed because the Windows Firewall service isn't running. Enable the Windows Firewall service and try again.

The packaging API has encountered an internal error.

The package isn't valid because its contents are interleaved.

The package isn't valid because it contains OPC relationships.

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\CodeIntegrity.cat, it must also contain \AppxSignature.p7x.

The package's AppxManifest.xml file isn't valid.

The package's AppxBlockMap.xml file isn't valid.

The package contents can't be read because it's corrupted.

The computed hash value of the block doesn't match the has value stored in the block map.

The requested byte range is over 4 GB when translated to a byte range of blocks.

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.

A certificate chain processed, but terminated in a root certificate which isn't trusted by the trust provider.

See Signing a package.

A certificate chain couldn't be built to a trusted root certification authority.

See Signing a package.

The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data

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.