TPM_E_PCP_INTERNAL_ERROR when validating a bad signature RRS feed

  • Question

  • I am calling NCryptValidateSignature using a valid signature: Everything is fine.

    I call the same function with the same parameters on a bad signature, expecting to get NTE_BAD_SIGNATURE. Instead I get a TPM_E_PCP_INTERNAL_ERROR. Is this a known problem or should I provide 

    The TPM driver used is the standard TPM 2.0 from Microsoft (loaded via System32/DRIVERS/tpm.sys)

    My sourcecode is C++. I can provide source if interested.

    Monday, June 15, 2020 9:39 AM

All replies

  • Hi,

    Thanks for posting here.

    Sorry, I cannot find any document for the "NCryptValidateSignature" maybe you mean NCryptVerifySignature.

    I will be very grateful If you can provide a reproducible minimal sample. Or you could try this sample:

    Signing Data with CNG

    and replace the BCryptVerifySignature with NCryptVerifySignature and some other corresponding modifications

    Best Regards,


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Tuesday, June 16, 2020 4:02 AM