| Previous | Next |
| ERROR_PRI_MERGE_MULTIPLE_PACKAGE_FAMILIES_NOT_ALLOWED | ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED |
ERROR_PRI_MERGE_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED
Packages for a PRI file merge must not include multiple main packages.
ERROR_PRI_MERGE_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED is a domain-specific Windows result.
Likely impact: Choosing a main package by file order makes output nondeterministic and can bind resources to the wrong identity.
Typical causes
- two main-package outputs are included.
- a bundle was expanded incorrectly.
- artifact classification marks a resource package as main.
- incremental build leaves an obsolete main PRI.
Troubleshooting steps
- Verify that the merge has exactly one main package that supplies authoritative identity and schema.
- Collect package role of every input and main package identities.
- Correlate artifact manifest with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic.
Useful evidence
- Collect build directory age and hashes.
- Collect MakePri classification diagnostic.
Recovery and retry
Select one authoritative main package and include only its compatible resource packages.
Related errors
ERROR_PRI_MERGE_MULTIPLE_PACKAGE_FAMILIES_NOT_ALLOWED finds distinct families; this code can occur within one family with multiple main packages
Example
A staging directory contains main PRI files from debug and release builds of the same app. Cleaning the directory leaves one authoritative main package.
References
Looking for a different code? Search another status or error code.