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.
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
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.
Looking for another service? Browse shopping and payment checks.
Include the device, installation stage and exact Store error.
Open the website in your browser and compare it with the result above.
Open Microsoft Store help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
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 Forbidden or 429 Too Many Requests 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.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
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 community buttons on this page to share whether the service works for you. For help from Microsoft Store, 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.