What does Windows error code 15155 (ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED) mean?

Previous	Next
ERROR_PRI_MERGE_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED	ERROR_PRI_MERGE_MAIN_PACKAGE_REQUIRED

ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED

Packages for a PRI file merge must not include bundle packages.

A wrapper may expose ERROR_PRI_MERGE_BUNDLE_PACKAGES_NOT_ALLOWED through PowerShell, RPC, REST, JSON, or an installer log, but the actionable evidence remains in the original Windows component. Keep decimal 15155, hexadecimal 0x00003B33, and the producing function together.

Operational meaning

The key question is whether the merge set contains the main package and resource packages rather than bundle-level package artifacts. The value describes a PRI merge input that represents an app bundle package; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Bundle metadata is not a substitute for the package-level resource schema expected by merge. 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 input that represents an app bundle 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

• a bundle PRI was supplied directly.
• the pipeline confuses bundle and package manifests.
• artifact discovery operates at the wrong directory level.
• a deployment bundle is reused as a merge input.

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 input that represents an app bundle package, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the merge set contains the main package and resource packages rather than bundle-level package artifacts.
4. collect package type of each input and bundle and package manifest paths before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate artifact-selection logic 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 package type of each input.
• collect bundle and package manifest paths.
• collect artifact-selection logic.
• collect MakePri command.
• collect intended deployment layout.

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 15155 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 extract or select the eligible constituent main and resource package PRI files instead of the bundle package.

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_bundle_packages_not_allowed_operation — producing API, command, callback, or servicing phase.
• record pri_merge_bundle_packages_not_allowed_target — stable object, zone, policy, package, file, or account identity.
• record pri_merge_bundle_packages_not_allowed_state_before and pri_merge_bundle_packages_not_allowed_requested_state.
• record pri_merge_bundle_packages_not_allowed_first_status — earliest component-specific code before translation.
• record pri_merge_bundle_packages_not_allowed_server, pri_merge_bundle_packages_not_allowed_process, UTC timestamp, and correlation ID.

A support bundle for this Win32 error should include decimal 15155, hexadecimal 0x00003B33, 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_MULTIPLE_MAIN_PACKAGES_NOT_ALLOWED concerns count; this code rejects the bundle package type itself 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 packaging job points MakePri at the bundle output directory. Selecting the constituent package resources removes the unsupported bundle input. 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 input that represents an app bundle 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.