You click the Microsoft Store icon. Nothing happens — or it flashes open and instantly closes, or it hangs on the loading spinner forever. The whole repair usually takes under ten minutes. Meanwhile everything else on your ASUS laptop works fine. It’s a small problem that blocks a big thing: installing and updating apps.

The Store is just another AppX app with a cache, a registration, and dependencies. When one of those breaks, the fixes are methodical and quick. Work through them in order.

Why this happens

  • Corrupted Store cache. The number-one cause — stale or damaged cache data crashing the app on launch.
  • Broken AppX registration. Windows updates or debloating breaking the Store’s package registration.
  • Wrong date, time, or region. The Store validates certificates and licensing against the clock; a wrong date breaks it silently.
  • Stuck Windows Update components. The Store depends on update services for downloads and licensing checks.
  • Antivirus or firewall blocking Store traffic. Security software intercepting the Store’s connections.
  • Corrupted user profile. Profile-level app-data corruption affecting only one account.
  • Pending Windows updates. Half-applied updates leaving Store dependencies mismatched.
  • Corrupted Store license sync. The Store’s license cache for your account can desync, especially after switching Microsoft accounts on the device.
  • Armoury Crate network tweaks. Crate’s network-optimization features occasionally interfere with the Store’s connections, though this is uncommon.

How to fix it

Work through these in order — the first two fix the large majority of cases.

Fix 1: Reset the Store cache with WSReset

The fastest fix and the right first step. Cache corruption is behind the majority of Store launch failures, which is why every technician starts here.

  1. Press Win + R, type wsreset.exe, and press Enter.
  2. A blank Command Prompt window appears — leave it alone. After 30–60 seconds it closes and the Store launches automatically.
  3. If the Store opens, you’re done. If nothing happens or it still crashes, move to Fix 2.
  4. Note: WSReset clears only the Store’s cache, not your apps or account.

Fix 2: Repair or reset the Store app in Settings

One level deeper than the cache reset.

  1. Go to Settings > Apps > Installed apps.
  2. Find Microsoft Store, click the … menu, and choose Advanced options.
  3. Click Repair first and test. If it still won’t open, come back and click Reset.
  4. Reset clears the app’s data (not your installed apps). Test the Store after each step.

Fix 3: Check date, time, and region

A wrong clock silently kills Store licensing.

  1. Go to Settings > Time & language > Date & time.
  2. Turn on Set time automatically and Set time zone automatically, then click Sync now.
  3. Go to Settings > Time & language > Language & region and confirm the region matches where you actually are.
  4. Restart the Store. Certificate validation fails with even a moderately wrong date, and the Store just refuses to launch.

Fix 4: Re-register the Store with PowerShell

Fix broken AppX registration directly. This is the same repair Windows itself attempts during major updates, run manually for when the automatic attempt failed.

  1. Open Terminal (Admin) from Win + X.
  2. Run: Get-AppXPackage -AllUsers *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  3. Wait for completion, then restart the laptop.
  4. This is the fix that resolves Store breakage after Windows updates in most remaining cases.

Fix 5: Run the Store troubleshooter and check Update services

Fix the dependencies the Store relies on. The Store doesn’t download anything by itself — it leans on Windows Update services and BITS, so a stuck dependency looks exactly like a broken Store.

  1. Go to Settings > System > Troubleshoot > Other troubleshooters and run Windows Store Apps.
  2. Press Win + R, type services.msc, and confirm Windows Update, Background Intelligent Transfer Service, and Cryptographic Services are running.
  3. If any are stopped, start them and set them to Automatic (or Manual for BITS, which is its default).
  4. Then check Settings > Windows Update and install everything pending — Store fixes often ride along with cumulative updates.

Fix 6: Check antivirus and firewall interference

Security software sometimes blocks the Store’s traffic or files.

  1. Temporarily disable your third-party antivirus (keep Windows Security on) and test the Store.
  2. If it opens, add the Store as an exception or check the firewall rules — don’t leave protection off.
  3. Also check any VPN or proxy: disconnect it and test, since the Store is sensitive to intercepted connections.

Fix 7: Test with a new user profile

Isolate profile corruption.

  1. Create a local test account under Settings > Accounts > Other users.
  2. Sign in and try the Store. If it works there, your main profile’s app data is corrupt.
  3. You can either migrate to the new profile or try repairing the old one — but for Store-only issues, migration is overkill; try Fix 8 first.

Fix 8: Repair system files and reinstall the Store

The deepest repair short of a reset.

  1. In Terminal (Admin), run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  2. Restart, then re-run the Fix 4 PowerShell re-registration.
  3. As a final step, check Microsoft’s Store troubleshooting guidance for any current known issues with your Windows build.

For Store issues on other brands, see our Lenovo , Acer , and Dell variants, or the post-update Store guide .

Closing

A dead Microsoft Store is almost always a cache or registration problem — WSReset and the PowerShell re-registration fix the vast majority of cases in minutes. Check the clock, keep Update services healthy, and the Store goes back to being the boring, reliable app installer it’s supposed to be. If the Store breaks again after the next Windows update, run WSReset before anything else — it’s a thirty-second fix for a recurring annoyance.

Frequently asked questions

Why won't the Microsoft Store open on my ASUS laptop?
The usual causes are a corrupted Store cache, broken AppX registration (often after a Windows update), incorrect date/time or region settings, a stuck Windows Update service the Store depends on, or third-party antivirus blocking Store traffic. On ASUS laptops, Armoury Crate updates occasionally coincide with the breakage, but the Store fixes are the same regardless.
Will resetting the Store delete my installed apps?
No. WSReset and the Settings-based repair/reset only clear the Store app’s own cache and data — your installed apps, games, and purchases are tied to your Microsoft account and stay put. The PowerShell re-registration also leaves your apps alone. Your library is safe.
The Store opens but downloads are stuck. Is that the same problem?
Related but distinct — that’s usually the delivery or update pipeline rather than the Store app itself. Run WSReset first, then check Settings > Windows Update for pending updates, and try the Windows Store Apps troubleshooter. Stuck downloads also respond well to signing out and back into the Store.
Do I need a Microsoft account for the Store to work?
You need one to download apps, but the Store app itself should open without it. If the Store won’t even launch, the account isn’t the issue — work through the cache and registration fixes. Sign in only matters once the app opens and you try to acquire something.