| Previous | Next |
| E_MULTIPLE_EXTENSIONS_FOR_APPLICATION | E_APPLICATION_MANAGER_NOT_RUNNING |
E_MULTIPLE_PACKAGES_FOR_FAMILY
Package-family resolution returned more than one unsupported candidate
E_MULTIPLE_PACKAGES_FOR_FAMILY is HRESULT 0x80270256 (signed decimal -2144927146, unsigned decimal 2150040150). The failure belongs to facility 39 (FACILITY_SHELL), with code field 0x0256. AllStat records: “This app's package family has more than one package installed. This is not supported.”
What package family means
A package family groups packages that share the package name and publisher identity. Windows normally uses package type, architecture, version, user registration, and related-set metadata to resolve the applicable main application package. This HRESULT says the activation path encountered a multiplicity it could not legally or unambiguously reduce to one target.
Do not assume that any two packages with the same family are automatically invalid. Resource and optional packages can legitimately participate in a package graph. The reported condition is specifically that the activation resolver found more than one installed package in a role where its contract supports only one. Evidence must therefore include package type and relationship, not just family name.
Typical cause branches
- A failed upgrade leaves two main-package registrations for the same family visible to one user.
- Manual deployment or image customization installs conflicting architecture/version candidates outside the expected servicing path.
- A related-set or optional-package configuration is malformed and candidates are classified incorrectly.
- User registration and machine provisioning disagree after profile migration or rollback.
- Automation chooses a family name when it should identify one application/package instance more precisely.
Evidence to collect
- Package family name and all matching package full names for the affected user and for all users.
- Version, architecture, package type, status, install location, dependencies, and related-set membership.
- Provisioned-package state, staged state, and per-user registration state.
- Deployment activity ID and AppX logs for the update, rollback, or sideload operation that preceded the failure.
- The AppUserModelID and activation contract that triggered family resolution.
Diagnostic sequence
- Enumerate matching packages without deleting anything and classify each as main, framework, resource, optional, or bundle-related.
- Identify the one package the application deployment model expects to be the activatable main package.
- Compare per-user registration with machine staging and provisioning to find orphaned registrations.
- Use the supported deployment/servicing mechanism to complete rollback, update, or removal; do not manually delete files from WindowsApps.
- Re-query the family after repair and confirm that one supported activation candidate remains for the user.
Retry and recovery
An immediate activation retry will traverse the same package graph. Retry after the deployment transaction completes or the conflicting registration is repaired. If servicing is currently active, wait for its activity to reach a terminal state rather than launching concurrent remove/add operations.
Distinguish it from extension ambiguity
E_MULTIPLE_EXTENSIONS_FOR_APPLICATION resolves one application but finds too many declarations for a contract. E_MULTIPLE_PACKAGES_FOR_FAMILY fails earlier while choosing the package candidate. E_APPLICATION_NOT_REGISTERED is the opposite absence case.
Practical scenario
A test image is captured during an interrupted app update. One user profile retains the old main-package registration while the newer main package is also registered. Activation by family-dependent metadata returns E_MULTIPLE_PACKAGES_FOR_FAMILY. Completing supported AppX cleanup for the stale registration resolves the graph; changing file permissions does not.
Official Microsoft references
- Microsoft: COM error codes for security and setup
- Microsoft: troubleshoot package deployment and query
- Microsoft: Appx PowerShell module
- Microsoft: application identity in a package manifest
- Microsoft: app activation by AppUserModelID
Looking for a different code? Search another status or error code.