/
/

How to Re-register the Microsoft Store in Windows 11

by Jarod Habana, IT Technical Writer
How to Re-register the Microsoft Store in Windows 11

Instant Summary

This NinjaOne blog post offers a comprehensive basic CMD commands list and deep dive into Windows commands with over 70 essential cmd commands for both beginners and advanced users. It explains practical command prompt commands for file management, directory navigation, network troubleshooting, disk operations, and automation with real examples to improve productivity. Whether you’re learning foundational cmd commands or mastering advanced Windows CLI tools, this guide helps you use the Command Prompt more effectively.

Key Points

  • Re-register the Microsoft Store to restore damaged package data in Windows 11.
  • Reset the Microsoft Store cache to clear corrupted temporary files.
  • Use PowerShell re-registration to fix broken or missing Store manifests.
  • Re-register all built-in apps to resolve system-wide package issues.
  • Run DISM and SFC to repair underlying system file corruption.
  • Validate Store functionality to confirm successful restoration.

The Microsoft Store serves as the primary distribution hub for Windows apps, frameworks, and various essential system components. So when it regularly needs troubleshooting because it stops responding or reports missing package data, it can become disruptive for admins and users.

One of the most practical and low-impact ways to resolve this issue and restore functionality without doing a full system reinstall is to re-register the Microsoft Store in Windows 11. Keep reading to learn how to do this.

How to re-register the Windows 11 Microsoft Store

Depending on the issue you’re facing, you can approach this task in several different ways. Below are some methods you can try, from simple resets to more advanced repair tools, to restore Microsoft Store functionality with minimal disruption.

📌 Prerequisites:

  • Windows 11 system with administrative privileges
  • Access to PowerShell running as administrator
  • Internet access for Store content and updates
  • Optional need to repair Store dependencies (e.g., framework packages)
  • Basic knowledge of Windows app package structure

Method 1: Reset the Microsoft Store cache

This first Microsoft Store repair method is a quick cache reset that often resolves issues caused by outdated or corrupted Store data. This forces Windows to rebuild temporary files and can restore basic functionality without deeper repairs.

  1. Press Windows key + R to open the Run dialog.
  2. Type the following command before pressing Enter to trigger a Store cache reset:

wsreset.exe

  1. Wait for the command window to appear and complete its process.
  2. Allow the Microsoft Store to reopen automatically afterward.
  3. Test the Store by installing or updating an app to confirm that core functions are working.

Method 2: Re-register the Microsoft Store using PowerShell

When the Store’s package registration becomes damaged, you can restore the manifest and deployment details that Windows relies on to load the app correctly by re-registering it through PowerShell. This directly repairs the Store’s underlying configuration without affecting other system components.

  1. Open PowerShell as administrator. Press Windows key + R, type “powershell,” and press Ctrl + Shift + Enter.
  2. Copy and paste the following PowerShell command before pressing Enter to re-register the Store package:

Get-AppxPackage -allusers Microsoft.WindowsStore | Foreach {Add-AppxPackage -Register “$($_.InstallLocation)\AppxManifest.xml” -DisableDevelopmentMode}

  1. Wait for the command to finish processing the registration.
  2. Restart the computer to apply the changes.
  3. Open the Microsoft Store to confirm that it launches and behaves normally.

Method 3: Re-register all built-in Windows apps

If the problem extends beyond the Microsoft Store and several built-in apps fail, you can start a broader reset by re-registering all default packages. This will refresh the manifest and registration data for every built-in Windows app.

  1. Open PowerShell as administrator. Press Windows key + R, type “powershell,” and press Ctrl + Shift + Enter.
  2. Copy and paste the following PowerShell command before pressing Enter to re-register all built-in app packages:

Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -Register “$($_.InstallLocation)\AppxManifest.xml” -DisableDevelopmentMode}

  1. Let Windows complete the deployment and processing steps.
  2. Restart the system to finalize the repairs.
  3. Test the Microsoft Store and other apps that depend on its components.

Method 4: Repair Store components using DISM and SFC

System file corruption can also interfere with how Windows registers and loads the Microsoft Store. You can run DISM (Deployment Image Servicing and Management) and SFC (System File Checker) to restore core system components and ensure that the Store’s underlying files and services are intact before attempting further repairs.

  1. Open PowerShell or Command Prompt as administrator. Press Windows key + R, type “powershell” or “cmd,” and press Ctrl + Shift + Enter.
  2. Copy and paste the following command before pressing Enter to restore the system image:

