| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_FULL | SL_REMAPPING_SP_PUB_TIMER_READ_ONLY |
SL_REMAPPING_SP_PUB_TS_ENTRY_READ_ONLY
What the protected licensing code means
Keep the symbolic result SL_REMAPPING_SP_PUB_TS_ENTRY_READ_ONLY together with HRESULT 0xC004D310. 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 the requested mutation targets a trusted-store entry marked read-only.
Diagnostic discriminator: Microsoft describes this condition as “Read-only entry cannot be modified.” Use that exact state to separate the value from nearby results in the same subsystem.
This result already rules out several broad guesses: the entry is present and readable; policy forbids modification. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
A reproducible troubleshooting path
- Use read-only inspection first: capture entry key, namespace, flags, operation and creator/ownership information.
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 entry key, namespace, flags, operation and creator/ownership information.
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.
Minimum data for a reliable diagnosis
- 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
Recommended handling
Use the supported owner operation or create a new mutable entry where the schema permits.
Representative case: A maintenance tool tries to overwrite an immutable licensing proof entry.
Why the symbolic code matters
| 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_READ_ONLY | Compared with this result, an update targets a protected entry attribute marked read-only. |
SL_REMAPPING_SP_PUB_TS_FULL | Compared with it, the trusted store has no capacity for the requested additional protected state. |
Actions that usually destroy useful evidence
- Do not manually delete protected store files before collecting state and event evidence.
- Do not use rearm as a generic repair for unrelated activation or integrity errors.
Technical references
- SoftwareLicensingProduct WMI class — official platform context used to interpret it.
- SoftwareLicensingService WMI class — supported state, API or recovery information relevant to this HRESULT.
- Slmgr.vbs options — reference for evidence collection and post-repair verification.
- Rebuild the Tokens.dat file — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.