| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_TAMPERED_DATA_BREADCRUMB_MISMATCH | SL_REMAPPING_SP_PUB_TAMPER_MODULE_AUTHENTICATION |
SL_REMAPPING_SP_PUB_TS_TAMPERED_DATA_VERSION_MISMATCH
What the protected licensing code means
The useful meaning of SL_REMAPPING_SP_PUB_TS_TAMPERED_DATA_VERSION_MISMATCH, value 0xC004D31C, is not simply “activation failed.” It comes from the trusted store and secure-timer layer, where the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs. The condition to investigate is trusted-store protected data uses a version incompatible with the integrity metadata or current processor.
the first result diagnostic fork is precise: this is version compatibility, not merely different generation numbers. That is why this result can require a different correction from the same visible activation banner.
Testing the failing stage
- Use read-only inspection first: capture data version, breadcrumb/version fields, OS build and upgrade/rollback sequence.
What to capture before recovery
- entry/timer flags including read-only state
- requested and actual data size
- trusted time, timer deadline and hardware-binding state
- tamper/recreation/rearm events in chronological order
- namespace, entry key and attribute name
Where it sits in the licensing pipeline
Trusted-store results concern protected persistent state; deleting the store can erase the evidence that distinguishes missing data, capacity, access, binding and integrity failures. To verify this, capture data version, breadcrumb/version fields, OS build and upgrade/rollback sequence.
A positive trusted-time or rearm/recreation result must be interpreted by HRESULT severity and the subsequent license state, not by treating every nonzero value as a fatal error.
Comparison with neighboring results
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_TAMPERED_DATA_BREADCRUMB_MISMATCH | Compared with this result, trusted-store data and the associated integrity breadcrumb do not authenticate the same state. |
SL_REMAPPING_SP_PUB_TS_TAMPERED_NO_DATA | Compared with this result, required protected trusted-store data is absent when integrity validation expects it. |
SL_REMAPPING_SP_PUB_TS_TAMPERED_INVALID_DATA | Compared with it, trusted-store data fails internal semantic or integrity validation. |
Targeted fix
Restore components and protected state from the same supported platform version or rebuild through documented recovery.
Representative case: An OS rollback leaves protected data written by a newer security-processor version.
Actions that usually destroy useful evidence
- Do not use rearm as a generic repair for unrelated activation or integrity errors.
- Do not manually delete protected store files before collecting state and event evidence.
Version skew usually points to servicing or rollback
Here the decisive comparison is between the protected-data schema, integrity metadata version, running security-processor build and current OS servicing level. A matching generation is not enough when one component interprets the bytes using a different version contract.
Review pending reboot state, failed cumulative updates, offline servicing, in-place upgrade history and VM rollback. Restore all licensing components from the same supported build using Windows servicing; do not copy a newer store into an older installation or downgrade individual policy and service binaries.
| Pattern | Likely boundary |
|---|---|
| New data, old service | An update wrote protected state but the running component did not complete replacement/reboot. |
| Old data, new service | Rollback or partial restore retained a store from an earlier schema. |
| Mixed policy files | Component-store repair is required before licensing-state recovery. |
Technical references
- SoftwareLicensingProduct WMI class — technical contract for the subsystem producing it.
- SoftwareLicensingService WMI class — official platform context used to interpret it.
- Slmgr.vbs options — supported state, API or recovery information relevant to this HRESULT.
- Rebuild the Tokens.dat file — reference for evidence collection and post-repair verification.
Looking for a different code? Search another status or error code.