| Previous | Next |
| SL_REMAPPING_SP_PUB_KM_CACHE_TAMPER_RESTORE_FAILED | SL_REMAPPING_SP_PUB_PROXY_SOFT_TAMPER |
SL_REMAPPING_SP_STATUS_PUSHKEY_CONFLICT
What this Software Protection result isolates
Keep the symbolic result SL_REMAPPING_SP_STATUS_PUSHKEY_CONFLICT together with HRESULT 0xC004D701. The producer is the Software Protection security-processor API; at the stateful API layer that initializes a protected environment, validates handles and versions, commits changes, enumerates data and enforces trusted-time or debugger restrictions, Windows determined that an external decryption key is already associated with the requested protected feature.
This distinction matters because the conflict indicates pre-existing key state rather than an invalid key length or missing key. A later “not licensed” state should not replace the first exact HRESULT in logs.
The diagnostic record that matters
- environment or handle lifetime
- buffer length and returned required size
- trusted time and system UTC time
- Security-SPP event sequence and caller process
- operation and API version
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, record feature identifier, key-generation metadata, provisioning source and the first successful key-set event without exporting the key.
Handle creation, mutation, commit and enumeration are separate stages, so the first failing call is more useful than a later activation summary.
Related codes with different remedies
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_STATUS_NO_MORE_DATA | Compared with this result, an enumeration cursor has reached the end of the available protected objects. |
SL_REMAPPING_SP_STATUS_INVALID_SPAPI_VERSION | Compared with this result, the caller and security processor disagree about the public API structure or protocol version. |
SL_REMAPPING_SP_STATUS_INVALID_SPAPI_CALL | Compared with this result, the requested security-processor operation is not valid for the current object type or state. |
Investigation sequence
- Record it,
0xC004D701, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record feature identifier, key-generation metadata, provisioning source and the first successful key-set event without exporting the key.
- Compare the neighboring results below and identify which condition actually applies.
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.
What to repair—and what not to reset
Use the existing authorized key association or perform the documented rotation/reset workflow for that feature.
Representative case: Two provisioning agents attempt to push different external keys for the same feature.
Technical references
- Software Licensing provider — reference for evidence collection and post-repair verification.
- SoftwareLicensingService WMI class — technical contract for the subsystem producing it.
- SoftwareLicensingProduct WMI class — official platform context used to interpret it.
- Windows SDK constants — supported state, API or recovery information relevant to this HRESULT.
Looking for a different code? Search another status or error code.