Microsoft Store Error 0x80073CF9: What It Means and How to Fix It (2026 Updated Guide)

Quick answer

Error 0x80073CF9 in the Microsoft Store means an app install or update failed at the package-installation stage. Most of the time the cause is a broken Store cache or a corrupted state from a previous interrupted install — both fixable in under five minutes with wsreset.exe. Don’t run the kitchen-sink command sequences other articles push without trying the simple fix first.

Before you start

A few things to know before you start running commands:

Don’t run “Microsoft Store fixer” tools from search results. There aren’t legitimate third-party tools for this; the ones advertised that way are at best useless, at worst malicious.
Don’t reinstall Windows. This error doesn’t warrant it.
Save your work in any open Microsoft Store apps. A few of the fixes below close Store apps mid-stream.
Administrator rights are required for the advanced fixes, but not for the first three. Try the simple fixes before opening an admin prompt.

What this error means

0x80073CF9 is one of the AppX deployment error codes. The Store is built on the Windows AppX/MSIX installation framework, and 0x80073CF9 translates roughly as “AppXManifest.xml is missing or invalid in the package being installed” — which in practice means the package didn’t get extracted or staged correctly.

Three things usually trigger it:

The Store cache is in an inconsistent state from a previous install or update that was interrupted.
The Windows packaging components themselves can’t write to the install location (permissions, disk full, sometimes antivirus blocking).
A Windows Update component is broken in a way that affects package deployment — 0x80073CF9 and Windows Update errors often appear together when this is the cause.

The error doesn’t mean the app you’re trying to install is broken. It means your local Store machinery couldn’t finish installing it. The same app installs cleanly for everyone else; it’s a local issue.

Where this error appears

The error shows up in three places:

In the Store app itself, on the page for the app you’re trying to install or update, with a button to retry.
In the Get Help app’s Store troubleshooter if you’ve already started that diagnostic.
In Event Viewer → Applications and Services Logs → Microsoft → Windows → AppXDeployment-Server → Microsoft-Windows-AppXDeploymentServer/Operational — useful if you want to see exactly which package and which step failed.

If you’re seeing 0x80073CF9 for every app you try, the cause is local. If you’re seeing it only for one app, the cause may still be local but it’s worth checking whether the app has been pulled or restricted in your region before going down the troubleshooting path.

Common causes

In rough order of frequency:

Store cache corruption. By far the most common. wsreset.exe fixes this in seconds.
Interrupted previous install. A previous install that was killed mid-way (PC slept, network dropped, app crashed) left the package in an inconsistent state.
Disk space pressure at the install location. Microsoft Store installs to the system drive by default, and if free space drops below about 2GB, deployments start failing. Also true for any custom install location.
Antivirus or third-party security software blocking the deployment. Less common in 2026 since most security suites have stopped interfering with AppX deployment, but still happens.
Windows Update component is broken. When the servicing stack is corrupted, Store installs can fail too.
System file corruption affecting the AppX deployment service. The least common cause but the one most articles jump to immediately.

The fix sequence below works through these in order.

Fixes to try first

In order. Stop when the install succeeds.

Run wsreset.exe. Press the Windows key, type wsreset, press Enter. A blank Command Prompt window opens for about 30 seconds, then the Store opens. This clears the Store cache. Try the install again. This works most of the time, and it’s harmless if it doesn’t.
Check free space on your system drive. Settings → System → Storage. If the C: drive (or wherever Store apps install) is below 2GB free, clear space and retry. Storage Sense can do this automatically — Settings → System → Storage → Storage Sense.
Restart and try again. A surprising number of 0x80073CF9 cases clear with a reboot, because the AppX deployment service starts in a clean state.
Run the Microsoft Store troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Microsoft Store apps → Run. This is the official Microsoft-supplied automatic fix and it covers the common cases.
Check Windows Update. Settings → Windows Update. If updates are pending, install them and retry. If updates are failing too — and you see errors like alongside 0x80073CF9 — the underlying issue is Windows Update, not the Store. Fix that first.

If the install succeeds at this point, stop. Don’t continue to the advanced fixes; you’ll spend time you don’t need to spend.

Advanced fixes

Only if the simple fixes haven’t worked.

