Microsoft Store and Windows Release
Windows has two practical paths: Store/MSIX or direct download. Pick one deliberately.
Path A: Microsoft Store/MSIX
Use this when you want Store trust, Store discovery, Store-managed updates, and less direct installer support.
Checklist:
- Reserve the app name in Partner Center.
- Confirm package identity and publisher identity.
- Build the MSIX/AppX package or bundle.
- Run the Windows App Certification Kit before submission.
- Upload packages and listing assets.
- Fill pricing, availability, age rating, privacy, and certification notes.
- Submit for certification.
- Review certification report if it fails.
- Publish immediately, schedule, or hold manually.
- Monitor Store analytics, reviews, crashes, and install issues.
Microsoft Store certification includes preprocessing, security tests, technical compliance tests, and content compliance. During publishing, Store packages are digitally signed by Microsoft for Store distribution.
Path B: Direct Windows Download
Use this when you need GitHub Releases, private distribution, enterprise distribution, or a non-Store installer.
Checklist:
- Choose installer format: NSIS, MSI, WiX, MSIX, portable ZIP, or framework-specific bundle.
- Choose signing path: OV certificate, EV certificate, Azure signing, SignPath, or another signing service.
- Sign every executable and installer artifact.
- Timestamp signatures so they survive certificate expiry.
- Download the artifact through the real public URL on a clean Windows VM.
- Test Defender and SmartScreen behavior before announcement.
- Submit false positives or reputation problems to Microsoft if needed.
- Decide update strategy before users install version 1.
Example MSIX signing shape:
signtool sign /fd SHA256 /a /tr http://timestamp.digicert.com /td SHA256 .\dist\MyApp.msixThat example shows the shape only. Real signing depends on where your certificate lives and how your CI accesses it.
Package Format Decision
| Format | Use when | Update model | Watch out for |
|---|---|---|---|
| MSIX/AppX via Store | You want Store distribution | Store updates | Package identity and certification |
| MSIX sideload | You want modern package identity outside Store | Enterprise or custom update path | Certificate trust on target machines |
| NSIS | You want direct desktop installer and Electron updater support | App updater or reinstall | SmartScreen reputation and uninstall behavior |
| MSI | You need enterprise deployment semantics | Enterprise tooling or reinstall | Not a good fit for electron-updater |
| Portable ZIP | You want no installer | Manual replacement | Weak trust, no update UX, more support burden |
Gotcha: The Microsoft Store account helps Store submissions. It does not solve direct-download SmartScreen reputation for arbitrary EXE or MSI files.