How to Manually Reset Corrupted Windows Store/UWP Apps (Windows 10/11)
This guide provides advanced methods to manually reset or re-register problematic Universal Windows Platform (UWP) apps, such as the Store client itself, when they crash or fail to update correctly on Windows 10 or 11.
Direct Diagnostic & Remediation Summary
- Action 1: Run PowerShell as Administrator and execute
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Name $_.PackageFullName}to re-register all packages. - Action 2: Use the Windows Settings app (Apps & features) to manually 'Reset' or 'Repair' individual problematic apps.
How to Manually Reset Corrupted Windows Store/UWP Apps (Windows 10 & 11)
When built-in apps like the Microsoft Store, Weather widget, or certain utility apps start behaving erratically—crashing on launch, failing to update, or displaying error codes—it is often due to corrupted local package data. This guide walks you through deep system commands in PowerShell to force a clean re-registration of these components.
Initial Triage & Environment Isolation (Checking Basic Health)
Before running deep commands, we must isolate if the issue is system-wide or confined to one app. We begin by using built-in Windows tools.
- Run System File Checker (SFC): This checks core OS files for corruption.
sfc /scannowWait for this scan to complete. If it finds and fixes errors, reboot immediately.
- Run DISM Check (Deployment Image Servicing and Management): This repairs the underlying Windows image source.
DISM /Online /Cleanup-Image /RestoreHealthThis process requires a stable internet connection as it downloads clean component files.
Diagnostic Scans & Hardware Isolation (The PowerShell Approach)
We now move to PowerShell, which allows direct manipulation of AppX packages. We must run this session with elevated privileges.
- Open PowerShell as Administrator: Search for
PowerShellin the Start Menu, right-click, and select Run as administrator. - List All Installed Packages (Optional Diagnostic): Run this command to see a comprehensive list of all packages that might be corrupted.
Get-AppxPackage -AllUsers | Select Name, PackageFullNameReviewing the output helps pinpoint which apps are present.
- Re-register All Packages (The Core Fix): This command iterates through every installed package and forces a clean re-registration across all user profiles.
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Name $_.PackageFullName}This process can take several minutes and may show yellow/red error text; ignore these if the command completes successfully.
Targeted Remediation & Fixes (Manual App Reset)
If the full package re-registration did not solve a single, specific application (like Photos or Calculator), we must use the Settings UI for targeted repair.
- Navigate to Settings: Press
Win + I. - Go to Apps: Click on Apps & features (or Installed Apps in Win 11).
- Locate the Problem App: Find the specific application that is failing.
- Reset/Repair: Click on the app, select Advanced options. You will see two critical buttons:
- Repair: Run this first. It attempts to fix corrupted files without deleting data.
- Reset: If Repair fails, use Reset. This clears all app settings and restores the app to its factory default state.
Common Pitfalls & Advanced Diagnostics
If the above steps fail, consider these advanced checks:
- User Profile Corruption: If the issue only appears for one user, that profile might be corrupt. Test logging in with a brand new local administrator account to see if the problem persists there.
- Group Policy Interference (Enterprise Users): In corporate environments, GPOs can override app settings. Check your device group policies for restrictions on UWP apps.
- Package Removal/Reinstallation: If the package is completely gone (not just corrupted), you might need to use PowerShell to remove it first, then re-add it via the Store or by downloading an official MSIX installer if available. Example removal:
Get-AppxPackage *nameofapp* | Remove-AppxPackage(Replace nameofapp with the actual package name.)
Verification, Results & Long-Term Stability Validation
After completing all steps (especially running SFC/DISM and the PowerShell re-registration), a full system reboot is mandatory. Once back online:
- Test Core Apps: Attempt to use the Microsoft Store, Calculator, and Photos app multiple times to ensure smooth operation.
Expected Result: No immediate crashes or persistent error messages. - Check for Updates: Open the Store and check if any pending updates are available for the problematic apps.
Pro Tip: If you use specialized hardware (e.g., Dell Precision, Lenovo ThinkPad), check the manufacturer's support site first. They sometimes release specific firmware or driver patches that address OS component conflicts.
Frequently Asked Questions
Q: Did I need to uninstall and reinstall the entire operating system?
A: Not usually. The PowerShell method is designed as a non-destructive, deep repair that rebuilds package manifests without wiping your personal files or core settings.
Q: Why are there yellow/red errors when running the re-registration command?
A: These errors often indicate that certain packages cannot be found or have already been removed by another process. As long as the main command finishes executing without a fatal PowerShell error, these warnings can usually be safely ignored.
Q: Does this fix issues with third-party desktop apps (like Adobe Photoshop)?
A: No. This guide specifically targets Microsoft's built-in UWP/AppX applications. Third-party software troubleshooting requires checking the application's specific settings or reinstalling that program entirely.
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Name $_.PackageFullName}
Frequently Asked Questions
Is this safe to run on a work computer?
Yes, provided you have administrator rights. It is a standard system maintenance procedure, but always ensure you are connected to the correct network if corporate policies restrict PowerShell execution.
What if I don't know the exact package name for an app?
If you suspect an app like 'Maps', you can use <code>Get-AppxPackage *maps*</code> in PowerShell first. This will list its full package details, which you can then reference for targeted removal or repair commands.
Need help implementing this solution?
Our cybersecurity and infrastructure engineers can audit, harden, or configure your systems directly.
Community Discussion & Confirmations (0)
Technical questions, hardware findings, and verified fix reports.
No reader questions posted yet. Have you tried this solution or experienced an edge case? Post below.