Fix Microsoft Store App Crashes Immediately on Open on Windows 11

Quick fix: Press Win + R, type wsreset.exe, press Enter. The Store cache resets in 30 seconds and the app relaunches. If it still crashes, run Get-AppxPackage Microsoft.WindowsStore | Reset-AppxPackage from elevated PowerShell to fully reset the Store app while preserving installed apps.

You click the Microsoft Store icon. The Store splash appears for a second, then vanishes. No error message. Open Event Viewer and you’ll find an Application Error entry naming WinStore.App.exe. The crash is almost always Store-specific (cache corruption, license check failure, region mismatch) and rarely indicates a deeper Windows problem.

What causes this

The Microsoft Store app is a UWP application with its own package, data, and license cache. Three components must all be healthy for it to launch: package integrity (the app’s files in C:\Program Files\WindowsApps), data cache (per-user data in %LocalAppData%\Packages\Microsoft.WindowsStore_*), and license/identity (Microsoft Account binding and AAD tokens). A failure in any one causes the app to crash silently on startup.

Common triggers: a partially-completed Windows update, a corrupted cumulative update, region/language mismatch, or an expired Microsoft Account cached token.

Method 1: Reset Store cache with WSReset

The first thing to try. Clears the data cache without removing installed apps.

1. Press Win + R, type wsreset.exe, press Enter.
2. A black Command Prompt window appears. Wait 30–60 seconds — the window will auto-close and Microsoft Store will launch.
3. If the Store launches but immediately crashes again, proceed to Method 2. If it stays open, you’re done.
4. For a more thorough reset: open Settings → Apps → Installed apps → search for Microsoft Store → click the three-dot menu → Advanced options.
5. Click Reset. This clears all app data including sign-in tokens. The Store will require sign-in again on next launch.
6. Restart Windows. Open Microsoft Store. Sign in if prompted.

WSReset alone resolves 60–70% of Store crashes. Reset (the bigger hammer) handles most of the rest.

Method 2: Re-register the Microsoft Store package

For when WSReset and the Reset button don’t work.

1. Open Terminal (Admin): right-click Start → Terminal (Admin).
2. Re-register the Store package:

   Get-AppxPackage Microsoft.WindowsStore | Reset-AppxPackage

   This removes the per-user data and re-registers the Store package from the system package store. Installed apps are preserved.

3. If Reset-AppxPackage isn’t available (older PowerShell), use:

   Get-AppxPackage *WindowsStore* | Remove-AppxPackage
   Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

   This unregisters and re-registers the Store for the current user.

4. Reboot. Open Microsoft Store. Sign in.
5. If you see “The package requires installation” or similar error, run Windows Update first — there may be a missing dependency package.

This rebuilds the Store registration without removing apps. Used by Microsoft Support as the standard escalation step.

Method 3: Repair the underlying Windows component store

For when even re-registration fails — indicates deeper system corruption.

1. Open Terminal (Admin).
2. Run:

   DISM /Online /Cleanup-Image /RestoreHealth

   This downloads fresh component-store content from Windows Update. Takes 10–30 minutes.

3. Follow with:

   sfc /scannow

   This applies the now-healthy component store to system files. Takes 10–15 minutes.

4. Reboot.
5. Repeat Method 2’s Reset-AppxPackage command.
6. If still crashing: open Settings → Time & language → Language & region. Confirm Region setting matches your Microsoft Account billing country. A mismatch can cause Store crashes during license check.
7. Sign out of Windows (Start → user icon → Sign out) and back in to refresh the Microsoft Account token cache.

This sequence addresses the deeper causes when the Store package itself is healthy but its dependencies (Windows component store, account services, region) are misaligned.

How to verify the fix worked

• Open Microsoft Store from Start menu. Splash screen leads to home page without crash.
• Navigate to Library. Your installed apps should be listed.
• Click any app entry. The app’s detail page should load with install/update/launch buttons.
• Run Get-AppxPackage Microsoft.WindowsStore | Format-List Status. Status should show Ok.

If none of these work

If the Store still crashes immediately on open after all three methods, the issue is account or service-level. Microsoft Account corruption: switch the Windows account to a local account temporarily (Settings → Accounts → Your info → Sign in with a local account instead). Reboot. Sign back in with the Microsoft Account. This forces a fresh token sync. Required services stopped: open services.msc and verify Microsoft Account Sign-in Assistant, License Manager, Microsoft Store Install Service, Windows Update are all set to Manual or Automatic and not Disabled. Region/language mismatch: Store sometimes crashes when Country/Region in Settings doesn’t match the Microsoft Account billing country — check account.microsoft.com for billing country, then set Settings → Time & language to match. Last resort: Settings → System → Recovery → Reset this PC → Keep my files. This refreshes Windows while preserving documents.

Bottom line: WSReset handles the common cache corruption. PowerShell’s Reset-AppxPackage handles the package-level issues. DISM + SFC handles the deepest layer. One of the three resolves the Store crash without needing a full Windows reset.