Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80073CF6

0x80073CF6: Package Could Not Be Registered – Fixing MSIX Dependency Errors

9 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

0x80073CF6 is ERROR_INSTALL_REGISTRATION_FAILURE, and Microsoft’s published instruction for it is to read the AppXDeployment-Server event log. 0x80073CF3 is the validation stage failing, which has three documented causes, not one. Get the log entry before you start installing frameworks.

Run these in an elevated PowerShell session; run the first one immediately after the failure

Get-AppxLog
Add-AppxPackage -Path .\app.msix -DependencyPath .\framework1.appx,.\framework2.appx
Get-AppxPackage -Name <PackageName> -AllUsers | ForEach-Object {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
  1. Read what Get-AppxLog returns. It names what could not be resolved, which decides everything after this.
  2. The same records are in Event Viewer under Applications and Services Logs, Microsoft, Windows, AppXDeployment-Server, Operational. The packaging-side channel is AppxPackaging, Operational.
  3. If a framework is named, get it from the vendor in the same architecture as the application and supply it with -DependencyPath, or install it first.
  4. If the log points at the user rather than the package, re-register per user with the third command. The package must already be staged for that to work.

Frameworks are architecture-specific. A 32-bit application on 64-bit Windows needs the 32-bit framework however many 64-bit ones are present.

If it installs, stop here. If the log names an architecture or a conflict rather than a dependency, the next section explains why 0x80073CF3 is not only a missing-framework code.

Why it happens

Deployment happens in two halves. Staging copies the payload into the machine-wide package repository and validates it. Registration then writes the per-user entries that make the application visible and launchable for one account: Start menu entries, protocol and file type handlers, and the state repository records that tie the identity to that profile.

0x80073CF3 is ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED, and Microsoft’s own text is broader than the name suggests: the package failed update, dependency or conflict validation. Three possible causes are listed – the incoming package conflicts with an installed package, a specified package dependency cannot be found, and the package does not support the correct processor architecture. Reading it as a missing framework and nothing else sends a reader with an architecture problem hunting for runtimes that were never absent.

0x80073CF6 is the second half failing: the payload is on disk and valid, but writing the user’s registration did not complete. That points at the profile rather than the package, which is why the same package often installs cleanly for a different account on the same machine. Microsoft does not publish a cause list for it – it publishes an instruction, which is to check the AppXDeployment-Server event log.

A framework package is missing or too old

You have this one if The deployment log names a framework – a C++ runtime framework, a XAML UI framework – rather than your application.

  1. Get the framework from the vendor or from the same source as the application, in every architecture the device needs.
  2. Supply them in the same operation with -DependencyPath, which takes a comma-separated list of file paths.
  3. A manifest declares each dependency by identity and minimum version. A present-but-older framework fails resolution exactly as an absent one does.

It is the architecture, not the dependency

You have this one if 0x80073CF3 with nothing named as missing, or the package installs on one machine and not on another of a different processor type.

  1. Compare the architectures in the bundle against the device. Microsoft lists ‘the package doesn’t support the correct processor architecture’ as a cause of this code.
  2. If the deployment failed specifically on architecture rather than validation as a whole, the code is 0x80073D10, ERROR_INSTALL_WRONG_PROCESSOR_ARCHITECTURE.
  3. Ask the vendor for a build covering that architecture rather than trying to force the one you have.

The incoming package conflicts with one already installed

You have this one if 0x80073CF3 on a machine that already has a related package, a resource package or an earlier optional package from the same family.

  1. List everything under the family name with Get-AppxPackage -Name <name> -AllUsers from an elevated session.
  2. Remove the conflicting registration for every user, then install again.
  3. If the application ships optional or related packages, deploy them as a set with -ExternalPackages rather than individually – that install is atomic, so a partial state cannot be left behind.

The per-user state is damaged, not the package

You have this one if 0x80073CF6, and the same package registers without complaint for a different account on the same machine.

  1. Re-register per user from the staged files with -Register plus -DisableDevelopmentMode. Microsoft documents that combination as the way to register an existing installation that was disabled, did not register, or became corrupted.
  2. If several unrelated packages fail the same way for one profile, test with a freshly created profile before spending more time on the package.
  3. 0x80073CFC is a different statement again: Microsoft’s published text is ‘The app can’t be started. Try reinstalling the app.’ That is a post-install problem, not a deployment one.

Full reference

What each code in this family actually says

Code Microsoft’s published meaning
0x80073CF6 ERROR_INSTALL_REGISTRATION_FAILURE. The package cannot be registered; check the AppXDeployment-Server event log
0x80073CF3 ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED. Failed update, dependency or conflict validation: a conflict with an installed package, a dependency that cannot be found, or the wrong processor architecture
0x80073CFD ERROR_INSTALL_PREREQUISITE_FAILED. A specified install prerequisite could not be satisfied
0x80073CFC ERROR_NEEDS_REMEDIATION. The app can’t be started. Try reinstalling the app
0x80073CF0 ERROR_INSTALL_OPEN_PACKAGE_FAILED. The package could not be opened – unsigned, publisher name not matching the signing certificate subject, or the file not found at the specified location

0x80073CFD says a prerequisite was not satisfied. It does not say which, and Microsoft does not name the minimum OS build as the usual one. Check the build with winver because it is quick, but read the log before concluding that is what failed.

Registering from a loose file layout

Add-AppxPackage -Register <path>\AppXManifest.xml registers an application in development mode from a folder of unpackaged files. Adding -DisableDevelopmentMode changes what the operation means: it registers an existing package installation that was disabled, did not register, or became corrupted. That is the form to use when you are repairing a staged package rather than developing one, and it is why the re-registration one-liner in the fix layer carries both.

There is a limit on how many packages can be sideloaded this way. When it is reached the deployment fails with 0x80073D11, ERROR_DEV_SIDELOAD_LIMIT_EXCEEDED, and the answer is to uninstall a sideloaded package – or, better, to sign the package and deploy it normally.

Log locations, and which to read

Where What is in it
Get-AppxLog The log for the most recent deployment operation. Run it straight after the failure
Get-AppxLog -All Every deployment log on the machine. More information is available when run elevated
AppXDeployment-Server, Operational The channel Microsoft names for 0x80073CF6 and 0x80073CF3. Staging, dependency resolution and registration
AppxPackaging, Operational The channel Microsoft names for package-opening failures such as 0x80073CF0

When Add-AppxPackage or Remove-AppxPackage report a failure they return an ActivityID, and that is the value Get-AppxLog takes to pull the record for that specific attempt rather than whatever ran last.

When the log names nothing useful

  • Repair the component store: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, then reboot and retry. Deployment leans on servicing, and a damaged component store produces failures that read as package problems.
  • Test with a new local profile. If the package registers there, the fault is the original profile’s state and not the package.
  • Check whether the package is staged at all. A registration failure on something that was never staged is a different problem from one on a package sitting in the repository.
  • Confirm the machine is not out of disk space. That failure has its own code, 0x80073CF4, but a nearly full volume produces odd secondary failures too.

Every code this article covers

Code What it points at Source
0x80073CF6 ERROR_INSTALL_REGISTRATION_FAILURE: the package cannot be registered. Microsoft’s instruction is to check the AppXDeployment-Server event log Microsoft Learn
0x80073CF3 ERROR_INSTALL_RESOLVE_DEPENDENCY_FAILED: the package failed update, dependency or conflict validation – a conflict with an installed package, a dependency that cannot be found, or the wrong processor architecture Microsoft Learn
0x80073CFD ERROR_INSTALL_PREREQUISITE_FAILED: a specified install prerequisite could not be satisfied. Microsoft does not name which prerequisites are typical Microsoft Learn
0x80073CFC ERROR_NEEDS_REMEDIATION: Microsoft’s published text is ‘The app can’t be started. Try reinstalling the app’ Microsoft Learn

Confirm the fix worked

  1. The application launches from Start, not just from the install command’s success message.
  2. Get-AppxPackage -Name <name> returns it for the user who needs it, not only under -AllUsers.
  3. Get-AppxLog for the successful run shows registration completing.
  4. A second profile on the same machine can launch it too, if the deployment was meant to cover more than one user.

Questions people ask about this

Do I need to install frameworks separately, or will the installer fetch them?

Add-AppxPackage does not go looking for them. You either install the framework packages first or pass them in the same operation with -DependencyPath. A Store install resolves dependencies for you; a sideloaded one does not.

0x80073CF3 with no framework named in the log – what now?

Check the architecture and check for a conflicting package. Microsoft lists three causes for that code, and only one of them is a missing dependency. If the real fault is architecture, the more specific code is 0x80073D10.

Is 0x80073CFC an install failure?

Not as Microsoft describes it. The published text is that the app cannot be started and to try reinstalling it, which places it after deployment rather than during it. Treat it as a signal to remove and reinstall cleanly rather than to repair the deployment stack.

Why does the same MSIX work for one user and fail for another?

Because staging is machine-wide and registration is per user. A package that is staged correctly can still fail to write one profile’s registration, which is what 0x80073CF6 reports. Re-register that profile from the staged files before touching the package.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix MSI 1619 and 1620: This Installation Package Could Not Be Opened Free Fix 0x80073CFB: The Package Is Already Installed or Cannot Be Downgraded License Error 0x803F8001: This App Is Not Licensed for Your Account or This Device Free Fix Error 1601 and 1719: Windows Installer Service Could Not Be Accessed
โ† Back to Knowledge Base