Microsoft Store not working on Windows 11 — apps won’t download, the Store won’t open, or error codes appear whenever you try to install anything — is fixable in almost every case. The challenge is that the Store’s error messages are often vague, so knowing which fix to try first makes a big difference. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
Before anything else: check if you’re signed in. Settings → Accounts → Your info — confirm a Microsoft account is active. The Store requires a Microsoft account; a local account won’t authenticate for downloads. If you’re signed in: try signing out and back in before running any fixes.
The fastest fix: reset the Microsoft Store
This resolves the majority of Store problems — a corrupted cache causes the Store to behave erratically or refuse to open. Win+R → type wsreset.exe → Enter. A blank Command Prompt window opens and runs for about 30-60 seconds, then the Store opens automatically. That’s the entire fix. If the Store now works: you’re done.
Error code lookup — what’s actually failing
The Store shows error codes that point to specific issues:
| Error Code | Meaning | Quick fix |
| 0x80073CF9 | Install error — app installation failed | wsreset → run Windows Store Apps troubleshooter |
| 0x80072EFD | Network connection issue | Check internet → sign out/in → reset Store |
| 0x80070005 | Access denied — permissions | Run Store as administrator; check account type |
| 0x803F8001 | App not available in your region or account type | Check app availability; confirm account region |
| 0x80070422 | Windows Update service issue affecting Store | Start Windows Update and related services |
| 0xC002001B | License acquisition failed | Sign out → sign in; re-link account |
Fix 1: Date and time
This sounds too simple to be real, but an incorrect system clock causes Store authentication to fail silently. Microsoft’s servers reject tokens where the timestamp differs too much from the server time. Settings → System → Date and time → toggle “Set time automatically” off → back on → Sync now. If the clock was off: Store authentication often restores immediately after the sync.
Fix 2: Sign out and back into your Microsoft account
Store authentication tokens expire or become invalidated — particularly after password changes or account security events. Settings → Accounts → Your info → “Sign in with a Microsoft account instead” (if on local account), or → Email and accounts → Microsoft account → Manage → Sign out. After signing out: restart → sign back in → test Store.
Fix 3: Windows Store Apps troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → Windows Store Apps → Run. This automated troubleshooter checks for common Store problems including service issues, package corruption, and registration errors. It’s worth running after wsreset if the reset alone didn’t resolve everything.
Fix 4: Re-register the Microsoft Store
When the Store is corrupted beyond what wsreset can clear: re-registering it from scratch works. Administrator PowerShell:
Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}
After running: restart → test Store. This re-registers all Store components without uninstalling and reinstalling.
Fix 5: DNS and network
The Store requires access to specific Microsoft domains. A DNS misconfiguration or network restriction blocks these connections, causing download failures or the Store to open but never load content. Administrator Command Prompt:
netsh winsock reset
ipconfig /flushdns
Restart. Also: disconnect any VPN before testing — VPN routing sometimes breaks Store’s connection to Microsoft’s CDN.
Fix 6: Windows Update
The Store and Windows Update share infrastructure. Settings → Windows Update → Check for updates → install all pending updates. Updates sometimes include Store component fixes. Also check whether Windows Update itself is working — a broken Update service affects the Store’s ability to download and install apps.
Our guide on Windows Update issues covers the service dependencies that also affect Store. For Store errors on managed corporate devices where IT controls app policies, our app troubleshooting guide covers the enterprise policy approaches. Microsoft’s Store troubleshooting documentation covers the complete list of Store error codes and specific resolution steps for less common errors.
Apps stuck on “Pending” or “Installing”
A download that gets stuck at 0% or at some intermediate percentage indefinitely is a common Store problem. Usually caused by a previous failed download blocking the queue. Open the Store → click your profile icon → Downloads → pause all downloads → clear any that are stuck → restart the specific download. If pausing doesn’t help: Settings → Apps → find partially-installed apps → uninstall them → retry from scratch.
Store opens but shows blank/empty content
If the Store opens but the content area is blank, or searching shows no results: the Store’s web components failed to load. This is different from a connection problem — it’s usually the rendering component. Try:
- Signing out of the Store (profile icon → Sign out) → restarting → signing back in
- If that doesn’t work: check whether a VPN or proxy is filtering Store content
- Check Windows’ date and time (as above) — blank Store content is sometimes caused by time mismatch preventing CDN authentication
Store missing from Windows 11
On some Windows 11 builds (particularly enterprise editions or debloated custom installs), the Microsoft Store may not be installed at all. Administrator PowerShell:
winget install "Microsoft.Store" --id 9WZDNCRFJBMP --source msstore
Or download the Store MSIXBUNDLE from Microsoft and install manually. Enterprise Windows 11 editions sometimes specifically exclude the Store — check with IT whether the organisation’s policy permits reinstalling it.
Metered connection blocking Store downloads
If your internet connection is marked as “Metered” in Windows: the Store by default doesn’t download large apps in the background. Settings → Network and internet → your connection → confirm “Metered connection” is Off for your home connection. Store updates and new downloads proceed normally once metered is disabled.
Specific app won’t install from the Store
When most apps install but one specific app consistently fails:
- Check whether the app is available for your Windows edition (some apps are Home-only, some Pro-only)
- Check region restrictions — some apps are region-locked and not available in all countries
- Look for the same app in a different format — many apps available in the Store also have a traditional installer from the publisher’s website that may install more reliably
- Check whether the app requires specific hardware (camera, GPS, specific sensors) that the current device doesn’t have
Store updates failing for existing apps
If installed Store apps won’t update but new installs work (or vice versa): the app’s current installation is registered incorrectly. For a specific app that won’t update: uninstall it → reinstall from the Store → let the Store install the current version fresh. This bypasses the corrupted update state for that specific app.
For all apps failing to update: the Store’s update mechanism has a broader issue. Re-registering the Store (Fix 4 above) or a full Windows repair install resolves update failures that persist through wsreset.
Corporate environment Store access
In enterprise Windows 11: the Microsoft Store can be restricted or completely disabled via Intune or Group Policy. Signs: the Store is visually present but shows “Microsoft Store is blocked” or “This app can’t be installed” for everything. IT controls these settings through Group Policy (Computer Configuration → Administrative Templates → Windows Components → Store) or Intune app management policies.
For enterprise users who need a specific app: the alternative is getting IT to deploy the app through Intune or SCCM rather than through the public Store. Enterprise app deployment gives IT more control over what’s installed while making apps available to users who need them.
Windows Store App Reset — deeper than wsreset
Settings → Apps → Installed apps → search “Microsoft Store” → three dots → Advanced options → Reset. This is a deeper reset than wsreset — it removes all local Store data including the authentication tokens, download history, and preferences. After this reset: sign in fresh and test. This level of reset resolves Store problems that wsreset doesn’t catch.
Also on the same page: “Repair” (fixes installation issues without resetting data) → try Repair before Reset if you want to preserve preferences.
SFC and DISM for Store infrastructure
Microsoft Store depends on Windows Component Store infrastructure that can be corrupted by failed updates or disk errors. Administrator Command Prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Run DISM first (repairs the component store), then SFC (repairs individual files). After both complete and the machine restarts: test the Store. If corruption was present: the Store typically returns to normal operation after these repairs without needing additional Store-specific steps.
Quick summary: Microsoft Store troubleshooting in order
- wsreset.exe (Win+R → wsreset.exe) — resolves most cache-related Store issues, 1 minute
- Date/time sync — fixes authentication failures, 30 seconds
- Sign out/in to Microsoft account — refreshes expired tokens, 2 minutes
- Windows Store Apps troubleshooter — automated fixes for service issues, 2 minutes
- Re-register Store (PowerShell command) — fixes deeper registration issues, 2 minutes
- DISM + SFC — repairs component store corruption, 20-30 minutes
The wsreset alone resolves approximately 70% of Microsoft Store problems. Date/time sync resolves a significant portion of the remainder. If both of those don’t work: the error code in the Store is the most useful next piece of information to look up, as it narrows the remaining investigation to a specific cause.
For IT teams managing Microsoft Store issues at scale: the Store for Business (now part of Microsoft Intune’s app management) provides a more controlled path for app deployment than the public Store. Apps can be approved, deployed automatically to specific user groups, and managed centrally without users needing direct Store access. This is worth knowing when individual Store troubleshooting doesn’t solve persistent problems in managed environments — the root cause may be the deployment model rather than a technical failure.
Microsoft Store on LTSC (Long-Term Servicing Channel)
Windows 11 Enterprise LTSC (Long-Term Servicing Channel) doesn’t include the Microsoft Store by default. This is by design for enterprise environments where app stability over years is the priority. Installing the Store on LTSC is possible but unsupported by Microsoft. If you’re on LTSC and need apps that are only available through the Store: consider whether the traditional installer version from the publisher exists (most popular apps have non-Store installers), or switch to a non-LTSC Windows 11 edition that includes the Store natively.
Store and Windows Insider
Windows Insider builds occasionally have Store issues where certain features don’t work correctly in the preview build before they’re refined for release. If Store problems appeared after enrolling in Windows Insider: check the Insider community (insider.windows.com) for known Store issues in the current build. Rolling back to the stable channel resolves Insider-related Store failures.
Checking Store service dependencies
The Microsoft Store relies on several Windows services. Win+R → services.msc → confirm these are Running with Automatic startup:
- Windows Update (wuauserv) — needed for app updates
- Background Intelligent Transfer Service (BITS) — handles background downloads
- Cryptographic Services — needed for package verification
- Microsoft Store Install Service — directly responsible for Store installations
If any of these are stopped: the Store may open but fail during download or installation without a clear error. Starting the stopped service and retrying often resolves download failures that don’t show a specific error code.
Windows Update cache affecting Store
Because the Store and Windows Update share infrastructure, a corrupted Windows Update cache sometimes prevents Store downloads. Administrator Command Prompt → stop Windows Update service → clear the SoftwareDistributionDownload folder → restart the service → test Store. The same cache clear that fixes Windows Update failures often also unblocks Store downloads.
Microsoft Store problems are worth solving even if you rarely buy apps — many Windows 11 system components (including the Photos app, Calculator, and various system tools) are installed through the Store infrastructure and receive updates through it. A broken Store means these components stop updating. The wsreset fix is so quick and effective that it’s worth running as a first response to any unusual system app behaviour, not just explicit Store errors.
One final note: the Microsoft Store has improved significantly in Windows 11 compared to its Windows 8/10 predecessors. Problems are less frequent, but when they do occur: the wsreset command and date/time sync remain the consistently most effective two-step fix. Knowing just these two fixes resolves the vast majority of real-world Store problems before needing any of the more involved approaches above.
For users who have tried everything listed here and the Store still doesn’t work: the nuclear option is a Windows repair install (mount the Windows 11 ISO, run setup.exe, choose to keep files and apps). This replaces all Windows system files including Store infrastructure without affecting user data or applications. It’s more thorough than DISM/SFC and resolves corruption that those tools can’t reach. Repair installs take 30-60 minutes but are reliably effective when all other approaches have been exhausted. Our guide on OneDrive Sign-In Error covers an adjacent issue.
