| Previous | Next |
| XACT_E_REPLAYREQUEST | SL_REMAPPING_SP_STATUS_DEBUGGER_DETECTED |
SL_REMAPPING_SP_STATUS_SYSTEM_TIME_SKEWED
What the security processor has established
0x8004D102 maps to SL_REMAPPING_SP_STATUS_SYSTEM_TIME_SKEWED. This result belongs to the Software Protection security-processor API and narrows the operation to the stateful API layer that initializes a protected environment, validates handles and versions, commits changes, enumerates data and enforces trusted-time or debugger restrictions. In concrete terms, the security processor’s trusted time and the machine time are outside the accepted relationship.
This distinction matters because this is a trusted-time consistency check, not ordinary KMS clock-skew alone. A later “not licensed” state should not replace the first exact HRESULT in logs.
Where it sits in the licensing pipeline
These results describe the protected API contract; they are not automatically evidence that the installed product key is invalid. To verify this, compare UTC system time, TrustedTime, time-service source, recent clock jumps, firmware time and suspend/restore events.
Minimum data for a reliable diagnosis
- operation and API version
- environment or handle lifetime
- buffer length and returned required size
- trusted time and system UTC time
- Security-SPP event sequence and caller process
Testing the failing stage
- Use read-only inspection first: compare UTC system time, TrustedTime, time-service source, recent clock jumps, firmware time and suspend/restore events.
Similar symptoms, different conditions
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_STATUS_DEBUGGER_DETECTED | Compared with this result, the protected security-processor operation detected a debugger or equivalent instrumentation and refused to run. |
SL_REMAPPING_SP_PUB_API_HANDLE_NOT_COMMITED | Compared with it, a protected handle was consumed before its staged changes were finalized with the required commit operation. |
SL_REMAPPING_SP_PUB_GENERAL_NOT_INITIALIZED | Compared with it, the security-processor environment was used before initialization completed successfully. |
Safe recovery direction
Correct the authoritative time source and clock state, then refresh license status without manually altering trusted-store timestamps.
Representative case: A VM snapshot restores an older system clock while protected trusted time has already advanced.
Actions that usually destroy useful evidence
- Do not retry the whole activation workflow without preserving the first API result.
- Do not attach debuggers or instrumentation to a protected production path while reproducing the issue.
Technical references
- Software Licensing provider — official platform context used to interpret it.
- SoftwareLicensingService WMI class — supported state, API or recovery information relevant to this HRESULT.
- SoftwareLicensingProduct WMI class — reference for evidence collection and post-repair verification.
- Windows SDK constants — technical contract for the subsystem producing it.
Looking for a different code? Search another status or error code.