A focused Windows recovery utility for repairing Microsoft Store, App Installer, BITS, Delivery Optimization, and Store-related update problems.
Overview | Screenshots | What It Fixes | Usage | Recovery Modes
MSStore Repair is a Windows PowerShell-based repair utility designed to recover Microsoft Store functionality when the Store, app updates, or app installations become stuck, broken, or unreliable.
It provides a guided terminal interface with three repair levels:
- Soft Recovery for quick cache and Store service repair.
- Default Recovery for common Store, BITS, Delivery Optimization, App Installer, and package registration issues.
- Hard Recovery for deeper Windows Update backend, system file, and network stack repair.
The main recovery tool is recovery.ps1. A small recovery.bat launcher is included for users who prefer opening the tool from File Explorer.
MSStore Repair is useful when the Microsoft Store appears installed but behaves incorrectly, downloads never progress, app updates remain pending, or Windows Store components need to be re-registered.
MSStore Repair is intended to help with Store-related problems such as:
- Microsoft Store download stuck at 1%.
- Microsoft Store stuck on Pending, Downloading, Starting download, or Acquiring license.
- Microsoft Store does not open correctly.
- Microsoft Store opens but app installation or updates fail.
- Store app updates do not progress from the Library page.
- App Installer-related problems affecting
.appx,.msix, or Microsoft Store package handling. - Broken or stale Microsoft Store cache.
- Broken Store package registration.
- BITS queue problems that affect app downloads.
- Delivery Optimization cache problems.
- Windows Update backend issues that can affect Microsoft Store downloads.
- DNS or Winsock issues that may prevent Store services from communicating correctly.
- Corrupted system files that can indirectly affect the Microsoft Store.
This tool is not a replacement for Windows reinstall or official Microsoft support, but it covers many common repair paths that are usually performed manually.
MSStore Repair performs a staged recovery process depending on the selected mode.
At a high level, it can:
- Require Administrator privileges before making system changes.
- Preview actions with optional dry-run mode before changing Windows settings.
- Attempt to create a Windows restore point.
- Close active Microsoft Store processes.
- Start and configure required Windows services.
- Reset the Microsoft Store cache with
wsreset.exe. - Remove local Microsoft Store cache directories.
- Reset BITS jobs.
- Clear Delivery Optimization cache.
- Reset parts of the Windows Update download backend.
- Check Store-related AppX package existence and manifests before attempting repair.
- Re-register Microsoft Store related AppX packages only when a valid manifest exists.
- Run DISM health restoration.
- Run System File Checker.
- Reset DNS and Windows network stack settings.
- Open Microsoft Store after recovery.
- Write a repair log to the Desktop.
The generated log is saved here when writable:
%USERPROFILE%\Desktop\MicrosoftStoreRecovery.log
If the Desktop log path is locked, MSStore Repair falls back to a log file beside recovery.ps1.
| Mode | Best For | What It Does | Estimated Time |
|---|---|---|---|
| Soft Recovery | Small Store glitches, cache problems, Store not opening correctly. | Starts required services, resets Store cache, cleans user Store cache, and re-registers Store-related apps. | Fast |
| Default Recovery | Downloads stuck at 1%, pending updates, App Installer issues, Store repair after failed updates. | Includes Soft Recovery, then resets BITS, Delivery Optimization, download queues, and related Store delivery components. | Moderate |
| Hard Recovery | Persistent Store failures, broken Windows Update backend, system corruption symptoms, repeated Store install failures. | Includes Default Recovery, then resets Windows Update cache areas, resets DNS/Winsock/IP stack, runs DISM RestoreHealth, and runs SFC. | Long |
Recommended order:
Soft Recovery -> Default Recovery -> Hard Recovery
Start with the lightest repair mode. Move to the next mode only if the issue is not fixed.
Download or clone this repository, then keep these files in the same folder:
recovery.ps1
recovery.bat
If you downloaded the repository as a ZIP file, extract it first.
Open PowerShell as Administrator in the extracted folder, then run:
powershell -ExecutionPolicy Bypass -File .\recovery.ps1
You can also right-click recovery.bat and choose Run as administrator. The batch file only launches recovery.ps1.
Administrator access is required because the tool modifies Windows services, Microsoft Store registration, Windows Update cache, and network settings.
When the menu appears, select one of the available recovery modes:
[1] Soft Recovery
[2] Default Recovery
[3] Hard Recovery
[4] Toggle dry-run preview
[5] Exit
For most users, the recommended starting point is:
2 - Default Recovery
Use Soft Recovery first if the issue is minor. Use Hard Recovery only when the problem continues after Soft or Default mode.
Dry-run mode shows the planned actions without changing Windows settings:
powershell -ExecutionPolicy Bypass -File .\recovery.ps1 -Mode Default -DryRun
For automation or quick testing:
powershell -ExecutionPolicy Bypass -File .\recovery.ps1 -Mode Soft -DryRun -SkipPrompt -NoStoreLaunch
Do not close the window while the repair is running.
Hard Recovery can take a long time because it may run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc.exe /scannow
These commands can appear slow or paused for several minutes. That is normal.
After the recovery finishes, restart Windows.
Then open Microsoft Store and go to:
Library -> Get updates
After that, try the failed installation or update again.
Use this flow if you are unsure which mode to choose:
| Problem | Recommended First Mode | If Not Fixed |
|---|---|---|
| Microsoft Store opens slowly or behaves strangely. | Soft Recovery | Run Default Recovery. |
| Downloads stuck at 1%. | Default Recovery | Restart, then run Hard Recovery. |
| Updates stuck on Pending or Downloading. | Default Recovery | Run Hard Recovery. |
| Store does not launch. | Soft Recovery | Run Default Recovery. |
| Repeated install failures after multiple attempts. | Default Recovery | Run Hard Recovery. |
| Windows Update and Microsoft Store are both broken. | Hard Recovery | Check the log and restart Windows. |
- Windows 10 or Windows 11.
- Administrator access.
- Microsoft Store installed on the system.
- PowerShell available.
- Internet connection for Microsoft Store downloads and repairs that need online Windows component sources.
For DISM repair in Hard Recovery, Windows may need access to Windows Update or a valid component source.
Depending on the selected mode, MSStore Repair may interact with the following Windows components:
| Component | Purpose |
|---|---|
| Microsoft Store cache | Removes stale Store cache files that may block downloads or updates. |
| AppX package registration | Re-registers Store-related package manifests. |
| BITS | Resets transfer jobs used by background downloads. |
| Delivery Optimization | Clears cached delivery data used by Store and Windows downloads. |
| Windows Update services | Restarts and repairs services related to Store delivery. |
| SoftwareDistribution | Clears selected Windows Update download/log cache areas in Hard Recovery. |
| Catroot2 | Renames the cryptographic catalog cache in Hard Recovery. |
| DNS cache | Flushes DNS resolver cache in Hard Recovery. |
| Winsock and IP stack | Resets network stack settings in Hard Recovery. |
| DISM and SFC | Repairs Windows image and system files in Hard Recovery. |
Every run writes a log file to the Desktop:
MicrosoftStoreRecovery.log
The log includes:
- Selected recovery mode.
- Start and finish time.
- Service repair output.
- PowerShell AppX registration output.
- DISM and SFC output when Hard Recovery is used.
- Service verification results.
If the Store is still broken after running MSStore Repair, check this log first.
MSStore Repair performs system-level repair actions. Read these notes before running it:
- Run it only from a trusted copy of this repository.
- Review
recovery.ps1andrecovery.batbefore running it. - Close Microsoft Store before starting the repair.
- Save open work before using Hard Recovery.
- Restart the PC after recovery.
- A restore point is attempted, but Windows may skip restore point creation if System Protection is disabled or restricted.
- Hard Recovery resets network stack settings, which may require a restart before everything behaves normally.
The script is provided as-is, without warranty.
MSStore Repair cannot guarantee a fix for every Microsoft Store issue.
It may not fix problems caused by:
- Microsoft account restrictions.
- Region, payment, or licensing issues.
- Microsoft Store service outages.
- Corporate, school, or group policy restrictions.
- Missing Microsoft Store packages that require a separate reinstall source.
- Severely damaged Windows installations.
- Third-party security software blocking Store traffic.
- Network firewalls, DNS filtering, or proxy rules outside Windows.
If the Store is still broken after Hard Recovery, check the log file and verify Windows Update, Microsoft account sign-in, system date/time, region settings, and network restrictions.
MSStore Repair
|-- recovery.ps1
|-- recovery.bat
|-- README.md
|-- LICENSE
`-- assets
`-- screenshots
|-- windows11-msstore-repair-menu.png
`-- windows11-msstore-repair-complete.png
This project is lightweight and script-based. It is designed for practical Store recovery rather than a full installer or GUI application.
Current release:
- v1.0.0: first MSStore Repair release package with the advanced
recovery.ps1console, optional dry-run mode, safer package preflight checks, and therecovery.batlauncher.
Future improvements may include:
- More detailed error-code guidance.
- Automatic log summary.
MSStore Repair is an independent utility and is not affiliated with Microsoft.
Microsoft Store, Windows, App Installer, BITS, Delivery Optimization, DISM, and SFC are Microsoft technologies and trademarks of their respective owner.
Use this tool at your own risk. Always review scripts before running them with Administrator privileges.