COM Error Codes (TPM, PLA, FVE)

The following table provides a list of error codes used by COM-based APIs.

If you are experiencing difficulty with an application you are installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, go to https://support.microsoft.com.

Symbolic	Code	Description
TPM_E_ERROR_MASK	0x80280000	This is an error mask to convert TPM hardware errors to win errors.
TPM_E_AUTHFAIL	0x80280001	Authentication failed.
TPM_E_BADINDEX	0x80280002	The index to a PCR, DIR or other register is incorrect.
TPM_E_BAD_PARAMETER	0x80280003	One or more parameter is bad.
TPM_E_AUDITFAILURE	0x80280004	An operation completed successfully but the auditing of that operation failed.
TPM_E_CLEAR_DISABLED	0x80280005	The clear disable flag is set and all clear operations now require physical access.
TPM_E_DEACTIVATED	0x80280006	Activate the Trusted Platform Module (TPM).
TPM_E_DISABLED	0x80280007	Enable the Trusted Platform Module (TPM).
TPM_E_DISABLED_CMD	0x80280008	The target command has been disabled.
TPM_E_FAIL	0x80280009	The operation failed.
TPM_E_BAD_ORDINAL	0x8028000A	The ordinal was unknown or inconsistent.
TPM_E_INSTALL_DISABLED	0x8028000B	The ability to install an owner is disabled.
TPM_E_INVALID_KEYHANDLE	0x8028000C	The key handle cannot be interpreted.
TPM_E_KEYNOTFOUND	0x8028000D	The key handle points to an invalid key.
TPM_E_INAPPROPRIATE_ENC	0x8028000E	Unacceptable encryption scheme.
TPM_E_MIGRATEFAIL	0x8028000F	Migration authorization failed.
TPM_E_INVALID_PCR_INFO	0x80280010	PCR information could not be interpreted.
TPM_E_NOSPACE	0x80280011	No room to load key.
TPM_E_NOSRK	0x80280012	There is no Storage Root Key (SRK) set.
TPM_E_NOTSEALED_BLOB	0x80280013	An encrypted blob is invalid or was not created by this TPM.
TPM_E_OWNER_SET	0x80280014	The Trusted Platform Module (TPM) already has an owner.
TPM_E_RESOURCES	0x80280015	The TPM has insufficient internal resources to perform the requested action.
TPM_E_SHORTRANDOM	0x80280016	A random string was too short.
TPM_E_SIZE	0x80280017	The TPM does not have the space to perform the operation.
TPM_E_WRONGPCRVAL	0x80280018	The named PCR value does not match the current PCR value.
TPM_E_BAD_PARAM_SIZE	0x80280019	The paramSize argument to the command has the incorrect value .
TPM_E_SHA_THREAD	0x8028001A	There is no existing SHA-1 thread.
TPM_E_SHA_ERROR	0x8028001B	The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error.
TPM_E_FAILEDSELFTEST	0x8028001C	The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, you might need to replace your TPM hardware or motherboard.
TPM_E_AUTH2FAIL	0x8028001D	The authorization for the second key in a 2 key function failed authorization.
TPM_E_BADTAG	0x8028001E	The tag value sent to for a command is invalid.
TPM_E_IOERROR	0x8028001F	An IO error occurred transmitting information to the TPM.
TPM_E_ENCRYPT_ERROR	0x80280020	The encryption process had a problem.
TPM_E_DECRYPT_ERROR	0x80280021	The decryption process did not complete.
TPM_E_INVALID_AUTHHANDLE	0x80280022	An invalid handle was used.
TPM_E_NO_ENDORSEMENT	0x80280023	The TPM does not have an Endorsement Key (EK) installed.
TPM_E_INVALID_KEYUSAGE	0x80280024	The usage of a key is not allowed.
TPM_E_WRONG_ENTITYTYPE	0x80280025	The submitted entity type is not allowed.
TPM_E_INVALID_POSTINIT	0x80280026	The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup.
TPM_E_INAPPROPRIATE_SIG	0x80280027	Signed data cannot include additional DER information.
TPM_E_BAD_KEY_PROPERTY	0x80280028	The key properties in TPM_KEY_PARMs are not supported by this TPM.
TPM_E_BAD_MIGRATION	0x80280029	The migration properties of this key are incorrect.
TPM_E_BAD_SCHEME	0x8028002A	The signature or encryption scheme for this key is incorrect or not permitted in this situation.
TPM_E_BAD_DATASIZE	0x8028002B	The size of the data (or blob) parameter is bad or inconsistent with the referenced key.
TPM_E_BAD_MODE	0x8028002C	A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob.
TPM_E_BAD_PRESENCE	0x8028002D	Either the physicalPresence or physicalPresenceLock bits have the wrong value.
TPM_E_BAD_VERSION	0x8028002E	The TPM cannot perform this version of the capability.
TPM_E_NO_WRAP_TRANSPORT	0x8028002F	The TPM does not allow for wrapped transport sessions.
TPM_E_AUDITFAIL_UNSUCCESSFUL	0x80280030	TPM audit construction failed and the underlying command was returning a failure code also.
TPM_E_AUDITFAIL_SUCCESSFUL	0x80280031	TPM audit construction failed and the underlying command was returning success.
TPM_E_NOTRESETABLE	0x80280032	Attempt to reset a PCR register that does not have the resettable attribute.
TPM_E_NOTLOCAL	0x80280033	Attempt to reset a PCR register that requires locality and locality modifier not part of command transport.
TPM_E_BAD_TYPE	0x80280034	Make identity blob not properly typed.
TPM_E_INVALID_RESOURCE	0x80280035	When saving context identified resource type does not match actual resource.
TPM_E_NOTFIPS	0x80280036	The TPM is attempting to execute a command only available when in FIPS mode.
TPM_E_INVALID_FAMILY	0x80280037	The command is attempting to use an invalid family ID.
TPM_E_NO_NV_PERMISSION	0x80280038	The permission to manipulate the NV storage is not available.
TPM_E_REQUIRES_SIGN	0x80280039	The operation requires a signed command.
TPM_E_KEY_NOTSUPPORTED	0x8028003A	Wrong operation to load an NV key.
TPM_E_AUTH_CONFLICT	0x8028003B	NV_LoadKey blob requires both owner and blob authorization.
TPM_E_AREA_LOCKED	0x8028003C	The NV area is locked and not writtable.
TPM_E_BAD_LOCALITY	0x8028003D	The locality is incorrect for the attempted operation.
TPM_E_READ_ONLY	0x8028003E	The NV area is read only and can't be written to.
TPM_E_PER_NOWRITE	0x8028003F	There is no protection on the write to the NV area.
TPM_E_FAMILYCOUNT	0x80280040	The family count value does not match.
TPM_E_WRITE_LOCKED	0x80280041	The NV area has already been written to.
TPM_E_BAD_ATTRIBUTES	0x80280042	The NV area attributes conflict.
TPM_E_INVALID_STRUCTURE	0x80280043	The structure tag and version are invalid or inconsistent.
TPM_E_KEY_OWNER_CONTROL	0x80280044	The key is under control of the TPM Owner and can only be evicted by the TPM Owner.
TPM_E_BAD_COUNTER	0x80280045	The counter handle is incorrect.
TPM_E_NOT_FULLWRITE	0x80280046	The write is not a complete write of the area.
TPM_E_CONTEXT_GAP	0x80280047	The gap between saved context counts is too large.
TPM_E_MAXNVWRITES	0x80280048	The maximum number of NV writes without an owner has been exceeded.
TPM_E_NOOPERATOR	0x80280049	No operator AuthData value is set.
TPM_E_RESOURCEMISSING	0x8028004A	The resource pointed to by context is not loaded.
TPM_E_DELEGATE_LOCK	0x8028004B	The delegate administration is locked.
TPM_E_DELEGATE_FAMILY	0x8028004C	Attempt to manage a family other than the delegated family.
TPM_E_DELEGATE_ADMIN	0x8028004D	Delegation table management not enabled.
TPM_E_TRANSPORT_NOTEXCLUSIVE	0x8028004E	There was a command executed outside of an exclusive transport session.
TPM_E_OWNER_CONTROL	0x8028004F	Attempt to context save an owner evict controlled key.
TPM_E_DAA_RESOURCES	0x80280050	The DAA command has no resources availble to execute the command.
TPM_E_DAA_INPUT_DATA0	0x80280051	The consistency check on DAA parameter inputData0 has failed.
TPM_E_DAA_INPUT_DATA1	0x80280052	The consistency check on DAA parameter inputData1 has failed.
TPM_E_DAA_ISSUER_SETTINGS	0x80280053	The consistency check on DAA_issuerSettings has failed.
TPM_E_DAA_TPM_SETTINGS	0x80280054	The consistency check on DAA_tpmSpecific has failed.
TPM_E_DAA_STAGE	0x80280055	The atomic process indicated by the submitted DAA command is not the expected process.
TPM_E_DAA_ISSUER_VALIDITY	0x80280056	The issuer's validity check has detected an inconsistency.
TPM_E_DAA_WRONG_W	0x80280057	The consistency check on w has failed.
TPM_E_BAD_HANDLE	0x80280058	The handle is incorrect.
TPM_E_BAD_DELEGATE	0x80280059	Delegation is not correct.
TPM_E_BADCONTEXT	0x8028005A	The context blob is invalid.
TPM_E_TOOMANYCONTEXTS	0x8028005B	Too many contexts held by the TPM.
TPM_E_MA_TICKET_SIGNATURE	0x8028005C	Migration authority signature validation failure.
TPM_E_MA_DESTINATION	0x8028005D	Migration destination not authenticated.
TPM_E_MA_SOURCE	0x8028005E	Migration source incorrect.
TPM_E_MA_AUTHORITY	0x8028005F	Incorrect migration authority.
TPM_E_PERMANENTEK	0x80280061	Attempt to revoke the EK and the EK is not revocable.
TPM_E_BAD_SIGNATURE	0x80280062	Bad signature of CMK ticket.
TPM_E_NOCONTEXTSPACE	0x80280063	There is no room in the context list for additional contexts.
TPM_E_COMMAND_BLOCKED	0x80280400	The command was blocked.
TPM_E_INVALID_HANDLE	0x80280401	The specified handle was not found.
TPM_E_DUPLICATE_VHANDLE	0x80280402	The TPM returned a duplicate handle and the command needs to be resubmitted.
TPM_E_EMBEDDED_COMMAND_BLOCKED	0x80280403	The command within the transport was blocked.
TPM_E_EMBEDDED_COMMAND_UNSUPPORTED	0x80280404	The command within the transport is not supported.
TPM_E_RETRY	0x80280800	The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time.
TPM_E_NEEDS_SELFTEST	0x80280801	SelfTestFull has not been run.
TPM_E_DOING_SELFTEST	0x80280802	The TPM is currently executing a full selftest.
TPM_E_DEFEND_LOCK_RUNNING	0x80280803	The TPM is defending against dictionary attacks and is in a time-out period.
TPM_20_E_ATTRIBUTES	0x80280082	TPM 2.0: Inconsistent attributes.
TPM_20_E_HASH	0x80280083	TPM 2.0: Hash algorithm not supported or not appropriate.
TPM_20_E_VALUE	0x80280084	TPM 2.0: Value is out of range or is not correct for the context.
TPM_20_E_HIERARCHY	0x80280085	TPM 2.0: Hierarchy is not enabled or is not correct for the use.
TPM_20_E_KEY_SIZE	0x80280086	TPM 2.0: Key size is not supported.
TPM_20_E_MGF	0x80280087	TPM 2.0: Mask generation function not supported.
TPM_20_E_MODE	0x80280089	TPM 2.0: Mode of operation not supported.
TPM_20_E_TYPE	0x8028008A	TPM 2.0: The type of the value is not appropriate for the use.
TPM_20_E_HANDLE	0x8028008B	TPM 2.0: The Handle is not correct for the use.
TPM_20_E_KDF	0x8028008C	TPM 2.0: Unsupported key derivation function or function not appropriate for use.
TPM_20_E_RANGE	0x8028008D	TPM 2.0: Value was out of allowed range.
TPM_20_E_AUTH_FAIL	0x8028008E	TPM 2.0: The authorization HMAC check failed and DA counter incremented.
TPM_20_E_NONCE	0x8028008F	TPM 2.0: Invalid nonce size.
TPM_20_E_SCHEME	0x80280092	TPM 2.0: Unsupported or incompatible scheme.
TPM_20_E_SIZE	0x80280095	TPM 2.0: Structure is wrong size..
TPM_20_E_SYMMETRIC	0x80280096	TPM 2.0: Unsupported symmetric algorithm or key size, or not appropriate for instance.
TPM_20_E_TAG	0x80280097	TPM 2.0: Incorrect structure tag.
TPM_20_E_SELECTOR	0x80280098	TPM 2.0: Union selector is incorrect.
TPM_20_E_INSUFFICIENT	0x8028009A	TPM 2.0: The TPM was unable to unmarshal a value because there were not enough octets in the input buffer.
TPM_20_E_SIGNATURE	0x8028009B	TPM 2.0: The signature is not valid.
TPM_20_E_KEY	0x80280087	TPM 2.0: Key fields are not compatible with the selected use.
TPM_20_E_POLICY_FAIL	0x8028009D	TPM 2.0: A policy check failed.
TPM_20_E_INTEGRITY	0x8028009F	TPM 2.0: Integrity check failed.
TPM_20_E_TICKET	0x802800A0	TPM 2.0: Invalid ticket.
TPM_20_E_RESERVED_BITS	0x802800A1	TPM 2.0: Reserved bits not set to zero as required.
TPM_20_E_BAD_AUTH	0x802800A2	TPM 2.0: Authorization failure without DA implications.
TPM_20_E_EXPIRED	0x802800A3	TPM 2.0: The policy has expired.
TPM_20_E_POLICY_CC	0x802800A4	TPM 2.0: The command code in the policy is not the command code of the command or the command code in a policy command references a command that is not implemented.
TPM_20_E_BINDING	0x802800A5	TPM 2.0: Public and sensitive portions of an object are not cryptographically bound.
TPM_20_E_CURVE	0x802800A6	TPM 2.0: Curve not supported.
TPM_20_E_ECC_POINT	0x802800A7	TPM 2.0: Point is not on the required curve.
TPM_20_E_INITIALIZE	0x80280100	TPM 2.0: TPM not initialized.
TPM_20_E_FAILURE	0x80280101	TPM 2.0: Commands not being accepted because of a TPM failure.
TPM_20_E_SEQUENCE	0x80280103	TPM 2.0: Improper use of a sequence handle.
TPM_20_E_PRIVATE		TPM 2.0: TPM_RC_PRIVATE error.
TPM_20_E_HMAC	0x80280119	TPM 2.0: TPM_RC_HMAC.
TPM_20_E_DISABLED	0x80280120	TPM 2.0: TPM_RC_DISABLED.
TPM_20_E_EXCLUSIVE	0x80280121	TPM 2.0: Command failed because audit sequence required exclusivity.
TPM_20_E_ECC_CURVE	0x80280123	TPM 2.0: Unsupported ECC curve.
TPM_20_E_AUTH_TYPE	0x80280124	TPM 2.0: Authorization handle is not correct for command.
TPM_20_E_AUTH_MISSING	0x80280125	TPM 2.0: Command requires an authorization session for handle and is not present.
TPM_20_E_POLICY	0x80280126	TPM 2.0: Policy failure in Math Operation or an invalid authPolicy value.
TPM_20_E_PCR	0x80280127	TPM 2.0: PCR check fail.
TPM_20_E_PCR_CHANGED	0x80280128	TPM 2.0: PCR have changed since checked.
TPM_20_E_UPGRADE	0x8028012D	TPM 2.0: The TPM is not in the right mode for upgrade.
TPM_20_E_TOO_MANY_CONTEXTS	0x8028012E	TPM 2.0: Context ID counter is at maximum.
TPM_20_E_AUTH_UNAVAILABLE	0x8028012F	TPM 2.0: authValue or authPolicy is not available for selected entity.
TPM_20_E_REBOOT	0x80280130	TPM 2.0: A _TPM_Init and Startup(CLEAR) is required before the TPM can resume operation.
TPM_20_E_UNBALANCED	0x80280131	TPM 2.0: The protection algorithms (hash and symmetric) are not reasonably balanced. The digest size of the hash must be larger than the key size of the symmetric algorithm.
TPM_20_E_COMMAND_SIZE	0x80280142	TPM 2.0: The TPM command's commandSize value is inconsistent with contents of the command buffer; either the size is not the same as the bytes loaded by the hardware interface layer or the value is not large enough to hold a command header.
TPM_20_E_COMMAND_CODE	0x80280143	TPM 2.0: Command code not supported.
TPM_20_E_AUTHSIZE	0x80280144	TPM 2.0: The value of authorizationSize is out of range or the number of octets in the authorization Area is greater than required.
TPM_20_E_AUTH_CONTEXT	0x80280145	TPM 2.0: Use of an authorization session with a context command or another command that cannot have an authorization session.
TPM_20_E_NV_RANGE	0x80280146	TPM 2.0: NV offset+size is out of range.
TPM_20_E_NV_SIZE	0x80280147	TPM 2.0: Requested allocation size is larger than allowed.
TPM_20_E_NV_LOCKED	0x80280148	TPM 2.0: NV access locked.
TPM_20_E_NV_AUTHORIZATION	0x80280149	TPM 2.0: NV access authorization fails in command actions
TPM_20_E_NV_UNINITIALIZED	0x8028014A	TPM 2.0: An NV index is used before being initialized or the state saved by TPM2_Shutdown(STATE) could not be restored.
TPM_20_E_NV_SPACE	0x8028014B	TPM 2.0: Insufficient space for NV allocation.
TPM_20_E_NV_DEFINED	0x8028014C	TPM 2.0: NV index or persistent object already defined.
TPM_20_E_BAD_CONTEXT	0x80280150	TPM 2.0: Context in TPM2_ContextLoad() is not valid.
TPM_20_E_CPHASH	0x80280151	TPM 2.0: chHash value already set or not correct for use.
TPM_20_E_PARENT	0x80280152	TPM 2.0: Handle for parent is not a valid parent.
TPM_20_E_NEEDS_TEST	0x80280153	TPM 2.0: Some function needs testing.
TPM_20_E_NO_RESULT	0x80280154	TPM 2.0: returned when an internal function cannot process a request due to an unspecified problem. This code is usually related to invalid parameters that are not properly filtered by the input unmarshaling code.
TPM_20_E_SENSITIVE	0x80280155	TPM 2.0: The sensitive area did not unmarshal correctly after decryption - this code is used in lieu of the other unmarshaling errors so that an attacker cannot determine where the unmarshaling error occurred.
TPM_20_E_CONTEXT_GAP	0x80280901	TPM 2.0: Gap for context ID is too large.
TPM_20_E_OBJECT_MEMORY	0x80280902	TPM 2.0: Out of memory for object contexts.
TPM_20_E_SESSION_MEMORY	0x80280903	TPM 2.0: Out of memory for session contexts.
TPM_20_E_MEMORY	0x80280904	TPM 2.0: Out of shared object/session memory or need space for internal operations.
TPM_20_E_SESSION_HANDLES	0x80280905	TPM 2.0: Out of session handles - a session must be flushed before a new session may be created.
TPM_20_E_OBJECT_HANDLES	0x80280906	TPM 2.0: Out of object handles - the handle space for objects is depleted and a reboot is required.
TPM_20_E_LOCALITY	0x80280907	TPM 2.0: Bad locality.
TPM_20_E_YIELDED	0x80280908	TPM 2.0: The TPM has suspended operation on the command; forward progress was made and the command may be retried.
TPM_20_E_CANCELED	0x80280909	TPM 2.0: The command was canceled.
TPM_20_E_TESTING	0x8028090A	TPM 2.0: TPM is performing self-tests.
TPM_20_E_NV_RATE	0x80280920	TPM 2.0: The TPM is rate-limiting accesses to prevent wearout of NV.
TPM_20_E_LOCKOUT	0x80280921	TPM 2.0: Authorization for objects subject to DA protection are not allowed at this time because the TPM is in DA lockout mode.
TPM_20_E_RETRY	0x80280922	TPM 2.0: The TPM was not able to start the command.
TPM_20_E_NV_UNAVAILABLE	0x80280923	TPM 2.0: the command may require writing of NV and NV is not current accessible..
TBS_E_INTERNAL_ERROR	0x80284001	An internal software error has been detected.
TBS_E_BAD_PARAMETER	0x80284002	One or more input parameters is bad.
TBS_E_INVALID_OUTPUT_POINTER	0x80284003	A specified output pointer is bad.
TBS_E_INVALID_CONTEXT	0x80284004	The specified context handle does not refer to a valid context.
TBS_E_INSUFFICIENT_BUFFER	0x80284005	A specified output buffer is too small.
TBS_E_IOERROR	0x80284006	An error occurred while communicating with the TPM.
TBS_E_INVALID_CONTEXT_PARAM	0x80284007	One or more context parameters is invalid.
TBS_E_SERVICE_NOT_RUNNING	0x80284008	The TBS service is not running and could not be started.
TBS_E_TOO_MANY_TBS_CONTEXTS	0x80284009	A new context could not be created because there are too many open contexts.
TBS_E_TOO_MANY_RESOURCES	0x8028400A	A new virtual resource could not be created because there are too many open virtual resources.
TBS_E_SERVICE_START_PENDING	0x8028400B	The TBS service has been started but is not yet running.
TBS_E_PPI_NOT_SUPPORTED	0x8028400C	The physical presence interface is not supported.
TBS_E_COMMAND_CANCELED	0x8028400D	The command was canceled.
TBS_E_BUFFER_TOO_LARGE	0x8028400E	The input or output buffer is too large.
TBS_E_TPM_NOT_FOUND	0x8028400F	A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer.
TBS_E_SERVICE_DISABLED	0x80284010	The TBS service has been disabled.
TBS_E_NO_EVENT_LOG	0x80284011	No TCG event log is available.
TBS_E_ACCESS_DENIED	0x80284012	The caller does not have the appropriate rights to perform the requested operation.
TBS_E_PROVISIONING_NOT_ALLOWED	0x80284013	The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions may be required. The TPM management console (tpm.msc) action to make the TPM Ready may help. For further information, see the documentation for the Win32_Tpm WMI method 'Provision'. (The actions that may be required include importing the TPM Owner Authorization value into the system, calling the Win32_Tpm WMI method for provisioning the TPM and specifying TRUE for either 'ForceClear_Allowed' or 'PhysicalPresencePrompts_Allowed' (as indicated by the value returned in the Additional Information), or enabling the TPM in the system BIOS.)
TBS_E_PPI_FUNCTION_UNSUPPORTED	0x80284014	The Physical Presence Interface of this firmware does not support the requested method.
TBS_E_OWNERAUTH_NOT_FOUND	0x80284015	The requested TPM OwnerAuth value was not found.
TBS_E_PROVISIONING_INCOMPLETE	0x80284016	The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information.
TPMAPI_E_INVALID_STATE	0x80290100	The command buffer is not in the correct state.
TPMAPI_E_NOT_ENOUGH_DATA	0x80290101	The command buffer does not contain enough data to satisfy the request.
TPMAPI_E_TOO_MUCH_DATA	0x80290102	The command buffer cannot contain any more data.
TPMAPI_E_INVALID_OUTPUT_POINTER	0x80290103	One or more output parameters was NULL or invalid.
TPMAPI_E_INVALID_PARAMETER	0x80290104	One or more input parameters is invalid.
TPMAPI_E_OUT_OF_MEMORY	0x80290105	Not enough memory was available to satisfy the request.
TPMAPI_E_BUFFER_TOO_SMALL	0x80290106	The specified buffer was too small.
TPMAPI_E_INTERNAL_ERROR	0x80290107	An internal error was detected.
TPMAPI_E_ACCESS_DENIED	0x80290108	The caller does not have the appropriate rights to perform the requested operation.
TPMAPI_E_AUTHORIZATION_FAILED	0x80290109	The specified authorization information was invalid.
TPMAPI_E_INVALID_CONTEXT_HANDLE	0x8029010A	The specified context handle was not valid.
TPMAPI_E_TBS_COMMUNICATION_ERROR	0x8029010B	An error occurred while communicating with the TBS.
TPMAPI_E_TPM_COMMAND_ERROR	0x8029010C	The TPM returned an unexpected result.
TPMAPI_E_MESSAGE_TOO_LARGE	0x8029010D	The message was too large for the encoding scheme.
TPMAPI_E_INVALID_ENCODING	0x8029010E	The encoding in the blob was not recognized.
TPMAPI_E_INVALID_KEY_SIZE	0x8029010F	The key size is not valid.
TPMAPI_E_ENCRYPTION_FAILED	0x80290110	The encryption operation failed.
TPMAPI_E_INVALID_KEY_PARAMS	0x80290111	The key parameters structure was not valid
TPMAPI_E_INVALID_MIGRATION_AUTHORIZATION_BLOB	0x80290112	The requested supplied data does not appear to be a valid migration authorization blob.
TPMAPI_E_INVALID_PCR_INDEX	0x80290113	The specified PCR index was invalid
TPMAPI_E_INVALID_DELEGATE_BLOB	0x80290114	The data given does not appear to be a valid delegate blob.
TPMAPI_E_INVALID_CONTEXT_PARAMS	0x80290115	One or more of the specified context parameters was not valid.
TPMAPI_E_INVALID_KEY_BLOB	0x80290116	The data given does not appear to be a valid key blob
TPMAPI_E_INVALID_PCR_DATA	0x80290117	The specified PCR data was invalid.
TPMAPI_E_INVALID_OWNER_AUTH	0x80290118	The format of the owner auth data was invalid.
TPMAPI_E_FIPS_RNG_CHECK_FAILED	0x80290119	The random number generated did not pass FIPS RNG check.
TPMAPI_E_EMPTY_TCG_LOG	0x8029011A	The TCG Event Log does not contain any data.
TPMAPI_E_INVALID_TCG_LOG_ENTRY	0x8029011B	An entry in the TCG Event Log was invalid.
TPMAPI_E_TCG_SEPARATOR_ABSENT	0x8029011C	A TCG Separator was not found.
TPMAPI_E_TCG_INVALID_DIGEST_ENTRY	0x8029011D	A digest value in a TCG Log entry did not match hashed data.
TPMAPI_E_POLICY_DENIES_OPERATION	0x8029011E	The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance.
TBSIMP_E_BUFFER_TOO_SMALL	0x80290200	The specified buffer was too small.
TBSIMP_E_CLEANUP_FAILED	0x80290201	The context could not be cleaned up.
TBSIMP_E_INVALID_CONTEXT_HANDLE	0x80290202	The specified context handle is invalid.
TBSIMP_E_INVALID_CONTEXT_PARAM	0x80290203	An invalid context parameter was specified.
TBSIMP_E_TPM_ERROR	0x80290204	An error occurred while communicating with the TPM
TBSIMP_E_HASH_BAD_KEY	0x80290205	No entry with the specified key was found.
TBSIMP_E_DUPLICATE_VHANDLE	0x80290206	The specified virtual handle matches a virtual handle already in use.
TBSIMP_E_INVALID_OUTPUT_POINTER	0x80290207	The pointer to the returned handle location was NULL or invalid
TBSIMP_E_INVALID_PARAMETER	0x80290208	One or more parameters is invalid
TBSIMP_E_RPC_INIT_FAILED	0x80290209	The RPC subsystem could not be initialized.
TBSIMP_E_SCHEDULER_NOT_RUNNING	0x8029020A	The TBS scheduler is not running.
TBSIMP_E_COMMAND_CANCELED	0x8029020B	The command was canceled.
TBSIMP_E_OUT_OF_MEMORY	0x8029020C	There was not enough memory to fulfill the request
TBSIMP_E_LIST_NO_MORE_ITEMS	0x8029020D	The specified list is empty, or the iteration has reached the end of the list.
TBSIMP_E_LIST_NOT_FOUND	0x8029020E	The specified item was not found in the list.
TBSIMP_E_NOT_ENOUGH_SPACE	0x8029020F	The TPM does not have enough space to load the requested resource.
TBSIMP_E_NOT_ENOUGH_TPM_CONTEXTS	0x80290210	There are too many TPM contexts in use.
TBSIMP_E_COMMAND_FAILED	0x80290211	The TPM command failed.
TBSIMP_E_UNKNOWN_ORDINAL	0x80290212	The TBS does not recognize the specified ordinal.
TBSIMP_E_RESOURCE_EXPIRED	0x80290213	The requested resource is no longer available.
TBSIMP_E_INVALID_RESOURCE	0x80290214	The resource type did not match.
TBSIMP_E_NOTHING_TO_UNLOAD	0x80290215	No resources can be unloaded.
TBSIMP_E_HASH_TABLE_FULL	0x80290216	No new entries can be added to the hash table.
TBSIMP_E_TOO_MANY_TBS_CONTEXTS	0x80290217	A new TBS context could not be created because there are too many open contexts.
TBSIMP_E_TOO_MANY_RESOURCES	0x80290218	A new virtual resource could not be created because there are too many open virtual resources.
TBSIMP_E_PPI_NOT_SUPPORTED	0x80290219	The physical presence interface is not supported.
TBSIMP_E_TPM_INCOMPATIBLE	0x8029021A	TBS is not compatible with the version of TPM found on the system.
TBSIMP_E_NO_EVENT_LOG	0x8029021B	No TCG event log is available.
TPM_E_PPI_ACPI_FAILURE	0x80290300	A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command.
TPM_E_PPI_USER_ABORT	0x80290301	The user failed to confirm the TPM operation request.
TPM_E_PPI_BIOS_FAILURE	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).
TPM_E_PPI_NOT_SUPPORTED	0x80290303	The BIOS does not support the physical presence interface.
TPM_E_PPI_BLOCKED_IN_BIOS	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.
TPM_E_PCP_ERROR_MASK	0x80290400	This is an error mask to convert Platform Crypto Provider errors to win errors.
TPM_E_PCP_DEVICE_NOT_READY	0x80290401	The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational.
TPM_E_PCP_INVALID_HANDLE	0x80290402	The handle provided to the Platform Crypto Provider is invalid.
TPM_E_PCP_INVALID_PARAMETER	0x80290403	A parameter provided to the Platform Crypto Provider is invalid.
TPM_E_PCP_FLAG_NOT_SUPPORTED	0x80290404	A provided flag to the Platform Crypto Provider is not supported.
TPM_E_PCP_NOT_SUPPORTED	0x80290405	The requested operation is not supported by this Platform Crypto Provider.
TPM_E_PCP_BUFFER_TOO_SMALL	0x80290406	The buffer is too small to contain all data. No information has been written to the buffer.
TPM_E_PCP_INTERNAL_ERROR	0x80290407	An unexpected internal error has occurred in the Platform Crypto Provider.
TPM_E_PCP_AUTHENTICATION_FAILED	0x80290408	The authorization to use a provider object has failed.
TPM_E_PCP_AUTHENTICATION_IGNORED	0x80290409	The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack.
TPM_E_PCP_POLICY_NOT_FOUND	0x8029040A	The referenced policy was not found.
TPM_E_PCP_PROFILE_NOT_FOUND	0x8029040B	The referenced profile was not found.
TPM_E_PCP_VALIDATION_FAILED	0x8029040C	The validation was not successful.
TPM_E_PCP_WRONG_PARENT	0x8029040E	An attempt was made to import or load a key under an incorrect storage parent.
TPM_E_KEY_NOT_LOADED	0x8029040F	The TPM key is not loaded.
TPM_E_NO_KEY_CERTIFICATION	0x80290410	The TPM key certification has not been generated.
TPM_E_KEY_NOT_FINALIZED	0x80290411	The TPM key is not yet finalized.
TPM_E_ATTESTATION_CHALLENGE_NOT_SET	0x80290412	The TPM attestation challenge is not set.
TPM_E_NOT_PCR_BOUND	0x80290413	The TPM PCR info is not available.
TPM_E_KEY_ALREADY_FINALIZED	0x80290414	The TPM key is already finalized.
TPM_E_KEY_USAGE_POLICY_NOT_SUPPORTED	0x80290415	The TPM key usage policy is not supported.
TPM_E_KEY_USAGE_POLICY_INVALID	0x80290416	The TPM key usage policy is invalid.
TPM_E_SOFT_KEY_ERROR	0x80290417	There was a problem with the software key being imported into the TPM.
TPM_E_KEY_NOT_AUTHENTICATED	0x80290418	The TPM key is not authenticated.
TPM_E_PCP_KEY_NOT_AIK	0x80290419	The TPM key is not an AIK.
TPM_E_KEY_NOT_SIGNING_KEY	0x8029041A	The TPM key is not a signing key.
TPM_E_LOCKED_OUT	0x8029041B	The TPM is locked out.
TPM_E_CLAIM_TYPE_NOT_SUPPORTED	0x8029041C	The claim type requested is not supported.
TPM_E_VERSION_NOT_SUPPORTED	0x8029041D	TPM version is not supported.
TPM_E_BUFFER_LENGTH_MISMATCH	0x8029041E	The buffer lengths do not match.
TPM_E_PCP_IFX_RSA_KEY_CREATION_BLOCKED	0x8029041F	The RSA key creation is blocked on this TPM due to known security vulnerabilities.
TPM_E_PCP_TICKET_MISSING	0x80290420	A ticket required to use a key was not provided.
TPM_E_PCP_RAW_POLICY_NOT_SUPPORTED	0x80290421	This key has a raw policy so the KSP can't authenticate against it.
TPM_E_PCP_KEY_HANDLE_INVALIDATED	0x80290422	The TPM key's handle was unexpectedly invalidated due to a hardware or firmware issue.
TPM_E_PCP_UNSUPPORTED_PSS_SALT	0x40290423	The requested salt size for signing with RSAPSS does not match what the TPM uses.
TPM_E_PCP_PLATFORM_CLAIM_MAY_BE_OUTDATED	0x40290424	Validation of the platform claim failed.
TPM_E_PCP_PLATFORM_CLAIM_OUTDATED	0x40290425	The requested platform claim is for a previous boot.
TPM_E_PCP_PLATFORM_CLAIM_REBOOT	0x40290426	The platform claim is for a previous boot, and cannot be created without reboot.
TPM_E_EXHAUST_ENABLED	0x80290500	TPM related network operations are blocked as Zero Exhaust mode is enabled on client.
TPM_E_PROVISIONING_INCOMPLETE	0x80290600	TPM provisioning did not run to completion.
TPM_E_INVALID_OWNER_AUTH	0x80290601	An invalid owner authorization value was specified.
TPM_E_TOO_MUCH_DATA	0x80290602	TPM command returned too much data.
PLA_E_DCS_NOT_FOUND	0x80300002	Data Collector Set was not found.
PLA_E_DCS_IN_USE	0x803000AA	The Data Collector Set or one of its dependencies is already in use.
PLA_E_TOO_MANY_FOLDERS	0x80300045	Unable to start Data Collector Set because there are too many folders.
PLA_E_NO_MIN_DISK	0x80300070	Not enough free disk space to start Data Collector Set.
PLA_E_DCS_ALREADY_EXISTS	0x803000B7	Data Collector Set already exists.
PLA_S_PROPERTY_IGNORED	0x00300100	Property value will be ignored.
PLA_E_PROPERTY_CONFLICT	0x80300101	Property value conflict.
PLA_E_DCS_SINGLETON_REQUIRED	0x80300102	The current configuration for this Data Collector Set requires that it contain exactly one Data Collector.
PLA_E_CREDENTIALS_REQUIRED	0x80300103	A user account is required in order to commit the current Data Collector Set properties.
PLA_E_DCS_NOT_RUNNING	0x80300104	Data Collector Set is not running.
PLA_E_CONFLICT_INCL_EXCL_API	0x80300105	A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list.
PLA_E_NETWORK_EXE_NOT_VALID	0x80300106	The executable path you have specified refers to a network share or UNC path.
PLA_E_EXE_ALREADY_CONFIGURED	0x80300107	The executable path you have specified is already configured for API tracing.
PLA_E_EXE_PATH_NOT_VALID	0x80300108	The executable path you have specified does not exist. Verify that the specified path is correct.
PLA_E_DC_ALREADY_EXISTS	0x80300109	Data Collector already exists.
PLA_E_DCS_START_WAIT_TIMEOUT	0x8030010A	The wait for the Data Collector Set start notification has timed out.
PLA_E_DC_START_WAIT_TIMEOUT	0x8030010B	The wait for the Data Collector to start has timed out.
PLA_E_REPORT_WAIT_TIMEOUT	0x8030010C	The wait for the report generation tool to finish has timed out.
PLA_E_NO_DUPLICATES	0x8030010D	Duplicate items are not allowed.
PLA_E_EXE_FULL_PATH_REQUIRED	0x8030010E	When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename.
PLA_E_INVALID_SESSION_NAME	0x8030010F	The session name provided is invalid.
PLA_E_PLA_CHANNEL_NOT_ENABLED	0x80300110	The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation.
PLA_E_TASKSCHED_CHANNEL_NOT_ENABLED	0x80300111	The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation.
PLA_E_RULES_MANAGER_FAILED	0x80300112	The execution of the Rules Manager failed.
PLA_E_CABAPI_FAILURE	0x80300113	An error occurred while attempting to compress or extract the data.
FVE_E_LOCKED_VOLUME	0x80310000	This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel.
FVE_E_NOT_ENCRYPTED	0x80310001	The drive is not encrypted.
FVE_E_NO_TPM_BIOS	0x80310002	The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.
FVE_E_NO_MBR_METRIC	0x80310003	The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions.
FVE_E_NO_BOOTSECTOR_METRIC	0x80310004	A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date.
FVE_E_NO_BOOTMGR_METRIC	0x80310005	The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).
FVE_E_WRONG_BOOTMGR	0x80310006	The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).
FVE_E_SECURE_KEY_REQUIRED	0x80310007	At least one secure key protector is required for this operation to be performed.
FVE_E_NOT_ACTIVATED	0x80310008	BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.
FVE_E_ACTION_NOT_ALLOWED	0x80310009	BitLocker Drive Encryption cannot perform requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again.
FVE_E_AD_SCHEMA_NOT_INSTALLED	0x8031000A	The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.
FVE_E_AD_INVALID_DATATYPE	0x8031000B	The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.
FVE_E_AD_INVALID_DATASIZE	0x8031000C	The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.
FVE_E_AD_NO_VALUES	0x8031000D	The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted.
FVE_E_AD_ATTR_NOT_SET	0x8031000E	The attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects.
FVE_E_AD_GUID_NOT_FOUND	0x8031000F	The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.
FVE_E_BAD_INFORMATION	0x80310010	The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.
FVE_E_TOO_SMALL	0x80310011	The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again.
FVE_E_SYSTEM_VOLUME	0x80310012	The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive.
FVE_E_FAILED_WRONG_FS	0x80310013	The drive cannot be encrypted because the file system is not supported.
FVE_E_BAD_PARTITION_SIZE	0x80310014	The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition.
FVE_E_NOT_SUPPORTED	0x80310015	This drive cannot be encrypted.
FVE_E_BAD_DATA	0x80310016	The data is not valid.
FVE_E_VOLUME_NOT_BOUND	0x80310017	The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically.
FVE_E_TPM_NOT_OWNED	0x80310018	You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption.
FVE_E_NOT_DATA_VOLUME	0x80310019	The operation attempted cannot be performed on an operating system drive.
FVE_E_AD_INSUFFICIENT_BUFFER	0x8031001A	The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again.
FVE_E_CONV_READ	0x8031001B	A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.
FVE_E_CONV_WRITE	0x8031001C	A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.
FVE_E_KEY_REQUIRED	0x8031001D	One or more BitLocker key protectors are required. You cannot delete the last key on this drive.
FVE_E_CLUSTERING_NOT_SUPPORTED	0x8031001E	Cluster configurations are not supported by BitLocker Drive Encryption.
FVE_E_VOLUME_BOUND_ALREADY	0x8031001F	The drive specified is already configured to be automatically unlocked on the current computer.
FVE_E_OS_NOT_PROTECTED	0x80310020	The operating system drive is not protected by BitLocker Drive Encryption.
FVE_E_PROTECTION_DISABLED	0x80310021	BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key.
FVE_E_RECOVERY_KEY_REQUIRED	0x80310022	The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive.
FVE_E_FOREIGN_VOLUME	0x80310023	BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive.
FVE_E_OVERLAPPED_UPDATE	0x80310024	The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again.
FVE_E_TPM_SRK_AUTH_NOT_ZERO	0x80310025	The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker.
FVE_E_FAILED_SECTOR_SIZE	0x80310026	The drive encryption algorithm cannot be used on this sector size.
FVE_E_FAILED_AUTHENTICATION	0x80310027	The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again.
FVE_E_NOT_OS_VOLUME	0x80310028	The drive specified is not the operating system drive.
FVE_E_AUTOUNLOCK_ENABLED	0x80310029	BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer.
FVE_E_WRONG_BOOTSECTOR	0x8031002A	The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector.
FVE_E_WRONG_SYSTEM_FS	0x8031002B	BitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker.
FVE_E_POLICY_PASSWORD_REQUIRED	0x8031002C	Group Policy settings require that a recovery password be specified before encrypting the drive.
FVE_E_CANNOT_SET_FVEK_ENCRYPTED	0x8031002D	The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker.
FVE_E_CANNOT_ENCRYPT_NO_KEY	0x8031002E	BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive.
FVE_E_BOOTABLE_CDDVD	0x80310030	BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker.
FVE_E_PROTECTOR_EXISTS	0x80310031	This key protector cannot be added. Only one key protector of this type is allowed for this drive.
FVE_E_RELATIVE_PATH	0x80310032	The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path.
FVE_E_PROTECTOR_NOT_FOUND	0x80310033	The specified key protector was not found on the drive. Try another key protector.
FVE_E_INVALID_KEY_FORMAT	0x80310034	The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive.
FVE_E_INVALID_PASSWORD_FORMAT	0x80310035	The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again.
FVE_E_FIPS_RNG_CHECK_FAILED	0x80310036	The random number generator check test failed.
FVE_E_FIPS_PREVENTS_RECOVERY_PASSWORD	0x80310037	The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent.
FVE_E_FIPS_PREVENTS_EXTERNAL_KEY_EXPORT	0x80310038	The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration.
FVE_E_NOT_DECRYPTED	0x80310039	The drive must be fully decrypted to complete this operation.
FVE_E_INVALID_PROTECTOR_TYPE	0x8031003A	The key protector specified cannot be used for this operation.
FVE_E_NO_PROTECTORS_TO_TEST	0x8031003B	No key protectors exist on the drive to perform the hardware test.
FVE_E_KEYFILE_NOT_FOUND	0x8031003C	The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions.
FVE_E_KEYFILE_INVALID	0x8031003D	The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again.
FVE_E_KEYFILE_NO_VMK	0x8031003E	The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again.
FVE_E_TPM_DISABLED	0x8031003F	The Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption.
FVE_E_NOT_ALLOWED_IN_SAFE_MODE	0x80310040	The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes.
FVE_E_TPM_INVALID_PCR	0x80310041	The Trusted Platform Module (TPM) was not able to unlock the drive because the system boot information has changed or a PIN was not provided correctly. Verify that the drive has not been tampered with and that changes to the system boot information were caused by a trusted source. After verifying that the drive is safe to access, use the BitLocker recovery console to unlock the drive and then suspend and resume BitLocker to update system boot information that BitLocker associates with this drive.
FVE_E_TPM_NO_VMK	0x80310042	The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM).
FVE_E_PIN_INVALID	0x80310043	The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN.
FVE_E_AUTH_INVALID_APPLICATION	0x80310044	A boot application has changed since BitLocker Drive Encryption was enabled.
FVE_E_AUTH_INVALID_CONFIG	0x80310045	The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled.
FVE_E_FIPS_DISABLE_PROTECTION_NOT_ALLOWED	0x80310046	The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information.
FVE_E_FS_NOT_EXTENDED	0x80310047	This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again.
FVE_E_FIRMWARE_TYPE_NOT_SUPPORTED	0x80310048	BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions.
FVE_E_NO_LICENSE	0x80310049	This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system.
FVE_E_NOT_ON_STACK	0x8031004A	BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.
FVE_E_FS_MOUNTED	0x8031004B	The drive cannot be locked when the drive is in use.
FVE_E_TOKEN_NOT_IMPERSONATED	0x8031004C	The access token associated with the current thread is not an impersonated token.
FVE_E_DRY_RUN_FAILED	0x8031004D	The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available.
FVE_E_REBOOT_REQUIRED	0x8031004E	You must restart your computer before continuing with BitLocker Drive Encryption.
FVE_E_DEBUGGER_ENABLED	0x8031004F	Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging.
FVE_E_RAW_ACCESS	0x80310050	No action was taken as BitLocker Drive Encryption is in raw access mode.
FVE_E_RAW_BLOCKED	0x80310051	BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use.
FVE_E_BCD_APPLICATIONS_PATH_INCORRECT	0x80310052	The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again.
FVE_E_NOT_ALLOWED_IN_VERSION	0x80310053	BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments.
FVE_E_NO_AUTOUNLOCK_MASTER_KEY	0x80310054	The auto-unlock master key was not available from the operating system drive.
FVE_E_MOR_FAILED	0x80310055	The system firmware failed to enable clearing of system memory when the computer was restarted.
FVE_E_HIDDEN_VOLUME	0x80310056	The hidden drive cannot be encrypted.
FVE_E_TRANSIENT_STATE	0x80310057	BitLocker encryption keys were ignored because the drive was in a transient state.
FVE_E_PUBKEY_NOT_ALLOWED	0x80310058	Public key based protectors are not allowed on this drive.
FVE_E_VOLUME_HANDLE_OPEN	0x80310059	BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing.
FVE_E_NO_FEATURE_LICENSE	0x8031005A	This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.
FVE_E_INVALID_STARTUP_OPTIONS	0x8031005B	The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information.
FVE_E_POLICY_RECOVERY_PASSWORD_NOT_ALLOWED	0x8031005C	Group policy settings do not permit the creation of a recovery password.
FVE_E_POLICY_RECOVERY_PASSWORD_REQUIRED	0x8031005D	Group policy settings require the creation of a recovery password.
FVE_E_POLICY_RECOVERY_KEY_NOT_ALLOWED	0x8031005E	Group policy settings do not permit the creation of a recovery key.
FVE_E_POLICY_RECOVERY_KEY_REQUIRED	0x8031005F	Group policy settings require the creation of a recovery key.
FVE_E_POLICY_STARTUP_PIN_NOT_ALLOWED	0x80310060	Group policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option.
FVE_E_POLICY_STARTUP_PIN_REQUIRED	0x80310061	Group policy settings require the use of a PIN at startup. Please choose this BitLocker startup option.
FVE_E_POLICY_STARTUP_KEY_NOT_ALLOWED	0x80310062	Group policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option.
FVE_E_POLICY_STARTUP_KEY_REQUIRED	0x80310063	Group policy settings require the use of a startup key. Please choose this BitLocker startup option.
FVE_E_POLICY_STARTUP_PIN_KEY_NOT_ALLOWED	0x80310064	Group policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option.
FVE_E_POLICY_STARTUP_PIN_KEY_REQUIRED	0x80310065	Group policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option.
FVE_E_POLICY_STARTUP_TPM_NOT_ALLOWED	0x80310066	Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option.
FVE_E_POLICY_STARTUP_TPM_REQUIRED	0x80310067	Group policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option.
FVE_E_POLICY_INVALID_PIN_LENGTH	0x80310068	The PIN provided does not meet minimum or maximum length requirements.
FVE_E_KEY_PROTECTOR_NOT_SUPPORTED	0x80310069	The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector.
FVE_E_POLICY_PASSPHRASE_NOT_ALLOWED	0x8031006A	Group policy settings do not permit the creation of a password.
FVE_E_POLICY_PASSPHRASE_REQUIRED	0x8031006B	Group policy settings require the creation of a password.
FVE_E_FIPS_PREVENTS_PASSPHRASE	0x8031006C	The group policy setting requiring FIPS compliance prevented the password from being generated or used. Please contact your domain administrator for more information.
FVE_E_OS_VOLUME_PASSPHRASE_NOT_ALLOWED	0x8031006D	A password cannot be added to the operating system drive.
FVE_E_INVALID_BITLOCKER_OID	0x8031006E	The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive.
FVE_E_VOLUME_TOO_SMALL	0x8031006F	The drive is too small to be protected using BitLocker Drive Encryption.
FVE_E_DV_NOT_SUPPORTED_ON_FS	0x80310070	The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives.
FVE_E_DV_NOT_ALLOWED_BY_GP	0x80310071	The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go.
FVE_E_POLICY_USER_CERTIFICATE_NOT_ALLOWED	0x80310072	Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption.
FVE_E_POLICY_USER_CERTIFICATE_REQUIRED	0x80310073	Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption.
FVE_E_POLICY_USER_CERT_MUST_BE_HW	0x80310074	Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption.
FVE_E_POLICY_USER_CONFIGURE_FDV_AUTOUNLOCK_NOT_ALLOWED	0x80310075	Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked.
FVE_E_POLICY_USER_CONFIGURE_RDV_AUTOUNLOCK_NOT_ALLOWED	0x80310076	Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked.
FVE_E_POLICY_USER_CONFIGURE_RDV_NOT_ALLOWED	0x80310077	Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives.
FVE_E_POLICY_USER_ENABLE_RDV_NOT_ALLOWED	0x80310078	Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker.
FVE_E_POLICY_USER_DISABLE_RDV_NOT_ALLOWED	0x80310079	Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker.
FVE_E_POLICY_INVALID_PASSPHRASE_LENGTH	0x80310080	Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization.
FVE_E_POLICY_PASSPHRASE_TOO_SIMPLE	0x80310081	Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols.
FVE_E_RECOVERY_PARTITION	0x80310082	This drive cannot be encrypted because it is reserved for Windows System Recovery Options.
FVE_E_POLICY_CONFLICT_FDV_RK_OFF_AUK_ON	0x80310083	BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.
FVE_E_POLICY_CONFLICT_RDV_RK_OFF_AUK_ON	0x80310084	BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occured, please ask your system administrator to resolve the settings conflict before enabling BitLocker.
FVE_E_NON_BITLOCKER_OID	0x80310085	The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker.
FVE_E_POLICY_PROHIBITS_SELFSIGNED	0x80310086	BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker.
FVE_E_POLICY_CONFLICT_RO_AND_STARTUP_KEY_REQUIRED	0x80310087	BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
FVE_E_CONV_RECOVERY_FAILED	0x80310088	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
FVE_E_VIRTUALIZED_SPACE_TOO_BIG	0x80310089	The requested virtualization size is too big.
FVE_E_POLICY_CONFLICT_OSV_RP_OFF_ADB_ON	0x80310090	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
FVE_E_POLICY_CONFLICT_FDV_RP_OFF_ADB_ON	0x80310091	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
FVE_E_POLICY_CONFLICT_RDV_RP_OFF_ADB_ON	0x80310092	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
FVE_E_NON_BITLOCKER_KU	0x80310093	The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement.
FVE_E_PRIVATEKEY_AUTH_FAILED	0x80310094	The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid.
FVE_E_REMOVAL_OF_DRA_FAILED	0x80310095	Removal of the data recovery agent certificate must be done using the Certificates snap-in.
FVE_E_OPERATION_NOT_SUPPORTED_ON_VISTA_VOLUME	0x80310096	This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command.
FVE_E_CANT_LOCK_AUTOUNLOCK_ENABLED_VOLUME	0x80310097	The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive.
FVE_E_FIPS_HASH_KDF_NOT_ALLOWED	0x80310098	The default Bitlocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments.
FVE_E_ENH_PIN_INVALID	0x80310099	The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals.
FVE_E_INVALID_PIN_CHARS	0x8031009A	The requested TPM PIN contains invalid characters.
FVE_E_INVALID_DATUM_TYPE	0x8031009B	The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.
FVE_E_EFI_ONLY	0x8031009C	The feature is only supported on EFI systems.
FVE_E_MULTIPLE_NKP_CERTS	0x8031009D	More than one Network Key Protector certificate has been found on the system.
FVE_E_REMOVAL_OF_NKP_FAILED	0x8031009E	Removal of the Network Key Protector certificate must be done using the Certificates snap-in.
FVE_E_INVALID_NKP_CERT	0x8031009F	An invalid certificate has been found in the Network Key Protector certificate store.
FVE_E_NO_EXISTING_PIN	0x803100A0	This drive isn't protected with a PIN.
FVE_E_PROTECTOR_CHANGE_PIN_MISMATCH	0x803100A1	Please enter the correct current PIN.
FVE_E_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED	0x803100A2	You must be logged on with an administrator account to change the PIN or password. Click the link to reset the PIN or password as an administrator.
FVE_E_PROTECTOR_CHANGE_MAX_PIN_CHANGE_ATTEMPTS_REACHED	0x803100A3	BitLocker has disabled PIN and password changes after too many failed requests. Click the link to reset the PIN or password as an administrator.
FVE_E_POLICY_PASSPHRASE_REQUIRES_ASCII	0x803100A4	Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ .
FVE_E_FULL_ENCRYPTION_NOT_ALLOWED_ON_TP_STORAGE	0x803100A5	BitLocker Drive Encryption only supports used space only encryption on thin provisioned storage.
FVE_E_WIPE_NOT_ALLOWED_ON_TP_STORAGE	0x803100A6	BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.
FVE_E_KEY_LENGTH_NOT_SUPPORTED_BY_EDRIVE	0x803100A7	The required authentication key length is not supported by the drive.
FVE_E_NO_EXISTING_PASSPHRASE	0x803100A8	This drive isn't protected with a password.
FVE_E_PROTECTOR_CHANGE_PASSPHRASE_MISMATCH	0x803100A9	Please enter the correct current password.
FVE_E_PASSPHRASE_TOO_LONG	0x803100AA	The password cannot exceed 256 characters.
FVE_E_NO_PASSPHRASE_WITH_TPM	0x803100AB	A password key protector cannot be added because a TPM protector exists on the drive.
FVE_E_NO_TPM_WITH_PASSPHRASE	0x803100AC	A TPM key protector cannot be added because a password protector exists on the drive.
FVE_E_NOT_ALLOWED_ON_CSV_STACK	0x803100AD	This command can only be performed from the coordinator node for the specified CSV volume.
FVE_E_NOT_ALLOWED_ON_CLUSTER	0x803100AE	This command cannot be performed on a volume when it is part of a cluster.
FVE_E_EDRIVE_NO_FAILOVER_TO_SW	0x803100AF	BitLocker did not revert to using BitLocker software encryption due to group policy configuration.
FVE_E_EDRIVE_BAND_IN_USE	0x803100B0	The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.
FVE_E_EDRIVE_DISALLOWED_BY_GP	0x803100B1	Group Policy settings do not allow the use of hardware-based encryption.
FVE_E_EDRIVE_INCOMPATIBLE_VOLUME	0x803100B2	The drive specified does not support hardware-based encryption.
FVE_E_NOT_ALLOWED_TO_UPGRADE_WHILE_CONVERTING	0x803100B3	BitLocker cannot be upgraded during disk encryption or decryption.
FVE_E_EDRIVE_DV_NOT_SUPPORTED	0x803100B4	Discovery Volumes are not supported for volumes using hardware encryption.
FVE_E_NO_PREBOOT_KEYBOARD_DETECTED	0x803100B5	No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume.
FVE_E_NO_PREBOOT_KEYBOARD_OR_WINRE_DETECTED	0x803100B6	No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume.
FVE_E_POLICY_REQUIRES_STARTUP_PIN_ON_TOUCH_DEVICE	0x803100B7	Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume.
FVE_E_POLICY_REQUIRES_RECOVERY_PASSWORD_ON_TOUCH_DEVICE	0x803100B8	Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume.
FVE_E_WIPE_CANCEL_NOT_APPLICABLE	0x803100B9	Wipe of free space is not currently taking place.
FVE_E_SECUREBOOT_DISABLED	0x803100BA	BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled.
FVE_E_SECUREBOOT_CONFIGURATION_INVALID	0x803100BB	BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker.
FVE_E_EDRIVE_DRY_RUN_FAILED	0x803100BC	Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.
FVE_E_SHADOW_COPY_PRESENT	0x803100BD	BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume.
FVE_E_POLICY_INVALID_ENHANCED_BCD_SETTINGS	0x803100BE	BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker.
FVE_E_EDRIVE_INCOMPATIBLE_FIRMWARE	0x803100BF	This PC's firmware is not capable of supporting hardware encryption.
FVE_E_PROTECTOR_CHANGE_MAX_PASSPHRASE_CHANGE_ATTEMPTS_REACHED	0x803100C0	BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator.
FVE_E_PASSPHRASE_PROTECTOR_CHANGE_BY_STD_USER_DISALLOWED	0x803100C1	You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator.
FVE_E_LIVEID_ACCOUNT_SUSPENDED	0x803100C2	BitLocker cannot save the recovery password because the specified Microsoft account is Suspended.
FVE_E_LIVEID_ACCOUNT_BLOCKED	0x803100C3	BitLocker cannot save the recovery password because the specified MIcrosoft account is Blocked.
FVE_E_NOT_PROVISIONED_ON_ALL_VOLUMES	0x803100C4	This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy.
FVE_E_DE_FIXED_DATA_NOT_SUPPORTED	0x803100C5	This PC cannot support device encryption because unencrypted fixed data volumes are present.
FVE_E_DE_HARDWARE_NOT_COMPLIANT	0x803100C6	This PC does not meet the hardware requirements to support device encryption.
FVE_E_DE_WINRE_NOT_CONFIGURED	0x803100C7	This PC cannot support device encryption because WinRE is not properly configured.
FVE_E_DE_PROTECTION_SUSPENDED	0x803100C8	Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot.
FVE_E_DE_OS_VOLUME_NOT_PROTECTED	0x803100C9	This PC is not provisioned to support device encryption.
FVE_E_DE_DEVICE_LOCKEDOUT	0x803100CA	Device Lock has been triggered due to too many incorrect password attempts.
FVE_E_DE_PROTECTION_NOT_YET_ENABLED	0x803100CB	Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information.
FVE_E_INVALID_PIN_CHARS_DETAILED	0x803100CC	Your PIN can only contain numbers from 0 to 9.
FVE_E_DEVICE_LOCKOUT_COUNTER_UNAVAILABLE	0x803100CD	BitLocker cannot use hardware replay protection because no counter is available on your PC.
FVE_E_DEVICELOCKOUT_COUNTER_MISMATCH	0x803100CE	Device Lockout state validation failed due to counter mismatch.
FVE_E_BUFFER_TOO_LARGE	0x803100CF	The input buffer is too large.
536 entries

Article text from the Win32 documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.