| Previous | Next |
| SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_PROVIDERID | SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_HASHID |
SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_KEYID
What the protected licensing code means
Keep the symbolic result SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_KEYID together with HRESULT 0xC004D206. The producer is cryptographic processing inside the security processor; at the provider, algorithm, key, hash, signature and block-processing stage used to authenticate protected licensing data, Windows determined that the requested cryptographic key type or key identifier is unknown to the selected provider.
This result already rules out several broad guesses: an unknown key ID differs from a known key that is temporarily unavailable or absent. Preserve its operation name, product instance and timestamp so a later retry does not hide the original failure.
Minimum data for a reliable diagnosis
- key type and key-material length
- cipher mode, block size and padding mode
- hash state and digest length
- signature format, length and verification key
- provider and algorithm identifiers
Where it sits in the licensing pipeline
Algorithm selection, key lookup, block formatting and signature verification are independent boundaries; a failure in one does not prove corruption at the others. To verify this, record provider ID, key ID, object state and whether key creation/import previously succeeded.
Cryptographic material should be logged by identifier, length, hash or thumbprint rather than by exporting secret keys or plaintext protected data.
Investigation sequence
- Record this result,
0xC004D206, the exact API or service operation, and the affected product or protected object. - Prove the specific condition: record provider ID, key ID, object state and whether key creation/import previously succeeded.
- Compare the neighboring results below and identify which condition actually applies.
Recovery while preserving licensing evidence
Request a supported key type and establish it through the documented create/import path.
Representative case: A caller asks the provider for a key role not defined by the current SPAPI version.
Adjacent states in the same subsystem
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_HASHID | Compared with this result, the requested hash algorithm identifier is not recognized by the selected provider. |
SL_REMAPPING_SP_PUB_CRYPTO_UNKNOWN_PROVIDERID | Compared with this result, the cryptographic provider identifier is not registered in the security-processor API. |
SL_REMAPPING_SP_PUB_CRYPTO_INVALID_CIPHERMODE | Compared with it, the requested encrypt/decrypt or chaining-mode configuration is internally contradictory or unsupported. |
Actions that usually destroy useful evidence
- Do not publish keys, decrypted license blobs or complete protected payloads in a support ticket.
- Do not disable signature or padding validation to make the operation continue.
Technical references
- CNG cryptographic primitive functions — supported state, API or recovery information relevant to this HRESULT.
- BCryptHashData — reference for evidence collection and post-repair verification.
- BCryptVerifySignature — technical contract for the subsystem producing it.
- Signing data with CNG — official platform context used to interpret it.
Looking for a different code? Search another status or error code.