Microsoft Store Keeps Crashing? How to Fix It Fast

If Microsoft Store keeps crashing when launched, you're not doing anything wrong. You click the icon, you see the splash screen for a second, then poof. It's gone.

In our research, this crash-on-launch pattern is one of the most common Store faults on Windows 10 22H2 and Windows 11 23H2 / 24H2 as of 2026. It usually points to cache or service trouble, not a dead PC. Let's walk through what causes it and fix it in the right order.

Quick Answer

Microsoft Store keeps crashing when launched due to corrupt cache usually. Clear the cache with wsreset.exe first. Repair the app if it still crashes.

Update Windows if problems continue.

Why Microsoft Store Opens Then Crashes in Seconds

Microsoft Store is a Universal Windows Platform app. That's a one sentence definition. It means it runs in a sandboxed container and depends on shared services to launch.

If any of those dependencies break, the Store can't stay open. You'll see the logo flash, then it closes with no error. That's the classic sign.

Our research shows these triggers cause most instant crashes:

• Corrupted Store cache in the LocalCache folder
• Disabled Microsoft Store Install Service or Windows Update service
• Pending Windows build update that left AppX registration half finished
• Wrong date, time, or region, so the license check fails
• VPN, proxy, or custom DNS blocking the Store connection
• Corrupt user profile that can't load app licenses

If you've ever dealt with slow network on just one device, this feels familiar. The app itself is fine. The stuff around it is blocking it.

60-Second Checks Before You Reset Anything

Don't reset yet. If your setup has a simple mismatch, a reset won't help. Run these quick checks first.

Restart your PC once, fully. Not sleep. Not hibernate.

A full Restart clears stuck Store processes.

Then check your clock and region. Go to Settings > Time & language. Turn on Set time automatically and Set time zone automatically.

Make sure your Country or region matches where you live. The Store kills the connection fast if your license region looks wrong.

Check your internet without a VPN. Pause your VPN, proxy, and third party firewall for one test launch. If your phone works but PC crawls, suspect the PC network stack first.

Press Win + R, type winver, and press Enter. If you're months behind on builds, plan to update soon. Old builds break new Store versions all the time.

Fix Microsoft Store Crashing in This Exact Order for Windows 10 and 11

Work this like a flowchart. If step one fixes it, stop. Only move down if it still crashes.

Branch 1: Clear Store Cache and Run Repair Without Losing Data

If the Store flashes then closes, start here. This clears junk without deleting your library.

Press Win + R, type wsreset.exe, and press Enter. A blank Command Prompt window will pop up for 10 to 20 seconds. Then the Store should try to open on its own.

If it still crashes, do a Repair. Go to Settings > Apps > Installed apps > Microsoft Store > three dots > Advanced options. Click Repair and wait for the checkmark.

Launch the Store again.

Still crashing? Sign out inside the Store if you can open it for even a second. Or go to Settings > Accounts and confirm your Microsoft account is syncing.

A stale login can loop the crash. For official steps, Microsoft outlines these first fixes on Microsoft Support.

Branch 2: Fix Windows Update, Date-Time, and Disabled Store Services

If cache and Repair didn't help, check the services the Store needs to live.

Go to Settings > Windows Update and install everything pending. Then open Microsoft Store > Library > Get updates if you can stay open long enough. Outdated inbox apps drag the Store down with them.

Next, press Win + R, type services.msc, and check three services. Microsoft Store Install Service should be Manual. Windows Update should be Manual or Automatic.

Background Intelligent Transfer Service should be Manual. If any are Disabled, double click them and set them back.

This is also where unstable connection on your PC bites you. Proxy or metered connection blocks can stop license sync cold.

Branch 3: Repair Corrupt System Files and Re-register Store With PowerShell

If services look fine, suspect corrupt files. This happens a lot right after a failed update.

Open Command Prompt as administrator. Run sfc /scannow and let it finish. It takes 10 to 20 minutes.

Then run DISM /Online /Cleanup-Image /RestoreHealth. Reboot when both complete.

If it still crashes, re-register the Store package. Open PowerShell as administrator and run the Get-AppXPackage command for WindowsStore to reinstall its manifest. This rewrites registration without touching your other data.

