| Previous | Next |
| STATUS_PCP_AUTHENTICATION_IGNORED | STATUS_PCP_PROFILE_NOT_FOUND |
STATUS_PCP_POLICY_NOT_FOUND
A policy reference does not resolve in the expected PCP context
STATUS_PCP_POLICY_NOT_FOUND says that the operation refers to a PCP policy that the provider cannot locate. It is not an assertion that every policy on the computer is invalid; the missing reference can be a name, identifier, parent relationship, or expected policy object in the active provider context.
Policy lookup errors are easiest to diagnose when the key lifecycle is reconstructed. A key created or enrolled under one profile, provider scope, or deployment may not have the policy record expected by a later operation in another context.
What to check
- Capture the policy identifier and the key/container identity passed to the failing CNG call.
- Verify that the application opened the intended storage provider and did not mix a software KSP handle with a PCP policy expectation.
- Compare provisioning metadata and deployment history before deleting policies or creating replacements.
References
- Microsoft: PCP and TPM error codes
- Microsoft: CNG Key Storage Providers
- Microsoft: NCryptCreatePersistedKey
Looking for a different code? Search another status or error code.