| Previous | Next |
| STATUS_PCP_TICKET_MISSING | STATUS_RTPM_NO_RESULT |
STATUS_PCP_RAW_POLICY_NOT_SUPPORTED
The key policy is valid TPM policy, but not manageable by PCP
STATUS_PCP_RAW_POLICY_NOT_SUPPORTED identifies a boundary between raw TPM policy and the higher-level authentication behavior implemented by the Platform Crypto Provider. The key carries a raw policy, so the KSP cannot perform the authentication step that the caller expects through the normal PCP interface.
This is not the same as an invalid policy or an absent key. The policy may be meaningful to a TPM-aware implementation, yet intentionally outside the provider's ability to evaluate or satisfy on behalf of a CNG caller.
What to check
- Determine who created the key and whether the intended consumer was PCP/CNG or a lower-level TPM policy implementation.
- Do not overwrite or strip the raw policy merely to make the key accessible; that can change its security semantics.
- Use the product's supported raw-policy flow or provision a separate key designed for PCP-managed authentication when the security architecture permits it.
References
Looking for a different code? Search another status or error code.