0xC0000451 STATUS_AMBIGUOUS_SYSTEM_DEVICE |
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
|
0xC0000452 STATUS_SYSTEM_DEVICE_NOT_FOUND |
The requested system device cannot be found. |
|
0xC0000453 STATUS_RESTART_BOOT_APPLICATION |
This boot application must be restarted. |
|
0xC0000454 STATUS_INSUFFICIENT_NVRAM_RESOURCES |
Insufficient NVRAM resources exist to complete the API. A reboot might be required. |
|
0xC0000460 STATUS_NO_RANGES_PROCESSED |
No ranges for the specified operation were able to be processed. |
|
0xC0000463 STATUS_DEVICE_FEATURE_NOT_SUPPORTED |
The storage device does not support Offload Write. |
|
0xC0000464 STATUS_DEVICE_UNREACHABLE |
Data cannot be moved because the source device cannot communicate with the destination device. |
|
0xC0000465 STATUS_INVALID_TOKEN |
The token representing the data is invalid or expired. |
|
0xC0000466 STATUS_SERVER_UNAVAILABLE |
The file server is temporarily unavailable. |
|
0xC0000500 STATUS_INVALID_TASK_NAME |
The specified task name is invalid. |
|
0xC0000501 STATUS_INVALID_TASK_INDEX |
The specified task index is invalid. |
|
0xC0000502 STATUS_THREAD_ALREADY_IN_TASK |
The specified thread is already joining a task. |
|
0xC0000503 STATUS_CALLBACK_BYPASS |
A callback has requested to bypass native code. |
|
0xC0000602 STATUS_FAIL_FAST_EXCEPTION |
A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
|
0xC0000603 STATUS_IMAGE_CERT_REVOKED |
Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked. |
|
0xC0000700 STATUS_PORT_CLOSED |
The ALPC port is closed. |
|
0xC0000701 STATUS_MESSAGE_LOST |
The ALPC message requested is no longer available. |
|
0xC0000702 STATUS_INVALID_MESSAGE |
The ALPC message supplied is invalid. |
|
0xC0000703 STATUS_REQUEST_CANCELED |
The ALPC message has been canceled. |
|
0xC0000704 STATUS_RECURSIVE_DISPATCH |
Invalid recursive dispatch attempt. |
|
0xC0000705 STATUS_LPC_RECEIVE_BUFFER_EXPECTED |
No receive buffer has been supplied in a synchronous request. |
|
0xC0000706 STATUS_LPC_INVALID_CONNECTION_USAGE |
The connection port is used in an invalid context. |
|
0xC0000707 STATUS_LPC_REQUESTS_NOT_ALLOWED |
The ALPC port does not accept new request messages. |
|
0xC0000708 STATUS_RESOURCE_IN_USE |
The resource requested is already in use. |
|
0xC0000709 STATUS_HARDWARE_MEMORY_ERROR |
The hardware has reported an uncorrectable memory error. |
|
0xC000070A STATUS_THREADPOOL_HANDLE_EXCEPTION |
Status 0x%08x was returned, waiting on handle 0x%x for wait 0x%p, in waiter 0x%p. |
|
0xC000070B STATUS_THREADPOOL_SET_EVENT_ON_COMPLETION_FAILED |
After a callback to 0x%p(0x%p), a completion call to Set event(0x%p) failed with status 0x%08x. |
|
0xC000070C STATUS_THREADPOOL_RELEASE_SEMAPHORE_ON_COMPLETION_FAILED |
After a callback to 0x%p(0x%p), a completion call to ReleaseSemaphore(0x%p, %d) failed with status 0x%08x. |
|
0xC000070D STATUS_THREADPOOL_RELEASE_MUTEX_ON_COMPLETION_FAILED |
After a callback to 0x%p(0x%p), a completion call to ReleaseMutex(%p) failed with status 0x%08x. |
|
0xC000070E STATUS_THREADPOOL_FREE_LIBRARY_ON_COMPLETION_FAILED |
After a callback to 0x%p(0x%p), a completion call to FreeLibrary(%p) failed with status 0x%08x. |
|
0xC000070F STATUS_THREADPOOL_RELEASED_DURING_OPERATION |
The thread pool 0x%p was released while a thread was posting a callback to 0x%p(0x%p) to it. |
|
0xC0000710 STATUS_CALLBACK_RETURNED_WHILE_IMPERSONATING |
A thread pool worker thread is impersonating a client, after a callback to 0x%p(0x%p). This is unexpected, indicating that the callback is missing a call to revert the impersonation. |
|
0xC0000711 STATUS_APC_RETURNED_WHILE_IMPERSONATING |
A thread pool worker thread is impersonating a client, after executing an APC. This is unexpected, indicating that the APC is missing a call to revert the impersonation. |
|
0xC0000712 STATUS_PROCESS_IS_PROTECTED |
Either the target process, or the target thread's containing process, is a protected process. |
|
0xC0000713 STATUS_MCA_EXCEPTION |
A thread is getting dispatched with MCA EXCEPTION because of MCA. |
|
0xC0000714 STATUS_CERTIFICATE_MAPPING_NOT_UNIQUE |
The client certificate account mapping is not unique. |
|
0xC0000715 STATUS_SYMLINK_CLASS_DISABLED |
The symbolic link cannot be followed because its type is disabled. |
|
0xC0000716 STATUS_INVALID_IDN_NORMALIZATION |
Indicates that the specified string is not valid for IDN normalization. |
|
0xC0000717 STATUS_NO_UNICODE_TRANSLATION |
No mapping for the Unicode character exists in the target multi-byte code page. |
|
0xC0000718 STATUS_ALREADY_REGISTERED |
The provided callback is already registered. |
|
0xC0000719 STATUS_CONTEXT_MISMATCH |
The provided context did not match the target. |
|
0xC000071A STATUS_PORT_ALREADY_HAS_COMPLETION_LIST |
The specified port already has a completion list. |
|
0xC000071B STATUS_CALLBACK_RETURNED_THREAD_PRIORITY |
A threadpool worker thread entered a callback at thread base priority 0x%x and exited at priority 0x%x. This is unexpected, indicating that the callback missed restoring the priority. |
|
0xC000071C STATUS_INVALID_THREAD |
An invalid thread, handle %p, is specified for this operation. Possibly, a threadpool worker thread was specified. |
|
0xC000071D STATUS_CALLBACK_RETURNED_TRANSACTION |
A threadpool worker thread entered a callback, which left transaction state. This is unexpected, indicating that the callback missed clearing the transaction. |
|
0xC000071E STATUS_CALLBACK_RETURNED_LDR_LOCK |
A threadpool worker thread entered a callback, which left the loader lock held. This is unexpected, indicating that the callback missed releasing the lock. |
|
0xC000071F STATUS_CALLBACK_RETURNED_LANG |
A threadpool worker thread entered a callback, which left with preferred languages set. This is unexpected, indicating that the callback missed clearing them. |
|
0xC0000720 STATUS_CALLBACK_RETURNED_PRI_BACK |
A threadpool worker thread entered a callback, which left with background priorities set. This is unexpected, indicating that the callback missed restoring the original priorities. |
|
0xC0000800 STATUS_DISK_REPAIR_DISABLED |
The attempted operation required self healing to be enabled. |
|
0xC0000801 STATUS_DS_DOMAIN_RENAME_IN_PROGRESS |
The directory service cannot perform the requested operation because a domain rename operation is in progress. |
|
0xC0000802 STATUS_DISK_QUOTA_EXCEEDED |
An operation failed because the storage quota was exceeded. |
|
0xC0000804 STATUS_CONTENT_BLOCKED |
An operation failed because the content was blocked. |
|
0xC0000805 STATUS_BAD_CLUSTERS |
The operation could not be completed due to bad clusters on disk. |
|
0xC0000806 STATUS_VOLUME_DIRTY |
The operation could not be completed because the volume is dirty. Please run the Chkdsk utility and try again. |
|
0xC0000901 STATUS_FILE_CHECKED_OUT |
This file is checked out or locked for editing by another user. |
|
0xC0000902 STATUS_CHECKOUT_REQUIRED |
The file must be checked out before saving changes. |
|
0xC0000903 STATUS_BAD_FILE_TYPE |
The file type being saved or retrieved has been blocked. |
|
0xC0000904 STATUS_FILE_TOO_LARGE |
The file size exceeds the limit allowed and cannot be saved. |
|
0xC0000905 STATUS_FORMS_AUTH_REQUIRED |
Access Denied. Before opening files in this location, you must first browse to the e.g. site and select the option to log on automatically. |
|
0xC0000906 STATUS_VIRUS_INFECTED |
The operation did not complete successfully because the file contains a virus. |
|
0xC0000907 STATUS_VIRUS_DELETED |
This file contains a virus and cannot be opened. Due to the nature of this virus, the file has been removed from this location. |
|
0xC0000908 STATUS_BAD_MCFG_TABLE |
The resources required for this device conflict with the MCFG table. |
|
0xC0000909 STATUS_CANNOT_BREAK_OPLOCK |
The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken. |
|
0xC0009898 STATUS_WOW_ASSERTION |
WOW Assertion Error. |
|
0xC000A000 STATUS_INVALID_SIGNATURE |
The cryptographic signature is invalid. |
|
0xC000A001 STATUS_HMAC_NOT_SUPPORTED |
The cryptographic provider does not support HMAC. |
|
0xC000A010 STATUS_IPSEC_QUEUE_OVERFLOW |
The IPsec queue overflowed. |
|
0xC000A011 STATUS_ND_QUEUE_OVERFLOW |
The neighbor discovery queue overflowed. |
|
0xC000A012 STATUS_HOPLIMIT_EXCEEDED |
An Internet Control Message Protocol (ICMP) hop limit exceeded error was received. |
|
0xC000A013 STATUS_PROTOCOL_NOT_SUPPORTED |
The protocol is not installed on the local machine. |
|
0xC000A080 STATUS_LOST_WRITEBEHIND_DATA_NETWORK_DISCONNECTED |
{Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error might be caused by network connectivity issues. Try to save this file elsewhere. |
|
0xC000A081 STATUS_LOST_WRITEBEHIND_DATA_NETWORK_SERVER_ERROR |
{Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error was returned by the server on which the file exists. Try to save this file elsewhere. |
|
0xC000A082 STATUS_LOST_WRITEBEHIND_DATA_LOCAL_DISK_ERROR |
{Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error might be caused if the device has been removed or the media is write-protected. |
|
0xC000A083 STATUS_XML_PARSE_ERROR |
Windows was unable to parse the requested XML data. |
|
0xC000A084 STATUS_XMLDSIG_ERROR |
An error was encountered while processing an XML digital signature. |
|
0xC000A085 STATUS_WRONG_COMPARTMENT |
This indicates that the caller made the connection request in the wrong routing compartment. |
|
0xC000A086 STATUS_AUTHIP_FAILURE |
This indicates that there was an AuthIP failure when attempting to connect to the remote host. |
|
0xC000A087 STATUS_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS |
OID mapped groups cannot have members. |
|
0xC000A088 STATUS_DS_OID_NOT_FOUND |
The specified OID cannot be found. |
|
0xC000A100 STATUS_HASH_NOT_SUPPORTED |
Hash generation for the specified version and hash type is not enabled on server. |
|
0xC000A101 STATUS_HASH_NOT_PRESENT |
The hash requests is not present or not up to date with the current file contents. |
|
0xC000A2A1 STATUS_OFFLOAD_READ_FLT_NOT_SUPPORTED |
A file system filter on the server has not opted in for Offload Read support. |
|
0xC000A2A2 STATUS_OFFLOAD_WRITE_FLT_NOT_SUPPORTED |
A file system filter on the server has not opted in for Offload Write support. |
|
0xC000A2A3 STATUS_OFFLOAD_READ_FILE_NOT_SUPPORTED |
Offload read operations cannot be performed on:
|
|
0xC000A2A4 STATUS_OFFLOAD_WRITE_FILE_NOT_SUPPORTED |
Offload write operations cannot be performed on:
|
|
0xC0010001 DBG_NO_STATE_CHANGE |
The debugger did not perform a state change. |
|
0xC0010002 DBG_APP_NOT_IDLE |
The debugger found that the application is not idle. |
|
0xC0020001 RPC_NT_INVALID_STRING_BINDING |
The string binding is invalid. |
|
0xC0020002 RPC_NT_WRONG_KIND_OF_BINDING |
The binding handle is not the correct type. |
|
0xC0020003 RPC_NT_INVALID_BINDING |
The binding handle is invalid. |
|
0xC0020004 RPC_NT_PROTSEQ_NOT_SUPPORTED |
The RPC protocol sequence is not supported. |
|
0xC0020005 RPC_NT_INVALID_RPC_PROTSEQ |
The RPC protocol sequence is invalid. |
|
0xC0020006 RPC_NT_INVALID_STRING_UUID |
The string UUID is invalid. |
|
0xC0020007 RPC_NT_INVALID_ENDPOINT_FORMAT |
The endpoint format is invalid. |
|
0xC0020008 RPC_NT_INVALID_NET_ADDR |
The network address is invalid. |
|
0xC0020009 RPC_NT_NO_ENDPOINT_FOUND |
No endpoint was found. |
|
0xC002000A RPC_NT_INVALID_TIMEOUT |
The time-out value is invalid. |
|
0xC002000B RPC_NT_OBJECT_NOT_FOUND |
The object UUID was not found. |
|
0xC002000C RPC_NT_ALREADY_REGISTERED |
The object UUID has already been registered. |
|
0xC002000D RPC_NT_TYPE_ALREADY_REGISTERED |
The type UUID has already been registered. |
|
0xC002000E RPC_NT_ALREADY_LISTENING |
The RPC server is already listening. |
|
0xC002000F RPC_NT_NO_PROTSEQS_REGISTERED |
No protocol sequences have been registered. |
|
0xC0020010 RPC_NT_NOT_LISTENING |
The RPC server is not listening. |
|
0xC0020011 RPC_NT_UNKNOWN_MGR_TYPE |
The manager type is unknown. |
|
0xC0020012 RPC_NT_UNKNOWN_IF |
The interface is unknown. |
|
0xC0020013 RPC_NT_NO_BINDINGS |
There are no bindings. |
|
0xC0020014 RPC_NT_NO_PROTSEQS |
There are no protocol sequences. |
|
0xC0020015 RPC_NT_CANT_CREATE_ENDPOINT |
The endpoint cannot be created. |
|
0xC0020016 RPC_NT_OUT_OF_RESOURCES |
Insufficient resources are available to complete this operation. |
|
0xC0020017 RPC_NT_SERVER_UNAVAILABLE |
The RPC server is unavailable. |
|
0xC0020018 RPC_NT_SERVER_TOO_BUSY |
The RPC server is too busy to complete this operation. |
|
0xC0020019 RPC_NT_INVALID_NETWORK_OPTIONS |
The network options are invalid. |
|
0xC002001A RPC_NT_NO_CALL_ACTIVE |
No RPCs are active on this thread. |
|
0xC002001B RPC_NT_CALL_FAILED |
The RPC failed. |
|
0xC002001C RPC_NT_CALL_FAILED_DNE |
The RPC failed and did not execute. |
|
0xC002001D RPC_NT_PROTOCOL_ERROR |
An RPC protocol error occurred. |
|
0xC002001F RPC_NT_UNSUPPORTED_TRANS_SYN |
The RPC server does not support the transfer syntax. |
|
0xC0020021 RPC_NT_UNSUPPORTED_TYPE |
The type UUID is not supported. |
|
0xC0020022 RPC_NT_INVALID_TAG |
The tag is invalid. |
|
0xC0020023 RPC_NT_INVALID_BOUND |
The array bounds are invalid. |
|
0xC0020024 RPC_NT_NO_ENTRY_NAME |
The binding does not contain an entry name. |
|
0xC0020025 RPC_NT_INVALID_NAME_SYNTAX |
The name syntax is invalid. |
|
0xC0020026 RPC_NT_UNSUPPORTED_NAME_SYNTAX |
The name syntax is not supported. |
|
0xC0020028 RPC_NT_UUID_NO_ADDRESS |
No network address is available to construct a UUID. |
|
0xC0020029 RPC_NT_DUPLICATE_ENDPOINT |
The endpoint is a duplicate. |
|
0xC002002A RPC_NT_UNKNOWN_AUTHN_TYPE |
The authentication type is unknown. |
|
0xC002002B RPC_NT_MAX_CALLS_TOO_SMALL |
The maximum number of calls is too small. |
|
0xC002002C RPC_NT_STRING_TOO_LONG |
The string is too long. |
|
0xC002002D RPC_NT_PROTSEQ_NOT_FOUND |
The RPC protocol sequence was not found. |
|
0xC002002E RPC_NT_PROCNUM_OUT_OF_RANGE |
The procedure number is out of range. |
|
0xC002002F RPC_NT_BINDING_HAS_NO_AUTH |
The binding does not contain any authentication information. |
|
0xC0020030 RPC_NT_UNKNOWN_AUTHN_SERVICE |
The authentication service is unknown. |
|
0xC0020031 RPC_NT_UNKNOWN_AUTHN_LEVEL |
The authentication level is unknown. |
|
0xC0020032 RPC_NT_INVALID_AUTH_IDENTITY |
The security context is invalid. |
|
0xC0020033 RPC_NT_UNKNOWN_AUTHZ_SERVICE |
The authorization service is unknown. |
|
0xC0020034 EPT_NT_INVALID_ENTRY |
The entry is invalid. |
|
0xC0020035 EPT_NT_CANT_PERFORM_OP |
The operation cannot be performed. |
|
0xC0020036 EPT_NT_NOT_REGISTERED |
No more endpoints are available from the endpoint mapper. |
|
0xC0020037 RPC_NT_NOTHING_TO_EXPORT |
No interfaces have been exported. |
|
0xC0020038 RPC_NT_INCOMPLETE_NAME |
The entry name is incomplete. |
|
0xC0020039 RPC_NT_INVALID_VERS_OPTION |
The version option is invalid. |
|
0xC002003A RPC_NT_NO_MORE_MEMBERS |
There are no more members. |
|
0xC002003B RPC_NT_NOT_ALL_OBJS_UNEXPORTED |
There is nothing to unexport. |
|
0xC002003C RPC_NT_INTERFACE_NOT_FOUND |
The interface was not found. |
|
0xC002003D RPC_NT_ENTRY_ALREADY_EXISTS |
The entry already exists. |
|
0xC002003E RPC_NT_ENTRY_NOT_FOUND |
The entry was not found. |
|
0xC002003F RPC_NT_NAME_SERVICE_UNAVAILABLE |
The name service is unavailable. |
|
0xC0020040 RPC_NT_INVALID_NAF_ID |
The network address family is invalid. |
|
0xC0020041 RPC_NT_CANNOT_SUPPORT |
The requested operation is not supported. |
|
0xC0020042 RPC_NT_NO_CONTEXT_AVAILABLE |
No security context is available to allow impersonation. |
|
0xC0020043 RPC_NT_INTERNAL_ERROR |
An internal error occurred in the RPC. |
|
0xC0020044 RPC_NT_ZERO_DIVIDE |
The RPC server attempted to divide an integer by zero. |
|
0xC0020045 RPC_NT_ADDRESS_ERROR |
An addressing error occurred in the RPC server. |
|
0xC0020046 RPC_NT_FP_DIV_ZERO |
A floating point operation at the RPC server caused a divide by zero. |
|
0xC0020047 RPC_NT_FP_UNDERFLOW |
A floating point underflow occurred at the RPC server. |
|
0xC0020048 RPC_NT_FP_OVERFLOW |
A floating point overflow occurred at the RPC server. |
|
0xC0020049 RPC_NT_CALL_IN_PROGRESS |
An RPC is already in progress for this thread. |
|
0xC002004A RPC_NT_NO_MORE_BINDINGS |
There are no more bindings. |
|
0xC002004B RPC_NT_GROUP_MEMBER_NOT_FOUND |
The group member was not found. |
|
0xC002004C EPT_NT_CANT_CREATE |
The endpoint mapper database entry could not be created. |
|
0xC002004D RPC_NT_INVALID_OBJECT |
The object UUID is the nil UUID. |
|
0xC002004F RPC_NT_NO_INTERFACES |
No interfaces have been registered. |
|
0xC0020050 RPC_NT_CALL_CANCELLED |
The RPC was canceled. |
|
0xC0020051 RPC_NT_BINDING_INCOMPLETE |
The binding handle does not contain all the required information. |
|
0xC0020052 RPC_NT_COMM_FAILURE |
A communications failure occurred during an RPC. |
|
0xC0020053 RPC_NT_UNSUPPORTED_AUTHN_LEVEL |
The requested authentication level is not supported. |
|
0xC0020054 RPC_NT_NO_PRINC_NAME |
No principal name was registered. |
|
0xC0020055 RPC_NT_NOT_RPC_ERROR |
The error specified is not a valid Windows RPC error code. |
|
0xC0020057 RPC_NT_SEC_PKG_ERROR |
A security package-specific error occurred. |
|
0xC0020058 RPC_NT_NOT_CANCELLED |
The thread was not canceled. |
|
0xC0020062 RPC_NT_INVALID_ASYNC_HANDLE |
Invalid asynchronous RPC handle. |
|
0xC0020063 RPC_NT_INVALID_ASYNC_CALL |
Invalid asynchronous RPC call handle for this operation. |
|
0xC0020064 RPC_NT_PROXY_ACCESS_DENIED |
Access to the HTTP proxy is denied. |
|
0xC0030001 RPC_NT_NO_MORE_ENTRIES |
The list of RPC servers available for auto-handle binding has been exhausted. |
|
0xC0030002 RPC_NT_SS_CHAR_TRANS_OPEN_FAIL |
The file designated by DCERPCCHARTRANS cannot be opened. |
|
0xC0030003 RPC_NT_SS_CHAR_TRANS_SHORT_FILE |
The file containing the character translation table has fewer than 512 bytes. |
|
0xC0030004 RPC_NT_SS_IN_NULL_CONTEXT |
A null context handle is passed as an [in] parameter. |
|
0xC0030005 RPC_NT_SS_CONTEXT_MISMATCH |
The context handle does not match any known context handles. |
|
0xC0030006 RPC_NT_SS_CONTEXT_DAMAGED |
The context handle changed during a call. |
|
0xC0030007 RPC_NT_SS_HANDLES_MISMATCH |
The binding handles passed to an RPC do not match. |
|
0xC0030008 RPC_NT_SS_CANNOT_GET_CALL_HANDLE |
The stub is unable to get the call handle. |
|
0xC0030009 RPC_NT_NULL_REF_POINTER |
A null reference pointer was passed to the stub. |
|
0xC003000A RPC_NT_ENUM_VALUE_OUT_OF_RANGE |
The enumeration value is out of range. |
|
0xC003000B RPC_NT_BYTE_COUNT_TOO_SMALL |
The byte count is too small. |
|
0xC003000C RPC_NT_BAD_STUB_DATA |
The stub received bad data. |
|
0xC0030059 RPC_NT_INVALID_ES_ACTION |
Invalid operation on the encoding/decoding handle. |
|
0xC003005A RPC_NT_WRONG_ES_VERSION |
Incompatible version of the serializing package. |
|
0xC003005B RPC_NT_WRONG_STUB_VERSION |
Incompatible version of the RPC stub. |
|
0xC003005C RPC_NT_INVALID_PIPE_OBJECT |
The RPC pipe object is invalid or corrupt. |
|
0xC003005D RPC_NT_INVALID_PIPE_OPERATION |
An invalid operation was attempted on an RPC pipe object. |
|
0xC003005E RPC_NT_WRONG_PIPE_VERSION |
Unsupported RPC pipe version. |
|
0xC003005F RPC_NT_PIPE_CLOSED |
The RPC pipe object has already been closed. |
|
0xC0030060 RPC_NT_PIPE_DISCIPLINE_ERROR |
The RPC call completed before all pipes were processed. |
|
0xC0030061 RPC_NT_PIPE_EMPTY |
No more data is available from the RPC pipe. |
|
0xC0040035 STATUS_PNP_BAD_MPS_TABLE |
A device is missing in the system BIOS MPS table. This device will not be used. Contact your system vendor for a system BIOS update. |
|
0xC0040036 STATUS_PNP_TRANSLATION_FAILED |
A translator failed to translate resources. |
|
0xC0040037 STATUS_PNP_IRQ_TRANSLATION_FAILED |
An IRQ translator failed to translate resources. |
|
0xC0040038 STATUS_PNP_INVALID_ID |
Driver %2 returned an invalid ID for a child device (%3). |
|
0xC0040039 STATUS_IO_REISSUE_AS_CACHED |
Reissue the given operation as a cached I/O operation |
|
0xC00A0001 STATUS_CTX_WINSTATION_NAME_INVALID |
Session name %1 is invalid. |
|
0xC00A0002 STATUS_CTX_INVALID_PD |
The protocol driver %1 is invalid. |
|
0xC00A0003 STATUS_CTX_PD_NOT_FOUND |
The protocol driver %1 was not found in the system path. |
|
0xC00A0006 STATUS_CTX_CLOSE_PENDING |
A close operation is pending on the terminal connection. |
|
0xC00A0007 STATUS_CTX_NO_OUTBUF |
No free output buffers are available. |
|
0xC00A0008 STATUS_CTX_MODEM_INF_NOT_FOUND |
The MODEM.INF file was not found. |
|
0xC00A0009 STATUS_CTX_INVALID_MODEMNAME |
The modem (%1) was not found in the MODEM.INF file. |
|
0xC00A000A STATUS_CTX_RESPONSE_ERROR |
The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem. |
|
0xC00A000B STATUS_CTX_MODEM_RESPONSE_TIMEOUT |
The modem did not respond to the command sent to it. Verify that the modem cable is properly attached and the modem is turned on. |
|
0xC00A000C STATUS_CTX_MODEM_RESPONSE_NO_CARRIER |
Carrier detection has failed or the carrier has been dropped due to disconnection. |
|
0xC00A000D STATUS_CTX_MODEM_RESPONSE_NO_DIALTONE |
A dial tone was not detected within the required time. Verify that the phone cable is properly attached and functional. |
|
0xC00A000E STATUS_CTX_MODEM_RESPONSE_BUSY |
A busy signal was detected at a remote site on callback. |
|
0xC00A000F STATUS_CTX_MODEM_RESPONSE_VOICE |
A voice was detected at a remote site on callback. |
|
0xC00A0010 STATUS_CTX_TD_ERROR |
Transport driver error. |
|
0xC00A0012 STATUS_CTX_LICENSE_CLIENT_INVALID |
The client you are using is not licensed to use this system. Your logon request is denied. |
|
0xC00A0013 STATUS_CTX_LICENSE_NOT_AVAILABLE |
The system has reached its licensed logon limit. Try again later. |
|
0xC00A0014 STATUS_CTX_LICENSE_EXPIRED |
The system license has expired. Your logon request is denied. |
|
0xC00A0015 STATUS_CTX_WINSTATION_NOT_FOUND |
The specified session cannot be found. |
|
0xC00A0016 STATUS_CTX_WINSTATION_NAME_COLLISION |
The specified session name is already in use. |
|
0xC00A0017 STATUS_CTX_WINSTATION_BUSY |
The requested operation cannot be completed because the terminal connection is currently processing a connect, disconnect, reset, or delete operation. |
|
0xC00A0018 STATUS_CTX_BAD_VIDEO_MODE |
An attempt has been made to connect to a session whose video mode is not supported by the current client. |
|
0xC00A0022 STATUS_CTX_GRAPHICS_INVALID |
The application attempted to enable DOS graphics mode. DOS graphics mode is not supported. |
|
0xC00A0024 STATUS_CTX_NOT_CONSOLE |
The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access. |
|
0xC00A0026 STATUS_CTX_CLIENT_QUERY_TIMEOUT |
The client failed to respond to the server connect message. |
|
0xC00A0027 STATUS_CTX_CONSOLE_DISCONNECT |
Disconnecting the console session is not supported. |
|
0xC00A0028 STATUS_CTX_CONSOLE_CONNECT |
Reconnecting a disconnected session to the console is not supported. |
|
0xC00A002A STATUS_CTX_SHADOW_DENIED |
The request to control another session remotely was denied. |
|
0xC00A002B STATUS_CTX_WINSTATION_ACCESS_DENIED |
A process has requested access to a session, but has not been granted those access rights. |
|
0xC00A002E STATUS_CTX_INVALID_WD |
The terminal connection driver %1 is invalid. |
|
0xC00A002F STATUS_CTX_WD_NOT_FOUND |
The terminal connection driver %1 was not found in the system path. |
|
0xC00A0030 STATUS_CTX_SHADOW_INVALID |
The requested session cannot be controlled remotely. You cannot control your own session, a session that is trying to control your session, a session that has no user logged on, or other sessions from the console. |
|
0xC00A0031 STATUS_CTX_SHADOW_DISABLED |
The requested session is not configured to allow remote control. |
|
0xC00A0032 STATUS_RDP_PROTOCOL_ERROR |
The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
|
0xC00A0033 STATUS_CTX_CLIENT_LICENSE_NOT_SET |
Your request to connect to this terminal server has been rejected. Your terminal server client license number has not been entered for this copy of the terminal client. Contact your system administrator for help in entering a valid, unique license number for this terminal server client. Click OK to continue. |
|
0xC00A0034 STATUS_CTX_CLIENT_LICENSE_IN_USE |
Your request to connect to this terminal server has been rejected. Your terminal server client license number is currently being used by another user. Contact your system administrator to obtain a new copy of the terminal server client with a valid, unique license number. Click OK to continue. |
|
0xC00A0035 STATUS_CTX_SHADOW_ENDED_BY_MODE_CHANGE |
The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported. |
|
0xC00A0036 STATUS_CTX_SHADOW_NOT_RUNNING |
Remote control could not be terminated because the specified session is not currently being remotely controlled. |
|
0xC00A0037 STATUS_CTX_LOGON_DISABLED |
Your interactive logon privilege has been disabled. Contact your system administrator. |
|
0xC00A0038 STATUS_CTX_SECURITY_LAYER_ERROR |
The terminal server security layer detected an error in the protocol stream and has disconnected the client. |
|
0xC00A0039 STATUS_TS_INCOMPATIBLE_SESSIONS |
The target session is incompatible with the current session. |
|
0xC00B0001 STATUS_MUI_FILE_NOT_FOUND |
The resource loader failed to find an MUI file. |
|
0xC00B0002 STATUS_MUI_INVALID_FILE |
The resource loader failed to load an MUI file because the file failed to pass validation. |
|
0xC00B0003 STATUS_MUI_INVALID_RC_CONFIG |
The RC manifest is corrupted with garbage data, is an unsupported version, or is missing a required item. |
|
0xC00B0004 STATUS_MUI_INVALID_LOCALE_NAME |
The RC manifest has an invalid culture name. |
|
0xC00B0005 STATUS_MUI_INVALID_ULTIMATEFALLBACK_NAME |
The RC manifest has and invalid ultimate fallback name. |
|
0xC00B0006 STATUS_MUI_FILE_NOT_LOADED |
The resource loader cache does not have a loaded MUI entry. |
|
0xC00B0007 STATUS_RESOURCE_ENUM_USER_STOP |
The user stopped resource enumeration. |
|
0xC0130001 STATUS_CLUSTER_INVALID_NODE |
The cluster node is not valid. |
|
0xC0130002 STATUS_CLUSTER_NODE_EXISTS |
The cluster node already exists. |
|
0xC0130003 STATUS_CLUSTER_JOIN_IN_PROGRESS |
A node is in the process of joining the cluster. |
|
0xC0130004 STATUS_CLUSTER_NODE_NOT_FOUND |
The cluster node was not found. |
|
0xC0130005 STATUS_CLUSTER_LOCAL_NODE_NOT_FOUND |
The cluster local node information was not found. |
|
0xC0130006 STATUS_CLUSTER_NETWORK_EXISTS |
The cluster network already exists. |
|
0xC0130007 STATUS_CLUSTER_NETWORK_NOT_FOUND |
The cluster network was not found. |
|
0xC0130008 STATUS_CLUSTER_NETINTERFACE_EXISTS |
The cluster network interface already exists. |
|
0xC0130009 STATUS_CLUSTER_NETINTERFACE_NOT_FOUND |
The cluster network interface was not found. |
|
0xC013000A STATUS_CLUSTER_INVALID_REQUEST |
The cluster request is not valid for this object. |
|
0xC013000B STATUS_CLUSTER_INVALID_NETWORK_PROVIDER |
The cluster network provider is not valid. |
|
0xC013000C STATUS_CLUSTER_NODE_DOWN |
The cluster node is down. |
|
0xC013000D STATUS_CLUSTER_NODE_UNREACHABLE |
The cluster node is not reachable. |
|
0xC013000E STATUS_CLUSTER_NODE_NOT_MEMBER |
The cluster node is not a member of the cluster. |
|
0xC013000F STATUS_CLUSTER_JOIN_NOT_IN_PROGRESS |
A cluster join operation is not in progress. |
|
0xC0130010 STATUS_CLUSTER_INVALID_NETWORK |
The cluster network is not valid. |
|
0xC0130011 STATUS_CLUSTER_NO_NET_ADAPTERS |
No network adapters are available. |
|
0xC0130012 STATUS_CLUSTER_NODE_UP |
The cluster node is up. |
|
0xC0130013 STATUS_CLUSTER_NODE_PAUSED |
The cluster node is paused. |
|
0xC0130014 STATUS_CLUSTER_NODE_NOT_PAUSED |
The cluster node is not paused. |
|
0xC0130015 STATUS_CLUSTER_NO_SECURITY_CONTEXT |
No cluster security context is available. |
|
0xC0130016 STATUS_CLUSTER_NETWORK_NOT_INTERNAL |
The cluster network is not configured for internal cluster communication. |
|
0xC0130017 STATUS_CLUSTER_POISONED |
The cluster node has been poisoned. |
|
0xC0140001 STATUS_ACPI_INVALID_OPCODE |
An attempt was made to run an invalid AML opcode. |
|
0xC0140002 STATUS_ACPI_STACK_OVERFLOW |
The AML interpreter stack has overflowed. |
|
0xC0140003 STATUS_ACPI_ASSERT_FAILED |
An inconsistent state has occurred. |
|
0xC0140004 STATUS_ACPI_INVALID_INDEX |
An attempt was made to access an array outside its bounds. |
|
0xC0140005 STATUS_ACPI_INVALID_ARGUMENT |
A required argument was not specified. |
|
0xC0140006 STATUS_ACPI_FATAL |
A fatal error has occurred. |
|
0xC0140007 STATUS_ACPI_INVALID_SUPERNAME |
An invalid SuperName was specified. |
|
0xC0140008 STATUS_ACPI_INVALID_ARGTYPE |
An argument with an incorrect type was specified. |
|
0xC0140009 STATUS_ACPI_INVALID_OBJTYPE |
An object with an incorrect type was specified. |
|
0xC014000A STATUS_ACPI_INVALID_TARGETTYPE |
A target with an incorrect type was specified. |
|
0xC014000B STATUS_ACPI_INCORRECT_ARGUMENT_COUNT |
An incorrect number of arguments was specified. |
|
0xC014000C STATUS_ACPI_ADDRESS_NOT_MAPPED |
An address failed to translate. |
|
0xC014000D STATUS_ACPI_INVALID_EVENTTYPE |
An incorrect event type was specified. |
|
0xC014000E STATUS_ACPI_HANDLER_COLLISION |
A handler for the target already exists. |
|
0xC014000F STATUS_ACPI_INVALID_DATA |
Invalid data for the target was specified. |
|
0xC0140010 STATUS_ACPI_INVALID_REGION |
An invalid region for the target was specified. |
|
0xC0140011 STATUS_ACPI_INVALID_ACCESS_SIZE |
An attempt was made to access a field outside the defined range. |
|
0xC0140012 STATUS_ACPI_ACQUIRE_GLOBAL_LOCK |
The global system lock could not be acquired. |
|
0xC0140013 STATUS_ACPI_ALREADY_INITIALIZED |
An attempt was made to reinitialize the ACPI subsystem. |
|
0xC0140014 STATUS_ACPI_NOT_INITIALIZED |
The ACPI subsystem has not been initialized. |
|
0xC0140015 STATUS_ACPI_INVALID_MUTEX_LEVEL |
An incorrect mutex was specified. |
|
0xC0140016 STATUS_ACPI_MUTEX_NOT_OWNED |
The mutex is not currently owned. |
|
0xC0140017 STATUS_ACPI_MUTEX_NOT_OWNER |
An attempt was made to access the mutex by a process that was not the owner. |
|
0xC0140018 STATUS_ACPI_RS_ACCESS |
An error occurred during an access to region space. |
|
0xC0140019 STATUS_ACPI_INVALID_TABLE |
An attempt was made to use an incorrect table. |
|
0xC0140020 STATUS_ACPI_REG_HANDLER_FAILED |
The registration of an ACPI event failed. |
|
0xC0140021 STATUS_ACPI_POWER_REQUEST_FAILED |
An ACPI power object failed to transition state. |
|
0xC0150001 STATUS_SXS_SECTION_NOT_FOUND |
The requested section is not present in the activation context. |
|
0xC0150002 STATUS_SXS_CANT_GEN_ACTCTX |
Windows was unble to process the application binding information. Refer to the system event log for further information. |
|
0xC0150003 STATUS_SXS_INVALID_ACTCTXDATA_FORMAT |
The application binding data format is invalid. |
|
0xC0150004 STATUS_SXS_ASSEMBLY_NOT_FOUND |
The referenced assembly is not installed on the system. |
|
0xC0150005 STATUS_SXS_MANIFEST_FORMAT_ERROR |
The manifest file does not begin with the required tag and format information. |
|
0xC0150006 STATUS_SXS_MANIFEST_PARSE_ERROR |
The manifest file contains one or more syntax errors. |
|
0xC0150007 STATUS_SXS_ACTIVATION_CONTEXT_DISABLED |
The application attempted to activate a disabled activation context. |
|
0xC0150008 STATUS_SXS_KEY_NOT_FOUND |
The requested lookup key was not found in any active activation context. |
|
0xC0150009 STATUS_SXS_VERSION_CONFLICT |
A component version required by the application conflicts with another component version that is already active. |
|
0xC015000A STATUS_SXS_WRONG_SECTION_TYPE |
The type requested activation context section does not match the query API used. |
|
0xC015000B STATUS_SXS_THREAD_QUERIES_DISABLED |
Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
|
0xC015000C STATUS_SXS_ASSEMBLY_MISSING |
The referenced assembly could not be found. |
|
0xC015000E STATUS_SXS_PROCESS_DEFAULT_ALREADY_SET |
An attempt to set the process default activation context failed because the process default activation context was already set. |
|
0xC015000F STATUS_SXS_EARLY_DEACTIVATION |
The activation context being deactivated is not the most recently activated one. |
|
0xC0150010 STATUS_SXS_INVALID_DEACTIVATION |
The activation context being deactivated is not active for the current thread of execution. |
|
0xC0150011 STATUS_SXS_MULTIPLE_DEACTIVATION |
The activation context being deactivated has already been deactivated. |
|
0xC0150012 STATUS_SXS_SYSTEM_DEFAULT_ACTIVATION_CONTEXT_EMPTY |
The activation context of the system default assembly could not be generated. |
|
0xC0150013 STATUS_SXS_PROCESS_TERMINATION_REQUESTED |
A component used by the isolation facility has requested that the process be terminated. |
|
0xC0150014 STATUS_SXS_CORRUPT_ACTIVATION_STACK |
The activation context activation stack for the running thread of execution is corrupt. |
|
0xC0150015 STATUS_SXS_CORRUPTION |
The application isolation metadata for this process or thread has become corrupt. |
|
0xC0150016 STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE |
The value of an attribute in an identity is not within the legal range. |
|
0xC0150017 STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME |
The name of an attribute in an identity is not within the legal range. |
|
0xC0150018 STATUS_SXS_IDENTITY_DUPLICATE_ATTRIBUTE |
An identity contains two definitions for the same attribute. |
|
0xC0150019 STATUS_SXS_IDENTITY_PARSE_ERROR |
The identity string is malformed. This might be due to a trailing comma, more than two unnamed attributes, a missing attribute name, or a missing attribute value. |
|
0xC015001A STATUS_SXS_COMPONENT_STORE_CORRUPT |
The component store has become corrupted. |
|
0xC015001B STATUS_SXS_FILE_HASH_MISMATCH |
A component's file does not match the verification information present in the component manifest. |
|
0xC015001C STATUS_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT |
The identities of the manifests are identical, but their contents are different. |
|
0xC015001D STATUS_SXS_IDENTITIES_DIFFERENT |
The component identities are different. |
|
0xC015001E STATUS_SXS_ASSEMBLY_IS_NOT_A_DEPLOYMENT |
The assembly is not a deployment. |
|
0xC015001F STATUS_SXS_FILE_NOT_PART_OF_ASSEMBLY |
The file is not a part of the assembly. |
|
0xC0150020 STATUS_ADVANCED_INSTALLER_FAILED |
An advanced installer failed during setup or servicing. |
|
0xC0150021 STATUS_XML_ENCODING_MISMATCH |
The character encoding in the XML declaration did not match the encoding used in the document. |
|
0xC0150022 STATUS_SXS_MANIFEST_TOO_BIG |
The size of the manifest exceeds the maximum allowed. |
|
0xC0150023 STATUS_SXS_SETTING_NOT_REGISTERED |
The setting is not registered. |
|
0xC0150024 STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE |
One or more required transaction members are not present. |
|
0xC0150025 STATUS_SMI_PRIMITIVE_INSTALLER_FAILED |
The SMI primitive installer failed during setup or servicing. |
|
0xC0150026 STATUS_GENERIC_COMMAND_FAILED |
A generic command executable returned a result that indicates failure. |
|
0xC0150027 STATUS_SXS_FILE_HASH_MISSING |
A component is missing file verification information in its manifest. |
|
0xC0190001 STATUS_TRANSACTIONAL_CONFLICT |
The function attempted to use a name that is reserved for use by another transaction. |
|
0xC0190002 STATUS_INVALID_TRANSACTION |
The transaction handle associated with this operation is invalid. |
|
0xC0190003 STATUS_TRANSACTION_NOT_ACTIVE |
The requested operation was made in the context of a transaction that is no longer active. |
|
0xC0190004 STATUS_TM_INITIALIZATION_FAILED |
The transaction manager was unable to be successfully initialized. Transacted operations are not supported. |
|
0xC0190005 STATUS_RM_NOT_ACTIVE |
Transaction support within the specified file system resource manager was not started or was shut down due to an error. |
|
0xC0190006 STATUS_RM_METADATA_CORRUPT |
The metadata of the resource manager has been corrupted. The resource manager will not function. |
|
0xC0190007 STATUS_TRANSACTION_NOT_JOINED |
The resource manager attempted to prepare a transaction that it has not successfully joined. |
|
0xC0190008 STATUS_DIRECTORY_NOT_RM |
The specified directory does not contain a file system resource manager. |
|
0xC019000A STATUS_TRANSACTIONS_UNSUPPORTED_REMOTE |
The remote server or share does not support transacted file operations. |
|
0xC019000B STATUS_LOG_RESIZE_INVALID_SIZE |
The requested log size for the file system resource manager is invalid. |
|
0xC019000C STATUS_REMOTE_FILE_VERSION_MISMATCH |
The remote server sent mismatching version number or Fid for a file opened with transactions. |
|
0xC019000F STATUS_CRM_PROTOCOL_ALREADY_EXISTS |
The resource manager tried to register a protocol that already exists. |
|
0xC0190010 STATUS_TRANSACTION_PROPAGATION_FAILED |
The attempt to propagate the transaction failed. |
|
0xC0190011 STATUS_CRM_PROTOCOL_NOT_FOUND |
The requested propagation protocol was not registered as a CRM. |
|
0xC0190012 STATUS_TRANSACTION_SUPERIOR_EXISTS |
The transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allowed. |
|
0xC0190013 STATUS_TRANSACTION_REQUEST_NOT_VALID |
The requested operation is not valid on the transaction object in its current state. |
|
0xC0190014 STATUS_TRANSACTION_NOT_REQUESTED |
The caller has called a response API, but the response is not expected because the transaction manager did not issue the corresponding request to the caller. |
|
0xC0190015 STATUS_TRANSACTION_ALREADY_ABORTED |
It is too late to perform the requested operation, because the transaction has already been aborted. |
|
0xC0190016 STATUS_TRANSACTION_ALREADY_COMMITTED |
It is too late to perform the requested operation, because the transaction has already been committed. |
|
0xC0190017 STATUS_TRANSACTION_INVALID_MARSHALL_BUFFER |
The buffer passed in to NtPushTransaction or NtPullTransaction is not in a valid format. |
|
0xC0190018 STATUS_CURRENT_TRANSACTION_NOT_VALID |
The current transaction context associated with the thread is not a valid handle to a transaction object. |
|
0xC0190019 STATUS_LOG_GROWTH_FAILED |
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
|
0xC0190021 STATUS_OBJECT_NO_LONGER_EXISTS |
The object (file, stream, or link) that corresponds to the handle has been deleted by a transaction savepoint rollback. |
|
0xC0190022 STATUS_STREAM_MINIVERSION_NOT_FOUND |
The specified file miniversion was not found for this transacted file open. |
|
0xC0190023 STATUS_STREAM_MINIVERSION_NOT_VALID |
The specified file miniversion was found but has been invalidated. The most likely cause is a transaction savepoint rollback. |
|
0xC0190024 STATUS_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION |
A miniversion can be opened only in the context of the transaction that created it. |
|
0xC0190025 STATUS_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT |
It is not possible to open a miniversion with modify access. |
|
0xC0190026 STATUS_CANT_CREATE_MORE_STREAM_MINIVERSIONS |
It is not possible to create any more miniversions for this stream. |
|
0xC0190028 STATUS_HANDLE_NO_LONGER_VALID |
The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint. |
|
0xC0190030 STATUS_LOG_CORRUPTION_DETECTED |
The log data is corrupt. |
|
0xC0190032 STATUS_RM_DISCONNECTED |
The transaction outcome is unavailable because the resource manager responsible for it is disconnected. |
|
0xC0190033 STATUS_ENLISTMENT_NOT_SUPERIOR |
The request was rejected because the enlistment in question is not a superior enlistment. |
|
0xC0190036 STATUS_FILE_IDENTITY_NOT_PERSISTENT |
The file cannot be opened in a transaction because its identity depends on the outcome of an unresolved transaction. |
|
0xC0190037 STATUS_CANT_BREAK_TRANSACTIONAL_DEPENDENCY |
The operation cannot be performed because another transaction is depending on this property not changing. |
|
0xC0190038 STATUS_CANT_CROSS_RM_BOUNDARY |
The operation would involve a single file with two transactional resource managers and is, therefore, not allowed. |
|
0xC0190039 STATUS_TXF_DIR_NOT_EMPTY |
The $Txf directory must be empty for this operation to succeed. |
|
0xC019003A STATUS_INDOUBT_TRANSACTIONS_EXIST |
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
|
0xC019003B STATUS_TM_VOLATILE |
The operation could not be completed because the transaction manager does not have a log. |
|
0xC019003C STATUS_ROLLBACK_TIMER_EXPIRED |
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
|
0xC019003D STATUS_TXF_ATTRIBUTE_CORRUPT |
The transactional metadata attribute on the file or directory %hs is corrupt and unreadable. |
|
0xC019003E STATUS_EFS_NOT_ALLOWED_IN_TRANSACTION |
The encryption operation could not be completed because a transaction is active. |
|
0xC019003F STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED |
This object is not allowed to be opened in a transaction. |
|
0xC0190040 STATUS_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE |
Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
|
0xC0190043 STATUS_TRANSACTION_REQUIRED_PROMOTION |
Promotion was required to allow the resource manager to enlist, but the transaction was set to disallow it. |
|
0xC0190044 STATUS_CANNOT_EXECUTE_FILE_IN_TRANSACTION |
This file is open for modification in an unresolved transaction and can be opened for execute only by a transacted reader. |
|
0xC0190045 STATUS_TRANSACTIONS_NOT_FROZEN |
The request to thaw frozen transactions was ignored because transactions were not previously frozen. |
|
0xC0190046 STATUS_TRANSACTION_FREEZE_IN_PROGRESS |
Transactions cannot be frozen because a freeze is already in progress. |
|
0xC0190047 STATUS_NOT_SNAPSHOT_VOLUME |
The target volume is not a snapshot volume. This operation is valid only on a volume mounted as a snapshot. |
|
0xC0190048 STATUS_NO_SAVEPOINT_WITH_OPEN_FILES |
The savepoint operation failed because files are open on the transaction, which is not permitted. |
|
0xC0190049 STATUS_SPARSE_NOT_ALLOWED_IN_TRANSACTION |
The sparse operation could not be completed because a transaction is active on the file. |
|
0xC019004A STATUS_TM_IDENTITY_MISMATCH |
The call to create a transaction manager object failed because the Tm Identity that is stored in the log file does not match the Tm Identity that was passed in as an argument. |
|
0xC019004B STATUS_FLOATED_SECTION |
I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. |
|
0xC019004C STATUS_CANNOT_ACCEPT_TRANSACTED_WORK |
The transactional resource manager cannot currently accept transacted work due to a transient condition, such as low resources. |
|
0xC019004D STATUS_CANNOT_ABORT_TRANSACTIONS |
The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manager has been shut down. |
|
0xC019004E STATUS_TRANSACTION_NOT_FOUND |
The specified transaction was unable to be opened because it was not found. |
|
0xC019004F STATUS_RESOURCEMANAGER_NOT_FOUND |
The specified resource manager was unable to be opened because it was not found. |
|
0xC0190050 STATUS_ENLISTMENT_NOT_FOUND |
The specified enlistment was unable to be opened because it was not found. |
|
0xC0190051 STATUS_TRANSACTIONMANAGER_NOT_FOUND |
The specified transaction manager was unable to be opened because it was not found. |
|
0xC0190052 STATUS_TRANSACTIONMANAGER_NOT_ONLINE |
The specified resource manager was unable to create an enlistment because its associated transaction manager is not online. |
|
0xC0190053 STATUS_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION |
The specified transaction manager was unable to create the objects contained in its log file in the Ob namespace. Therefore, the transaction manager was unable to recover. |
|
0xC0190054 STATUS_TRANSACTION_NOT_ROOT |
The call to create a superior enlistment on this transaction object could not be completed because the transaction object specified for the enlistment is a subordinate branch of the transaction. Only the root of the transaction can be enlisted as a superior. |
|
0xC0190055 STATUS_TRANSACTION_OBJECT_EXPIRED |
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
|
0xC0190056 STATUS_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION |
The compression operation could not be completed because a transaction is active on the file. |
|
0xC0190057 STATUS_TRANSACTION_RESPONSE_NOT_ENLISTED |
The specified operation could not be performed on this superior enlistment because the enlistment was not created with the corresponding completion response in the NotificationMask. |
|
0xC0190058 STATUS_TRANSACTION_RECORD_TOO_LONG |
The specified operation could not be performed because the record to be logged was too long. This can occur because either there are too many enlistments on this transaction or the combined RecoveryInformation being logged on behalf of those enlistments is too long. |
|
0xC0190059 STATUS_NO_LINK_TRACKING_IN_TRANSACTION |
The link-tracking operation could not be completed because a transaction is active. |
|
0xC019005A STATUS_OPERATION_NOT_SUPPORTED_IN_TRANSACTION |
This operation cannot be performed in a transaction. |
|
0xC019005B STATUS_TRANSACTION_INTEGRITY_VIOLATED |
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
|
0xC0190060 STATUS_EXPIRED_HANDLE |
The handle is no longer properly associated with its transaction. It might have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one. |
|
0xC0190061 STATUS_TRANSACTION_NOT_ENLISTED |
The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
|
0xC01A0001 STATUS_LOG_SECTOR_INVALID |
The log service found an invalid log sector. |
|
0xC01A0002 STATUS_LOG_SECTOR_PARITY_INVALID |
The log service encountered a log sector with invalid block parity. |
|
0xC01A0003 STATUS_LOG_SECTOR_REMAPPED |
The log service encountered a remapped log sector. |
|
0xC01A0004 STATUS_LOG_BLOCK_INCOMPLETE |
The log service encountered a partial or incomplete log block. |
|
0xC01A0005 STATUS_LOG_INVALID_RANGE |
The log service encountered an attempt to access data outside the active log range. |
|
0xC01A0006 STATUS_LOG_BLOCKS_EXHAUSTED |
The log service user-log marshaling buffers are exhausted. |
|
0xC01A0007 STATUS_LOG_READ_CONTEXT_INVALID |
The log service encountered an attempt to read from a marshaling area with an invalid read context. |
|
0xC01A0008 STATUS_LOG_RESTART_INVALID |
The log service encountered an invalid log restart area. |
|
0xC01A0009 STATUS_LOG_BLOCK_VERSION |
The log service encountered an invalid log block version. |
|
0xC01A000A STATUS_LOG_BLOCK_INVALID |
The log service encountered an invalid log block. |
|
0xC01A000B STATUS_LOG_READ_MODE_INVALID |
The log service encountered an attempt to read the log with an invalid read mode. |
|
0xC01A000D STATUS_LOG_METADATA_CORRUPT |
The log service encountered a corrupted metadata file. |
|
0xC01A000E STATUS_LOG_METADATA_INVALID |
The log service encountered a metadata file that could not be created by the log file system. |
|
0xC01A000F STATUS_LOG_METADATA_INCONSISTENT |
The log service encountered a metadata file with inconsistent data. |
|
0xC01A0010 STATUS_LOG_RESERVATION_INVALID |
The log service encountered an attempt to erroneously allocate or dispose reservation space. |
|
0xC01A0011 STATUS_LOG_CANT_DELETE |
The log service cannot delete the log file or the file system container. |
|
0xC01A0012 STATUS_LOG_CONTAINER_LIMIT_EXCEEDED |
The log service has reached the maximum allowable containers allocated to a log file. |
|
0xC01A0013 STATUS_LOG_START_OF_LOG |
The log service has attempted to read or write backward past the start of the log. |
|
0xC01A0014 STATUS_LOG_POLICY_ALREADY_INSTALLED |
The log policy could not be installed because a policy of the same type is already present. |
|
0xC01A0015 STATUS_LOG_POLICY_NOT_INSTALLED |
The log policy in question was not installed at the time of the request. |
|
0xC01A0016 STATUS_LOG_POLICY_INVALID |
The installed set of policies on the log is invalid. |
|
0xC01A0017 STATUS_LOG_POLICY_CONFLICT |
A policy on the log in question prevented the operation from completing. |
|
0xC01A0018 STATUS_LOG_PINNED_ARCHIVE_TAIL |
The log space cannot be reclaimed because the log is pinned by the archive tail. |
|
0xC01A0019 STATUS_LOG_RECORD_NONEXISTENT |
The log record is not a record in the log file. |
|
0xC01A001A STATUS_LOG_RECORDS_RESERVED_INVALID |
The number of reserved log records or the adjustment of the number of reserved log records is invalid. |
|
0xC01A001B STATUS_LOG_SPACE_RESERVED_INVALID |
The reserved log space or the adjustment of the log space is invalid. |
|
0xC01A001C STATUS_LOG_TAIL_INVALID |
A new or existing archive tail or the base of the active log is invalid. |
|
0xC01A001D STATUS_LOG_FULL |
The log space is exhausted. |
|
0xC01A001E STATUS_LOG_MULTIPLEXED |
The log is multiplexed; no direct writes to the physical log are allowed. |
|
0xC01A001F STATUS_LOG_DEDICATED |
The operation failed because the log is dedicated. |
|
0xC01A0020 STATUS_LOG_ARCHIVE_NOT_IN_PROGRESS |
The operation requires an archive context. |
|
0xC01A0021 STATUS_LOG_ARCHIVE_IN_PROGRESS |
Log archival is in progress. |
|
0xC01A0022 STATUS_LOG_EPHEMERAL |
The operation requires a nonephemeral log, but the log is ephemeral. |
|
0xC01A0023 STATUS_LOG_NOT_ENOUGH_CONTAINERS |
The log must have at least two containers before it can be read from or written to. |
|
0xC01A0024 STATUS_LOG_CLIENT_ALREADY_REGISTERED |
A log client has already registered on the stream. |
|
0xC01A0025 STATUS_LOG_CLIENT_NOT_REGISTERED |
A log client has not been registered on the stream. |
|
0xC01A0026 STATUS_LOG_FULL_HANDLER_IN_PROGRESS |
A request has already been made to handle the log full condition. |
|
0xC01A0027 STATUS_LOG_CONTAINER_READ_FAILED |
The log service encountered an error when attempting to read from a log container. |
|
0xC01A0028 STATUS_LOG_CONTAINER_WRITE_FAILED |
The log service encountered an error when attempting to write to a log container. |
|
0xC01A0029 STATUS_LOG_CONTAINER_OPEN_FAILED |
The log service encountered an error when attempting to open a log container. |
|
0xC01A002A STATUS_LOG_CONTAINER_STATE_INVALID |
The log service encountered an invalid container state when attempting a requested action. |
|
0xC01A002B STATUS_LOG_STATE_INVALID |
The log service is not in the correct state to perform a requested action. |
|
0xC01A002C STATUS_LOG_PINNED |
The log space cannot be reclaimed because the log is pinned. |
|
0xC01A002D STATUS_LOG_METADATA_FLUSH_FAILED |
The log metadata flush failed. |
|
0xC01A002E STATUS_LOG_INCONSISTENT_SECURITY |
Security on the log and its containers is inconsistent. |
|
0xC01A002F STATUS_LOG_APPENDED_FLUSH_FAILED |
Records were appended to the log or reservation changes were made, but the log could not be flushed. |
|
0xC01A0030 STATUS_LOG_PINNED_RESERVATION |
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
|
0xC01B00EA STATUS_VIDEO_HUNG_DISPLAY_DRIVER_THREAD |
{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 computer, a dialog box will allow you to upload data about this failure to Microsoft. |
|
0xC01C0001 STATUS_FLT_NO_HANDLER_DEFINED |
A handler was not defined by the filter for this operation. |
|
0xC01C0002 STATUS_FLT_CONTEXT_ALREADY_DEFINED |
A context is already defined for this object. |
|
0xC01C0003 STATUS_FLT_INVALID_ASYNCHRONOUS_REQUEST |
Asynchronous requests are not valid for this operation. |
|
0xC01C0004 STATUS_FLT_DISALLOW_FAST_IO |
This is an internal error code used by the filter manager to determine if a fast I/O operation should be forced down the input/output request packet (IRP) path. Minifilters should never return this value. |
|
0xC01C0005 STATUS_FLT_INVALID_NAME_REQUEST |
An invalid name request was made. The name requested cannot be retrieved at this time. |
|
0xC01C0006 STATUS_FLT_NOT_SAFE_TO_POST_OPERATION |
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
|
0xC01C0007 STATUS_FLT_NOT_INITIALIZED |
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is loaded as a driver. |
|
0xC01C0008 STATUS_FLT_FILTER_NOT_READY |
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
|
0xC01C0009 STATUS_FLT_POST_OPERATION_CLEANUP |
The filter must clean up any operation-specific context at this time because it is being removed from the system before the operation is completed by the lower drivers. |
|
0xC01C000A STATUS_FLT_INTERNAL_ERROR |
The Filter Manager had an internal error from which it cannot recover; therefore, the operation has failed. This is usually the result of a filter returning an invalid value from a pre-operation callback. |
|
0xC01C000B STATUS_FLT_DELETING_OBJECT |
The object specified for this action is in the process of being deleted; therefore, the action requested cannot be completed at this time. |
|
0xC01C000C STATUS_FLT_MUST_BE_NONPAGED_POOL |
A nonpaged pool must be used for this type of context. |
|
0xC01C000D STATUS_FLT_DUPLICATE_ENTRY |
A duplicate handler definition has been provided for an operation. |
|
0xC01C000E STATUS_FLT_CBDQ_DISABLED |
The callback data queue has been disabled. |
|
0xC01C000F STATUS_FLT_DO_NOT_ATTACH |
Do not attach the filter to the volume at this time. |
|
0xC01C0010 STATUS_FLT_DO_NOT_DETACH |
Do not detach the filter from the volume at this time. |
|
0xC01C0011 STATUS_FLT_INSTANCE_ALTITUDE_COLLISION |
An instance already exists at this altitude on the volume specified. |
|
0xC01C0012 STATUS_FLT_INSTANCE_NAME_COLLISION |
An instance already exists with this name on the volume specified. |
|
0xC01C0013 STATUS_FLT_FILTER_NOT_FOUND |
The system could not find the filter specified. |
|
0xC01C0014 STATUS_FLT_VOLUME_NOT_FOUND |
The system could not find the volume specified. |
|
0xC01C0015 STATUS_FLT_INSTANCE_NOT_FOUND |
The system could not find the instance specified. |
|
0xC01C0016 STATUS_FLT_CONTEXT_ALLOCATION_NOT_FOUND |
No registered context allocation definition was found for the given request. |
|
0xC01C0017 STATUS_FLT_INVALID_CONTEXT_REGISTRATION |
An invalid parameter was specified during context registration. |
|
0xC01C0018 STATUS_FLT_NAME_CACHE_MISS |
The name requested was not found in the Filter Manager name cache and could not be retrieved from the file system. |
|
0xC01C0019 STATUS_FLT_NO_DEVICE_OBJECT |
The requested device object does not exist for the given volume. |
|
0xC01C001A STATUS_FLT_VOLUME_ALREADY_MOUNTED |
The specified volume is already mounted. |
|
0xC01C001B STATUS_FLT_ALREADY_ENLISTED |
The specified transaction context is already enlisted in a transaction. |
|
0xC01C001C STATUS_FLT_CONTEXT_ALREADY_LINKED |
The specified context is already attached to another object. |
|
0xC01C0020 STATUS_FLT_NO_WAITER_FOR_REPLY |
No waiter is present for the filter's reply to this message. |
|
0xC01D0001 STATUS_MONITOR_NO_DESCRIPTOR |
A monitor descriptor could not be obtained. |
|
0xC01D0002 STATUS_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT |
This release does not support the format of the obtained monitor descriptor. |
|
0xC01D0003 STATUS_MONITOR_INVALID_DESCRIPTOR_CHECKSUM |
The checksum of the obtained monitor descriptor is invalid. |
|
0xC01D0004 STATUS_MONITOR_INVALID_STANDARD_TIMING_BLOCK |
The monitor descriptor contains an invalid standard timing block. |
|
0xC01D0005 STATUS_MONITOR_WMI_DATABLOCK_REGISTRATION_FAILED |
WMI data-block registration failed for one of the MSMonitorClass WMI subclasses. |
|
0xC01D0006 STATUS_MONITOR_INVALID_SERIAL_NUMBER_MONDSC_BLOCK |
The provided monitor descriptor block is either corrupted or does not contain the monitor's detailed serial number. |
|
0xC01D0007 STATUS_MONITOR_INVALID_USER_FRIENDLY_MONDSC_BLOCK |
The provided monitor descriptor block is either corrupted or does not contain the monitor's user-friendly name. |
|
0xC01D0008 STATUS_MONITOR_NO_MORE_DESCRIPTOR_DATA |
There is no monitor descriptor data at the specified (offset or size) region. |
|
0xC01D0009 STATUS_MONITOR_INVALID_DETAILED_TIMING_BLOCK |
The monitor descriptor contains an invalid detailed timing block. |
|
0xC01D000A STATUS_MONITOR_INVALID_MANUFACTURE_DATE |
Monitor descriptor contains invalid manufacture date. |
|
0xC01E0000 STATUS_GRAPHICS_NOT_EXCLUSIVE_MODE_OWNER |
Exclusive mode ownership is needed to create an unmanaged primary allocation. |
|
0xC01E0001 STATUS_GRAPHICS_INSUFFICIENT_DMA_BUFFER |
The driver needs more DMA buffer space to complete the requested operation. |
|
0xC01E0002 STATUS_GRAPHICS_INVALID_DISPLAY_ADAPTER |
The specified display adapter handle is invalid. |
|
0xC01E0003 STATUS_GRAPHICS_ADAPTER_WAS_RESET |
The specified display adapter and all of its state have been reset. |
|
0xC01E0004 STATUS_GRAPHICS_INVALID_DRIVER_MODEL |
The driver stack does not match the expected driver model. |
|
0xC01E0005 STATUS_GRAPHICS_PRESENT_MODE_CHANGED |
Present happened but ended up into the changed desktop mode. |
|
0xC01E0006 STATUS_GRAPHICS_PRESENT_OCCLUDED |
Nothing to present due to desktop occlusion. |
|
0xC01E0007 STATUS_GRAPHICS_PRESENT_DENIED |
Not able to present due to denial of desktop access. |
|
0xC01E0008 STATUS_GRAPHICS_CANNOTCOLORCONVERT |
Not able to present with color conversion. |
|
0xC01E000B STATUS_GRAPHICS_PRESENT_REDIRECTION_DISABLED |
Present redirection is disabled (desktop windowing management subsystem is off). |
|
0xC01E000C STATUS_GRAPHICS_PRESENT_UNOCCLUDED |
Previous exclusive VidPn source owner has released its ownership |
|
0xC01E0100 STATUS_GRAPHICS_NO_VIDEO_MEMORY |
Not enough video memory is available to complete the operation. |
|
0xC01E0101 STATUS_GRAPHICS_CANT_LOCK_MEMORY |
Could not probe and lock the underlying memory of an allocation. |
|
0xC01E0102 STATUS_GRAPHICS_ALLOCATION_BUSY |
The allocation is currently busy. |
|
0xC01E0103 STATUS_GRAPHICS_TOO_MANY_REFERENCES |
An object being referenced has already reached the maximum reference count and cannot be referenced further. |
|
0xC01E0104 STATUS_GRAPHICS_TRY_AGAIN_LATER |
A problem could not be solved due to an existing condition. Try again later. |
|
0xC01E0105 STATUS_GRAPHICS_TRY_AGAIN_NOW |
A problem could not be solved due to an existing condition. Try again now. |
|
0xC01E0106 STATUS_GRAPHICS_ALLOCATION_INVALID |
The allocation is invalid. |
|
0xC01E0107 STATUS_GRAPHICS_UNSWIZZLING_APERTURE_UNAVAILABLE |
No more unswizzling apertures are currently available. |
|
0xC01E0108 STATUS_GRAPHICS_UNSWIZZLING_APERTURE_UNSUPPORTED |
The current allocation cannot be unswizzled by an aperture. |
|
0xC01E0109 STATUS_GRAPHICS_CANT_EVICT_PINNED_ALLOCATION |
The request failed because a pinned allocation cannot be evicted. |
|
0xC01E0110 STATUS_GRAPHICS_INVALID_ALLOCATION_USAGE |
The allocation cannot be used from its current segment location for the specified operation. |
|
0xC01E0111 STATUS_GRAPHICS_CANT_RENDER_LOCKED_ALLOCATION |
A locked allocation cannot be used in the current command buffer. |
|
0xC01E0112 STATUS_GRAPHICS_ALLOCATION_CLOSED |
The allocation being referenced has been closed permanently. |
|
0xC01E0113 STATUS_GRAPHICS_INVALID_ALLOCATION_INSTANCE |
An invalid allocation instance is being referenced. |
|
0xC01E0114 STATUS_GRAPHICS_INVALID_ALLOCATION_HANDLE |
An invalid allocation handle is being referenced. |
|
0xC01E0115 STATUS_GRAPHICS_WRONG_ALLOCATION_DEVICE |
The allocation being referenced does not belong to the current device. |
|
0xC01E0116 STATUS_GRAPHICS_ALLOCATION_CONTENT_LOST |
The specified allocation lost its content. |
|
0xC01E0200 STATUS_GRAPHICS_GPU_EXCEPTION_ON_DEVICE |
A GPU exception was detected on the given device. The device cannot be scheduled. |
|
0xC01E0300 STATUS_GRAPHICS_INVALID_VIDPN_TOPOLOGY |
The specified VidPN topology is invalid. |
|
0xC01E0301 STATUS_GRAPHICS_VIDPN_TOPOLOGY_NOT_SUPPORTED |
The specified VidPN topology is valid but is not supported by this model of the display adapter. |
|
0xC01E0302 STATUS_GRAPHICS_VIDPN_TOPOLOGY_CURRENTLY_NOT_SUPPORTED |
The specified VidPN topology is valid but is not currently supported by the display adapter due to allocation of its resources. |
|
0xC01E0303 STATUS_GRAPHICS_INVALID_VIDPN |
The specified VidPN handle is invalid. |
|
0xC01E0304 STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE |
The specified video present source is invalid. |
|
0xC01E0305 STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET |
The specified video present target is invalid. |
|
0xC01E0306 STATUS_GRAPHICS_VIDPN_MODALITY_NOT_SUPPORTED |
The specified VidPN modality is not supported (for example, at least two of the pinned modes are not co-functional). |
|
0xC01E0308 STATUS_GRAPHICS_INVALID_VIDPN_SOURCEMODESET |
The specified VidPN source mode set is invalid. |
|
0xC01E0309 STATUS_GRAPHICS_INVALID_VIDPN_TARGETMODESET |
The specified VidPN target mode set is invalid. |
|
0xC01E030A STATUS_GRAPHICS_INVALID_FREQUENCY |
The specified video signal frequency is invalid. |
|
0xC01E030B STATUS_GRAPHICS_INVALID_ACTIVE_REGION |
The specified video signal active region is invalid. |
|
0xC01E030C STATUS_GRAPHICS_INVALID_TOTAL_REGION |
The specified video signal total region is invalid. |
|
0xC01E0310 STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE_MODE |
The specified video present source mode is invalid. |
|
0xC01E0311 STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_TARGET_MODE |
The specified video present target mode is invalid. |
|
0xC01E0312 STATUS_GRAPHICS_PINNED_MODE_MUST_REMAIN_IN_SET |
The pinned mode must remain in the set on the VidPN's co-functional modality enumeration. |
|
0xC01E0313 STATUS_GRAPHICS_PATH_ALREADY_IN_TOPOLOGY |
The specified video present path is already in the VidPN's topology. |
|
0xC01E0314 STATUS_GRAPHICS_MODE_ALREADY_IN_MODESET |
The specified mode is already in the mode set. |
|
0xC01E0315 STATUS_GRAPHICS_INVALID_VIDEOPRESENTSOURCESET |
The specified video present source set is invalid. |
|
0xC01E0316 STATUS_GRAPHICS_INVALID_VIDEOPRESENTTARGETSET |
The specified video present target set is invalid. |
|
0xC01E0317 STATUS_GRAPHICS_SOURCE_ALREADY_IN_SET |
The specified video present source is already in the video present source set. |
|
0xC01E0318 STATUS_GRAPHICS_TARGET_ALREADY_IN_SET |
The specified video present target is already in the video present target set. |
|
0xC01E0319 STATUS_GRAPHICS_INVALID_VIDPN_PRESENT_PATH |
The specified VidPN present path is invalid. |
|
0xC01E031A STATUS_GRAPHICS_NO_RECOMMENDED_VIDPN_TOPOLOGY |
The miniport has no recommendation for augmenting the specified VidPN's topology. |
|
0xC01E031B STATUS_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGESET |
The specified monitor frequency range set is invalid. |
|
0xC01E031C STATUS_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE |
The specified monitor frequency range is invalid. |
|
0xC01E031D STATUS_GRAPHICS_FREQUENCYRANGE_NOT_IN_SET |
The specified frequency range is not in the specified monitor frequency range set. |
|
0xC01E031F STATUS_GRAPHICS_FREQUENCYRANGE_ALREADY_IN_SET |
The specified frequency range is already in the specified monitor frequency range set. |
|
0xC01E0320 STATUS_GRAPHICS_STALE_MODESET |
The specified mode set is stale. Reacquire the new mode set. |
|
0xC01E0321 STATUS_GRAPHICS_INVALID_MONITOR_SOURCEMODESET |
The specified monitor source mode set is invalid. |
|
0xC01E0322 STATUS_GRAPHICS_INVALID_MONITOR_SOURCE_MODE |
The specified monitor source mode is invalid. |
|
0xC01E0323 STATUS_GRAPHICS_NO_RECOMMENDED_FUNCTIONAL_VIDPN |
The miniport does not have a recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
|
0xC01E0324 STATUS_GRAPHICS_MODE_ID_MUST_BE_UNIQUE |
The ID of the specified mode is being used by another mode in the set. |
|
0xC01E0325 STATUS_GRAPHICS_EMPTY_ADAPTER_MONITOR_MODE_SUPPORT_INTERSECTION |
The system failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
|
0xC01E0326 STATUS_GRAPHICS_VIDEO_PRESENT_TARGETS_LESS_THAN_SOURCES |
The number of video present targets must be greater than or equal to the number of video present sources. |
|
0xC01E0327 STATUS_GRAPHICS_PATH_NOT_IN_TOPOLOGY |
The specified present path is not in the VidPN's topology. |
|
0xC01E0328 STATUS_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_SOURCE |
The display adapter must have at least one video present source. |
|
0xC01E0329 STATUS_GRAPHICS_ADAPTER_MUST_HAVE_AT_LEAST_ONE_TARGET |
The display adapter must have at least one video present target. |
|
0xC01E032A STATUS_GRAPHICS_INVALID_MONITORDESCRIPTORSET |
The specified monitor descriptor set is invalid. |
|
0xC01E032B STATUS_GRAPHICS_INVALID_MONITORDESCRIPTOR |
The specified monitor descriptor is invalid. |
|
0xC01E032C STATUS_GRAPHICS_MONITORDESCRIPTOR_NOT_IN_SET |
The specified descriptor is not in the specified monitor descriptor set. |
|
0xC01E032D STATUS_GRAPHICS_MONITORDESCRIPTOR_ALREADY_IN_SET |
The specified descriptor is already in the specified monitor descriptor set. |
|
0xC01E032E STATUS_GRAPHICS_MONITORDESCRIPTOR_ID_MUST_BE_UNIQUE |
The ID of the specified monitor descriptor is being used by another descriptor in the set. |
|
0xC01E032F STATUS_GRAPHICS_INVALID_VIDPN_TARGET_SUBSET_TYPE |
The specified video present target subset type is invalid. |
|
0xC01E0330 STATUS_GRAPHICS_RESOURCES_NOT_RELATED |
Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
|
0xC01E0331 STATUS_GRAPHICS_SOURCE_ID_MUST_BE_UNIQUE |
The ID of the specified video present source is being used by another source in the set. |
|
0xC01E0332 STATUS_GRAPHICS_TARGET_ID_MUST_BE_UNIQUE |
The ID of the specified video present target is being used by another target in the set. |
|
0xC01E0333 STATUS_GRAPHICS_NO_AVAILABLE_VIDPN_TARGET |
The specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
|
0xC01E0334 STATUS_GRAPHICS_MONITOR_COULD_NOT_BE_ASSOCIATED_WITH_ADAPTER |
The newly arrived monitor could not be associated with a display adapter. |
|
0xC01E0335 STATUS_GRAPHICS_NO_VIDPNMGR |
The particular display adapter does not have an associated VidPN manager. |
|
0xC01E0336 STATUS_GRAPHICS_NO_ACTIVE_VIDPN |
The VidPN manager of the particular display adapter does not have an active VidPN. |
|
0xC01E0337 STATUS_GRAPHICS_STALE_VIDPN_TOPOLOGY |
The specified VidPN topology is stale; obtain the new topology. |
|
0xC01E0338 STATUS_GRAPHICS_MONITOR_NOT_CONNECTED |
No monitor is connected on the specified video present target. |
|
0xC01E0339 STATUS_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY |
The specified source is not part of the specified VidPN's topology. |
|
0xC01E033A STATUS_GRAPHICS_INVALID_PRIMARYSURFACE_SIZE |
The specified primary surface size is invalid. |
|
0xC01E033B STATUS_GRAPHICS_INVALID_VISIBLEREGION_SIZE |
The specified visible region size is invalid. |
|
0xC01E033C STATUS_GRAPHICS_INVALID_STRIDE |
The specified stride is invalid. |
|
0xC01E033D STATUS_GRAPHICS_INVALID_PIXELFORMAT |
The specified pixel format is invalid. |
|
0xC01E033E STATUS_GRAPHICS_INVALID_COLORBASIS |
The specified color basis is invalid. |
|
0xC01E033F STATUS_GRAPHICS_INVALID_PIXELVALUEACCESSMODE |
The specified pixel value access mode is invalid. |
|
0xC01E0340 STATUS_GRAPHICS_TARGET_NOT_IN_TOPOLOGY |
The specified target is not part of the specified VidPN's topology. |
|
0xC01E0341 STATUS_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT |
Failed to acquire the display mode management interface. |
|
0xC01E0342 STATUS_GRAPHICS_VIDPN_SOURCE_IN_USE |
The specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
|
0xC01E0343 STATUS_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN |
The specified VidPN is active and cannot be accessed. |
|
0xC01E0344 STATUS_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL |
The specified VidPN's present path importance ordinal is invalid. |
|
0xC01E0345 STATUS_GRAPHICS_INVALID_PATH_CONTENT_GEOMETRY_TRANSFORMATION |
The specified VidPN's present path content geometry transformation is invalid. |
|
0xC01E0346 STATUS_GRAPHICS_PATH_CONTENT_GEOMETRY_TRANSFORMATION_NOT_SUPPORTED |
The specified content geometry transformation is not supported on the respective VidPN present path. |
|
0xC01E0347 STATUS_GRAPHICS_INVALID_GAMMA_RAMP |
The specified gamma ramp is invalid. |
|
0xC01E0348 STATUS_GRAPHICS_GAMMA_RAMP_NOT_SUPPORTED |
The specified gamma ramp is not supported on the respective VidPN present path. |
|
0xC01E0349 STATUS_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED |
Multisampling is not supported on the respective VidPN present path. |
|
0xC01E034A STATUS_GRAPHICS_MODE_NOT_IN_MODESET |
The specified mode is not in the specified mode set. |
|
0xC01E034D STATUS_GRAPHICS_INVALID_VIDPN_TOPOLOGY_RECOMMENDATION_REASON |
The specified VidPN topology recommendation reason is invalid. |
|
0xC01E034E STATUS_GRAPHICS_INVALID_PATH_CONTENT_TYPE |
The specified VidPN present path content type is invalid. |
|
0xC01E034F STATUS_GRAPHICS_INVALID_COPYPROTECTION_TYPE |
The specified VidPN present path copy protection type is invalid. |
|
0xC01E0350 STATUS_GRAPHICS_UNASSIGNED_MODESET_ALREADY_EXISTS |
Only one unassigned mode set can exist at any one time for a particular VidPN source or target. |
|
0xC01E0352 STATUS_GRAPHICS_INVALID_SCANLINE_ORDERING |
The specified scan line ordering type is invalid. |
|
0xC01E0353 STATUS_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED |
The topology changes are not allowed for the specified VidPN. |
|
0xC01E0354 STATUS_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS |
All available importance ordinals are being used in the specified topology. |
|
0xC01E0355 STATUS_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT |
The specified primary surface has a different private-format attribute than the current primary surface. |
|
0xC01E0356 STATUS_GRAPHICS_INVALID_MODE_PRUNING_ALGORITHM |
The specified mode-pruning algorithm is invalid. |
|
0xC01E0357 STATUS_GRAPHICS_INVALID_MONITOR_CAPABILITY_ORIGIN |
The specified monitor-capability origin is invalid. |
|
0xC01E0358 STATUS_GRAPHICS_INVALID_MONITOR_FREQUENCYRANGE_CONSTRAINT |
The specified monitor-frequency range constraint is invalid. |
|
0xC01E0359 STATUS_GRAPHICS_MAX_NUM_PATHS_REACHED |
The maximum supported number of present paths has been reached. |
|
0xC01E035A STATUS_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION |
The miniport requested that augmentation be canceled for the specified source of the specified VidPN's topology. |
|
0xC01E035B STATUS_GRAPHICS_INVALID_CLIENT_TYPE |
The specified client type was not recognized. |
|
0xC01E035C STATUS_GRAPHICS_CLIENTVIDPN_NOT_SET |
The client VidPN is not set on this adapter (for example, no user mode-initiated mode changes have taken place on this adapter). |
|
0xC01E0400 STATUS_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED |
The specified display adapter child device already has an external device connected to it. |
|
0xC01E0401 STATUS_GRAPHICS_CHILD_DESCRIPTOR_NOT_SUPPORTED |
The display adapter child device does not support reporting a descriptor. |
|
0xC01E0430 STATUS_GRAPHICS_NOT_A_LINKED_ADAPTER |
The display adapter is not linked to any other adapters. |
|
0xC01E0431 STATUS_GRAPHICS_LEADLINK_NOT_ENUMERATED |
The lead adapter in a linked configuration was not enumerated yet. |
|
0xC01E0432 STATUS_GRAPHICS_CHAINLINKS_NOT_ENUMERATED |
Some chain adapters in a linked configuration have not yet been enumerated. |
|
0xC01E0433 STATUS_GRAPHICS_ADAPTER_CHAIN_NOT_READY |
The chain of linked adapters is not ready to start because of an unknown failure. |
|
0xC01E0434 STATUS_GRAPHICS_CHAINLINKS_NOT_STARTED |
An attempt was made to start a lead link display adapter when the chain links had not yet started. |
|
0xC01E0435 STATUS_GRAPHICS_CHAINLINKS_NOT_POWERED_ON |
An attempt was made to turn on a lead link display adapter when the chain links were turned off. |
|
0xC01E0436 STATUS_GRAPHICS_INCONSISTENT_DEVICE_LINK_STATE |
The adapter link was found in an inconsistent state. Not all adapters are in an expected PNP/power state. |
|
0xC01E0438 STATUS_GRAPHICS_NOT_POST_DEVICE_DRIVER |
The driver trying to start is not the same as the driver for the posted display adapter. |
|
0xC01E043B STATUS_GRAPHICS_ADAPTER_ACCESS_NOT_EXCLUDED |
An operation is being attempted that requires the display adapter to be in a quiescent state. |
|
0xC01E0500 STATUS_GRAPHICS_OPM_NOT_SUPPORTED |
The driver does not support OPM. |
|
0xC01E0501 STATUS_GRAPHICS_COPP_NOT_SUPPORTED |
The driver does not support COPP. |
|
0xC01E0502 STATUS_GRAPHICS_UAB_NOT_SUPPORTED |
The driver does not support UAB. |
|
0xC01E0503 STATUS_GRAPHICS_OPM_INVALID_ENCRYPTED_PARAMETERS |
The specified encrypted parameters are invalid. |
|
0xC01E0504 STATUS_GRAPHICS_OPM_PARAMETER_ARRAY_TOO_SMALL |
An array passed to a function cannot hold all of the data that the function wants to put in it. |
|
0xC01E0505 STATUS_GRAPHICS_OPM_NO_PROTECTED_OUTPUTS_EXIST |
The GDI display device passed to this function does not have any active protected outputs. |
|
0xC01E0506 STATUS_GRAPHICS_PVP_NO_DISPLAY_DEVICE_CORRESPONDS_TO_NAME |
The PVP cannot find an actual GDI display device that corresponds to the passed-in GDI display device name. |
|
0xC01E0507 STATUS_GRAPHICS_PVP_DISPLAY_DEVICE_NOT_ATTACHED_TO_DESKTOP |
This function failed because the GDI display device passed to it was not attached to the Windows desktop. |
|
0xC01E0508 STATUS_GRAPHICS_PVP_MIRRORING_DEVICES_NOT_SUPPORTED |
The PVP does not support mirroring display devices because they do not have any protected outputs. |
|
0xC01E050A STATUS_GRAPHICS_OPM_INVALID_POINTER |
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is null, is not correctly aligned, or it points to an invalid address or a kernel mode address. |
|
0xC01E050B STATUS_GRAPHICS_OPM_INTERNAL_ERROR |
An internal error caused an operation to fail. |
|
0xC01E050C STATUS_GRAPHICS_OPM_INVALID_HANDLE |
The function failed because the caller passed in an invalid OPM user-mode handle. |
|
0xC01E050D STATUS_GRAPHICS_PVP_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE |
This function failed because the GDI device passed to it did not have any monitors associated with it. |
|
0xC01E050E STATUS_GRAPHICS_PVP_INVALID_CERTIFICATE_LENGTH |
A certificate could not be returned because the certificate buffer passed to the function was too small. |
|
0xC01E050F STATUS_GRAPHICS_OPM_SPANNING_MODE_ENABLED |
DxgkDdiOpmCreateProtectedOutput() could not create a protected output because the video present yarget is in spanning mode. |
|
0xC01E0510 STATUS_GRAPHICS_OPM_THEATER_MODE_ENABLED |
DxgkDdiOpmCreateProtectedOutput() could not create a protected output because the video present target is in theater mode. |
|
0xC01E0511 STATUS_GRAPHICS_PVP_HFS_FAILED |
The function call failed because the display adapter's hardware functionality scan (HFS) failed to validate the graphics hardware. |
|
0xC01E0512 STATUS_GRAPHICS_OPM_INVALID_SRM |
The HDCP SRM passed to this function did not comply with section 5 of the HDCP 1.1 specification. |
|
0xC01E0513 STATUS_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_HDCP |
The protected output cannot enable the HDCP system because it does not support it. |
|
0xC01E0514 STATUS_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_ACP |
The protected output cannot enable analog copy protection because it does not support it. |
|
0xC01E0515 STATUS_GRAPHICS_OPM_OUTPUT_DOES_NOT_SUPPORT_CGMSA |
The protected output cannot enable the CGMS-A protection technology because it does not support it. |
|
0xC01E0516 STATUS_GRAPHICS_OPM_HDCP_SRM_NEVER_SET |
DxgkDdiOPMGetInformation() cannot return the version of the SRM being used because the application never successfully passed an SRM to the protected output. |
|
0xC01E0517 STATUS_GRAPHICS_OPM_RESOLUTION_TOO_HIGH |
DxgkDdiOPMConfigureProtectedOutput() cannot enable the specified output protection technology because the output's screen resolution is too high. |
|
0xC01E0518 STATUS_GRAPHICS_OPM_ALL_HDCP_HARDWARE_ALREADY_IN_USE |
DxgkDdiOPMConfigureProtectedOutput() cannot enable HDCP because other physical outputs are using the display adapter's HDCP hardware. |
|
0xC01E051A STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_NO_LONGER_EXISTS |
The operating system asynchronously destroyed this OPM-protected output because the operating system state changed. This error typically occurs because the monitor PDO associated with this protected output was removed or stopped, the protected output's session became a nonconsole session, or the protected output's desktop became inactive. |
|
0xC01E051B STATUS_GRAPHICS_OPM_SESSION_TYPE_CHANGE_IN_PROGRESS |
OPM functions cannot be called when a session is changing its type. Three types of sessions currently exist: console, disconnected, and remote (RDP or ICA). |
|
0xC01E051C STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS |
The DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned only if a protected output has OPM semantics. DxgkDdiOPMGetCOPPCompatibleInformation always returns this error if a protected output has OPM semantics. DxgkDdiOPMGetInformation returns this error code if the caller requested COPP-specific information. DxgkDdiOPMConfigureProtectedOutput returns this error when the caller tries to use a COPP-specific command. |
|
0xC01E051D STATUS_GRAPHICS_OPM_INVALID_INFORMATION_REQUEST |
The DxgkDdiOPMGetInformation and DxgkDdiOPMGetCOPPCompatibleInformation functions return this error code if the passed-in sequence number is not the expected sequence number or the passed-in OMAC value is invalid. |
|
0xC01E051E STATUS_GRAPHICS_OPM_DRIVER_INTERNAL_ERROR |
The function failed because an unexpected error occurred inside a display driver. |
|
0xC01E051F STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_DOES_NOT_HAVE_OPM_SEMANTICS |
The DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned only if a protected output has COPP semantics. DxgkDdiOPMGetCOPPCompatibleInformation returns this error code if the caller requested OPM-specific information. DxgkDdiOPMGetInformation always returns this error if a protected output has COPP semantics. DxgkDdiOPMConfigureProtectedOutput returns this error when the caller tries to use an OPM-specific command. |
|
0xC01E0520 STATUS_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED |
The DxgkDdiOPMGetCOPPCompatibleInformation and DxgkDdiOPMConfigureProtectedOutput functions return this error if the display driver does not support the DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING and DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs. |
|
0xC01E0521 STATUS_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST |
The DxgkDdiOPMConfigureProtectedOutput 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. |
|
0xC01E0580 STATUS_GRAPHICS_I2C_NOT_SUPPORTED |
The monitor connected to the specified video output does not have an I2C bus. |
|
0xC01E0581 STATUS_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST |
No device on the I2C bus has the specified address. |
|
0xC01E0582 STATUS_GRAPHICS_I2C_ERROR_TRANSMITTING_DATA |
An error occurred while transmitting data to the device on the I2C bus. |
|
0xC01E0583 STATUS_GRAPHICS_I2C_ERROR_RECEIVING_DATA |
An error occurred while receiving data from the device on the I2C bus. |
|
0xC01E0584 STATUS_GRAPHICS_DDCCI_VCP_NOT_SUPPORTED |
The monitor does not support the specified VCP code. |
|
0xC01E0585 STATUS_GRAPHICS_DDCCI_INVALID_DATA |
The data received from the monitor is invalid. |
|
0xC01E0586 STATUS_GRAPHICS_DDCCI_MONITOR_RETURNED_INVALID_TIMING_STATUS_BYTE |
A function call failed because a monitor returned an invalid timing status byte when the operating system used the DDC/CI get timing report and timing message command to get a timing report from a monitor. |
|
0xC01E0587 STATUS_GRAPHICS_DDCCI_INVALID_CAPABILITIES_STRING |
A monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification. |
|
0xC01E0588 STATUS_GRAPHICS_MCA_INTERNAL_ERROR |
An internal error caused an operation to fail. |
|
0xC01E0589 STATUS_GRAPHICS_DDCCI_INVALID_MESSAGE_COMMAND |
An operation failed because a DDC/CI message had an invalid value in its command field. |
|
0xC01E058A STATUS_GRAPHICS_DDCCI_INVALID_MESSAGE_LENGTH |
This error occurred because a DDC/CI message had an invalid value in its length field. |
|
0xC01E058B STATUS_GRAPHICS_DDCCI_INVALID_MESSAGE_CHECKSUM |
This error occurred because the value in a DDC/CI message's checksum field 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. |
|
0xC01E058C STATUS_GRAPHICS_INVALID_PHYSICAL_MONITOR_HANDLE |
This function failed because an invalid monitor handle was passed to it. |
|
0xC01E058D STATUS_GRAPHICS_MONITOR_NO_LONGER_EXISTS |
The operating system asynchronously destroyed the monitor that 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 or stopped, or a display mode change occurred. A display mode change occurs when Windows sends a WM_DISPLAYCHANGE message to applications. |
|
0xC01E05E0 STATUS_GRAPHICS_ONLY_CONSOLE_SESSION_SUPPORTED |
This function can be used only if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session. |
|
0xC01E05E1 STATUS_GRAPHICS_NO_DISPLAY_DEVICE_CORRESPONDS_TO_NAME |
This function cannot find an actual GDI display device that corresponds to the specified GDI display device name. |
|
0xC01E05E2 STATUS_GRAPHICS_DISPLAY_DEVICE_NOT_ATTACHED_TO_DESKTOP |
The function failed because the specified GDI display device was not attached to the Windows desktop. |
|
0xC01E05E3 STATUS_GRAPHICS_MIRRORING_DEVICES_NOT_SUPPORTED |
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. |
|
0xC01E05E4 STATUS_GRAPHICS_INVALID_POINTER |
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is null, is not correctly aligned, or points to an invalid address or to a kernel mode address. |
|
0xC01E05E5 STATUS_GRAPHICS_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE |
This function failed because the GDI device passed to it did not have a monitor associated with it. |
|
0xC01E05E6 STATUS_GRAPHICS_PARAMETER_ARRAY_TOO_SMALL |
An array passed to the function cannot hold all of the data that the function must copy into the array. |
|
0xC01E05E7 STATUS_GRAPHICS_INTERNAL_ERROR |
An internal error caused an operation to fail. |
|
0xC01E05E8 STATUS_GRAPHICS_SESSION_TYPE_CHANGE_IN_PROGRESS |
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. Three types of sessions currently exist: console, disconnected, and remote (RDP or ICA). |
|
0xC0210000 STATUS_FVE_LOCKED_VOLUME |
The volume must be unlocked before it can be used. |
|
0xC0210001 STATUS_FVE_NOT_ENCRYPTED |
The volume is fully decrypted and no key is available. |
|
0xC0210002 STATUS_FVE_BAD_INFORMATION |
The control block for the encrypted volume is not valid. |
|
0xC0210003 STATUS_FVE_TOO_SMALL |
Not enough free space remains on the volume to allow encryption. |
|
0xC0210004 STATUS_FVE_FAILED_WRONG_FS |
The partition cannot be encrypted because the file system is not supported. |
|
0xC0210005 STATUS_FVE_FAILED_BAD_FS |
The file system is inconsistent. Run the Check Disk utility. |
|
0xC0210006 STATUS_FVE_FS_NOT_EXTENDED |
The file system does not extend to the end of the volume. |
|
0xC0210007 STATUS_FVE_FS_MOUNTED |
This operation cannot be performed while a file system is mounted on the volume. |
|
0xC0210008 STATUS_FVE_NO_LICENSE |
BitLocker Drive Encryption is not included with this version of Windows. |
|
0xC0210009 STATUS_FVE_ACTION_NOT_ALLOWED |
The requested action was denied by the FVE control engine. |
|
0xC021000A STATUS_FVE_BAD_DATA |
The data supplied is malformed. |
|
0xC021000B STATUS_FVE_VOLUME_NOT_BOUND |
The volume is not bound to the system. |
|
0xC021000C STATUS_FVE_NOT_DATA_VOLUME |
The volume specified is not a data volume. |
|
0xC021000D STATUS_FVE_CONV_READ_ERROR |
A read operation failed while converting the volume. |
|
0xC021000E STATUS_FVE_CONV_WRITE_ERROR |
A write operation failed while converting the volume. |
|
0xC021000F STATUS_FVE_OVERLAPPED_UPDATE |
The control block for the encrypted volume was updated by another thread. Try again. |
|
0xC0210010 STATUS_FVE_FAILED_SECTOR_SIZE |
The volume encryption algorithm cannot be used on this sector size. |
|
0xC0210011 STATUS_FVE_FAILED_AUTHENTICATION |
BitLocker recovery authentication failed. |
|
0xC0210012 STATUS_FVE_NOT_OS_VOLUME |
The volume specified is not the boot operating system volume. |
|
0xC0210013 STATUS_FVE_KEYFILE_NOT_FOUND |
The BitLocker startup key or recovery password could not be read from external media. |
|
0xC0210014 STATUS_FVE_KEYFILE_INVALID |
The BitLocker startup key or recovery password file is corrupt or invalid. |
|
0xC0210015 STATUS_FVE_KEYFILE_NO_VMK |
The BitLocker encryption key could not be obtained from the startup key or the recovery password. |
|
0xC0210016 STATUS_FVE_TPM_DISABLED |
The TPM is disabled. |
|
0xC0210017 STATUS_FVE_TPM_SRK_AUTH_NOT_ZERO |
The authorization data for the SRK of the TPM is not zero. |
|
0xC0210018 STATUS_FVE_TPM_INVALID_PCR |
The system boot information changed or the TPM locked out access to BitLocker encryption keys until the computer is restarted. |
|
0xC0210019 STATUS_FVE_TPM_NO_VMK |
The BitLocker encryption key could not be obtained from the TPM. |
|
0xC021001A STATUS_FVE_PIN_INVALID |
The BitLocker encryption key could not be obtained from the TPM and PIN. |
|
0xC021001B STATUS_FVE_AUTH_INVALID_APPLICATION |
A boot application hash does not match the hash computed when BitLocker was turned on. |
|
0xC021001C STATUS_FVE_AUTH_INVALID_CONFIG |
The Boot Configuration Data (BCD) settings are not supported or have changed because BitLocker was enabled. |
|
0xC021001D STATUS_FVE_DEBUGGER_ENABLED |
Boot debugging is enabled. Run Windows Boot Configuration Data Store Editor (bcdedit.exe) to turn it off. |
|
0xC021001E STATUS_FVE_DRY_RUN_FAILED |
The BitLocker encryption key could not be obtained. |
|
0xC021001F STATUS_FVE_BAD_METADATA_POINTER |
The metadata disk region pointer is incorrect. |
|
0xC0210020 STATUS_FVE_OLD_METADATA_COPY |
The backup copy of the metadata is out of date. |
|
0xC0210021 STATUS_FVE_REBOOT_REQUIRED |
No action was taken because a system restart is required. |
|
0xC0210022 STATUS_FVE_RAW_ACCESS |
No action was taken because BitLocker Drive Encryption is in RAW access mode. |
|
0xC0210023 STATUS_FVE_RAW_BLOCKED |
BitLocker Drive Encryption cannot enter RAW access mode for this volume. |
|
0xC0210026 STATUS_FVE_NO_FEATURE_LICENSE |
This feature of BitLocker Drive Encryption is not included with this version of Windows. |
|
0xC0210027 STATUS_FVE_POLICY_USER_DISABLE_RDV_NOT_ALLOWED |
Group policy does not permit turning off BitLocker Drive Encryption on roaming data volumes. |
|
0xC0210028 STATUS_FVE_CONV_RECOVERY_FAILED |
Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected. |
|
0xC0210029 STATUS_FVE_VIRTUALIZED_SPACE_TOO_BIG |
The requested virtualization size is too big. |
|
0xC0210030 STATUS_FVE_VOLUME_TOO_SMALL |
The drive is too small to be protected using BitLocker Drive Encryption. |
|
0xC0220001 STATUS_FWP_CALLOUT_NOT_FOUND |
The callout does not exist. |
|
0xC0220002 STATUS_FWP_CONDITION_NOT_FOUND |
The filter condition does not exist. |
|
0xC0220003 STATUS_FWP_FILTER_NOT_FOUND |
The filter does not exist. |
|
0xC0220004 STATUS_FWP_LAYER_NOT_FOUND |
The layer does not exist. |
|
0xC0220005 STATUS_FWP_PROVIDER_NOT_FOUND |
The provider does not exist. |
|
0xC0220006 STATUS_FWP_PROVIDER_CONTEXT_NOT_FOUND |
The provider context does not exist. |
|
0xC0220007 STATUS_FWP_SUBLAYER_NOT_FOUND |
The sublayer does not exist. |
|
0xC0220008 STATUS_FWP_NOT_FOUND |
The object does not exist. |
|
0xC0220009 STATUS_FWP_ALREADY_EXISTS |
An object with that GUID or LUID already exists. |
|
0xC022000A STATUS_FWP_IN_USE |
The object is referenced by other objects and cannot be deleted. |
|
0xC022000B STATUS_FWP_DYNAMIC_SESSION_IN_PROGRESS |
The call is not allowed from within a dynamic session. |
|
0xC022000C STATUS_FWP_WRONG_SESSION |
The call was made from the wrong session and cannot be completed. |
|
0xC022000D STATUS_FWP_NO_TXN_IN_PROGRESS |
The call must be made from within an explicit transaction. |
|
0xC022000E STATUS_FWP_TXN_IN_PROGRESS |
The call is not allowed from within an explicit transaction. |
|
0xC022000F STATUS_FWP_TXN_ABORTED |
The explicit transaction has been forcibly canceled. |
|
0xC0220010 STATUS_FWP_SESSION_ABORTED |
The session has been canceled. |
|
0xC0220011 STATUS_FWP_INCOMPATIBLE_TXN |
The call is not allowed from within a read-only transaction. |
|
0xC0220012 STATUS_FWP_TIMEOUT |
The call timed out while waiting to acquire the transaction lock. |
|
0xC0220013 STATUS_FWP_NET_EVENTS_DISABLED |
The collection of network diagnostic events is disabled. |
|
0xC0220014 STATUS_FWP_INCOMPATIBLE_LAYER |
The operation is not supported by the specified layer. |
|
0xC0220015 STATUS_FWP_KM_CLIENTS_ONLY |
The call is allowed for kernel-mode callers only. |
|
0xC0220016 STATUS_FWP_LIFETIME_MISMATCH |
The call tried to associate two objects with incompatible lifetimes. |
|
0xC0220017 STATUS_FWP_BUILTIN_OBJECT |
The object is built-in and cannot be deleted. |
|
0xC0220018 STATUS_FWP_TOO_MANY_BOOTTIME_FILTERS |
The maximum number of boot-time filters has been reached. |
|
0xC0220018 STATUS_FWP_TOO_MANY_CALLOUTS |
The maximum number of callouts has been reached. |
|
0xC0220019 STATUS_FWP_NOTIFICATION_DROPPED |
A notification could not be delivered because a message queue has reached maximum capacity. |
|
0xC022001A STATUS_FWP_TRAFFIC_MISMATCH |
The traffic parameters do not match those for the security association context. |
|
0xC022001B STATUS_FWP_INCOMPATIBLE_SA_STATE |
The call is not allowed for the current security association state. |
|
0xC022001C STATUS_FWP_NULL_POINTER |
A required pointer is null. |
|
0xC022001D STATUS_FWP_INVALID_ENUMERATOR |
An enumerator is not valid. |
|
0xC022001E STATUS_FWP_INVALID_FLAGS |
The flags field contains an invalid value. |
|
0xC022001F STATUS_FWP_INVALID_NET_MASK |
A network mask is not valid. |
|
0xC0220020 STATUS_FWP_INVALID_RANGE |
An FWP_RANGE is not valid. |
|
0xC0220021 STATUS_FWP_INVALID_INTERVAL |
The time interval is not valid. |
|
0xC0220022 STATUS_FWP_ZERO_LENGTH_ARRAY |
An array that must contain at least one element has a zero length. |
|
0xC0220023 STATUS_FWP_NULL_DISPLAY_NAME |
The displayData.name field cannot be null. |
|
0xC0220024 STATUS_FWP_INVALID_ACTION_TYPE |
The action type is not one of the allowed action types for a filter. |
|
0xC0220025 STATUS_FWP_INVALID_WEIGHT |
The filter weight is not valid. |
|
0xC0220026 STATUS_FWP_MATCH_TYPE_MISMATCH |
A filter condition contains a match type that is not compatible with the operands. |
|
0xC0220027 STATUS_FWP_TYPE_MISMATCH |
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
|
0xC0220028 STATUS_FWP_OUT_OF_BOUNDS |
An integer value is outside the allowed range. |
|
0xC0220029 STATUS_FWP_RESERVED |
A reserved field is nonzero. |
|
0xC022002A STATUS_FWP_DUPLICATE_CONDITION |
A filter cannot contain multiple conditions operating on a single field. |
|
0xC022002B STATUS_FWP_DUPLICATE_KEYMOD |
A policy cannot contain the same keying module more than once. |
|
0xC022002C STATUS_FWP_ACTION_INCOMPATIBLE_WITH_LAYER |
The action type is not compatible with the layer. |
|
0xC022002D STATUS_FWP_ACTION_INCOMPATIBLE_WITH_SUBLAYER |
The action type is not compatible with the sublayer. |
|
0xC022002E STATUS_FWP_CONTEXT_INCOMPATIBLE_WITH_LAYER |
The raw context or the provider context is not compatible with the layer. |
|
0xC022002F STATUS_FWP_CONTEXT_INCOMPATIBLE_WITH_CALLOUT |
The raw context or the provider context is not compatible with the callout. |
|
0xC0220030 STATUS_FWP_INCOMPATIBLE_AUTH_METHOD |
The authentication method is not compatible with the policy type. |
|
0xC0220031 STATUS_FWP_INCOMPATIBLE_DH_GROUP |
The Diffie-Hellman group is not compatible with the policy type. |
|
0xC0220032 STATUS_FWP_EM_NOT_SUPPORTED |
An IKE policy cannot contain an Extended Mode policy. |
|
0xC0220033 STATUS_FWP_NEVER_MATCH |
The enumeration template or subscription will never match any objects. |
|
0xC0220034 STATUS_FWP_PROVIDER_CONTEXT_MISMATCH |
The provider context is of the wrong type. |
|
0xC0220035 STATUS_FWP_INVALID_PARAMETER |
The parameter is incorrect. |
|
0xC0220036 STATUS_FWP_TOO_MANY_SUBLAYERS |
The maximum number of sublayers has been reached. |
|
0xC0220037 STATUS_FWP_CALLOUT_NOTIFICATION_FAILED |
The notification function for a callout returned an error. |
|
0xC0220038 STATUS_FWP_INCOMPATIBLE_AUTH_CONFIG |
The IPsec authentication configuration is not compatible with the authentication type. |
|
0xC0220039 STATUS_FWP_INCOMPATIBLE_CIPHER_CONFIG |
The IPsec cipher configuration is not compatible with the cipher type. |
|
0xC022003C STATUS_FWP_DUPLICATE_AUTH_METHOD |
A policy cannot contain the same auth method more than once. |
|
0xC0220100 STATUS_FWP_TCPIP_NOT_READY |
The TCP/IP stack is not ready. |
|
0xC0220101 STATUS_FWP_INJECT_HANDLE_CLOSING |
The injection handle is being closed by another thread. |
|
0xC0220102 STATUS_FWP_INJECT_HANDLE_STALE |
The injection handle is stale. |
|
0xC0220103 STATUS_FWP_CANNOT_PEND |
The classify cannot be pended. |
|
0xC0230002 STATUS_NDIS_CLOSING |
The binding to the network interface is being closed. |
|
0xC0230004 STATUS_NDIS_BAD_VERSION |
An invalid version was specified. |
|
0xC0230005 STATUS_NDIS_BAD_CHARACTERISTICS |
An invalid characteristics table was used. |
|
0xC0230006 STATUS_NDIS_ADAPTER_NOT_FOUND |
Failed to find the network interface or the network interface is not ready. |
|
0xC0230007 STATUS_NDIS_OPEN_FAILED |
Failed to open the network interface. |
|
0xC0230008 STATUS_NDIS_DEVICE_FAILED |
The network interface has encountered an internal unrecoverable failure. |
|
0xC0230009 STATUS_NDIS_MULTICAST_FULL |
The multicast list on the network interface is full. |
|
0xC023000A STATUS_NDIS_MULTICAST_EXISTS |
An attempt was made to add a duplicate multicast address to the list. |
|
0xC023000B STATUS_NDIS_MULTICAST_NOT_FOUND |
At attempt was made to remove a multicast address that was never added. |
|
0xC023000C STATUS_NDIS_REQUEST_ABORTED |
The network interface aborted the request. |
|
0xC023000D STATUS_NDIS_RESET_IN_PROGRESS |
The network interface cannot process the request because it is being reset. |
|
0xC023000F STATUS_NDIS_INVALID_PACKET |
An attempt was made to send an invalid packet on a network interface. |
|
0xC0230010 STATUS_NDIS_INVALID_DEVICE_REQUEST |
The specified request is not a valid operation for the target device. |
|
0xC0230011 STATUS_NDIS_ADAPTER_NOT_READY |
The network interface is not ready to complete this operation. |
|
0xC0230014 STATUS_NDIS_INVALID_LENGTH |
The length of the buffer submitted for this operation is not valid. |
|
0xC0230015 STATUS_NDIS_INVALID_DATA |
The data used for this operation is not valid. |
|
0xC0230016 STATUS_NDIS_BUFFER_TOO_SHORT |
The length of the submitted buffer for this operation is too small. |
|
0xC0230017 STATUS_NDIS_INVALID_OID |
The network interface does not support this object identifier. |
|
0xC0230018 STATUS_NDIS_ADAPTER_REMOVED |
The network interface has been removed. |
|
0xC0230019 STATUS_NDIS_UNSUPPORTED_MEDIA |
The network interface does not support this media type. |
|
0xC023001A STATUS_NDIS_GROUP_ADDRESS_IN_USE |
An attempt was made to remove a token ring group address that is in use by other components. |
|
0xC023001B STATUS_NDIS_FILE_NOT_FOUND |
An attempt was made to map a file that cannot be found. |
|
0xC023001C STATUS_NDIS_ERROR_READING_FILE |
An error occurred while NDIS tried to map the file. |
|
0xC023001D STATUS_NDIS_ALREADY_MAPPED |
An attempt was made to map a file that is already mapped. |
|
0xC023001E STATUS_NDIS_RESOURCE_CONFLICT |
An attempt to allocate a hardware resource failed because the resource is used by another component. |
|
0xC023001F STATUS_NDIS_MEDIA_DISCONNECTED |
The I/O operation failed because the network media is disconnected or the wireless access point is out of range. |
|
0xC0230022 STATUS_NDIS_INVALID_ADDRESS |
The network address used in the request is invalid. |
|
0xC023002A STATUS_NDIS_PAUSED |
The offload operation on the network interface has been paused. |
|
0xC023002B STATUS_NDIS_INTERFACE_NOT_FOUND |
The network interface was not found. |
|
0xC023002C STATUS_NDIS_UNSUPPORTED_REVISION |
The revision number specified in the structure is not supported. |
|
0xC023002D STATUS_NDIS_INVALID_PORT |
The specified port does not exist on this network interface. |
|
0xC023002E STATUS_NDIS_INVALID_PORT_STATE |
The current state of the specified port on this network interface does not support the requested operation. |
|
0xC023002F STATUS_NDIS_LOW_POWER_STATE |
The miniport adapter is in a lower power state. |
|
0xC02300BB STATUS_NDIS_NOT_SUPPORTED |
The network interface does not support this request. |
|
0xC023100F STATUS_NDIS_OFFLOAD_POLICY |
The TCP connection is not offloadable because of a local policy setting. |
|
0xC0231012 STATUS_NDIS_OFFLOAD_CONNECTION_REJECTED |
The TCP connection is not offloadable by the Chimney offload target. |
|
0xC0231013 STATUS_NDIS_OFFLOAD_PATH_REJECTED |
The IP Path object is not in an offloadable state. |
|
0xC0232000 STATUS_NDIS_DOT11_AUTO_CONFIG_ENABLED |
The wireless LAN interface is in auto-configuration mode and does not support the requested parameter change operation. |
|
0xC0232001 STATUS_NDIS_DOT11_MEDIA_IN_USE |
The wireless LAN interface is busy and cannot perform the requested operation. |
|
0xC0232002 STATUS_NDIS_DOT11_POWER_STATE_INVALID |
The wireless LAN interface is power down and does not support the requested operation. |
|
0xC0232003 STATUS_NDIS_PM_WOL_PATTERN_LIST_FULL |
The list of wake on LAN patterns is full. |
|
0xC0232004 STATUS_NDIS_PM_PROTOCOL_OFFLOAD_LIST_FULL |
The list of low power protocol offloads is full. |
|
0xC0360001 STATUS_IPSEC_BAD_SPI |
The SPI in the packet does not match a valid IPsec SA. |
|
0xC0360002 STATUS_IPSEC_SA_LIFETIME_EXPIRED |
The packet was received on an IPsec SA whose lifetime has expired. |
|
0xC0360003 STATUS_IPSEC_WRONG_SA |
The packet was received on an IPsec SA that does not match the packet characteristics. |
|
0xC0360004 STATUS_IPSEC_REPLAY_CHECK_FAILED |
The packet sequence number replay check failed. |
|
0xC0360005 STATUS_IPSEC_INVALID_PACKET |
The IPsec header and/or trailer in the packet is invalid. |
|
0xC0360006 STATUS_IPSEC_INTEGRITY_CHECK_FAILED |
The IPsec integrity check failed. |
|
0xC0360007 STATUS_IPSEC_CLEAR_TEXT_DROP |
IPsec dropped a clear text packet. |
|
0xC0360008 STATUS_IPSEC_AUTH_FIREWALL_DROP |
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
|
0xC0360009 STATUS_IPSEC_THROTTLE_DROP |
IPsec dropped a packet due to DOS throttle. |
|
0xC0368000 STATUS_IPSEC_DOSP_BLOCK |
IPsec Dos Protection matched an explicit block rule. |
|
0xC0368001 STATUS_IPSEC_DOSP_RECEIVED_MULTICAST |
IPsec Dos Protection received an IPsec specific multicast packet which is not allowed. |
|
0xC0368002 STATUS_IPSEC_DOSP_INVALID_PACKET |
IPsec Dos Protection received an incorrectly formatted packet. |
|
0xC0368003 STATUS_IPSEC_DOSP_STATE_LOOKUP_FAILED |
IPsec Dos Protection failed to lookup state. |
|
0xC0368004 STATUS_IPSEC_DOSP_MAX_ENTRIES |
IPsec Dos Protection failed to create state because there are already maximum number of entries allowed by policy. |
|
0xC0368005 STATUS_IPSEC_DOSP_KEYMOD_NOT_ALLOWED |
IPsec Dos Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
|
0xC0368006 STATUS_IPSEC_DOSP_MAX_PER_IP_RATELIMIT_QUEUES |
IPsec Dos Protection failed to create per internal IP ratelimit queue because there is already maximum number of queues allowed by policy. |
|
0xC038005B STATUS_VOLMGR_MIRROR_NOT_SUPPORTED |
The system does not support mirrored volumes. |
|
0xC038005C STATUS_VOLMGR_RAID5_NOT_SUPPORTED |
The system does not support RAID-5 volumes. |
|
0xC03A0014 STATUS_VIRTDISK_PROVIDER_NOT_FOUND |
A virtual disk support provider for the specified file was not found. |
|
0xC03A0015 STATUS_VIRTDISK_NOT_VIRTUAL_DISK |
The specified disk is not a virtual disk. |
|
0xC03A0016 STATUS_VHD_PARENT_VHD_ACCESS_DENIED |
The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk. |
|
0xC03A0017 STATUS_VHD_CHILD_PARENT_SIZE_MISMATCH |
The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. |
|
0xC03A0018 STATUS_VHD_DIFFERENCING_CHAIN_CYCLE_DETECTED |
The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. |
|
0xC03A0019 STATUS_VHD_DIFFERENCING_CHAIN_ERROR_IN_PARENT |
The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. |