- Software and digital services
- Operating system
0x80073CFB
Windows 0x80073CFB on operating system: package conflict
Risk level
Low
Usually safe to check without specialist tools.
Urgency
Medium
Quick answer
Error 0x80073CFB (ERROR_PACKAGE_ALREADY_EXISTS) on Windows indicates that the app package is already installed and reinstallation is blocked, either because an identical package is registered or a rebuilt or re-signed package is no longer bitwise identical.
Safety first
Safe checks you can perform
- Identify the conflicting package in AppxDeployment-Server or Get-AppxLog
- Uninstall the existing package for the current user before reinstalling
- Remove the old package for every user or increment the package version number
Leave these tasks to a qualified professional
- Do not attempt this professional task: System-wide package removal by the system administrator or IT support
- Do not attempt this professional task: Escalation to Microsoft Support or the package developer
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
System-wide package removal by the system administrator or IT support
What they doHave a system administrator remove the old package for every user on the system before installing the new package.
They must show youThe 0x80073CFB (ERROR_PACKAGE_ALREADY_EXISTS) event in Applications and Services Logs > Microsoft > Windows > AppxDeployment-Server..
In writingConflicting package name removed across user accounts and confirmation of successful reinstallation..
Escalation to Microsoft Support or the package developer
What they doContact Microsoft Support if a Microsoft Store app continues to fail with 0x80073CFB, or request a rebuilt and re-signed package with an incremented version number from the developer.
They must show youThe Get-AppxLog output and the AppxDeployment-Server event log showing 0x80073CFB..
In writingInstalled package version versus incoming package version and the support case reference..
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Identify the conflicting package in AppxDeployment-Server or Get-AppxLog
- Who:
- user
- How:
- Open Event Viewer (eventvwr.msc) and check Applications and Services Logs > Microsoft > Windows > AppxDeployment-Server, or run Get-AppxLog | Out-GridView in PowerShell to see the exact package name behind 0x80073CFB.
- Result that matters:
- The deployment log identifies the registered package name and confirms ERROR_PACKAGE_ALREADY_EXISTS.
- If Once you know the conflicting package name, proceed to uninstall the existing package first.
- If If the package does not appear under your current user, check whether another user on the PC has it installed.
- Evidence to keep:
- Event entry for 0x80073CFB in Microsoft-Windows-AppXDeploymentServer/Operational or Get-AppxLog output.
Evidence: MSIX deployment troubleshooting - MSIX | Microsoft Learn · Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Learn
Uninstall the existing package for the current user before reinstalling
- Who:
- user
- How:
- Uninstall the existing app in Windows or run Get-AppxPackage <PackageName> | Remove-AppxPackage in PowerShell, then reinstall the app from Library in Microsoft Store.
- Result that matters:
- The existing package registration for your user account is removed before the new installation starts.
- If If the package installs without error 0x80073CFB after removing the existing copy, the conflict is resolved.
- If If 0x80073CFB still appears, check for registrations across other user accounts on the system.
- Evidence to keep:
- Completion of Remove-AppxPackage and clean reinstallation from Microsoft Store Library.
Evidence: Fix problems with apps from Microsoft Store · MSIX deployment troubleshooting - MSIX | Microsoft Learn
Remove the old package for every user or increment the package version number
- Who:
- user
- How:
- Remove the old package for every user on the system before installing the new package, or if you are deploying a rebuilt or re-signed package, increment the version number of the app and then rebuild and re-sign the package.
- Result that matters:
- All prior user registrations are cleared or the package carries a higher version number than the installed copy.
- If If removing the package across all users or incrementing the version allows deployment, no further action is needed.
- If If the issue persists with a Store download, contact your system administrator or Microsoft Support.
- Evidence to keep:
- Package version number in AppxManifest.xml and removal confirmation across system user accounts.
Evidence: Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Learn
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x80073cfb Windows
- error 0x80073CFB Microsoft Store
- ERROR_PACKAGE_ALREADY_EXISTS
- Microsoft Store error 0x80073CFB
- package already exists 0x80073CFB
- paquete ya existe 0x80073CFB
What it means
When Windows reports error code 0x80073CFB (ERROR_PACKAGE_ALREADY_EXISTS), the deployment engine blocks package installation because the provided package is already registered on the system. According to official Microsoft Learn documentation, this happens when an identical package is already registered for the current user, when an older copy remains installed for another user on the system, or when installing a rebuilt or re-signed package that is no longer bitwise identical to the already installed version (since the digital signature is part of the package). A single error code never proves that hardware has failed or that a license is invalid.
Symptoms and causes
Probable causes · in order
- Identical package already registered for the current userCommon
An existing registration of the same app package is already present for the user account and blocks reinstallation until the existing package is uninstalled first.
Evidence: MSIX deployment troubleshooting - MSIX | Microsoft Learn
- Rebuilt or re-signed package is not bitwise identical to the installed packagePossible
Because the digital signature is part of the package, rebuilding or re-signing a package without incrementing its version number makes it no longer bitwise identical to the installed copy and blocks reinstallation.
Evidence: Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Learn
- Old package still installed for another user account on the systemPossible
Another user profile on the same computer still has the old package installed, preventing the new package from being registered until the old package is removed for every user on the system.
Evidence: Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Learn
Virtual technician
Does 0x80073CFB still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Fix problems with apps from Microsoft Store
Microsoft · 2026 · official_doc
- 2
Solucionar problemas relacionados con las aplicaciones de Microsoft Store
Microsoft · 2026 · official_doc
- 3
MSIX deployment troubleshooting - MSIX | Microsoft Learn
Microsoft · 2026 · official_doc
- 4
Solución de problemas de implementación de MSIX - MSIX | Microsoft Learn
Microsoft · 2026 · official_doc
- 5
Troubleshooting packaging, deployment, and query of Windows apps - Win32 apps | Microsoft Learn
Microsoft · 2026 · official_doc
- 6
Microsoft · 2026 · official_doc
Was this entry useful?