0x80073CFA Removal Failed | Fix Store App Uninstall

You click Uninstall, the progress bar blinks, and Windows throws the same line again. If you’re staring at 0x80073cfa, you’re not alone. This error shows up most with Microsoft Store apps and built-in Windows apps, where removal rules are tighter than standard desktop programs.

The good news is you can fix it without random guessing. The trick is to start with low-risk checks, then move to admin tools that can remove the package when the normal button won’t cooperate. Follow the order below and retry uninstall after each phase, so you can stop as soon as it works.

Why This Error Shows Up During App Removal

“Removal failed” is Windows saying the uninstall request didn’t complete inside the app deployment system. The Settings app and Start menu both rely on that same deployment layer, so the error can follow you across different menus.

Common triggers that match real PCs

• Close app processes — A background process, service, or task is still holding files open, so removal can’t finish cleanly.
• Reset Store licensing state — Store cache and licensing data can drift, so Windows can’t validate the uninstall action.
• Repair deployment components — Microsoft Store, App Installer, and related services work together, so one broken piece can block removal.
• Fix provisioned package mismatch — Some apps exist as a user install and as a provisioned image item for new accounts, and the two can get out of sync.
• Use admin rights — Some packages need elevated removal, and policy or security tools can block it.

If the failing app came from Microsoft Store or shipped with Windows, the fix is often about repairing the Store and deployment stack, not hunting for a separate uninstaller file.

0x80073CFA Removal Failed On Windows 11 And 10

Start here even if you plan to use PowerShell later. These steps solve a large share of cases with minimal risk, and they also set up the deeper steps so they succeed more often.

Try the fast sequence that clears stuck deployment

1. Restart the PC — A restart closes open processes and clears pending deployment locks that can block removal.
2. Run the Store apps troubleshooter — Open Settings, then System, then Troubleshoot, then Other troubleshooters, and run Windows Store Apps.
3. Reset the Store cache — Press Win + R, type wsreset.exe, and wait until it finishes and Store opens.
4. Repair the target app — Go to Settings, Apps, Installed apps, open the app menu, choose Advanced options, then select Repair.
5. Reset the target app — If Repair didn’t change anything, select Reset, then try uninstall again.

Retry uninstall right after this sequence. A cache reset plus a restart often clears the failure loop because the deployment system stops tripping over stale Store data.

Use this decision table to pick the next step

If the error returns after the basics, move on. The next sections give you control that Settings can’t provide.

Remove A Stubborn Store App With PowerShell

PowerShell can remove the exact package that Windows refuses to delete. This is the most direct fix when the uninstall button loops, and it’s also the step many people try first. Doing the quick fixes above still helps, since it reduces the chance of a partial removal.

Remove the app for your current account

1. Open Terminal as admin — Right-click Start, choose Terminal (Admin), and approve the prompt.
2. List matching packages — Run Get-AppxPackage | Select Name, PackageFullName | more and search for the app name.
3. Copy the PackageFullName — Copy the full string for the target package.
4. Remove the package — Run Remove-AppxPackage -Package and wait for the prompt to return.

If the removal completes, the app should vanish from Start and from Settings. If you still get “0x80073CFA Removal Failed” inside Terminal, Windows is still blocking the deployment remove action, often because the package is tied to other users, provisioned apps, or broken registrations.

Remove the package for all users and new accounts

Some built-in apps are provisioned into the Windows image so new user profiles receive them. Removing both the installed layer and the provisioned layer is cleaner when you truly want it gone.

1. Confirm the package identity — Run Get-AppxPackage -AllUsers *AppName* to verify the package name.
2. Remove installed copies — Run Get-AppxPackage -AllUsers *AppName* | Remove-AppxPackage.
3. Remove the provisioned copy — Run Get-AppxProvisionedPackage -Online | Where-Object DisplayName -like "*AppName*" | Remove-AppxProvisionedPackage -Online.
4. Restart the PC — A restart clears lingering registrations and refreshes Start entries.

If the target is a core Windows component, removal may still be blocked. In that case, repairing Store components and system files often clears the block, then PowerShell removal works on the next try.

Repair Microsoft Store And App Installer Components

