Error 0x80073CF9 is one of those Microsoft Store errors that just stops you cold. You click Install, the progress bar barely moves, and then boom, the whole thing falls over with that code. We see it constantly in remote support sessions at Vivid Repairs. Nine times out of ten it comes down to a handful of the same culprits, and most of them are fixable in under 30 minutes without touching anything scary.

TL;DR

0x80073CF9 is a Microsoft Store deployment failure on Windows 10. Run wsreset.exe first, check the AUInstallAgent folder exists in C:\Windows, confirm your Store-related services are running, then run SFC and DISM if the error persists. That sequence clears the problem for the vast majority of users.

⏱️ 13 min read ✅ 75-85% success rate 📅 Updated July 2026

Key Takeaways

0x80073CF9 is almost always caused by a corrupted Store cache, a missing AUInstallAgent folder, or stopped services.
Running wsreset.exe and checking the AUInstallAgent folder fixes it for most people without needing anything advanced.
If the quick fix doesn't work, SFC and DISM repair the underlying deployment components that the Store depends on.
If the error only appears in your user account and not a fresh one, your Windows profile is likely corrupted.
Never delete or manually permission-edit the WindowsApps folder. It will make things significantly worse.

At a Glance

Difficulty: Intermediate
Time Required: 15 to 60 mins
Success Rate: 75-85% with Solution 1 alone

What Actually Causes 0x80073CF9?

Before you start clicking things, it helps to know what you're dealing with. The error code 0x80073CF9 sits in the Windows deployment engine, which is the bit of Windows responsible for unpacking and installing Store app packages. When it throws this code, it's basically saying "I tried to deploy this package and something went wrong at a fundamental level." That's not very helpful on its own, so here's what's actually going wrong behind the scenes.

The most common cause, by a long stretch, is a corrupted Store cache. Every time you download or install an app, the Store writes temporary data to a local cache. If a previous install failed partway through, or if Windows had a rough shutdown mid-download, that cache can end up with broken or incomplete entries. The next time you try to install anything, the deployment engine trips over the old mess and refuses to continue.

Second most common: the AUInstallAgent folder is missing. This is a folder that should live at C:\Windows\AUInstallAgent and it's specifically required for Store downloads and Xbox app installations. It's a bit obscure, honestly. Microsoft doesn't document it prominently, but its absence reliably causes 0x80073CF9, especially for gaming apps. Some overzealous cleanup tools and third-party optimisers delete it because it looks like junk. It isn't.

Then there's the services angle. The Microsoft Store depends on three Windows services running properly: Windows Update, Background Intelligent Transfer Service (BITS), and Microsoft Store Install Service. If any of these are stopped, set to Manual when they should be Automatic, or stuck in a broken state, the Store can't download or deploy packages. This is more common than you'd think, especially on machines where someone has run a "Windows debloater" script from the internet.

Corrupted system files round out the top causes. The Store's deployment engine relies on DLLs and manifests that are part of the core Windows installation. If those files are damaged, SFC and DISM are the tools to fix them. And on the permissions side, the C:\Program Files\WindowsApps folder needs to be owned by TrustedInstaller with specific ACLs intact. If those have been changed, installs will fail. See the Windows Boot Manager boot failed guide for a broader look at how Windows system file corruption can cascade into multiple failure modes like this one.

Third-party antivirus is the wildcard. Some AV products are genuinely too aggressive with Store processes and will block wsappx.exe or silently modify WindowsApps permissions. It's worth ruling out early.

0x80073CF9 Quick Fix: Cache Reset and Service Check

Start here. This fixes the problem for roughly 75 to 85% of users and takes about 10 to 15 minutes.

Store Cache Reset and Service Repair Easy

Reset the Store app itself
Open Settings, go to Apps, scroll to Microsoft Store and click it, then select Advanced options. Click Terminate first (force-closes any running Store process), wait 10 seconds, then click Repair, wait for that to finish, then click Reset. You'll be signed out of the Store. That's expected.
Run wsreset.exe
Press Win+R, type wsreset.exe and hit Enter. A blank black Command Prompt window appears. Do not close it. It will close itself after 10 to 30 seconds and the Store will reopen automatically. That means it worked.
Check the AUInstallAgent folder
Open File Explorer and navigate to C:\Windows. Look for a folder called AUInstallAgent. If it's not there, right-click in the Windows folder, select New then Folder, and name it exactly AUInstallAgent. Case matters. You'll need admin rights to do this.
Verify your services are running
Press Win+R, type services.msc and press Enter. Find Windows Update, Background Intelligent Transfer Service, and Microsoft Store Install Service. For each one: right-click, Properties, set Startup type to Automatic, click Apply, then click Start if the status isn't already Running.
Restart and test
Full restart, not sleep. After logging back in, open the Store and try installing the app that was failing. If it downloads and installs without 0x80073CF9, you're sorted.

Most users see the app install cleanly after this. If not, move to Solution 2.

Quick note on install issues software: for persistent deployment errors like 0x80073CF9 that keep coming back, a dedicated install issues repair tool can automate the permission checks, service resets, and cache clearing that you'd otherwise have to do manually each time. Worth considering if this is a recurring problem on your machine.

Advanced 0x80073CF9 Fixes: Permissions and Profile Repair

Right, so Solutions 1 and 2 haven't shifted it. At this point we're dealing with either a permissions problem on the Store's core folders, a corrupted Windows Update cache, or a corrupted user profile. These are less common but they do happen, particularly on machines that have had third-party optimisation tools run on them, or machines that have been through several major Windows feature updates without a clean install.

