Microsoft Store certification and package errors
Search for the message you got, or find it below. Each page says what the error means and how to fix it, with the Microsoft docs and threads it comes from.
Partner Center rejects the package
- Apps are not allowed to have a Version with a revision number other than zero specified in the app manifest
Why Partner Center rejects an MSIX whose version ends in anything but .0, and how to set the version so the package uploads.
- The PublisherDisplayName element in the app manifest doesn't match your publisher display name
What the PublisherDisplayName package validation error in Partner Center means, where to copy the right value from, and how to rebuild the package.
- You don't have permission to submit framework packages at this time
Why Partner Center rejects Microsoft.VCLibs and other framework packages in your upload, and how to declare the dependency in your manifest instead.
- The package uses an unsupported version of file makepri.exe
Why Partner Center rejects packages built with a Windows SDK it doesn’t accept yet, how to read the allowed versions in the message and how to rebuild.
- Duplicate build metadata files were found in the manifest of package
What the duplicate makepri.exe build metadata error in Partner Center means and the fixes developers reported on Microsoft Q&A.
- A previous submission for this app was released with a Windows 10/11 .msixbundle or .appxbundle. Subsequent submissions must continue to contain a Windows 10/11 .msixbundle or .appxbundle.
Why Partner Center rejects a single .msix after your app shipped a bundle, and how to build a real .msixbundle with MakeAppx.
- The following restricted capabilities require approval before you can use them in your app: runFullTrust
Why Partner Center flags runFullTrust on MSIX desktop apps, whether you need it, and what to write on the Submission options page so certification approves it.
- Invalid package identity name / Invalid package publisher name
The Name or Publisher in your manifest differs from the values Partner Center reserved for the app.
- The name found in the package is not one of your reserved app names
The package uses a name you haven't reserved for this app in Partner Center.
Certification report failures
- 10.1.1.1 Inaccurate Representation: The product name contains the title of another piece of software or service
What the 10.1.1.1 Inaccurate Representation certification failure means, why the Product name field looks read-only, and how to rename the app.
- 10.1.2.10 Functionality: The product crashes while trying to load
What the 10.1.2.10 Functionality certification failure means, including "primary functions are not useable", and how to find and fix the problem before you resubmit.
- 10.2.4 Software Dependencies: Your product contains drivers that have not been provided by Microsoft
Why the Microsoft Store fails apps that install drivers or NT services under policy 10.2.4, who can get an exception, and what your options are.
- 10.3 Product is Testable
What the 10.3 Product is Testable failure means, and what to put in Notes for certification so testers can sign in and reach every feature.
- 10.5.1 Personal Information: privacy policy required
When the Microsoft Store requires a privacy policy, why every Win32 app needs one, what it has to cover and where to enter it in Partner Center.
- 11.11 Age Ratings
The answers to the IARC age rating questionnaire don’t match what the app contains.
Windows App Certification Kit failures
- The image {image name} failed the size restrictions
What each app manifest resources test error in the Windows App Certification Kit means, including logo size, missing images and resources.pri, and the logo sizes to use.
- Branding validation failed: the app uses default images
Why the Windows App Certification Kit fails apps that still use Visual Studio or SDK sample images, and how to fix it.
- Debug configuration test failed
Why the Windows App Certification Kit fails debug builds, why they also fail the supported API test, and how to build a release package.
- NXCheck, DBCheck, SafeSEHCheck, AppContainerCheck or WXCheck Test failed
What each BinScope Binary Analyzer failure in the Windows App Certification Kit security test means, and the linker setting that fixes it.
- Platform appropriate files test failed
Why the Windows App Certification Kit fails packages whose binaries don’t match the declared architecture, and what each architecture may contain.
Signing errors
- The app manifest publisher name must match the subject name of the signing certificate
What SignTool error 0x8007000B means when signing an MSIX, how to find the real cause in Event Viewer, and how to make a certificate whose subject matches your manifest.
Sending updates with StoreFast
StoreFast checks the package name and version before sending an update and tells you when Partner Center rejects it.