| Previous | Next |
| SL_REMAPPING_SP_PUB_TS_TAMPERED | SL_REMAPPING_SP_PUB_TS_RECREATED |
SL_REMAPPING_SP_PUB_TS_REARMED
What the protected licensing code means
SL_REMAPPING_SP_PUB_TS_REARMED (0xC004D302) 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: the trusted store has completed a supported rearm transition and licensing timers/state were reset according to policy.
the first result diagnostic fork is precise: this is a state transition result, not evidence that activation itself succeeded. That is why this result can require a different correction from the same visible activation banner.
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 rearm count before/after, command source, timestamp, reboot requirement and post-reboot state.
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.
Investigation sequence
- Use read-only inspection first: record rearm count before/after, command source, timestamp, reboot requirement and post-reboot state.
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
Comparison with neighboring results
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_TS_RECREATED | Compared with this result, the trusted store was recreated rather than opened in its previous generation. |
SL_REMAPPING_SP_PUB_TS_TAMPERED | Compared with this result, the trusted store failed an integrity check and its protected state cannot be accepted as authentic. |
SL_REMAPPING_SP_PUB_TS_ENTRY_KEY_NOT_FOUND | Compared with it, the requested entry key is absent from the selected trusted-store namespace. |
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
Complete any required reboot and verify the intended product’s grace and activation state.
Representative case: Image preparation performs an authorized rearm before capture.
Rearm is an image-lifecycle event
A rearm changes protected grace and image-deployment state; it is not a substitute for activation and does not prove that a retail, MAK, KMS or subscription entitlement is valid. Capture RemainingWindowsReArmCount before and after the operation and associate the event with the deployment task that requested it.
In managed imaging, the useful verification point is after the required reboot and before capture: confirm that the reference image is in the intended generalized state, that no production machine is repeatedly consuming rearm count, and that later activation uses the correct channel. A successful rearm followed by an unlicensed product is not contradictory.
| Check | Expected interpretation |
|---|---|
| Counter decreases | The protected rearm allowance was consumed by an authorized state transition. |
| Reboot pending | Do not judge the final grace state until the platform completes the transition. |
| Activation still required | Rearm and entitlement are separate; activate through the legitimate product channel. |
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.