| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_DATA_SIZE_TOO_BIG | SL_REMAPPING_SP_PUB_TIMER_ALREADY_EXISTS |
SL_REMAPPING_SP_PUB_TS_INVALID_HW_BINDING
What the protected licensing code means
The useful meaning of SL_REMAPPING_SP_PUB_TS_INVALID_HW_BINDING, value 0xC004D309, 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 the trusted-store state no longer matches the machine hardware identity within allowed tolerance.
This result already rules out several broad guesses: hardware binding differs from trusted-time skew and from a bad product key. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
From HRESULT to a verified cause
- Record this result,
0xC004D309, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record hardware and firmware changes, VM clone/restore history, HWID-related events and last successful evaluation.
- Compare the neighboring results below and identify which condition actually applies.
Minimum data for a reliable diagnosis
- 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, record hardware and firmware changes, VM clone/restore history, HWID-related events and last successful evaluation.
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.
Related codes with different remedies
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TIMER_ALREADY_EXISTS | Compared with this result, creation was requested for a secure timer whose name already exists in the namespace. |
SL_REMAPPING_SP_PUB_TS_DATA_SIZE_TOO_BIG | Compared with this result, the value being stored exceeds the maximum data size for one trusted-store entry. |
SL_REMAPPING_SP_PUB_TIMER_NOT_FOUND | Compared with it, the named secure timer is absent from the selected namespace. |
Targeted fix
Restore the intended machine identity where appropriate or reactivate through the legitimate channel after the change.
Representative case: A VM is cloned with protected state bound to the source machine’s hardware identity.
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.
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.