Why Microsoft Store Cannot Open a Specific Page on Windows 11

Quick fix: Open Run (Win+R), type wsreset.exe, press Enter. Store resets and reopens to home. If specific page still won’t open: re-register the Store package via PowerShell (Admin): Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"}. Reboot. Sign in to Microsoft account. Page should open.

Microsoft Store sometimes fails to open a specific app page or category. Common causes: cache corruption, region mismatch, network restriction, app removed from Store, license issues. Reset cache first; re-register Store if persistent.

What causes this

Microsoft Store uses cache for app metadata, ratings, screenshots. Cache can corrupt or lag behind server state. If cache is broken, specific pages may show:

• Spinner that never resolves.
• “Page can’t be displayed” error.
• Blank page.
• “Try again” with no progress.

Method 1: Reset Store cache via wsreset

The standard route.

1. Close Microsoft Store completely.
2. Open Run dialog: Win+R.
3. Type wsreset.exe and press Enter.
4. A black Command Prompt window opens. Wait 30 seconds. Microsoft Store reopens.
5. Try the specific page again.
6. If page now loads: cache was the issue.
7. If still broken: continue to Method 2.
8. Note: wsreset preserves apps but clears local cache, search history, recent items.

This is the standard cache reset.

Method 2: Re-register Microsoft Store

For deeper repair.

1. Open PowerShell as Admin.
2. Re-register Store package:

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

   This re-registers Store for all users.

3. Wait for completion. Output is brief.
4. Restart PC.
5. Sign in to Microsoft account. Open Store.
6. For specific app issue: also re-register the framework dependency: Microsoft.WindowsAppRuntime.1.x packages.
7. To find dependency versions:

   Get-AppxPackage Microsoft.WindowsAppRuntime*

8. If specific app affected by mismatch: also: Get-AppxPackage -AllUsers Microsoft.VCLibs.140.00.UWPDesktop | Foreach {Add-AppxPackage -Register "$($_.InstallLocation)\AppxManifest.xml" -DisableDevelopmentMode}

This is the comprehensive re-register.

Method 3: Check region and network connectivity

For environment-level issues.

1. Region mismatch: app may not be available in your Microsoft account region.
   • Visit account.microsoft.com → Edit profile → Country/region.
   • Region changes locked for 90 days. Plan accordingly.
2. Time/Date wrong: SSL certs require accurate time. Settings → Time & language → Set time automatically. Re-sync.
3. DNS issues: try different DNS:

   netsh interface ip set dns "Wi-Fi" static 8.8.8.8
   netsh interface ip add dns "Wi-Fi" 1.1.1.1 index=2

   Or via Settings → Network & internet → adapter → DNS server assignment.

4. Proxy / VPN: disable. Some VPNs block Store traffic.
5. Firewall: Windows Defender Firewall → Allow an app → Microsoft Store ticked.
6. Network reset: Settings → Network & internet → Advanced network settings → Network reset. Reverts to defaults; may resolve.
7. Specific page sun-set: developer removed app. App page returns 404 essentially. Check Microsoft Store community.

This is the environment check.

How to verify the fix worked

• Specific app page loads with full details, screenshots, ratings.
• Install / Get button appears.
• Other Store pages also load correctly.
• No more spinning / blank pages.

If none of these work

If still broken: Microsoft Store service: services.msc → Microsoft Store Install Service. Restart. For corporate-managed PCs: IT may block specific apps via Intune. Contact IT. For sign-in issues: sign out completely from Microsoft Store, sign back in. For specific apps disappearing: developer pulled app. Find alternative. For chronic Store failures: in-place Windows upgrade via Media Creation Tool. Repairs Store and related components. For Windows 11 Insider Preview: Store on Insider builds sometimes lags behind. Roll back to stable. For 0x80073CF9 errors: licensing issue. slmgr /rilc reinstall licenses. Last resort: clean reinstall via DISM: dism /online /add-package /packagepath:[path to Store msixbundle] with package downloaded from Microsoft.

Bottom line: wsreset.exe from Run dialog. If that doesn’t fix it: re-register Store via PowerShell. Check region, DNS, time, network. Specific apps may be region-restricted.