When uninstall failures happen across multiple apps, the shared Store pipeline is often at fault. Microsoft Store, App Installer, and related services work as a bundle. Fixing that bundle can turn a stuck uninstall into a normal one.

Repair and reset Store components from Settings

1. Open Installed apps — Go to Settings, Apps, then Installed apps.
2. Repair Microsoft Store — Open Microsoft Store, choose Advanced options, select Repair, then retry uninstall.
3. Reset Microsoft Store — If Repair didn’t help, select Reset, sign back in if prompted, then retry.
4. Repair App Installer — Open App Installer, select Repair, then retry uninstall.
5. Reset App Installer — If needed, select Reset, then restart once.

Re-register Store apps when installs and icons break

This step is useful when Store apps refuse to launch, tiles disappear, or many packages misbehave. It refreshes registrations without wiping Windows.

1. Open Terminal as admin — Use Terminal (Admin) again.
2. Re-register packages — Run Get-AppxPackage -AllUsers | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}.
3. Restart the PC — Reboot so registrations load cleanly.

After re-registering, try uninstall again from Settings first, then PowerShell if needed.

If you want official and reference explanations for Store app repair paths, you can cross-check Microsoft community threads and Windows deployment write-ups here: Microsoft Q&A discussion and package removal notes.

Repair System Files That Block App Deployment

If app removal fails after Store repair, the system image may have file damage that blocks deployment actions. Windows includes two built-in tools that can repair the component store and protected system files: DISM and SFC.

Run DISM then SFC in the right order

1. Open Terminal as admin — Right-click Start, choose Terminal (Admin).
2. Run DISM repair — Enter DISM /Online /Cleanup-Image /RestoreHealth and wait for completion.
3. Run System File Checker — Enter sfc /scannow and let it reach 100%.
4. Restart the PC — Reboot once, then attempt uninstall again.

DISM repairs the component store that SFC pulls from. SFC then replaces missing or broken protected files. If either tool reports fixes, retry uninstall before you change anything else.

Use a local repair source when online repair fails

DISM can fail when it can’t fetch clean files through Windows Update. A Windows ISO that matches your installed version can serve as a repair source. If you’re comfortable with that step, mount the ISO, run DISM with a Source path to the install image, then run SFC again.

If you’d like a plain walkthrough for DISM and SFC flow, this Windows 11 guide is a solid reference: DISM and SFC steps.

Last Resort Fixes That Keep Your Files

At this stage you’ve cleared cache, repaired Store components, tried package removal, and repaired system files. If 0x80073cfa still blocks removal, the issue is often tied to a damaged user profile or a deeper servicing problem.

Try a fresh admin profile for a clean uninstall

1. Create a local admin account — In Settings, Accounts, Other users, add a new user, then set the account type to Administrator.
2. Sign in once — Log out, then log in to the new admin profile so Windows builds it fully.
3. Uninstall from the new profile — Remove the app via Settings or PowerShell, then restart.

If the uninstall works in the new profile, your original profile likely has broken app registration entries. You can keep using the new profile or migrate your files and settings at your own pace.

Run an in-place repair install when servicing is stuck

1. Back up must-have files — Copy files you can’t lose to an external drive or your preferred storage service.
2. Download Windows installation media — Use Microsoft’s installer for your Windows version and language.
3. Run setup and keep files — Start setup from inside Windows and choose the option that keeps personal files and apps.
4. Retry removal — After the repair completes, remove the app again via Settings or PowerShell.

This refreshes servicing components without wiping your data, and it often clears stubborn deployment errors that survive DISM and SFC.

Reduce impact if you choose not to uninstall

Sometimes the app is harmless but annoying. If removal keeps failing and you don’t want deeper repair work, you can limit the app’s footprint and move on.

1. Disable startup entries — Open Task Manager, go to Startup apps, and disable items tied to the app.
2. Restrict background activity — In Settings, Apps, open the app page and limit its background access if the toggle exists.
3. Unpin and hide shortcuts — Remove pins from Start and the taskbar to keep it out of sight.

When you see “0x80073CFA Removal Failed,” the safest rhythm is simple: try one phase, retry uninstall, then stop once it works. That keeps your system clean, and it makes the fix easier to repeat if the error returns later.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback