| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_ENTRY_READ_ONLY | SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_READ_ONLY |
SL_REMAPPING_SP_PUB_TIMER_READ_ONLY
What the protected licensing code means
The useful meaning of SL_REMAPPING_SP_PUB_TIMER_READ_ONLY, value 0xC004D311, 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 requested update targets a secure timer whose deadline or attributes are immutable.
the first result diagnostic fork is precise: read-only status differs from expiration or absence. That is why this result can require a different correction from the same visible activation banner.
What to capture before recovery
- namespace, entry key and attribute name
- 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
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 timer flags, current deadline, requested change and owning policy.
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_ATTRIBUTE_READ_ONLY | Compared with this result, an update targets a protected entry attribute marked read-only. |
SL_REMAPPING_SP_PUB_TS_ENTRY_READ_ONLY | Compared with this result, the requested mutation targets a trusted-store entry marked read-only. |
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND | Compared with this result, the requested attribute is not present on the selected trusted-store entry. |
A reproducible troubleshooting path
- Record it,
0xC004D311, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record timer flags, current deadline, requested change and owning policy.
- Compare the neighboring results below and identify which condition actually applies.
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.
What to repair—and what not to reset
Let the owning licensing policy replace or renew the timer through its documented workflow.
Representative case: A caller attempts to extend an immutable evaluation timer directly.
Technical references
- SoftwareLicensingProduct WMI class — reference for evidence collection and post-repair verification.
- SoftwareLicensingService WMI class — technical contract for the subsystem producing it.
- Slmgr.vbs options — official platform context used to interpret it.
- Rebuild the Tokens.dat file — supported state, API or recovery information relevant to this HRESULT.
Looking for a different code? Search another status or error code.