| Previous | Next |
| SL_REMAPPING_SP_PUB_TIMER_READ_ONLY | SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND |
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_READ_ONLY
Why this is more specific than an activation failure
Keep the symbolic result SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_READ_ONLY together with HRESULT 0xC004D312. The producer is the trusted store and secure-timer layer; at the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs, Windows determined that an update targets a protected entry attribute marked read-only.
the first result diagnostic fork is precise: the entry itself can be mutable while this particular attribute is not. That is why this result can require a different correction from the same visible activation banner.
State to compare on both sides of the failure
- 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
- entry/timer flags including read-only state
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 namespace, entry, attribute ID, flags and attempted value change.
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.
Testing the failing stage
- Record this result,
0xC004D312, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: capture namespace, entry, attribute ID, flags and attempted value change.
- Compare the neighboring results below and identify which condition actually applies.
Safe recovery direction
Modify the object only through the supported operation that owns that attribute.
Representative case: A generic editor tries to change an integrity attribute maintained by the security processor.
Similar symptoms, different conditions
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TIMER_READ_ONLY | Compared with this result, the requested update targets a secure timer whose deadline or attributes are immutable. |
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND | Compared with this result, the requested attribute is not present on the selected trusted-store entry. |
SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED | Compared with it, the caller is not authorized for the requested trusted-store namespace or operation. |
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 — supported state, API or recovery information relevant to this HRESULT.
- SoftwareLicensingService WMI class — reference for evidence collection and post-repair verification.
- Slmgr.vbs options — technical contract for the subsystem producing it.
- Rebuild the Tokens.dat file — official platform context used to interpret it.
Looking for a different code? Search another status or error code.