What does Windows error code 14096 (ERROR_UNMAPPED_SUBSTITUTION_STRING) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: A substitution string had no mapping.

Previous	Next
ERROR_SXS_INCORRECT_PUBLIC_KEY_TOKEN	ERROR_SXS_ASSEMBLY_NOT_LOCKED

ERROR_UNMAPPED_SUBSTITUTION_STRING

A substitution string had no mapping.

ERROR_UNMAPPED_SUBSTITUTION_STRING is Windows status 14096 (0x00003710) associated with resolution of a syntactically valid substitution token without a mapping. 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 substitution table defines a value for every token used by the localized resource. The value describes resolution of a syntactically valid substitution token without a mapping; it does not prove that the whole domain, DNS service, network, servicing stack, application package, or operating system has failed.

Likely impact: Leaving a token unresolved can expose placeholders to users or break servicing decisions that depend on the text. 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 resolution of a syntactically valid substitution token without a mapping.
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 mapping entry is absent.
token spelling or case differs.
the wrong localization scope is loaded.
package generation omitted a variable.

Diagnostic sequence

capture it immediately after the failing or status-returning call and record whether the API uses Win32, DNS_STATUS, HRESULT conversion, or callback semantics.
identify the exact target involved in resolution of a syntactically valid substitution token without a mapping, including stable GUIDs, DNs, zone names, package identities, file hashes, policy names, or process identifiers as applicable.
prove the state boundary: the substitution table defines a value for every token used by the localized resource.
collect token name and source string and available substitution map before restarting services, deleting objects, rebuilding packages, or changing policy.
correlate locale and resource scope with CBS.log, setup logs, servicing stack events, installer stdout/stderr, manifest identity, XML bytes, and the first HRESULT or process exit code.
determine whether the result is a failure, warning, informational completion, continuation request, or marker constant before choosing retry behavior.
after changing one responsible condition, repeat the same smallest operation and verify both success and absence of unintended partial effects.

Evidence to preserve

collect token name and source string.
collect available substitution map.
collect locale and resource scope.
collect package or manifest identity.
collect build step that generated mappings.

Preserve raw identifiers and the first detailed diagnostic: translating everything to 14096 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 add the authoritative mapping or correct the token name and rebuild the resource package.

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 unmapped_substitution_string_operation — producing API, command, callback, or servicing phase.
record unmapped_substitution_string_target — stable object, zone, policy, package, file, or account identity.
record unmapped_substitution_string_state_before and unmapped_substitution_string_requested_state.
record unmapped_substitution_string_first_status — earliest component-specific code before translation.
record unmapped_substitution_string_server, unmapped_substitution_string_process, UTC timestamp, and correlation ID.

A support bundle for it should include decimal 14096, hexadecimal 0x00003710, 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_MALFORMED_SUBSTITUTION_STRING fails syntax; this code parses the token but cannot resolve it 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 manifest references $(PublisherDisplayName) but the package mapping omits it. Restoring the generated mapping resolves the resource. 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 resolution of a syntactically valid substitution token without a mapping. 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.