DISM /Online /Cleanup-Image /RestoreHealth

  1. Wait for the process to finish, then run this command to repair the remaining corrupted files:

sfc /scannow

  1. Restart Windows to apply the repaired system components.
  2. Try launching the Microsoft Store to check if the issue is resolved.

Validate Store registration after repair

After executing any of the methods mentioned above, make sure to verify that the Microsoft Store is functioning as expected. A quick check should help confirm that registration succeeded and that the Store can communicate with Microsoft services without errors.

  1. Launch the Microsoft Store and confirm it opens normally.
  2. Check that the interface loads fully and no error messages appear.
  3. Try downloading or updating an app to verify functionality.
  4. Open the Library section to confirm updates are processing correctly.
  5. Review Event Viewer for any deployment or Store-related errors left.
  6. Document the steps taken and the results for future troubleshooting and reference.

Why re-register the Microsoft Store in Windows 11?

This action is often necessary when the Microsoft Store becomes unresponsive, fails to open, or shows signs of corruption, preventing normal updates or installations. This restores underlying package registration, which can resolve issues that basic resets or cache clears can’t fix. Re-registering the Microsoft Store is usually done to:

  • Correct damaged or missing package registrations
  • Restore launch functionality when the Store won’t open
  • Fix update or installation failures caused by corrupted metadata
  • Repair dependencies that rely on properly registered Store components
  • Provide a non-invasive alternative to reinstalling Windows

Troubleshooting

Even after re-registration, some issues may persist if underlying components or dependencies are still damaged. Below are some common problems and corresponding resolution steps to help you narrow down the cause and successfully fix the Microsoft Store in Windows.

Store fails to launch

If the Store still refuses to open, confirm that all PowerShell commands were executed with full administrative privileges. Running them without elevation can lead to incomplete repairs.

Manifest path errors

When PowerShell reports missing manifest files, the Store’s installation directory may be damaged or partially removed. Try performing a full re-registration of all built-in apps to restore the missing structure and allow the Store to deploy correctly.

Store missing from the Get-AppxPackage list

If the Store doesn’t appear in the package list, the app may have been manually removed or corrupted beyond normal recovery. Reinstalling it through a Microsoft Store installer package or a provisioning package often resolves this and restores the required files.

DISM fails to repair

DISM relies on healthy online sources to restore system images, so failures may indicate connectivity issues or unavailable repair files. Verifying network access or pointing DISM to a local repair source can resolve these problems.

Multiple apps broken

If several apps exhibit similar failures, the issue is likely broader than just the Microsoft Store. Run the full re-registration for all built-in packages.

Ensuring reliable Store functionality across Windows 11 systems

Re-registering the Microsoft Store is a good way to correct app registration issues, restore missing components, and reestablish a stable and functional Windows 11 system without full reinstallation.

Moving methodically from the simplest cache reset to deeper repairs should resolve Store-related failure with minimal disruption. Ensure that you verify the results and document the process and results for future reference, and you can keep the Microsoft Store operating properly.

Related topics:

FAQs

No, re-registration only repairs the Store’s underlying package data and does not uninstall or modify your existing apps. Your applications, settings, and licenses remain intact.

The re-registration commands themselves work offline, but the Store needs internet access to load catalog data and download updates. Without connectivity, you may still encounter loading or installation errors.

If the Store fails to appear in the app list after re-registration, the package may have been removed or corrupted beyond repair. Restoring it typically requires reinstalling the Store component through a provisioning package or Windows repair source.

Yes, the PowerShell re-registration process is widely used in IT support workflows and does not modify user data. However, some organizations may enforce policies that limit app package repairs, so administrators should confirm compliance with internal guidelines.

In many cases, yes, especially when the problem stems from corrupted metadata or damaged Store registration entries. If issues persist, system-level corruption or network restrictions may require additional troubleshooting.

Persistent failures often indicate deeper problems with user profiles, Group Policy restrictions, or damaged Windows components. At that point, creating a new user profile, restoring system health from a local source, or performing an in-place upgrade may be necessary.

You might also like

Ready to simplify the hardest parts of IT?