Microsoft Store is where you get UWP apps, games, and even some system component updates. When it will not open, it spins, crashes, shows a white screen, or throws a code like 0x80073CFE, 0x8024001E, or 0x80072EFD, people freeze. Most cases fix themselves if you walk the nine steps below.
1, Rule out the network first
Store talks to Microsoft's servers, and a proxy, VPN, or public DNS can block it.
Turn off the VPN or proxy and try once. Switch DNS to a public one like 223.5.5.5 or 119.29.29.29, in Browser Can't Open Web Pages, but WeChat Works. Try another network, a phone hotspot, and if it opens there the problem is your original network.
2, Reset the Store cache (wsreset)
The most common and safest move, it clears Store's local cache.
Press Win + R, type wsreset.exe, Enter. An empty command window appears, clears the cache, and reopens Store. Let it finish.
3, Repair or reset the app itself
Settings, Apps, Installed apps, find Microsoft Store, Advanced options. Click "Repair" first (keeps data), then "Reset" (clears sign-in and cache, does not remove installed apps).
4, Re-register Store in PowerShell
When the cache and a broken component are the issue, re-registering often cures it, in an admin terminal:
Get-AppxPackage -allusers *WindowsStore* | ForEach-Object { Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml" }
Reopen Store after.
5, Run the Windows Store troubleshooter
Settings, System, Troubleshoot, Other troubleshooters, Windows Store, Run. Windows diagnoses and fixes some known config errors.
6, Check the date and time
A wrong system clock breaks HTTPS certificates and Store goes down, and it also breaks https web pages.
Turn on "Set time automatically" and "Set time zone automatically" and force a sync, in Computer Clock Wrong or Not Syncing.
7, Repair system files with SFC and DISM
Corrupted system files drag Store down too.
In an admin terminal run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth. Reboot after.
8, Check proxy and TLS
Settings, Network and Internet, Proxy, turn off "Use a proxy server". In Internet Options (Control Panel), Advanced, Security, tick TLS 1.2 and TLS 1.3. On a corporate network with a forced proxy, whitelist Microsoft domains like storeedgefd.dsx.mp.microsoft.com.
9, Test with a new local account
Sometimes the current user profile is damaged and Store never opens there.
Create a local account and sign in to test Store, in Win11/Win10 Microsoft Account to Local Account. If it works there, the old profile is bad, move your files and retire it.
Error code quick reference
| Code | Meaning | Try first |
|---|---|---|
| 0x80073CFE | Deployment or package corrupted | Step 4 re-register plus Step 3 reset |
| 0x8024001E | Store update component broken | Step 2 wsreset plus Step 4 |
| 0x80072EFD | Cannot connect (network or proxy) | Step 1 plus Step 8 |
| 0x80070005 | Insufficient permission | Run Step 4 as admin |
| 0x80073D23 | Missing package dependency | Re-register plus update to latest |
Still broken, extreme options
Manually reinstall Store: in admin PowerShell run Get-AppxPackage -allusers Microsoft.WindowsStore | Remove-AppxPackage, then recover. For deep system damage, consider a file-keeping reset. If Store stays disabled after reinstall, check Group Policy or MDM for a Microsoft Store block.
Why Store breaks so easily
Store is wired into a stack of system components (AppX, dependency frameworks, licensing services), and damage to any one of them can stop it opening. The usual triggers are an interrupted update, a forced shutdown, or a questionable optimizer tool that touches system apps. So it failing is common, and the nine steps above fix it in place without a reinstall.
A wrong clock is the sneakiest cause. When the certificate date does not match, HTTPS to Microsoft fails silently and Store hangs on a spinner with no code. The time fix in step 6 resolves it, and it also restores access to https web pages that suddenly stop loading.
When there is no error code
Beyond codes, Store has no-error but unusable modes. A white screen is usually cache or a GPU driver issue, wsreset then update the driver. An endless spinner is mostly network or proxy, step 1. Opening then crashing instantly points to a damaged user profile, verify with the new-account step 9.
Habits that prevent recurrence
Do not let one-click cleaner tools touch system apps and components. After a feature update, if Store misbehaves, run wsreset and reboot before editing the registry. In a corporate setting where Store is disabled by policy, an ordinary user cannot change it, ask IT to enable it.
A few practical notes
The re-register command in step 4 is safe and non-destructive, it repairs the app manifest without touching your data, so try it before the harder steps. The reset in step 3 clears sign-in and cache but does not remove installed apps, use it when re-register alone fails.
If Store opens but downloads stall at a percentage, the issue is usually the delivery optimization cache or a stuck update, not Store itself. Clear the cache with wsreset, then check Windows Update for a hung package. In rare cases a clean boot reveals a third-party download manager or VPN client interfering with the delivery service.
Do not reach for a reinstall too early. A full reset or clean install is the last resort here, because the nine steps above resolve the overwhelming majority of Store failures without touching your other apps or files.
One more thing
Store also delivers updates for built-in apps like Calculator, Photos, and Mail, so a broken Store quietly starves those of fixes, and restoring it fixes more than the shopfront itself. If wsreset appears to do nothing and its window never shows, the Store process may be stuck in Task Manager, end it there, then run wsreset again.
These steps apply to both Windows 11 and Windows 10. The menu labels differ slightly in wording, but the order is the same, so the guide works on either version.
Summary
Nine times out of ten, Store opens again with the wsreset, repair or reset, and re-register trio, and the rest are network, clock, or profile issues. Walk the nine steps and you usually rescue it without a reinstall.