Microsoft Store and app errors: full list and fixes
For Microsoft Store and app errors, match the exact code or symptom first: sign-in and licensing faults need account checks, download/update stalls need cache and service resets, and app crashes usually need repair, reset, or re-registering. I have seen guessing waste time and make app data, updates, or Store licensing worse. This guide maps the main Microsoft Store failure patterns and error codes to the first fix to try, plus the likely cause behind each one.
Use this triage table first
This map is the fastest way to avoid a random checklist. Start with the symptom you can see, then use the code if one appears. The first fix here is the safest one to try before moving into permissions, profile testing, Event Viewer, or reinstallation.
| Symptom or code | Most likely root cause | Fastest safe fix | Escalation if it fails | Check Event Viewer first? | Windows 10 / Windows 11 path notes |
|---|---|---|---|---|---|
| Microsoft Store will not open | Store cache fault, broken sign-in token, pending Store update | Press Win + R, type wsreset.exe, press Enter, wait for the blank command window to close and Store to relaunch, then in Store open Library > Get updates (Microsoft Learn) | In Store, click the profile icon, choose sign out, close Store, reopen it, sign back in, then use Repair or Reset for Microsoft Store | No, unless it flashes and closes instantly | Windows 11: Settings > Apps > Installed apps > Microsoft Store > Advanced options; Windows 10: Settings > Apps > Apps & features > Microsoft Store > Advanced options |
| Store opens, but downloads never start | Cache issue, account sync fault, Store service issue, VPN or proxy interference | Click the profile icon, sign out, close Store, reopen it, sign in again, run wsreset.exe from Run, then use Library > Get updates | Temporarily disable VPN or antivirus, check Windows Update, then test a clean boot | No | Older builds may show Downloads and updates rather than Library |
Install or update fails with 0x80070005 | Access denied, permissions fault, account token issue | Sign out/in, run the Windows Store Apps troubleshooter on Windows 10, then Repair or Reset Store | Check Event Viewer, test another user profile, inspect permissions issues tied to All Application Packages | Yes, if repeatable | Windows 10 troubleshooter: Settings > Update & Security > Troubleshoot |
| App flashes, then closes | Broken app registration, missing permissions, profile corruption | Open Settings > Apps, select the affected app, open Advanced options, click Repair, test it, then use Reset only if Repair fails | Reinstall the app, test another user account, then inspect Event ID 5961 or Event ID 1000 with 0xc000027b | Yes | Windows 11 flash-and-close cases often point past cache and toward launch or permissions faults |
| Store works, but one installed app will not start | App-specific corruption | Repair, Reset, or reinstall that app from Store Library or My Library | Compare behavior in another Windows account, then inspect app crash logs | Sometimes | Separate Store failure from app failure before touching the Store itself |
| Sign-in fails or Store says licensing/account error | Microsoft account problem, VPN/proxy block, token mismatch | In Microsoft Store, try signing out, closing the app, reopening it, and then signing back into the same Microsoft account. | Disable VPN briefly, test local vs Microsoft account behavior, then check Windows Update | No | Microsoft recommends signing in to a Microsoft account before troubleshooting Store apps |
| “Something happened on our end” | Generic Store error that may hide account, network, or permission trouble | Retry after account sign-out/in, then wsreset.exe | If paired with 0x80070005, treat it as access denied and inspect logs and permissions | Yes, if the message repeats after cache and account checks | Do not assume this is a Microsoft outage without checking local signs first |
| Apps fail across many user profiles | System permissions damage, Store infrastructure fault, Windows component issue | Check Windows Update and Store updates first | Inspect Event Viewer, review All Application Packages access, then consider Store re-registration or in-place Windows repair | Yes | Windows 11: Settings > Windows Update; Windows 10: Settings > Update & Security > Windows Update |
Fastest safe fix vs escalation step
Use cache reset, account sign-out, app Repair, app Reset, and Store updates early because they are low-risk. Move to Event Viewer, clean boot, alternate profile tests, and permission checks only when the pattern points there. I stick to that order because it avoids wiping app data when the real issue is sign-in or network related.
When to check Event Viewer before changing anything
Check Event Viewer first when apps flash and close, when multiple Store apps fail to start, or when 0x80070005 keeps returning after basic fixes. Event ID 5961 and Event ID 1000 with exception code 0xc000027b can shift the diagnosis from cache trouble to access-denied or activation failure.
Windows 10 vs Windows 11 path notes
The support guidance applies to Windows 10 and Windows 11. The menus differ enough to matter. Windows 11 puts updates in Settings > Windows Update. Windows 10 uses Settings > Update & Security > Windows Update. App repair settings also split between Installed apps on Windows 11 and Apps & features on Windows 10. (Microsoft Support)
What type of Microsoft Store or app failure do you have?
Start by sorting the problem into one of four groups: the Store does not open, the Store opens but downloads stall, an installed app flashes or fails to launch, or a code appears. That split matters because cache fixes, account fixes, and permission fixes solve different failure patterns.
The Store will not open at all
If Microsoft Store does nothing, opens and hangs, or closes without loading, start with wsreset.exe. Press Win + R, type wsreset.exe, press Enter, and wait for the blank command window to finish and Store to reopen. This clears the Store cache. I use it early because it is safe, but it does not repair broken permissions or profile damage.
Next, update the Store itself. Microsoft says to update the Microsoft Store from Library > Get updates. On some builds, the wording is Downloads and updates. If you cannot reach that screen, use the Store app’s Repair option.
The Store opens but downloads or updates never start
This pattern often points to cache, account state, or a network blocker. Inside Microsoft Store, click the profile icon, choose sign out, close the app, reopen it, sign back in with the same Microsoft account, and try the same app again. Microsoft recommends signing in to a Microsoft account before troubleshooting Store apps.
Then check Windows Update. Windows 11 users are told to check for updates in Settings > Windows Update. On Windows 10, go to Settings > Update & Security > Windows Update. Pending updates can carry Store infrastructure fixes.
An installed app flashes, closes, or says it cannot start
This is a different branch. If the Store opens normally but one app crashes, it is reasonable to start by treating it as an app-specific problem. Open the app’s Advanced options, run Repair, test it, and use Reset only if Repair fails. Microsoft also recommends repairing or resetting apps.
If several Store apps flash and close, skip the idea that this is a simple cache fault.All Application Packages access, or account/profile corruption far more often than a stuck Store cache.
You see a code such as 0x80070005 or a vague Store message
Codes beat guesswork. A generic message can still point you in the right direction. A Microsoft Q&A answer ties the Store failure to error code 0x80070005, and that code maps to access denied. Treat that as a permissions clue, not a random Store glitch.
If the only message is something happened on our end, use the account and cache branch first. If it comes back with 0x80070005 or launch failures, move to logs and permissions.
Why does Microsoft Store say something happened on our end?
That message usually means the Store hit a failure it could not describe cleanly. In practice, it can point to sign-in trouble, a blocked download path, a service glitch, or an access-denied condition such as 0x80070005. The wording is vague, so the surrounding symptom matters more than the message itself.
What that message usually means in practice
The message appears in cases where the Store cannot complete a request but also does not show the real cause on screen. The same Q&A thread that mentions the message also points to 0x80070005, which is why I would not treat this error as a harmless temporary outage by default.
When it points to sign-in, network, or service trouble
If the Store opens, browsing works, but installs or updates never begin, start with account state and network. Sign out and back in from the Store profile menu. Then run wsreset.exe. If a VPN, proxy, or antivirus filter is active, disable it briefly and retest one download.
Keep the test short. If disabling security software changes nothing, turn it back on and move on.
When it is really an access-denied or permissions problem
If the same message appears with 0x80070005, or apps later fail to start, think access denied. Missing permissions tied to All Application Packages can stop Store installs and app launches. That is when Event Viewer becomes more useful than repeating cache resets.
How to separate a Microsoft-side outage from a local fault
Try more than one app. Try the Store Library update flow. Test another Windows user account if available. If Store fails only in one account, the problem is likely local to that profile. If all Store apps fail to start and Event Viewer shows 5961 or 0xc000027b, look inward, not outward.
How do you fix Microsoft Store install and update errors first?
Start with the low-risk branch: update the Store, update Windows, reset the Store cache, then refresh account sign-in. If the error is install or update related and the Store still opens, those steps are quicker and safer than re-registration or permission work, and they fit the most common causes.
Check Library > Get updates and Windows Update
Microsoft says to update the Microsoft Store from Library > Get updates. Do that before chasing app-specific repairs. Then check Windows Update.
- Open Microsoft Store.
- Open Library.
- Select Get updates.
- Retry the failed install or update.
- On Windows 11, go to Settings > Windows Update.
- On Windows 10, go to Settings > Update & Security > Windows Update.
- Install pending updates and test again.
Run wsreset.exe and test again
wsreset.exe resets the Microsoft Store cache. Press Win + R, type wsreset.exe, and press Enter. Wait for the command window to close and for Microsoft Store to reopen before you test again. It is useful when Store opens badly, fails to start downloads, or keeps stale licensing data. It is unlikely to fix app flash-and-close failures, broken registrations, or missing permissions.
Sign out and back into your Microsoft account
Account token problems can block Store installs, licensing checks, and app ownership checks. In Store, click the profile icon at the top right, choose sign out, close Store, reopen it, click the profile icon again, and sign back in with the same Microsoft account. If the problem exists only under a local account and clears under a Microsoft account, that is a strong profile clue.
Use Repair or Reset for the Store app
Microsoft also recommends repairing or resetting apps. Use Repair first. Reset is stronger and may clear app data.
Windows 11: Settings > Apps > Installed apps > Microsoft Store > Advanced options > Repair or Reset.
Windows 10: Settings > Apps > Apps & features > Microsoft Store > Advanced options > Repair or Reset.
What should you do when Store apps fail to start or flash and close?
When Store apps open for a second and vanish, treat that as a launch failure branch, not a download branch. Repair or reset the affected app first, then test another Windows profile and a clean boot state. If many apps behave the same way, move quickly toward logs and permissions checks.
Tell apart one broken app from a Store-wide launch failure
If only one app fails, fix that app. If Calculator, Photos, Mail, or several Store apps all flash and close, the Store itself may be fine while the app platform is not. That distinction decides whether to stay inside app settings or inspect system-level launch errors.
Repair, reset, or reinstall the affected app
On Windows 11, go to Settings > Apps > Installed apps, choose the app, open Advanced options, click Repair, test the app, then click Reset only if it still fails. On Windows 10, use Settings > Apps > Apps & features. If reset fails, uninstall the app and reinstall it from Store Library or My Library.
Microsoft lists reinstalling apps from the Store Library as a fix. This is best when one app is broken and Store itself still works.
Test another Windows user profile and clean boot state
Create or sign into another Windows account and test the same app. If the app launches there, the fault is likely profile-specific. Then try a clean boot state to see whether a background service, antivirus filter, or VPN client is interfering with app startup or Store communication.
When app launch failures point to permissions instead of cache
If apps flash and close immediately on Windows 11, or if the same behavior affects many Store apps, cache is no longer the lead suspect. Microsoft notes Event ID 5961 for app launch failures. Event ID 1000 with exception code 0xc000027b points toward fatal access-denied during initialization. (Microsoft Learn)
How do error codes and event logs narrow the root cause?
Error codes and Event Viewer entries cut through vague Store messages. Use them when the problem repeats after account, cache, and repair steps. In this branch, 0x80070005 suggests access denied, Event ID 5961 suggests app activation failure, and Event ID 1000 with 0xc000027b suggests fatal initialization trouble.
0x80070005: access denied during install or update
A Microsoft Q&A answer ties Store failure to 0x80070005. That code should push the diagnosis toward access denied, not random corruption. If it appears during install or update, try sign-out/sign-in and Store Repair first, then inspect permissions and account scope if it keeps returning.
Event ID 5961: app activation failed
Microsoft’s Store app failure material notes Event ID 5961 under Microsoft-Windows-Immersive-Shell for app launch failures. This event is a strong clue when apps do not stay open. It points to a launch or activation problem, often beyond simple cache trouble.
Event ID 1000 with 0xc000027b: fatal initialization failure
Microsoft says 0xc000027b can appear for an access-denied initialization failure. In Event Viewer, that often appears as Event ID 1000 under Application Error. When that pair shows up during Store app launch, permission damage becomes a far stronger suspect than networking.
Where to find the logs and what to compare
Open Event Viewer and check these areas:
- Windows Logs > Application for Event ID 1000 and exception code
0xc000027b. - Applications and Services Logs > Microsoft > Windows for Microsoft-Windows-Immersive-Shell entries such as Event ID 5961.
Compare the event time to the exact moment the app failed. If every failed launch writes the same event, that pattern is more useful than the on-screen message.
When are permissions, All Application Packages, or corruption the real problem?
Permissions become the leading suspect when many Store apps fail to start, 0x80070005 appears repeatedly, or Event Viewer shows 5961 or 0xc000027b after basic fixes. Missing read access for the All Application Packages group can stop Store apps from launching even when Store cache resets appear to run normally.
Why Store apps depend on All Application Packages access
Microsoft states missing permissions for All Application Packages can break Store apps. Store apps rely on this group being able to read required locations. When that access is missing on certain registry or file paths, the app can fail during activation or initialization.
Symptoms that fit missing read permissions
Look for these signs:
- Apps flash and close with no useful message.
- More than one Store app fails the same way.
- The Store may open, but installed apps will not.
- Event Viewer shows Event ID 5961 or Event ID 1000 with
0xc000027b. - Install or update errors include
0x80070005.
Safe checks before touching registry or file ACLs
Before changing permissions, verify that the fault is not account-specific. Test another Windows user profile. Run a clean boot. Install all pending Windows updates. Repair or reset the app. Reinstall one affected app from Library or My Library. These checks reduce the chance of changing system permissions for the wrong reason.
If a permission issue still looks likely, back up the system first. I have seen broad ACL edits create a second problem that is harder to unwind than the first.
When to move from repair steps to system-level repair
Move beyond app repair when the issue crosses multiple Store apps, affects multiple user profiles, and lines up with Event Viewer errors. At that point, Store re-registration or an in-place Windows repair can be cleaner than chasing each app one by one. Keep PowerShell re-registration as a later step, not the opener.
Can antivirus, VPN, proxy, or IPv6 cause Microsoft Store errors?
Yes, but only in certain patterns. Antivirus, VPN, proxy, and IPv6 checks make sense when Store sign-in fails, downloads never start, or licensing cannot validate. They are weaker suspects when apps flash and close and Event Viewer points to activation or access-denied failures inside Windows.
Cases where security software blocks sign-in or downloads
Third-party antivirus and endpoint tools can block Store traffic, token handling, or app package downloads. That is most plausible when browsing works elsewhere but Store sign-in loops, downloads stall at start, or the same issue clears in a clean boot state.
How to do a short disable test without changing everything
Disable the VPN or third-party antivirus briefly, then retry one Store sign-in or one small app install. Re-enable it immediately after the test. The point is diagnosis, not running unprotected for long periods. If nothing changes, stop chasing that branch.
VPN, proxy, DNS, and IPv6 checks that matter
Turn off VPN first. If a manual proxy is configured, test without it. One cited answer says disabling IPv6 worked for the issue. That makes IPv6 a conditional test when Store reaches the internet poorly, not a universal fix. Use it only after simpler account and cache checks.
How to avoid chasing network settings when logs point elsewhere
If apps fail after opening, and Event Viewer logs 5961 or 0xc000027b at each launch, network tuning is likely a distraction. Those logs point inward, toward app activation or permissions. Save VPN, proxy, and IPv6 changes for Store sign-in and download branches.
How do you reinstall Microsoft Store or affected apps safely?
Reinstall only after Repair, Reset, cache reset, and account checks fail. If one app is broken, reinstall that app from Store Library or My Library first. If Microsoft Store itself is broken across multiple tests, consider Store re-registration or reinstallation, then move to an in-place Windows repair if needed.
Reinstall an individual app from Library or My Library
Uninstall the affected app from Settings, then reopen Microsoft Store. Go to Library or My Library, find the app, and reinstall it. Microsoft lists reinstalling apps from the Store Library as a fix. This is the cleanest path when Store works but the app does not.
Re-register or reinstall Microsoft Store after other fixes fail
Reserve Store re-registration for cases where Store itself fails after updates, cache reset, sign-in refresh, and Repair or Reset. This is the right stage for PowerShell-based re-registration or package repair, because earlier steps rule out simpler causes. Do not lead with PowerShell when one app alone is failing.
What to back up or note before deeper repair steps
Note the exact error code, affected apps, whether another Windows account works, and whether Event Viewer logs 5961 or 0xc000027b. Back up app data where possible before Reset or uninstall. That record helps if the next step is Store re-registration or an in-place Windows repair.
When an in-place Windows repair is the cleanest next move
If multiple Store apps fail across accounts, Windows is current, Store cache and app resets do nothing, and logs point to activation or permission damage, an in-place Windows repair is often cleaner than manual permission edits. Use that route when the fault is broad and repeatable.
Frequently asked questions
Why does Microsoft Store say something happened on our end?
It is a generic Store message, not a diagnosis. It can mean sign-in trouble, download blockage, a service issue, or an access-denied condition such as 0x80070005. If the message repeats after account sign-out and wsreset.exe, check whether logs or codes point to permissions instead.
How do I fix Microsoft Store app error 0x80070005?
Treat 0x80070005 as access denied. Sign out and back into the Microsoft account, run the Windows Store Apps troubleshooter on Windows 10, reset the Store cache with wsreset.exe, then Repair or Reset Microsoft Store. If it persists, inspect Event Viewer and permissions tied to All Application Packages.
What should I do if Microsoft Store apps fail to start?
First decide whether one app is broken or many are. Repair or Reset the affected app, then reinstall it from Store Library if needed. If several apps flash and close, test another Windows profile and check Event Viewer for Event ID 5961 or Event ID 1000 with 0xc000027b.
How do I repair Microsoft Store or reset its cache?
Run wsreset.exe from the Run dialog to clear the Store cache. Then, if needed, use the app’s Repair or Reset option. On Windows 11, go to Settings > Apps > Installed apps > Microsoft Store > Advanced options. On Windows 10, use Apps & features instead.
Why do Store apps flash and close immediately on Windows 11?
This usually points beyond simple cache trouble. Common causes include broken app registration, account/profile corruption, or missing access for All Application Packages. If several apps behave this way, check Event Viewer before changing network settings. Event ID 5961 or 0xc000027b makes permissions more likely.
Can antivirus, VPN, or IPv6 cause Microsoft Store errors?
Yes, mainly when Store sign-in fails or downloads never begin. Do a short test with VPN or third-party antivirus disabled, then re-enable it. IPv6 is a conditional test, not a first move. If Event Viewer shows launch failures, network settings are probably not the main cause.
