What does Windows error code 15156 (ERROR_PRI_MERGE_MAIN_PACKAGE_REQUIRED) mean?

Previous	Next
ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED	ERROR_PRI_MERGE_RESOURCE_PACKAGE_REQUIRED

ERROR_PRI_MERGE_MAIN_PACKAGE_REQUIRED

Packages for a PRI file merge must include one main package.

ERROR_PRI_MERGE_MAIN_PACKAGE_REQUIRED is Windows status 15156 (0x00003B34) associated with a PRI merge set with no main package. The system meaning is “this condition” Preserve the value at the API boundary because subsequent cleanup or logging calls can overwrite the last-error state.

Operational meaning

The key question is whether exactly one main-package PRI supplies identity, schema, and default resource maps. The value describes a PRI merge set with no main package; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Resource-only inputs cannot establish the canonical package context. Record the scope that was actually tested instead of escalating from one rejected object or phase to a system-wide outage.

Where the result appears

• This result can appear while processing a PRI merge set with no main package.
• This result can appear while merging resources.pri files for an app package, resource package, or deployment image.
• This result can appear while MakePri merge or build automation that combines package resource indexes.
• It can appear while validation of package family, main-package, bundle, schema, and canonical output constraints.

Typical causes

• only resource-package PRI files were selected.
• the main build artifact was omitted.
• artifact filtering excluded the neutral package.
• the main PRI failed earlier generation.

Diagnostic sequence

1. capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
2. identify the exact target involved in a PRI merge set with no main package, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: exactly one main-package PRI supplies identity, schema, and default resource maps.
4. collect input package roles and expected main package path before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate build manifest and generation logs with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic.
6. determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
7. after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

• collect input package roles.
• collect expected path.
• collect build manifest and generation logs.
• collect schema presence.
• collect artifact filter result.

Correlate this evidence with MakePri command line, input PRI inventory, package identities, schemas, file hashes, output path, tool version, and the first detailed merge diagnostic. Preserve raw identifiers and the first detailed diagnostic: translating everything to 15156 can hide whether the cause was validation, topology, authorization, replication, policy, file I/O, packaging, or an intentional continuation state.

Recovery and retry

The recovery objective for this Win32 error is to generate or include the authoritative main-package PRI before adding resource packages.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for this Win32 error can usually be repeated with bounded backoff; directory mutations, DNS updates, policy installation, servicing actions, and PRI writes require a state check first. Backoff for this Win32 error cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record pri_merge_main_package_required_operation — producing API, command, callback, or servicing phase.
• record pri_merge_main_package_required_target — stable object, zone, policy, package, file, or account identity.
• record pri_merge_main_package_required_state_before and pri_merge_main_package_required_requested_state.
• record pri_merge_main_package_required_first_status — earliest component-specific code before translation.
• record pri_merge_main_package_required_server, pri_merge_main_package_required_process, UTC timestamp, and correlation ID.

A support bundle for this Win32 error should include decimal 15156, hexadecimal 0x00003B34, the smallest reproducible request, target identity, effective configuration, and evidence from the owning Windows component. When documenting it, remove secrets from exported logs but keep SIDs, GUIDs, package-family names, record types, and hashes when they are needed to distinguish objects.

Difference from nearby results

ERROR_PRI_MERGE_RESOURCE_PACKAGE_REQUIRED means the main exists but no resource package is present; this code lacks the main package This distinction determines whether the correct next step is input correction, topology repair, continuation, policy review, package rebuild, or no error handling at all.

Practical validation scenario

A localization pipeline collects only language packages. Adding the neutral main package gives merge the schema and identity it needs. A negative test should reproduce it with the responsible condition preserved; the recovery test should alter only that condition and confirm the intended final state.

Developer and administrator guidance

Developers should model it explicitly in the result domain instead of collapsing every nonzero value into “failed.” Administrators should capture evidence before destructive remediation and use the component that owns a PRI merge set with no main package. Monitoring for this Win32 error should suppress range markers and classify warning, informational, cancellation, and continuation values separately from terminal failures.

References

• Microsoft: exact Win32 system error range — official context relevant to it.
• Microsoft: MakePri.exe command options — official context relevant to it.
• Microsoft: Package Resource Index files — official context relevant to it.

---

Looking for a different code? Search another status or error code.