Fix Error 0x80073cf6: Windows Store App

Error 0x80073cf6 usually appears when a Windows Store (Microsoft Store) app fails to install or update, often due to corrupted cache, permission issues, or a stalled background task. The fix is to clear the Store cache, run the built-in Windows Store Apps troubleshooter, and if that fails, re-register the app via PowerShell. Below is a step-by-step guide covering the most reliable methods, plus what causes the error and how to avoid it.

What Is Error 0x80073cf6?

This error code is part of the Windows Store app deployment family (0x80073xxx). It specifically indicates a problem during the installation or update process of a UWP (Universal Windows Platform) app. Unlike a simple “download failed” message, 0x80073cf6 often points to a conflict between the Store’s internal state and the app package being processed. Common triggers include:

• Corrupted Store cache files
• Pending updates that stalled
• Insufficient disk space (though the error message may not say so)
• Third-party antivirus or firewall blocking the Store’s network access
• Windows Update components that are out of sync

The error can affect any Store app—from built-in ones like Mail or Photos to third-party games—and typically appears as a dialog box when you click “Update” or “Install.”

Before You Start: Quick Checks

Spend 30 seconds on these basics before diving into deeper fixes. They resolve a surprising number of cases:

1. Restart your PC. A simple reboot clears temporary locks on app files.
2. Check disk space. Open Settings > System > Storage. Ensure you have at least 10 GB free (more for large games).
3. Check date/time. Right-click the clock > Adjust date/time. Wrong time breaks certificate validation for Store downloads.
4. Run Windows Update. Settings > Windows Update > Check for updates. Install any pending updates, then retry the Store.

If the error persists, proceed with the methods below in order.

Method 1: Clear the Microsoft Store Cache

The Store keeps a cache of downloaded app metadata and temporary files. Corruption here is the most common cause of 0x80073cf6. Windows has a built-in tool for this:

1. Press Win + R, type wsreset.exe, and press Enter.
2. A blank Command Prompt window will open. Wait—it may take 30–60 seconds. The Store will open automatically when done.
3. Try installing/updating the app again.

If wsreset.exe doesn’t help, manually delete the cache folder:

1. Close the Store completely (check the system tray).
2. Open File Explorer and navigate to %LocalAppData%\Packages\Microsoft.WindowsStore_8wekyb3d8bbwe\LocalCache.
3. Delete everything inside that folder (not the folder itself).
4. Restart the Store.

Method 2: Run the Windows Store Apps Troubleshooter

Windows includes a dedicated troubleshooter that automates many of the fixes you’d do manually. It’s worth running because it also checks for permission issues and service problems.

1. Open Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10).
2. Find Windows Store Apps and click Run.
3. Follow the prompts. It will scan for common issues like corrupted cache or misconfigured permissions.
4. Restart your PC after it finishes, even if it says no problems found.

This tool often fixes the error silently, so always try it before more aggressive methods.

Method 3: Re-register the App via PowerShell

If the cache and troubleshooter don’t work, the app’s registration in Windows is likely corrupted. Re-registering all Store apps forces Windows to rebuild the app’s package links. This is safe and doesn’t delete your app data.

1. Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin).
2. Copy and paste this command, then press Enter:

Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

3. Wait for the command to complete (it may take a few minutes). You’ll see no output if successful.
4. Restart your PC and try the Store again.

If you only want to re-register the specific app causing trouble, replace the command with:

Get-AppxPackage -Name "*AppName*" | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

For example, for the Mail app: Get-AppxPackage -Name "*microsoft.windowscommunicationsapps*".

Method 4: Reset the App’s Data and Permissions

Sometimes the error is specific to one app that has a corrupted local state. You can reset that app without affecting others.

1. Go to Settings > Apps > Installed apps (Windows 11) or Settings > Apps > Apps & features (Windows 10).
2. Find the problematic app, click the three-dot menu (or the app name), and select Advanced options.
3. Scroll down and click Reset. This clears the app’s data (like login info and settings) but not the app itself.
4. Restart your PC and try the update again.

If the app still fails, check its permissions under the same Advanced options screen—ensure it has access to the network and storage if needed.

Method 5: Check for Third-Party Interference

Antivirus software, VPNs, and proxy settings can block the Store’s connection or file operations, leading to this error. To test:

• Temporarily disable your antivirus (not Windows Defender) and retry. If it works, add an exception for the Store or the app.
• Turn off VPN/proxy and retry. The Store needs a direct connection to Microsoft servers.
• Check the Windows Firewall: ensure “Microsoft Store” is allowed. Go to Control Panel > Windows Defender Firewall > Allow an app through the firewall. If missing, click “Change settings” and “Allow another app” to add it.

Remember to re-enable your antivirus immediately after testing.

Method 6: Repair Windows Update Components

The Store relies on Windows Update services. If those are corrupted, the error can appear even when the Store itself is fine. Run these commands in an elevated Command Prompt (right-click Start > Command Prompt (Admin) or Terminal (Admin)):

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

This resets the update cache. Restart your PC and try the Store again.

Frequently Asked Questions

Will these steps delete my apps or data?

No. Methods 1–3 and 6 only clear temporary files or re-register app packages. Method 4 (Reset) does clear the app’s local data (like saved games or login tokens), so use it only if you’re comfortable reconfiguring that app. Your files and other apps remain untouched.

Why does the error happen only for one app?

That usually means the app’s package is corrupted, not the Store. Try Method 4 (Reset) for that specific app first. If it still fails, uninstall the app entirely and reinstall it from the Store—this often fixes a corrupted package.

Can I fix this without admin rights?

Most methods require an administrator account, especially PowerShell and Command Prompt commands. If you’re on a work or school device, contact your IT admin. The wsreset.exe cache clear may work without admin, but the others will prompt for elevation.

Is this error related to a Windows update?

Sometimes. A recent Windows update can break the Store’s dependencies. If the error started after an update, try uninstalling that update (Settings > Windows Update > Update history > Uninstall updates) or wait for a new cumulative update that fixes it. Method 6 (repairing update components) often helps in this scenario.

What if none of these methods work?

As a last resort, you can create a new local user account and see if the Store works there. If it does, your original account’s profile is corrupted. Otherwise, consider using the Windows Media Creation Tool to perform an in-place upgrade repair (keeps your files and apps) or contact Microsoft Support.

Does this error affect Windows 10 and 11 the same way?

Yes, the error code and underlying causes are identical. The steps above work for both, though the Settings menu names differ slightly (e.g., “Apps & features” vs. “Installed apps”). The PowerShell command is the same.

Related

• Fix macOS Mojave Problems: A Practical Guide
• Android x86 Installation & Troubleshooting Guide
• Fix Windows 11 Activation Error 0x803fa067