Microsoft Store help and reporting
Include the device, installation stage and exact Store error.
Live Domain Check
Run a live reachability check for apps.microsoft.com. Compare the regional responses with the problem you see in Microsoft Store.
Find Microsoft Store help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Microsoft Store browsing, app installation and purchase recognition can fail separately.
The checker above requests apps.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Store action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Include the device, installation stage and exact Store error.
Compare the website entrypoint with your browser or app. This website link is separate from a provider incident dashboard.
No separate incident dashboard is linked here. Use the official product help and any current announcements it links to; this does not mean that no outage is possible.
Include the device, installation stage and exact Store error.
Open Microsoft Store help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
App/product, Windows/device version, installation stage, error code and private purchase reference.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft Store.
These are troubleshooting comparisons, not claims that Microsoft Store is currently experiencing a particular incident.
Compare a second app's listing with the failing install and record the exact Store or Windows error.
Check account, device storage and purchase history before reinstalling applications or repeating a payment.
A 403 or 429 means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
Use these local troubleshooting steps after the down-check workflow when Microsoft Store seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open apps.microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Store issue.
Compare Wi-Fi and mobile data only where you are permitted to do so. Keep required VPN, proxy and security controls in place, and record which network fails.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Store support.
Run the apps.microsoft.com check and compare its original timestamps and responses with your actual error. Microsoft Store browsing, app installation and purchase recognition can fail separately.
Use the official help/reporting resource linked above. Include the device, installation stage and exact Store error.
Compare a second app's listing with the failing install and record the exact Store or Windows error. Check account, device storage and purchase history before reinstalling applications or repeating a payment.
App/product, Windows/device version, installation stage, error code and private purchase reference.