| Previous | Next |
| STATUS_PCP_TPM_VERSION_NOT_SUPPORTED | STATUS_PCP_IFX_RSA_KEY_CREATION_BLOCKED |
STATUS_PCP_BUFFER_LENGTH_MISMATCH
Platform Crypto Provider buffer-length mismatch
STATUS_PCP_BUFFER_LENGTH_MISMATCH is different from a buffer that is simply too small. It means the Platform Crypto Provider saw length fields or paired buffers that do not agree with the operation being requested.
This can happen with property blobs, attestation structures, key blobs, or provider-specific input data where an outer buffer length, inner structure size, and expected TPM command payload length must match. A larger buffer does not fix inconsistent embedded lengths.
Diagnostic focus
- Check both the API buffer length and any length fields inside the structure being passed.
- Verify structure version and packing when data crosses process, architecture, or language boundaries.
- Regenerate provider blobs from API output instead of editing serialized data manually.
References
- Microsoft: CNG key storage providers
- Microsoft: NCryptOpenStorageProvider
- Microsoft: Key storage and retrieval
- Microsoft: TPM Base Services
- Microsoft: COM error codes for TPM, PLA and FVE
Looking for a different code? Search another status or error code.