Home › Microsoft Store / UWP Apps › 0x80073CF3

Microsoft Store / UWP Apps · 0x80073CF3 · Windows 10 / Windows 11

Microsoft Store UWP App Install Fails with Error Code 0x80073CF3 - Windows 10/11

Error occurs due to corrupted staging record or dependency issues; fix by removing and reinstalling the app.

Error Details

FactValueSourceNote
Exact error string0x80073CF3Event Viewer > AppXDeployment Operational logs-> Event ID 402, 404 or 440
Affected build rangeWindows 10/11Microsoft Docs
Registry key involvedHKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\AppxDeploymentClientRegistry Editor-> Check for staging locks
Relevant service/endpoint URLhttp://localhost:4736/appinstallerApp Installer Service
Log line signatureError code 0x80073CF3 in AppXDeployment Operational logsEvent Viewer

Log Files to Check

What This Error Actually Means

The error code 0x80073CF3, also known as ERROR_INSTALL_PACKAGE_OPEN_FAILED, is raised by the Windows AppX Deployment Service (AppXSvc) when a Universal Windows Platform (UWP) application fails to install, update, or repair from the Microsoft Store. This error typically occurs due to issues with package staging, corrupted files, insufficient disk space, or conflicts with existing applications. The specific component responsible for this error is the AppXDeploymentClient, which manages the installation and deployment of UWP apps.

Affected Versions and Scope

This error affects Windows 10 and Windows 11 operating systems across various build numbers. It can occur in both enterprise environments with strict tenant configurations as well as consumer devices. However, it does not affect older versions like Windows 8 or earlier. The issue is particularly prevalent in scenarios where multiple users share the same device or when deploying applications via group policies or Intune.

Where To Look First: Logs and Event IDs

To diagnose this error, start by examining the Microsoft-Windows-AppXDeployment-Operational.evtx log file located at C:\Windows\System32\winevt\Logs. You should look for entries containing the exact string "Error code 0x80073CF3". Additionally, filter Event Viewer logs by searching for specific event IDs: 402 and 404. These events provide detailed information about why the package installation failed.

Root Causes

Corrupted or Partially Installed Packages

When a UWP application is partially installed or corrupted, it can prevent other applications from installing correctly due to conflicts in the staging area. To identify such issues, use PowerShell cmdlets like Get-AppxPackage -AllUsers | Where-Object {$_.Status -ne 'OK'}. This command lists all packages that are not in an OK status.

Disk Space Insufficiency

The staging area for UWP applications is located at %ProgramFiles%\WindowsApps, and it requires a minimum of 1 GB free space, with 5 GB recommended. Use the PowerShell cmdlet Get-PSDrive C | Select Free to check available disk space.

Dependency Package Issues

Missing or outdated dependency packages such as Microsoft.VCLibs can cause installation failures. To identify missing dependencies, use the command Get-AppxPackage -Name '*packagename*' -AllUsers | Select Name, Version, Status. If a dependency is found to be missing, download and install it from GitHub or another trusted source.

Virus Scanner Interference

Windows Defender Antivirus might block the installation of UWP applications due to false positives. To verify this, temporarily exclude the staging folder C:\Program Files\WindowsApps in Windows Security > Virus & threat protection > Manage settings > Exclusions and retry the installation.

Fix Procedure

  1. Remove Corrupted Package: Use PowerShell cmdlet Get-AppxPackage -AllUsers -Name '*PackageName*' | Remove-AppxPackage -AllUsers. Reopen Microsoft Store and get updates to reinstall the package.
  2. Register/Re-stage Application: If removing is not an option, use Add-AppxPackage -Register -DisableDevelopmentMode "C:\Program Files\WindowsApps\\AppxManifest.xml". This re-registers existing staged files without redownloading.
  3. Install Missing Dependencies: Download and install missing dependency packages using the command Add-AppxPackage -Path .\Microsoft.UI.Xaml.2.x.msix.
  4. Clear Store Cache: Run wreset.exe from an elevated command prompt to reset the Microsoft Store without removing installed apps.
  5. Reset AppX Deployment Service: Use PowerShell cmdlets: net stop AppXSvc && net start AppXSvc. If the service cannot be stopped, use Restart-Service -Name AppXSvc -Force.
  6. Virus Scanner Exclusion: Add a temporary exclusion for the staging folder in Windows Security > Virus & threat protection > Manage settings > Exclusions and retry installation.
Be cautious when stopping services like AppXSvc as it can disrupt ongoing installations or updates on enrolled devices.

Error Code Variants

CodeDescription
0x80073CF0Dependency package is missing or outdated.
0x80073CFFThe staging area is locked by another process.
0x80070070Inadequate disk space for the staging area.

Verification

After applying fixes, re-open Microsoft Store > Library and trigger the update/install. Verify success by checking Event Viewer logs for event ID 403 (success) related to the package installation. Additionally, run Get-AppxPackage -Name '*packagename*' | Select Status. The output should show 'OK' under the status field.

Prevention

To prevent recurrence of this issue, ensure that your organization maintains sufficient disk space on Windows installations and regularly updates dependency packages. Implement a policy to monitor and manage installed applications through Intune admin center > Devices > Configuration Profiles > Create Profile > Apps & Browser > App Management Policies. Additionally, configure OMA-URI settings like ./Device/Vendor/MSFT/AppManagement/DisableAppInstall in your device configurations to enforce strict control over app installations.
A quick diagnostic shortcut is to use the PowerShell cmdlet Get-WinEvent -LogName "Microsoft-Windows-AppXDeployment-Operational" | Where-Object {$_.Message -like "*0x80073CF3*"} . This command filters out all events related to this specific error code directly from the event log.

Sources & References

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.