traditional windows app in MS store

For a traditional EXE/MSI app that “just sits there” in the Microsoft Store submission pipeline, the key points to verify are:

1. Packaging format
   • Traditional installers are supported, but must be .exe or .msi only.
   • The installer must be a standalone/offline installer – it cannot download additional binaries during setup.
   • The installer must not change after submission and must not bundle unrelated software.
   • If using EXE/MSI, the installer must be hosted on own infrastructure or CDN, and a package URL must be provided in the submission.
2. Code signing
   • For EXE/MSI submissions, the Store does not re-sign installers.
   • The EXE/MSI must be Authenticode-signed with a valid code signing certificate that chains to a CA in the Microsoft Trusted Root Program.
   • Unsigned or improperly signed installers can fail security tests and stall or fail certification.
3. Certification timing and status
   • After submission, the app enters certification, which can take up to three business days.
   • Once certification passes, the listing typically appears in the Store within about 15 minutes, and the status changes to In the Store / In Microsoft Store.
   • If there are issues (for example, security or content compliance failures, or problems with the installer URL), a failure notification is sent and details appear in the submission’s certification report.
4. Security tests that affect traditional apps
   • Offline/standalone check: verifies the installer is not a downloader.
   • Bundleware check: ensures no unrelated third‑party apps are installed.
   • Non‑Microsoft drivers/NT services: any such dependencies must be disclosed in Partner Center during submission.
   • A valid privacy policy URL is required if the app accesses personal information.
5. Next steps to move forward
   • In Partner Center, open the app submission and check:
     • Status: whether it is still “In certification”, “Pre-processing”, “Failed”, or “In the Store”.
     • Certification report: look for failures related to signing, offline installer, bundleware, or undisclosed drivers/services.
   • Confirm that:
     • The EXE/MSI is properly Authenticode-signed.
     • The package URL is reachable and the binary at that URL has not changed since submission.
     • The installer is fully offline and does not attempt to download additional components.
     • Any full‑trust behavior and dependencies are clearly described and, where required, disclosed (for example, non‑Microsoft drivers/services).

If all of the above are correct and the submission has been stuck in certification for longer than a few business days with no failure report, the next step is to review the submission details in Partner Center and contact Store support from there, referencing the specific submission ID.

References:

• Submit your app to Microsoft Store
• Publish your first Windows app
• Get started with Microsoft Store
• The app certification process for MSI/EXE app