The product failed to install through the Store

The Store certification result “The product failed to install through the Store – 10.3 App is Testable” means the tester could not successfully install the app using the Microsoft Store, so the app could not be tested as required by policy section 10.3 (Product is Testable).

Relevant points from the Store policies:

• The product must be testable. If it is not possible to test the product for any reason, it may fail requirement 10.3.
• If the product uses an installer via HTTPS URL (policy 10.2.9), it must:
  • Use only .msi or .exe as the installer binary.
  • Be a standalone installer, not a web/downloader stub.
  • Support a silent install (no installation UI; only UAC is allowed).
  • For some policy versions, be digitally signed with a certificate chaining to a CA in the Microsoft Trusted Root Program.
  • Not take an unreasonable amount of time to download and must not have an unreasonably low installation success rate.
• All products and in-product offerings acquired from the Store must be installed and updated only through the Store (10.2.5 / 10.2.6 variants in the archive policies).

Typical reasons for this failure on the tester’s device (for example, a Surface Laptop) include:

1. The Store cannot complete the install (network, installer, or signing issues), so the app never launches.
2. The submitted installer URL is invalid, changed after submission, or points to a non-standalone or interactive installer.
3. The installer takes too long to download or fails repeatedly, triggering 10.4.4 (unreasonable download time / low success rate) and causing the app to be effectively untestable.

To move forward:

1. Verify the installer flow from the Store
   • Acquire the app from the Store on a clean Windows device (ideally similar to the Surface Laptop used in testing).
   • Confirm that the app installs end-to-end without manual steps outside the Store.
2. If using an HTTPS installer URL (10.2.9):
   • Confirm the URL is versioned and that the binary at that URL never changes after submission.
   • Ensure the installer is .msi or .exe, standalone, and silent (no UI except UAC).
   • If applicable per policy version, ensure all PE files are code-signed with a certificate from a CA in the Microsoft Trusted Root Program.
3. If the app requires login or backend services:
   • Provide working demo credentials in “Notes for certification” (10.3.1).
   • Ensure any required server is online and functional (10.3.2), so the tester can complete first-run and basic validation.
4. Re-submit
   • After fixing installer and testability issues, resubmit the product in Partner Center and include any necessary test notes (e.g., credentials, special steps) in the Notes for certification field.

If the Store still cannot install the app on internal tests, open a support ticket through Partner Center so the certification team can review Store-side logs for the failed installation.

References:

• Microsoft Store Policies
• Microsoft Store Policies (7.18)
• Microsoft Store Policies (7.17)
• Microsoft Store Policies (7.16.1)
• Microsoft Store Policies (7.16)
• Microsoft Store Policies (7.14)
• Microsoft Store Policies (7.13)
• Microsoft Store Policies (7.12)
• one note installation from store => command not supported - Microsoft Q&A
• Microsoft Store not working – unable to download or update any apps - Microsoft Q&A
• 0X80070490 problem - Microsoft Q&A
• Purchased Microsoft Flight Simulator 2024 Aviator Edition over a week ago. Still won't download. - Microsoft Q&A
• error message ms-contact-support link - Microsoft Q&A