Microsoft Store installation hangs typically stem from corrupted cache files, disrupted background services, or conflicting third-party security software. By resetting the store cache via wsreset.exe, ensuring Windows Update and Store services are running, and repairing system integrity with SFC and DISM commands, you can resolve most stuck installation states without needing to reinstall the operating system.
Resetting the Microsoft Store Cache
The most common cause for an installation appearing "stuck" at a specific percentage is a corrupted local cache. The Microsoft Store relies on temporary files to download and verify app packages. When these files become inconsistent, the process halts indefinitely. You can clear this cache using a built-in diagnostic tool that requires no administrative privileges.
Open the Run dialog by pressing
Win + R. Type
wsreset.exe into the text field and press Enter. A blank command prompt window will appear. Do not close it immediately; wait for the process to complete. This action clears the store's internal cache and automatically restarts the Microsoft Store application once finished. If the installation was previously hanging due to bad cache data, the issue should now be resolved.
Verifying Essential Background Services
If resetting the cache does not work, the underlying services responsible for handling app installations may be disabled or stopped. The Microsoft Store depends heavily on the Windows Update service, even for apps that do not update through traditional Windows Update channels. Additionally, the Cryptographic Services must be active to verify the digital signatures of app packages.
Navigate to the Services management console by typing
services.msc in the Start menu search bar. Locate the following three services:
- Windows Update: Ensure the Startup type is set to Automatic (Delayed Start) or Automatic.
- Cryptographic Services: Set the Startup type to Automatic.
- Microsoft Store Install Service: If present on your version of Windows, ensure it is Running and set to Automatic.
For each service, right-click and select Properties. Change the startup type if necessary, then click Start to launch the service if it is currently stopped. Apply the changes and restart your computer before attempting the installation again.
Repairing System File Integrity
Corrupted system files can prevent the installer from writing new components to your hard drive. Windows includes two powerful command-line tools designed to detect and repair these issues: the System File Checker (SFC) and the Deployment Image Servicing and Management (DISM) tool. These tools scan protected system files and replace incorrect versions with correct Microsoft ones.
Open Command Prompt as an administrator. Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin). First, run the SFC scan by typing
sfc /scannow and pressing Enter. This process may take several minutes. If SFC finds errors but cannot fix them, proceed to run the DISM command:
DISM /Online /Cleanup-Image /RestoreHealth. This command uses Windows Update to source healthy files for repair. Once both processes complete successfully, reboot your device.
Checking Third-Party Interference
Antivirus software and firewalls sometimes misidentify the Microsoft Store installer as a threat or block its network access. This interference often manifests as a hang during the verification phase. Temporarily disabling real-time protection can help determine if security software is the culprit.
Pause your antivirus protection for 10-15 minutes. Try installing the app again. If the installation completes successfully, add an exception for the Microsoft Store and related Windows App Execution Aliases in your security software settings. Remember to re-enable your antivirus protection immediately after testing. For users experiencing broader app issues, such as those seen on newer hardware architectures, checking specific driver compatibility might also be necessary, as discussed in guides regarding
Windows Apps Won't Start: Troubleshooting a 12th Gen Intel Core i5 System.
Re-registering the Store via PowerShell
If the above steps fail, the Store app package itself may be corrupted. You can force Windows to re-register the app using PowerShell. This process removes the current instance and reinstalls the manifest files required for the app to function.
Right-click the Start button and select Windows PowerShell (Admin) or Windows Terminal (Admin). Paste the following command and press Enter:
Get-AppXPackage *WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
You may see red error messages during this process. Ignore them, as they often relate to missing dependencies that are already installed. Wait for the command prompt to return to the normal state. Restart your computer and try the installation one last time.
Frequently Asked Questions
Why does my installation stay at 0%?
A 0% status usually indicates that the installer cannot establish a connection with the server or that the local cache is completely locked. Clearing the cache with
wsreset.exe is the primary solution for this symptom.
Can I install apps without the Microsoft Store?
Yes, you can sideload apps by enabling Developer Mode in Settings > Update & Security > For Developers. However, this method bypasses security checks and is generally intended for developers rather than general users.
What if the Microsoft Store won't open at all?
If the app fails to launch entirely, re-registering the package via PowerShell, as described in the previous section, is the most effective fix. It forces Windows to rebuild the app's configuration files.
Does resetting the PC fix Store issues?
A full reset is a last-resort option. Before doing so, try the service and cache fixes first, as they address the root cause in most cases. Resetting takes significantly longer and may require re-downloading all applications.
Are there known issues with specific Windows updates?
Occasionally, a buggy Windows Update can break the Store service. In such cases, uninstalling the recent update via Settings > Update & Security > View update history > Uninstall updates may restore functionality.