| Previous | Next |
| STATUS_PCP_NOT_SUPPORTED | STATUS_PCP_INTERNAL_ERROR |
STATUS_PCP_BUFFER_TOO_SMALL
Platform Crypto Provider buffer is too small
STATUS_PCP_BUFFER_TOO_SMALL is the TPM-backed provider version of a common NCrypt sizing failure. Many NCrypt queries and operations use a two-step pattern: first ask for the required size, then allocate a buffer of that size and repeat the call.
The status is not evidence that the TPM key is bad. It indicates that the caller did not provide enough space for a provider object, property, blob, signature, attestation result, or other output data.
Diagnostic focus
- Use the returned required-size value when the API provides one, then repeat with a correctly sized buffer.
- Keep byte counts separate from character counts for string properties.
- Check structure version and length fields; a correct raw buffer can still fail if embedded sizes are inconsistent.
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.