| Previous | Next |
| SL_REMAPPING_SP_PUB_TIMER_ALREADY_EXISTS | SL_REMAPPING_SP_PUB_TIMER_EXPIRED |
SL_REMAPPING_SP_PUB_TIMER_NOT_FOUND
Why this is more specific than an activation failure
The useful meaning of SL_REMAPPING_SP_PUB_TIMER_NOT_FOUND, value 0xC004D30B, 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 named secure timer is absent from the selected namespace.
This result already rules out several broad guesses: absence differs from a timer that exists and has expired. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
A reproducible troubleshooting path
- Identify the caller and operation instance that produced
0xC004D30B. - Collect the code-specific evidence: record timer name, namespace, expected creation event and store recreation history.
Inputs that distinguish this condition
- 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, record timer name, namespace, expected creation event and store recreation history.
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_TIMER_ALREADY_EXISTS | Compared with this result, creation was requested for a secure timer whose name already exists in the namespace. |
SL_REMAPPING_SP_PUB_TIMER_EXPIRED | Compared with this result, trusted time has passed the secure timer’s protected deadline. |
SL_REMAPPING_SP_PUB_TIMER_NAME_SIZE_TOO_BIG | Compared with this result, the secure-timer name exceeds the supported encoded length. |
Targeted fix
Recreate the timer only through the owning licensing workflow or restore the authoritative state.
Representative case: Store recreation removes a timer that a later policy evaluation expects.
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.