Windows command guide
Microsoft Store and AppX Repair Bundle for Broken Built-In Apps
A broken Microsoft Store often points to a wider built-in app platform problem, not only a storefront issue. When built-in apps disappear, refuse to open, or throw package registration errors, a better response is a small bundle: clear the Store cache, re-register AppX packages, and then verify protected files with SFC.
This guide is written around the specific symptom-command match for run a microsoft store and appx repair bundle, not as a generic dump of terminal lines. That makes the page more useful for real troubleshooting and reduces the chance of running the wrong repair step.
wsreset.exe
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
sfc /scannow
Best place to run it
Elevated PowerShell is the right execution context for this page. Because this repair touches protected Windows state, a normal unelevated shell can return misleading access errors or partial results.
Fast repair workflow
- Start from the exact symptom on this page: The Microsoft Store does not open or closes immediately
- Run the primary repair line exactly as shown: wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow.
- This workflow is tuned for this repair, so avoid mixing it with unrelated repair commands too early.
- Reboot if the servicing stack or protected files were changed, then retry the original Windows action.
- Escalate only after reading the output, usually toward CBS.log, DISM source repair, or Windows Update-specific repair.
Copyable wrapper script
Use this wrapper when you want the page command inside a clearer script block with start and finish prompts.
$ErrorActionPreference = "Continue"
Write-Host "Run this PowerShell block in an elevated window before trusting the result."
Write-Host "Starting targeted Windows repair step..."
wsreset.exe
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
sfc /scannow
Write-Host "`nReview the output above before moving to the next fix."
Verification commands after the repair
These follow-up commands help you check whether the repair actually changed the Windows state that matters, instead of assuming success from a single line.
findstr /c:"[SR]" %windir%LogsCBSCBS.log
sfc /verifyonly
What problem this bundle is trying to solve
It targets Store and built-in app platform failures where the Store itself, packaged apps, or registration state are damaged.
- The Microsoft Store does not open or closes immediately.
- Built-in apps fail after updates, profile issues, or package errors.
- Package registration problems appear across more than one app.
How the bundle works
The first step clears Store cache state. The second re-registers packaged apps using their manifest locations. The final SFC scan checks whether protected Windows files are also contributing to the breakage.
When it makes sense to run it
Use it when the issue affects the Store or multiple built-in apps, not just one third-party package installation.
Before you run this command
- Open an elevated Command Prompt or PowerShell window before running wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow.
- Confirm that the symptom really matches this guide, especially if you are seeing signs such as: the microsoft store does not open or closes immediately.
- Keep any exact DISM, SFC, CBS, or Windows Update error output because those details matter in the next step.
What result to expect
After running wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow, compare the result against the symptom that brought you here. The most useful checkpoint is whether the microsoft store does not open or closes immediately becomes less frequent, changes form, or produces a clearer error message. A command page is stronger when it helps you verify a real change instead of just assuming the line must have worked.
How to verify that it worked
The best verification step after wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow is to repeat the action that previously triggered the problem. If built-in apps fail after updates, profile issues, or package errors still appears in exactly the same way, the command probably was not the whole answer and you should move to the next targeted check instead of assuming the page is finished.
Why administrator rights matter here
This command changes system integrity and component corruption. Run it in an elevated shell so Windows can apply the repair instead of only returning an access or privilege error.
Before you run it
Open PowerShell as administrator for the AppX registration step. The registration pass can produce a lot of output, and some lines may refer to packages that are not relevant to the active problem.
When this is probably the wrong fix
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.
What to do if it does not help
If wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow does not improve the microsoft store does not open or closes immediately, move to the next repair step that matches the same symptom family instead of piling on random commands. The best follow-up depends on whether the failure is mainly about system integrity and component corruption.
Frequently asked questions
Should I use wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow for this exact Windows symptom?
Use it when the behavior on your PC lines up with the repair target on this page: It targets Store and built-in app platform failures where the Store itself, packaged apps, or registration state are damaged.
What should I check right after wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow?
Check whether the original trigger still reproduces the same failure. For this page, a useful checkpoint is whether the microsoft store does not open or closes immediately becomes less frequent, changes form, or points you toward a more specific next step.
When should I not rely on wsreset.exe Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} sfc /scannow alone?
This is not the right first fix for a single third-party app bug, a browser-only issue, or obvious hardware failure. Use it when the symptom points to Windows image health, recurring update corruption, or protected system files.