Home › DevOps › 0x80073CF3: Package Failed Updates, Dependency, or Conflict Validation — Windows Fix
Beginner 3 min · November 21, 2026

0x80073CF3: Package Failed Updates, Dependency, or Conflict Validation — Windows Fix

0x80073CF3 means an app package failed one of Windows' pre-install checks: a missing framework dependency, a newer version already installed.

N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Lessons pulled from things that broke in production.

Follow
✓ Production
production tested
November 21, 2026
last updated
2,136
articles · all by Naren
Before you start⏱ 7 min
  • ✓Windows PowerShell basics
 ● Production Incident 🔎 Debug Guide
⚡Quick Answer
  • One of three checks failed: dependencies, version, or architecture.
  • Get the ActivityID from the error, then: Get-AppPackageLog -ActivityID .
  • Missing framework (VCLibs, .NET Native, Windows App Runtime): install it, or pass -DependencyPath.
  • Newer version installed: remove it (Remove-AppxPackage) or raise the package version.
  • Wrong architecture: use the x64/arm64 package that matches the device.
  • Re-downloading the same package won't help.
✦ Definition~90s read
What is Windows Error 0x80073CF3?

0x80073CF3 (ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED, message 'Package failed updates, dependency, or conflict validation') is returned by Add-AppxPackage or the App Installer when an MSIX/APPX package fails validation before installation.

★
Before Windows installs the app, it checks the paperwork: are the parts it needs already there, is a newer copy already installed, is it built for this kind of PC.
Plain-English First

Before Windows installs the app, it checks the paperwork: are the parts it needs already there, is a newer copy already installed, is it built for this kind of PC. One failed check stops the install, but the error doesn't say which one.

A line-of-business MSIX installed fine on old laptops and failed with 0x80073CF3 on every new one. The package was fine; the new laptops lacked a framework it depends on.

Read the Deployment Log

The error includes an ActivityID. The log for that activity says which check failed.

log.ps1POWERSHELL
1
2
3
Add-AppxPackage .\Orders.msix
# ... ActivityID: 4a1c...
Get-AppPackageLog -ActivityID 4a1c...
🎯 Key Takeaway
The log names the failed check.

Missing Dependency

Install the framework package first, or deploy it together with the app.

deps.ps1POWERSHELL
1
Add-AppxPackage .\Orders.msix -DependencyPath .\Microsoft.VCLibs.x64.14.00.Desktop.appx
🎯 Key Takeaway
Ship the framework too.

Version Conflict

Windows won't install an older version over a newer one. Remove the newer version (for all users if needed), or raise your package version.

version.ps1POWERSHELL
1
2
Get-AppxPackage *Orders* -AllUsers | Select Name, Version
Get-AppxPackage *Orders* -AllUsers | Remove-AppxPackage -AllUsers
🎯 Key Takeaway
No silent downgrades.
● Production incidentPOST-MORTEMseverity: high

Fine on Old Laptops, Failed on New Ones

Symptom
Add-AppxPackage: Deployment failed with HRESULT: 0x80073CF3, Package failed updates, dependency, or conflict validation.
Assumption
IT assumed a corrupt download.
Root cause
The package depends on Microsoft.VCLibs.140.00.UWPDesktop. The old laptops had it from another app; the new image didn't.
Fix
Added the VCLibs framework package to the deployment with -DependencyPath.
Key lesson
  • Read the deployment log.
  • Ship dependencies with the package.
  • Re-downloading doesn't fix validation errors.
Production debug guideWhich validation failed?3 entries
Symptom · 01
Log mentions a framework/dependency
→
Fix
Install it or use -DependencyPath.
Symptom · 02
Log mentions a higher version installed
→
Fix
Remove the installed version for all users, or bump the version.
Symptom · 03
Log mentions processor architecture
→
Fix
Use the package for the device's architecture.
⚙ Quick Reference
3 commands from this guide
FileCommand / CodePurpose
log.ps1Add-AppxPackage .\Orders.msixRead the Deployment Log
deps.ps1Add-AppxPackage .\Orders.msix -DependencyPath .\Microsoft.VCLibs.x64.14.00.Deskt...Missing Dependency
version.ps1Get-AppxPackage *Orders* -AllUsers | Select Name, VersionVersion Conflict

Key takeaways

1
Three checks
dependencies, version, architecture.
2
Get-AppPackageLog -ActivityID.
3
Ship dependencies.
4
Remove newer versions first.

Common mistakes to avoid

3 patterns
×

Re-downloading the package

Symptom
Same error.
Fix
Read the deployment log.
×

Not shipping framework dependencies

Symptom
Works only on some machines.
Fix
-DependencyPath.
×

Installing an older build over a newer one

Symptom
Conflict validation fails.
Fix
Remove the newer one or bump the version.
INTERVIEW PREP · PRACTICE MODE

Interview Questions on This Topic

Q01SENIOR
How do you find why an MSIX install failed?
Q01 of 01SENIOR

How do you find why an MSIX install failed?

ANSWER
Get-AppPackageLog with the ActivityID from the error, or the AppXDeployment-Server event log.
FAQ · 2 QUESTIONS

Frequently Asked Questions

01
How do I fix 0x80073CF3?
02
Is 0x80073CF3 a corrupt download?
N
Naren Founder & Principal Engineer

20+ years shipping production infrastructure and CI/CD at scale. Lessons pulled from things that broke in production.

Follow
✓ Verified
production tested
November 21, 2026
last updated
2,136
articles · all by Naren
🔥

That's Platform. Mark it forged?

3 min read · try the examples if you haven't

←
Previous
Windows Error 0x80073D23: Special Profile Deployment Not Allowed
3 / 4 · Platform
Next
Exit Code 143: SIGTERM in Docker, Kubernetes and YARN
→