I'm getting the errors x80090016 and 0x80280185 from NCryptOpenKey occasionally. What are all the possible reasons for these errors.
I'm getting the errors x80090016 and 0x80280185 from NCryptOpenKey occasionally. What are all the possible reasons for these errors.
Hello, @Wise42-6819
You can refer COM Error Codes(Seurity and Setup)which provides a list of error codes used by COM-based APIs.
NTE_BAD_KEYSET 0x80090016 Keyset does not exist
You can also check the NCryptOpenKey documentation to determine the error message
I did not find the error message about 0x80280185, please help to check the error code.
Thank you!
If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
When using the platform provider (e.g., the TPM) is there a case where an error in the TPM can cause this error to occur? IOW: If there were an error in the TPM would that always return a different error?
I'll double check on the other error code.
This was not a helpful response. My primary question is still: Would an error returned by the TPM ever result in "NTE_BAD_KEYSET 0x80090016 Keyset does not exist" or is there error always the result of the key not being in the key manager?
I will contact the relevant engineer to help you solve the problem, please be patient.
5 people are following this question.
Custom Credential Provider Command Link to to open a browser with URL, does not open browser
CryptUIWizDigitalSign locks a file if it fails
Increasing Private Bytes but constant Virtual Bytes and Working Set. Genuine Memory Leak?
Experience with SSPI & TLS 1.3
AccessCheck() and MoveFileEx() doesn't work with network mapped driver