Re-register the Microsoft Store. Open Windows Terminal as admin (right-click Start → Terminal (Admin)) and run:
```
Get-AppxPackage -AllUsers Microsoft.WindowsStore* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
```
This re-registers the Store app for all users. It’s reversible — running it again has no negative effect.
Reset the Microsoft Store. Settings → Apps → Installed apps → Microsoft Store → ⋯ → Advanced options → Reset. This is heavier than wsreset — it clears not just the cache but all Store app data. You’ll be signed out of the Store and need to sign in again.
Check for antivirus interference. Temporarily disable real-time scanning in your security software (or, if you only have Microsoft Defender, that’s already controlled by Windows). Retry the install. If the install succeeds with real-time scanning off, the security software is the cause — add an exclusion for C:\Program Files\WindowsApps and re-enable scanning.
Run DISM and SFC. If the AppX deployment service is broken because of system file corruption, repairing system files can resolve it. Useful when 0x80073CF9 is paired with other instability.
Reset Windows Update components. Use the Windows Update component reset procedure if Windows Update is also broken. Store and Update share servicing infrastructure, and fixing the latter sometimes resolves the former.

Fixes that aren’t worth your time

A few common suggestions you can skip:

Editing the registry to “fix” Store keys. No registry edit reliably fixes 0x80073CF9, and you can break the Store more thoroughly than it was broken to start with.
Creating a new Windows user account. Sometimes recommended on forums. It can confirm the issue is profile-specific, but it’s a heavyweight diagnostic for a problem that’s almost always systemwide. Not worth it before the standard fixes.
Rolling back a Windows update. Almost never the right call for 0x80073CF9 unless the error literally started the moment the update finished and nothing else has changed. Rolling back updates introduces new risks; reach for it last, not first.

If you are on a work or school device

Some organizations restrict Store access through Group Policy or Intune configuration. If you’re on a managed device and Store installs are failing across the board, this might be by design — the Store may be configured to only allow private store apps or specific allowed packages. Check with IT before troubleshooting.

What to send to IT:

The exact error code (0x80073CF9).
Whether it affects every app or just one.
A screenshot of Event Viewer’s AppXDeploymentServer/Operational log around the time of the failure.
Whether wsreset.exe was attempted and what happened.

When to stop

Stop and don’t continue if:

You’ve worked through the simple and advanced fixes without success. At that point further client-side fixes won’t help.
The error only affects one specific app and that app may have been removed from the Store or restricted in your region — that’s not your problem to fix.
You’re on a managed device and Store installs are restricted by policy.
You’ve spent more than an hour on this and the app you’re trying to install is also available outside the Store. The Store isn’t the only delivery channel for most apps; sometimes the right answer is to install via the developer’s website instead.

How to Reset Windows Update Components — when Store and Update both fail and share an underlying servicing-stack issue.
Windows Update Error 0x80070643 — common companion error to 0x80073CF9.
How to Run DISM and SFC Safely — for system-file corruption that can affect AppX deployment.

Official references

Microsoft Support: Fix problems with apps from Microsoft Store
Microsoft Learn: AppX deployment error reference
Microsoft Learn: Reset and re-register Microsoft Store

FAQ

Does 0x80073CF9 mean my Microsoft account is broken? No. It’s a local package-deployment error, not an account problem. You don’t need to sign out, change password, or recover your account.

Will reinstalling Windows fix this? Almost certainly, but it’s enormous overkill. Every fix above is reversible and most take under a minute. A clean install for a Store error is bringing a sledgehammer to a paperclip.

Why does wsreset work so often? Because the Store cache is the single most common point of failure, and wsreset.exe is the official tool for clearing it. It’s the equivalent of restarting your router for a network problem — simple, common, and effective for the most common cause.

Can I install Microsoft Store apps without using the Store? Sometimes. Some apps are also distributed as MSIX or AppX installers from the developer’s website, or via winget (Windows Package Manager). If you’ve exhausted Store troubleshooting and the app is available another way, that’s usually the lowest-effort path forward.

Why did 0x80073CF9 start after a Windows update? Updates occasionally leave the AppX deployment service in a state where its cache or staged-package directory needs to be cleared. wsreset.exe followed by a reboot is the standard fix. If it persists, the Windows Update components themselves may be in a bad state — fix those first.

Is it safe to reset the Microsoft Store? Yes. The reset clears Store app data — your sign-in session, Store-specific cache, and download queue — but it doesn’t touch any Store apps you’ve already installed. Apps stay installed; you’ll just need to sign back into the Store afterwards.

↑ Back to top