NCryptOpenKey returning x80090016 and 0x80280185 [Note change in function]

Wise42 1

I'm getting the errors x80090016 and 0x80280185 from NCryptOpenKey occasionally. What are all the possible reasons for these errors.

2 answers

Strive Sun-MSFT 426 Reputation points

2021-03-05T03:15:50.393+00:00

Hello, @Wise42

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.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
Wise42 1 Reputation point

2021-03-05T14:03:25.967+00:00

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.
Please sign in to rate this answer.
Strive Sun-MSFT 426 Reputation points

2021-03-08T07:51:13.387+00:00

I have not used TPM. You can check what caused the error.

Wise42 1 Reputation point

2021-03-09T13:28:21.74+00:00

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?

Strive Sun-MSFT 426 Reputation points

2021-03-10T08:34:45.057+00:00

I will contact the relevant engineer to help you solve the problem, please be patient.

Wise42 1 Reputation point

2021-03-18T14:14:33.013+00:00

Any status?

Strive Sun-MSFT 426 Reputation points

2021-03-19T03:07:50.49+00:00

Thanks for your patience.

The error code 0x80090016 (NTE_BAD_KEYSET) is only returned if the key is not found in persisted storage. Running a process monitor trace for the operation should show if the operation is successful or not with showing locations being checked.

For the other error code, it is an independent vendor specific error code. The error code in question (0x80280185) is in the TPM 2.0 error code area but not an error code that the OS itself returns.

Here is the TPM error codes that we have listed and can return from OS layer at least:

COM Error Codes (TPM, PLA, FVE)

Wise42 1 Reputation point

2021-03-19T14:00:04.657+00:00

Thanks, this is what I was looking for.
I noticed in the link you provided there are several TPM-specific error codes. I'm looking to make use of the TPM. What functions (e.g., ncrypt, bcrypt) would call these TPM functions?

Strive Sun-MSFT 426 Reputation points

2021-03-23T01:29:12.433+00:00

For the follow-up on API involving TPM, it is best to show this via an open source project via Microsoft research.

https://github.com/microsoft/TSS.MSR/tree/master/TSS.NET/TSS.Net

This could answer the questions on what API's and overall design for TPM interaction with samples. Support is provided via the GitHub on this rather complex topic too if you do hit an issue.
Sign in to comment