PowerShell Fix Microsoft Store: Step-by-step

Start with the Microsoft Store app reset; if it still crashes, shows a black window, or will not reopen, use PowerShell re-registration, and only move to reinstall steps when the Store is missing or the package is damaged. Choosing the wrong fix wastes time and can break app installs, updates, and license sync. This guide walks you through the fastest safe reset first, then the exact PowerShell path for each failure pattern.

Microsoft Store error symptoms explained

Microsoft Store failures usually fall into three patterns: the app crashes or opens to a black window, it refuses to launch after a reset, or it opens but will not install or update apps. The first move is wsreset.exe, because it clears the Store cache without changing your account or installed apps.

What a black window usually means

A black window can happen when the Store cache or app session is not loading correctly. It does not by itself prove that Windows is damaged. Start with the cache reset, then move to re-registration if the Store still fails.

When the Store will not open at all

If the Store does nothing after you click it, or opens and closes immediately, check the app cache and package registration first. If resetting does not change the behavior, confirm the Microsoft Store Install Service is available on your system and then continue with repair steps.

When installs or updates fail instead

If the Store opens but downloads stall, fail, or loop, the issue can be with package registration, service state, or Windows file corruption. In that case, cache reset still comes first, but PowerShell repair and system checks move up the ladder sooner.

Likely causes

Most often, the Store cache is stuck or the app session is broken. Less commonly, the Store package registration is damaged, the required service is unavailable or misconfigured, or Windows file integrity is affecting the app platform.

1. Stuck cache or session: wsreset.exe is the first repair because it clears the Store cache without touching the app package.
2. Broken Store registration: PowerShell can re-register the Store package and rebuild the app manifest entries.
3. Store service issue: the Microsoft Store Install Service may need to be started or rechecked in Services.
4. Windows corruption: if the Store still fails after reset and registration fixes, run SFC and then DISM.

Say your Store turns black for a second and then closes every time you open it. That pattern fits cache or registration trouble better than a full reinstall, so reset first, then re-register the package before touching deeper system tools.

Suppose the Store opens, but every update stops at “pending.” That points away from the app shell and more toward service state or package repair, which is why the service check belongs before reinstall steps.

Microsoft Store fix matrix

Use this matrix to match the symptom to the safest next step. The commands below are exact, and the fallback path tells you when to stop waiting and move on.

Should you start with wsreset.exe?

Yes. Start with wsreset.exe unless the Store is missing entirely. It is the quickest safe reset, it does not require PowerShell, and it often fixes a stalled cache before you touch more invasive repair commands. A blank Command Prompt window can appear while it runs.

Run wsreset from the Run dialog

1. Press Windows key + R.
2. Type wsreset.exe.
3. Press Enter.
4. Wait for the Store to relaunch, or for the blank Command Prompt window to close.
5. If the Store opens normally, stop there and retest downloads.

What the blank window means

A blank Command Prompt window during the reset is normal. The reset may take about 30 seconds to a minute, and longer on slower systems. If nothing happens after that and the Store still fails, move to re-registration instead of repeating the reset over and over.

How do you re-register Microsoft Store with PowerShell?

Open PowerShell as administrator, then re-register the Microsoft Store package with its manifest path built from the installed package itself. Use Get-AppxPackage -AllUsers and AppXManifest.xml to rebuild the Store registration.

Use a copy-safe command

1. Right-click Start and choose Windows Terminal (Admin) or PowerShell (Admin).
2. Confirm the admin prompt.
3. Run this command exactly: Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
4. Wait for the deployment to finish.
5. Open Microsoft Store again and test a small app update.

What to expect while the command runs

PowerShell may show deployment activity or a Processing message while it rebuilds the package registration. That does not mean it is stuck right away. Give it time before assuming failure, then check service state and Windows integrity if it does not finish.

What services should be running for Microsoft Store to work?

Check the Microsoft Store Install Service if the Store still will not launch or install after reset and re-registration. Verify whether it is available, started, and enabled on your system, then adjust it if needed.

Verify service status

1. Press Windows key + R, type services.msc, and press Enter.
2. Find Microsoft Store Install Service.
3. Check whether its status is Running.
4. Open its properties and set Startup type to Automatic if that option is available and the service is not starting as expected.
5. Select Start if the service is stopped.
6. Restart the PC and retest the Store.

What if the service is already running?

If the service is already running, do not force changes just for the sake of changing something. Move to SFC and DISM instead, because deeper Windows corruption can block Store repair even when the service looks correct.

What if PowerShell gets stuck on Processing?

Give it a short wait first. A deployment can remain on Processing while Windows is working through the package. If it still does not move after a reasonable wait, check service state and system integrity before trying another reinstall path.

How long to wait

1. If the command is still moving or the disk activity is active, wait longer.
2. If it has sat unchanged for about 15 minutes, move to the next check.
3. Open services.msc and confirm the Store service is not disabled.
4. Run sfc /scannow.
5. Then run DISM /Online /Cleanup-Image /RestoreHealth.

What to try if it never finishes

Suppose PowerShell sits on Processing after a reboot and the Store service is running. That points toward broader Windows corruption, not just a bad Store package. At that stage, SFC and DISM are the right next checks, not repeated registration loops.

If that didn't work, try this next

If reset, re-registration, and service checks do not fix the Store, move to system repair. Run SFC first, then DISM /Online /Cleanup-Image /RestoreHealth. SFC checks protected system files, and DISM repairs the Windows image when corruption is deeper.

Run SFC and DISM in order

1. Open Command Prompt (Admin) or PowerShell (Admin).
2. Run sfc /scannow.
3. Restart if SFC repairs files.
4. If the Store still fails, run DISM /Online /Cleanup-Image /RestoreHealth.
5. Restart again and retest the Store.

When reinstall becomes the last step

Reinstalling Microsoft Store is the last repair, not the first. If the Store is missing or severely damaged, open PowerShell (Admin), confirm the package with Get-AppxPackage -AllUsers Microsoft.WindowsStore, and if it is present, restore it with Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. If the package is not present, repair Windows with sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth before trying again, as outlined on Microsoft Learn.

Frequently asked questions

Why is microsoft store not working?

Most failures come from a stuck cache, broken registration, or a disabled Microsoft Store Install Service. Start with wsreset.exe, then re-register the Store with Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. If that fails, run sfc /scannow.

How do I fix microsoft store if it keeps crashing?

Open wsreset.exe first, then test the Store again. If it still crashes or shows a black window, open PowerShell as administrator and run the re-registration command for Microsoft.WindowsStore. If the crash remains, check the service and run DISM /Online /Cleanup-Image /RestoreHealth.

What command reinstalls microsoft store

There is no single universal reinstall command that fits every Windows system. Use Get-AppxPackage -AllUsers Microsoft.WindowsStore first to confirm the package is present, then re-register it with Get-AppxPackage -AllUsers Microsoft.WindowsStore | ForEach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. If the package is absent, repair Windows with sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth before trying again.

Why is powershell stuck on processing when reinstalling store?

PowerShell can sit on Processing while the package deployment runs. Wait first. If it does not move after a reasonable wait, check whether the Microsoft Store Install Service is disabled, then run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth.

Should I run wsreset before using powershell?

Yes. Start with wsreset.exe unless the Store is missing. It is the fastest low-risk reset, and the PowerShell re-registration step is the next move only when the cache reset does not fix the crash, black window, or update failure.