Microsoft Store Error Codes: How to Fix 0x80070422,

The Microsoft Store is one of the most reliable ways to install Windows apps — when it works. Unfortunately, cryptic hex error codes like 0x80070422, 0x80073D05, and 0x80073CFC can stop installations dead in their tracks, leaving users frustrated with no clear path forward.

This guide is the most comprehensive Microsoft Store error code reference available. For every common error, we explain the root cause, the fastest fix, and when to simply bypass the Store entirely by downloading the app package directly.

---

Quick Error Code Reference Table§

---

Detailed Fix Guide§

Error `0x80070422` — Windows Update / Store Services Disabled§

What it means: The Windows Update service or the Windows Store Install Service has been stopped, either manually, by a Group Policy, or by third-party optimization software.

Fix Step 1: Re-enable services

1. Press Win + R, type services.msc, and press Enter.
2. Find Windows Update → right-click → Properties → set Startup type to Automatic → click Start.
3. Find Windows Store Install Service → same steps.

Fix Step 2: Reset Windows Update components (if step 1 doesn't work):

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Fastest alternative: Download the app directly without needing Windows Update services at all.

---

Error `0x80073D05` — Package Already Staged / Corrupted Install§

What it means: A previous installation attempt failed mid-way, leaving behind a corrupted staging folder. Windows detects the partial package and refuses to overwrite it cleanly.

Fix:

# Find the stuck package
Get-AppxPackage -AllUsers | Where-Object { $_.Name -like "*AppNameHere*" }

# Remove it completely
Get-AppxPackage -Name "Publisher.AppName_8wekyb3d8bbwe" | Remove-AppxPackage -AllUsers

# Reinstall using direct download
Add-AppxPackage -Path "C:\Downloads\AppName.msixbundle"

---

Error `0x80073CF6` — App Installer Component Missing or Corrupted§

What it means: The built-in Windows AppxManifest resolver is missing or failed to register properly. This often happens after a Windows reset, repair install, or when App Installer itself was uninstalled.

Fix:

# Re-register the App Installer
Add-AppxPackage -RegisterBySourceLayout `
 -ForceApplicationShutdown `
 -ForceUpdateFromAnyVersion `
 -Register `
 -Path "C:\Windows\SystemApps\Microsoft.Windows.AppResolver_cw5n1h2txyewy\AppxManifest.xml"

If App Installer is completely missing, download it directly using its Product ID 9NBLGGH4NNS1 via the NexaTools Store Generator.

---

Error `0x80073CFC` — Package Blocked by System Policy§

What it means: Sideloading of .appx/.msix packages is disabled on your device, either by your own settings or by an enterprise Group Policy Object (GPO).

Fix for personal PCs:

1. Open Settings → System → For developers.
2. Toggle Developer Mode to On (this enables sideloading).
3. Alternatively, just enable Install apps from any source under the App installer settings.

Fix for enterprise/domain PCs: Your IT administrator has blocked sideloading via GPO. Contact your IT department, or request that they whitelist specific app installers.

---

Error `0x80073CF3` — Missing Dependency Package§

What it means: The .msix or .appx package requires a framework dependency (like Microsoft.VCLibs, .NET Runtime, or Microsoft.UI.Xaml) that isn't installed on the system.

Fix — Manual dependency install:

1. Use NexaTools Store Generator to generate the download links for the app.
2. In the results table, look for files with VCLibs, Framework, or Runtime in the filename.
3. Download and install those files first, then install the main app package.

Fix — Automated (recommended): Use the NexaTools PowerShell one-liner — it auto-detects and installs all dependencies in the correct order:

irm nexatools.in/ms/PRODUCT_ID | iex

---

Error `0x803FB005` — Microsoft Store Server Error§

What it means: Microsoft's Store backend is experiencing issues, or there's a problem with your account's licensing entitlement token.

Fixes to try:

1. Wait 10–30 minutes and try again (server-side issues resolve automatically).
2. Sign out and back into your Microsoft account in the Store.
3. Reset the Store cache:

wsreset.exe

4. If urgent, download the app directly — this completely bypasses the Store backend.

---

Error `0x80240438` — Store Can't Connect (Firewall/Proxy)§

What it means: The Microsoft Store is being blocked by your firewall, proxy configuration, or VPN.

Fixes:

1. Temporarily disable your VPN or proxy.
2. Add *.microsoft.com and *.windowsupdate.com to your firewall whitelist.
3. Use the direct download method — the NexaTools generator and Microsoft CDN (delivery.mp.microsoft.com) use standard HTTPS port 443 and work through most firewalls that block the Store protocol.

---

The Nuclear Option: Bypass the Store Entirely§

When none of the fixes above work — or when you simply don't have time to troubleshoot — the fastest solution is to download the app package directly from Microsoft's CDN, bypassing the Store client entirely.

This works because:

• All Microsoft Store apps are hosted on official Microsoft CDNs
• The files are digitally signed by Microsoft — Windows enforces signature verification on install
• No Microsoft Account or Store login is required

How to get direct download links§

Use the NexaTools Microsoft Store Generator:

1. Find the app's Product ID on apps.microsoft.com (the alphanumeric code at the end of the URL)
2. Paste it into the generator
3. Download the .msixbundle or .appx file for your architecture
4. Double-click to install via App Installer, or use Add-AppxPackage in PowerShell

No error codes. No Store client. No frustration.

---

Frequently Asked Questions§

Why does the Microsoft Store keep showing error codes?§

The Store client depends on multiple Windows services, account tokens, and network connectivity. Any disruption — from a stopped service to a proxy misconfiguration — can produce error codes. Direct download methods bypass all of these dependencies.

Can I fix Store errors without admin rights?§

Some fixes (like re-registering App Installer) require admin rights. But downloading and installing a .msixbundle via App Installer does not require admin rights for user-scoped apps.

Does downloading directly affect future app updates?§

No. Once installed via a direct .msix/.appx package, the app registers with Windows as a normal Store application and will receive automatic updates through Windows Update and the Store.

Is the NexaTools Store Generator an rg-adguard alternative?§

Yes — the NexaTools Microsoft Store Generator provides the same core functionality as store.rg-adguard.net (generate direct CDN download links for any Microsoft Store app), but with a modern UI, zero software bloat, no tracking scripts, and additional features like automated dependency resolution and a PowerShell one-liner installer.