COM Error Codes (FWP, WS, NDIS, HyperV)
【外部リンク】
https://msdn.microsoft.com/en-us/library/windows/desktop/dd542649(v=vs.85).aspx
Constant/value Description
FWP_E_CALLOUT_NOT_FOUND
0x80320001
The callout does not exist.
FWP_E_CONDITION_NOT_FOUND
0x80320002
The filter condition does not exist.
FWP_E_FILTER_NOT_FOUND
0x80320003
The filter does not exist.
FWP_E_LAYER_NOT_FOUND
0x80320004
The layer does not exist.
FWP_E_PROVIDER_NOT_FOUND
0x80320005
The provider does not exist.
FWP_E_PROVIDER_CONTEXT_NOT_FOUND
0x80320006
The provider context does not exist.
FWP_E_SUBLAYER_NOT_FOUND
0x80320007
The sublayer does not exist.
FWP_E_NOT_FOUND
0x80320008
The object does not exist.
FWP_E_ALREADY_EXISTS
0x80320009
An object with that GUID or LUID already exists.
FWP_E_IN_USE
0x8032000A
The object is referenced by other objects so cannot be deleted.
FWP_E_DYNAMIC_SESSION_IN_PROGRESS
0x8032000B
The call is not allowed from within a dynamic session.
FWP_E_WRONG_SESSION
0x8032000C
The call was made from the wrong session so cannot be completed.
FWP_E_NO_TXN_IN_PROGRESS
0x8032000D
The call must be made from within an explicit transaction.
FWP_E_TXN_IN_PROGRESS
0x8032000E
The call is not allowed from within an explicit transaction.
FWP_E_TXN_ABORTED
0x8032000F
The explicit transaction has been forcibly canceled.
FWP_E_SESSION_ABORTED
0x80320010
The session has been canceled.
FWP_E_INCOMPATIBLE_TXN
0x80320011
The call is not allowed from within a read-only transaction.
FWP_E_TIMEOUT
0x80320012
The call timed out while waiting to acquire the transaction lock.
FWP_E_NET_EVENTS_DISABLED
0x80320013
Collection of network diagnostic events is disabled.
FWP_E_INCOMPATIBLE_LAYER
0x80320014
The operation is not supported by the specified layer.
FWP_E_KM_CLIENTS_ONLY
0x80320015
The call is allowed for kernel-mode callers only.
FWP_E_LIFETIME_MISMATCH
0x80320016
The call tried to associate two objects with incompatible lifetimes.
FWP_E_BUILTIN_OBJECT
0x80320017
The object is built in so cannot be deleted.
FWP_E_TOO_MANY_CALLOUTS
0x80320018
The maximum number of callouts has been reached.
FWP_E_NOTIFICATION_DROPPED
0x80320019
A notification could not be delivered because a message queue is at its maximum capacity.
FWP_E_TRAFFIC_MISMATCH
0x8032001A
The traffic parameters do not match those for the security association context.
FWP_E_INCOMPATIBLE_SA_STATE
0x8032001B
The call is not allowed for the current security association state.
FWP_E_NULL_POINTER
0x8032001C
A required pointer is null.
FWP_E_INVALID_ENUMERATOR
0x8032001D
An enumerator is not valid.
FWP_E_INVALID_FLAGS
0x8032001E
The flags field contains an invalid value.
FWP_E_INVALID_NET_MASK
0x8032001F
A network mask is not valid.
FWP_E_INVALID_RANGE
0x80320020
An FWP_RANGE is not valid.
FWP_E_INVALID_INTERVAL
0x80320021
The time interval is not valid.
FWP_E_ZERO_LENGTH_ARRAY
0x80320022
An array that must contain at least one element is zero length.
FWP_E_NULL_DISPLAY_NAME
0x80320023
The displayData.name field cannot be null.
FWP_E_INVALID_ACTION_TYPE
0x80320024
The action type is not one of the allowed action types for a filter.
FWP_E_INVALID_WEIGHT
0x80320025
The filter weight is not valid.
FWP_E_MATCH_TYPE_MISMATCH
0x80320026
A filter condition contains a match type that is not compatible with the operands.
FWP_E_TYPE_MISMATCH
0x80320027
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type.
FWP_E_OUT_OF_BOUNDS
0x80320028
An integer value is outside the allowed range.
FWP_E_RESERVED
0x80320029
A reserved field is nonzero.
FWP_E_DUPLICATE_CONDITION
0x8032002A
A filter cannot contain multiple conditions operating on a single field.
FWP_E_DUPLICATE_KEYMOD
0x8032002B
A policy cannot contain the same keying module more than once.
FWP_E_ACTION_INCOMPATIBLE_WITH_LAYER
0x8032002C
The action type is not compatible with the layer.
FWP_E_ACTION_INCOMPATIBLE_WITH_SUBLAYER
0x8032002D
The action type is not compatible with the sublayer.
FWP_E_CONTEXT_INCOMPATIBLE_WITH_LAYER
0x8032002E
The raw context or the provider context is not compatible with the layer.
FWP_E_CONTEXT_INCOMPATIBLE_WITH_CALLOUT
0x8032002F
The raw context or the provider context is not compatible with the callout.
FWP_E_INCOMPATIBLE_AUTH_METHOD
0x80320030
The authentication method is not compatible with the policy type.
FWP_E_INCOMPATIBLE_DH_GROUP
0x80320031
The Diffie-Hellman group is not compatible with the policy type.
FWP_E_EM_NOT_SUPPORTED
0x80320032
An IKE policy cannot contain an Extended Mode policy.
FWP_E_NEVER_MATCH
0x80320033
The enumeration template or subscription will never match any objects.
FWP_E_PROVIDER_CONTEXT_MISMATCH
0x80320034
The provider context is of the wrong type.
FWP_E_INVALID_PARAMETER
0x80320035
The parameter is incorrect.
FWP_E_TOO_MANY_SUBLAYERS
0x80320036
The maximum number of sublayers has been reached.
FWP_E_CALLOUT_NOTIFICATION_FAILED
0x80320037
The notification function for a callout returned an error.
FWP_E_INVALID_AUTH_TRANSFORM
0x80320038
The IPsec authentication transform is not valid.
FWP_E_INVALID_CIPHER_TRANSFORM
0x80320039
The IPsec cipher transform is not valid.
FWP_E_INCOMPATIBLE_CIPHER_TRANSFORM
0x8032003A
The IPsec cipher transform is not compatible with the policy.
FWP_E_INVALID_TRANSFORM_COMBINATION
0x8032003B
The combination of IPsec transform types is not valid.
FWP_E_DUPLICATE_AUTH_METHOD
0x8032003C
A policy cannot contain the same auth method more than once.
FWP_E_INVALID_TUNNEL_ENDPOINT
0x8032003D
A tunnel endpoint configuration is invalid.
FWP_E_L2_DRIVER_NOT_READY
0x8032003E
The WFP MAC Layers are not ready.
FWP_E_KEY_DICTATOR_ALREADY_REGISTERED
0x8032003F
A key manager capable of key dictation is already registered
FWP_E_KEY_DICTATION_INVALID_KEYING_MATERIAL
0x80320040
A key manager dictated invalid keys
FWP_E_CONNECTIONS_DISABLED
0x80320041
The BFE IPsec Connection Tracking is disabled.
FWP_E_INVALID_DNS_NAME
0x80320042
The DNS name is invalid.
FWP_E_STILL_ON
0x80320043
The engine option is still enabled due to other configuration settings.
FWP_E_IKEEXT_NOT_RUNNING
0x80320044
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine.
FWP_E_DROP_NOICMP
0x80320104
The packet should be dropped, no ICMP should be sent.
WS_S_ASYNC
0x003D0000
The function call is completing asynchronously.
WS_S_END
0x003D0001
There are no more messages available on the channel.
WS_E_INVALID_FORMAT
0x803D0000
The input data was not in the expected format or did not have the expected value.
WS_E_OBJECT_FAULTED
0x803D0001
The operation could not be completed because the object is in a faulted state due to a previous error.
WS_E_NUMERIC_OVERFLOW
0x803D0002
The operation could not be completed because it would lead to numeric overflow.
WS_E_INVALID_OPERATION
0x803D0003
The operation is not allowed due to the current state of the object.
WS_E_OPERATION_ABORTED
0x803D0004
The operation was aborted.
WS_E_ENDPOINT_ACCESS_DENIED
0x803D0005
Access was denied by the remote endpoint.
WS_E_OPERATION_TIMED_OUT
0x803D0006
The operation did not complete within the time allotted.
WS_E_OPERATION_ABANDONED
0x803D0007
The operation was abandoned.
WS_E_QUOTA_EXCEEDED
0x803D0008
A quota was exceeded.
WS_E_NO_TRANSLATION_AVAILABLE
0x803D0009
The information was not available in the specified language.
WS_E_SECURITY_VERIFICATION_FAILURE
0x803D000A
Security verification was not successful for the received data.
WS_E_ADDRESS_IN_USE
0x803D000B
The address is already being used.
WS_E_ADDRESS_NOT_AVAILABLE
0x803D000C
The address is not valid for this context.
WS_E_ENDPOINT_NOT_FOUND
0x803D000D
The remote endpoint does not exist or could not be located.
WS_E_ENDPOINT_NOT_AVAILABLE
0x803D000E
The remote endpoint is not currently in service at this location.
WS_E_ENDPOINT_FAILURE
0x803D000F
The remote endpoint could not process the request.
WS_E_ENDPOINT_UNREACHABLE
0x803D0010
The remote endpoint was not reachable.
WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
0x803D0011
The operation was not supported by the remote endpoint.
WS_E_ENDPOINT_TOO_BUSY
0x803D0012
The remote endpoint is unable to process the request due to being overloaded.
WS_E_ENDPOINT_FAULT_RECEIVED
0x803D0013
A message containing a fault was received from the remote endpoint.
WS_E_ENDPOINT_DISCONNECTED
0x803D0014
The connection with the remote endpoint was terminated.
WS_E_PROXY_FAILURE
0x803D0015
The HTTP proxy server could not process the request.
WS_E_PROXY_ACCESS_DENIED
0x803D0016
Access was denied by the HTTP proxy server.
WS_E_NOT_SUPPORTED
0x803D0017
The requested feature is not available on this platform.
WS_E_PROXY_REQUIRES_BASIC_AUTH
0x803D0018
The HTTP proxy server requires HTTP authentication scheme 'basic'.
WS_E_PROXY_REQUIRES_DIGEST_AUTH
0x803D0019
The HTTP proxy server requires HTTP authentication scheme 'digest'.
WS_E_PROXY_REQUIRES_NTLM_AUTH
0x803D001A
The HTTP proxy server requires HTTP authentication scheme 'NTLM'.
WS_E_PROXY_REQUIRES_NEGOTIATE_AUTH
0x803D001B
The HTTP proxy server requires HTTP authentication scheme 'negotiate'.
WS_E_SERVER_REQUIRES_BASIC_AUTH
0x803D001C
The remote endpoint requires HTTP authentication scheme 'basic'.
WS_E_SERVER_REQUIRES_DIGEST_AUTH
0x803D001D
The remote endpoint requires HTTP authentication scheme 'digest'.
WS_E_SERVER_REQUIRES_NTLM_AUTH
0x803D001E
The remote endpoint requires HTTP authentication scheme 'NTLM'.
WS_E_SERVER_REQUIRES_NEGOTIATE_AUTH
0x803D001F
The remote endpoint requires HTTP authentication scheme 'negotiate'.
WS_E_INVALID_ENDPOINT_URL
0x803D0020
The endpoint address URL is invalid.
WS_E_OTHER
0x803D0021
Unrecognized error occurred in the Windows Web Services framework.
WS_E_SECURITY_TOKEN_EXPIRED
0x803D0022
A security token was rejected by the server because it has expired.
WS_E_SECURITY_SYSTEM_FAILURE
0x803D0023
A security operation failed in the Windows Web Services framework.
ERROR_NDIS_INTERFACE_CLOSING
0x80340002
The binding to the network interface is being closed.
ERROR_NDIS_BAD_VERSION
0x80340004
An invalid version was specified.
ERROR_NDIS_BAD_CHARACTERISTICS
0x80340005
An invalid characteristics table was used.
ERROR_NDIS_ADAPTER_NOT_FOUND
0x80340006
Failed to find the network interface or network interface is not ready.
ERROR_NDIS_OPEN_FAILED
0x80340007
Failed to open the network interface.
ERROR_NDIS_DEVICE_FAILED
0x80340008
Network interface has encountered an internal unrecoverable failure.
ERROR_NDIS_MULTICAST_FULL
0x80340009
The multicast list on the network interface is full.
ERROR_NDIS_MULTICAST_EXISTS
0x8034000A
An attempt was made to add a duplicate multicast address to the list.
ERROR_NDIS_MULTICAST_NOT_FOUND
0x8034000B
At attempt was made to remove a multicast address that was never added.
ERROR_NDIS_REQUEST_ABORTED
0x8034000C
Netowork interface aborted the request.
ERROR_NDIS_RESET_IN_PROGRESS
0x8034000D
Network interface cannot process the request because it is being reset.
ERROR_NDIS_NOT_SUPPORTED
0x803400BB
Netword interface does not support this request.
ERROR_NDIS_INVALID_PACKET
0x8034000F
An attempt was made to send an invalid packet on a network interface.
ERROR_NDIS_ADAPTER_NOT_READY
0x80340011
Network interface is not ready to complete this operation.
ERROR_NDIS_INVALID_LENGTH
0x80340014
The length of the buffer submitted for this operation is not valid.
ERROR_NDIS_INVALID_DATA
0x80340015
The data used for this operation is not valid.
ERROR_NDIS_BUFFER_TOO_SHORT
0x80340016
The length of buffer submitted for this operation is too small.
ERROR_NDIS_INVALID_OID
0x80340017
Network interface does not support this OID (Object Identifier)
ERROR_NDIS_ADAPTER_REMOVED
0x80340018
The network interface has been removed.
ERROR_NDIS_UNSUPPORTED_MEDIA
0x80340019
Network interface does not support this media type.
ERROR_NDIS_GROUP_ADDRESS_IN_USE
0x8034001A
An attempt was made to remove a token ring group address that is in use by other components.
ERROR_NDIS_FILE_NOT_FOUND
0x8034001B
An attempt was made to map a file that cannot be found.
ERROR_NDIS_ERROR_READING_FILE
0x8034001C
An error occurred while NDIS tried to map the file.
ERROR_NDIS_ALREADY_MAPPED
0x8034001D
An attempt was made to map a file that is alreay mapped.
ERROR_NDIS_RESOURCE_CONFLICT
0x8034001E
An attempt to allocate a hardware resource failed because the resource is used by another component.
ERROR_NDIS_MEDIA_DISCONNECTED
0x8034001F
The I/O operation failed because network media is disconnected or wireless access point is out of range.
ERROR_NDIS_INVALID_ADDRESS
0x80340022
The network address used in the request is invalid.
ERROR_NDIS_INVALID_DEVICE_REQUEST
0x80340010
The specified request is not a valid operation for the target device.
ERROR_NDIS_PAUSED
0x8034002A
The offload operation on the network interface has been paused.
ERROR_NDIS_INTERFACE_NOT_FOUND
0x8034002B
Network interface was not found.
ERROR_NDIS_UNSUPPORTED_REVISION
0x8034002C
The revision number specified in the structure is not supported.
ERROR_NDIS_INVALID_PORT
0x8034002D
The specified port does not exist on this network interface.
ERROR_NDIS_INVALID_PORT_STATE
0x8034002E
The current state of the specified port on this network interface does not support the requested operation.
ERROR_NDIS_LOW_POWER_STATE
0x8034002F
The miniport adapter is in low power state.
ERROR_NDIS_REINIT_REQUIRED
0x80340030
This operation requires the miniport adapter to be reinitialized.
ERROR_NDIS_DOT11_AUTO_CONFIG_ENABLED
0x80342000
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation.
ERROR_NDIS_DOT11_MEDIA_IN_USE
0x80342001
The wireless local area network interface is busy and cannot perform the requested operation.
ERROR_NDIS_DOT11_POWER_STATE_INVALID
0x80342002
The wireless local area network interface is powered down and doesn't support the requested operation.
ERROR_NDIS_PM_WOL_PATTERN_LIST_FULL
0x80342003
The list of wake on LAN patterns is full.
ERROR_NDIS_PM_PROTOCOL_OFFLOAD_LIST_FULL
0x80342004
The list of low power protocol offloads is full.
ERROR_NDIS_INDICATION_REQUIRED
0x00340001
The request will be completed later by NDIS status indication.
ERROR_NDIS_OFFLOAD_POLICY
0xC034100F
The TCP connection is not offloadable because of a local policy setting.
ERROR_NDIS_OFFLOAD_CONNECTION_REJECTED
0xC0341012
The TCP connection is not offloadable by the Chimney Offload target.
ERROR_NDIS_OFFLOAD_PATH_REJECTED
0xC0341013
The IP Path object is not in an offloadable state.
ERROR_HV_INVALID_HYPERCALL_CODE
0xC0350002
The hypervisor does not support the operation because the specified hypercall code is not supported.
ERROR_HV_INVALID_HYPERCALL_INPUT
0xC0350003
The hypervisor does not support the operation because the encoding for the hypercall input register is not supported.
ERROR_HV_INVALID_ALIGNMENT
0xC0350004
The hypervisor could not perform the operation because a parameter has an invalid alignment.
ERROR_HV_INVALID_PARAMETER
0xC0350005
The hypervisor could not perform the operation because an invalid parameter was specified.
ERROR_HV_ACCESS_DENIED
0xC0350006
Access to the specified object was denied.
ERROR_HV_INVALID_PARTITION_STATE
0xC0350007
The hypervisor could not perform the operation because the partition is entering or in an invalid state.
ERROR_HV_OPERATION_DENIED
0xC0350008
The operation is not allowed in the current state.
ERROR_HV_UNKNOWN_PROPERTY
0xC0350009
The hypervisor does not recognize the specified partition property.
ERROR_HV_PROPERTY_VALUE_OUT_OF_RANGE
0xC035000A
The specified value of a partition property is out of range or violates an invariant.
ERROR_HV_INSUFFICIENT_MEMORY
0xC035000B
There is not enough memory in the hypervisor pool to complete the operation.
ERROR_HV_PARTITION_TOO_DEEP
0xC035000C
The maximum partition depth has been exceeded for the partition hierarchy.
ERROR_HV_INVALID_PARTITION_ID
0xC035000D
A partition with the specified partition Id does not exist.
ERROR_HV_INVALID_VP_INDEX
0xC035000E
The hypervisor could not perform the operation because the specified VP index is invalid.
ERROR_HV_INVALID_PORT_ID
0xC0350011
The hypervisor could not perform the operation because the specified port identifier is invalid.
ERROR_HV_INVALID_CONNECTION_ID
0xC0350012
The hypervisor could not perform the operation because the specified connection identifier is invalid.
ERROR_HV_INSUFFICIENT_BUFFERS
0xC0350013
Not enough buffers were supplied to send a message.
ERROR_HV_NOT_ACKNOWLEDGED
0xC0350014
The previous virtual interrupt has not been acknowledged.
ERROR_HV_ACKNOWLEDGED
0xC0350016
The previous virtual interrupt has already been acknowledged.
ERROR_HV_INVALID_SAVE_RESTORE_STATE
0xC0350017
The indicated partition is not in a valid state for saving or restoring.
ERROR_HV_INVALID_SYNIC_STATE
0xC0350018
The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled.
ERROR_HV_OBJECT_IN_USE
0xC0350019
The hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation.
ERROR_HV_INVALID_PROXIMITY_DOMAIN_INFO
0xC035001A
The proximity domain information is invalid.
ERROR_HV_NO_DATA
0xC035001B
An attempt to retrieve debugging data failed because none was available.
ERROR_HV_INACTIVE
0xC035001C
The physical connection being used for debuggging has not recorded any receive activity since the last operation.
ERROR_HV_NO_RESOURCES
0xC035001D
There are not enough resources to complete the operation.
ERROR_HV_FEATURE_UNAVAILABLE
0xC035001E
A hypervisor feature is not available to the user.
ERROR_HV_INSUFFICIENT_DEVICE_DOMAINS
0xC0350038
The maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition.
ERROR_HV_INVALID_LP_INDEX
0xC0350041
The hypervisor could not perform the operation because the specified LP index is invalid.
ERROR_HV_NOT_PRESENT
0xC0351000
No hypervisor is present on this system.
ERROR_VID_DUPLICATE_HANDLER
0xC0370001
The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_TOO_MANY_HANDLERS
0xC0370002
The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_QUEUE_FULL
0xC0370003
The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_HANDLER_NOT_PRESENT
0xC0370004
No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_INVALID_OBJECT_NAME
0xC0370005
The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_PARTITION_NAME_TOO_LONG
0xC0370006
The partition name of the virtualization infrastructure driver exceeds the maximum.
ERROR_VID_MESSAGE_QUEUE_NAME_TOO_LONG
0xC0370007
The message queue name of the virtualization infrastructure driver exceeds the maximum.
ERROR_VID_PARTITION_ALREADY_EXISTS
0xC0370008
Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.
ERROR_VID_PARTITION_DOES_NOT_EXIST
0xC0370009
The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_PARTITION_NAME_NOT_FOUND
0xC037000A
The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MESSAGE_QUEUE_ALREADY_EXISTS
0xC037000B
A message queue with the same name already exists for the virtualization infrastructure driver.
ERROR_VID_EXCEEDED_MBP_ENTRY_MAP_LIMIT
0xC037000C
The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MB_STILL_REFERENCED
0xC037000D
The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.
ERROR_VID_CHILD_GPA_PAGE_SET_CORRUPTED
0xC037000E
Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_INVALID_NUMA_SETTINGS
0xC037000F
The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration.
ERROR_VID_INVALID_NUMA_NODE_INDEX
0xC0370010
The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.
ERROR_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED
0xC0370011
The memory block for the virtualization infrastructure driver is already associated with a message queue.
ERROR_VID_INVALID_MEMORY_BLOCK_HANDLE
0xC0370012
The handle is not a valid memory block handle for the virtualization infrastructure driver.
ERROR_VID_PAGE_RANGE_OVERFLOW
0xC0370013
The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_INVALID_MESSAGE_QUEUE_HANDLE
0xC0370014
The handle is not a valid message queue handle for the virtualization infrastructure driver.
ERROR_VID_INVALID_GPA_RANGE_HANDLE
0xC0370015
The handle is not a valid page range handle for the virtualization infrastructure driver.
ERROR_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE
0xC0370016
Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.
ERROR_VID_MEMORY_BLOCK_LOCK_COUNT_EXCEEDED
0xC0370017
The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_INVALID_PPM_HANDLE
0xC0370018
The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.
ERROR_VID_MBPS_ARE_LOCKED
0xC0370019
Notifications cannot be created on the memory block because it is use.
ERROR_VID_MESSAGE_QUEUE_CLOSED
0xC037001A
The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED
0xC037001B
Cannot add a virtual processor to the partition because the maximum has been reached.
ERROR_VID_STOP_PENDING
0xC037001C
Cannot stop the virtual processor immediately because of a pending intercept.
ERROR_VID_INVALID_PROCESSOR_STATE
0xC037001D
Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_EXCEEDED_KM_CONTEXT_COUNT_LIMIT
0xC037001E
The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_KM_INTERFACE_ALREADY_INITIALIZED
0xC037001F
This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MB_PROPERTY_ALREADY_SET_RESET
0xC0370020
Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MMIO_RANGE_DESTROYED
0xC0370021
The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_INVALID_CHILD_GPA_PAGE_SET
0xC0370022
The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_RESERVE_PAGE_SET_IS_BEING_USED
0xC0370023
Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_RESERVE_PAGE_SET_TOO_SMALL
0xC0370024
The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MBP_ALREADY_LOCKED_USING_RESERVED_PAGE
0xC0370025
Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_MBP_COUNT_EXCEEDED_LIMIT
0xC0370026
Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
ERROR_VID_SAVED_STATE_CORRUPT
0xC0370027
Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine.
ERROR_VID_SAVED_STATE_UNRECOGNIZED_ITEM
0xC0370028
Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine.
ERROR_VID_SAVED_STATE_INCOMPATIBLE
0xC0370029
Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.
ERROR_VID_REMOTE_NODE_PARENT_GPA_PAGES_USED
0x80370001
A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration.
20170624
COM Error Codes (TPM, PLA, FVE)
COM Error Codes (TPM, PLA, FVE)
【外部リンク】
https://msdn.microsoft.com/en-us/library/windows/desktop/dd542648(v=vs.85).aspx
Constant/value 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 a 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.
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.
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.
【外部リンク】
https://msdn.microsoft.com/en-us/library/windows/desktop/dd542648(v=vs.85).aspx
Constant/value 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 a 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.
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.
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.
COM Error Codes (COMADMIN, FILTER, GRAPHICS)
COM Error Codes (COMADMIN, FILTER, GRAPHICS)
【外部リンク】
https://msdn.microsoft.com/en-us/library/windows/desktop/dd542647(v=vs.85).aspx
Constant/value Description
COMADMIN_E_OBJECTERRORS
0x80110401
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail
COMADMIN_E_OBJECTINVALID
0x80110402
One or more of the object's properties are missing or invalid
COMADMIN_E_KEYMISSING
0x80110403
The object was not found in the catalog
COMADMIN_E_ALREADYINSTALLED
0x80110404
The object is already registered
COMADMIN_E_APP_FILE_WRITEFAIL
0x80110407
Error occurred writing to the application file
COMADMIN_E_APP_FILE_READFAIL
0x80110408
Error occurred reading the application file
COMADMIN_E_APP_FILE_VERSION
0x80110409
Invalid version number in application file
COMADMIN_E_BADPATH
0x8011040A
The file path is invalid
COMADMIN_E_APPLICATIONEXISTS
0x8011040B
The application is already installed
COMADMIN_E_ROLEEXISTS
0x8011040C
The role already exists
COMADMIN_E_CANTCOPYFILE
0x8011040D
An error occurred copying the file
COMADMIN_E_NOUSER
0x8011040F
One or more users are not valid
COMADMIN_E_INVALIDUSERIDS
0x80110410
One or more users in the application file are not valid
COMADMIN_E_NOREGISTRYCLSID
0x80110411
The component's CLSID is missing or corrupt
COMADMIN_E_BADREGISTRYPROGID
0x80110412
The component's progID is missing or corrupt
COMADMIN_E_AUTHENTICATIONLEVEL
0x80110413
Unable to set required authentication level for update request
COMADMIN_E_USERPASSWDNOTVALID
0x80110414
The identity or password set on the application is not valid
COMADMIN_E_CLSIDORIIDMISMATCH
0x80110418
Application file CLSIDs or IIDs do not match corresponding DLLs
COMADMIN_E_REMOTEINTERFACE
0x80110419
Interface information is either missing or changed
COMADMIN_E_DLLREGISTERSERVER
0x8011041A
DllRegisterServer failed on component install
COMADMIN_E_NOSERVERSHARE
0x8011041B
No server file share available
COMADMIN_E_DLLLOADFAILED
0x8011041D
DLL could not be loaded
COMADMIN_E_BADREGISTRYLIBID
0x8011041E
The registered TypeLib ID is not valid
COMADMIN_E_APPDIRNOTFOUND
0x8011041F
Application install directory not found
COMADMIN_E_REGISTRARFAILED
0x80110423
Errors occurred while in the component registrar
COMADMIN_E_COMPFILE_DOESNOTEXIST
0x80110424
The file does not exist
COMADMIN_E_COMPFILE_LOADDLLFAIL
0x80110425
The DLL could not be loaded
COMADMIN_E_COMPFILE_GETCLASSOBJ
0x80110426
GetClassObject failed in the DLL
COMADMIN_E_COMPFILE_CLASSNOTAVAIL
0x80110427
The DLL does not support the components listed in the TypeLib
COMADMIN_E_COMPFILE_BADTLB
0x80110428
The TypeLib could not be loaded
COMADMIN_E_COMPFILE_NOTINSTALLABLE
0x80110429
The file does not contain components or component information
COMADMIN_E_NOTCHANGEABLE
0x8011042A
Changes to this object and its sub-objects have been disabled
COMADMIN_E_NOTDELETEABLE
0x8011042B
The delete function has been disabled for this object
COMADMIN_E_SESSION
0x8011042C
The server catalog version is not supported
COMADMIN_E_COMP_MOVE_LOCKED
0x8011042D
The component move was disallowed, because the source or destination application is either a system application or currently locked against changes
COMADMIN_E_COMP_MOVE_BAD_DEST
0x8011042E
The component move failed because the destination application no longer exists
COMADMIN_E_REGISTERTLB
0x80110430
The system was unable to register the TypeLib
COMADMIN_E_SYSTEMAPP
0x80110433
This operation cannot be performed on the system application
COMADMIN_E_COMPFILE_NOREGISTRAR
0x80110434
The component registrar referenced in this file is not available
COMADMIN_E_COREQCOMPINSTALLED
0x80110435
A component in the same DLL is already installed
COMADMIN_E_SERVICENOTINSTALLED
0x80110436
The service is not installed
COMADMIN_E_PROPERTYSAVEFAILED
0x80110437
One or more property settings are either invalid or in conflict with each other
COMADMIN_E_OBJECTEXISTS
0x80110438
The object you are attempting to add or rename already exists
COMADMIN_E_COMPONENTEXISTS
0x80110439
The component already exists
COMADMIN_E_REGFILE_CORRUPT
0x8011043B
The registration file is corrupt
COMADMIN_E_PROPERTY_OVERFLOW
0x8011043C
The property value is too large
COMADMIN_E_NOTINREGISTRY
0x8011043E
Object was not found in registry
COMADMIN_E_OBJECTNOTPOOLABLE
0x8011043F
This object is not poolable
COMADMIN_E_APPLID_MATCHES_CLSID
0x80110446
A CLSID with the same GUID as the new application ID is already installed on this machine
COMADMIN_E_ROLE_DOES_NOT_EXIST
0x80110447
A role assigned to a component, interface, or method did not exist in the application
COMADMIN_E_START_APP_NEEDS_COMPONENTS
0x80110448
You must have components in an application in order to start the application
COMADMIN_E_REQUIRES_DIFFERENT_PLATFORM
0x80110449
This operation is not enabled on this platform
COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY
0x8011044A
Application Proxy is not exportable
COMADMIN_E_CAN_NOT_START_APP
0x8011044B
Failed to start application because it is either a library application or an application proxy
COMADMIN_E_CAN_NOT_EXPORT_SYS_APP
0x8011044C
System application is not exportable
COMADMIN_E_CANT_SUBSCRIBE_TO_COMPONENT
0x8011044D
Cannot subscribe to this component (the component may have been imported)
COMADMIN_E_EVENTCLASS_CANT_BE_SUBSCRIBER
0x8011044E
An event class cannot also be a subscriber component
COMADMIN_E_LIB_APP_PROXY_INCOMPATIBLE
0x8011044F
Library applications and application proxies are incompatible
COMADMIN_E_BASE_PARTITION_ONLY
0x80110450
This function is valid for the base partition only
COMADMIN_E_START_APP_DISABLED
0x80110451
You cannot start an application that has been disabled
COMADMIN_E_CAT_DUPLICATE_PARTITION_NAME
0x80110457
The specified partition name is already in use on this computer
COMADMIN_E_CAT_INVALID_PARTITION_NAME
0x80110458
The specified partition name is invalid. Check that the name contains at least one visible character
COMADMIN_E_CAT_PARTITION_IN_USE
0x80110459
The partition cannot be deleted because it is the default partition for one or more users
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
0x8011045A
The partition cannot be exported, because one or more components in the partition have the same file name
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
0x8011045B
Applications that contain one or more imported components cannot be installed into a non-base partition
COMADMIN_E_AMBIGUOUS_APPLICATION_NAME
0x8011045C
The application name is not unique and cannot be resolved to an application id
COMADMIN_E_AMBIGUOUS_PARTITION_NAME
0x8011045D
The partition name is not unique and cannot be resolved to a partition id
COMADMIN_E_REGDB_NOTINITIALIZED
0x80110472
The COM+ registry database has not been initialized
COMADMIN_E_REGDB_NOTOPEN
0x80110473
The COM+ registry database is not open
COMADMIN_E_REGDB_SYSTEMERR
0x80110474
The COM+ registry database detected a system error
COMADMIN_E_REGDB_ALREADYRUNNING
0x80110475
The COM+ registry database is already running
COMADMIN_E_MIG_VERSIONNOTSUPPORTED
0x80110480
This version of the COM+ registry database cannot be migrated
COMADMIN_E_MIG_SCHEMANOTFOUND
0x80110481
The schema version to be migrated could not be found in the COM+ registry database
COMADMIN_E_CAT_BITNESSMISMATCH
0x80110482
There was a type mismatch between binaries
COMADMIN_E_CAT_UNACCEPTABLEBITNESS
0x80110483
A binary of unknown or invalid type was provided
COMADMIN_E_CAT_WRONGAPPBITNESS
0x80110484
There was a type mismatch between a binary and an application
COMADMIN_E_CAT_PAUSE_RESUME_NOT_SUPPORTED
0x80110485
The application cannot be paused or resumed
COMADMIN_E_CAT_SERVERFAULT
0x80110486
The COM+ Catalog Server threw an exception during execution
COMQC_E_APPLICATION_NOT_QUEUED
0x80110600
Only COM+ Applications marked "queued" can be invoked using the "queue" moniker
COMQC_E_NO_QUEUEABLE_INTERFACES
0x80110601
At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker
COMQC_E_QUEUING_SERVICE_NOT_AVAILABLE
0x80110602
MSMQ is required for the requested operation and is not installed
COMQC_E_NO_IPERSISTSTREAM
0x80110603
Unable to marshal an interface that does not support IPersistStream
COMQC_E_BAD_MESSAGE
0x80110604
The message is improperly formatted or was damaged in transit
COMQC_E_UNAUTHENTICATED
0x80110605
An unauthenticated message was received by an application that accepts only authenticated messages
COMQC_E_UNTRUSTED_ENQUEUER
0x80110606
The message was requeued or moved by a user not in the "QC Trusted User" role
MSDTC_E_DUPLICATE_RESOURCE
0x80110701
Cannot create a duplicate resource of type Distributed Transaction Coordinator
COMADMIN_E_OBJECT_PARENT_MISSING
0x80110808
One of the objects being inserted or updated does not belong to a valid parent collection
COMADMIN_E_OBJECT_DOES_NOT_EXIST
0x80110809
One of the specified objects cannot be found
COMADMIN_E_APP_NOT_RUNNING
0x8011080A
The specified application is not currently running
COMADMIN_E_INVALID_PARTITION
0x8011080B
The partition(s) specified are not valid.
COMADMIN_E_SVCAPP_NOT_POOLABLE_OR_RECYCLABLE
0x8011080D
COM+ applications that run as NT service may not be pooled or recycled
COMADMIN_E_USER_IN_SET
0x8011080E
One or more users are already assigned to a local partition set.
COMADMIN_E_CANTRECYCLELIBRARYAPPS
0x8011080F
Library applications may not be recycled.
COMADMIN_E_CANTRECYCLESERVICEAPPS
0x80110811
Applications running as NT services may not be recycled.
COMADMIN_E_PROCESSALREADYRECYCLED
0x80110812
The process has already been recycled.
COMADMIN_E_PAUSEDPROCESSMAYNOTBERECYCLED
0x80110813
A paused process may not be recycled.
COMADMIN_E_CANTMAKEINPROCSERVICE
0x80110814
Library applications may not be NT services.
COMADMIN_E_PROGIDINUSEBYCLSID
0x80110815
The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID.
COMADMIN_E_DEFAULT_PARTITION_NOT_IN_SET
0x80110816
The partition specified as default is not a member of the partition set.
COMADMIN_E_RECYCLEDPROCESSMAYNOTBEPAUSED
0x80110817
A recycled process may not be paused.
COMADMIN_E_PARTITION_ACCESSDENIED
0x80110818
Access to the specified partition is denied.
COMADMIN_E_PARTITION_MSI_ONLY
0x80110819
Only Application Files (*.MSI files) can be installed into partitions.
COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_1_0_FORMAT
0x8011081A
Applications containing one or more legacy components may not be exported to 1.0 format.
COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS
0x8011081B
Legacy components may not exist in non-base partitions.
COMADMIN_E_COMP_MOVE_SOURCE
0x8011081C
A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application
COMADMIN_E_COMP_MOVE_DEST
0x8011081D
A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application
COMADMIN_E_COMP_MOVE_PRIVATE
0x8011081E
A private component cannot be moved (or copied) to a library application or to the base partition
COMADMIN_E_BASEPARTITION_REQUIRED_IN_SET
0x8011081F
The Base Application Partition exists in all partition sets and cannot be removed.
COMADMIN_E_CANNOT_ALIAS_EVENTCLASS
0x80110820
Event Class components cannot be aliased.
COMADMIN_E_PRIVATE_ACCESSDENIED
0x80110821
Access is denied because the component is private.
COMADMIN_E_SAFERINVALID
0x80110822
The specified SAFER level is invalid.
COMADMIN_E_REGISTRY_ACCESSDENIED
0x80110823
The specified user cannot write to the system registry
COMADMIN_E_PARTITIONS_DISABLED
0x80110824
COM+ partitions are currently disabled.
ERROR_FLT_IO_COMPLETE
0x001F0001
The IO was completed by a filter.
ERROR_FLT_NO_HANDLER_DEFINED
0x801F0001
A handler was not defined by the filter for this operation.
ERROR_FLT_CONTEXT_ALREADY_DEFINED
0x801F0002
A context is already defined for this object.
ERROR_FLT_INVALID_ASYNCHRONOUS_REQUEST
0x801F0003
Asynchronous requests are not valid for this operation.
ERROR_FLT_DISALLOW_FAST_IO
0x801F0004
Disallow the Fast IO path for this operation.
ERROR_FLT_INVALID_NAME_REQUEST
0x801F0005
An invalid name request was made. The name requested cannot be retrieved at this time.
ERROR_FLT_NOT_SAFE_TO_POST_OPERATION
0x801F0006
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.
ERROR_FLT_NOT_INITIALIZED
0x801F0007
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver.
ERROR_FLT_FILTER_NOT_READY
0x801F0008
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).
ERROR_FLT_POST_OPERATION_CLEANUP
0x801F0009
The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers.
ERROR_FLT_INTERNAL_ERROR
0x801F000A
The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback.
ERROR_FLT_DELETING_OBJECT
0x801F000B
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.
ERROR_FLT_MUST_BE_NONPAGED_POOL
0x801F000C
Non-paged pool must be used for this type of context.
ERROR_FLT_DUPLICATE_ENTRY
0x801F000D
A duplicate handler definition has been provided for an operation.
ERROR_FLT_CBDQ_DISABLED
0x801F000E
The callback data queue has been disabled.
ERROR_FLT_DO_NOT_ATTACH
0x801F000F
Do not attach the filter to the volume at this time.
ERROR_FLT_DO_NOT_DETACH
0x801F0010
Do not detach the filter from the volume at this time.
ERROR_FLT_INSTANCE_ALTITUDE_COLLISION
0x801F0011
An instance already exists at this altitude on the volume specified.
ERROR_FLT_INSTANCE_NAME_COLLISION
0x801F0012
An instance already exists with this name on the volume specified.
ERROR_FLT_FILTER_NOT_FOUND
0x801F0013
The system could not find the filter specified.
ERROR_FLT_VOLUME_NOT_FOUND
0x801F0014
The system could not find the volume specified.
ERROR_FLT_INSTANCE_NOT_FOUND
0x801F0015
The system could not find the instance specified.
ERROR_FLT_CONTEXT_ALLOCATION_NOT_FOUND
0x801F0016
No registered context allocation definition was found for the given request.
ERROR_FLT_INVALID_CONTEXT_REGISTRATION
0x801F0017
An invalid parameter was specified during context registration.
ERROR_FLT_NAME_CACHE_MISS
0x801F0018
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.
ERROR_FLT_NO_DEVICE_OBJECT
0x801F0019
The requested device object does not exist for the given volume.
ERROR_FLT_VOLUME_ALREADY_MOUNTED
0x801F001A
The specified volume is already mounted.
ERROR_FLT_ALREADY_ENLISTED
0x801F001B
The specified Transaction Context is already enlisted in a transaction
ERROR_FLT_CONTEXT_ALREADY_LINKED
0x801F001C
The specified context is already attached to another object
ERROR_FLT_NO_WAITER_FOR_REPLY
0x801F0020
No waiter is present for the filter's reply to this message.
ERROR_FLT_REGISTRATION_BUSY
0x801F0023
The filesystem database resource is in use. Registration cannot complete at this time.
ERROR_HUNG_DISPLAY_DRIVER_THREAD
0x80260001
Display Driver Stopped Responding} The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft.
DWM_E_COMPOSITIONDISABLED
0x80263001
Desktop composition is disabled} The operation could not be completed because desktop composition is disabled.
DWM_E_REMOTING_NOT_SUPPORTED
0x80263002
Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session.
DWM_E_NO_REDIRECTION_SURFACE_AVAILABLE
0x80263003
No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present.
DWM_E_NOT_QUEUING_PRESENTS
0x80263004
DWM is not queuing presents for the specified window} The window specified is not currently using queued presents.
DWM_E_ADAPTER_NOT_FOUND
0x80263005
The adapter specified by the LUID is not found} DWM cannot find the adapter specified by the LUID.
DWM_S_GDI_REDIRECTION_SURFACE
0x00263005
GDI redirection surface was returned} GDI redirection surface of the top level window was returned.
DWM_E_TEXTURE_TOO_LARGE
0x80263007
Redirection surface can not be created. The size of the surface is larger than what is supported on this machine} Redirection surface can not be created. The size of the surface is larger than what is supported on this machine.
ERROR_MONITOR_NO_DESCRIPTOR
0x80261001
Monitor descriptor could not be obtained.
ERROR_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT
0x80261002
Format of the obtained monitor descriptor is not supported by this release.
ERROR_MONITOR_INVALID_DESCRIPTOR_CHECKSUM
0xC0261003
Checksum of the obtained monitor descriptor is invalid.
ERROR_MONITOR_INVALID_STANDARD_TIMING_BLOCK
0xC0261004
Monitor descriptor contains an invalid standard timing block.
ERROR_MONITOR_WMI_DATABLOCK_REGISTRATION_FAILED
0xC0261005
WMI data block registration failed for one of the MSMonitorClass WMI subclasses.
ERROR_MONITOR_INVALID_SERIAL_NUMBER_MONDSC_BLOCK
0xC0261006
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.
ERROR_MONITOR_INVALID_USER_FRIENDLY_MONDSC_BLOCK
0xC0261007
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.
ERROR_MONITOR_NO_MORE_DESCRIPTOR_DATA
0xC0261008
There is no monitor descriptor data at the specified (offset, size) region.
ERROR_MONITOR_INVALID_DETAILED_TIMING_BLOCK
0xC0261009
Monitor descriptor contains an invalid detailed timing block.
ERROR_MONITOR_INVALID_MANUFACTURE_DATE
0xC026100A
Monitor descriptor contains invalid manufacture date.
ERROR_GRAPHICS_NOT_EXCLUSIVE_MODE_OWNER
0xC0262000
Exclusive mode ownership is needed to create unmanaged primary allocation.
ERROR_GRAPHICS_INSUFFICIENT_DMA_BUFFER
0xC0262001
The driver needs more DMA buffer space in order to complete the requested operation.
ERROR_GRAPHICS_INVALID_DISPLAY_ADAPTER
0xC0262002
Specified display adapter handle is invalid.
ERROR_GRAPHICS_ADAPTER_WAS_RESET
0xC0262003
Specified display adapter and all of its state has been reset.
ERROR_GRAPHICS_INVALID_DRIVER_MODEL
0xC0262004
The driver stack doesn't match the expected driver model.
ERROR_GRAPHICS_PRESENT_MODE_CHANGED
0xC0262005
Present happened but ended up in the changed desktop
ERROR_GRAPHICS_PRESENT_OCCLUDED
0xC0262006
Nothing to present due to desktop occlusion
ERROR_GRAPHICS_PRESENT_DENIED
0xC0262007
Not able to present due to denial of desktop access
ERROR_GRAPHICS_CANNOTCOLORCONVERT
0xC0262008
Not able to present with color convertion
ERROR_GRAPHICS_DRIVER_MISMATCH
0xC0262009
The kernel driver detected a version mismatch between it and the user mode driver.
ERROR_GRAPHICS_PARTIAL_DATA_POPULATED
0x4026200A
Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific).
ERROR_GRAPHICS_PRESENT_REDIRECTION_DISABLED
0xC026200B
Present redirection is disabled (desktop windowing management subsystem is off).
ERROR_GRAPHICS_PRESENT_UNOCCLUDED
0xC026200C
Previous exclusive VidPn source owner has released its ownership
ERROR_GRAPHICS_WINDOWDC_NOT_AVAILABLE
0xC026200D
Window DC is not available for presentation
ERROR_GRAPHICS_NO_VIDEO_MEMORY
0xC0262100
Not enough video memory available to complete the operation.
ERROR_GRAPHICS_CANT_LOCK_MEMORY
0xC0262101
Couldn't probe and lock the underlying memory of an allocation.
ERROR_GRAPHICS_ALLOCATION_BUSY
0xC0262102
The allocation is currently busy.
ERROR_GRAPHICS_TOO_MANY_REFERENCES
0xC0262103
An object being referenced has reach the maximum reference count already and can't be reference further.
ERROR_GRAPHICS_TRY_AGAIN_LATER
0xC0262104
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later.
ERROR_GRAPHICS_TRY_AGAIN_NOW
0xC0262105
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately.
ERROR_GRAPHICS_ALLOCATION_INVALID
0xC0262106
The allocation is invalid.
ERROR_GRAPHICS_UNSWIZZLING_APERTURE_UNAVAILABLE
0xC0262107
No more unswizzling aperture are currently available.
ERROR_GRAPHICS_UNSWIZZLING_APERTURE_UNSUPPORTED
0xC0262108
The current allocation can't be unswizzled by an aperture.
ERROR_GRAPHICS_CANT_EVICT_PINNED_ALLOCATION
0xC0262109
The request failed because a pinned allocation can't be evicted.
ERROR_GRAPHICS_INVALID_ALLOCATION_USAGE
0xC0262110
The allocation can't be used from its current segment location for the specified operation.
ERROR_GRAPHICS_CANT_RENDER_LOCKED_ALLOCATION
0xC0262111
A locked allocation can't be used in the current command buffer.
ERROR_GRAPHICS_ALLOCATION_CLOSED
0xC0262112
The allocation being referenced has been closed permanently.
ERROR_GRAPHICS_INVALID_ALLOCATION_INSTANCE
0xC0262113
An invalid allocation instance is being referenced.
ERROR_GRAPHICS_INVALID_ALLOCATION_HANDLE
0xC0262114
An invalid allocation handle is being referenced.
ERROR_GRAPHICS_WRONG_ALLOCATION_DEVICE
0xC0262115
The allocation being referenced doesn't belong to the current device.
ERROR_GRAPHICS_ALLOCATION_CONTENT_LOST
0xC0262116
The specified allocation lost its content.
ERROR_GRAPHICS_GPU_EXCEPTION_ON_DEVICE
0xC0262200
GPU exception is detected on the given device. The device is not able to be scheduled.
ERROR_GRAPHICS_SKIP_ALLOCATION_PREPARATION
0x40262201
Skip preparation of allocations referenced by the DMA buffer.
ERROR_GRAPHICS_INVALID_VIDPN_TOPOLOGY
0xC0262300
Specified VidPN topology is invalid.
ERROR_GRAPHICS_VIDPN_TOPOLOGY_NOT_SUPPORTED
0xC0262301
Specified VidPN topology is valid but is not supported by this model of the display adapter.
ERROR_GRAPHICS_VIDPN_TOPOLOGY_CURRENTLY_NOT_SUPPORTED
0xC0262302
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources.
ERROR_GRAPHICS_INVALID_VIDPN
0xC0262303
Specified VidPN handle is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE
0xC0262304
Specified video present source is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET
0xC0262305
Specified video present target is invalid.
ERROR_GRAPHICS_VIDPN_MODALITY_NOT_SUPPORTED
0xC0262306
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).
ERROR_GRAPHICS_MODE_NOT_PINNED
0x00262307
No mode is pinned on the specified VidPN source/target.
ERROR_GRAPHICS_INVALID_VIDPN_SOURCEMODESET
0xC0262308
Specified VidPN source mode set is invalid.
ERROR_GRAPHICS_INVALID_VIDPN_TARGETMODESET
0xC0262309
Specified VidPN target mode set is invalid.
ERROR_GRAPHICS_INVALID_FREQUENCY
0xC026230A
Specified video signal frequency is invalid.
ERROR_GRAPHICS_INVALID_ACTIVE_REGION
0xC026230B
Specified video signal active region is invalid.
ERROR_GRAPHICS_INVALID_TOTAL_REGION
0xC026230C
Specified video signal total region is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE_MODE
0xC0262310
Specified video present source mode is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET_MODE
0xC0262311
Specified video present target mode is invalid.
ERROR_GRAPHICS_PINNED_MODE_MUST_REMAIN_IN_SET
0xC0262312
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.
ERROR_GRAPHICS_PATH_ALREADY_IN_TOPOLOGY
0xC0262313
Specified video present path is already in VidPN's topology.
ERROR_GRAPHICS_MODE_ALREADY_IN_MODESET
0xC0262314
Specified mode is already in the mode set.
ERROR_GRAPHICS_INVALID_VIDEOPRESENTSOURCESET
0xC0262315
Specified video present source set is invalid.
ERROR_GRAPHICS_INVALID_VIDEOPRESENTTARGETSET
0xC0262316
Specified video present target set is invalid.
ERROR_GRAPHICS_SOURCE_ALREADY_IN_SET
0xC0262317
Specified video present source is already in the video present source set.
ERROR_GRAPHICS_TARGET_ALREADY_IN_SET
0xC0262318
Specified video present target is already in the video present target set.
ERROR_GRAPHICS_INVALID_VIDPN_PRESENT_PATH
0xC0262319
Specified VidPN present path is invalid.
ERROR_GRAPHICS_NO_RECOMMENDED_VIDPN_TOPOLOGY
0xC026231A
Miniport has no recommendation for augmentation of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGESET
0xC026231B
Specified monitor frequency range set is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE
0xC026231C
Specified monitor frequency range is invalid.
ERROR_GRAPHICS_FREQUENCYRANGE_NOT_IN_SET
0xC026231D
Specified frequency range is not in the specified monitor frequency range set.
ERROR_GRAPHICS_NO_PREFERRED_MODE
0x0026231E
Specified mode set does not specify preference for one of its modes.
ERROR_GRAPHICS_FREQUENCYRANGE_ALREADY_IN_SET
0xC026231F
Specified frequency range is already in the specified monitor frequency range set.
ERROR_GRAPHICS_STALE_MODESET
0xC0262320
Specified mode set is stale. Please reacquire the new mode set.
ERROR_GRAPHICS_INVALID_MONITOR_SOURCEMODESET
0xC0262321
Specified monitor source mode set is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_SOURCE_MODE
0xC0262322
Specified monitor source mode is invalid.
ERROR_GRAPHICS_NO_RECOMMENDED_FUNCTIONAL_VIDPN
0xC0262323
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.
ERROR_GRAPHICS_MODE_ID_MUST_BE_UNIQUE
0xC0262324
ID of the specified mode is already used by another mode in the set.
ERROR_GRAPHICS_EMPTY_ADAPTER_MONITOR_MODE_SUPPORT_INTERSECTION
0xC0262325
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.
ERROR_GRAPHICS_VIDEO_PRESENT_TARGETS_LESS_THAN_SOURCES
0xC0262326
Number of video present targets must be greater than or equal to the number of video present sources.
ERROR_GRAPHICS_PATH_NOT_IN_TOPOLOGY
0xC0262327
Specified present path is not in VidPN's topology.
ERROR_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_SOURCE
0xC0262328
Display adapter must have at least one video present source.
ERROR_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_TARGET
0xC0262329
Display adapter must have at least one video present target.
ERROR_GRAPHICS_INVALID_MONITORDESCRIPTORSET
0xC026232A
Specified monitor descriptor set is invalid.
ERROR_GRAPHICS_INVALID_MONITORDESCRIPTOR
0xC026232B
Specified monitor descriptor is invalid.
ERROR_GRAPHICS_MONITORDESCRIPTOR_NOT_IN_SET
0xC026232C
Specified descriptor is not in the specified monitor descriptor set.
ERROR_GRAPHICS_MONITORDESCRIPTOR_ALREADY_IN_SET
0xC026232D
Specified descriptor is already in the specified monitor descriptor set.
ERROR_GRAPHICS_MONITORDESCRIPTOR_ID_MUST_BE_UNIQUE
0xC026232E
ID of the specified monitor descriptor is already used by another descriptor in the set.
ERROR_GRAPHICS_INVALID_VIDPN_TARGET_SUBSET_TYPE
0xC026232F
Specified video present target subset type is invalid.
ERROR_GRAPHICS_RESOURCES_NOT_RELATED
0xC0262330
Two or more of the specified resources are not related to each other, as defined by the interface semantics.
ERROR_GRAPHICS_SOURCE_ID_MUST_BE_UNIQUE
0xC0262331
ID of the specified video present source is already used by another source in the set.
ERROR_GRAPHICS_TARGET_ID_MUST_BE_UNIQUE
0xC0262332
ID of the specified video present target is already used by another target in the set.
ERROR_GRAPHICS_NO_AVAILABLE_VIDPN_TARGET
0xC0262333
Specified VidPN source cannot be used because there is no available VidPN target to connect it to.
ERROR_GRAPHICS_MONITOR_COULD_NOT_BE_ASSOCIATED_WITH_ADAPTER
0xC0262334
Newly arrived monitor could not be associated with a display adapter.
ERROR_GRAPHICS_NO_VIDPNMGR
0xC0262335
Display adapter in question does not have an associated VidPN manager.
ERROR_GRAPHICS_NO_ACTIVE_VIDPN
0xC0262336
VidPN manager of the display adapter in question does not have an active VidPN.
ERROR_GRAPHICS_STALE_VIDPN_TOPOLOGY
0xC0262337
Specified VidPN topology is stale. Please reacquire the new topology.
ERROR_GRAPHICS_MONITOR_NOT_CONNECTED
0xC0262338
There is no monitor connected on the specified video present target.
ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY
0xC0262339
Specified source is not part of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE
0xC026233A
Specified primary surface size is invalid.
ERROR_GRAPHICS_INVALID_VISIBLEREGION_SIZE
0xC026233B
Specified visible region size is invalid.
ERROR_GRAPHICS_INVALID_STRIDE
0xC026233C
Specified stride is invalid.
ERROR_GRAPHICS_INVALID_PIXELFORMAT
0xC026233D
Specified pixel format is invalid.
ERROR_GRAPHICS_INVALID_COLORBASIS
0xC026233E
Specified color basis is invalid.
ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE
0xC026233F
Specified pixel value access mode is invalid.
ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY
0xC0262340
Specified target is not part of the specified VidPN's topology.
ERROR_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT
0xC0262341
Failed to acquire display mode management interface.
ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE
0xC0262342
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it.
ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN
0xC0262343
Specified VidPN is active and cannot be accessed.
ERROR_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL
0xC0262344
Specified VidPN present path importance ordinal is invalid.
ERROR_GRAPHICS_INVALID_PATH_CONTENT_GEOMETRY_TRANSFORMATION
0xC0262345
Specified VidPN present path content geometry transformation is invalid.
ERROR_GRAPHICS_PATH_CONTENT_GEOMETRY_TRANSFORMATION_NOT_SUPPORTED
0xC0262346
Specified content geometry transformation is not supported on the respective VidPN present path.
ERROR_GRAPHICS_INVALID_GAMMA_RAMP
0xC0262347
Specified gamma ramp is invalid.
ERROR_GRAPHICS_GAMMA_RAMP_NOT_SUPPORTED
0xC0262348
Specified gamma ramp is not supported on the respective VidPN present path.
ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED
0xC0262349
Multi-sampling is not supported on the respective VidPN present path.
ERROR_GRAPHICS_MODE_NOT_IN_MODESET
0xC026234A
Specified mode is not in the specified mode set.
ERROR_GRAPHICS_DATASET_IS_EMPTY
0x0026234B
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty.
ERROR_GRAPHICS_NO_MORE_ELEMENTS_IN_DATASET
0x0026234C
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements.
ERROR_GRAPHICS_INVALID_VIDPN_TOPOLOGY_RECOMMENDATION_REASON
0xC026234D
Specified VidPN topology recommendation reason is invalid.
ERROR_GRAPHICS_INVALID_PATH_CONTENT_TYPE
0xC026234E
Specified VidPN present path content type is invalid.
ERROR_GRAPHICS_INVALID_COPYPROTECTION_TYPE
0xC026234F
Specified VidPN present path copy protection type is invalid.
ERROR_GRAPHICS_UNASSIGNED_MODESET_ALREADY_EXISTS
0xC0262350
No more than one unassigned mode set can exist at any given time for a given VidPN source/target.
ERROR_GRAPHICS_PATH_CONTENT_GEOMETRY_TRANSFORMATION_NOT_PINNED
0x00262351
Specified content transformation is not pinned on the specified VidPN present path.
ERROR_GRAPHICS_INVALID_SCANLINE_ORDERING
0xC0262352
Specified scanline ordering type is invalid.
ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED
0xC0262353
Topology changes are not allowed for the specified VidPN.
ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS
0xC0262354
All available importance ordinals are already used in specified topology.
ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT
0xC0262355
Specified primary surface has a different private format attribute than the current primary surface
ERROR_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM
0xC0262356
Specified mode pruning algorithm is invalid
ERROR_GRAPHICS_INVALID_MONITOR_CAPABILITY_ORIGIN
0xC0262357
Specified monitor capability origin is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE_CONSTRAINT
0xC0262358
Specified monitor frequency range constraint is invalid.
ERROR_GRAPHICS_MAX_NUM_PATHS_REACHED
0xC0262359
Maximum supported number of present paths has been reached.
ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION
0xC026235A
Miniport requested that augmentation be canceled for the specified source of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_CLIENT_TYPE
0xC026235B
Specified client type was not recognized.
ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET
0xC026235C
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).
ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED
0xC0262400
Specified display adapter child device already has an external device connected to it.
ERROR_GRAPHICS_CHILD_DESCRIPTOR_NOT_SUPPORTED
0xC0262401
Specified display adapter child device does not support descriptor exposure.
ERROR_GRAPHICS_UNKNOWN_CHILD_STATUS
0x4026242F
Child device presence was not reliably detected.
ERROR_GRAPHICS_NOT_A_LINKED_ADAPTER
0xC0262430
The display adapter is not linked to any other adapters.
ERROR_GRAPHICS_LEADLINK_NOT_ENUMERATED
0xC0262431
Lead adapter in a linked configuration was not enumerated yet.
ERROR_GRAPHICS_CHAINLINKS_NOT_ENUMERATED
0xC0262432
Some chain adapters in a linked configuration were not enumerated yet.
ERROR_GRAPHICS_ADAPTER_CHAIN_NOT_READY
0xC0262433
The chain of linked adapters is not ready to start because of an unknown failure.
ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED
0xC0262434
An attempt was made to start a lead link display adapter when the chain links were not started yet.
ERROR_GRAPHICS_CHAINLINKS_NOT_POWERED_ON
0xC0262435
An attempt was made to power up a lead link display adapter when the chain links were powered down.
ERROR_GRAPHICS_INCONSISTENT_DEVICE_LINK_STATE
0xC0262436
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state.
ERROR_GRAPHICS_LEADLINK_START_DEFERRED
0x40262437
Starting the leadlink adapter has been deferred temporarily.
ERROR_GRAPHICS_NOT_POST_DEVICE_DRIVER
0xC0262438
The driver trying to start is not the same as the driver for the POSTed display adapter.
ERROR_GRAPHICS_POLLING_TOO_FREQUENTLY
0x40262439
The display adapter is being polled for children too frequently at the same polling level.
ERROR_GRAPHICS_START_DEFERRED
0x4026243A
Starting the adapter has been deferred temporarily.
ERROR_GRAPHICS_ADAPTER_ACCESS_NOT_EXCLUDED
0xC026243B
An operation is being attempted that requires the display adapter to be in a quiescent state.
ERROR_GRAPHICS_OPM_NOT_SUPPORTED
0xC0262500
The driver does not support OPM.
ERROR_GRAPHICS_COPP_NOT_SUPPORTED
0xC0262501
The driver does not support COPP.
ERROR_GRAPHICS_UAB_NOT_SUPPORTED
0xC0262502
The driver does not support UAB.
ERROR_GRAPHICS_OPM_INVALID_ENCRYPTED_PARAMETERS
0xC0262503
The specified encrypted parameters are invalid.
ERROR_GRAPHICS_OPM_NO_VIDEO_OUTPUTS_EXIST
0xC0262505
The GDI display device passed to this function does not have any active video outputs.
ERROR_GRAPHICS_OPM_INTERNAL_ERROR
0xC026250B
An internal error caused this operation to fail.
ERROR_GRAPHICS_OPM_INVALID_HANDLE
0xC026250C
The function failed because the caller passed in an invalid OPM user mode handle.
ERROR_GRAPHICS_PVP_INVALID_CERTIFICATE_LENGTH
0xC026250E
A certificate could not be returned because the certificate buffer passed to the function was too small.
ERROR_GRAPHICS_OPM_SPANNING_MODE_ENABLED
0xC026250F
A video output could not be created because the frame buffer is in spanning mode.
ERROR_GRAPHICS_OPM_THEATER_MODE_ENABLED
0xC0262510
A video output could not be created because the frame buffer is in theater mode.
ERROR_GRAPHICS_PVP_HFS_FAILED
0xC0262511
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.
ERROR_GRAPHICS_OPM_INVALID_SRM
0xC0262512
The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_HDCP
0xC0262513
The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_ACP
0xC0262514
The video output cannot enable Analog Copy Protection (ACP) because it does not support ACP.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_CGMSA
0xC0262515
The video output cannot enable the Content Generation Management System Analog (CGMS-A) protection technology because it does not support CGMS-A.
ERROR_GRAPHICS_OPM_HDCP_SRM_NEVER_SET
0xC0262516
The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output.
ERROR_GRAPHICS_OPM_RESOLUTION_TOO_HIGH
0xC0262517
The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high.
ERROR_GRAPHICS_OPM_ALL_HDCP_HARDWARE_ALREADY_IN_USE
0xC0262518
The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_NO_LONGER_EXISTS
0xC026251A
The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop.
ERROR_GRAPHICS_OPM_SESSION_TYPE_CHANGE_IN_PROGRESS
0xC026251B
The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS
0xC026251C
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only.
ERROR_GRAPHICS_OPM_INVALID_INFORMATION_REQUEST
0xC026251D
The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
ERROR_GRAPHICS_OPM_DRIVER_INTERNAL_ERROR
0xC026251E
The method failed because an unexpected error occurred inside of a display driver.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_OPM_SEMANTICS
0xC026251F
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only.
ERROR_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED
0xC0262520
The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.
ERROR_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST
0xC0262521
The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
ERROR_GRAPHICS_I2C_NOT_SUPPORTED
0xC0262580
The monitor connected to the specified video output does not have an I2C bus.
ERROR_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST
0xC0262581
No device on the I2C bus has the specified address.
ERROR_GRAPHICS_I2C_ERROR_TRANSMITTING_DATA
0xC0262582
An error occurred while transmitting data to the device on the I2C bus.
ERROR_GRAPHICS_I2C_ERROR_RECEIVING_DATA
0xC0262583
An error occurred while receiving data from the device on the I2C bus.
ERROR_GRAPHICS_DDCCI_VCP_NOT_SUPPORTED
0xC0262584
The monitor does not support the specified VCP code.
ERROR_GRAPHICS_DDCCI_INVALID_DATA
0xC0262585
The data received from the monitor is invalid.
ERROR_GRAPHICS_DDCCI_MONITOR_RETURNED_INVALID_TIMING_STATUS_BYTE
0xC0262586
The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor.
ERROR_GRAPHICS_MCA_INVALID_CAPABILITIES_STRING
0xC0262587
The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.
ERROR_GRAPHICS_MCA_INTERNAL_ERROR
0xC0262588
An internal Monitor Configuration API error occurred.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_COMMAND
0xC0262589
An operation failed because a DDC/CI message had an invalid value in its command field.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_LENGTH
0xC026258A
An error occurred because the field length of a DDC/CI message contained an invalid value.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_CHECKSUM
0xC026258B
An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer.
ERROR_GRAPHICS_INVALID_PHYSICAL_MONITOR_HANDLE
0xC026258C
This function failed because an invalid monitor handle was passed to it.
ERROR_GRAPHICS_MONITOR_NO_LONGER_EXISTS
0xC026258D
The operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications.
ERROR_GRAPHICS_DDCCI_CURRENT_CURRENT_VALUE_GREATER_THAN_MAXIMUM_VALUE
0xC02625D8
A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value.
ERROR_GRAPHICS_MCA_INVALID_VCP_VERSION
0xC02625D9
The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
ERROR_GRAPHICS_MCA_MONITOR_VIOLATES_MCCS_SPECIFICATION
0xC02625DA
The monitor does not comply with the MCCS specification it claims to support.
ERROR_GRAPHICS_MCA_MCCS_VERSION_MISMATCH
0xC02625DB
The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
ERROR_GRAPHICS_MCA_UNSUPPORTED_MCCS_VERSION
0xC02625DC
The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_MCA_INVALID_TECHNOLOGY_TYPE_RETURNED
0xC02625DE
The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_MCA_UNSUPPORTED_COLOR_TEMPERATURE
0xC02625DF
SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_ONLY_CONSOLE_SESSION_SUPPORTED
0xC02625E0
This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session.
ERROR_GRAPHICS_NO_DISPLAY_DEVICE_CORRESPONDS_TO_NAME
0xC02625E1
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.
ERROR_GRAPHICS_DISPLAY_DEVICE_NOT_ATTACHED_TO_DESKTOP
0xC02625E2
The function failed because the specified GDI display device was not attached to the Windows desktop.
ERROR_GRAPHICS_MIRRORING_DEVICES_NOT_SUPPORTED
0xC02625E3
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.
ERROR_GRAPHICS_INVALID_POINTER
0xC02625E4
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned.
ERROR_GRAPHICS_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE
0xC02625E5
The function failed because the specified GDI device did not have any monitors associated with it.
ERROR_GRAPHICS_PARAMETER_ARRAY_TOO_SMALL
0xC02625E6
An array passed to the function cannot hold all of the data that the function must copy into the array.
ERROR_GRAPHICS_INTERNAL_ERROR
0xC02625E7
An internal error caused an operation to fail.
ERROR_GRAPHICS_SESSION_TYPE_CHANGE_IN_PROGRESS
0xC02605E8
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote.
【外部リンク】
https://msdn.microsoft.com/en-us/library/windows/desktop/dd542647(v=vs.85).aspx
Constant/value Description
COMADMIN_E_OBJECTERRORS
0x80110401
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail
COMADMIN_E_OBJECTINVALID
0x80110402
One or more of the object's properties are missing or invalid
COMADMIN_E_KEYMISSING
0x80110403
The object was not found in the catalog
COMADMIN_E_ALREADYINSTALLED
0x80110404
The object is already registered
COMADMIN_E_APP_FILE_WRITEFAIL
0x80110407
Error occurred writing to the application file
COMADMIN_E_APP_FILE_READFAIL
0x80110408
Error occurred reading the application file
COMADMIN_E_APP_FILE_VERSION
0x80110409
Invalid version number in application file
COMADMIN_E_BADPATH
0x8011040A
The file path is invalid
COMADMIN_E_APPLICATIONEXISTS
0x8011040B
The application is already installed
COMADMIN_E_ROLEEXISTS
0x8011040C
The role already exists
COMADMIN_E_CANTCOPYFILE
0x8011040D
An error occurred copying the file
COMADMIN_E_NOUSER
0x8011040F
One or more users are not valid
COMADMIN_E_INVALIDUSERIDS
0x80110410
One or more users in the application file are not valid
COMADMIN_E_NOREGISTRYCLSID
0x80110411
The component's CLSID is missing or corrupt
COMADMIN_E_BADREGISTRYPROGID
0x80110412
The component's progID is missing or corrupt
COMADMIN_E_AUTHENTICATIONLEVEL
0x80110413
Unable to set required authentication level for update request
COMADMIN_E_USERPASSWDNOTVALID
0x80110414
The identity or password set on the application is not valid
COMADMIN_E_CLSIDORIIDMISMATCH
0x80110418
Application file CLSIDs or IIDs do not match corresponding DLLs
COMADMIN_E_REMOTEINTERFACE
0x80110419
Interface information is either missing or changed
COMADMIN_E_DLLREGISTERSERVER
0x8011041A
DllRegisterServer failed on component install
COMADMIN_E_NOSERVERSHARE
0x8011041B
No server file share available
COMADMIN_E_DLLLOADFAILED
0x8011041D
DLL could not be loaded
COMADMIN_E_BADREGISTRYLIBID
0x8011041E
The registered TypeLib ID is not valid
COMADMIN_E_APPDIRNOTFOUND
0x8011041F
Application install directory not found
COMADMIN_E_REGISTRARFAILED
0x80110423
Errors occurred while in the component registrar
COMADMIN_E_COMPFILE_DOESNOTEXIST
0x80110424
The file does not exist
COMADMIN_E_COMPFILE_LOADDLLFAIL
0x80110425
The DLL could not be loaded
COMADMIN_E_COMPFILE_GETCLASSOBJ
0x80110426
GetClassObject failed in the DLL
COMADMIN_E_COMPFILE_CLASSNOTAVAIL
0x80110427
The DLL does not support the components listed in the TypeLib
COMADMIN_E_COMPFILE_BADTLB
0x80110428
The TypeLib could not be loaded
COMADMIN_E_COMPFILE_NOTINSTALLABLE
0x80110429
The file does not contain components or component information
COMADMIN_E_NOTCHANGEABLE
0x8011042A
Changes to this object and its sub-objects have been disabled
COMADMIN_E_NOTDELETEABLE
0x8011042B
The delete function has been disabled for this object
COMADMIN_E_SESSION
0x8011042C
The server catalog version is not supported
COMADMIN_E_COMP_MOVE_LOCKED
0x8011042D
The component move was disallowed, because the source or destination application is either a system application or currently locked against changes
COMADMIN_E_COMP_MOVE_BAD_DEST
0x8011042E
The component move failed because the destination application no longer exists
COMADMIN_E_REGISTERTLB
0x80110430
The system was unable to register the TypeLib
COMADMIN_E_SYSTEMAPP
0x80110433
This operation cannot be performed on the system application
COMADMIN_E_COMPFILE_NOREGISTRAR
0x80110434
The component registrar referenced in this file is not available
COMADMIN_E_COREQCOMPINSTALLED
0x80110435
A component in the same DLL is already installed
COMADMIN_E_SERVICENOTINSTALLED
0x80110436
The service is not installed
COMADMIN_E_PROPERTYSAVEFAILED
0x80110437
One or more property settings are either invalid or in conflict with each other
COMADMIN_E_OBJECTEXISTS
0x80110438
The object you are attempting to add or rename already exists
COMADMIN_E_COMPONENTEXISTS
0x80110439
The component already exists
COMADMIN_E_REGFILE_CORRUPT
0x8011043B
The registration file is corrupt
COMADMIN_E_PROPERTY_OVERFLOW
0x8011043C
The property value is too large
COMADMIN_E_NOTINREGISTRY
0x8011043E
Object was not found in registry
COMADMIN_E_OBJECTNOTPOOLABLE
0x8011043F
This object is not poolable
COMADMIN_E_APPLID_MATCHES_CLSID
0x80110446
A CLSID with the same GUID as the new application ID is already installed on this machine
COMADMIN_E_ROLE_DOES_NOT_EXIST
0x80110447
A role assigned to a component, interface, or method did not exist in the application
COMADMIN_E_START_APP_NEEDS_COMPONENTS
0x80110448
You must have components in an application in order to start the application
COMADMIN_E_REQUIRES_DIFFERENT_PLATFORM
0x80110449
This operation is not enabled on this platform
COMADMIN_E_CAN_NOT_EXPORT_APP_PROXY
0x8011044A
Application Proxy is not exportable
COMADMIN_E_CAN_NOT_START_APP
0x8011044B
Failed to start application because it is either a library application or an application proxy
COMADMIN_E_CAN_NOT_EXPORT_SYS_APP
0x8011044C
System application is not exportable
COMADMIN_E_CANT_SUBSCRIBE_TO_COMPONENT
0x8011044D
Cannot subscribe to this component (the component may have been imported)
COMADMIN_E_EVENTCLASS_CANT_BE_SUBSCRIBER
0x8011044E
An event class cannot also be a subscriber component
COMADMIN_E_LIB_APP_PROXY_INCOMPATIBLE
0x8011044F
Library applications and application proxies are incompatible
COMADMIN_E_BASE_PARTITION_ONLY
0x80110450
This function is valid for the base partition only
COMADMIN_E_START_APP_DISABLED
0x80110451
You cannot start an application that has been disabled
COMADMIN_E_CAT_DUPLICATE_PARTITION_NAME
0x80110457
The specified partition name is already in use on this computer
COMADMIN_E_CAT_INVALID_PARTITION_NAME
0x80110458
The specified partition name is invalid. Check that the name contains at least one visible character
COMADMIN_E_CAT_PARTITION_IN_USE
0x80110459
The partition cannot be deleted because it is the default partition for one or more users
COMADMIN_E_FILE_PARTITION_DUPLICATE_FILES
0x8011045A
The partition cannot be exported, because one or more components in the partition have the same file name
COMADMIN_E_CAT_IMPORTED_COMPONENTS_NOT_ALLOWED
0x8011045B
Applications that contain one or more imported components cannot be installed into a non-base partition
COMADMIN_E_AMBIGUOUS_APPLICATION_NAME
0x8011045C
The application name is not unique and cannot be resolved to an application id
COMADMIN_E_AMBIGUOUS_PARTITION_NAME
0x8011045D
The partition name is not unique and cannot be resolved to a partition id
COMADMIN_E_REGDB_NOTINITIALIZED
0x80110472
The COM+ registry database has not been initialized
COMADMIN_E_REGDB_NOTOPEN
0x80110473
The COM+ registry database is not open
COMADMIN_E_REGDB_SYSTEMERR
0x80110474
The COM+ registry database detected a system error
COMADMIN_E_REGDB_ALREADYRUNNING
0x80110475
The COM+ registry database is already running
COMADMIN_E_MIG_VERSIONNOTSUPPORTED
0x80110480
This version of the COM+ registry database cannot be migrated
COMADMIN_E_MIG_SCHEMANOTFOUND
0x80110481
The schema version to be migrated could not be found in the COM+ registry database
COMADMIN_E_CAT_BITNESSMISMATCH
0x80110482
There was a type mismatch between binaries
COMADMIN_E_CAT_UNACCEPTABLEBITNESS
0x80110483
A binary of unknown or invalid type was provided
COMADMIN_E_CAT_WRONGAPPBITNESS
0x80110484
There was a type mismatch between a binary and an application
COMADMIN_E_CAT_PAUSE_RESUME_NOT_SUPPORTED
0x80110485
The application cannot be paused or resumed
COMADMIN_E_CAT_SERVERFAULT
0x80110486
The COM+ Catalog Server threw an exception during execution
COMQC_E_APPLICATION_NOT_QUEUED
0x80110600
Only COM+ Applications marked "queued" can be invoked using the "queue" moniker
COMQC_E_NO_QUEUEABLE_INTERFACES
0x80110601
At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker
COMQC_E_QUEUING_SERVICE_NOT_AVAILABLE
0x80110602
MSMQ is required for the requested operation and is not installed
COMQC_E_NO_IPERSISTSTREAM
0x80110603
Unable to marshal an interface that does not support IPersistStream
COMQC_E_BAD_MESSAGE
0x80110604
The message is improperly formatted or was damaged in transit
COMQC_E_UNAUTHENTICATED
0x80110605
An unauthenticated message was received by an application that accepts only authenticated messages
COMQC_E_UNTRUSTED_ENQUEUER
0x80110606
The message was requeued or moved by a user not in the "QC Trusted User" role
MSDTC_E_DUPLICATE_RESOURCE
0x80110701
Cannot create a duplicate resource of type Distributed Transaction Coordinator
COMADMIN_E_OBJECT_PARENT_MISSING
0x80110808
One of the objects being inserted or updated does not belong to a valid parent collection
COMADMIN_E_OBJECT_DOES_NOT_EXIST
0x80110809
One of the specified objects cannot be found
COMADMIN_E_APP_NOT_RUNNING
0x8011080A
The specified application is not currently running
COMADMIN_E_INVALID_PARTITION
0x8011080B
The partition(s) specified are not valid.
COMADMIN_E_SVCAPP_NOT_POOLABLE_OR_RECYCLABLE
0x8011080D
COM+ applications that run as NT service may not be pooled or recycled
COMADMIN_E_USER_IN_SET
0x8011080E
One or more users are already assigned to a local partition set.
COMADMIN_E_CANTRECYCLELIBRARYAPPS
0x8011080F
Library applications may not be recycled.
COMADMIN_E_CANTRECYCLESERVICEAPPS
0x80110811
Applications running as NT services may not be recycled.
COMADMIN_E_PROCESSALREADYRECYCLED
0x80110812
The process has already been recycled.
COMADMIN_E_PAUSEDPROCESSMAYNOTBERECYCLED
0x80110813
A paused process may not be recycled.
COMADMIN_E_CANTMAKEINPROCSERVICE
0x80110814
Library applications may not be NT services.
COMADMIN_E_PROGIDINUSEBYCLSID
0x80110815
The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID.
COMADMIN_E_DEFAULT_PARTITION_NOT_IN_SET
0x80110816
The partition specified as default is not a member of the partition set.
COMADMIN_E_RECYCLEDPROCESSMAYNOTBEPAUSED
0x80110817
A recycled process may not be paused.
COMADMIN_E_PARTITION_ACCESSDENIED
0x80110818
Access to the specified partition is denied.
COMADMIN_E_PARTITION_MSI_ONLY
0x80110819
Only Application Files (*.MSI files) can be installed into partitions.
COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_1_0_FORMAT
0x8011081A
Applications containing one or more legacy components may not be exported to 1.0 format.
COMADMIN_E_LEGACYCOMPS_NOT_ALLOWED_IN_NONBASE_PARTITIONS
0x8011081B
Legacy components may not exist in non-base partitions.
COMADMIN_E_COMP_MOVE_SOURCE
0x8011081C
A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application
COMADMIN_E_COMP_MOVE_DEST
0x8011081D
A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application
COMADMIN_E_COMP_MOVE_PRIVATE
0x8011081E
A private component cannot be moved (or copied) to a library application or to the base partition
COMADMIN_E_BASEPARTITION_REQUIRED_IN_SET
0x8011081F
The Base Application Partition exists in all partition sets and cannot be removed.
COMADMIN_E_CANNOT_ALIAS_EVENTCLASS
0x80110820
Event Class components cannot be aliased.
COMADMIN_E_PRIVATE_ACCESSDENIED
0x80110821
Access is denied because the component is private.
COMADMIN_E_SAFERINVALID
0x80110822
The specified SAFER level is invalid.
COMADMIN_E_REGISTRY_ACCESSDENIED
0x80110823
The specified user cannot write to the system registry
COMADMIN_E_PARTITIONS_DISABLED
0x80110824
COM+ partitions are currently disabled.
ERROR_FLT_IO_COMPLETE
0x001F0001
The IO was completed by a filter.
ERROR_FLT_NO_HANDLER_DEFINED
0x801F0001
A handler was not defined by the filter for this operation.
ERROR_FLT_CONTEXT_ALREADY_DEFINED
0x801F0002
A context is already defined for this object.
ERROR_FLT_INVALID_ASYNCHRONOUS_REQUEST
0x801F0003
Asynchronous requests are not valid for this operation.
ERROR_FLT_DISALLOW_FAST_IO
0x801F0004
Disallow the Fast IO path for this operation.
ERROR_FLT_INVALID_NAME_REQUEST
0x801F0005
An invalid name request was made. The name requested cannot be retrieved at this time.
ERROR_FLT_NOT_SAFE_TO_POST_OPERATION
0x801F0006
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.
ERROR_FLT_NOT_INITIALIZED
0x801F0007
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver.
ERROR_FLT_FILTER_NOT_READY
0x801F0008
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).
ERROR_FLT_POST_OPERATION_CLEANUP
0x801F0009
The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers.
ERROR_FLT_INTERNAL_ERROR
0x801F000A
The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback.
ERROR_FLT_DELETING_OBJECT
0x801F000B
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.
ERROR_FLT_MUST_BE_NONPAGED_POOL
0x801F000C
Non-paged pool must be used for this type of context.
ERROR_FLT_DUPLICATE_ENTRY
0x801F000D
A duplicate handler definition has been provided for an operation.
ERROR_FLT_CBDQ_DISABLED
0x801F000E
The callback data queue has been disabled.
ERROR_FLT_DO_NOT_ATTACH
0x801F000F
Do not attach the filter to the volume at this time.
ERROR_FLT_DO_NOT_DETACH
0x801F0010
Do not detach the filter from the volume at this time.
ERROR_FLT_INSTANCE_ALTITUDE_COLLISION
0x801F0011
An instance already exists at this altitude on the volume specified.
ERROR_FLT_INSTANCE_NAME_COLLISION
0x801F0012
An instance already exists with this name on the volume specified.
ERROR_FLT_FILTER_NOT_FOUND
0x801F0013
The system could not find the filter specified.
ERROR_FLT_VOLUME_NOT_FOUND
0x801F0014
The system could not find the volume specified.
ERROR_FLT_INSTANCE_NOT_FOUND
0x801F0015
The system could not find the instance specified.
ERROR_FLT_CONTEXT_ALLOCATION_NOT_FOUND
0x801F0016
No registered context allocation definition was found for the given request.
ERROR_FLT_INVALID_CONTEXT_REGISTRATION
0x801F0017
An invalid parameter was specified during context registration.
ERROR_FLT_NAME_CACHE_MISS
0x801F0018
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.
ERROR_FLT_NO_DEVICE_OBJECT
0x801F0019
The requested device object does not exist for the given volume.
ERROR_FLT_VOLUME_ALREADY_MOUNTED
0x801F001A
The specified volume is already mounted.
ERROR_FLT_ALREADY_ENLISTED
0x801F001B
The specified Transaction Context is already enlisted in a transaction
ERROR_FLT_CONTEXT_ALREADY_LINKED
0x801F001C
The specified context is already attached to another object
ERROR_FLT_NO_WAITER_FOR_REPLY
0x801F0020
No waiter is present for the filter's reply to this message.
ERROR_FLT_REGISTRATION_BUSY
0x801F0023
The filesystem database resource is in use. Registration cannot complete at this time.
ERROR_HUNG_DISPLAY_DRIVER_THREAD
0x80260001
Display Driver Stopped Responding} The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft.
DWM_E_COMPOSITIONDISABLED
0x80263001
Desktop composition is disabled} The operation could not be completed because desktop composition is disabled.
DWM_E_REMOTING_NOT_SUPPORTED
0x80263002
Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session.
DWM_E_NO_REDIRECTION_SURFACE_AVAILABLE
0x80263003
No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present.
DWM_E_NOT_QUEUING_PRESENTS
0x80263004
DWM is not queuing presents for the specified window} The window specified is not currently using queued presents.
DWM_E_ADAPTER_NOT_FOUND
0x80263005
The adapter specified by the LUID is not found} DWM cannot find the adapter specified by the LUID.
DWM_S_GDI_REDIRECTION_SURFACE
0x00263005
GDI redirection surface was returned} GDI redirection surface of the top level window was returned.
DWM_E_TEXTURE_TOO_LARGE
0x80263007
Redirection surface can not be created. The size of the surface is larger than what is supported on this machine} Redirection surface can not be created. The size of the surface is larger than what is supported on this machine.
ERROR_MONITOR_NO_DESCRIPTOR
0x80261001
Monitor descriptor could not be obtained.
ERROR_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT
0x80261002
Format of the obtained monitor descriptor is not supported by this release.
ERROR_MONITOR_INVALID_DESCRIPTOR_CHECKSUM
0xC0261003
Checksum of the obtained monitor descriptor is invalid.
ERROR_MONITOR_INVALID_STANDARD_TIMING_BLOCK
0xC0261004
Monitor descriptor contains an invalid standard timing block.
ERROR_MONITOR_WMI_DATABLOCK_REGISTRATION_FAILED
0xC0261005
WMI data block registration failed for one of the MSMonitorClass WMI subclasses.
ERROR_MONITOR_INVALID_SERIAL_NUMBER_MONDSC_BLOCK
0xC0261006
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.
ERROR_MONITOR_INVALID_USER_FRIENDLY_MONDSC_BLOCK
0xC0261007
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.
ERROR_MONITOR_NO_MORE_DESCRIPTOR_DATA
0xC0261008
There is no monitor descriptor data at the specified (offset, size) region.
ERROR_MONITOR_INVALID_DETAILED_TIMING_BLOCK
0xC0261009
Monitor descriptor contains an invalid detailed timing block.
ERROR_MONITOR_INVALID_MANUFACTURE_DATE
0xC026100A
Monitor descriptor contains invalid manufacture date.
ERROR_GRAPHICS_NOT_EXCLUSIVE_MODE_OWNER
0xC0262000
Exclusive mode ownership is needed to create unmanaged primary allocation.
ERROR_GRAPHICS_INSUFFICIENT_DMA_BUFFER
0xC0262001
The driver needs more DMA buffer space in order to complete the requested operation.
ERROR_GRAPHICS_INVALID_DISPLAY_ADAPTER
0xC0262002
Specified display adapter handle is invalid.
ERROR_GRAPHICS_ADAPTER_WAS_RESET
0xC0262003
Specified display adapter and all of its state has been reset.
ERROR_GRAPHICS_INVALID_DRIVER_MODEL
0xC0262004
The driver stack doesn't match the expected driver model.
ERROR_GRAPHICS_PRESENT_MODE_CHANGED
0xC0262005
Present happened but ended up in the changed desktop
ERROR_GRAPHICS_PRESENT_OCCLUDED
0xC0262006
Nothing to present due to desktop occlusion
ERROR_GRAPHICS_PRESENT_DENIED
0xC0262007
Not able to present due to denial of desktop access
ERROR_GRAPHICS_CANNOTCOLORCONVERT
0xC0262008
Not able to present with color convertion
ERROR_GRAPHICS_DRIVER_MISMATCH
0xC0262009
The kernel driver detected a version mismatch between it and the user mode driver.
ERROR_GRAPHICS_PARTIAL_DATA_POPULATED
0x4026200A
Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific).
ERROR_GRAPHICS_PRESENT_REDIRECTION_DISABLED
0xC026200B
Present redirection is disabled (desktop windowing management subsystem is off).
ERROR_GRAPHICS_PRESENT_UNOCCLUDED
0xC026200C
Previous exclusive VidPn source owner has released its ownership
ERROR_GRAPHICS_WINDOWDC_NOT_AVAILABLE
0xC026200D
Window DC is not available for presentation
ERROR_GRAPHICS_NO_VIDEO_MEMORY
0xC0262100
Not enough video memory available to complete the operation.
ERROR_GRAPHICS_CANT_LOCK_MEMORY
0xC0262101
Couldn't probe and lock the underlying memory of an allocation.
ERROR_GRAPHICS_ALLOCATION_BUSY
0xC0262102
The allocation is currently busy.
ERROR_GRAPHICS_TOO_MANY_REFERENCES
0xC0262103
An object being referenced has reach the maximum reference count already and can't be reference further.
ERROR_GRAPHICS_TRY_AGAIN_LATER
0xC0262104
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later.
ERROR_GRAPHICS_TRY_AGAIN_NOW
0xC0262105
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately.
ERROR_GRAPHICS_ALLOCATION_INVALID
0xC0262106
The allocation is invalid.
ERROR_GRAPHICS_UNSWIZZLING_APERTURE_UNAVAILABLE
0xC0262107
No more unswizzling aperture are currently available.
ERROR_GRAPHICS_UNSWIZZLING_APERTURE_UNSUPPORTED
0xC0262108
The current allocation can't be unswizzled by an aperture.
ERROR_GRAPHICS_CANT_EVICT_PINNED_ALLOCATION
0xC0262109
The request failed because a pinned allocation can't be evicted.
ERROR_GRAPHICS_INVALID_ALLOCATION_USAGE
0xC0262110
The allocation can't be used from its current segment location for the specified operation.
ERROR_GRAPHICS_CANT_RENDER_LOCKED_ALLOCATION
0xC0262111
A locked allocation can't be used in the current command buffer.
ERROR_GRAPHICS_ALLOCATION_CLOSED
0xC0262112
The allocation being referenced has been closed permanently.
ERROR_GRAPHICS_INVALID_ALLOCATION_INSTANCE
0xC0262113
An invalid allocation instance is being referenced.
ERROR_GRAPHICS_INVALID_ALLOCATION_HANDLE
0xC0262114
An invalid allocation handle is being referenced.
ERROR_GRAPHICS_WRONG_ALLOCATION_DEVICE
0xC0262115
The allocation being referenced doesn't belong to the current device.
ERROR_GRAPHICS_ALLOCATION_CONTENT_LOST
0xC0262116
The specified allocation lost its content.
ERROR_GRAPHICS_GPU_EXCEPTION_ON_DEVICE
0xC0262200
GPU exception is detected on the given device. The device is not able to be scheduled.
ERROR_GRAPHICS_SKIP_ALLOCATION_PREPARATION
0x40262201
Skip preparation of allocations referenced by the DMA buffer.
ERROR_GRAPHICS_INVALID_VIDPN_TOPOLOGY
0xC0262300
Specified VidPN topology is invalid.
ERROR_GRAPHICS_VIDPN_TOPOLOGY_NOT_SUPPORTED
0xC0262301
Specified VidPN topology is valid but is not supported by this model of the display adapter.
ERROR_GRAPHICS_VIDPN_TOPOLOGY_CURRENTLY_NOT_SUPPORTED
0xC0262302
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources.
ERROR_GRAPHICS_INVALID_VIDPN
0xC0262303
Specified VidPN handle is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE
0xC0262304
Specified video present source is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET
0xC0262305
Specified video present target is invalid.
ERROR_GRAPHICS_VIDPN_MODALITY_NOT_SUPPORTED
0xC0262306
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).
ERROR_GRAPHICS_MODE_NOT_PINNED
0x00262307
No mode is pinned on the specified VidPN source/target.
ERROR_GRAPHICS_INVALID_VIDPN_SOURCEMODESET
0xC0262308
Specified VidPN source mode set is invalid.
ERROR_GRAPHICS_INVALID_VIDPN_TARGETMODESET
0xC0262309
Specified VidPN target mode set is invalid.
ERROR_GRAPHICS_INVALID_FREQUENCY
0xC026230A
Specified video signal frequency is invalid.
ERROR_GRAPHICS_INVALID_ACTIVE_REGION
0xC026230B
Specified video signal active region is invalid.
ERROR_GRAPHICS_INVALID_TOTAL_REGION
0xC026230C
Specified video signal total region is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE_MODE
0xC0262310
Specified video present source mode is invalid.
ERROR_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET_MODE
0xC0262311
Specified video present target mode is invalid.
ERROR_GRAPHICS_PINNED_MODE_MUST_REMAIN_IN_SET
0xC0262312
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.
ERROR_GRAPHICS_PATH_ALREADY_IN_TOPOLOGY
0xC0262313
Specified video present path is already in VidPN's topology.
ERROR_GRAPHICS_MODE_ALREADY_IN_MODESET
0xC0262314
Specified mode is already in the mode set.
ERROR_GRAPHICS_INVALID_VIDEOPRESENTSOURCESET
0xC0262315
Specified video present source set is invalid.
ERROR_GRAPHICS_INVALID_VIDEOPRESENTTARGETSET
0xC0262316
Specified video present target set is invalid.
ERROR_GRAPHICS_SOURCE_ALREADY_IN_SET
0xC0262317
Specified video present source is already in the video present source set.
ERROR_GRAPHICS_TARGET_ALREADY_IN_SET
0xC0262318
Specified video present target is already in the video present target set.
ERROR_GRAPHICS_INVALID_VIDPN_PRESENT_PATH
0xC0262319
Specified VidPN present path is invalid.
ERROR_GRAPHICS_NO_RECOMMENDED_VIDPN_TOPOLOGY
0xC026231A
Miniport has no recommendation for augmentation of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGESET
0xC026231B
Specified monitor frequency range set is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE
0xC026231C
Specified monitor frequency range is invalid.
ERROR_GRAPHICS_FREQUENCYRANGE_NOT_IN_SET
0xC026231D
Specified frequency range is not in the specified monitor frequency range set.
ERROR_GRAPHICS_NO_PREFERRED_MODE
0x0026231E
Specified mode set does not specify preference for one of its modes.
ERROR_GRAPHICS_FREQUENCYRANGE_ALREADY_IN_SET
0xC026231F
Specified frequency range is already in the specified monitor frequency range set.
ERROR_GRAPHICS_STALE_MODESET
0xC0262320
Specified mode set is stale. Please reacquire the new mode set.
ERROR_GRAPHICS_INVALID_MONITOR_SOURCEMODESET
0xC0262321
Specified monitor source mode set is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_SOURCE_MODE
0xC0262322
Specified monitor source mode is invalid.
ERROR_GRAPHICS_NO_RECOMMENDED_FUNCTIONAL_VIDPN
0xC0262323
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.
ERROR_GRAPHICS_MODE_ID_MUST_BE_UNIQUE
0xC0262324
ID of the specified mode is already used by another mode in the set.
ERROR_GRAPHICS_EMPTY_ADAPTER_MONITOR_MODE_SUPPORT_INTERSECTION
0xC0262325
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.
ERROR_GRAPHICS_VIDEO_PRESENT_TARGETS_LESS_THAN_SOURCES
0xC0262326
Number of video present targets must be greater than or equal to the number of video present sources.
ERROR_GRAPHICS_PATH_NOT_IN_TOPOLOGY
0xC0262327
Specified present path is not in VidPN's topology.
ERROR_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_SOURCE
0xC0262328
Display adapter must have at least one video present source.
ERROR_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_TARGET
0xC0262329
Display adapter must have at least one video present target.
ERROR_GRAPHICS_INVALID_MONITORDESCRIPTORSET
0xC026232A
Specified monitor descriptor set is invalid.
ERROR_GRAPHICS_INVALID_MONITORDESCRIPTOR
0xC026232B
Specified monitor descriptor is invalid.
ERROR_GRAPHICS_MONITORDESCRIPTOR_NOT_IN_SET
0xC026232C
Specified descriptor is not in the specified monitor descriptor set.
ERROR_GRAPHICS_MONITORDESCRIPTOR_ALREADY_IN_SET
0xC026232D
Specified descriptor is already in the specified monitor descriptor set.
ERROR_GRAPHICS_MONITORDESCRIPTOR_ID_MUST_BE_UNIQUE
0xC026232E
ID of the specified monitor descriptor is already used by another descriptor in the set.
ERROR_GRAPHICS_INVALID_VIDPN_TARGET_SUBSET_TYPE
0xC026232F
Specified video present target subset type is invalid.
ERROR_GRAPHICS_RESOURCES_NOT_RELATED
0xC0262330
Two or more of the specified resources are not related to each other, as defined by the interface semantics.
ERROR_GRAPHICS_SOURCE_ID_MUST_BE_UNIQUE
0xC0262331
ID of the specified video present source is already used by another source in the set.
ERROR_GRAPHICS_TARGET_ID_MUST_BE_UNIQUE
0xC0262332
ID of the specified video present target is already used by another target in the set.
ERROR_GRAPHICS_NO_AVAILABLE_VIDPN_TARGET
0xC0262333
Specified VidPN source cannot be used because there is no available VidPN target to connect it to.
ERROR_GRAPHICS_MONITOR_COULD_NOT_BE_ASSOCIATED_WITH_ADAPTER
0xC0262334
Newly arrived monitor could not be associated with a display adapter.
ERROR_GRAPHICS_NO_VIDPNMGR
0xC0262335
Display adapter in question does not have an associated VidPN manager.
ERROR_GRAPHICS_NO_ACTIVE_VIDPN
0xC0262336
VidPN manager of the display adapter in question does not have an active VidPN.
ERROR_GRAPHICS_STALE_VIDPN_TOPOLOGY
0xC0262337
Specified VidPN topology is stale. Please reacquire the new topology.
ERROR_GRAPHICS_MONITOR_NOT_CONNECTED
0xC0262338
There is no monitor connected on the specified video present target.
ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY
0xC0262339
Specified source is not part of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE
0xC026233A
Specified primary surface size is invalid.
ERROR_GRAPHICS_INVALID_VISIBLEREGION_SIZE
0xC026233B
Specified visible region size is invalid.
ERROR_GRAPHICS_INVALID_STRIDE
0xC026233C
Specified stride is invalid.
ERROR_GRAPHICS_INVALID_PIXELFORMAT
0xC026233D
Specified pixel format is invalid.
ERROR_GRAPHICS_INVALID_COLORBASIS
0xC026233E
Specified color basis is invalid.
ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE
0xC026233F
Specified pixel value access mode is invalid.
ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY
0xC0262340
Specified target is not part of the specified VidPN's topology.
ERROR_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT
0xC0262341
Failed to acquire display mode management interface.
ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE
0xC0262342
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it.
ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN
0xC0262343
Specified VidPN is active and cannot be accessed.
ERROR_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL
0xC0262344
Specified VidPN present path importance ordinal is invalid.
ERROR_GRAPHICS_INVALID_PATH_CONTENT_GEOMETRY_TRANSFORMATION
0xC0262345
Specified VidPN present path content geometry transformation is invalid.
ERROR_GRAPHICS_PATH_CONTENT_GEOMETRY_TRANSFORMATION_NOT_SUPPORTED
0xC0262346
Specified content geometry transformation is not supported on the respective VidPN present path.
ERROR_GRAPHICS_INVALID_GAMMA_RAMP
0xC0262347
Specified gamma ramp is invalid.
ERROR_GRAPHICS_GAMMA_RAMP_NOT_SUPPORTED
0xC0262348
Specified gamma ramp is not supported on the respective VidPN present path.
ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED
0xC0262349
Multi-sampling is not supported on the respective VidPN present path.
ERROR_GRAPHICS_MODE_NOT_IN_MODESET
0xC026234A
Specified mode is not in the specified mode set.
ERROR_GRAPHICS_DATASET_IS_EMPTY
0x0026234B
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty.
ERROR_GRAPHICS_NO_MORE_ELEMENTS_IN_DATASET
0x0026234C
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements.
ERROR_GRAPHICS_INVALID_VIDPN_TOPOLOGY_RECOMMENDATION_REASON
0xC026234D
Specified VidPN topology recommendation reason is invalid.
ERROR_GRAPHICS_INVALID_PATH_CONTENT_TYPE
0xC026234E
Specified VidPN present path content type is invalid.
ERROR_GRAPHICS_INVALID_COPYPROTECTION_TYPE
0xC026234F
Specified VidPN present path copy protection type is invalid.
ERROR_GRAPHICS_UNASSIGNED_MODESET_ALREADY_EXISTS
0xC0262350
No more than one unassigned mode set can exist at any given time for a given VidPN source/target.
ERROR_GRAPHICS_PATH_CONTENT_GEOMETRY_TRANSFORMATION_NOT_PINNED
0x00262351
Specified content transformation is not pinned on the specified VidPN present path.
ERROR_GRAPHICS_INVALID_SCANLINE_ORDERING
0xC0262352
Specified scanline ordering type is invalid.
ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED
0xC0262353
Topology changes are not allowed for the specified VidPN.
ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS
0xC0262354
All available importance ordinals are already used in specified topology.
ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT
0xC0262355
Specified primary surface has a different private format attribute than the current primary surface
ERROR_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM
0xC0262356
Specified mode pruning algorithm is invalid
ERROR_GRAPHICS_INVALID_MONITOR_CAPABILITY_ORIGIN
0xC0262357
Specified monitor capability origin is invalid.
ERROR_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE_CONSTRAINT
0xC0262358
Specified monitor frequency range constraint is invalid.
ERROR_GRAPHICS_MAX_NUM_PATHS_REACHED
0xC0262359
Maximum supported number of present paths has been reached.
ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION
0xC026235A
Miniport requested that augmentation be canceled for the specified source of the specified VidPN's topology.
ERROR_GRAPHICS_INVALID_CLIENT_TYPE
0xC026235B
Specified client type was not recognized.
ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET
0xC026235C
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).
ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED
0xC0262400
Specified display adapter child device already has an external device connected to it.
ERROR_GRAPHICS_CHILD_DESCRIPTOR_NOT_SUPPORTED
0xC0262401
Specified display adapter child device does not support descriptor exposure.
ERROR_GRAPHICS_UNKNOWN_CHILD_STATUS
0x4026242F
Child device presence was not reliably detected.
ERROR_GRAPHICS_NOT_A_LINKED_ADAPTER
0xC0262430
The display adapter is not linked to any other adapters.
ERROR_GRAPHICS_LEADLINK_NOT_ENUMERATED
0xC0262431
Lead adapter in a linked configuration was not enumerated yet.
ERROR_GRAPHICS_CHAINLINKS_NOT_ENUMERATED
0xC0262432
Some chain adapters in a linked configuration were not enumerated yet.
ERROR_GRAPHICS_ADAPTER_CHAIN_NOT_READY
0xC0262433
The chain of linked adapters is not ready to start because of an unknown failure.
ERROR_GRAPHICS_CHAINLINKS_NOT_STARTED
0xC0262434
An attempt was made to start a lead link display adapter when the chain links were not started yet.
ERROR_GRAPHICS_CHAINLINKS_NOT_POWERED_ON
0xC0262435
An attempt was made to power up a lead link display adapter when the chain links were powered down.
ERROR_GRAPHICS_INCONSISTENT_DEVICE_LINK_STATE
0xC0262436
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state.
ERROR_GRAPHICS_LEADLINK_START_DEFERRED
0x40262437
Starting the leadlink adapter has been deferred temporarily.
ERROR_GRAPHICS_NOT_POST_DEVICE_DRIVER
0xC0262438
The driver trying to start is not the same as the driver for the POSTed display adapter.
ERROR_GRAPHICS_POLLING_TOO_FREQUENTLY
0x40262439
The display adapter is being polled for children too frequently at the same polling level.
ERROR_GRAPHICS_START_DEFERRED
0x4026243A
Starting the adapter has been deferred temporarily.
ERROR_GRAPHICS_ADAPTER_ACCESS_NOT_EXCLUDED
0xC026243B
An operation is being attempted that requires the display adapter to be in a quiescent state.
ERROR_GRAPHICS_OPM_NOT_SUPPORTED
0xC0262500
The driver does not support OPM.
ERROR_GRAPHICS_COPP_NOT_SUPPORTED
0xC0262501
The driver does not support COPP.
ERROR_GRAPHICS_UAB_NOT_SUPPORTED
0xC0262502
The driver does not support UAB.
ERROR_GRAPHICS_OPM_INVALID_ENCRYPTED_PARAMETERS
0xC0262503
The specified encrypted parameters are invalid.
ERROR_GRAPHICS_OPM_NO_VIDEO_OUTPUTS_EXIST
0xC0262505
The GDI display device passed to this function does not have any active video outputs.
ERROR_GRAPHICS_OPM_INTERNAL_ERROR
0xC026250B
An internal error caused this operation to fail.
ERROR_GRAPHICS_OPM_INVALID_HANDLE
0xC026250C
The function failed because the caller passed in an invalid OPM user mode handle.
ERROR_GRAPHICS_PVP_INVALID_CERTIFICATE_LENGTH
0xC026250E
A certificate could not be returned because the certificate buffer passed to the function was too small.
ERROR_GRAPHICS_OPM_SPANNING_MODE_ENABLED
0xC026250F
A video output could not be created because the frame buffer is in spanning mode.
ERROR_GRAPHICS_OPM_THEATER_MODE_ENABLED
0xC0262510
A video output could not be created because the frame buffer is in theater mode.
ERROR_GRAPHICS_PVP_HFS_FAILED
0xC0262511
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.
ERROR_GRAPHICS_OPM_INVALID_SRM
0xC0262512
The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_HDCP
0xC0262513
The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_ACP
0xC0262514
The video output cannot enable Analog Copy Protection (ACP) because it does not support ACP.
ERROR_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_CGMSA
0xC0262515
The video output cannot enable the Content Generation Management System Analog (CGMS-A) protection technology because it does not support CGMS-A.
ERROR_GRAPHICS_OPM_HDCP_SRM_NEVER_SET
0xC0262516
The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output.
ERROR_GRAPHICS_OPM_RESOLUTION_TOO_HIGH
0xC0262517
The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high.
ERROR_GRAPHICS_OPM_ALL_HDCP_HARDWARE_ALREADY_IN_USE
0xC0262518
The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_NO_LONGER_EXISTS
0xC026251A
The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop.
ERROR_GRAPHICS_OPM_SESSION_TYPE_CHANGE_IN_PROGRESS
0xC026251B
The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS
0xC026251C
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only.
ERROR_GRAPHICS_OPM_INVALID_INFORMATION_REQUEST
0xC026251D
The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
ERROR_GRAPHICS_OPM_DRIVER_INTERNAL_ERROR
0xC026251E
The method failed because an unexpected error occurred inside of a display driver.
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_OPM_SEMANTICS
0xC026251F
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only.
ERROR_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED
0xC0262520
The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.
ERROR_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST
0xC0262521
The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
ERROR_GRAPHICS_I2C_NOT_SUPPORTED
0xC0262580
The monitor connected to the specified video output does not have an I2C bus.
ERROR_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST
0xC0262581
No device on the I2C bus has the specified address.
ERROR_GRAPHICS_I2C_ERROR_TRANSMITTING_DATA
0xC0262582
An error occurred while transmitting data to the device on the I2C bus.
ERROR_GRAPHICS_I2C_ERROR_RECEIVING_DATA
0xC0262583
An error occurred while receiving data from the device on the I2C bus.
ERROR_GRAPHICS_DDCCI_VCP_NOT_SUPPORTED
0xC0262584
The monitor does not support the specified VCP code.
ERROR_GRAPHICS_DDCCI_INVALID_DATA
0xC0262585
The data received from the monitor is invalid.
ERROR_GRAPHICS_DDCCI_MONITOR_RETURNED_INVALID_TIMING_STATUS_BYTE
0xC0262586
The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor.
ERROR_GRAPHICS_MCA_INVALID_CAPABILITIES_STRING
0xC0262587
The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.
ERROR_GRAPHICS_MCA_INTERNAL_ERROR
0xC0262588
An internal Monitor Configuration API error occurred.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_COMMAND
0xC0262589
An operation failed because a DDC/CI message had an invalid value in its command field.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_LENGTH
0xC026258A
An error occurred because the field length of a DDC/CI message contained an invalid value.
ERROR_GRAPHICS_DDCCI_INVALID_MESSAGE_CHECKSUM
0xC026258B
An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer.
ERROR_GRAPHICS_INVALID_PHYSICAL_MONITOR_HANDLE
0xC026258C
This function failed because an invalid monitor handle was passed to it.
ERROR_GRAPHICS_MONITOR_NO_LONGER_EXISTS
0xC026258D
The operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications.
ERROR_GRAPHICS_DDCCI_CURRENT_CURRENT_VALUE_GREATER_THAN_MAXIMUM_VALUE
0xC02625D8
A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value.
ERROR_GRAPHICS_MCA_INVALID_VCP_VERSION
0xC02625D9
The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
ERROR_GRAPHICS_MCA_MONITOR_VIOLATES_MCCS_SPECIFICATION
0xC02625DA
The monitor does not comply with the MCCS specification it claims to support.
ERROR_GRAPHICS_MCA_MCCS_VERSION_MISMATCH
0xC02625DB
The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
ERROR_GRAPHICS_MCA_UNSUPPORTED_MCCS_VERSION
0xC02625DC
The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_MCA_INVALID_TECHNOLOGY_TYPE_RETURNED
0xC02625DE
The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_MCA_UNSUPPORTED_COLOR_TEMPERATURE
0xC02625DF
SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
ERROR_GRAPHICS_ONLY_CONSOLE_SESSION_SUPPORTED
0xC02625E0
This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session.
ERROR_GRAPHICS_NO_DISPLAY_DEVICE_CORRESPONDS_TO_NAME
0xC02625E1
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.
ERROR_GRAPHICS_DISPLAY_DEVICE_NOT_ATTACHED_TO_DESKTOP
0xC02625E2
The function failed because the specified GDI display device was not attached to the Windows desktop.
ERROR_GRAPHICS_MIRRORING_DEVICES_NOT_SUPPORTED
0xC02625E3
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.
ERROR_GRAPHICS_INVALID_POINTER
0xC02625E4
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned.
ERROR_GRAPHICS_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE
0xC02625E5
The function failed because the specified GDI device did not have any monitors associated with it.
ERROR_GRAPHICS_PARAMETER_ARRAY_TOO_SMALL
0xC02625E6
An array passed to the function cannot hold all of the data that the function must copy into the array.
ERROR_GRAPHICS_INTERNAL_ERROR
0xC02625E7
An internal error caused an operation to fail.
ERROR_GRAPHICS_SESSION_TYPE_CHANGE_IN_PROGRESS
0xC02605E8
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote.
登録:
投稿 (Atom)
--
注目の投稿
【重要】[共用サーバーSD / お名前メール] PHPの脆弱性への弊社対応のお知らせ (掲載開始日:2026/10/23)
【外部リンク】 https://www.onamae.com/news/article/11596 【重要】[共用サーバーSD / お名前メール] PHPの脆弱性への弊社対応のお知らせ (掲載開始日:2026/10/23) お名前.com レンタルサーバーをご利用いただ...
人気の投稿
-
【外部リンク】 https://help.onamae.com/answer/9103 ただいまメンテナンス作業中です。 大変恐れ入りますが、メンテナンス終了まで今しばらくお待ちくださいますようお願い申し上げます。 System Maintenance Underway...
-
n117 データアクセスに制限がかかっています PS Vita エラーコード「N117」の解説:データアクセス制限の原因と解決策 PS Vitaを使用中に突然表示される「N117(データアクセスに制限がかかっています)」というエラー。これは主に、ネットワーク通信やPlay...
-
テクニカルサポート詐欺に注意!PS VitaやPCを守るための防衛術 「PCのウイルスを検出しました」「システムが破損しています」といった警告音とともに画面に表示される警告メッセージ。これらは、ユーザーをパニックにさせて高額なサポート料金や個人情報を搾取しようとする「テクニカルサ...
-
PS Vita / PS Vita TV のエラーコード PS Vita / PS Vita TV エラーコード完全ガイド:原因と解決策まとめ 1. ネットワーク・接続関連のエラー もっとも多いのが、PlayStation™Network(PSN)への接続や通信に関するエラー...
-
au ID セッションタイムアウトになりました。再度接続してください。(CCAE0003) ※何度も、このエラーが表示される場合は、ご利用のブラウザでCookieを受け入れる設定に変更を行ってください。 【外部リンク】 https://id.auone.jp/age/...