FACILITY_TPM_SOFTWARE: the Trusted Platform Module applications.
The source of the error code is the Trusted Platform Module applications.[1][2]
0x80290100: The command buffer is not in the correct state.[2]0x80290101: The command buffer does not contain enough data to satisfy the request.[2]0x80290102: The command buffer cannot contain any more data.[2]0x80290103: One or more output parameters was NULL or invalid.[2]0x80290104: One or more input parameters is invalid.[2]0x80290105: Not enough memory was available to satisfy the request.[2]0x80290106: The specified buffer was too small.[2]0x80290107: An internal error was detected.[2]0x80290108: The caller does not have the appropriate rights to perform the requested operation.[2]0x80290109: The specified authorization information was invalid.[2]0x8029010A: The specified context handle was not valid.[2]0x8029010B: An error occurred while communicating with the TBS.[2]0x8029010C: The TPM returned an unexpected result.[2]0x8029010D: The message was too large for the encoding scheme.[2]0x8029010E: The encoding in the blob was not recognized.[2]0x8029010F: The key size is not valid.[2]0x80290110: The encryption operation failed.[2]0x80290111: The key parameters structure was not valid[2]0x80290112: The requested supplied data does not appear to be a valid migration authorization blob.[2]0x80290113: The specified PCR index was invalid[2]0x80290114: The data given does not appear to be a valid delegate blob.[2]0x80290115: One or more of the specified context parameters was not valid.[2]0x80290116: The data given does not appear to be a valid key blob[2]0x80290117: The specified PCR data was invalid.[2]0x80290118: The format of the owner auth data was invalid.[2]0x80290119: The random number generated did not pass FIPS RNG check.[2]0x8029011A: The TCG Event Log does not contain any data.[2]0x8029011B: An entry in the TCG Event Log was invalid.[2]0x8029011C: A TCG Separator was not found.[2]0x8029011D: A digest value in a TCG Log entry did not match hashed data.[2]0x8029011E: The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance.[2]0x80290200: The specified buffer was too small.[2]0x80290201: The context could not be cleaned up.[2]0x80290202: The specified context handle is invalid.[2]0x80290203: An invalid context parameter was specified.[2]0x80290204: An error occurred while communicating with the TPM[2]0x80290205: No entry with the specified key was found.[2]0x80290206: The specified virtual handle matches a virtual handle already in use.[2]0x80290207: The pointer to the returned handle location was NULL or invalid[2]0x80290208: One or more parameters is invalid[2]0x80290209: The RPC subsystem could not be initialized.[2]0x8029020A: The TBS scheduler is not running.[2]0x8029020B: The command was canceled.[2]0x8029020C: There was not enough memory to fulfill the request[2]0x8029020D: The specified list is empty, or the iteration has reached the end of the list.[2]0x8029020E: The specified item was not found in the list.[2]0x8029020F: The TPM does not have enough space to load the requested resource.[2]0x80290210: There are too many TPM contexts in use.[2]0x80290211: The TPM command failed.[2]0x80290212: The TBS does not recognize the specified ordinal.[2]0x80290213: The requested resource is no longer available.[2]0x80290214: The resource type did not match.[2]0x80290215: No resources can be unloaded.[2]0x80290216: No new entries can be added to the hash table.[2]0x80290217: A new TBS context could not be created because there are too many open contexts.[2]0x80290218: A new virtual resource could not be created because there are too many open virtual resources.[2]0x80290219: The physical presence interface is not supported.[2]0x8029021A: TBS is not compatible with the version of TPM found on the system.[2]0x8029021B: No TCG event log is available.[2]0x80290300: A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command.[2]0x80290301: The user failed to confirm the TPM operation request.[2]0x80290302: The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM).[2]0x80290303: The BIOS does not support the physical presence interface.[2]0x80290304: The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command.[2]0x80290400: This is an error mask to convert Platform Crypto Provider errors to win errors.[2]0x80290401: The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational.[2]0x80290402: The handle provided to the Platform Crypto Provider is invalid.[2]0x80290403: A parameter provided to the Platform Crypto Provider is invalid.[2]0x80290404: A provided flag to the Platform Crypto Provider is not supported.[2]0x80290405: The requested operation is not supported by this Platform Crypto Provider.[2]0x80290406: The buffer is too small to contain all data. No information has been written to the buffer.[2]0x80290407: An unexpected internal error has occurred in the Platform Crypto Provider.[2]0x80290408: The authorization to use a provider object has failed.[2]0x80290409: The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack.[2]0x8029040A: The referenced policy was not found.[2]0x8029040B: The referenced profile was not found.[2]0x8029040C: The validation was not succesful.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0