| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_NAMESPACE_NOT_FOUND | SL_REMAPPING_SP_PUB_TS_TAMPERED_BREADCRUMB_LOAD_INVALID |
SL_REMAPPING_SP_PUB_TS_NAMESPACE_IN_USE
What the protected licensing code means
SL_REMAPPING_SP_PUB_TS_NAMESPACE_IN_USE (0xC004D316) is emitted by the trusted store and secure-timer layer. It marks a specific point inside the protected state store that keeps namespaced entries, attributes, secure timers, trusted time, hardware binding, rearm state and integrity breadcrumbs: a namespace operation requires exclusive ownership but active handles or transactions still reference it.
This result already rules out several broad guesses: the namespace exists and may be healthy; it is busy rather than inaccessible. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
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 open handles, caller processes, transaction state and requested delete/reset operation.
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.
Inputs that distinguish this condition
- 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
Investigation sequence
- Identify the caller and operation instance that produced
0xC004D316. - Collect the code-specific evidence: capture open handles, caller processes, transaction state and requested delete/reset operation.
Related codes with different remedies
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_NAMESPACE_NOT_FOUND | Compared with this result, the requested trusted-store namespace does not exist. |
SL_REMAPPING_SP_PUB_TS_TAMPERED_BREADCRUMB_LOAD_INVALID | Compared with this result, the integrity breadcrumb loaded for the trusted store is malformed or fails validation. |
SL_REMAPPING_SP_PUB_TS_ACCESS_DENIED | Compared with this result, the caller is not authorized for the requested trusted-store namespace or operation. |
Recommended handling
Close owning contexts or stop the supported service cleanly before retrying the namespace operation.
Representative case: A repair tool attempts to reset a namespace while sppsvc is evaluating licenses from it.
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.