The Microsoft Store breaking after the 24H2 update is frustrating precisely because the errors are so unhelpful: “Something happened on our end,” a hex code like 0x80070005 or 0x803F8001, or the Store just spinning forever. You know the internet works, you know your account is fine, but the Store disagrees.

On 24H2 specifically, the pattern is consistent: the feature update touches the app platform underneath the Store, and on some machines the Store’s cache, package registration, or license sync doesn’t survive the trip. The fixes below go from the 30-second cache clear to the deeper repairs, and one of them will match your error.

Why this happens

  • Corrupt Store cache: The most common cause. The cache that holds temporary Store data gets damaged during the 24H2 upgrade, and the Store errors out instead of recovering.
  • Broken app package registration: 24H2’s app-platform changes can leave the Store’s registration pointing at the wrong files or versions.
  • License sync failures: The Store can’t verify your app licenses against your Microsoft account — common right after a feature update changes the device identity.
  • Wrong date, time, or region: The Store’s servers reject connections when your clock is off, producing cryptic errors instead of a helpful message.
  • Corrupt system files: Damage to the app-platform components the Store depends on.
  • Third-party antivirus or VPN interference: Security software and VPNs intercepting Store traffic or blocking its background services.
  • User profile corruption: Store data in your profile is damaged while the system-wide installation is fine — hence “works in a new account.”

How to fix it

Work through these in order — the cache clear alone fixes most cases.

Fix 1: Clear the Store cache with wsreset

The fastest fix and the most effective first step.

  1. Press Win + R, type wsreset.exe, and press Enter.
  2. A blank Command Prompt window appears — leave it alone. After 30-60 seconds the Store opens automatically with a fresh cache.
  3. Try downloading or updating an app. If the error is gone, you’re done.
  4. If wsreset itself errors out or changes nothing, the problem is deeper than cache — continue.

Fix 2: Check date, time, region — and disconnect VPN/antivirus interference

The Store is picky about clocks in a way browsers aren’t, and security software loves intercepting its traffic.

  1. Open Settings > Time & language > Date & time.
  2. Turn on Set time automatically and Set time zone automatically, then click Sync now.
  3. Go to Time & language > Language & region and confirm your region matches where your Microsoft account is registered.
  4. Disconnect any VPN — the Store’s license servers are region-sensitive, and VPNs cause exactly the cryptic errors you’re seeing.
  5. Temporarily disable third-party antivirus and retry the Store (Windows Security stays active and doesn’t interfere). If it works, add the Store as an exception in your security product.
  6. Restart the Store and test. Clock, region, VPN, and antivirus account for a large share of “mysterious” Store errors.

Fix 3: Run the Store Apps troubleshooter

Windows can diagnose its own Store problems.

  1. Open Settings > System > Troubleshoot > Other troubleshooters.
  2. Find Windows Store Apps and click Run.
  3. Apply whatever it recommends — it commonly resets permissions and re-registers components.
  4. Microsoft documents additional Store repair steps at Microsoft’s Windows support hub .

Fix 4: Repair or reset the Microsoft Store app

The built-in app repair, no commands needed.

  1. Open Settings > Apps > Installed apps, find Microsoft Store.
  2. Click the three dots > Advanced options.
  3. First click Repair and test the Store.
  4. If it still errors, go back and click Reset — this clears all Store data (not your apps) and usually resolves 0x80070005 and license errors.

Fix 5: Re-register the Store with PowerShell

For a Store that won’t open at all or crashes instantly.

  1. Open Terminal (Admin) (Win + X > Terminal (Admin)).
  2. Run: Get-AppXPackage -AllUsers *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  3. Wait for completion, ignoring errors about already-registered packages.
  4. Restart and test. This rebuilds the registration 24H2 may have damaged.

Fix 6: Sign out and back into the Store

License sync failures need a fresh sign-in.

  1. Open the Store, click your profile icon, and Sign out.
  2. Close the Store completely (end it in Task Manager to be sure).
  3. Reopen, sign back in with your Microsoft account, and wait a minute for licenses to sync.
  4. Then try the failing download again. For the “won’t open” variant specifically, see Windows Store not opening in 24H2 .

Fix 7: Repair system files

When the app platform underneath is damaged.

  1. In Terminal (Admin), run sfc /scannow.
  2. Then DISM /Online /Cleanup-Image /RestoreHealth.
  3. Restart and test. If Store errors started immediately after the 24H2 upgrade, this repairs upgrade damage.

Fix 8: Test a new user profile

The final isolation step.

  1. Create a new local account (Settings > Accounts > Other users > Add account) and sign into it.
  2. Open the Store there. If it works, your original profile’s Store data is corrupt.
  3. You can try repairing it by deleting the profile’s Store cache folders, but migrating to the new profile is more reliable.
  4. For the post-update error-code family, Microsoft Store error after a Windows 11 update covers related codes with the same toolkit.

Closing

Microsoft Store errors on 24H2 look cryptic but they’re almost always one of three things: a corrupt cache (wsreset), a broken registration (PowerShell re-register), or a license sync failure (sign out/in). Work the list top to bottom and the Store comes back — and once it’s healthy, leave the cache alone and let updates install promptly, since most of these corruptions trace back to interrupted updates in the first place.

One last habit worth building: when the Store misbehaves again in the future, start with wsreset before anything else. It takes thirty seconds, fixes the most common cause, and tells you immediately whether you’re dealing with cache (fixed) or something deeper (not fixed) — which makes the rest of the troubleshooting dramatically faster.

Frequently asked questions

Why does the Microsoft Store show errors on Windows 11 24H2?
The 24H2 update changed several app-platform components the Store depends on, and upgrades sometimes leave the Store’s cache, registration, or licensing in a broken state. Corrupt cache and broken package registration cause the vast majority of cases.
What does error 0x80070005 mean in the Microsoft Store?
It’s an access-denied error — the Store can’t read or write files it needs, usually because permissions on its cache or package folders got mangled during the 24H2 upgrade. Resetting the Store app and repairing system files resolves it.
Will resetting the Microsoft Store delete my installed apps?
No. Resetting (or wsreset.exe) only clears the Store’s own cache and settings — your installed apps, games, and purchases are tied to your Microsoft account and stay put. You’ll just need to sign back in.
Why does the Store work on a new user account but not mine?
That points to corruption in your user profile’s Store data — the per-user cache, licenses, or app registration. Either repair the profile’s Store registration with PowerShell or migrate to the new profile.