A word of caution before anything else: do not manually edit the permissions on C:\Program Files\WindowsApps unless you genuinely know what you're doing with NTFS ACLs. That folder needs to be owned by TrustedInstaller. If you accidentally grant yourself ownership and then something goes wrong, you can break every Store app on the machine permanently. The troubleshooter in the next step is the safer route. For reference, Microsoft's DISM documentation covers how Windows manages app package deployment and why these permissions matter so much.

CRITICAL: Do not delete or take ownership of the WindowsApps folder. Incorrect permission changes will break all Store apps permanently and may require a full Windows reinstall to recover.

Advanced Permissions Repair and Profile Reset Advanced

Reset Windows Update components
Open an elevated Command Prompt. Run these commands one at a time:
net stop wuauserv
net stop bits
Then navigate to C:\Windows and rename SoftwareDistribution to SoftwareDistribution.old. Navigate to C:\Windows\System32 and rename catroot2 to catroot2.old. Then restart the services:
net start wuauserv
net start bits
Windows rebuilds both folders fresh on next use.
Run the Windows Store Apps Troubleshooter
Go to Settings, then Update and Security, then Troubleshoot, then Additional troubleshooters. Select Windows Store Apps and click Run the troubleshooter. Follow all prompts and apply every fix it recommends. It checks permissions, services, and Store configuration automatically.
Check WindowsApps folder exists and has correct ownership
Open File Explorer, navigate to C:\Program Files, and enable hidden items (View tab, tick Hidden items). Confirm the WindowsApps folder is there. Right-click it, Properties, Security tab. Verify SYSTEM and TrustedInstaller are listed. If they're missing, that's your problem. At this point, contact a technician rather than attempting to fix it manually.
Test with a fresh user profile
Go to Settings, then Accounts, then Family and other users, then Add someone else to this PC. Create a new local account with administrator privileges. Sign out, log in to the new account, and try installing the same app. If it works in the new account, your original profile is corrupted, not the system.
If the new profile works, migrate your data
Copy your personal files (Documents, Desktop, Downloads, Pictures) from C:\Users\[OldUsername] to the new profile. Do not copy AppData folders. That's where the corruption lives. Reconfigure your applications from scratch in the new profile.
Last resort: in-place upgrade
Download the Windows 10 Media Creation Tool from Microsoft, run it, and choose Upgrade this PC now, keeping personal files and apps. This reinstalls Windows over itself, refreshing all system files while preserving your data. It takes 1 to 2 hours and needs 10GB+ free space. Plug your laptop in first.

The profile test is the key diagnostic here. If a fresh profile works, you know exactly where the problem is and migration is the clean fix.

One more thing worth trying at this stage if you haven't already: temporarily disable your third-party antivirus completely (not just real-time protection, the whole thing) and attempt the install. If 0x80073CF9 disappears, your AV is the culprit. Add wsappx.exe, svchost.exe (for Store services), and the C:\Program Files\WindowsApps folder to your exclusion list. This is a known issue with several popular AV products and it's genuinely easy to miss because the AV doesn't log what it's blocking in an obvious way.

If you've had a major Windows feature update recently and the error appeared right after, that's also worth knowing. Feature updates can reset service configurations and occasionally corrupt Store components. The PowerShell re-registration command from Solution 2 is particularly effective in that scenario. If your machine has also been experiencing boot issues alongside Store errors, check out our Windows boot loop recovery guide as deep system corruption can sometimes affect both simultaneously.

Preventing 0x80073CF9 Coming Back

Once you've fixed it, you don't want to be back here in three months doing this again. Here's what actually makes a difference, in order of importance.

Run wsreset.exe monthly. Seriously, just add it to your calendar. It takes 30 seconds and clears out accumulated cache junk before it has a chance to cause problems. Press Win+R, type wsreset.exe, done.

Keep Windows updated. The Store's deployment components are tied to the Windows servicing stack. Skipping updates means skipping fixes to the exact bits of Windows that handle app installation. Turn on automatic updates and let them run.

Leave WindowsApps alone. Don't take ownership of it, don't run permission-fixing scripts on it, don't let optimiser tools touch it. The NTFS ACLs on that folder are specific and intentional. Messing with them is the most reliable way to cause 0x80073CF9 permanently.

Keep 20GB free on C:. Store apps need room to unpack during installation. Running tight on space causes all sorts of odd deployment failures. If your drive is getting full, it's worth looking at 10 TB cloud storage options for Windows to offload files rather than deleting things you might need.

Sort your antivirus exclusions. If you're running third-party AV, add wsappx.exe and the WindowsApps folder to your exclusion list now, before it causes a problem. It's a five-minute job and it prevents a class of Store errors that are genuinely annoying to diagnose.

Check your region and time settings. This one catches people out. The Store uses your system date, time, and region for authentication. If your clock is wrong or your region is set to something that doesn't match your account, you'll get authentication failures that look like deployment errors. UK users: make sure your region is set to United Kingdom and your time zone is UTC+00:00.

0x80073CF9 Summary

Error 0x80073CF9 is frustrating but it's fixable. The vast majority of cases come down to a corrupted Store cache, a missing AUInstallAgent folder, or stopped services, and the wsreset plus service check combination sorts those out quickly. If that doesn't work, SFC and DISM repair the underlying deployment components, and the PowerShell re-registration rebuilds the Store's own setup. For the stubborn cases, a fresh user profile or in-place Windows upgrade is the clean answer. The key thing is to work through the solutions in order rather than jumping straight to the nuclear options. And whatever you do, don't touch the WindowsApps permissions manually. That path leads somewhere much worse than 0x80073CF9.

Windows 10 Store error 0x80073CF9 app installation failed