Launch the Store once more before moving on.

Branch 4: Test a New User Profile and Decide on Last-Resort Fixes

If nothing above works, test for profile damage. Go to Settings > Accounts > Other users > Add account. Create a new local administrator account.

Sign into it and launch the Store there.

If Store works in the new profile, your old profile is corrupt. Move your files over and use the new profile going forward. That's faster than fighting permissions for hours.

If it crashes in both profiles, run the Windows Store Apps Troubleshooter through Settings > System > Troubleshoot. As a last resort, consider an in place repair upgrade. Only do a clean install if Reliability History shows repeated Store faults for weeks.

Repair vs Reset vs PowerShell Re-register: Which One You Actually Need

Pick the lightest fix that matches your symptom. Reset wipes more than people expect.

If your crash started after an update, Repair plus Windows Update fixes most cases. If you see codes like 0x80072EFD or 0x80070422, think network or disabled service first.

Reset helps when cache is truly mangled. But you'll need to sign back in. You'll lose preferences and offline licenses will resync.

Back up game saves and app data before you click it.

Folks who've seen storage glitches after an update know the pattern. Updates fix a lot. They also break registrations.

Re-register is your middle ground before a reinstall.

Mistakes That Keep Microsoft Store Broken

These are the traps we see over and over in forums and aggregate reviews.

• Jumping straight to Reset. You wipe sign in state you didn't need to lose. Always try wsreset.exe and Repair first.
• Running random reinstall scripts. Unofficial scripts often remove packages you need like Xbox dependencies. Stick to built in tools.
• Leaving antivirus web filtering on during testing. Pause it for one launch test. Then add an exception only if that was the block.
• Forgetting date and region. A PC set to the wrong country will fail the license check every single time.
• Deleting the whole Packages folder. Only clear the Store LocalCache if you go manual. Deleting more breaks other apps.
• Skipping reboot after SFC and DISM. The fix doesn't apply fully until you restart. Test only after that reboot.

If you've chased drives disappearing after updates, you already know this rule. Change one thing, reboot, test. Don't stack five fixes and guess what worked.

How to Stop Microsoft Store From Crashing Again

If it's working again, leave the parts it needs alone. If you followed a debloat guide before, don't disable the Microsoft Store Install Service, Windows Update, or BITS again. Those three keep Store licenses and downloads alive in the background.

Our research shows most repeat crashes come back after the same triggers. Use this short maintenance habit and you'll avoid most of them:

• Keep Windows Update on automatic and reboot when it asks
• Keep Set time automatically on so license checks don't fail
• Keep at least 10 to 15 GB free on C so cache can rebuild cleanly
• Update Store apps from Library once a week instead of letting 20 pile up
• Skip registry cleaners and Store removal scripts, they break AppX registration

Pause your VPN for Store updates if you've had blocks before. The same network quirks that cause drops that hit one machine only can stall a big app update and corrupt cache again. If you manage PCs for family, you can read the background on app identity and updates in the Microsoft Learn docs for Store apps.

Create a System Restore Point before major updates too. It takes a minute. It saves you hours if the next build leaves the Store half registered, just like it helps when you're keeping add-on hardware steady across updates.

FAQs About Microsoft Store Keeps Crashing When Launched

Why does Microsoft Store close right after I open it?

That instant close usually means corrupt cache or a failed license check. Run wsreset.exe first, then Repair from Advanced options. If it still closes, check date, region, and VPN blocks before you try Reset.

Will Reset delete my apps and games?

Reset clears Store data, sign in state, and preferences. It does not uninstall all your other apps. You'll need to sign back in and resync licenses.

Back up game saves and app data first to be safe.

What if wsreset.exe does nothing or flashes and closes?

If wsreset.exe opens a blank window then vanishes, run SFC and DISM next. Then re-register the Store with PowerShell as administrator and reboot. If it fails in a new local profile too, run the Store Apps Troubleshooter.

Do I need to reinstall Windows to fix this?

No, not in most cases. In our research, cache clear, Repair, updates, and service fixes solve the bulk of launch crashes. Try a new user profile test first.

Save an in place repair upgrade as your last step before a clean install.