What does Windows error code 14108 (ERROR_SMI_PRIMITIVE_INSTALLER_FAILED) mean?

Previous	Next
ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE	ERROR_GENERIC_COMMAND_FAILED

ERROR_SMI_PRIMITIVE_INSTALLER_FAILED

The SMI primitive installer failed during setup or servicing.

ERROR_SMI_PRIMITIVE_INSTALLER_FAILED is Windows status 14108 (0x0000371C) associated with a primitive installer operation in the servicing management infrastructure. 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 the primitive operation completes its narrowly defined file, registry, service, or component action. The value describes a primitive installer operation in the servicing management infrastructure; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Manual recreation of the primitive side effect can leave the servicing database inconsistent with the machine. 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 primitive installer operation in the servicing management infrastructure.
• This result can appear while component installation, package servicing, manifest processing, or resource substitution.
• This result can appear while a setup engine invoking an advanced, primitive, or generic installer step.
• It can appear while XML or localized-content parsing before a component can be committed.

Typical causes

• the primitive receives invalid package data.
• the target resource is locked or unavailable.
• the operation violates servicing state.
• the underlying file, registry, or service call fails.

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 primitive installer operation in the servicing management infrastructure, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
3. prove the state boundary: the primitive operation completes its narrowly defined file, registry, service, or component action.
4. collect primitive installer type and target resource before restarting services, deleting objects, rebuilding packages, or changing policy.
5. correlate first lower-level Win32 or HRESULT with CBS.log, setup logs, servicing stack events, installer stdout/stderr, manifest identity, XML bytes, and the first HRESULT or process exit code.
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 primitive installer type.
• collect target resource.
• collect first lower-level Win32 or HRESULT.
• collect CBS and setup log section.
• collect transaction rollback state.

Preserve raw identifiers and the first detailed diagnostic: translating everything to 14108 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 it is to repair the underlying target or package data and rerun through servicing so transaction ownership is preserved.

Retry only after the recorded boundary changes and prior completion is known. Read-only discovery for it 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 it cannot repair malformed input, unsupported structure, identity collision, missing authority, or incompatible package metadata.

Telemetry and support fields

• record smi_primitive_installer_failed_operation — producing API, command, callback, or servicing phase.
• record smi_primitive_installer_failed_target — stable object, zone, policy, package, file, or account identity.
• record smi_primitive_installer_failed_state_before and smi_primitive_installer_failed_requested_state.
• record smi_primitive_installer_failed_first_status — earliest component-specific code before translation.
• record smi_primitive_installer_failed_server, smi_primitive_installer_failed_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 14108, hexadecimal 0x0000371C, 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_ADVANCED_INSTALLER_FAILED reports an advanced installer; this code names the lower-level primitive installer 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 primitive registry operation fails on a protected key during package apply. CBS logs identify the exact target and access status for correction. 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 primitive installer operation in the servicing management infrastructure. Monitoring for it 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: Assembly manifests — official context relevant to it.
• Microsoft: Side-by-side assemblies — official context relevant to it.

---

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