| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_READ_ONLY | SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED |
SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND
What the security processor has established
0xC004D313 maps to SL_REMAPPING_SP_PUB_TS_ATTRIBUTE_NOT_FOUND. This result belongs to the trusted store and secure-timer layer and narrows the operation to the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs. In concrete terms, the requested attribute is not present on the selected trusted-store entry.
This distinction matters because the entry exists; the missing object is one attribute, not the whole entry. A later “not licensed” state should not replace the first exact HRESULT in logs.
What to capture before recovery
- 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
- requested and actual data size
Testing the failing stage
- Identify the caller and operation instance that produced
0xC004D313. - Collect the code-specific evidence: record namespace, entry key, attribute ID, object version and expected producer.
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 namespace, entry key, attribute ID, object version and expected producer.
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.
Why the symbolic code matters
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED | Compared with this result, the caller is not authorized for the requested trusted-store namespace or operation. |
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_TIMER_READ_ONLY | Compared with it, the requested update targets a secure timer whose deadline or attributes are immutable. |
Safe recovery direction
Handle the attribute as optional when the schema allows or regenerate it through the owning component.
Representative case: A newer policy reader expects metadata not written by an older object 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.
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.