| Previous | Next |
| SL_REMAPPING_SP_PUB_CRYPTO_KEY_NOT_FOUND | SL_REMAPPING_SP_PUB_CRYPTO_INVALID_SIGNATURELENGTH |
SL_REMAPPING_SP_PUB_CRYPTO_NOT_BLOCK_ALIGNED
Why this is more specific than an activation failure
Keep the symbolic result SL_REMAPPING_SP_PUB_CRYPTO_NOT_BLOCK_ALIGNED together with HRESULT 0xC004D20C. 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 input length is not a whole multiple of the cipher block size for a mode that requires aligned data.
For triage, this belongs to the cryptographic processing inside the security processor. Alignment concerns payload length; INVALID_BLOCKLENGTH concerns configured algorithm block size. Product-key changes or network tests are useful only when the evidence points back to those layers.
Minimum data for a reliable diagnosis
- hash state and digest length
- signature format, length and verification key
- provider and algorithm identifiers
- key type and key-material length
- cipher mode, block size and padding mode
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, capture input length, provider-reported block size, chaining mode and padding setting.
Cryptographic material should be logged by identifier, length, hash or thumbprint rather than by exporting secret keys or plaintext protected data.
A reproducible troubleshooting path
- Use read-only inspection first: capture input length, provider-reported block size, chaining mode and padding setting.
Recovery while preserving licensing evidence
Supply correctly sized data or use the documented padding/streaming mode appropriate to the format.
Representative case: CBC decryption is attempted on a truncated ciphertext without a complete final block.
Related codes with different remedies
| Result | Different condition |
|---|---|
SL_REMAPPING_SP_PUB_CRYPTO_INVALID_SIGNATURELENGTH | Compared with this result, the signature byte count does not match the selected key and signature encoding. |
SL_REMAPPING_SP_PUB_CRYPTO_KEY_NOT_FOUND | Compared with this result, the selected provider has no key object for the requested identifier. |
SL_REMAPPING_SP_PUB_CRYPTO_INVALID_SIGNATURE | Compared with it, signature verification completed and the signature does not authenticate the supplied hash with the selected key. |
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.