0x80073CF3 means the package failed update, dependency, or conflict validation. The documented causes are:
- The incoming package conflicts with an installed package.
- A required package dependency cannot be found.
- The package does not support the correct processor architecture.
For Intune-delivered Store apps, the same code is also documented as a package update, dependency, or conflict validation failure.
To identify the conflicting or missing package, start with deployment diagnostics rather than package inventory comparison alone:
- Check the AppXDeployment-Server event log first. This is the primary log called out for
0x80073CF3.- Open Event Viewer.
- Go to Applications and Services Logs > Microsoft > Windows.
- Review AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational.
- If the install command returned an ActivityID, use
Get-AppxLogwith that ActivityID.-
Get-AppxLogreturns the app package installation log created during deployment. - When
Add-AppxPackageorRemove-AppxPackagefails, the returned ActivityID can be used to pull the related errors, warnings, and detailed deployment events.
-
- Use the log details to determine which of these applies:
- a conflicting installed package
- a missing dependency package/framework
- an architecture mismatch
- If the log shows a dependency name or framework package, that is the package to investigate on the device.
Get-AppxPackage -AllUsers and Get-AppxProvisionedPackage -Online can help with inventory validation, but the documented method for isolating the actual conflicting or missing package is the AppXDeployment-Server log and Get-AppxLog output, because those surfaces report the specific dependency/conflict condition for the failed deployment.