| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_REARMED | SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_NOT_FOUND |
SL_REMAPPING_SP_PUB_TS_RECREATED
What the protected licensing code means
The useful meaning of SL_REMAPPING_SP_PUB_TS_RECREATED, value 0xC004D303, 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 trusted store was recreated rather than opened in its previous generation.
For triage, this belongs to the trusted store and secure-timer layer. Recreation can be successful while licenses still need reinstallation or reevaluation. Product-key changes or network tests are useful only when the evidence points back to those layers.
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 why recreation was initiated, old/new generation identifiers, restored licenses and resulting product inventory.
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.
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
A reproducible troubleshooting path
- Use read-only inspection first: record why recreation was initiated, old/new generation identifiers, restored licenses and resulting product inventory.
Why the symbolic code matters
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_NOT_FOUND | Compared with this result, the requested entry key is absent from the selected trusted-store namespace. |
SL_REMAPPING_SP_PUB_TS_REARMED | Compared with this result, the trusted store has completed a supported rearm transition and licensing timers/state were reset according to policy. |
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_ALREADY_EXISTS | Compared with it, creation conflicts with an existing entry key in the same trusted-store namespace. |
Recommended handling
Reload authoritative license files and verify every affected Activation ID after recreation.
Representative case: The supported Tokens.dat rebuild sequence creates a new store from installed licensing data.
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.