TpmSoftwareMessages
TpmSoftwareMessages.Instance (HResult.TPM_SOFTWARE) contains Microsoft's HResult code descriptions for Trusted Platform Module applications (TPM_SOFTWARE facility).
HResult | Key | Text | Exception |
---|---|---|---|
0x80290100 | TPM_SOFTWARE.TPMAPI_E_INVALID_STATE | The command buffer is not in the correct state. | |
0x80290101 | TPM_SOFTWARE.TPMAPI_E_NOT_ENOUGH_DATA | The command buffer does not contain enough data to satisfy the request. | |
0x80290102 | TPM_SOFTWARE.TPMAPI_E_TOO_MUCH_DATA | The command buffer cannot contain any more data. | |
0x80290103 | TPM_SOFTWARE.TPMAPI_E_INVALID_OUTPUT_POINTER | One or more output parameters was null or invalid. | |
0x80290104 | TPM_SOFTWARE.TPMAPI_E_INVALID_PARAMETER | One or more input parameters are invalid. | |
0x80290105 | TPM_SOFTWARE.TPMAPI_E_OUT_OF_MEMORY | Not enough memory was available to satisfy the request. | |
0x80290106 | TPM_SOFTWARE.TPMAPI_E_BUFFER_TOO_SMALL | The specified buffer was too small. | |
0x80290107 | TPM_SOFTWARE.TPMAPI_E_INTERNAL_ERROR | An internal error was detected. | |
0x80290108 | TPM_SOFTWARE.TPMAPI_E_ACCESS_DENIED | The caller does not have the appropriate rights to perform the requested operation. | |
0x80290109 | TPM_SOFTWARE.TPMAPI_E_AUTHORIZATION_FAILED | The specified authorization information was invalid. | |
0x8029010A | TPM_SOFTWARE.TPMAPI_E_INVALID_CONTEXT_HANDLE | The specified context handle was not valid. | |
0x8029010B | TPM_SOFTWARE.TPMAPI_E_TBS_COMMUNICATION_ERROR | An error occurred while communicating with the TBS. | |
0x8029010C | TPM_SOFTWARE.TPMAPI_E_TPM_COMMAND_ERROR | The TPM returned an unexpected result. | |
0x8029010D | TPM_SOFTWARE.TPMAPI_E_MESSAGE_TOO_LARGE | The message was too large for the encoding scheme. | |
0x8029010E | TPM_SOFTWARE.TPMAPI_E_INVALID_ENCODING | The encoding in the binary large object (BLOB) was not recognized. | |
0x8029010F | TPM_SOFTWARE.TPMAPI_E_INVALID_KEY_SIZE | The key size is not valid. | |
0x80290110 | TPM_SOFTWARE.TPMAPI_E_ENCRYPTION_FAILED | The encryption operation failed. | |
0x80290111 | TPM_SOFTWARE.TPMAPI_E_INVALID_KEY_PARAMS | The key parameters structure was not valid. | |
0x80290112 | TPM_SOFTWARE.TPMAPI_E_INVALID_MIGRATION_AUTHORIZATION_BLOB | The requested supplied data does not appear to be a valid migration authorization BLOB. | |
0x80290113 | TPM_SOFTWARE.TPMAPI_E_INVALID_PCR_INDEX | The specified PCR index was invalid. | |
0x80290114 | TPM_SOFTWARE.TPMAPI_E_INVALID_DELEGATE_BLOB | The data given does not appear to be a valid delegate BLOB. | |
0x80290115 | TPM_SOFTWARE.TPMAPI_E_INVALID_CONTEXT_PARAMS | One or more of the specified context parameters was not valid. | |
0x80290116 | TPM_SOFTWARE.TPMAPI_E_INVALID_KEY_BLOB | The data given does not appear to be a valid key BLOB. | |
0x80290117 | TPM_SOFTWARE.TPMAPI_E_INVALID_PCR_DATA | The specified PCR data was invalid. | |
0x80290118 | TPM_SOFTWARE.TPMAPI_E_INVALID_OWNER_AUTH | The format of the owner authorization data was invalid. | |
0x80290200 | TPM_SOFTWARE.TBSIMP_E_BUFFER_TOO_SMALL | The specified buffer was too small. | |
0x80290201 | TPM_SOFTWARE.TBSIMP_E_CLEANUP_FAILED | The context could not be cleaned up. | |
0x80290202 | TPM_SOFTWARE.TBSIMP_E_INVALID_CONTEXT_HANDLE | The specified context handle is invalid. | |
0x80290203 | TPM_SOFTWARE.TBSIMP_E_INVALID_CONTEXT_PARAM | An invalid context parameter was specified. | |
0x80290204 | TPM_SOFTWARE.TBSIMP_E_TPM_ERROR | An error occurred while communicating with the TPM. | |
0x80290205 | TPM_SOFTWARE.TBSIMP_E_HASH_BAD_KEY | No entry with the specified key was found. | |
0x80290206 | TPM_SOFTWARE.TBSIMP_E_DUPLICATE_VHANDLE | The specified virtual handle matches a virtual handle already in use. | |
0x80290207 | TPM_SOFTWARE.TBSIMP_E_INVALID_OUTPUT_POINTER | The pointer to the returned handle location was null or invalid. | |
0x80290208 | TPM_SOFTWARE.TBSIMP_E_INVALID_PARAMETER | One or more parameters are invalid. | |
0x80290209 | TPM_SOFTWARE.TBSIMP_E_RPC_INIT_FAILED | The RPC subsystem could not be initialized. | |
0x8029020A | TPM_SOFTWARE.TBSIMP_E_SCHEDULER_NOT_RUNNING | The TBS scheduler is not running. | |
0x8029020B | TPM_SOFTWARE.TBSIMP_E_COMMAND_CANCELED | The command was canceled. | |
0x8029020C | TPM_SOFTWARE.TBSIMP_E_OUT_OF_MEMORY | There was not enough memory to fulfill the request. | |
0x8029020D | TPM_SOFTWARE.TBSIMP_E_LIST_NO_MORE_ITEMS | The specified list is empty, or the iteration has reached the end of the list. | |
0x8029020E | TPM_SOFTWARE.TBSIMP_E_LIST_NOT_FOUND | The specified item was not found in the list. | |
0x8029020F | TPM_SOFTWARE.TBSIMP_E_NOT_ENOUGH_SPACE | The TPM does not have enough space to load the requested resource. | |
0x80290210 | TPM_SOFTWARE.TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS | There are too many TPM contexts in use. | |
0x80290211 | TPM_SOFTWARE.TBSIMP_E_COMMAND_FAILED | The TPM command failed. | |
0x80290212 | TPM_SOFTWARE.TBSIMP_E_UNKNOWN_ORDINAL | The TBS does not recognize the specified ordinal. | |
0x80290213 | TPM_SOFTWARE.TBSIMP_E_RESOURCE_EXPIRED | The requested resource is no longer available. | |
0x80290214 | TPM_SOFTWARE.TBSIMP_E_INVALID_RESOURCE | The resource type did not match. | |
0x80290215 | TPM_SOFTWARE.TBSIMP_E_NOTHING_TO_UNLOAD | No resources can be unloaded. | |
0x80290216 | TPM_SOFTWARE.TBSIMP_E_HASH_TABLE_FULL | No new entries can be added to the hash table. | |
0x80290217 | TPM_SOFTWARE.TBSIMP_E_TOO_MANY_TBS_CONTEXTS | A new TBS context could not be created because there are too many open contexts. | |
0x80290218 | TPM_SOFTWARE.TBSIMP_E_TOO_MANY_RESOURCES | A new virtual resource could not be created because there are too many open virtual resources. | |
0x80290219 | TPM_SOFTWARE.TBSIMP_E_PPI_NOT_SUPPORTED | The physical presence interface is not supported. | |
0x8029021A | TPM_SOFTWARE.TBSIMP_E_TPM_INCOMPATIBLE | TBS is not compatible with the version of TPM found on the system. | |
0x80290300 | TPM_SOFTWARE.TPM_E_PPI_ACPI_FAILURE | A general error was detected when attempting to acquire the BIOS response to a physical presence command. | |
0x80290301 | TPM_SOFTWARE.TPM_E_PPI_USER_ABORT | The user failed to confirm the TPM operation request. | |
0x80290302 | TPM_SOFTWARE.TPM_E_PPI_BIOS_FAILURE | The BIOS failure prevented the successful execution of the requested TPM operation (for example, invalid TPM operation request, BIOS communication error with the TPM). | |
0x80290303 | TPM_SOFTWARE.TPM_E_PPI_NOT_SUPPORTED | The BIOS does not support the physical presence interface. |
This document is partially derived from work with following license.
/*This file is a derivate of a source file that has following license (below). ======================================================================== The MIT License (MIT) Copyright (c) Microsoft Corporation Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ======================================================================*/