0x8000001F: A COM call to an ASTA was blocked because the call chain originated in or passed through another ASTA. This call pattern is deadlock-prone and disallowed by apartment call control.[1]
0x8004D00B: The requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero.[1]
0x8004D00C: There is no resource presently associated with this enlistment[1]
0x8004D00D: The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers.[1]
0x8004D00E: The transaction has already been implicitly or explicitly committed or aborted[1]
0x8004D00F: An invalid combination of flags was specified[1]
0x8004D010: The resource manager id is not associated with this transaction or the transaction manager.[1]
0x8004D011: This method was called in the wrong state[1]
0x8004D012: The indicated unit of work does not match the unit of work expected by the resource manager.[1]
0x8004D013: An enlistment in a transaction already exists.[1]
0x8004D014: An import object for the transaction could not be found.[1]
0x8004D02A: The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.[1]
0x8004D02B: The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.[1]
0x8004D02C: The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions.[1]
0x0004D002: The method call succeeded because the transaction was read-only.[1]
0x0004D003: The transaction was successfully aborted. However, this is a coordinated transaction, and some number of enlisted resources were aborted outright because they could not support abort-retaining semantics[1]
0x0004D004: No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes.[1]
0x0004D005: The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call.[1]
0x0004D006: The sink is for the moment and wishes the transaction to proceed, but if other changes are made following this return by other event sinks then this sink wants another chance to look[1]
0x0004D007: The transaction was successfully aborted. However, the abort was non-retaining.[1]
0x0004D008: An abort operation was already in progress.[1]
0x0004D009: The resource manager has performed a single-phase commit of the transaction.[1]
0x0004D00A: The local transaction has not aborted.[1]
0x0004D010: The resource manager has requested to be the coordinator (last resource manager) for the transaction.[1]
0x8004E002: The root transaction wanted to commit, but transaction aborted[1]
0x8004E003: You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting.[1]
0x8004E02B: An attempt to use a database generated a database specific error.[1]
0x8004E02C: The COM+ component you created must use object pooling to work.[1]
0x8004E02D: The COM+ component you created must use object construction to work correctly.[1]
0x8004E02E: The COM+ component requires synchronization, and it is not configured for it.[1]
0x8004E02F: The TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the "root" component for the transaction. The creation failed.[1]
0x8004E030: The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope.[1]
0x8004E031: The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning.[1]
0x00040000: Use the registry database to provide the requested information[1]
0x80080008: Object server is stopping when OLE service contacts it[1]
0x80080009: An invalid root block pointer was specified[1]
0x80080010: An allocation chain contained an invalid link pointer[1]
0x80080011: The requested allocation size was too large[1]
0x00080012: Not all the requested interfaces were available[1]
0x00080013: The specified machine name was not found in the cache.[1]
0x80080015: The activation requires a display name to be present under the CLSID key.[1]
0x80080016: The activation requires that the RunAs value for the application is Activate As Activator.[1]
0x80080017: The class is not configured to support Elevated activation.[1]
0x80080200: Appx packaging API has encountered an internal error.[1]
0x80080201: The file is not a valid Appx package because its contents are interleaved.[1]
0x80080202: The file is not a valid Appx package because it contains OPC relationships.[1]
0x80080203: The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present.[1]
0x80080204: The Appx package's manifest is invalid.[1]
0x80080205: The Appx package's block map is invalid.[1]
0x80080206: The Appx package's content cannot be read because it is corrupt.[1]
0x80080207: The computed hash value of the block does not match the one stored in the block map.[1]
0x80080208: The requested byte range is over 4GB when translated to byte range of blocks.[1]
0x80080209: The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data.[1]
0x8008020A: The APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data.[1]
0x80080300: The background task activation is spurious.[1]
0x80010115: OLE has sent a request and is waiting for a reply.[1]
0x80010116: OLE is waiting before retrying a request.[1]
0x80010117: Call context cannot be accessed after call completed.[1]
0x80010118: Impersonate on unsecure calls is not supported.[1]
0x80010119: Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized.[1]
0x8001011A: No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server.[1]
0x8009030D: The credentials supplied to the package were not recognized[1]
0x8009030E: No credentials are available in the security package[1]
0x8009030F: The message or signature supplied for verification has been altered[1]
0x80090310: The message supplied for verification is out of sequence[1]
0x80090311: No authority could be contacted for authentication.[1]
0x00090312: The function completed successfully, but must be called again to complete the context[1]
0x00090313: The function completed successfully, but CompleteToken must be called[1]
0x00090314: The function completed successfully, but both CompleteToken and this function must be called to complete the context[1]
0x00090315: The logon was completed, but no network authority was available. The logon was made using locally known information[1]
0x80090316: The requested security package does not exist[1]
0x80090317: The context has expired and can no longer be used.[1]
0x00090317: The context has expired and can no longer be used.[1]
0x80090318: The supplied message is incomplete. The signature was not verified.[1]
0x80090320: The credentials supplied were not complete, and could not be verified. The context could not be initialized.[1]
0x80090321: The buffers supplied to a function was too small.[1]
0x00090320: The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context.[1]
0x00090321: The context data must be renegotiated with the peer.[1]
0x80090322: The target principal name is incorrect.[1]
0x00090323: There is no LSA mode context associated with this context.[1]
0x80090324: The clocks on the client and server machines are skewed.[1]
0x80090325: The certificate chain was issued by an authority that is not trusted.[1]
0x80090326: The message received was unexpected or badly formatted.[1]
0x80090327: An unknown error occurred while processing the certificate.[1]
0x80090328: The received certificate has expired.[1]
0x80090329: The specified data could not be encrypted.[1]
0x80090330: The specified data could not be decrypted.[1]
0x80090331: The client and server cannot communicate, because they do not possess a common algorithm.[1]
0x80090332: The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation).[1]
0x80090333: A security context was deleted before the context was completed. This is considered a logon failure.[1]
0x80090334: The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply.[1]
0x80090335: Unable to accomplish the requested task because the local machine does not have any IP addresses.[1]
0x80090336: The supplied credential handle does not match the credential associated with the security context.[1]
0x80090337: The crypto system or checksum function is invalid because a required function is unavailable.[1]
0x80090338: The number of maximum ticket referrals has been exceeded.[1]
0x80090339: The local machine must be a Kerberos KDC (domain controller) and it is not.[1]
0x8009033A: The other end of the security negotiation is requires strong crypto but it is not supported on the local machine.[1]
0x8009033B: The KDC reply contained more than one principal name.[1]
0x8009033C: Expected to find PA data for a hint of what etype to use, but it was not found.[1]
0x8009033D: The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator.[1]
0x8009033E: Smartcard logon is required and was not used.[1]
0x80090340: An invalid request was sent to the KDC.[1]
0x80090341: The KDC was unable to generate a referral for the service requested.[1]
0x80090342: The encryption type requested is not supported by the KDC.[1]
0x80090343: An unsupported preauthentication mechanism was presented to the Kerberos package.[1]
0x80090345: The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.[1]
0x80090346: Client's supplied SSPI channel bindings were incorrect.[1]
0x80090347: The received certificate was mapped to multiple accounts.[1]
0x80090349: The certificate is not valid for the requested usage.[1]
0x80090350: The system cannot contact a domain controller to service the authentication request. Please try again later.[1]
0x80090351: The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log.[1]
0x80090352: An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator.[1]
0x80090353: The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator.[1]
0x80090354: The smartcard certificate used for authentication was not trusted. Please contact your system administrator.[1]
0x80090355: The smartcard certificate used for authentication has expired. Please contact your system administrator.[1]
0x80090356: The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user.[1]
0x80090357: An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator.[1]
0x80090358: The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator.[1]
0x80090359: An untrusted certificate authority was detected while processing the domain controller certificate used for authentication. There is additional information in the system event log. Please contact your system administrator.[1]
0x8009035A: The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log.[1]
0x8009035B: The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log.[1]
0x0009035C: A signature operation must be performed before the user can authenticate.[1]
0x8009035D: One or more of the parameters passed to the function was invalid.[1]
0x8009035E: Client policy does not allow credential delegation to target server.[1]
0x8009035F: Client policy does not allow credential delegation to target server with NLTM only authentication.[1]
0x00090360: The recipient rejected the renegotiation request.[1]
0x80090361: The required security context does not exist.[1]
0x80090362: The PKU2U protocol encountered an error while attempting to utilize the associated certificates.[1]
0x80090363: The identity of the server computer could not be verified.[1]
0x00090364: The returned buffer is only a fragment of the message. More fragments need to be returned.[1]
0x80092011: No Dll or exported function was found to verify revocation.[1]
0x80092012: The revocation function was unable to check revocation for the certificate.[1]
0x80092013: The revocation function was unable to check revocation because the revocation server was offline.[1]
0x80092014: The certificate is not in the revocation server's database.[1]
0x80092020: The string contains a non-numeric character.[1]
0x80092021: The string contains a non-printable character.[1]
0x80092022: The string contains a character not in the 7 bit ASCII character set.[1]
0x80092023: The string contains an invalid X500 name attribute key, oid, value or delimiter.[1]
0x80092024: The dwValueType for the CERT_NAME_VALUE is not one of the character strings. Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_RDN_OCTET_STRING.[1]
0x80092025: The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done.[1]
0x80092026: The cryptographic operation failed due to a local security option setting.[1]
0x80092027: No DLL or exported function was found to verify subject usage.[1]
0x80092028: The called function was unable to do a usage check on the subject.[1]
0x80092029: Since the server was offline, the called function was unable to complete the usage check.[1]
0x8009202A: The subject was not found in a Certificate Trust List (CTL).[1]
0x8009202B: None of the signers of the cryptographic message or certificate trust list is trusted.[1]
0x8009202C: The public key's algorithm parameters are missing.[1]
0x8009202D: An object could not be located using the object locator infrastructure with the given name.[1]
0x80093000: OSS Certificate encode/decode error code base
See asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR.[1]
0x80093001: OSS ASN.1 Error: Output Buffer is too small.[1]
0x80093002: OSS ASN.1 Error: Signed integer is encoded as a unsigned integer.[1]
0x80093003: OSS ASN.1 Error: Unknown ASN.1 data type.[1]
0x80093004: OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated.[1]
0x80094003: The request's current status does not allow this operation.[1]
0x80094004: The requested property value is empty.[1]
0x80094005: The certification authority's certificate contains invalid data.[1]
0x80094006: Certificate service has been suspended for a database restore operation.[1]
0x80094007: The certificate contains an encoded length that is potentially incompatible with older enrollment software.[1]
0x80094008: The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation.[1]
0x80094009: The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester.[1]
0x8009400A: Cannot archive private key. The certification authority is not configured for key archival.[1]
0x8009400B: Cannot archive private key. The certification authority could not verify one or more key recovery certificates.[1]
0x8009400C: The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature.[1]
0x8009400D: At least one security principal must have the permission to manage this CA.[1]
0x8009400E: The request contains an invalid renewal certificate attribute.[1]
0x8009400F: An attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions.[1]
0x80094010: A memory reference caused a data alignment fault.[1]
0x80094011: The permissions on this certification authority do not allow the current user to enroll for certificates.[1]
0x80094012: The permissions on the certificate template do not allow the current user to enroll for this type of certificate.[1]
0x80094013: The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access.[1]
0x80094014: The request was denied by a certificate manager or CA administrator.[1]
0x80094015: An enrollment policy server cannot be located.[1]
0x80094016: A signature algorithm or public key length does not meet the system's minimum required strength.[1]
0x80094017: Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation.[1]
0x80094018: No encryption certificate was specified.[1]
0x80094800: The requested certificate template is not supported by this CA.[1]
0x80094801: The request contains no certificate template information.[1]
0x80094802: The request contains conflicting template information.[1]
0x80094803: The request is missing a required Subject Alternate name extension.[1]
0x80094804: The request is missing a required private key for archival by the server.[1]
0x80094805: The request is missing a required SMIME capabilities extension.[1]
0x80094806: The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request.[1]
0x80094807: The request template version is newer than the supported template version.[1]
0x80094808: The template is missing a required signature policy attribute.[1]
0x80094809: The request is missing required signature policy information.[1]
0x8009480A: The request is missing one or more required signatures.[1]
0x8009480B: One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures.[1]
0x8009480C: The request is missing one or more required signature issuance policies.[1]
0x8009480D: The UPN is unavailable and cannot be added to the Subject Alternate name.[1]
0x8009480E: The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name.[1]
0x8009480F: The DNS name is unavailable and cannot be added to the Subject Alternate name.[1]
0x80094810: The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template.[1]
0x80094811: The public key does not meet the minimum size required by the specified certificate template.[1]
0x80094812: The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name.[1]
0x80094813: One or more certificate templates to be enabled on this certification authority could not be found.[1]
0x80094814: The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed.[1]
0x80094815: The certificate template requires too many RA signatures. Only one RA signature is allowed.[1]
0x80094816: The certificate template requires renewal with the same public key, but the request uses a different public key.[1]
0x80094817: The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent.[1]
0x80094818: The certification authority cannot validate the Attestation Identity Key Id Binding.[1]
0x80094819: The certification authority cannot validate the private key attestation data.[1]
0x8009481A: The request does not support private key attestation as defined in the certificate template.[1]
0x8009481B: The request public key is not consistent with the private key attestation data.[1]
0x8009481C: The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable.[1]
0x8009481D: The attestation response could not be validated. It is either unexpected or incorrect.[1]
0x8009481E: A valid Request ID was not detected in the request attributes, or an invalid one was submitted.[1]
0x800B0009: The size of the data could not be determined.[1]
0x800B000A: The size of the indefinite-sized data could not be determined.[1]
0x800B000B: This object does not read and write self-sizing data.[1]
0x800B0100: No signature was present in the subject.[1]
0x800B0101: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.[1]
0x800B0102: The validity periods of the certification chain do not nest correctly.[1]
0x800B0103: A certificate that can only be used as an end-entity is being used as a CA or vice versa.[1]
0x800B0104: A path length constraint in the certification chain has been violated.[1]
0x800B0105: A certificate contains an unknown extension that is marked 'critical'.[1]
0x800B0106: A certificate being used for a purpose other than the ones specified by its CA.[1]
0x800B0107: A parent of a given certificate in fact did not issue that child certificate.[1]
0x800B0108: A certificate is missing or has an empty value for an important field, such as a subject or issuer name.[1]
0x800B0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.[1]
0x800B010A: A certificate chain could not be built to a trusted root authority.[1]
0x800F0236: The operation involving unsigned file copying was rolled back, so that a system restore point could be set.[1]
0x800F0237: An INF was copied into the Windows INF directory in an improper manner.[1]
0x800F0238: The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product.[1]
0x800F0239: An unknown exception was encountered.[1]
0x800F023A: A problem was encountered when accessing the Plug and Play registry database.[1]
0x800F023B: The requested operation is not supported for a remote machine.[1]
0x800F023C: The specified file is not an installed OEM INF.[1]
0x800F023D: One or more devices are presently installed using the specified INF.[1]
0x800F023E: The requested device install operation is obsolete.[1]
0x800F023F: A file could not be verified because it does not have an associated catalog signed via Authenticode(tm).[1]
0x800F0240: Authenticode(tm) signature verification is not supported for the specified INF.[1]
0x800F0241: The INF was signed with an Authenticode(tm) catalog from a trusted publisher.[1]
0x800F0242: The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.[1]
0x800F0243: The publisher of an Authenticode(tm) signed catalog was not established as trusted.[1]
0x800F0244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.[1]
0x800F0245: The file may only be validated by a catalog signed via Authenticode(tm).[1]
0x800F0246: One of the installers for this device cannot perform the installation at this time.[1]
0x800F0247: A problem was encountered while attempting to add the driver to the store.[1]
0x800F0248: The installation of this device is forbidden by system policy. Contact your system administrator.[1]
0x800F0249: The installation of this driver is forbidden by system policy. Contact your system administrator.[1]
0x800F024A: The specified INF is the wrong type for this operation.[1]
0x800F024B: The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.[1]
0x800F024C: A problem was encountered while attempting to delete the driver from the store.[1]
0x800F0300: An unrecoverable stack overflow was encountered.[1]
0x800F1000: No installed components were detected.[1]
0x80100001: An internal consistency check failed.[1]
0x80100002: The action was cancelled by an SCardCancel request.[1]
0x80110429: The file does not contain components or component information[1]
0x8011042A: Changes to this object and its sub-objects have been disabled[1]
0x8011042B: The delete function has been disabled for this object[1]
0x8011042C: The server catalog version is not supported[1]
0x8011042D: The component move was disallowed, because the source or destination application is either a system application or currently locked against changes[1]
0x8011042E: The component move failed because the destination application no longer exists[1]
0x80110430: The system was unable to register the TypeLib[1]
0x80110433: This operation cannot be performed on the system application[1]
0x80110434: The component registrar referenced in this file is not available[1]
0x80110435: A component in the same DLL is already installed[1]
0x801F0001: A handler was not defined by the filter for this operation.[1]
0x801F0002: A context is already defined for this object.[1]
0x801F0003: Asynchronous requests are not valid for this operation.[1]
0x801F0004: Disallow the Fast IO path for this operation.[1]
0x801F0005: An invalid name request was made. The name requested cannot be retrieved at this time.[1]
0x801F0006: Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.[1]
0x801F0007: The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver.[1]
0x801F0008: The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).[1]
0x801F0009: The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers.[1]
0x801F000A: The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback.[1]
0x801F000B: The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.[1]
0x801F000C: Non-paged pool must be used for this type of context.[1]
0x801F000D: A duplicate handler definition has been provided for an operation.[1]
0x801F000E: The callback data queue has been disabled.[1]
0x801F000F: Do not attach the filter to the volume at this time.[1]
0x801F0010: Do not detach the filter from the volume at this time.[1]
0x801F0011: An instance already exists at this altitude on the volume specified.[1]
0x801F0012: An instance already exists with this name on the volume specified.[1]
0x801F0013: The system could not find the filter specified.[1]
0x801F0014: The system could not find the volume specified.[1]
0x801F0015: The system could not find the instance specified.[1]
0x801F0016: No registered context allocation definition was found for the given request.[1]
0x801F0017: An invalid parameter was specified during context registration.[1]
0x801F0018: The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.[1]
0x801F0019: The requested device object does not exist for the given volume.[1]
0x801F001A: The specified volume is already mounted.[1]
0x801F001B: The specified Transaction Context is already enlisted in a transaction[1]
0x801F001C: The specifiec context is already attached to another object[1]
0x801F0020: No waiter is present for the filter's reply to this message.[1]
0x801F0023: The filesystem database resource is in use. Registration cannot complete at this time.[1]
0x80260001: {Display Driver Stopped Responding}
The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality.
The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft.[1]
0x80263001: {Desktop composition is disabled}
The operation could not be completed because desktop composition is disabled.[1]
0x80263002: {Some desktop composition APIs are not supported while remoting}
The operation is not supported while running in a remote session.[1]
0x80263003: {No DWM redirection surface is available}
The DWM was unable to provide a redireciton surface to complete the DirectX present.[1]
0x80263004: {DWM is not queuing presents for the specified window}
The window specified is not currently using queued presents.[1]
0x80263005: {The adapter specified by the LUID is not found}
DWM can not find the adapter specified by the LUID.[1]
0x00263005: {GDI redirection surface was returned}
GDI redirection surface of the top level window was returned.[1]
0x80263007: {Redirection surface can not be created. The size of the surface is larger than what is supported on this machine}
Redirection surface can not be created. The size of the surface is larger than what is supported on this machine.[1]
0x00263008: {GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI}
GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI.[1]
0x00261001: Monitor descriptor could not be obtained.[1]
0x00261002: Format of the obtained monitor descriptor is not supported by this release.[1]
0xC0261003: Checksum of the obtained monitor descriptor is invalid.[1]
0xC0261004: Monitor descriptor contains an invalid standard timing block.[1]
0xC0261005: WMI data block registration failed for one of the MSMonitorClass WMI subclasses.[1]
0xC0261006: Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.[1]
0xC0261007: Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.[1]
0xC0261008: There is no monitor descriptor data at the specified (offset, size) region.[1]
0xC0261009: Monitor descriptor contains an invalid detailed timing block.[1]
0xC0262000: Exclusive mode ownership is needed to create unmanaged primary allocation.[1]
0xC0262001: The driver needs more DMA buffer space in order to complete the requested operation.[1]
0xC0262002: Specified display adapter handle is invalid.[1]
0xC0262003: Specified display adapter and all of its state has been reset.[1]
0xC0262004: The driver stack doesn't match the expected driver model.[1]
0xC0262005: Present happened but ended up into the changed desktop mode[1]
0xC0262006: Nothing to present due to desktop occlusion[1]
0xC0262007: Not able to present due to denial of desktop access[1]
0xC0262008: Not able to present with color convertion[1]
0xC0262009: The kernel driver detected a version mismatch between it and the user mode driver.[1]
0x4026200A: Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific).[1]
0xC026200B: Present redirection is disabled (desktop windowing management subsystem is off).[1]
0xC026200C: Previous exclusive VidPn source owner has released its ownership[1]
0xC026200D: Window DC is not available for presentation[1]
0xC026200E: Windowless present is disabled (desktop windowing management subsystem is off).[1]
0xC0262100: Not enough video memory available to complete the operation.[1]
0xC0262101: Couldn't probe and lock the underlying memory of an allocation.[1]
0xC0262304: Specified video present source is invalid.[1]
0xC0262305: Specified video present target is invalid.[1]
0xC0262306: Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).[1]
0x00262307: No mode is pinned on the specified VidPN source/target.[1]
0xC0262308: Specified VidPN source mode set is invalid.[1]
0xC0262309: Specified VidPN target mode set is invalid.[1]
0xC026230A: Specified video signal frequency is invalid.[1]
0xC026230B: Specified video signal active region is invalid.[1]
0xC026230C: Specified video signal total region is invalid.[1]
0xC0262310: Specified video present source mode is invalid.[1]
0xC0262311: Specified video present target mode is invalid.[1]
0xC0262312: Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.[1]
0xC0262313: Specified video present path is already in VidPN's topology.[1]
0xC0262314: Specified mode is already in the mode set.[1]
0xC0262315: Specified video present source set is invalid.[1]
0xC0262316: Specified video present target set is invalid.[1]
0xC0262317: Specified video present source is already in the video present source set.[1]
0xC0262318: Specified video present target is already in the video present target set.[1]
0xC0262319: Specified VidPN present path is invalid.[1]
0xC026231A: Miniport has no recommendation for augmentation of the specified VidPN's topology.[1]
0xC026231B: Specified monitor frequency range set is invalid.[1]
0xC026231C: Specified monitor frequency range is invalid.[1]
0xC026231D: Specified frequency range is not in the specified monitor frequency range set.[1]
0x0026231E: Specified mode set does not specify preference for one of its modes.[1]
0xC026231F: Specified frequency range is already in the specified monitor frequency range set.[1]
0xC0262320: Specified mode set is stale. Please reacquire the new mode set.[1]
0xC0262321: Specified monitor source mode set is invalid.[1]
0xC0262322: Specified monitor source mode is invalid.[1]
0xC0262323: Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.[1]
0xC0262324: ID of the specified mode is already used by another mode in the set.[1]
0xC0262325: System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.[1]
0xC0262326: Number of video present targets must be greater than or equal to the number of video present sources.[1]
0xC0262327: Specified present path is not in VidPN's topology.[1]
0xC0262328: Display adapter must have at least one video present source.[1]
0xC0262329: Display adapter must have at least one video present target.[1]
0xC026232A: Specified monitor descriptor set is invalid.[1]
0xC026232B: Specified monitor descriptor is invalid.[1]
0xC026232C: Specified descriptor is not in the specified monitor descriptor set.[1]
0xC026232D: Specified descriptor is already in the specified monitor descriptor set.[1]
0xC026232E: ID of the specified monitor descriptor is already used by another descriptor in the set.[1]
0xC026232F: Specified video present target subset type is invalid.[1]
0xC0262330: Two or more of the specified resources are not related to each other, as defined by the interface semantics.[1]
0xC0262331: ID of the specified video present source is already used by another source in the set.[1]
0xC0262332: ID of the specified video present target is already used by another target in the set.[1]
0xC0262333: Specified VidPN source cannot be used because there is no available VidPN target to connect it to.[1]
0xC0262334: Newly arrived monitor could not be associated with a display adapter.[1]
0xC0262335: Display adapter in question does not have an associated VidPN manager.[1]
0xC0262336: VidPN manager of the display adapter in question does not have an active VidPN.[1]
0xC0262337: Specified VidPN topology is stale. Please reacquire the new topology.[1]
0xC0262338: There is no monitor connected on the specified video present target.[1]
0xC0262339: Specified source is not part of the specified VidPN's topology.[1]
0xC026233A: Specified primary surface size is invalid.[1]
0xC026233B: Specified visible region size is invalid.[1]
0xC0262503: The specified encrypted parameters are invalid.[1]
0xC0262505: The GDI display device passed to this function does not have any active video outputs.[1]
0xC026250B: An internal error caused this operation to fail.[1]
0xC026250C: The function failed because the caller passed in an invalid OPM user mode handle.[1]
0xC026250E: A certificate could not be returned because the certificate buffer passed to the function was too small.[1]
0xC026250F: A video output could not be created because the frame buffer is in spanning mode.[1]
0xC0262510: A video output could not be created because the frame buffer is in theater mode.[1]
0xC0262511: The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.[1]
0xC0262512: The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.[1]
0xC0262513: The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.[1]
0xC0262514: The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP.[1]
0xC0262515: The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A.[1]
0xC0262516: The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output.[1]
0xC0262517: The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high.[1]
0xC0262518: The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.[1]
0xC026251A: The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop.[1]
0xC026251B: The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote.[1]
0xC026251C: Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only.[1]
0xC026251D: The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.[1]
0xC026251E: The method failed because an unexpected error occurred inside of a display driver.[1]
0xC026251F: Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only.[1]
0xC0262520: The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.[1]
0xC0262521: The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.[1]
0xC0262580: The monitor connected to the specified video output does not have an I2C bus.[1]
0xC0262581: No device on the I2C bus has the specified address.[1]
0xC0262582: An error occurred while transmitting data to the device on the I2C bus.[1]
0xC0262583: An error occurred while receiving data from the device on the I2C bus.[1]
0xC0262584: The monitor does not support the specified VCP code.[1]
0xC0262585: The data received from the monitor is invalid.[1]
0xC0262586: The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor.[1]
0xC0262587: The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.[1]
0xC0262588: An internal Monitor Configuration API error occurred.[1]
0xC0262589: An operation failed because a DDC/CI message had an invalid value in its command field.[1]
0xC026258A: An error occurred because the field length of a DDC/CI message contained an invalid value.[1]
0xC026258B: An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer.[1]
0xC026258C: This function failed because an invalid monitor handle was passed to it.[1]
0xC026258D: The operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications.[1]
0xC02625D8: A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value.[1]
0xC02625D9: The monitor's VCP Version (0xDF) VCP code returned an invalid version value.[1]
0xC02625DA: The monitor does not comply with the MCCS specification it claims to support.[1]
0xC02625DB: The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.[1]
0xC02625DC: The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.[1]
0xC02625DE: The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0xC02625DF: SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0xC02625E0: This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session.[1]
0xC02625E1: This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.[1]
0xC02625E2: The function failed because the specified GDI display device was not attached to the Windows desktop.[1]
0xC02625E3: This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.[1]
0xC02625E4: The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned.[1]
0xC02625E5: The function failed because the specified GDI device did not have any monitors associated with it.[1]
0xC02625E6: An array passed to the function cannot hold all of the data that the function must copy into the array.[1]
0xC02625E7: An internal error caused an operation to fail.[1]
0xC02605E8: The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote.[1]
0x8028001B: The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error.[1]
0x8028001C: The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, check for the latest BIOS or firmware update for your TPM hardware. Consult the computer manufacturer's documentation for instructions.[1]
0x8028001D: The authorization for the second key in a 2 key function failed authorization.[1]
0x8028001E: The tag value sent to for a command is invalid.[1]
0x8028001F: An IO error occurred transmitting information to the TPM.[1]
0x80280020: The encryption process had a problem.[1]
0x80280021: The decryption process did not complete.[1]
0x80280025: The submitted entity type is not allowed.[1]
0x80280026: The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup.[1]
0x80280027: Signed data cannot include additional DER information.[1]
0x80280028: The key properties in TPM_KEY_PARMs are not supported by this TPM.[1]
0x80280029: The migration properties of this key are incorrect.[1]
0x8028002A: The signature or encryption scheme for this key is incorrect or not permitted in this situation.[1]
0x8028002B: The size of the data (or blob) parameter is bad or inconsistent with the referenced key.[1]
0x8028002C: A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob.[1]
0x8028002D: Either the physicalPresence or physicalPresenceLock bits have the wrong value.[1]
0x8028002E: The TPM cannot perform this version of the capability.[1]
0x8028002F: The TPM does not allow for wrapped transport sessions.[1]
0x80280030: TPM audit construction failed and the underlying command was returning a failure code also.[1]
0x80280031: TPM audit construction failed and the underlying command was returning success.[1]
0x80280032: Attempt to reset a PCR register that does not have the resettable attribute.[1]
0x80280033: Attempt to reset a PCR register that requires locality and locality modifier not part of command transport.[1]
0x80280034: Make identity blob not properly typed.[1]
0x80280035: When saving context identified resource type does not match actual resource.[1]
0x80280036: The TPM is attempting to execute a command only available when in FIPS mode.[1]
0x80280037: The command is attempting to use an invalid family ID.[1]
0x80280038: The permission to manipulate the NV storage is not available.[1]
0x80280039: The operation requires a signed command.[1]
0x80284012: The caller does not have the appropriate rights to perform the requested operation.[1]
0x80284013: The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions may be required. The TPM management console (tpm.msc) action to make the TPM Ready may help. For further information, see the documentation for the Win32_Tpm WMI method 'Provision'. (The actions that may be required include importing the TPM Owner Authorization value into the system, calling the Win32_Tpm WMI method for provisioning the TPM and specifying TRUE for either 'ForceClear_Allowed' or 'PhysicalPresencePrompts_Allowed' (as indicated by the value returned in the Additional Information), or enabling the TPM in the system BIOS.)[1]
0x80284014: The Physical Presence Interface of this firmware does not support the requested method.[1]
0x80284015: The requested TPM OwnerAuth value was not found.[1]
0x80284016: The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information.[1]
0x80290100: The command buffer is not in the correct state.[1]
0x80290101: The command buffer does not contain enough data to satisfy the request.[1]
0x80290102: The command buffer cannot contain any more data.[1]
0x80290103: One or more output parameters was NULL or invalid.[1]
0x80290104: One or more input parameters is invalid.[1]
0x80290105: Not enough memory was available to satisfy the request.[1]
0x80290300: A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command.[1]
0x80290301: The user failed to confirm the TPM operation request.[1]
0x80290302: The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM).[1]
0x80290303: The BIOS does not support the physical presence interface.[1]
0x80290304: The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command.[1]
0x80290400: This is an error mask to convert Platform Crypto Provider errors to win errors.[1]
0x80290401: The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational.[1]
0x80290402: The handle provided to the Platform Crypto Provider is invalid.[1]
0x80290403: A parameter provided to the Platform Crypto Provider is invalid.[1]
0x80290404: A provided flag to the Platform Crypto Provider is not supported.[1]
0x80290405: The requested operation is not supported by this Platform Crypto Provider.[1]
0x80290406: The buffer is too small to contain all data. No information has been written to the buffer.[1]
0x80290407: An unexpected internal error has occurred in the Platform Crypto Provider.[1]
0x80290408: The authorization to use a provider object has failed.[1]
0x80290409: The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack.[1]
0x80310002: The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.[1]
0x80310003: The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions.[1]
0x80310004: A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date.[1]
0x80310005: The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).[1]
0x80310006: The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).[1]
0x80310007: At least one secure key protector is required for this operation to be performed.[1]
0x80310008: BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.[1]
0x80310009: BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again.[1]
0x8031000A: The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.[1]
0x8031000B: The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.[1]
0x8031000C: The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.[1]
0x8031000D: The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted.[1]
0x8031000E: The attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects.[1]
0x8031000F: The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.[1]
0x80310010: The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.[1]
0x80310011: The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again.[1]
0x80310012: The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive.[1]
0x80310013: The drive cannot be encrypted because the file system is not supported.[1]
0x80310014: The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition.[1]
0x80310017: The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically.[1]
0x80310018: You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption.[1]
0x80310019: The operation attempted cannot be performed on an operating system drive.[1]
0x8031001A: The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again.[1]
0x8031001B: A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.[1]
0x8031001C: A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.[1]
0x8031001D: One or more BitLocker key protectors are required. You cannot delete the last key on this drive.[1]
0x8031001E: Cluster configurations are not supported by BitLocker Drive Encryption.[1]
0x8031001F: The drive specified is already configured to be automatically unlocked on the current computer.[1]
0x80310020: The operating system drive is not protected by BitLocker Drive Encryption.[1]
0x80310021: BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key.[1]
0x80310022: The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive.[1]
0x80310023: BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive.[1]
0x80310024: The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again.[1]
0x80310025: The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker.[1]
0x80310026: The drive encryption algorithm cannot be used on this sector size.[1]
0x80310027: The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again.[1]
0x80310028: The drive specified is not the operating system drive.[1]
0x80310029: BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer.[1]
0x8031002A: The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector.[1]
0x8031002B: BitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker.[1]
0x8031002C: Group Policy settings require that a recovery password be specified before encrypting the drive.[1]
0x8031002D: The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker.[1]
0x8031002E: BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive.[1]
0x80310030: BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker.[1]
0x80310031: This key protector cannot be added. Only one key protector of this type is allowed for this drive.[1]
0x80310032: The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path.[1]
0x80310033: The specified key protector was not found on the drive. Try another key protector.[1]
0x80310034: The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive.[1]
0x80310035: The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again.[1]
0x80310036: The random number generator check test failed.[1]
0x80310037: The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent.[1]
0x80310038: The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration.[1]
0x80310039: The drive must be fully decrypted to complete this operation.[1]
0x8031003A: The key protector specified cannot be used for this operation.[1]
0x8031003B: No key protectors exist on the drive to perform the hardware test.[1]
0x8031003C: The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions.[1]
0x8031003D: The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again.[1]
0x8031003E: The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again.[1]
0x8031003F: The Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption.[1]
0x80310040: The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes.[1]
0x80310041: The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem.[1]
0x80310042: The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM).[1]
0x80310043: The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN.[1]
0x80310044: A boot application has changed since BitLocker Drive Encryption was enabled.[1]
0x80310045: The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled.[1]
0x80310046: The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information.[1]
0x80310047: This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again.[1]
0x80310048: BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions.[1]
0x80310049: This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system.[1]
0x8031004A: BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.[1]
0x8031004B: The drive cannot be locked when the drive is in use.[1]
0x8031004C: The access token associated with the current thread is not an impersonated token.[1]
0x8031004D: The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available.[1]
0x8031004E: You must restart your computer before continuing with BitLocker Drive Encryption.[1]
0x8031004F: Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging.[1]
0x80310050: No action was taken as BitLocker Drive Encryption is in raw access mode.[1]
0x80310051: BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use.[1]
0x80310052: The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again.[1]
0x80310053: BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments.[1]
0x80310054: The auto-unlock master key was not available from the operating system drive.[1]
0x80310055: The system firmware failed to enable clearing of system memory when the computer was restarted.[1]
0x80310056: The hidden drive cannot be encrypted.[1]
0x80310057: BitLocker encryption keys were ignored because the drive was in a transient state.[1]
0x80310058: Public key based protectors are not allowed on this drive.[1]
0x80310059: BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing.[1]
0x8031005A: This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.[1]
0x8031005B: The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information.[1]
0x8031005C: Group Policy settings do not permit the creation of a recovery password.[1]
0x8031005D: Group Policy settings require the creation of a recovery password.[1]
0x8031005E: Group Policy settings do not permit the creation of a recovery key.[1]
0x8031005F: Group Policy settings require the creation of a recovery key.[1]
0x80310060: Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option.[1]
0x80310061: Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option.[1]
0x80310062: Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option.[1]
0x80310063: Group Policy settings require the use of a startup key. Please choose this BitLocker startup option.[1]
0x80310064: Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option.[1]
0x80310065: Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option.[1]
0x80310066: Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option.[1]
0x80310067: Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option.[1]
0x80310068: The PIN provided does not meet minimum or maximum length requirements.[1]
0x80310069: The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector.[1]
0x8031006A: Group Policy settings do not permit the creation of a password.[1]
0x8031006B: Group Policy settings require the creation of a password.[1]
0x8031006C: The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information.[1]
0x8031006D: A password cannot be added to the operating system drive.[1]
0x8031006E: The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive.[1]
0x8031006F: The drive is too small to be protected using BitLocker Drive Encryption.[1]
0x80310070: The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives.[1]
0x80310071: The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go.[1]
0x80310072: Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption.[1]
0x80310073: Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption.[1]
0x80310074: Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption.[1]
0x80310075: Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked.[1]
0x80310076: Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked.[1]
0x80310077: Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives.[1]
0x80310078: Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker.[1]
0x80310079: Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker.[1]
0x80310080: Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization.[1]
0x80310081: Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols.[1]
0x80310082: This drive cannot be encrypted because it is reserved for Windows System Recovery Options.[1]
0x80310083: BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.[1]
0x80310084: BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.[1]
0x80310085: The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker.[1]
0x80310086: BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker.[1]
0x80310087: BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[1]
0x80310088: BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.[1]
0x80310089: The requested virtualization size is too big.[1]
0x80310090: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[1]
0x80310091: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[1]
0x80310092: BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.[1]
0x80310093: The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement.[1]
0x80310094: The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid.[1]
0x80310095: Removal of the data recovery agent certificate must be done using the Certificates snap-in.[1]
0x80310096: This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command.[1]
0x80310097: The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive.[1]
0x80310098: The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments.[1]
0x80310099: The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals.[1]
0x8031009A: The requested TPM PIN contains invalid characters.[1]
0x8031009B: The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.[1]
0x8031009C: The feature is only supported on EFI systems.[1]
0x8031009D: More than one Network Key Protector certificate has been found on the system.[1]
0x8031009E: Removal of the Network Key Protector certificate must be done using the Certificates snap-in.[1]
0x8031009F: An invalid certificate has been found in the Network Key Protector certificate store.[1]
0x803100A0: This drive isn't protected with a PIN.[1]
0x803100A1: Please enter the correct current PIN.[1]
0x803100A2: You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator.[1]
0x803100A3: BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator.[1]
0x803100A4: Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ .[1]
0x803100A5: BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.[1]
0x803100A6: BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.[1]
0x803100A7: The required authentication key length is not supported by the drive.[1]
0x803100A8: This drive isn't protected with a password.[1]
0x803100A9: Please enter the correct current password.[1]
0x803100AA: The password cannot exceed 256 characters.[1]
0x803100AB: A password key protector cannot be added because a TPM protector exists on the drive.[1]
0x803100AC: A TPM key protector cannot be added because a password protector exists on the drive.[1]
0x803100AD: This command can only be performed from the coordinator node for the specified CSV volume.[1]
0x803100AE: This command cannot be performed on a volume when it is part of a cluster.[1]
0x803100AF: BitLocker did not revert to using BitLocker software encryption due to group policy configuration.[1]
0x803100B0: The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.[1]
0x803100B1: Group Policy settings do not allow the use of hardware-based encryption.[1]
0x803100B2: The drive specified does not support hardware-based encryption.[1]
0x803100B3: BitLocker cannot be upgraded during disk encryption or decryption.[1]
0x803100B4: Discovery Volumes are not supported for volumes using hardware encryption.[1]
0x803100B5: No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume.[1]
0x803100B6: No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume.[1]
0x803100B7: Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume.[1]
0x803100B8: Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume.[1]
0x803100B9: Wipe of free space is not currently taking place.[1]
0x803100BA: BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled.[1]
0x803100BB: BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker.[1]
0x803100BC: Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.[1]
0x803100BD: BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume.[1]
0x803100BE: BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker.[1]
0x803100BF: This PC's firmware is not capable of supporting hardware encryption.[1]
0x803100C0: BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator.[1]
0x803100C1: You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator.[1]
0x803100C2: BitLocker cannot save the recovery password because the specified Microsoft account is Suspended.[1]
0x803100C3: BitLocker cannot save the recovery password because the specified Microsoft account is Blocked.[1]
0x803100C4: This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy.[1]
0x803100C5: This PC cannot support device encryption because unencrypted fixed data volumes are present.[1]
0x803100C6: This PC does not meet the hardware requirements to support device encryption.[1]
0x803100C7: This PC cannot support device encryption because WinRE is not properly configured.[1]
0x803100C8: Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot.[1]
0x803100C9: This PC is not provisioned to support device encryption.[1]
0x803100CA: Device Lock has been triggered due to too many incorrect password attempts.[1]
0x803100CB: Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information.[1]
0x803100CC: Your PIN can only contain numbers from 0 to 9.[1]
0x803100CD: BitLocker cannot use hardware replay protection because no counter is available on your PC.[1]
0x803100CE: Device Lockout state validation failed due to counter mismatch.[1]
0x803100D0: The target of an invocation does not support requested capability.[1]
0x803100D1: Device encryption is currently blocked by this PC's configuration.[1]
0x803100D2: This drive has been opted out of device encryption.[1]
0x803100D3: Device encryption isn't available for this drive.[1]
0x803100D4: The encrypt on write mode for BitLocker is not supported in this version of Windows. You can turn on BitLocker without using the encrypt on write mode.[1]
0x803100D5: Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator.[1]
0x803100D6: Device encryption can't be turned off while this drive is being encrypted. Please try again later.[1]
0x803100D7: This action isn't supported because this drive isn't automatically managed with device encryption.[1]
0x803100D8: BitLocker can't be suspended on this drive until the next restart.[1]
0x8034002C: The revision number specified in the structure is not supported.[1]
0x8034002D: The specified port does not exist on this network interface.[1]
0x8034002E: The current state of the specified port on this network interface does not support the requested operation.[1]
0x8034002F: The miniport adapter is in low power state.[1]
0x80340030: This operation requires the miniport adapter to be reinitialized.[1]
0x80342000: The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation.[1]
0x80342001: The wireless local area network interface is busy and can not perform the requested operation.[1]
0x80342002: The wireless local area network interface is powered down and doesn't support the requested operation.[1]
0x80342003: The list of wake on LAN patterns is full.[1]
0x80342004: The list of low power protocol offloads is full.[1]
0x80342005: The wireless local area network interface cannot start an AP on the specified channel right now.[1]
0x80342006: The wireless local area network interface cannot start an AP on the specified band right now.[1]
0x80342007: The wireless local area network interface cannot start an AP on this channel due to regulatory reasons.[1]
0x80342008: The wireless local area network interface cannot start an AP on this band due to regulatory reasons.[1]
0x00340001: The request will be completed later by NDIS status indication.[1]
0xC034100F: The TCP connection is not offloadable because of a local policy setting.[1]
0xC0341012: The TCP connection is not offloadable by the Chimney Offload target.[1]
0xC0341013: The IP Path object is not in an offloadable state.[1]
0xC0350002: The hypervisor does not support the operation because the specified hypercall code is not supported.[1]
0xC0350003: The hypervisor does not support the operation because the encoding for the hypercall input register is not supported.[1]
0xC0350004: The hypervisor could not perform the operation because a parameter has an invalid alignment.[1]
0xC0350005: The hypervisor could not perform the operation because an invalid parameter was specified.[1]
0xC0350006: Access to the specified object was denied.[1]
0xC0350007: The hypervisor could not perform the operation because the partition is entering or in an invalid state.[1]
0xC0350008: The operation is not allowed in the current state.[1]
0xC0350009: The hypervisor does not recognize the specified partition property.[1]
0xC035000A: The specified value of a partition property is out of range or violates an invariant.[1]
0xC035000B: There is not enough memory in the hypervisor pool to complete the operation.[1]
0xC035000C: The maximum partition depth has been exceeded for the partition hierarchy.[1]
0xC035000D: A partition with the specified partition Id does not exist.[1]
0xC035000E: The hypervisor could not perform the operation because the specified VP index is invalid.[1]
0xC0350011: The hypervisor could not perform the operation because the specified port identifier is invalid.[1]
0xC0350012: The hypervisor could not perform the operation because the specified connection identifier is invalid.[1]
0xC0350013: Not enough buffers were supplied to send a message.[1]
0xC0350014: The previous virtual interrupt has not been acknowledged.[1]
0xC0350015: A virtual processor is not in the correct state for the indicated operation.[1]
0xC0350016: The previous virtual interrupt has already been acknowledged.[1]
0xC0350017: The indicated partition is not in a valid state for saving or restoring.[1]
0xC0350018: The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled.[1]
0xC0350019: The hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation.[1]
0xC035001A: The proximity domain information is invalid.[1]
0xC035001B: An attempt to retrieve debugging data failed because none was available.[1]
0xC035001C: The physical connection being used for debuggging has not recorded any receive activity since the last operation.[1]
0xC035001D: There are not enough resources to complete the operation.[1]
0xC035001E: A hypervisor feature is not available to the user.[1]
0xC0350033: The specified buffer was too small to contain all of the requested data.[1]
0xC0350038: The maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition.[1]
0xC035003C: Validation of CPUID data of the processor failed.[1]
0xC035003D: Validation of XSAVE CPUID data of the processor failed.[1]
0xC035003E: Processor did not respond within the timeout period.[1]
0xC0350058: The operation is not allowed in the current device state.[1]
0x00350059: The device had pending page requests which were discarded.[1]
0xC0350060: The supplied page request specifies a memory access that the guest does not have permissions to perform.[1]
0xC035006F: A CPU group with the specified CPU group Id does not exist.[1]
0xC0350070: The hypervisor could not perform the operation because the CPU group is entering or in an invalid state.[1]
0xC0350071: The hypervisor could not perform the operation because it is not allowed with nested virtualization active.[1]
0xC0351000: No hypervisor is present on this system.[1]
0xC0370001: The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370002: The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370003: The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370004: No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370005: The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370006: The partition name of the virtualization infrastructure driver exceeds the maximum.[1]
0xC0370007: The message queue name of the virtualization infrastructure driver exceeds the maximum.[1]
0xC0370008: Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.[1]
0xC0370009: The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037000A: The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037000B: A message queue with the same name already exists for the virtualization infrastructure driver.[1]
0xC037000C: The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037000D: The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.[1]
0xC037000E: Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037000F: The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration.[1]
0xC0370010: The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.[1]
0xC0370011: The memory block for the virtualization infrastructure driver is already associated with a message queue.[1]
0xC0370012: The handle is not a valid memory block handle for the virtualization infrastructure driver.[1]
0xC0370013: The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370014: The handle is not a valid message queue handle for the virtualization infrastructure driver.[1]
0xC0370015: The handle is not a valid page range handle for the virtualization infrastructure driver.[1]
0xC0370016: Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.[1]
0xC0370017: The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370018: The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.[1]
0xC0370019: Notifications cannot be created on the memory block because it is use.[1]
0xC037001A: The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037001B: Cannot add a virtual processor to the partition because the maximum has been reached.[1]
0xC037001C: Cannot stop the virtual processor immediately because of a pending intercept.[1]
0xC037001D: Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037001E: The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC037001F: This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370020: Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370021: The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370022: The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370023: Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370024: The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370025: Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370026: Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[1]
0xC0370027: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine.[1]
0xC0370028: Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine.[1]
0xC0370029: Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.[1]
0xC037002A: The specified VTL does not have the permission to access the resource.[1]
0xC0370100: The compute system unexpectedly terminated while starting.[1]
0xC0370101: The operating system of the container does not match the operating system of the host.[1]
0xC0370102: A Virtual Machine could not be started because Hyper-V is not installed.[1]
0xC0370103: The call to start an asynchronous operation succeeded and the operation is performed in the background.[1]
0xC0370104: The supported number of notification callbacks has been exceeded.[1]
0xC0370105: The requested compute system operation is not valid in the current state.[1]
0xC0370106: The compute system exited unexpectedly.[1]
0xC0370107: The compute system was forcefully terminated.[1]
0xC0370108: A connection could not be established with the Virtual Machine hosting the Container.[1]
0xC0370109: The operation timed out because a response was not received from the Virtual Machine hosting the Container.[1]
0xC037010A: The connection with the Virtual Machine hosting the container was closed.[1]
0xC037010B: An unknown internal message was received by the Hyper-V Compute Service.[1]
0xC037010C: The communication protocol version between the Hyper-V Host and Guest Compute Services is not supported.[1]
0xC037010E: A Compute System with the specified identifier does not exist.[1]
0xC037010F: A Compute System with the specified identifier already exists.[1]
0xC0370110: The Compute System with the specified identifier did already stop.[1]
0xC0370200: A virtual switch with the given name was not found.[1]
0x80370001: A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration.[1]
0x80380001: The regeneration operation was not able to copy all data from the active plexes due to bad sectors.[1]
0x80380002: One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems.[1]
0xC0380013: There is not enough usable space for this operation.[1]
0xC0380014: The force revectoring of bad sectors failed.[1]
0xC0380015: The specified disk has an invalid sector size.[1]
0xC0380016: The specified disk set contains volumes which exist on disks outside of the set.[1]
0xC0380017: A disk in the volume layout provides extents to more than one member of a plex.[1]
0xC0380018: A disk in the volume layout provides extents to more than one plex.[1]
0xC0380019: Dynamic disks are not supported on this system.[1]
0xC038001A: The specified extent is already used by other volumes.[1]
0xC038001B: The specified volume is retained and can only be extended into a contiguous extent. The specified extent to grow the volume is not contiguous with the specified volume.[1]
0xC038001C: The specified volume extent is not within the public region of the disk.[1]
0xC038001D: The specifed volume extent is not sector aligned.[1]
0xC038001E: The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks).[1]
0xC038001F: The specified extent lengths cannot be used to construct a volume with specified length.[1]
0xC0380020: The system does not support fault tolerant volumes.[1]
0xC0380021: The specified interleave length is invalid.[1]
0xC0380022: There is already a maximum number of registered users.[1]
0xC0380023: The specified member is already in-sync with the other active members. It does not need to be regenerated.[1]
0xC0380024: The same member index was specified more than once.[1]
0xC0380025: The specified member index is greater or equal than the number of members in the volume plex.[1]
0xC0380026: The specified member is missing. It cannot be regenerated.[1]
0xC0380027: The specified member is not detached. Cannot replace a member which is not detached.[1]
0xC0380028: The specified member is already regenerating.[1]
0xC0380029: All disks belonging to the pack failed.[1]
0xC038002A: There are currently no registered users for notifications. The task number is irrelevant unless there are registered users.[1]
0xC038002B: The specified notification user does not exist. Failed to unregister user for notifications.[1]
0xC038002C: The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications.[1]
0xC038002D: The specified number of members is invalid.[1]
0xC038002E: The specified number of plexes is invalid.[1]
0xC038002F: The specified source and target packs are identical.[1]
0xC0380030: The specified pack id is invalid. There are no packs with the specified pack id.[1]
0xC0380031: The specified pack is the invalid pack. The operation cannot complete with the invalid pack.[1]
0xC038005A: The specified number of disks is invalid.[1]
0xC038005B: The system does not support mirrored volumes.[1]
0xC038005C: The system does not support RAID-5 volumes.[1]
0x80390001: Some BCD entries were not imported correctly from the BCD store.[1]
0xC0390002: Entries enumerated have exceeded the allowed threshold.[1]
0x80390003: Some BCD entries were not synchronized correctly with the firmware.[1]
0xC03A0001: The virtual hard disk is corrupted. The virtual hard disk drive footer is missing.[1]
0xC03A0002: The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum.[1]
0xC03A0003: The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted.[1]
0xC03A0004: The system does not recognize the file format of this virtual hard disk.[1]
0xC03A0005: The version does not support this version of the file format.[1]
0xC03A0006: The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum.[1]
0xC03A0007: The system does not support this version of the virtual hard disk.This version of the sparse header is not supported.[1]
0xC03A0008: The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt.[1]
0xC03A0009: Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk.[1]
0xC03A000A: The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt.[1]
0xC03A000B: The system does not support this version of the virtual hard disk. The block size is invalid.[1]
0xC03A000C: The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk.[1]
0xC03A000D: The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk.[1]
0xC03A000E: The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk.[1]
0xC03A000F: The chain of virtual hard disks is corrupted. The time stamp of the parent virtual hard disk does not match the time stamp of the differencing disk.[1]
0xC03A0010: Failed to read the metadata of the virtual hard disk.[1]
0xC03A0011: Failed to write to the metadata of the virtual hard disk.[1]
0xC03A0012: The size of the virtual hard disk is not valid.[1]
0xC03A0013: The file size of this virtual hard disk is not valid.[1]
0xC03A0014: A virtual disk support provider for the specified file was not found.[1]
0xC03A0015: The specified disk is not a virtual disk.[1]
0xC03A0016: 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.[1]
0xC03A0017: 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.[1]
0xC03A0018: The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain.[1]
0xC03A0019: The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain.[1]
0xC03A001A: The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.[1]
0xC03A001B: The requested operation cannot be performed on a virtual disk of this type.[1]
0xC03A001C: The requested operation cannot be performed on the virtual disk in its current state.[1]
0xC03A001D: The sector size of the physical disk on which the virtual disk resides is not supported.[1]
0xC03A001E: The disk is already owned by a different owner.[1]
0xC03A001F: The disk must be offline or read-only.[1]
0xC03A0020: Change Tracking is not initialized for this virtual disk.[1]
0xC03A0021: Size of change tracking file exceeded the maximum size limit.[1]
0xC03A0022: VHD file is changed due to compaction, expansion, or offline updates.[1]
0xC03A0023: Change Tracking for the virtual disk is not in a valid state to perform this request. Change tracking could be discontinued or already in the requested state.[1]
0xC03A0024: Change Tracking file for the virtual disk is not in a valid state.[1]
0xC03A0025: The requested resize operation could not be completed because it might truncate user data residing on the virtual disk.[1]
0xC03A0026: The requested operation could not be completed because the virtual disk's minimum safe size could not be determined.
This may be due to a missing or corrupt partition table.[1]
0xC03A0027: The requested operation could not be completed because the virtual disk's size cannot be safely reduced further.[1]
0xC03A0028: There is not enough space in the virtual disk file for the provided metadata item.[1]
0xC03A0029: The specified change tracking identifier is not valid.[1]
0xC03A002A: Change tracking is disabled for the specified virtual hard disk, so no change tracking information is available.[1]
0xC03A0030: There is no change tracking data available associated with the specified change tracking identifier.[1]
0x803A0001: The virtualization storage subsystem has generated an error.[1]
0xC0EA0009: CLiP license hardware ID is out of tolerance.[1]
0xC0EA000A: CLiP license device ID does not match the device ID in the bound device license.[1]
0x087A0001: The Present operation was invisible to the user.[1]
0x087A0002: The Present operation was partially invisible to the user.[1]
0x087A0004: The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager.[1]
0x087A0005: The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del).[1]
0x087A0006: The Present operation was not visible because the target monitor was being used for some other purpose.[1]
0x087A0007: The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation.[1]
0x087A0008: The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time.[1]
0x887A0001: The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect.
Enable the D3D debug layer in order to see details via debug messages.[1]
0x887A0002: The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal.[1]
0x887A0003: The caller did not supply a sufficiently large buffer.[1]
0x887A0004: The specified device interface or feature level is not supported on this system.[1]
0x887A0005: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.[1]
0x887A0006: The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application.[1]
0x887A0007: The GPU will not respond to more commands, most likely because some other application submitted invalid commands.
The calling application should re-create the device and continue.[1]
0x887A000A: The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled.[1]
0x887A000B: An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should be
considered invalid.[1]
0x887A000C: Fullscreen mode could not be achieved because the specified output was already in use.[1]
0x887A0020: An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect,
and the application should not continue.[1]
0x887A0021: A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time.[1]
0x887A0022: A resource is not available at the time of the call, but may become available later.[1]
0x887A0023: The application's remote device has been removed due to session disconnect or network disconnect.
The application should call IDXGIFactory1::IsCurrent to find out when the remote device becomes available again.[1]
0x887A0024: The device has been removed during a remote session because the remote computer ran out of memory.[1]
0x887A0027: The timeout value has elapsed and the resource is not yet available.[1]
0x887A0028: The output duplication has been turned off because the Windows session ended or was disconnected.
This happens when a remote user disconnects, or when "switch user" is used locally.[1]
0x887A0029: The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed.[1]
0x887A002A: DXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver,
or by the application using a swapchain that is incompatible with content protection.[1]
0x887A002B: The application is trying to use a resource to which it does not have the required access privileges.
This is most commonly caused by writing to a shared resource with read-only access.[1]
0x887A002C: The application is trying to create a shared handle using a name that is already associated with some other resource.[1]
0x887A002D: The application requested an operation that depends on an SDK component that is missing or mismatched.[1]
0x887A002E: The DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed.[1]
0x887A0030: Insufficient HW protected memory exits for proper function.[1]
0x087A000A: The adapter did not have access to the required resources to complete the Desktop Duplication Present() call, the Present() call needs to be made again[1]
0x887A0025: An on-going mode change prevented completion of the call. The call may succeed if attempted later.[1]
0x087A002F: The present succeeded but the caller should present again on the next V-sync, even if there are no changes to the content.[1]
0x887B0001: The GPU was busy when the operation was requested.[1]
0x887B0002: The driver has rejected the creation of this resource.[1]
0x887B0003: The GPU counter was in use by another process or d3d device when application requested access to it.[1]
0x88790001: The application has exceeded the maximum number of unique state objects per Direct3D device.
The limit is 4096 for feature levels up to 11.1.[1]
0x887C0001: The application has exceeded the maximum number of unique state objects per Direct3D device.
The limit is 4096 for feature levels up to 11.1.[1]
0x887C0003: The application has exceeded the maximum number of unique view objects per Direct3D device.
The limit is 2^20 for feature levels up to 11.1.[1]
0x887C0004: The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD.[1]
0x887E0001: The blob provided does not match the adapter that the device was created on.[1]
0x887E0002: The blob provided was created for a different version of the driver, and must be re-created.[1]
0x88990001: The object was not in the correct state to process the method.[1]
0x88990002: The object has not yet been initialized.[1]
0x88990003: The requested operation is not supported.[1]
0x88990004: The geometry scanner failed to process the data.[1]
0x88990005: Direct2D could not access the screen.[1]
0x88990006: A valid display state could not be determined.[1]
0x88990008: An internal error (Direct2D bug) occurred. On checked builds, we would assert. The application should close this instance of Direct2D and should consider restarting its process.[1]
0x88990009: The display format Direct2D needs to render is not supported by the hardware device.[1]
0x8899000B: No hardware rendering device is available for this operation.[1]
0x8899000C: There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present.[1]
0x8899000D: Shader construction failed because it was too complex.[1]
0x8899001A: The render target is not compatible with GDI.[1]
0x8899001B: A text client drawing effect object is of the wrong type.[1]
0x8899001C: The application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid.[1]
0x8899001D: The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level.[1]
0x8899001E: There was a configuration error in the graph.[1]
0x8899001F: There was a internal configuration error in the graph.[1]
0x88990021: Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option.[1]
0x88990022: The operation cannot complete while there are outstanding references to the target bitmap.[1]
0x88990023: The operation failed because the original target is not currently bound as a target.[1]
0x88990024: Cannot set the image as a target because it is either an effect or is a bitmap that does not have the D2D1_BITMAP_OPTIONS_TARGET flag set.[1]
0x88990025: Cannot draw with a bitmap that is currently bound as the target bitmap.[1]
0x88990026: D3D Device does not have sufficient capabilities to perform the requested action.[1]
0x88990027: The graph could not be rendered with the context's current tiling settings.[1]
0x88990028: The CLSID provided to Unregister did not correspond to a registered effect.[1]
0x88990029: The specified property does not exist.[1]
0x8899002A: The specified sub-property does not exist.[1]
0x8899002B: AddPage or Close called after print job is already closed.[1]
0x8899002C: Error during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control.[1]
0x8899002D: An effect attempted to use a transform with too many inputs.[1]
0x8899002E: An error was encountered while decoding or parsing the requested glyph image.[1]
0x88985000: Indicates an error in an input file such as a font file.[1]
0x88985001: Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from.[1]
0x88985002: Indicates the specified font does not exist.[1]
0x88985003: A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable.[1]
0x88985004: A font file exists but could not be opened due to access denied, sharing violation, or similar error.[1]
0x88985005: A font collection is obsolete due to changes in the system.[1]
0x88985006: The given interface is already registered.[1]
0x88985007: The font cache contains invalid data.[1]
0x88985008: A font cache file corresponds to a different version of DirectWrite.[1]
0x88985009: The operation is not supported for this type of font.[1]
0x8898500A: The version of the text renderer interface is not compatible.[1]
0x8898500B: The flow direction conflicts with the reading direction. They must be perpendicular to each other.[1]
0x8898500C: The font or glyph run does not contain any colored glyphs.[1]
0x88980086: Lock attempted on an already locked object.[1]
0x88980087: Unlock attempted on an unlocked object.[1]
0x88980088: No algorithm avaliable to render text with this device[1]
0x88980089: Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache.[1]
0x8898008A: Some glyph bitmaps in glyph cache are unexpectedly big.[1]
0x8898008B: Marker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred, but still unwind the stack in the correct location.[1]
0x8898008C: Guideline coordinates are not sorted properly or contain NaNs.[1]
0x8898008D: No HW rendering device is available for this operation.[1]
0x8898008E: There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present.
There are two known case for this: 1) D3D Driver Internal error 2) D3D E_FAIL 2a) Unknown root cause b) When resizing too quickly for DWM and D3D stay in sync[1]
0x8898008F: The object has already been initialized.[1]
0x88980090: The size of the object does not match the expected size.[1]
0x8027025C: This app failed to launch because of an issue with its license. Please try again in a moment.[1]
0x8027025D: This app failed to launch because its trial license has expired.[1]
0x80270260: Please choose a folder on a drive that's formatted with the NTFS file system.[1]
0x80270261: This location is already being used. Please choose a different location.[1]
0x80270262: This location cannot be indexed. Please choose a different location.[1]
0x80270263: Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later.[1]
0x80270264: Sorry, the action couldn't be completed.[1]
0x80270265: This content can only be moved to a folder. To move the content to this drive, please choose or create a folder.[1]
0x8802B001: The file size is larger than supported by the sync engine.[1]
0x8802B002: The file cannot be uploaded because it doesn't fit in the user's available service provided storage space.[1]
0x8802B003: The file name contains invalid characters.[1]
0x8802B004: The maximum file count has been reached for this folder in the sync engine.[1]
0x8802B005: The file sync has been delegated to another program and has run into an issue.[1]
0x8802B006: Sync has been delayed due to a throttling request from the service.[1]
0x8802C002: We can't seem to find that file. Please try again later.[1]
0x8802C003: The account you're signed in with doesn't have permission to open this file.[1]
0x8802C004: There was a problem connecting to the service. Please try again later.[1]
0x8802C005: Sorry, there was a problem downloading the file.[1]
0x8802C006: We're having trouble downloading the file right now. Please try again later.[1]
0x8802C007: We're having trouble downloading the file right now. Please try again later.[1]
0x8802D001: The sync engine does not have permissions to access a local folder under the sync root.[1]
0x8802D002: The folder name contains invalid characters.[1]
0x8802D003: The sync engine is not allowed to run in your current market.[1]
0x8802D004: All files and folders can't be uploaded because a path of a file or folder is too long.[1]
0x8802D005: All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit.[1]
0x8802D006: Updates are needed in order to use the sync engine.[1]
0x8802D007: The sync engine needs to authenticate with a proxy server.[1]
0x8802D008: There was a problem setting up the storage services for the account.[1]
0x8802D009: Files can't be uploaded because there's an unsupported reparse point.[1]
0x8802D00A: The service has blocked your account from accessing the storage service.[1]
0x8802D00B: The action can't be performed right now because this folder is being moved. Please try again later.[1]
0x80550001: Windows cannot evaluate this EAS policy since this is not managed by the operating system.[1]
0x80550002: The system can be made compliant to this EAS policy if certain actions are performed by the user.[1]
0x80550003: The EAS policy being evaluated cannot be enforced by the system.[1]
0x80550004: EAS password policies for the user cannot be evaluated as the user has a blank password.[1]
0x80550005: EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system.[1]
0x80550006: The user is not allowed to change her password.[1]
0x80550007: EAS password policies cannot be evaluated as one or more admins have blank passwords.[1]
0x80550008: One or more admins are not allowed to change their password.[1]
0x80550009: There are other standard users present who are not allowed to change their password.[1]
0x8055000A: The EAS password policy cannot be enforced by the connected account provider of at least one administrator.[1]
0x8055000B: There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance.[1]
0x8055000C: The EAS password policy cannot be enforced by the connected account provider of the current user.[1]
0x8055000D: The connected account password of the current user needs to be changed for EAS password policy compliance.[1]
0x80400000: Input data cannot be processed in the non-chronological order.[1]
0x80400001: Requested operation cannot be performed inside the callback or event handler.[1]
0x80400002: Input cannot be processed because there is ongoing interaction with another pointer type.[1]
0x80400003: One or more fields in the input packet are invalid.[1]
0x80400004: Packets in the frame are inconsistent. Either pointer ids are not unique or there is a discrepancy in timestamps, frame ids, pointer types or source devices.[1]
0x80400005: The history of frames is inconsistent. Pointer ids, types, source devices don't match, or frame ids are not unique, or timestamps are out of order.[1]
0x80400006: Failed to retrieve information about the input device.[1]
0x80400007: Coordinate system transformation failed to transform the data.[1]
0x80400008: The property is not supported or not reported correctly by the input device.[1]
0x800C0015: The requested resource is a directory, not a file.[1]
0x80B00001: Could not create new process from ARM architecture device.[1]
0x80B00002: Could not attach to the application process from ARM architecture device.[1]
0x80B00003: Could not connect to dbgsrv server from ARM architecture device.[1]
0x80B00004: Could not start dbgsrv server from ARM architecture device.[1]
0x89010001: The operation was preempted by a higher priority operation. It must be resumed later.[1]
0x89020001: Function could not execute because it was deleted or garbage collected.[1]
0x88010001: One or more fixed volumes are not provisioned with the 3rd party encryption providers to support device encryption. Enable encryption with the 3rd party provider to comply with policy.[1]
0x88010002: This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption.[1]
0x88010003: This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider.[1]
0x88010004: This computer cannot support device encryption because the requisites for the device lock feature are not configured.[1]
0x88010005: Protection is enabled on this volume but is not in the active state.[1]
0x88010006: The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated.[1]
0x88010007: The operating system drive is not protected by 3rd party drive encryption.[1]
0x88010008: Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin.[1]
0x88010009: The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large.[1]
0xC05C0000: The proper error code with sense data was stored on server side.[1]
0xC05CFF00: The requested error data is not available on the server.[1]
0xC05CFF01: Unit Attention data is available for the initiator to query.[1]
0xC05CFF02: The data capacity of the device has changed, resulting in a Unit Attention condition.[1]
0xC05CFF03: A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition.[1]
0xC05CFF04: A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition.[1]
0xC05CFF05: A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition.[1]
0xC05CFF06: The data storage format of the device has changed, resulting in a Unit Attention condition.[1]
0xC05CFF07: The current initiator is not allowed to perform the SCSI command because of a reservation conflict.[1]
0xC05CFF08: Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks.[1]
0xC05CFF09: The server version does not match the requested version.[1]
0xC05CFF0A: The requested operation cannot be performed on the virtual disk as it is currently used in shared mode.[1]
0xC05CFF0B: Invalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures.[1]
0xC05CFF0C: The requested operation failed due to a missing backing storage file.[1]
0xC05D0000: Failed to negotiate a preauthentication integrity hash function.[1]
0xC05D0001: The current cluster functional level does not support this SMB dialect.[1]
0x80072EE1: No more Internet handles can be allocated[1]
0x80070033: Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.[1]
0x00000033: Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.[1]
0x80070034: You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.[1]
0x00000034: You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.[1]
0x80070044: The name limit for the local computer network adapter card was exceeded.[1]
0x00000044: The name limit for the local computer network adapter card was exceeded.[1]
0x80070045: The network BIOS session limit was exceeded.[1]
0x00000045: The network BIOS session limit was exceeded.[1]
0x80070046: The remote server has been paused or is in the process of being started.[1]
0x00000046: The remote server has been paused or is in the process of being started.[1]
0x80070047: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.[1]
0x00000047: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.[1]
0x80070048: The specified printer or disk device has been paused.[1]
0x00000048: The specified printer or disk device has been paused.[1]
0x800700D8: This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.[1]
0x000000D8: This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.[1]
0x800700D9: The image file %1 is signed, unable to modify.[1]
0x000000D9: The image file %1 is signed, unable to modify.[1]
0x800700DA: The image file %1 is strong signed, unable to modify.[1]
0x000000DA: The image file %1 is strong signed, unable to modify.[1]
0x800700DC: This file is checked out or locked for editing by another user.[1]
0x000000DC: This file is checked out or locked for editing by another user.[1]
0x800700DD: The file must be checked out before saving changes.[1]
0x000000DD: The file must be checked out before saving changes.[1]
0x800700DE: The file type being saved or retrieved has been blocked.[1]
0x000000DE: The file type being saved or retrieved has been blocked.[1]
0x800700DF: The file size exceeds the limit allowed and cannot be saved.[1]
0x000000DF: The file size exceeds the limit allowed and cannot be saved.[1]
0x800700E0: Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.[1]
0x000000E0: Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.[1]
0x800700E1: Operation did not complete successfully because the file contains a virus or potentially unwanted software.[1]
0x000000E1: Operation did not complete successfully because the file contains a virus or potentially unwanted software.[1]
0x800700E2: This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location.[1]
0x000000E2: This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location.[1]
0x80070161: The maximum number of sessions has been reached.[1]
0x00000161: The maximum number of sessions has been reached.[1]
0x80070162: Enterprise Data Protection policy does not allow access to this network resource.[1]
0x00000162: Enterprise Data Protection policy does not allow access to this network resource.[1]
0x80070163: The device hint name buffer is too small to receive the remaining name.[1]
0x00000163: The device hint name buffer is too small to receive the remaining name.[1]
0x80070164: The requested operation was blocked by Enterprise Data Protection policy. For more information, contact your system administrator.[1]
0x00000164: The requested operation was blocked by Enterprise Data Protection policy. For more information, contact your system administrator.[1]
0x80070165: The requested operation cannot be performed because hardware or software configuration of the device does not comply with Enterprise Data Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator.[1]
0x00000165: The requested operation cannot be performed because hardware or software configuration of the device does not comply with Enterprise Data Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator.[1]
0x80070217: There is a process on other end of the pipe.[1]
0x00000217: There is a process on other end of the pipe.[1]
0x80070218: Waiting for a process to open the other end of the pipe.[1]
0x00000218: Waiting for a process to open the other end of the pipe.[1]
0x80070219: Application verifier has found an error in the current process.[1]
0x00000219: Application verifier has found an error in the current process.[1]
0x8007021A: An error occurred in the ABIOS subsystem.[1]
0x0000021A: An error occurred in the ABIOS subsystem.[1]
0x8007021B: A warning occurred in the WX86 subsystem.[1]
0x0000021B: A warning occurred in the WX86 subsystem.[1]
0x8007021C: An error occurred in the WX86 subsystem.[1]
0x0000021C: An error occurred in the WX86 subsystem.[1]
0x8007021D: An attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine.[1]
0x0000021D: An attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine.[1]
0x8007021F: An invalid or unaligned stack was encountered during an unwind operation.[1]
0x0000021F: An invalid or unaligned stack was encountered during an unwind operation.[1]
0x80070220: An invalid unwind target was encountered during an unwind operation.[1]
0x00000220: An invalid unwind target was encountered during an unwind operation.[1]
0x80070221: Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort[1]
0x00000221: Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort[1]
0x80070222: Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port.[1]
0x00000222: Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port.[1]
0x80070223: An attempt was made to lower a quota limit below the current usage.[1]
0x00000223: An attempt was made to lower a quota limit below the current usage.[1]
0x80070224: An attempt was made to attach to a device that was already attached to another device.[1]
0x00000224: An attempt was made to attach to a device that was already attached to another device.[1]
0x80070225: An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references.[1]
0x00000225: An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references.[1]
0x80070228: The passed ACL did not contain the minimum required information.[1]
0x00000228: The passed ACL did not contain the minimum required information.[1]
0x80070229: The number of active profiling objects is at the maximum and no more may be started.[1]
0x00000229: The number of active profiling objects is at the maximum and no more may be started.[1]
0x8007022A: Used to indicate that an operation cannot continue without blocking for I/O.[1]
0x0000022A: Used to indicate that an operation cannot continue without blocking for I/O.[1]
0x8007022B: Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process.[1]
0x0000022B: Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process.[1]
0x8007022C: In this case information is lost, however, the filter correctly handles the exception.[1]
0x0000022C: In this case information is lost, however, the filter correctly handles the exception.[1]
0x8007022D: In this case information is lost, however, the filter correctly handles the exception.[1]
0x0000022D: In this case information is lost, however, the filter correctly handles the exception.[1]
0x8007022E: In this case information is lost, however, the filter correctly handles the exception.[1]
0x0000022E: In this case information is lost, however, the filter correctly handles the exception.[1]
0x8007022F: A malformed function table was encountered during an unwind operation.[1]
0x0000022F: A malformed function table was encountered during an unwind operation.[1]
0x80070230: This causes the protection attempt to fail, which may cause a file creation attempt to fail.[1]
0x00000230: This causes the protection attempt to fail, which may cause a file creation attempt to fail.[1]
0x80070231: Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors.[1]
0x00000231: Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors.[1]
0x80070233: Indicates that the starting value for the LDT information was not an integral multiple of the selector size.[1]
0x00000233: Indicates that the starting value for the LDT information was not an integral multiple of the selector size.[1]
0x80070234: Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.[1]
0x00000234: Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.[1]
0x80070235: Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads.[1]
0x00000235: Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads.[1]
0x80070236: An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified.[1]
0x00000236: An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified.[1]
0x80070238: The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.[1]
0x00000238: The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.[1]
0x80070239: The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.[1]
0x00000239: The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.[1]
0x8007023A: The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.[1]
0x0000023A: The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.[1]
0x8007023B: The I/O permissions for the process could not be changed.[1]
0x0000023B: The I/O permissions for the process could not be changed.[1]
0x8007023C: The application terminated as a result of a CTRL+C.[1]
0x0000023C: The application terminated as a result of a CTRL+C.[1]
0x8007023D: The required system file %hs is bad or missing.[1]
0x0000023D: The required system file %hs is bad or missing.[1]
0x8007023E: The exception %s (0x%08lx) occurred in the application at location 0x%08lx.[1]
0x0000023E: The exception %s (0x%08lx) occurred in the application at location 0x%08lx.[1]
0x8007023F: The application was unable to start correctly (0x%lx). Click OK to close the application.[1]
0x0000023F: The application was unable to start correctly (0x%lx). Click OK to close the application.[1]
0x80070240: The creation of the paging file %hs failed (%lx). The requested size was %ld.[1]
0x00000240: The creation of the paging file %hs failed (%lx). The requested size was %ld.[1]
0x80070241: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.[1]
0x00000241: Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.[1]
0x80070242: No paging file was specified in the system configuration.[1]
0x00000242: No paging file was specified in the system configuration.[1]
0x80070243: A real-mode application issued a floating-point instruction and floating-point hardware is not present.[1]
0x00000243: A real-mode application issued a floating-point instruction and floating-point hardware is not present.[1]
0x80070244: An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.[1]
0x00000244: An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.[1]
0x80070245: A Windows Server has an incorrect configuration.[1]
0x00000245: A Windows Server has an incorrect configuration.[1]
0x80070246: An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.[1]
0x00000246: An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.[1]
0x80070247: The Unicode character is not defined in the Unicode character set installed on the system.[1]
0x00000247: The Unicode character is not defined in the Unicode character set installed on the system.[1]
0x80070248: The paging file cannot be created on a floppy diskette.[1]
0x00000248: The paging file cannot be created on a floppy diskette.[1]
0x80070249: The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected.[1]
0x00000249: The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected.[1]
0x8007024A: This operation is only allowed for the Primary Domain Controller of the domain.[1]
0x0000024A: This operation is only allowed for the Primary Domain Controller of the domain.[1]
0x8007024B: An attempt was made to acquire a mutant such that its maximum count would have been exceeded.[1]
0x0000024B: An attempt was made to acquire a mutant such that its maximum count would have been exceeded.[1]
0x8007024C: A volume has been accessed for which a file system driver is required that has not yet been loaded.[1]
0x0000024C: A volume has been accessed for which a file system driver is required that has not yet been loaded.[1]
0x8007024D: It is corrupt, absent, or not writable.[1]
0x0000024D: It is corrupt, absent, or not writable.[1]
0x8007024E: An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error.[1]
0x0000024E: An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error.[1]
0x80070252: The driver %hs failed to complete a cancelled I/O request in the allotted time.[1]
0x00000252: The driver %hs failed to complete a cancelled I/O request in the allotted time.[1]
0x80070253: An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message.[1]
0x00000253: An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message.[1]
0x80070254: This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[1]
0x00000254: This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.[1]
0x80070255: The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window.[1]
0x00000255: The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window.[1]
0x80070257: The request must be handled by the stack overflow code.[1]
0x00000257: The request must be handled by the stack overflow code.[1]
0x80070258: Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream.[1]
0x00000258: Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream.[1]
0x80070259: The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation.[1]
0x00000259: The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation.[1]
0x8007025A: The bucket array must be grown. Retry transaction after doing so.[1]
0x0000025A: The bucket array must be grown. Retry transaction after doing so.[1]
0x8007025B: The user/kernel marshalling buffer has overflowed.[1]
0x0000025B: The user/kernel marshalling buffer has overflowed.[1]
0x8007025C: The supplied variant structure contains invalid data.[1]
0x0000025C: The supplied variant structure contains invalid data.[1]
0x8007025D: The specified buffer contains ill-formed data.[1]
0x0000025D: The specified buffer contains ill-formed data.[1]
0x8007025E: An attempt to generate a security audit failed.[1]
0x0000025E: An attempt to generate a security audit failed.[1]
0x8007025F: The timer resolution was not previously set by the current process.[1]
0x0000025F: The timer resolution was not previously set by the current process.[1]
0x80070260: There is insufficient account information to log you on.[1]
0x00000260: There is insufficient account information to log you on.[1]
0x80070261: The entrypoint should be declared as WINAPI or STDCALL. Select YES to fail the DLL load. Select NO to continue execution. Selecting NO may cause the application to operate incorrectly.[1]
0x00000261: The entrypoint should be declared as WINAPI or STDCALL. Select YES to fail the DLL load. Select NO to continue execution. Selecting NO may cause the application to operate incorrectly.[1]
0x80070262: The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly.[1]
0x00000262: The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly.[1]
0x80070263: There is an IP address conflict with another system on the network[1]
0x00000263: There is an IP address conflict with another system on the network[1]
0x80070264: There is an IP address conflict with another system on the network[1]
0x00000264: There is an IP address conflict with another system on the network[1]
0x80070265: The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.[1]
0x00000265: The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.[1]
0x80070266: A callback return system service cannot be executed when no callback is active.[1]
0x00000266: A callback return system service cannot be executed when no callback is active.[1]
0x80070268: If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned.[1]
0x00000268: If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned.[1]
0x80070269: The policy of your user account does not allow this. Please select a password that you have not previously used.[1]
0x00000269: The policy of your user account does not allow this. Please select a password that you have not previously used.[1]
0x8007026A: The specified compression format is unsupported.[1]
0x0000026A: The specified compression format is unsupported.[1]
0x8007026B: The specified hardware profile configuration is invalid.[1]
0x0000026B: The specified hardware profile configuration is invalid.[1]
0x8007026C: The specified Plug and Play registry device path is invalid.[1]
0x0000026C: The specified Plug and Play registry device path is invalid.[1]
0x8007026D: The specified quota list is internally inconsistent with its descriptor.[1]
0x0000026D: The specified quota list is internally inconsistent with its descriptor.[1]
0x8007026E: The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product.[1]
0x0000026E: The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product.[1]
0x8007026F: The relocation occurred because the DLL %hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.[1]
0x0000026F: The relocation occurred because the DLL %hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL.[1]
0x80070270: The application failed to initialize because the window station is shutting down.[1]
0x00000270: The application failed to initialize because the window station is shutting down.[1]
0x80070271: The validation process needs to continue on to the next step.[1]
0x00000271: The validation process needs to continue on to the next step.[1]
0x80070272: There are no more matches for the current index enumeration.[1]
0x00000272: There are no more matches for the current index enumeration.[1]
0x80070273: The range could not be added to the range list because of a conflict.[1]
0x00000273: The range could not be added to the range list because of a conflict.[1]
0x80070274: The server process is running under a SID different than that required by client.[1]
0x00000274: The server process is running under a SID different than that required by client.[1]
0x80070275: A group marked use for deny only cannot be enabled.[1]
0x00000275: A group marked use for deny only cannot be enabled.[1]
0x80070281: The system is in the process of shutting down.[1]
0x00000281: The system is in the process of shutting down.[1]
0x80070282: An attempt to remove a processes DebugPort was made, but a port was not already associated with the process.[1]
0x00000282: An attempt to remove a processes DebugPort was made, but a port was not already associated with the process.[1]
0x80070283: This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller.[1]
0x00000283: This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller.[1]
0x80070284: The specified range could not be found in the range list.[1]
0x00000284: The specified range could not be found in the range list.[1]
0x80070286: The driver was not loaded because the system is booting into safe mode.[1]
0x00000286: The driver was not loaded because the system is booting into safe mode.[1]
0x80070287: The driver was not loaded because it failed its initialization call.[1]
0x00000287: The driver was not loaded because it failed its initialization call.[1]
0x80070288: This may be caused by a failure of your hardware or by a poor connection.[1]
0x00000288: This may be caused by a failure of your hardware or by a poor connection.[1]
0x80070289: The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.[1]
0x00000289: The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.[1]
0x8007028A: The device object parameter is either not a valid device object or is not attached to the volume specified by the file name.[1]
0x0000028A: The device object parameter is either not a valid device object or is not attached to the volume specified by the file name.[1]
0x8007028B: A Machine Check Error has occurred. Please check the system eventlog for additional information.[1]
0x0000028B: A Machine Check Error has occurred. Please check the system eventlog for additional information.[1]
0x8007028C: There was error [%2] processing the driver database.[1]
0x0000028C: There was error [%2] processing the driver database.[1]
0x8007028D: System hive size has exceeded its limit.[1]
0x0000028D: System hive size has exceeded its limit.[1]
0x8007028E: The driver could not be loaded because a previous version of the driver is still in memory.[1]
0x0000028E: The driver could not be loaded because a previous version of the driver is still in memory.[1]
0x8007028F: Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation.[1]
0x0000028F: Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation.[1]
0x80070290: The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted.[1]
0x00000290: The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted.[1]
0x800702A8: A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended.[1]
0x000002A8: A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended.[1]
0x800702A9: The create operation stopped after reaching a symbolic link[1]
0x000002A9: The create operation stopped after reaching a symbolic link[1]
0x800702AB: The Plug and Play query operation was not successful.[1]
0x000002AB: The Plug and Play query operation was not successful.[1]
0x800702AC: A frame consolidation has been executed.[1]
0x000002AC: A frame consolidation has been executed.[1]
0x800702AD: was corrupted and it has been recovered. Some data might have been lost.[1]
0x000002AD: was corrupted and it has been recovered. Some data might have been lost.[1]
0x800702AE: The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?[1]
0x000002AE: The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?[1]
0x800702AF: The application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?[1]
0x000002AF: The application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?[1]
0x800702B0: Debugger did not handle the exception.[1]
0x000002B0: Debugger did not handle the exception.[1]
0x800702B9: Debugger command communication exception.[1]
0x000002B9: Debugger command communication exception.[1]
0x800702BA: An attempt was made to create an object and the object name already existed.[1]
0x000002BA: An attempt was made to create an object and the object name already existed.[1]
0x800702BB: A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.[1]
0x000002BB: A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.[1]
0x800702BC: An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image.[1]
0x000002BC: An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image.[1]
0x800702BD: This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created.[1]
0x000002BD: This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created.[1]
0x800702BE: An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments.[1]
0x000002BE: An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments.[1]
0x800702BF: Select OK to set current directory to %hs, or select CANCEL to exit.[1]
0x000002BF: Select OK to set current directory to %hs, or select CANCEL to exit.[1]
0x800702C0: This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device.[1]
0x000002C0: This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device.[1]
0x800702C1: This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device.[1]
0x000002C1: This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device.[1]
0x800702C2: The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load.[1]
0x000002C2: The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load.[1]
0x800702C3: The network transport returned partial data to its client. The remaining data will be sent later.[1]
0x000002C3: The network transport returned partial data to its client. The remaining data will be sent later.[1]
0x800702C4: The network transport returned data to its client that was marked as expedited by the remote system.[1]
0x000002C4: The network transport returned data to its client that was marked as expedited by the remote system.[1]
0x800702C5: The network transport returned partial data to its client and this data was marked as expedited by the remote system. The remaining data will be sent later.[1]
0x000002C5: The network transport returned partial data to its client and this data was marked as expedited by the remote system. The remaining data will be sent later.[1]
0x800702C6: The TDI indication has completed successfully.[1]
0x000002C6: The TDI indication has completed successfully.[1]
0x800702C7: The TDI indication has entered the pending state.[1]
0x000002C7: The TDI indication has entered the pending state.[1]
0x800702D0: The image file %hs is valid, but is for a machine type other than the current machine.[1]
0x000002D0: The image file %hs is valid, but is for a machine type other than the current machine.[1]
0x800702D1: A yield execution was performed and no thread was available to run.[1]
0x000002D1: A yield execution was performed and no thread was available to run.[1]
0x800702D2: The resumable flag to a timer API was ignored.[1]
0x000002D2: The resumable flag to a timer API was ignored.[1]
0x800702D3: The arbiter has deferred arbitration of these resources to its parent[1]
0x000002D3: The arbiter has deferred arbitration of these resources to its parent[1]
0x800702D4: The inserted CardBus device cannot be started because of a configuration error on "%hs".[1]
0x000002D4: The inserted CardBus device cannot be started because of a configuration error on "%hs".[1]
0x800702D5: The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported.[1]
0x000002D5: The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported.[1]
0x800702D7: The system was resumed from hibernation.[1]
0x000002D7: The system was resumed from hibernation.[1]
0x800702D8: Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].[1]
0x000002D8: Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].[1]
0x800702D9: A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit.[1]
0x000002D9: A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit.[1]
0x80070300: An exception occurred in a user mode callback and the kernel callback frame should be removed.[1]
0x00000300: An exception occurred in a user mode callback and the kernel callback frame should be removed.[1]
0x80070301: Compression is disabled for this volume.[1]
0x00000301: Compression is disabled for this volume.[1]
0x80070302: The data provider cannot fetch backwards through a result set.[1]
0x00000302: The data provider cannot fetch backwards through a result set.[1]
0x80070303: The data provider cannot scroll backwards through a result set.[1]
0x00000303: The data provider cannot scroll backwards through a result set.[1]
0x80070304: The data provider requires that previously fetched data is released before asking for more data.[1]
0x00000304: The data provider requires that previously fetched data is released before asking for more data.[1]
0x80070305: The data provider was not able to interpret the flags set for a column binding in an accessor.[1]
0x00000305: The data provider was not able to interpret the flags set for a column binding in an accessor.[1]
0x80070306: One or more errors occurred while processing the request.[1]
0x00000306: One or more errors occurred while processing the request.[1]
0x80070307: The implementation is not capable of performing the request.[1]
0x00000307: The implementation is not capable of performing the request.[1]
0x80070308: The client of a component requested an operation which is not valid given the state of the component instance.[1]
0x00000308: The client of a component requested an operation which is not valid given the state of the component instance.[1]
0x80070309: A version number could not be parsed.[1]
0x00000309: A version number could not be parsed.[1]
0x8007030A: The iterator's start position is invalid.[1]
0x0000030A: The iterator's start position is invalid.[1]
0x8007030B: The hardware has reported an uncorrectable memory error.[1]
0x0000030B: The hardware has reported an uncorrectable memory error.[1]
0x8007030C: The attempted operation required self healing to be enabled.[1]
0x0000030C: The attempted operation required self healing to be enabled.[1]
0x8007030D: The Desktop heap encountered an error while allocating session memory. There is more information in the system event log.[1]
0x0000030D: The Desktop heap encountered an error while allocating session memory. There is more information in the system event log.[1]
0x8007030E: The system power state is transitioning from %2 to %3.[1]
0x0000030E: The system power state is transitioning from %2 to %3.[1]
0x8007030F: The system power state is transitioning from %2 to %3 but could enter %4.[1]
0x0000030F: The system power state is transitioning from %2 to %3 but could enter %4.[1]
0x80070310: A thread is getting dispatched with MCA EXCEPTION because of MCA.[1]
0x00000310: A thread is getting dispatched with MCA EXCEPTION because of MCA.[1]
0x80070311: Access to %1 is monitored by policy rule %2.[1]
0x00000311: Access to %1 is monitored by policy rule %2.[1]
0x80070312: Access to %1 has been restricted by your Administrator by policy rule %2.[1]
0x00000312: Access to %1 has been restricted by your Administrator by policy rule %2.[1]
0x80070313: A valid hibernation file has been invalidated and should be abandoned.[1]
0x00000313: A valid hibernation file has been invalidated and should be abandoned.[1]
0x80070314: This error may be caused by network connectivity issues. Please try to save this file elsewhere.[1]
0x00000314: This error may be caused by network connectivity issues. Please try to save this file elsewhere.[1]
0x80070315: This error was returned by the server on which the file exists. Please try to save this file elsewhere.[1]
0x00000315: This error was returned by the server on which the file exists. Please try to save this file elsewhere.[1]
0x80070316: This error may be caused if the device has been removed or the media is write-protected.[1]
0x00000316: This error may be caused if the device has been removed or the media is write-protected.[1]
0x80070317: The resources required for this device conflict with the MCFG table.[1]
0x00000317: The resources required for this device conflict with the MCFG table.[1]
0x80070318: Please schedule to take the volume offline so that it can be repaired.[1]
0x00000318: Please schedule to take the volume offline so that it can be repaired.[1]
0x80070319: The volume repair was not successful.[1]
0x00000319: The volume repair was not successful.[1]
0x8007031A: One of the volume corruption logs is full. Further corruptions that may be detected won't be logged.[1]
0x0000031A: One of the volume corruption logs is full. Further corruptions that may be detected won't be logged.[1]
0x8007031B: One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.[1]
0x0000031B: One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.[1]
0x8007031C: One of the volume corruption logs is unavailable for being operated on.[1]
0x0000031C: One of the volume corruption logs is unavailable for being operated on.[1]
0x8007031D: One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned.[1]
0x0000031D: One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned.[1]
0x8007031E: One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions.[1]
0x0000031E: One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions.[1]
0x8007031F: Orphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory.[1]
0x0000031F: Orphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory.[1]
0x80070320: The oplock that was associated with this handle is now associated with a different handle.[1]
0x00000320: The oplock that was associated with this handle is now associated with a different handle.[1]
0x80070321: An oplock of the requested level cannot be granted. An oplock of a lower level may be available.[1]
0x00000321: An oplock of the requested level cannot be granted. An oplock of a lower level may be available.[1]
0x80070322: 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.[1]
0x00000322: 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.[1]
0x80070323: The handle with which this oplock was associated has been closed. The oplock is now broken.[1]
0x00000323: The handle with which this oplock was associated has been closed. The oplock is now broken.[1]
0x80070324: The specified access control entry (ACE) does not contain a condition.[1]
0x00000324: The specified access control entry (ACE) does not contain a condition.[1]
0x80070325: The specified access control entry (ACE) contains an invalid condition.[1]
0x00000325: The specified access control entry (ACE) contains an invalid condition.[1]
0x80070326: Access to the specified file handle has been revoked.[1]
0x00000326: Access to the specified file handle has been revoked.[1]
0x80070327: An image file was mapped at a different address from the one specified in the image file but fixups will still be automatically performed on the image.[1]
0x00000327: An image file was mapped at a different address from the one specified in the image file but fixups will still be automatically performed on the image.[1]
0x80070328: The read or write operation to an encrypted file could not be completed because the file has not been opened for data access.[1]
0x00000328: The read or write operation to an encrypted file could not be completed because the file has not been opened for data access.[1]
0x80070329: File metadata optimization is already in progress.[1]
0x00000329: File metadata optimization is already in progress.[1]
0x8007032A: The requested operation failed due to quota operation is still in progress.[1]
0x0000032A: The requested operation failed due to quota operation is still in progress.[1]
0x8007032B: Access to the specified handle has been revoked.[1]
0x0000032B: Access to the specified handle has been revoked.[1]
0x8007032C: The callback function must be invoked inline.[1]
0x0000032C: The callback function must be invoked inline.[1]
0x8007032D: The specified CPU Set IDs are invalid.[1]
0x0000032D: The specified CPU Set IDs are invalid.[1]
0x800703E2: Access to the extended attribute was denied.[1]
0x000003E2: Access to the extended attribute was denied.[1]
0x800703E3: The I/O operation has been aborted because of either a thread exit or an application request.[1]
0x000003E3: The I/O operation has been aborted because of either a thread exit or an application request.[1]
0x800703E4: Overlapped I/O event is not in a signaled state.[1]
0x000003E4: Overlapped I/O event is not in a signaled state.[1]
0x800703E5: Overlapped I/O operation is in progress.[1]
0x000003E5: Overlapped I/O operation is in progress.[1]
0x800703ED: Please make sure that all required file system drivers are loaded and that the volume is not corrupted.[1]
0x000003ED: Please make sure that all required file system drivers are loaded and that the volume is not corrupted.[1]
0x800703EE: The volume for a file has been externally altered so that the opened file is no longer valid.[1]
0x000003EE: The volume for a file has been externally altered so that the opened file is no longer valid.[1]
0x800703EF: The requested operation cannot be performed in full-screen mode.[1]
0x000003EF: The requested operation cannot be performed in full-screen mode.[1]
0x800703F0: An attempt was made to reference a token that does not exist.[1]
0x000003F0: An attempt was made to reference a token that does not exist.[1]
0x800703F1: The configuration registry database is corrupt.[1]
0x000003F1: The configuration registry database is corrupt.[1]
0x800703F2: The configuration registry key is invalid.[1]
0x000003F2: The configuration registry key is invalid.[1]
0x800703F3: The configuration registry key could not be opened.[1]
0x000003F3: The configuration registry key could not be opened.[1]
0x800703F4: The configuration registry key could not be read.[1]
0x000003F4: The configuration registry key could not be read.[1]
0x800703F5: The configuration registry key could not be written.[1]
0x000003F5: The configuration registry key could not be written.[1]
0x800703F6: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.[1]
0x000003F6: One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.[1]
0x800703F7: The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.[1]
0x000003F7: The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.[1]
0x800703F8: An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.[1]
0x000003F8: An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.[1]
0x800703F9: The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.[1]
0x000003F9: The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.[1]
0x800703FA: Illegal operation attempted on a registry key that has been marked for deletion.[1]
0x000003FA: Illegal operation attempted on a registry key that has been marked for deletion.[1]
0x800703FB: System could not allocate the required space in a registry log.[1]
0x000003FB: System could not allocate the required space in a registry log.[1]
0x800703FC: Cannot create a symbolic link in a registry key that already has subkeys or values.[1]
0x000003FC: Cannot create a symbolic link in a registry key that already has subkeys or values.[1]
0x800703FD: Cannot create a stable subkey under a volatile parent key.[1]
0x000003FD: Cannot create a stable subkey under a volatile parent key.[1]
0x800703FE: A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.[1]
0x000003FE: A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.[1]
0x8007041B: A stop control has been sent to a service that other running services are dependent on.[1]
0x0000041B: A stop control has been sent to a service that other running services are dependent on.[1]
0x8007041C: The requested control is not valid for this service.[1]
0x0000041C: The requested control is not valid for this service.[1]
0x8007041D: The service did not respond to the start or control request in a timely fashion.[1]
0x0000041D: The service did not respond to the start or control request in a timely fashion.[1]
0x8007041E: A thread could not be created for the service.[1]
0x0000041E: A thread could not be created for the service.[1]
0x8007045C: Unable to abort the system shutdown because no shutdown was in progress.[1]
0x0000045C: Unable to abort the system shutdown because no shutdown was in progress.[1]
0x8007045D: The request could not be performed because of an I/O device error.[1]
0x0000045D: The request could not be performed because of an I/O device error.[1]
0x8007045E: No serial device was successfully initialized. The serial driver will unload.[1]
0x0000045E: No serial device was successfully initialized. The serial driver will unload.[1]
0x8007045F: Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.[1]
0x0000045F: Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.[1]
0x80070460: (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)[1]
0x00000460: (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)[1]
0x80070461: (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)[1]
0x00000461: (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)[1]
0x80070462: No ID address mark was found on the floppy disk.[1]
0x00000462: No ID address mark was found on the floppy disk.[1]
0x80070463: Mismatch between the floppy disk sector ID field and the floppy disk controller track address.[1]
0x00000463: Mismatch between the floppy disk sector ID field and the floppy disk controller track address.[1]
0x80070464: The floppy disk controller reported an error that is not recognized by the floppy disk driver.[1]
0x00000464: The floppy disk controller reported an error that is not recognized by the floppy disk driver.[1]
0x80070465: The floppy disk controller returned inconsistent results in its registers.[1]
0x00000465: The floppy disk controller returned inconsistent results in its registers.[1]
0x80070466: While accessing the hard disk, a recalibrate operation failed, even after retries.[1]
0x00000466: While accessing the hard disk, a recalibrate operation failed, even after retries.[1]
0x80070467: While accessing the hard disk, a disk operation failed even after retries.[1]
0x00000467: While accessing the hard disk, a disk operation failed even after retries.[1]
0x80070468: While accessing the hard disk, a disk controller reset was needed, but even that failed.[1]
0x00000468: While accessing the hard disk, a disk controller reset was needed, but even that failed.[1]
0x80070497: Unable to remove the file to be replaced.[1]
0x00000497: Unable to remove the file to be replaced.[1]
0x80070498: Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.[1]
0x00000498: Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.[1]
0x80070499: Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.[1]
0x00000499: Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.[1]
0x8007049A: The volume change journal is being deleted.[1]
0x0000049A: The volume change journal is being deleted.[1]
0x8007049B: The volume change journal is not active.[1]
0x0000049B: The volume change journal is not active.[1]
0x8007049C: A file was found, but it may not be the correct file.[1]
0x0000049C: A file was found, but it may not be the correct file.[1]
0x8007049D: The journal entry has been deleted from the journal.[1]
0x0000049D: The journal entry has been deleted from the journal.[1]
0x800704A6: A system shutdown has already been scheduled.[1]
0x000004A6: A system shutdown has already been scheduled.[1]
0x800704A7: The system shutdown cannot be initiated because there are other users logged on to the computer.[1]
0x000004A7: The system shutdown cannot be initiated because there are other users logged on to the computer.[1]
0x800704B0: The specified device name is invalid.[1]
0x000004B0: The specified device name is invalid.[1]
0x800704B1: The device is not currently connected but it is a remembered connection.[1]
0x000004B1: The device is not currently connected but it is a remembered connection.[1]
0x800704B2: The local device name has a remembered connection to another network resource.[1]
0x000004B2: The local device name has a remembered connection to another network resource.[1]
0x800704B3: The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.[1]
0x000004B3: The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.[1]
0x800704B4: The specified network provider name is invalid.[1]
0x000004B4: The specified network provider name is invalid.[1]
0x800704B5: Unable to open the network connection profile.[1]
0x000004B5: Unable to open the network connection profile.[1]
0x800704B6: The network connection profile is corrupted.[1]
0x000004B6: The network connection profile is corrupted.[1]
0x800704B9: The format of the specified group name is invalid.[1]
0x000004B9: The format of the specified group name is invalid.[1]
0x800704BA: The format of the specified computer name is invalid.[1]
0x000004BA: The format of the specified computer name is invalid.[1]
0x800704BB: The format of the specified event name is invalid.[1]
0x000004BB: The format of the specified event name is invalid.[1]
0x800704BC: The format of the specified domain name is invalid.[1]
0x000004BC: The format of the specified domain name is invalid.[1]
0x800704BD: The format of the specified service name is invalid.[1]
0x000004BD: The format of the specified service name is invalid.[1]
0x800704BE: The format of the specified network name is invalid.[1]
0x000004BE: The format of the specified network name is invalid.[1]
0x800704BF: The format of the specified share name is invalid.[1]
0x000004BF: The format of the specified share name is invalid.[1]
0x800704C0: The format of the specified password is invalid.[1]
0x000004C0: The format of the specified password is invalid.[1]
0x800704C1: The format of the specified message name is invalid.[1]
0x000004C1: The format of the specified message name is invalid.[1]
0x800704C2: The format of the specified message destination is invalid.[1]
0x000004C2: The format of the specified message destination is invalid.[1]
0x800704C3: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.[1]
0x000004C3: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.[1]
0x800704C4: An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.[1]
0x000004C4: An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.[1]
0x800704C5: The workgroup or domain name is already in use by another computer on the network.[1]
0x000004C5: The workgroup or domain name is already in use by another computer on the network.[1]
0x800704C6: The network is not present or not started.[1]
0x000004C6: The network is not present or not started.[1]
0x800704C7: The operation was canceled by the user.[1]
0x000004C7: The operation was canceled by the user.[1]
0x800704C8: The requested operation cannot be performed on a file with a user-mapped section open.[1]
0x000004C8: The requested operation cannot be performed on a file with a user-mapped section open.[1]
0x800704C9: The remote computer refused the network connection.[1]
0x000004C9: The remote computer refused the network connection.[1]
0x800704CA: The network connection was gracefully closed.[1]
0x000004CA: The network connection was gracefully closed.[1]
0x800704CB: The network transport endpoint already has an address associated with it.[1]
0x000004CB: The network transport endpoint already has an address associated with it.[1]
0x800704CC: An address has not yet been associated with the network endpoint.[1]
0x000004CC: An address has not yet been associated with the network endpoint.[1]
0x800704CD: An operation was attempted on a nonexistent network connection.[1]
0x000004CD: An operation was attempted on a nonexistent network connection.[1]
0x800704CE: An invalid operation was attempted on an active network connection.[1]
0x000004CE: An invalid operation was attempted on an active network connection.[1]
0x800704CF: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x000004CF: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x800704D0: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x000004D0: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x800704D1: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x000004D1: The network location cannot be reached. For information about network troubleshooting, see Windows Help.[1]
0x800704D2: No service is operating at the destination network endpoint on the remote system.[1]
0x000004D2: No service is operating at the destination network endpoint on the remote system.[1]
0x800704D4: The network connection was aborted by the local system.[1]
0x000004D4: The network connection was aborted by the local system.[1]
0x800704D5: The operation could not be completed. A retry should be performed.[1]
0x000004D5: The operation could not be completed. A retry should be performed.[1]
0x800704D6: A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.[1]
0x000004D6: A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.[1]
0x800704D7: Attempting to log in during an unauthorized time of day for this account.[1]
0x000004D7: Attempting to log in during an unauthorized time of day for this account.[1]
0x800704D8: The account is not authorized to log in from this station.[1]
0x000004D8: The account is not authorized to log in from this station.[1]
0x800704D9: The network address could not be used for the operation requested.[1]
0x000004D9: The network address could not be used for the operation requested.[1]
0x800704DB: The specified service does not exist.[1]
0x000004DB: The specified service does not exist.[1]
0x800704DC: The operation being requested was not performed because the user has not been authenticated.[1]
0x000004DC: The operation being requested was not performed because the user has not been authenticated.[1]
0x800704DD: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.[1]
0x000004DD: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.[1]
0x800704E8: The remote system is not available. For information about network troubleshooting, see Windows Help.[1]
0x000004E8: The remote system is not available. For information about network troubleshooting, see Windows Help.[1]
0x800704E9: The security identifier provided is not from an account domain.[1]
0x000004E9: The security identifier provided is not from an account domain.[1]
0x800704EA: The security identifier provided does not have a domain component.[1]
0x000004EA: The security identifier provided does not have a domain component.[1]
0x800704EB: AppHelp dialog canceled thus preventing the application from starting.[1]
0x000004EB: AppHelp dialog canceled thus preventing the application from starting.[1]
0x800704EC: This program is blocked by group policy. For more information, contact your system administrator.[1]
0x000004EC: This program is blocked by group policy. For more information, contact your system administrator.[1]
0x800704ED: A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific.[1]
0x000004ED: A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific.[1]
0x800704EE: The share is currently offline or does not exist.[1]
0x000004EE: The share is currently offline or does not exist.[1]
0x800704EF: The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log.[1]
0x000004EF: The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log.[1]
0x800704F0: The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.[1]
0x000004F0: The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.[1]
0x800704F1: The system cannot contact a domain controller to service the authentication request. Please try again later.[1]
0x000004F1: The system cannot contact a domain controller to service the authentication request. Please try again later.[1]
0x800704F7: The machine is locked and cannot be shut down without the force option.[1]
0x000004F7: The machine is locked and cannot be shut down without the force option.[1]
0x800704F8: You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.[1]
0x000004F8: You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.[1]
0x800704F9: An application-defined callback gave invalid data when called.[1]
0x000004F9: An application-defined callback gave invalid data when called.[1]
0x800704FA: The group policy framework should call the extension in the synchronous foreground policy refresh.[1]
0x000004FA: The group policy framework should call the extension in the synchronous foreground policy refresh.[1]
0x800704FB: This driver has been blocked from loading[1]
0x000004FB: This driver has been blocked from loading[1]
0x800704FC: A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image.[1]
0x000004FC: A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image.[1]
0x800704FD: Windows cannot open this program since it has been disabled.[1]
0x000004FD: Windows cannot open this program since it has been disabled.[1]
0x800704FE: Windows cannot open this program because the license enforcement system has been tampered with or become corrupted.[1]
0x000004FE: Windows cannot open this program because the license enforcement system has been tampered with or become corrupted.[1]
0x80070500: The current thread has already been converted to a fiber.[1]
0x00000500: The current thread has already been converted to a fiber.[1]
0x80070501: The current thread has already been converted from a fiber.[1]
0x00000501: The current thread has already been converted from a fiber.[1]
0x80070502: The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.[1]
0x00000502: The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.[1]
0x80070503: Data present in one of the parameters is more than the function can operate on.[1]
0x00000503: Data present in one of the parameters is more than the function can operate on.[1]
0x80070504: An attempt to do an operation on a debug object failed because the object is in the process of being deleted.[1]
0x00000504: An attempt to do an operation on a debug object failed because the object is in the process of being deleted.[1]
0x80070505: An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.[1]
0x00000505: An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.[1]
0x80070506: %1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator.[1]
0x00000506: %1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator.[1]
0x80070507: Insufficient information exists to identify the cause of failure.[1]
0x00000507: Insufficient information exists to identify the cause of failure.[1]
0x80070508: The parameter passed to a C runtime function is incorrect.[1]
0x00000508: The parameter passed to a C runtime function is incorrect.[1]
0x80070509: The operation occurred beyond the valid data length of the file.[1]
0x00000509: The operation occurred beyond the valid data length of the file.[1]
0x8007050A: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.[1]
0x0000050A: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.[1]
0x8007050B: The process hosting the driver for this device has been terminated.[1]
0x0000050B: The process hosting the driver for this device has been terminated.[1]
0x8007050C: An operation attempted to exceed an implementation-defined limit.[1]
0x0000050C: An operation attempted to exceed an implementation-defined limit.[1]
0x8007050D: Either the target process, or the target thread's containing process, is a protected process.[1]
0x0000050D: Either the target process, or the target thread's containing process, is a protected process.[1]
0x8007050E: The service notification client is lagging too far behind the current state of services in the machine.[1]
0x0000050E: The service notification client is lagging too far behind the current state of services in the machine.[1]
0x8007050F: To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator.[1]
0x0000050F: To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator.[1]
0x80070510: The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.[1]
0x00000510: The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.[1]
0x80070511: You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration.[1]
0x00000511: You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration.[1]
0x80070512: A thread involved in this operation appears to be unresponsive.[1]
0x00000512: A thread involved in this operation appears to be unresponsive.[1]
0x80070513: Indicates a particular Security ID may not be assigned as the label of an object.[1]
0x00000513: Indicates a particular Security ID may not be assigned as the label of an object.[1]
0x80070514: Not all privileges or groups referenced are assigned to the caller.[1]
0x00000514: Not all privileges or groups referenced are assigned to the caller.[1]
0x80070515: Some mapping between account names and security IDs was not done.[1]
0x00000515: Some mapping between account names and security IDs was not done.[1]
0x80070516: No system quota limits are specifically set for this account.[1]
0x00000516: No system quota limits are specifically set for this account.[1]
0x80070517: No encryption key is available. A well-known encryption key was returned.[1]
0x00000517: No encryption key is available. A well-known encryption key was returned.[1]
0x80070518: The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.[1]
0x00000518: The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.[1]
0x80070528: Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.[1]
0x00000528: Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.[1]
0x80070529: The specified user account is not a member of the specified group account.[1]
0x00000529: The specified user account is not a member of the specified group account.[1]
0x8007052A: This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon.[1]
0x0000052A: This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon.[1]
0x8007052B: Unable to update the password. The value provided as the current password is incorrect.[1]
0x0000052B: Unable to update the password. The value provided as the current password is incorrect.[1]
0x8007052C: Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.[1]
0x0000052C: Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.[1]
0x8007052D: Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain.[1]
0x0000052D: Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain.[1]
0x8007052E: The user name or password is incorrect.[1]
0x0000052E: The user name or password is incorrect.[1]
0x8007052F: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.[1]
0x0000052F: Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.[1]
0x80070530: Your account has time restrictions that keep you from signing in right now.[1]
0x00000530: Your account has time restrictions that keep you from signing in right now.[1]
0x80070531: This user isn't allowed to sign in to this computer.[1]
0x00000531: This user isn't allowed to sign in to this computer.[1]
0x80070532: The password for this account has expired.[1]
0x00000532: The password for this account has expired.[1]
0x80070533: This user can't sign in because this account is currently disabled.[1]
0x00000533: This user can't sign in because this account is currently disabled.[1]
0x80070534: No mapping between account names and security IDs was done.[1]
0x00000534: No mapping between account names and security IDs was done.[1]
0x80070535: Too many local user identifiers (LUIDs) were requested at one time.[1]
0x00000535: Too many local user identifiers (LUIDs) were requested at one time.[1]
0x80070536: No more local user identifiers (LUIDs) are available.[1]
0x00000536: No more local user identifiers (LUIDs) are available.[1]
0x80070537: The subauthority part of a security ID is invalid for this particular use.[1]
0x00000537: The subauthority part of a security ID is invalid for this particular use.[1]
0x80070538: The access control list (ACL) structure is invalid.[1]
0x00000538: The access control list (ACL) structure is invalid.[1]
0x80070539: The security ID structure is invalid.[1]
0x00000539: The security ID structure is invalid.[1]
0x8007053A: The security descriptor structure is invalid.[1]
0x0000053A: The security descriptor structure is invalid.[1]
0x8007053C: The inherited access control list (ACL) or access control entry (ACE) could not be built.[1]
0x0000053C: The inherited access control list (ACL) or access control entry (ACE) could not be built.[1]
0x8007053F: The value provided was an invalid value for an identifier authority.[1]
0x0000053F: The value provided was an invalid value for an identifier authority.[1]
0x80070540: No more memory is available for security information updates.[1]
0x00000540: No more memory is available for security information updates.[1]
0x80070541: The specified attributes are invalid, or incompatible with the attributes for the group as a whole.[1]
0x00000541: The specified attributes are invalid, or incompatible with the attributes for the group as a whole.[1]
0x80070542: Either a required impersonation level was not provided, or the provided impersonation level is invalid.[1]
0x00000542: Either a required impersonation level was not provided, or the provided impersonation level is invalid.[1]
0x80070543: Cannot open an anonymous level security token.[1]
0x00000543: Cannot open an anonymous level security token.[1]
0x80070544: The validation information class requested was invalid.[1]
0x00000544: The validation information class requested was invalid.[1]
0x80070545: The type of the token is inappropriate for its attempted use.[1]
0x00000545: The type of the token is inappropriate for its attempted use.[1]
0x80070546: Unable to perform a security operation on an object that has no associated security.[1]
0x00000546: Unable to perform a security operation on an object that has no associated security.[1]
0x80070547: Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.[1]
0x00000547: Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.[1]
0x80070548: The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.[1]
0x00000548: The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.[1]
0x80070549: The domain was in the wrong state to perform the security operation.[1]
0x00000549: The domain was in the wrong state to perform the security operation.[1]
0x8007054A: This operation is only allowed for the Primary Domain Controller of the domain.[1]
0x0000054A: This operation is only allowed for the Primary Domain Controller of the domain.[1]
0x8007054B: The specified domain either does not exist or could not be contacted.[1]
0x0000054B: The specified domain either does not exist or could not be contacted.[1]
0x80070550: Generic access types were contained in an access mask which should already be mapped to nongeneric types.[1]
0x00000550: Generic access types were contained in an access mask which should already be mapped to nongeneric types.[1]
0x80070551: A security descriptor is not in the right format (absolute or self-relative).[1]
0x00000551: A security descriptor is not in the right format (absolute or self-relative).[1]
0x80070552: The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.[1]
0x00000552: The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.[1]
0x80070553: Cannot start a new logon session with an ID that is already in use.[1]
0x00000553: Cannot start a new logon session with an ID that is already in use.[1]
0x80070554: A specified authentication package is unknown.[1]
0x00000554: A specified authentication package is unknown.[1]
0x80070555: The logon session is not in a state that is consistent with the requested operation.[1]
0x00000555: The logon session is not in a state that is consistent with the requested operation.[1]
0x80070556: The logon session ID is already in use.[1]
0x00000556: The logon session ID is already in use.[1]
0x80070557: A logon request contained an invalid logon type value.[1]
0x00000557: A logon request contained an invalid logon type value.[1]
0x80070558: Unable to impersonate using a named pipe until data has been read from that pipe.[1]
0x00000558: Unable to impersonate using a named pipe until data has been read from that pipe.[1]
0x80070559: The transaction state of a registry subtree is incompatible with the requested operation.[1]
0x00000559: The transaction state of a registry subtree is incompatible with the requested operation.[1]
0x8007055A: An internal security database corruption has been encountered.[1]
0x0000055A: An internal security database corruption has been encountered.[1]
0x8007055B: Cannot perform this operation on built-in accounts.[1]
0x0000055B: Cannot perform this operation on built-in accounts.[1]
0x8007055C: Cannot perform this operation on this built-in special group.[1]
0x0000055C: Cannot perform this operation on this built-in special group.[1]
0x8007055D: Cannot perform this operation on this built-in special user.[1]
0x0000055D: Cannot perform this operation on this built-in special user.[1]
0x8007055E: The user cannot be removed from a group because the group is currently the user's primary group.[1]
0x0000055E: The user cannot be removed from a group because the group is currently the user's primary group.[1]
0x8007055F: The token is already in use as a primary token.[1]
0x0000055F: The token is already in use as a primary token.[1]
0x80070560: The specified local group does not exist.[1]
0x00000560: The specified local group does not exist.[1]
0x80070561: The specified account name is not a member of the group.[1]
0x00000561: The specified account name is not a member of the group.[1]
0x80070562: The specified account name is already a member of the group.[1]
0x00000562: The specified account name is already a member of the group.[1]
0x80070563: The specified local group already exists.[1]
0x00000563: The specified local group already exists.[1]
0x80070564: Logon failure: the user has not been granted the requested logon type at this computer.[1]
0x00000564: Logon failure: the user has not been granted the requested logon type at this computer.[1]
0x80070565: The maximum number of secrets that may be stored in a single system has been exceeded.[1]
0x00000565: The maximum number of secrets that may be stored in a single system has been exceeded.[1]
0x80070566: The length of a secret exceeds the maximum length allowed.[1]
0x00000566: The length of a secret exceeds the maximum length allowed.[1]
0x80070567: The local security authority database contains an internal inconsistency.[1]
0x00000567: The local security authority database contains an internal inconsistency.[1]
0x80070568: During a logon attempt, the user's security context accumulated too many security IDs.[1]
0x00000568: During a logon attempt, the user's security context accumulated too many security IDs.[1]
0x80070569: Logon failure: the user has not been granted the requested logon type at this computer.[1]
0x00000569: Logon failure: the user has not been granted the requested logon type at this computer.[1]
0x8007056A: A cross-encrypted password is necessary to change a user password.[1]
0x0000056A: A cross-encrypted password is necessary to change a user password.[1]
0x8007056B: A member could not be added to or removed from the local group because the member does not exist.[1]
0x0000056B: A member could not be added to or removed from the local group because the member does not exist.[1]
0x8007056C: A new member could not be added to a local group because the member has the wrong account type.[1]
0x0000056C: A new member could not be added to a local group because the member has the wrong account type.[1]
0x8007056D: Too many security IDs have been specified.[1]
0x0000056D: Too many security IDs have been specified.[1]
0x8007056E: A cross-encrypted password is necessary to change this user password.[1]
0x0000056E: A cross-encrypted password is necessary to change this user password.[1]
0x8007056F: Indicates an ACL contains no inheritable components.[1]
0x0000056F: Indicates an ACL contains no inheritable components.[1]
0x80070570: The file or directory is corrupted and unreadable.[1]
0x00000570: The file or directory is corrupted and unreadable.[1]
0x80070571: The disk structure is corrupted and unreadable.[1]
0x00000571: The disk structure is corrupted and unreadable.[1]
0x80070572: There is no user session key for the specified logon session.[1]
0x00000572: There is no user session key for the specified logon session.[1]
0x80070573: The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.[1]
0x00000573: The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.[1]
0x80070574: The target account name is incorrect.[1]
0x00000574: The target account name is incorrect.[1]
0x80070575: Mutual Authentication failed. The server's password is out of date at the domain controller.[1]
0x00000575: Mutual Authentication failed. The server's password is out of date at the domain controller.[1]
0x80070576: There is a time and/or date difference between the client and server.[1]
0x00000576: There is a time and/or date difference between the client and server.[1]
0x80070577: This operation cannot be performed on the current domain.[1]
0x00000577: This operation cannot be performed on the current domain.[1]
0x80070610: The specified thread is already joining a task.[1]
0x00000610: The specified thread is already joining a task.[1]
0x80070641: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.[1]
0x00000641: The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.[1]
0x8007064C: The installation source for this product is not available. Verify that the source exists and that you can access it.[1]
0x0000064C: The installation source for this product is not available. Verify that the source exists and that you can access it.[1]
0x8007064D: This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.[1]
0x0000064D: This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.[1]
0x80070652: Another installation is already in progress. Complete that installation before proceeding with this install.[1]
0x00000652: Another installation is already in progress. Complete that installation before proceeding with this install.[1]
0x80070653: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.[1]
0x00000653: This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.[1]
0x80070654: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.[1]
0x00000654: This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.[1]
0x80070655: There was an error starting the Windows Installer service user interface. Contact your support personnel.[1]
0x00000655: There was an error starting the Windows Installer service user interface. Contact your support personnel.[1]
0x80070656: Error opening installation log file. Verify that the specified log file location exists and that you can write to it.[1]
0x00000656: Error opening installation log file. Verify that the specified log file location exists and that you can write to it.[1]
0x80070657: The language of this installation package is not supported by your system.[1]
0x00000657: The language of this installation package is not supported by your system.[1]
0x80070658: Error applying transforms. Verify that the specified transform paths are valid.[1]
0x00000658: Error applying transforms. Verify that the specified transform paths are valid.[1]
0x80070659: This installation is forbidden by system policy. Contact your system administrator.[1]
0x00000659: This installation is forbidden by system policy. Contact your system administrator.[1]
0x8007065F: The Windows Installer service failed to start. Contact your support personnel.[1]
0x0000065F: The Windows Installer service failed to start. Contact your support personnel.[1]
0x80070660: The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder.[1]
0x00000660: The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder.[1]
0x80070661: This installation package is not supported by this processor type. Contact your product vendor.[1]
0x00000661: This installation package is not supported by this processor type. Contact your product vendor.[1]
0x80070663: This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.[1]
0x00000663: This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.[1]
0x80070664: This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.[1]
0x00000664: This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.[1]
0x80070665: This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.[1]
0x00000665: This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.[1]
0x80070666: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.[1]
0x00000666: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.[1]
0x80070667: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.[1]
0x00000667: Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.[1]
0x80070668: Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.[1]
0x00000668: Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.[1]
0x80070669: The requested operation completed successfully. The system will be restarted so the changes can take effect.[1]
0x00000669: The requested operation completed successfully. The system will be restarted so the changes can take effect.[1]
0x8007066A: The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.[1]
0x0000066A: The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.[1]
0x8007066B: The update package is not permitted by software restriction policy.[1]
0x0000066B: The update package is not permitted by software restriction policy.[1]
0x8007066C: One or more customizations are not permitted by software restriction policy.[1]
0x0000066C: One or more customizations are not permitted by software restriction policy.[1]
0x8007066D: The Windows Installer does not permit installation from a Remote Desktop Connection.[1]
0x0000066D: The Windows Installer does not permit installation from a Remote Desktop Connection.[1]
0x8007066E: Uninstallation of the update package is not supported.[1]
0x0000066E: Uninstallation of the update package is not supported.[1]
0x8007066F: The update is not applied to this product.[1]
0x0000066F: The update is not applied to this product.[1]
0x80070670: No valid sequence could be found for the set of updates.[1]
0x00000670: No valid sequence could be found for the set of updates.[1]
0x80070671: Update removal was disallowed by policy.[1]
0x00000671: Update removal was disallowed by policy.[1]
0x80070673: Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update.[1]
0x00000673: Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update.[1]
0x80070674: The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state.[1]
0x00000674: The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state.[1]
0x80070675: A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.[1]
0x00000675: A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.[1]
0x80070676: The app that you are trying to run is not supported on this version of Windows.[1]
0x00000676: The app that you are trying to run is not supported on this version of Windows.[1]
0x80070677: The operation was blocked as the process prohibits dynamic code generation.[1]
0x00000677: The operation was blocked as the process prohibits dynamic code generation.[1]
0x80070773: The user's password must be changed before signing in.[1]
0x00000773: The user's password must be changed before signing in.[1]
0x80070774: Could not find the domain controller for this domain.[1]
0x00000774: Could not find the domain controller for this domain.[1]
0x80070775: The referenced account is currently locked out and may not be logged on to.[1]
0x00000775: The referenced account is currently locked out and may not be logged on to.[1]
0x8007077F: No site name is available for this machine.[1]
0x0000077F: No site name is available for this machine.[1]
0x80070780: The file cannot be accessed by the system.[1]
0x00000780: The file cannot be accessed by the system.[1]
0x80070781: The name of the file cannot be resolved by the system.[1]
0x00000781: The name of the file cannot be resolved by the system.[1]
0x8007078A: The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.[1]
0x0000078A: The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.[1]
0x8007078B: The context has expired and can no longer be used.[1]
0x0000078B: The context has expired and can no longer be used.[1]
0x8007078C: The current user's delegated trust creation quota has been exceeded.[1]
0x0000078C: The current user's delegated trust creation quota has been exceeded.[1]
0x8007078D: The total delegated trust creation quota has been exceeded.[1]
0x0000078D: The total delegated trust creation quota has been exceeded.[1]
0x8007078E: The current user's delegated trust deletion quota has been exceeded.[1]
0x0000078E: The current user's delegated trust deletion quota has been exceeded.[1]
0x8007078F: The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer.[1]
0x0000078F: The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer.[1]
0x80070790: Remote connections to the Print Spooler are blocked by a policy set on your machine.[1]
0x00000790: Remote connections to the Print Spooler are blocked by a policy set on your machine.[1]
0x80070791: Authentication failed because NTLM authentication has been disabled.[1]
0x00000791: Authentication failed because NTLM authentication has been disabled.[1]
0x80070792: Logon Failure: EAS policy requires that the user change their password before this operation can be performed.[1]
0x00000792: Logon Failure: EAS policy requires that the user change their password before this operation can be performed.[1]
0x80070FA2: The importation from the file failed.[1]
0x00000FA2: The importation from the file failed.[1]
0x80070FA3: The backup failed. Was a full backup done before?[1]
0x00000FA3: The backup failed. Was a full backup done before?[1]
0x80070FA4: The backup failed. Check the directory to which you are backing the database.[1]
0x00000FA4: The backup failed. Check the directory to which you are backing the database.[1]
0x80070FA5: The name does not exist in the WINS database.[1]
0x00000FA5: The name does not exist in the WINS database.[1]
0x80070FA6: Replication with a nonconfigured partner is not allowed.[1]
0x00000FA6: Replication with a nonconfigured partner is not allowed.[1]
0x80071004: The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.[1]
0x00001004: The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.[1]
0x80071068: The GUID passed was not recognized as valid by a WMI data provider.[1]
0x00001068: The GUID passed was not recognized as valid by a WMI data provider.[1]
0x80071069: The instance name passed was not recognized as valid by a WMI data provider.[1]
0x00001069: The instance name passed was not recognized as valid by a WMI data provider.[1]
0x8007106A: The data item ID passed was not recognized as valid by a WMI data provider.[1]
0x0000106A: The data item ID passed was not recognized as valid by a WMI data provider.[1]
0x8007106B: The WMI request could not be completed and should be retried.[1]
0x0000106B: The WMI request could not be completed and should be retried.[1]
0x8007106C: The WMI data provider could not be located.[1]
0x0000106C: The WMI data provider could not be located.[1]
0x8007106D: The WMI data provider references an instance set that has not been registered.[1]
0x0000106D: The WMI data provider references an instance set that has not been registered.[1]
0x8007106E: The WMI data block or event notification has already been enabled.[1]
0x0000106E: The WMI data block or event notification has already been enabled.[1]
0x8007106F: The WMI data block is no longer available.[1]
0x0000106F: The WMI data block is no longer available.[1]
0x80071070: The WMI data service is not available.[1]
0x00001070: The WMI data service is not available.[1]
0x80071071: The WMI data provider failed to carry out the request.[1]
0x00001071: The WMI data provider failed to carry out the request.[1]
0x80071072: The WMI MOF information is not valid.[1]
0x00001072: The WMI MOF information is not valid.[1]
0x80071073: The WMI registration information is not valid.[1]
0x00001073: The WMI registration information is not valid.[1]
0x80071074: The WMI data block or event notification has already been disabled.[1]
0x00001074: The WMI data block or event notification has already been disabled.[1]
0x80071075: The WMI data item or data block is read only.[1]
0x00001075: The WMI data item or data block is read only.[1]
0x80071076: The WMI data item or data block could not be changed.[1]
0x00001076: The WMI data item or data block could not be changed.[1]
0x8007109A: This operation is only valid in the context of an app container.[1]
0x0000109A: This operation is only valid in the context of an app container.[1]
0x8007109B: This application can only run in the context of an app container.[1]
0x0000109B: This application can only run in the context of an app container.[1]
0x8007109C: This functionality is not supported in the context of an app container.[1]
0x0000109C: This functionality is not supported in the context of an app container.[1]
0x8007109D: The length of the SID supplied is not a valid length for app container SIDs.[1]
0x0000109D: The length of the SID supplied is not a valid length for app container SIDs.[1]
0x800710CC: The media identifier does not represent a valid medium.[1]
0x000010CC: The media identifier does not represent a valid medium.[1]
0x800710CD: The library identifier does not represent a valid library.[1]
0x000010CD: The library identifier does not represent a valid library.[1]
0x800710CE: The media pool identifier does not represent a valid media pool.[1]
0x000010CE: The media pool identifier does not represent a valid media pool.[1]
0x800710CF: The drive and medium are not compatible or exist in different libraries.[1]
0x000010CF: The drive and medium are not compatible or exist in different libraries.[1]
0x800710D0: The medium currently exists in an offline library and must be online to perform this operation.[1]
0x000010D0: The medium currently exists in an offline library and must be online to perform this operation.[1]
0x800710D1: The operation cannot be performed on an offline library.[1]
0x000010D1: The operation cannot be performed on an offline library.[1]
0x800710D2: The library, drive, or media pool is empty.[1]
0x000010D2: The library, drive, or media pool is empty.[1]
0x800710D3: The library, drive, or media pool must be empty to perform this operation.[1]
0x000010D3: The library, drive, or media pool must be empty to perform this operation.[1]
0x800710D4: No media is currently available in this media pool or library.[1]
0x000010D4: No media is currently available in this media pool or library.[1]
0x800710D5: A resource required for this operation is disabled.[1]
0x000010D5: A resource required for this operation is disabled.[1]
0x800710D6: The media identifier does not represent a valid cleaner.[1]
0x000010D6: The media identifier does not represent a valid cleaner.[1]
0x800710D7: The drive cannot be cleaned or does not support cleaning.[1]
0x000010D7: The drive cannot be cleaned or does not support cleaning.[1]
0x800710D8: The object identifier does not represent a valid object.[1]
0x000010D8: The object identifier does not represent a valid object.[1]
0x800710D9: Unable to read from or write to the database.[1]
0x000010D9: Unable to read from or write to the database.[1]
0x80071394: The cluster group is not available for any new requests.[1]
0x00001394: The cluster group is not available for any new requests.[1]
0x80071395: The cluster group could not be found.[1]
0x00001395: The cluster group could not be found.[1]
0x80071396: The operation could not be completed because the cluster group is not online.[1]
0x00001396: The operation could not be completed because the cluster group is not online.[1]
0x80071397: The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.[1]
0x00001397: The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.[1]
0x80071398: The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.[1]
0x00001398: The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.[1]
0x80071399: The cluster resource could not be created in the specified resource monitor.[1]
0x00001399: The cluster resource could not be created in the specified resource monitor.[1]
0x8007139A: The cluster resource could not be brought online by the resource monitor.[1]
0x0000139A: The cluster resource could not be brought online by the resource monitor.[1]
0x8007139B: The operation could not be completed because the cluster resource is online.[1]
0x0000139B: The operation could not be completed because the cluster resource is online.[1]
0x8007139C: The cluster resource could not be deleted or brought offline because it is the quorum resource.[1]
0x0000139C: The cluster resource could not be deleted or brought offline because it is the quorum resource.[1]
0x8007139D: The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.[1]
0x0000139D: The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.[1]
0x8007139E: The cluster software is shutting down.[1]
0x0000139E: The cluster software is shutting down.[1]
0x8007139F: The group or resource is not in the correct state to perform the requested operation.[1]
0x0000139F: The group or resource is not in the correct state to perform the requested operation.[1]
0x800713A0: The properties were stored but not all changes will take effect until the next time the resource is brought online.[1]
0x000013A0: The properties were stored but not all changes will take effect until the next time the resource is brought online.[1]
0x800713A1: The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.[1]
0x000013A1: The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.[1]
0x800713A2: The cluster resource could not be deleted since it is a core resource.[1]
0x000013A2: The cluster resource could not be deleted since it is a core resource.[1]
0x800713A3: The quorum resource failed to come online.[1]
0x000013A3: The quorum resource failed to come online.[1]
0x800713A4: The quorum log could not be created or mounted successfully.[1]
0x000013A4: The quorum log could not be created or mounted successfully.[1]
0x800713C7: The cluster network is already online.[1]
0x000013C7: The cluster network is already online.[1]
0x800713C8: The cluster network is already offline.[1]
0x000013C8: The cluster network is already offline.[1]
0x800713C9: The cluster node is already a member of the cluster.[1]
0x000013C9: The cluster node is already a member of the cluster.[1]
0x800713CA: The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.[1]
0x000013CA: The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.[1]
0x800713CB: One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.[1]
0x000013CB: One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.[1]
0x800713CC: This operation cannot currently be performed on the cluster group containing the quorum resource.[1]
0x000013CC: This operation cannot currently be performed on the cluster group containing the quorum resource.[1]
0x800713CD: The cluster quorum resource is not allowed to have any dependencies.[1]
0x000013CD: The cluster quorum resource is not allowed to have any dependencies.[1]
0x800713D2: The cluster join operation was aborted.[1]
0x000013D2: The cluster join operation was aborted.[1]
0x800713D3: The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet.[1]
0x000013D3: The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet.[1]
0x800713D4: This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.[1]
0x000013D4: This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.[1]
0x800713D5: The system configuration changed during the cluster join or form operation. The join or form operation was aborted.[1]
0x000013D5: The system configuration changed during the cluster join or form operation. The join or form operation was aborted.[1]
0x800713D6: The specified resource type was not found.[1]
0x000013D6: The specified resource type was not found.[1]
0x800713D7: The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.[1]
0x000013D7: The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.[1]
0x800713D8: The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.[1]
0x000013D8: The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.[1]
0x800713D9: No authentication package could be registered with the RPC server.[1]
0x000013D9: No authentication package could be registered with the RPC server.[1]
0x800713DA: You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.[1]
0x000013DA: You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.[1]
0x800713DB: The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.[1]
0x000013DB: The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.[1]
0x800713DC: The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.[1]
0x000013DC: The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.[1]
0x800713DD: A non locker code got a request to reserve the lock for making global updates.[1]
0x000013DD: A non locker code got a request to reserve the lock for making global updates.[1]
0x800713DE: The quorum disk could not be located by the cluster service.[1]
0x000013DE: The quorum disk could not be located by the cluster service.[1]
0x800713DF: The backed up cluster database is possibly corrupt.[1]
0x000013DF: The backed up cluster database is possibly corrupt.[1]
0x800713E0: A DFS root already exists in this cluster node.[1]
0x000013E0: A DFS root already exists in this cluster node.[1]
0x800713E1: An attempt to modify a resource property failed because it conflicts with another existing property.[1]
0x000013E1: An attempt to modify a resource property failed because it conflicts with another existing property.[1]
0x800713E2: This operation is not supported on a cluster without an Administrator Access Point.[1]
0x000013E2: This operation is not supported on a cluster without an Administrator Access Point.[1]
0x80071702: An operation was attempted that is incompatible with the current membership state of the node.[1]
0x00001702: An operation was attempted that is incompatible with the current membership state of the node.[1]
0x80071703: The quorum resource does not contain the quorum log.[1]
0x00001703: The quorum resource does not contain the quorum log.[1]
0x80071704: The membership engine requested shutdown of the cluster service on this node.[1]
0x00001704: The membership engine requested shutdown of the cluster service on this node.[1]
0x80071705: The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.[1]
0x00001705: The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.[1]
0x80071706: A matching cluster network for the specified IP address could not be found.[1]
0x00001706: A matching cluster network for the specified IP address could not be found.[1]
0x80071707: The actual data type of the property did not match the expected data type of the property.[1]
0x00001707: The actual data type of the property did not match the expected data type of the property.[1]
0x80071708: The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.[1]
0x00001708: The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.[1]
0x80071709: Two or more parameter values specified for a resource's properties are in conflict.[1]
0x00001709: Two or more parameter values specified for a resource's properties are in conflict.[1]
0x8007170A: This computer cannot be made a member of a cluster.[1]
0x0000170A: This computer cannot be made a member of a cluster.[1]
0x8007170B: This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.[1]
0x0000170B: This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.[1]
0x8007170C: A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.[1]
0x0000170C: A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.[1]
0x8007170D: The cluster configuration action has already been committed.[1]
0x0000170D: The cluster configuration action has already been committed.[1]
0x8007170E: The cluster configuration action could not be rolled back.[1]
0x0000170E: The cluster configuration action could not be rolled back.[1]
0x8007170F: The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.[1]
0x0000170F: The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.[1]
0x80071710: One or more nodes in the cluster are running a version of Windows that does not support this operation.[1]
0x00001710: One or more nodes in the cluster are running a version of Windows that does not support this operation.[1]
0x80071711: The name of the corresponding computer account doesn't match the Network Name for this resource.[1]
0x00001711: The name of the corresponding computer account doesn't match the Network Name for this resource.[1]
0x80071714: The group is unable to accept the request since it is moving to another node.[1]
0x00001714: The group is unable to accept the request since it is moving to another node.[1]
0x80071715: The resource type cannot accept the request since is too busy performing another operation.[1]
0x00001715: The resource type cannot accept the request since is too busy performing another operation.[1]
0x80071716: The call to the cluster resource DLL timed out.[1]
0x00001716: The call to the cluster resource DLL timed out.[1]
0x80071717: The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.[1]
0x00001717: The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.[1]
0x80071718: An internal cluster error occurred. A call to an invalid function was attempted.[1]
0x00001718: An internal cluster error occurred. A call to an invalid function was attempted.[1]
0x80071719: A parameter value is out of acceptable range.[1]
0x00001719: A parameter value is out of acceptable range.[1]
0x8007171A: A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.[1]
0x0000171A: A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.[1]
0x8007171B: An invalid cluster registry operation was attempted.[1]
0x0000171B: An invalid cluster registry operation was attempted.[1]
0x8007171C: An input string of characters is not properly terminated.[1]
0x0000171C: An input string of characters is not properly terminated.[1]
0x8007171D: An input string of characters is not in a valid format for the data it represents.[1]
0x0000171D: An input string of characters is not in a valid format for the data it represents.[1]
0x8007171E: An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.[1]
0x0000171E: An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.[1]
0x8007171F: An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.[1]
0x0000171F: An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.[1]
0x80071720: An internal cluster error occurred. Data was not properly initialized.[1]
0x00001720: An internal cluster error occurred. Data was not properly initialized.[1]
0x80071721: An error occurred while reading from a stream of data. An unexpected number of bytes was returned.[1]
0x00001721: An error occurred while reading from a stream of data. An unexpected number of bytes was returned.[1]
0x80071722: An error occurred while writing to a stream of data. The required number of bytes could not be written.[1]
0x00001722: An error occurred while writing to a stream of data. The required number of bytes could not be written.[1]
0x80071723: An error occurred while deserializing a stream of cluster data.[1]
0x00001723: An error occurred while deserializing a stream of cluster data.[1]
0x80071724: One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).[1]
0x00001724: One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).[1]
0x80071725: A quorum of cluster nodes was not present to form a cluster.[1]
0x00001725: A quorum of cluster nodes was not present to form a cluster.[1]
0x80071726: The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.[1]
0x00001726: The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.[1]
0x80071727: The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.[1]
0x00001727: The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.[1]
0x80071728: Quorum resource cannot reside in the Available Storage group.[1]
0x00001728: Quorum resource cannot reside in the Available Storage group.[1]
0x80071729: The dependencies for this resource are nested too deeply.[1]
0x00001729: The dependencies for this resource are nested too deeply.[1]
0x8007172A: The call into the resource DLL raised an unhandled exception.[1]
0x0000172A: The call into the resource DLL raised an unhandled exception.[1]
0x8007172B: The RHS process failed to initialize.[1]
0x0000172B: The RHS process failed to initialize.[1]
0x8007172C: The Failover Clustering feature is not installed on this node.[1]
0x0000172C: The Failover Clustering feature is not installed on this node.[1]
0x8007172D: The resources must be online on the same node for this operation[1]
0x0000172D: The resources must be online on the same node for this operation[1]
0x8007172E: A new node can not be added since this cluster is already at its maximum number of nodes.[1]
0x0000172E: A new node can not be added since this cluster is already at its maximum number of nodes.[1]
0x8007172F: This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit.[1]
0x0000172F: This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit.[1]
0x80071730: An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain.[1]
0x00001730: An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain.[1]
0x80071731: This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed.[1]
0x00001731: This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed.[1]
0x80071732: File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes.[1]
0x00001732: File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes.[1]
0x80071733: If it is the last node in the cluster, destroy cluster command should be used.[1]
0x00001733: If it is the last node in the cluster, destroy cluster command should be used.[1]
0x80071734: Only one instance of this resource type is allowed in the cluster.[1]
0x00001734: Only one instance of this resource type is allowed in the cluster.[1]
0x80071735: Only one instance of this resource type is allowed per resource group.[1]
0x00001735: Only one instance of this resource type is allowed per resource group.[1]
0x80071736: The resource failed to come online due to the failure of one or more provider resources.[1]
0x00001736: The resource failed to come online due to the failure of one or more provider resources.[1]
0x80071737: The resource has indicated that it cannot come online on any node.[1]
0x00001737: The resource has indicated that it cannot come online on any node.[1]
0x80071738: The current operation cannot be performed on this group at this time.[1]
0x00001738: The current operation cannot be performed on this group at this time.[1]
0x80071739: The directory or file is not located on a cluster shared volume.[1]
0x00001739: The directory or file is not located on a cluster shared volume.[1]
0x8007173A: The Security Descriptor does not meet the requirements for a cluster.[1]
0x0000173A: The Security Descriptor does not meet the requirements for a cluster.[1]
0x8007173B: Those resources must be moved to available storage in order for operation to succeed.[1]
0x0000173B: Those resources must be moved to available storage in order for operation to succeed.[1]
0x8007173C: Use shared volume APIs to perform desired operation.[1]
0x0000173C: Use shared volume APIs to perform desired operation.[1]
0x8007173D: Back up is in progress. Please wait for backup completion before trying this operation again.[1]
0x0000173D: Back up is in progress. Please wait for backup completion before trying this operation again.[1]
0x8007173E: The path does not belong to a cluster shared volume.[1]
0x0000173E: The path does not belong to a cluster shared volume.[1]
0x8007173F: The cluster shared volume is not locally mounted on this node.[1]
0x0000173F: The cluster shared volume is not locally mounted on this node.[1]
0x80071741: A resource vetoed a move between two nodes because they are incompatible.[1]
0x00001741: A resource vetoed a move between two nodes because they are incompatible.[1]
0x80071742: The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements.[1]
0x00001742: The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements.[1]
0x8007174B: Clustered storage is not connected to the node.[1]
0x0000174B: Clustered storage is not connected to the node.[1]
0x8007174C: The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS.[1]
0x0000174C: The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS.[1]
0x8007174D: The resource must be part of the Available Storage group to complete this action.[1]
0x0000174D: The resource must be part of the Available Storage group to complete this action.[1]
0x8007174E: CSVFS failed operation as volume is in redirected mode.[1]
0x0000174E: CSVFS failed operation as volume is in redirected mode.[1]
0x8007174F: CSVFS failed operation as volume is not in redirected mode.[1]
0x0000174F: CSVFS failed operation as volume is not in redirected mode.[1]
0x80071750: Cluster properties cannot be returned at this time.[1]
0x00001750: Cluster properties cannot be returned at this time.[1]
0x80071751: The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes.[1]
0x00001751: The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes.[1]
0x80071752: The operation cannot be completed because the resource is in maintenance mode.[1]
0x00001752: The operation cannot be completed because the resource is in maintenance mode.[1]
0x80071753: The operation cannot be completed because of cluster affinity conflicts[1]
0x00001753: The operation cannot be completed because of cluster affinity conflicts[1]
0x80071754: The operation cannot be completed because the resource is a replica virtual machine.[1]
0x00001754: The operation cannot be completed because the resource is a replica virtual machine.[1]
0x80071755: The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version.[1]
0x00001755: The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version.[1]
0x80071756: of fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level.[1]
0x00001756: of fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level.[1]
0x800719F6: Security on the log and its containers is inconsistent.[1]
0x000019F6: Security on the log and its containers is inconsistent.[1]
0x800719F7: Records were appended to the log or reservation changes were made, but the log could not be flushed.[1]
0x000019F7: Records were appended to the log or reservation changes were made, but the log could not be flushed.[1]
0x800719F8: The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.[1]
0x000019F8: The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.[1]
0x80071A2C: The transaction handle associated with this operation is not valid.[1]
0x00001A2C: The transaction handle associated with this operation is not valid.[1]
0x80071A2D: The requested operation was made in the context of a transaction that is no longer active.[1]
0x00001A2D: The requested operation was made in the context of a transaction that is no longer active.[1]
0x80071A2E: The requested operation is not valid on the Transaction object in its current state.[1]
0x00001A2E: The requested operation is not valid on the Transaction object in its current state.[1]
0x80071A2F: The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.[1]
0x00001A2F: The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.[1]
0x80071A30: It is too late to perform the requested operation, since the Transaction has already been aborted.[1]
0x00001A30: It is too late to perform the requested operation, since the Transaction has already been aborted.[1]
0x80071A31: It is too late to perform the requested operation, since the Transaction has already been committed.[1]
0x00001A31: It is too late to perform the requested operation, since the Transaction has already been committed.[1]
0x80071A32: The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.[1]
0x00001A32: The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.[1]
0x80071A33: The specified ResourceManager made no changes or updates to the resource under this transaction.[1]
0x00001A33: The specified ResourceManager made no changes or updates to the resource under this transaction.[1]
0x80071A34: The resource manager has attempted to prepare a transaction that it has not successfully joined.[1]
0x00001A34: The resource manager has attempted to prepare a transaction that it has not successfully joined.[1]
0x80071A35: 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 allow.[1]
0x00001A35: 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 allow.[1]
0x80071A36: The RM tried to register a protocol that already exists.[1]
0x00001A36: The RM tried to register a protocol that already exists.[1]
0x80071A37: The attempt to propagate the Transaction failed.[1]
0x00001A37: The attempt to propagate the Transaction failed.[1]
0x80071A38: The requested propagation protocol was not registered as a CRM.[1]
0x00001A38: The requested propagation protocol was not registered as a CRM.[1]
0x80071A39: The buffer passed in to PushTransaction or PullTransaction is not in a valid format.[1]
0x00001A39: The buffer passed in to PushTransaction or PullTransaction is not in a valid format.[1]
0x80071A3A: The current transaction context associated with the thread is not a valid handle to a transaction object.[1]
0x00001A3A: The current transaction context associated with the thread is not a valid handle to a transaction object.[1]
0x80071A3B: The specified Transaction object could not be opened, because it was not found.[1]
0x00001A3B: The specified Transaction object could not be opened, because it was not found.[1]
0x80071A3C: The specified ResourceManager object could not be opened, because it was not found.[1]
0x00001A3C: The specified ResourceManager object could not be opened, because it was not found.[1]
0x80071A3D: The specified Enlistment object could not be opened, because it was not found.[1]
0x00001A3D: The specified Enlistment object could not be opened, because it was not found.[1]
0x80071A3E: The specified TransactionManager object could not be opened, because it was not found.[1]
0x00001A3E: The specified TransactionManager object could not be opened, because it was not found.[1]
0x80071A3F: The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.[1]
0x00001A3F: The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.[1]
0x80071A40: The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.[1]
0x00001A40: The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.[1]
0x80071A41: 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 on as a superior.[1]
0x00001A41: 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 on as a superior.[1]
0x80071A42: Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.[1]
0x00001A42: Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.[1]
0x80071A43: 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.[1]
0x00001A43: 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.[1]
0x80071A44: The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.[1]
0x00001A44: The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.[1]
0x80071A45: Implicit transaction are not supported.[1]
0x00001A45: Implicit transaction are not supported.[1]
0x80071A46: The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.[1]
0x00001A46: The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.[1]
0x80071A47: The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.[1]
0x00001A47: The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.[1]
0x80071A48: This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.[1]
0x00001A48: This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.[1]
0x80071A49: The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.[1]
0x00001A49: The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.[1]
0x80071A4A: The transaction does not have a superior enlistment.[1]
0x00001A4A: The transaction does not have a superior enlistment.[1]
0x80071A4B: The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.[1]
0x00001A4B: The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.[1]
0x80071A90: The function attempted to use a name that is reserved for use by another transaction.[1]
0x00001A90: The function attempted to use a name that is reserved for use by another transaction.[1]
0x80071A91: Transaction support within the specified resource manager is not started or was shut down due to an error.[1]
0x00001A91: Transaction support within the specified resource manager is not started or was shut down due to an error.[1]
0x80071A92: The metadata of the RM has been corrupted. The RM will not function.[1]
0x00001A92: The metadata of the RM has been corrupted. The RM will not function.[1]
0x80071A93: The specified directory does not contain a resource manager.[1]
0x00001A93: The specified directory does not contain a resource manager.[1]
0x80071A95: The remote server or share does not support transacted file operations.[1]
0x00001A95: The remote server or share does not support transacted file operations.[1]
0x80071A97: The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.[1]
0x00001A97: The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.[1]
0x80071A98: The specified file miniversion was not found for this transacted file open.[1]
0x00001A98: The specified file miniversion was not found for this transacted file open.[1]
0x80071A99: The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.[1]
0x00001A99: The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.[1]
0x80071A9A: A miniversion may only be opened in the context of the transaction that created it.[1]
0x00001A9A: A miniversion may only be opened in the context of the transaction that created it.[1]
0x80071A9B: It is not possible to open a miniversion with modify access.[1]
0x00001A9B: It is not possible to open a miniversion with modify access.[1]
0x80071A9C: It is not possible to create any more miniversions for this stream.[1]
0x00001A9C: It is not possible to create any more miniversions for this stream.[1]
0x80071A9E: The remote server sent mismatching version number or Fid for a file opened with transactions.[1]
0x00001A9E: The remote server sent mismatching version number or Fid for a file opened with transactions.[1]
0x80071A9F: 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.[1]
0x00001A9F: 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.[1]
0x80071AA0: There is no transaction metadata on the file.[1]
0x00001AA0: There is no transaction metadata on the file.[1]
0x80071AA2: The file can't be recovered because there is a handle still open on it.[1]
0x00001AA2: The file can't be recovered because there is a handle still open on it.[1]
0x80071AA3: The transaction outcome is unavailable because the resource manager responsible for it has disconnected.[1]
0x00001AA3: The transaction outcome is unavailable because the resource manager responsible for it has disconnected.[1]
0x80071AA4: The request was rejected because the enlistment in question is not a superior enlistment.[1]
0x00001AA4: The request was rejected because the enlistment in question is not a superior enlistment.[1]
0x80071AA5: The transactional resource manager is already consistent. Recovery is not needed.[1]
0x00001AA5: The transactional resource manager is already consistent. Recovery is not needed.[1]
0x80071AA6: The transactional resource manager has already been started.[1]
0x00001AA6: The transactional resource manager has already been started.[1]
0x80071AA7: The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.[1]
0x00001AA7: The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.[1]
0x80071AA8: The operation cannot be performed because another transaction is depending on the fact that this property will not change.[1]
0x00001AA8: The operation cannot be performed because another transaction is depending on the fact that this property will not change.[1]
0x80071AA9: The operation would involve a single file with two transactional resource managers and is therefore not allowed.[1]
0x00001AA9: The operation would involve a single file with two transactional resource managers and is therefore not allowed.[1]
0x80071AAA: The $Txf directory must be empty for this operation to succeed.[1]
0x00001AAA: The $Txf directory must be empty for this operation to succeed.[1]
0x80071AAB: The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.[1]
0x00001AAB: The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.[1]
0x80071AAC: The operation could not be completed because the transaction manager does not have a log.[1]
0x00001AAC: The operation could not be completed because the transaction manager does not have a log.[1]
0x80071AAD: A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.[1]
0x00001AAD: A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.[1]
0x80071AAE: The transactional metadata attribute on the file or directory is corrupt and unreadable.[1]
0x00001AAE: The transactional metadata attribute on the file or directory is corrupt and unreadable.[1]
0x80071AAF: The encryption operation could not be completed because a transaction is active.[1]
0x00001AAF: The encryption operation could not be completed because a transaction is active.[1]
0x80071AB0: This object is not allowed to be opened in a transaction.[1]
0x00001AB0: This object is not allowed to be opened in a transaction.[1]
0x80071AB1: An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.[1]
0x00001AB1: An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.[1]
0x80071AB2: Memory mapping (creating a mapped section) a remote file under a transaction is not supported.[1]
0x00001AB2: Memory mapping (creating a mapped section) a remote file under a transaction is not supported.[1]
0x80071AB3: Transaction metadata is already present on this file and cannot be superseded.[1]
0x00001AB3: Transaction metadata is already present on this file and cannot be superseded.[1]
0x80071AB4: A transaction scope could not be entered because the scope handler has not been initialized.[1]
0x00001AB4: A transaction scope could not be entered because the scope handler has not been initialized.[1]
0x80071AB5: Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.[1]
0x00001AB5: Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.[1]
0x80071AB6: This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.[1]
0x00001AB6: This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.[1]
0x80071AB7: The request to thaw frozen transactions was ignored because transactions had not previously been frozen.[1]
0x00001AB7: The request to thaw frozen transactions was ignored because transactions had not previously been frozen.[1]
0x80071AB8: Transactions cannot be frozen because a freeze is already in progress.[1]
0x00001AB8: Transactions cannot be frozen because a freeze is already in progress.[1]
0x80071AB9: The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.[1]
0x00001AB9: The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.[1]
0x80071ABA: The savepoint operation failed because files are open on the transaction. This is not permitted.[1]
0x00001ABA: The savepoint operation failed because files are open on the transaction. This is not permitted.[1]
0x80071ABB: Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.[1]
0x00001ABB: Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.[1]
0x80071ABC: The sparse operation could not be completed because a transaction is active on the file.[1]
0x00001ABC: The sparse operation could not be completed because a transaction is active on the file.[1]
0x80071ABD: The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.[1]
0x00001ABD: The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.[1]
0x80071ABE: I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.[1]
0x00001ABE: I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.[1]
0x80071ABF: The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.[1]
0x00001ABF: The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.[1]
0x80071AC0: The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down.[1]
0x00001AC0: The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down.[1]
0x80071AC1: The operation could not be completed due to bad clusters on disk.[1]
0x00001AC1: The operation could not be completed due to bad clusters on disk.[1]
0x80071AC2: The compression operation could not be completed because a transaction is active on the file.[1]
0x00001AC2: The compression operation could not be completed because a transaction is active on the file.[1]
0x80071AC3: The operation could not be completed because the volume is dirty. Please run chkdsk and try again.[1]
0x00001AC3: The operation could not be completed because the volume is dirty. Please run chkdsk and try again.[1]
0x80071AC4: The link tracking operation could not be completed because a transaction is active.[1]
0x00001AC4: The link tracking operation could not be completed because a transaction is active.[1]
0x80071AC5: This operation cannot be performed in a transaction.[1]
0x00001AC5: This operation cannot be performed in a transaction.[1]
0x80071AC6: The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.[1]
0x00001AC6: The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.[1]
0x80071AC7: The specified operation could not be performed because the resource manager is not enlisted in the transaction.[1]
0x00001AC7: The specified operation could not be performed because the resource manager is not enlisted in the transaction.[1]
0x80071B59: The specified session name is invalid.[1]
0x00001B59: The specified session name is invalid.[1]
0x80071B5A: The specified protocol driver is invalid.[1]
0x00001B5A: The specified protocol driver is invalid.[1]
0x80071B5B: The specified protocol driver was not found in the system path.[1]
0x00001B5B: The specified protocol driver was not found in the system path.[1]
0x80071B5C: The specified terminal connection driver was not found in the system path.[1]
0x00001B5C: The specified terminal connection driver was not found in the system path.[1]
0x80071B5D: A registry key for event logging could not be created for this session.[1]
0x00001B5D: A registry key for event logging could not be created for this session.[1]
0x80071B5E: A service with the same name already exists on the system.[1]
0x00001B5E: A service with the same name already exists on the system.[1]
0x80071B5F: A close operation is pending on the session.[1]
0x00001B5F: A close operation is pending on the session.[1]
0x80071B60: There are no free output buffers available.[1]
0x00001B60: There are no free output buffers available.[1]
0x80071B6E: The specified session cannot be found.[1]
0x00001B6E: The specified session cannot be found.[1]
0x80071B6F: The specified session name is already in use.[1]
0x00001B6F: The specified session name is already in use.[1]
0x80071B70: The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.[1]
0x00001B70: The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.[1]
0x80071B71: An attempt has been made to connect to a session whose video mode is not supported by the current client.[1]
0x00001B71: An attempt has been made to connect to a session whose video mode is not supported by the current client.[1]
0x80071B7B: The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.[1]
0x00001B7B: The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.[1]
0x80071B7D: Your interactive logon privilege has been disabled. Please contact your administrator.[1]
0x00001B7D: Your interactive logon privilege has been disabled. Please contact your administrator.[1]
0x80071B7E: 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.[1]
0x00001B7E: 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.[1]
0x80071B80: The client failed to respond to the server connect message.[1]
0x00001B80: The client failed to respond to the server connect message.[1]
0x80071B81: Disconnecting the console session is not supported.[1]
0x00001B81: Disconnecting the console session is not supported.[1]
0x80071B82: Reconnecting a disconnected session to the console is not supported.[1]
0x00001B82: Reconnecting a disconnected session to the console is not supported.[1]
0x80071B84: The request to control another session remotely was denied.[1]
0x00001B84: The request to control another session remotely was denied.[1]
0x80071B85: The requested session access is denied.[1]
0x00001B85: The requested session access is denied.[1]
0x80071B89: The specified terminal connection driver is invalid.[1]
0x00001B89: The specified terminal connection driver is invalid.[1]
0x80071B8A: This may be because the session is disconnected or does not currently have a user logged on.[1]
0x00001B8A: This may be because the session is disconnected or does not currently have a user logged on.[1]
0x80071B8B: The requested session is not configured to allow remote control.[1]
0x00001B8B: The requested session is not configured to allow remote control.[1]
0x80071B8C: Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.[1]
0x00001B8C: Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.[1]
0x80071B8D: 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 Server client. Please contact your system administrator.[1]
0x00001B8D: 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 Server client. Please contact your system administrator.[1]
0x80071B8E: The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.[1]
0x00001B8E: The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.[1]
0x80071B8F: The client you are using is not licensed to use this system. Your logon request is denied.[1]
0x00001B8F: The client you are using is not licensed to use this system. Your logon request is denied.[1]
0x80071B90: The system license has expired. Your logon request is denied.[1]
0x00001B90: The system license has expired. Your logon request is denied.[1]
0x80071B91: Remote control could not be terminated because the specified session is not currently being remotely controlled.[1]
0x00001B91: Remote control could not be terminated because the specified session is not currently being remotely controlled.[1]
0x80071B92: 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.[1]
0x00001B92: 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.[1]
0x80071B93: Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.[1]
0x00001B93: Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.[1]
0x80071B94: Remote logins are currently disabled.[1]
0x00001B94: Remote logins are currently disabled.[1]
0x80071B95: You do not have the proper encryption level to access this Session.[1]
0x00001B95: You do not have the proper encryption level to access this Session.[1]
0x80071B96: The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.[1]
0x00001B96: The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.[1]
0x80071B97: The user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\%s and have them log off.[1]
0x00001B97: The user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\%s and have them log off.[1]
0x80071B98: Unable to log you on because of an account restriction.[1]
0x00001B98: Unable to log you on because of an account restriction.[1]
0x80071B99: The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.[1]
0x00001B99: The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.[1]
0x80071B9A: The Client Drive Mapping Service Has Connected on Terminal Connection.[1]
0x00001B9A: The Client Drive Mapping Service Has Connected on Terminal Connection.[1]
0x80071B9B: The Client Drive Mapping Service Has Disconnected on Terminal Connection.[1]
0x00001B9B: The Client Drive Mapping Service Has Disconnected on Terminal Connection.[1]
0x80071B9C: The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.[1]
0x00001B9C: The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.[1]
0x80071B9D: The target session is incompatible with the current session.[1]
0x00001B9D: The target session is incompatible with the current session.[1]
0x80071B9E: Windows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance.[1]
0x00001B9E: Windows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance.[1]
0x80072008: An error occurred while installing the directory service. For more information, see the event log.[1]
0x00002008: An error occurred while installing the directory service. For more information, see the event log.[1]
0x80072009: The directory service evaluated group memberships locally.[1]
0x00002009: The directory service evaluated group memberships locally.[1]
0x8007200A: The specified directory service attribute or value does not exist.[1]
0x0000200A: The specified directory service attribute or value does not exist.[1]
0x8007200B: The attribute syntax specified to the directory service is invalid.[1]
0x0000200B: The attribute syntax specified to the directory service is invalid.[1]
0x8007200C: The attribute type specified to the directory service is not defined.[1]
0x0000200C: The attribute type specified to the directory service is not defined.[1]
0x8007200D: The specified directory service attribute or value already exists.[1]
0x0000200D: The specified directory service attribute or value already exists.[1]
0x80072046: The search results exceed the offset range specified.[1]
0x00002046: The search results exceed the offset range specified.[1]
0x80072047: The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation.[1]
0x00002047: The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation.[1]
0x8007206D: The root object must be the head of a naming context. The root object cannot have an instantiated parent.[1]
0x0000206D: The root object must be the head of a naming context. The root object cannot have an instantiated parent.[1]
0x8007206E: The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.[1]
0x0000206E: The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.[1]
0x8007206F: A reference to an attribute that is not defined in the schema occurred.[1]
0x0000206F: A reference to an attribute that is not defined in the schema occurred.[1]
0x80072070: The maximum size of an object has been exceeded.[1]
0x00002070: The maximum size of an object has been exceeded.[1]
0x80072071: An attempt was made to add an object to the directory with a name that is already in use.[1]
0x00002071: An attempt was made to add an object to the directory with a name that is already in use.[1]
0x80072072: An attempt was made to add an object of a class that does not have an RDN defined in the schema.[1]
0x00002072: An attempt was made to add an object of a class that does not have an RDN defined in the schema.[1]
0x80072073: An attempt was made to add an object using an RDN that is not the RDN defined in the schema.[1]
0x00002073: An attempt was made to add an object using an RDN that is not the RDN defined in the schema.[1]
0x80072074: None of the requested attributes were found on the objects.[1]
0x00002074: None of the requested attributes were found on the objects.[1]
0x800720D3: The attribute could not be removed from the cache.[1]
0x000020D3: The attribute could not be removed from the cache.[1]
0x800720D4: The class could not be removed from the cache.[1]
0x000020D4: The class could not be removed from the cache.[1]
0x800720D5: The distinguished name attribute could not be read.[1]
0x000020D5: The distinguished name attribute could not be read.[1]
0x800720D6: No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest.[1]
0x000020D6: No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest.[1]
0x800720D7: The instance type attribute could not be retrieved.[1]
0x000020D7: The instance type attribute could not be retrieved.[1]
0x800720DF: Schema allocation failed. Please check if the machine is running low on memory.[1]
0x000020DF: Schema allocation failed. Please check if the machine is running low on memory.[1]
0x800720E0: Failed to obtain the required syntax for the attribute schema.[1]
0x000020E0: Failed to obtain the required syntax for the attribute schema.[1]
0x800720E1: The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.[1]
0x000020E1: The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.[1]
0x800720E2: The replication operation failed because of a schema mismatch between the servers involved.[1]
0x000020E2: The replication operation failed because of a schema mismatch between the servers involved.[1]
0x800720EA: The attempt to build the hierarchy table failed.[1]
0x000020EA: The attempt to build the hierarchy table failed.[1]
0x800720EB: The directory configuration parameter is missing from the registry.[1]
0x000020EB: The directory configuration parameter is missing from the registry.[1]
0x800720EC: The attempt to count the address book indices failed.[1]
0x000020EC: The attempt to count the address book indices failed.[1]
0x800720ED: The allocation of the hierarchy table failed.[1]
0x000020ED: The allocation of the hierarchy table failed.[1]
0x800720EE: The directory service encountered an internal failure.[1]
0x000020EE: The directory service encountered an internal failure.[1]
0x800720EF: The directory service encountered an unknown failure.[1]
0x000020EF: The directory service encountered an unknown failure.[1]
0x800720F0: A root object requires a class of 'top'.[1]
0x000020F0: A root object requires a class of 'top'.[1]
0x800720F1: This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.[1]
0x000020F1: This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.[1]
0x800720F2: The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.[1]
0x000020F2: The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.[1]
0x800720F3: The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.[1]
0x000020F3: The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.[1]
0x80072106: The requested operation is not supported by this version of the directory service.[1]
0x00002106: The requested operation is not supported by this version of the directory service.[1]
0x80072107: The replication remote procedure call was cancelled.[1]
0x00002107: The replication remote procedure call was cancelled.[1]
0x80072108: The source server is currently rejecting replication requests.[1]
0x00002108: The source server is currently rejecting replication requests.[1]
0x80072109: The destination server is currently rejecting replication requests.[1]
0x00002109: The destination server is currently rejecting replication requests.[1]
0x8007210A: The replication operation failed due to a collision of object names.[1]
0x0000210A: The replication operation failed due to a collision of object names.[1]
0x8007210B: The replication source has been reinstalled.[1]
0x0000210B: The replication source has been reinstalled.[1]
0x8007210C: The replication operation failed because a required parent object is missing.[1]
0x0000210C: The replication operation failed because a required parent object is missing.[1]
0x8007210D: The replication operation was preempted.[1]
0x0000210D: The replication operation was preempted.[1]
0x8007210E: The replication synchronization attempt was abandoned because of a lack of updates.[1]
0x0000210E: The replication synchronization attempt was abandoned because of a lack of updates.[1]
0x8007210F: The replication operation was terminated because the system is shutting down.[1]
0x0000210F: The replication operation was terminated because the system is shutting down.[1]
0x80072110: Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.[1]
0x00002110: Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.[1]
0x80072111: The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.[1]
0x00002111: The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.[1]
0x80072112: The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.[1]
0x00002112: The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.[1]
0x80072113: The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.[1]
0x00002113: The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.[1]
0x80072114: Schema update failed: An attribute with the same link identifier already exists.[1]
0x00002114: Schema update failed: An attribute with the same link identifier already exists.[1]
0x80072115: Name translation: Generic processing error.[1]
0x00002115: Name translation: Generic processing error.[1]
0x80072116: Name translation: Could not find the name or insufficient right to see name.[1]
0x00002116: Name translation: Could not find the name or insufficient right to see name.[1]
0x80072117: Name translation: Input name mapped to more than one output name.[1]
0x00002117: Name translation: Input name mapped to more than one output name.[1]
0x80072118: Name translation: Input name found, but not the associated output format.[1]
0x00002118: Name translation: Input name found, but not the associated output format.[1]
0x80072119: Name translation: Unable to resolve completely, only the domain was found.[1]
0x00002119: Name translation: Unable to resolve completely, only the domain was found.[1]
0x8007211A: Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.[1]
0x0000211A: Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.[1]
0x8007211B: Modification of a constructed attribute is not allowed.[1]
0x0000211B: Modification of a constructed attribute is not allowed.[1]
0x8007211C: The OM-Object-Class specified is incorrect for an attribute with the specified syntax.[1]
0x0000211C: The OM-Object-Class specified is incorrect for an attribute with the specified syntax.[1]
0x8007211D: The replication request has been posted; waiting for reply.[1]
0x0000211D: The replication request has been posted; waiting for reply.[1]
0x8007211E: The requested operation requires a directory service, and none was available.[1]
0x0000211E: The requested operation requires a directory service, and none was available.[1]
0x8007211F: The LDAP display name of the class or attribute contains non-ASCII characters.[1]
0x0000211F: The LDAP display name of the class or attribute contains non-ASCII characters.[1]
0x80072120: The requested search operation is only supported for base searches.[1]
0x00002120: The requested search operation is only supported for base searches.[1]
0x80072121: The search failed to retrieve attributes from the database.[1]
0x00002121: The search failed to retrieve attributes from the database.[1]
0x80072122: The schema update operation tried to add a backward link attribute that has no corresponding forward link.[1]
0x00002122: The schema update operation tried to add a backward link attribute that has no corresponding forward link.[1]
0x80072123: Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.[1]
0x00002123: Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.[1]
0x80072124: Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.[1]
0x00002124: Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.[1]
0x80072125: Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.[1]
0x00002125: Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.[1]
0x80072126: Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.[1]
0x00002126: Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.[1]
0x80072127: Destination of a cross-domain move is not authoritative for the destination naming context.[1]
0x00002127: Destination of a cross-domain move is not authoritative for the destination naming context.[1]
0x80072128: Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.[1]
0x00002128: Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.[1]
0x80072129: Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.[1]
0x00002129: Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.[1]
0x8007212A: Another operation which requires exclusive access to the PDC FSMO is already in progress.[1]
0x0000212A: Another operation which requires exclusive access to the PDC FSMO is already in progress.[1]
0x8007212B: A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.[1]
0x0000212B: A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.[1]
0x8007212C: This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move.[1]
0x0000212C: This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move.[1]
0x8007212D: Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.[1]
0x0000212D: Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.[1]
0x8007212E: A naming context head must be the immediate child of another naming context head, not of an interior node.[1]
0x0000212E: A naming context head must be the immediate child of another naming context head, not of an interior node.[1]
0x8007212F: The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)[1]
0x0000212F: The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)[1]
0x80072130: Destination domain must be in native mode.[1]
0x00002130: Destination domain must be in native mode.[1]
0x80072131: The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.[1]
0x00002131: The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.[1]
0x80072132: Cross-domain move of non-empty account groups is not allowed.[1]
0x00002132: Cross-domain move of non-empty account groups is not allowed.[1]
0x80072133: Cross-domain move of non-empty resource groups is not allowed.[1]
0x00002133: Cross-domain move of non-empty resource groups is not allowed.[1]
0x80072134: The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.[1]
0x00002134: The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.[1]
0x80072135: Tree deletions starting at an object which has an NC head as a descendant are not allowed.[1]
0x00002135: Tree deletions starting at an object which has an NC head as a descendant are not allowed.[1]
0x80072136: The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.[1]
0x00002136: The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.[1]
0x80072137: The directory service failed to identify the list of objects to delete while attempting a tree deletion.[1]
0x00002137: The directory service failed to identify the list of objects to delete while attempting a tree deletion.[1]
0x80072138: Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.[1]
0x00002138: Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.[1]
0x80072139: Only an administrator can modify the membership list of an administrative group.[1]
0x00002139: Only an administrator can modify the membership list of an administrative group.[1]
0x8007213A: Cannot change the primary group ID of a domain controller account.[1]
0x0000213A: Cannot change the primary group ID of a domain controller account.[1]
0x8007213B: An attempt is made to modify the base schema.[1]
0x0000213B: An attempt is made to modify the base schema.[1]
0x8007213C: Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.[1]
0x0000213C: Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.[1]
0x8007213D: Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.[1]
0x0000213D: Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.[1]
0x8007213E: An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.[1]
0x0000213E: An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.[1]
0x8007213F: The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.[1]
0x0000213F: The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.[1]
0x80072140: The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.[1]
0x00002140: The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.[1]
0x80072142: You cannot nest global groups in a mixed domain if the group is security-enabled.[1]
0x00002142: You cannot nest global groups in a mixed domain if the group is security-enabled.[1]
0x80072143: You cannot nest local groups in a mixed domain if the group is security-enabled.[1]
0x00002143: You cannot nest local groups in a mixed domain if the group is security-enabled.[1]
0x80072144: A global group cannot have a local group as a member.[1]
0x00002144: A global group cannot have a local group as a member.[1]
0x80072145: A global group cannot have a universal group as a member.[1]
0x00002145: A global group cannot have a universal group as a member.[1]
0x80072146: A universal group cannot have a local group as a member.[1]
0x00002146: A universal group cannot have a local group as a member.[1]
0x80072147: A global group cannot have a cross-domain member.[1]
0x00002147: A global group cannot have a cross-domain member.[1]
0x80072148: A local group cannot have another cross domain local group as a member.[1]
0x00002148: A local group cannot have another cross domain local group as a member.[1]
0x80072149: A group with primary members cannot change to a security-disabled group.[1]
0x00002149: A group with primary members cannot change to a security-disabled group.[1]
0x8007214A: The schema cache load failed to convert the string default SD on a class-schema object.[1]
0x0000214A: The schema cache load failed to convert the string default SD on a class-schema object.[1]
0x8007214B: Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)[1]
0x0000214B: Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)[1]
0x8007214C: The DSA operation is unable to proceed because of a DNS lookup failure.[1]
0x0000214C: The DSA operation is unable to proceed because of a DNS lookup failure.[1]
0x8007214D: While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.[1]
0x0000214D: While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.[1]
0x8007214E: The Security Descriptor attribute could not be read.[1]
0x0000214E: The Security Descriptor attribute could not be read.[1]
0x8007214F: The object requested was not found, but an object with that key was found.[1]
0x0000214F: The object requested was not found, but an object with that key was found.[1]
0x80072150: The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1[1]
0x00002150: The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1[1]
0x80072151: Security Account Manager needs to get the boot password.[1]
0x00002151: Security Account Manager needs to get the boot password.[1]
0x80072152: Security Account Manager needs to get the boot key from floppy disk.[1]
0x00002152: Security Account Manager needs to get the boot key from floppy disk.[1]
0x80072155: The connection between client and server requires packet privacy or better.[1]
0x00002155: The connection between client and server requires packet privacy or better.[1]
0x80072156: The source domain may not be in the same forest as destination.[1]
0x00002156: The source domain may not be in the same forest as destination.[1]
0x80072157: The destination domain must be in the forest.[1]
0x00002157: The destination domain must be in the forest.[1]
0x80072158: The operation requires that destination domain auditing be enabled.[1]
0x00002158: The operation requires that destination domain auditing be enabled.[1]
0x80072159: The operation couldn't locate a DC for the source domain.[1]
0x00002159: The operation couldn't locate a DC for the source domain.[1]
0x8007215A: The source object must be a group or user.[1]
0x0000215A: The source object must be a group or user.[1]
0x8007215B: The source object's SID already exists in destination forest.[1]
0x0000215B: The source object's SID already exists in destination forest.[1]
0x8007215C: The source and destination object must be of the same type.[1]
0x0000215C: The source and destination object must be of the same type.[1]
0x8007215D: Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.[1]
0x0000215D: Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information.[1]
0x8007215E: Schema information could not be included in the replication request.[1]
0x0000215E: Schema information could not be included in the replication request.[1]
0x8007215F: The replication operation could not be completed due to a schema incompatibility.[1]
0x0000215F: The replication operation could not be completed due to a schema incompatibility.[1]
0x80072160: The replication operation could not be completed due to a previous schema incompatibility.[1]
0x00002160: The replication operation could not be completed due to a previous schema incompatibility.[1]
0x80072161: The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.[1]
0x00002161: The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.[1]
0x80072162: The requested domain could not be deleted because there exist domain controllers that still host this domain.[1]
0x00002162: The requested domain could not be deleted because there exist domain controllers that still host this domain.[1]
0x80072163: The requested operation can be performed only on a global catalog server.[1]
0x00002163: The requested operation can be performed only on a global catalog server.[1]
0x80072164: A local group can only be a member of other local groups in the same domain.[1]
0x00002164: A local group can only be a member of other local groups in the same domain.[1]
0x80072165: Foreign security principals cannot be members of universal groups.[1]
0x00002165: Foreign security principals cannot be members of universal groups.[1]
0x80072166: The attribute is not allowed to be replicated to the GC because of security reasons.[1]
0x00002166: The attribute is not allowed to be replicated to the GC because of security reasons.[1]
0x80072167: The checkpoint with the PDC could not be taken because there too many modifications being processed currently.[1]
0x00002167: The checkpoint with the PDC could not be taken because there too many modifications being processed currently.[1]
0x80072168: The operation requires that source domain auditing be enabled.[1]
0x00002168: The operation requires that source domain auditing be enabled.[1]
0x80072169: Security principal objects can only be created inside domain naming contexts.[1]
0x00002169: Security principal objects can only be created inside domain naming contexts.[1]
0x8007216A: A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.[1]
0x0000216A: A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.[1]
0x8007216B: A Filter was passed that uses constructed attributes.[1]
0x0000216B: A Filter was passed that uses constructed attributes.[1]
0x8007216C: The unicodePwd attribute value must be enclosed in double quotes.[1]
0x0000216C: The unicodePwd attribute value must be enclosed in double quotes.[1]
0x8007216D: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.[1]
0x0000216D: Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.[1]
0x8007216E: For security reasons, the operation must be run on the destination DC.[1]
0x0000216E: For security reasons, the operation must be run on the destination DC.[1]
0x8007216F: For security reasons, the source DC must be NT4SP4 or greater.[1]
0x0000216F: For security reasons, the source DC must be NT4SP4 or greater.[1]
0x80072170: Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.[1]
0x00002170: Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.[1]
0x80072171: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.[1]
0x00002171: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.[1]
0x80072172: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.[1]
0x00002172: Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.[1]
0x80072173: The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set.[1]
0x00002173: The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set.[1]
0x80072174: The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain.[1]
0x00002174: The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain.[1]
0x80072175: The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set.[1]
0x00002175: The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set.[1]
0x80072176: The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain.[1]
0x00002176: The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain.[1]
0x80072177: The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.[1]
0x00002177: The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.[1]
0x80072178: The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level.[1]
0x00002178: The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level.[1]
0x80072179: The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level.[1]
0x00002179: The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level.[1]
0x8007217A: The sort order requested is not supported.[1]
0x0000217A: The sort order requested is not supported.[1]
0x8007217B: The requested name already exists as a unique identifier.[1]
0x0000217B: The requested name already exists as a unique identifier.[1]
0x8007217C: The machine account was created pre-NT4. The account needs to be recreated.[1]
0x0000217C: The machine account was created pre-NT4. The account needs to be recreated.[1]
0x8007217D: The database is out of version store.[1]
0x0000217D: The database is out of version store.[1]
0x8007217E: Unable to continue operation because multiple conflicting controls were used.[1]
0x0000217E: Unable to continue operation because multiple conflicting controls were used.[1]
0x8007217F: Unable to find a valid security descriptor reference domain for this partition.[1]
0x0000217F: Unable to find a valid security descriptor reference domain for this partition.[1]
0x80072180: Schema update failed: The link identifier is reserved.[1]
0x00002180: Schema update failed: The link identifier is reserved.[1]
0x80072181: Schema update failed: There are no link identifiers available.[1]
0x00002181: Schema update failed: There are no link identifiers available.[1]
0x80072182: An account group cannot have a universal group as a member.[1]
0x00002182: An account group cannot have a universal group as a member.[1]
0x80072183: Rename or move operations on naming context heads or read-only objects are not allowed.[1]
0x00002183: Rename or move operations on naming context heads or read-only objects are not allowed.[1]
0x80072184: Move operations on objects in the schema naming context are not allowed.[1]
0x00002184: Move operations on objects in the schema naming context are not allowed.[1]
0x80072185: A system flag has been set on the object and does not allow the object to be moved or renamed.[1]
0x00002185: A system flag has been set on the object and does not allow the object to be moved or renamed.[1]
0x80072186: This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.[1]
0x00002186: This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.[1]
0x80072187: Unable to resolve completely, a referral to another forest is generated.[1]
0x00002187: Unable to resolve completely, a referral to another forest is generated.[1]
0x80072188: The requested action is not supported on standard server.[1]
0x00002188: The requested action is not supported on standard server.[1]
0x80072189: Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question.[1]
0x00002189: Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question.[1]
0x8007218A: The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.[1]
0x0000218A: The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.[1]
0x8007218B: The thread limit for this request was exceeded.[1]
0x0000218B: The thread limit for this request was exceeded.[1]
0x8007218C: The Global catalog server is not in the closest site.[1]
0x0000218C: The Global catalog server is not in the closest site.[1]
0x8007218D: The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.[1]
0x0000218D: The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.[1]
0x8007218E: The Directory Service failed to enter single user mode.[1]
0x0000218E: The Directory Service failed to enter single user mode.[1]
0x8007218F: The Directory Service cannot parse the script because of a syntax error.[1]
0x0000218F: The Directory Service cannot parse the script because of a syntax error.[1]
0x80072190: The Directory Service cannot process the script because of an error.[1]
0x00002190: The Directory Service cannot process the script because of an error.[1]
0x80072191: The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).[1]
0x00002191: The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).[1]
0x80072192: The directory service binding must be renegotiated due to a change in the server extensions information.[1]
0x00002192: The directory service binding must be renegotiated due to a change in the server extensions information.[1]
0x80072193: Operation not allowed on a disabled cross ref.[1]
0x00002193: Operation not allowed on a disabled cross ref.[1]
0x80072194: Schema update failed: No values for msDS-IntId are available.[1]
0x00002194: Schema update failed: No values for msDS-IntId are available.[1]
0x80072195: Schema update failed: Duplicate msDS-INtId. Retry the operation.[1]
0x00002195: Schema update failed: Duplicate msDS-INtId. Retry the operation.[1]
0x80072196: Schema deletion failed: attribute is used in rDNAttID.[1]
0x00002196: Schema deletion failed: attribute is used in rDNAttID.[1]
0x80072197: The directory service failed to authorize the request.[1]
0x00002197: The directory service failed to authorize the request.[1]
0x80072198: The Directory Service cannot process the script because it is invalid.[1]
0x00002198: The Directory Service cannot process the script because it is invalid.[1]
0x80072199: The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.[1]
0x00002199: The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.[1]
0x8007219A: A cross reference is in use locally with the same name.[1]
0x0000219A: A cross reference is in use locally with the same name.[1]
0x8007219B: The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest.[1]
0x0000219B: The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest.[1]
0x8007219C: Writeable NCs prevent this DC from demoting.[1]
0x0000219C: Writeable NCs prevent this DC from demoting.[1]
0x8007219D: The requested object has a non-unique identifier and cannot be retrieved.[1]
0x0000219D: The requested object has a non-unique identifier and cannot be retrieved.[1]
0x8007219E: Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.[1]
0x0000219E: Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.[1]
0x8007219F: The group cannot be converted due to attribute restrictions on the requested group type.[1]
0x0000219F: The group cannot be converted due to attribute restrictions on the requested group type.[1]
0x800721A0: Cross-domain move of non-empty basic application groups is not allowed.[1]
0x000021A0: Cross-domain move of non-empty basic application groups is not allowed.[1]
0x800721A1: Cross-domain move of non-empty query based application groups is not allowed.[1]
0x000021A1: Cross-domain move of non-empty query based application groups is not allowed.[1]
0x800721A2: The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.[1]
0x000021A2: The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.[1]
0x800721A3: The target container for a redirection of a well known object container cannot already be a special container.[1]
0x000021A3: The target container for a redirection of a well known object container cannot already be a special container.[1]
0x800721A4: The Directory Service cannot perform the requested operation because a domain rename operation is in progress.[1]
0x000021A4: The Directory Service cannot perform the requested operation because a domain rename operation is in progress.[1]
0x800721A5: The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.[1]
0x000021A5: The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.[1]
0x800721A6: The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.[1]
0x000021A6: The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.[1]
0x800721A7: The requested operation is not allowed on an object under the system container.[1]
0x000021A7: The requested operation is not allowed on an object under the system container.[1]
0x800721A8: The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected.[1]
0x000021A8: The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected.[1]
0x800721A9: The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency.[1]
0x000021A9: The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency.[1]
0x800721AA: At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies.[1]
0x000021AA: At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies.[1]
0x800721AB: The site settings object for the specified site does not exist.[1]
0x000021AB: The site settings object for the specified site does not exist.[1]
0x800721AC: The local account store does not contain secret material for the specified account.[1]
0x000021AC: The local account store does not contain secret material for the specified account.[1]
0x800721AD: Could not find a writable domain controller in the domain.[1]
0x000021AD: Could not find a writable domain controller in the domain.[1]
0x800721AE: The server object for the domain controller does not exist.[1]
0x000021AE: The server object for the domain controller does not exist.[1]
0x800721AF: The NTDS Settings object for the domain controller does not exist.[1]
0x000021AF: The NTDS Settings object for the domain controller does not exist.[1]
0x800721B0: The requested search operation is not supported for ASQ searches.[1]
0x000021B0: The requested search operation is not supported for ASQ searches.[1]
0x800721B1: A required audit event could not be generated for the operation.[1]
0x000021B1: A required audit event could not be generated for the operation.[1]
0x800721B2: The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.[1]
0x000021B2: The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.[1]
0x800721B3: The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.[1]
0x000021B3: The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.[1]
0x800721B4: The address books are nested too deeply. Failed to build the hierarchy table.[1]
0x000021B4: The address books are nested too deeply. Failed to build the hierarchy table.[1]
0x800721B5: The specified up-to-date-ness vector is corrupt.[1]
0x000021B5: The specified up-to-date-ness vector is corrupt.[1]
0x800721B6: The request to replicate secrets is denied.[1]
0x000021B6: The request to replicate secrets is denied.[1]
0x800721B7: Schema update failed: The MAPI identifier is reserved.[1]
0x000021B7: Schema update failed: The MAPI identifier is reserved.[1]
0x800721B8: Schema update failed: There are no MAPI identifiers available.[1]
0x000021B8: Schema update failed: There are no MAPI identifiers available.[1]
0x800721B9: The replication operation failed because the required attributes of the local krbtgt object are missing.[1]
0x000021B9: The replication operation failed because the required attributes of the local krbtgt object are missing.[1]
0x800721BA: The domain name of the trusted domain already exists in the forest.[1]
0x000021BA: The domain name of the trusted domain already exists in the forest.[1]
0x800721BB: The flat name of the trusted domain already exists in the forest.[1]
0x000021BB: The flat name of the trusted domain already exists in the forest.[1]
0x800721BC: The User Principal Name (UPN) is invalid.[1]
0x000021BC: The User Principal Name (UPN) is invalid.[1]
0x800721BD: OID mapped groups cannot have members.[1]
0x000021BD: OID mapped groups cannot have members.[1]
0x800721BF: The replication operation failed because the target object referred by a link value is recycled.[1]
0x000021BF: The replication operation failed because the target object referred by a link value is recycled.[1]
0x800721C0: The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller.[1]
0x000021C0: The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller.[1]
0x800721C1: The functional level of the AD LDS configuration set cannot be lowered to the requested value.[1]
0x000021C1: The functional level of the AD LDS configuration set cannot be lowered to the requested value.[1]
0x800721C2: The functional level of the domain (or forest) cannot be lowered to the requested value.[1]
0x000021C2: The functional level of the domain (or forest) cannot be lowered to the requested value.[1]
0x800721C3: The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level.[1]
0x000021C3: The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level.[1]
0x800721C4: The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information.[1]
0x000021C4: The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information.[1]
0x800721C5: The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object.[1]
0x000021C5: The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object.[1]
0x800721C6: The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site.[1]
0x000021C6: The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site.[1]
0x800721C7: The operation failed because SPN value provided for addition/modification is not unique forest-wide.[1]
0x000021C7: The operation failed because SPN value provided for addition/modification is not unique forest-wide.[1]
0x800721C8: The operation failed because UPN value provided for addition/modification is not unique forest-wide.[1]
0x000021C8: The operation failed because UPN value provided for addition/modification is not unique forest-wide.[1]
0x800721C9: The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present.[1]
0x000021C9: The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present.[1]
0x800721CA: The link value specified was not found, but a link value with that key was found.[1]
0x000021CA: The link value specified was not found, but a link value with that key was found.[1]
0x800732C8: The specified quick mode policy already exists.[1]
0x000032C8: The specified quick mode policy already exists.[1]
0x800732C9: The specified quick mode policy was not found.[1]
0x000032C9: The specified quick mode policy was not found.[1]
0x800732CA: The specified quick mode policy is being used.[1]
0x000032CA: The specified quick mode policy is being used.[1]
0x800732CB: The specified main mode policy already exists.[1]
0x000032CB: The specified main mode policy already exists.[1]
0x800732CC: The specified main mode policy was not found[1]
0x000032CC: The specified main mode policy was not found[1]
0x800732CD: The specified main mode policy is being used.[1]
0x000032CD: The specified main mode policy is being used.[1]
0x800732CE: The specified main mode filter already exists.[1]
0x000032CE: The specified main mode filter already exists.[1]
0x800732CF: The specified main mode filter was not found.[1]
0x000032CF: The specified main mode filter was not found.[1]
0x800732D0: The specified transport mode filter already exists.[1]
0x000032D0: The specified transport mode filter already exists.[1]
0x800732D1: The specified transport mode filter does not exist.[1]
0x000032D1: The specified transport mode filter does not exist.[1]
0x800732D2: The specified main mode authentication list exists.[1]
0x000032D2: The specified main mode authentication list exists.[1]
0x800732D3: The specified main mode authentication list was not found.[1]
0x000032D3: The specified main mode authentication list was not found.[1]
0x800732D4: The specified main mode authentication list is being used.[1]
0x000032D4: The specified main mode authentication list is being used.[1]
0x800732D5: The specified default main mode policy was not found.[1]
0x000032D5: The specified default main mode policy was not found.[1]
0x800732D6: The specified default main mode authentication list was not found.[1]
0x000032D6: The specified default main mode authentication list was not found.[1]
0x800732D7: The specified default quick mode policy was not found.[1]
0x000032D7: The specified default quick mode policy was not found.[1]
0x800732D8: The specified tunnel mode filter exists.[1]
0x000032D8: The specified tunnel mode filter exists.[1]
0x800732D9: The specified tunnel mode filter was not found.[1]
0x000032D9: The specified tunnel mode filter was not found.[1]
0x800732DA: The Main Mode filter is pending deletion.[1]
0x000032DA: The Main Mode filter is pending deletion.[1]
0x800732DB: The transport filter is pending deletion.[1]
0x000032DB: The transport filter is pending deletion.[1]
0x800732DC: The tunnel filter is pending deletion.[1]
0x000032DC: The tunnel filter is pending deletion.[1]
0x800732DD: The Main Mode policy is pending deletion.[1]
0x000032DD: The Main Mode policy is pending deletion.[1]
0x800732DE: The Main Mode authentication bundle is pending deletion.[1]
0x000032DE: The Main Mode authentication bundle is pending deletion.[1]
0x800732DF: The Quick Mode policy is pending deletion.[1]
0x000032DF: The Quick Mode policy is pending deletion.[1]
0x800735EE: IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.[1]
0x000035EE: IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.[1]
0x800735EF: IKE SA deleted by peer before establishment completed[1]
0x000035EF: IKE SA deleted by peer before establishment completed[1]
0x800735F0: IKE SA deleted before establishment completed[1]
0x000035F0: IKE SA deleted before establishment completed[1]
0x800735F1: Negotiation request sat in Queue too long[1]
0x000035F1: Negotiation request sat in Queue too long[1]
0x800735F2: Negotiation request sat in Queue too long[1]
0x000035F2: Negotiation request sat in Queue too long[1]
0x800735F3: Negotiation request sat in Queue too long[1]
0x000035F3: Negotiation request sat in Queue too long[1]
0x800735F4: Negotiation request sat in Queue too long[1]
0x000035F4: Negotiation request sat in Queue too long[1]
0x800735FC: IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.[1]
0x000035FC: IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.[1]
0x8007361D: Failed to obtain security function table dispatch address from SSPI.[1]
0x0000361D: Failed to obtain security function table dispatch address from SSPI.[1]
0x8007361E: Failed to query Kerberos package to obtain max token size.[1]
0x0000361E: Failed to query Kerberos package to obtain max token size.[1]
0x8007361F: Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.[1]
0x0000361F: Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.[1]
0x80073620: Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).[1]
0x00003620: Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).[1]
0x80073621: Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.[1]
0x00003621: Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.[1]
0x80073624: Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.[1]
0x00003624: Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.[1]
0x80073636: Temporary state created to perform reinitialization. This is not a real failure.[1]
0x00003636: Temporary state created to perform reinitialization. This is not a real failure.[1]
0x80073637: The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.[1]
0x00003637: The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.[1]
0x80073638: The recipient cannot handle version of IKE specified in the header.[1]
0x00003638: The recipient cannot handle version of IKE specified in the header.[1]
0x80073639: Key length in certificate is too small for configured security requirements.[1]
0x00003639: Key length in certificate is too small for configured security requirements.[1]
0x8007363A: Max number of established MM SAs to peer exceeded.[1]
0x0000363A: Max number of established MM SAs to peer exceeded.[1]
0x8007363B: IKE received a policy that disables negotiation.[1]
0x0000363B: IKE received a policy that disables negotiation.[1]
0x8007363C: Reached maximum quick mode limit for the main mode. New main mode will be started.[1]
0x0000363C: Reached maximum quick mode limit for the main mode. New main mode will be started.[1]
0x8007363D: Main mode SA lifetime expired or peer sent a main mode delete.[1]
0x0000363D: Main mode SA lifetime expired or peer sent a main mode delete.[1]
0x8007363E: Main mode SA assumed to be invalid because peer stopped responding.[1]
0x0000363E: Main mode SA assumed to be invalid because peer stopped responding.[1]
0x8007363F: Certificate doesn't chain to a trusted root in IPsec policy.[1]
0x0000363F: Certificate doesn't chain to a trusted root in IPsec policy.[1]
0x80073652: SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential.[1]
0x00003652: SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential.[1]
0x80073653: SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard.[1]
0x00003653: SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard.[1]
0x80073654: SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA.[1]
0x00003654: SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA.[1]
0x8007365D: IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.[1]
0x0000365D: IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.[1]
0x8007365E: IPsec dropped a packet due to DoS throttling.[1]
0x0000365E: IPsec dropped a packet due to DoS throttling.[1]
0x80073665: IPsec DoS Protection matched an explicit block rule.[1]
0x00003665: IPsec DoS Protection matched an explicit block rule.[1]
0x80073666: IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.[1]
0x00003666: IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.[1]
0x80073667: IPsec DoS Protection received an incorrectly formatted packet.[1]
0x00003667: IPsec DoS Protection received an incorrectly formatted packet.[1]
0x80073668: IPsec DoS Protection failed to look up state.[1]
0x00003668: IPsec DoS Protection failed to look up state.[1]
0x80073669: IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.[1]
0x00003669: IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.[1]
0x8007366A: IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.[1]
0x0000366A: IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.[1]
0x8007366B: IPsec DoS Protection has not been enabled.[1]
0x0000366B: IPsec DoS Protection has not been enabled.[1]
0x8007366C: IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached.[1]
0x0000366C: IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached.[1]
0x800736B0: The requested section was not present in the activation context.[1]
0x000036B0: The requested section was not present in the activation context.[1]
0x800736B1: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.[1]
0x000036B1: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.[1]
0x800736B2: The application binding data format is invalid.[1]
0x000036B2: The application binding data format is invalid.[1]
0x800736B3: The referenced assembly is not installed on your system.[1]
0x000036B3: The referenced assembly is not installed on your system.[1]
0x800736B4: The manifest file does not begin with the required tag and format information.[1]
0x000036B4: The manifest file does not begin with the required tag and format information.[1]
0x800736B5: The manifest file contains one or more syntax errors.[1]
0x000036B5: The manifest file contains one or more syntax errors.[1]
0x800736B6: The application attempted to activate a disabled activation context.[1]
0x000036B6: The application attempted to activate a disabled activation context.[1]
0x800736B7: The requested lookup key was not found in any active activation context.[1]
0x000036B7: The requested lookup key was not found in any active activation context.[1]
0x800736B8: A component version required by the application conflicts with another component version already active.[1]
0x000036B8: A component version required by the application conflicts with another component version already active.[1]
0x800736B9: The type requested activation context section does not match the query API used.[1]
0x000036B9: The type requested activation context section does not match the query API used.[1]
0x800736BA: Lack of system resources has required isolated activation to be disabled for the current thread of execution.[1]
0x000036BA: Lack of system resources has required isolated activation to be disabled for the current thread of execution.[1]
0x800736BB: An attempt to set the process default activation context failed because the process default activation context was already set.[1]
0x000036BB: An attempt to set the process default activation context failed because the process default activation context was already set.[1]
0x800736BC: The encoding group identifier specified is not recognized.[1]
0x000036BC: The encoding group identifier specified is not recognized.[1]
0x800736BD: The encoding requested is not recognized.[1]
0x000036BD: The encoding requested is not recognized.[1]
0x800736BE: The manifest contains a reference to an invalid URI.[1]
0x000036BE: The manifest contains a reference to an invalid URI.[1]
0x800736BF: The application manifest contains a reference to a dependent assembly which is not installed[1]
0x000036BF: The application manifest contains a reference to a dependent assembly which is not installed[1]
0x800736C0: The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed[1]
0x000036C0: The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed[1]
0x800736C1: The manifest contains an attribute for the assembly identity which is not valid.[1]
0x000036C1: The manifest contains an attribute for the assembly identity which is not valid.[1]
0x800736C2: The manifest is missing the required default namespace specification on the assembly element.[1]
0x000036C2: The manifest is missing the required default namespace specification on the assembly element.[1]
0x800736C3: The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1".[1]
0x000036C3: The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1".[1]
0x800736C4: The private manifest probed has crossed a path with an unsupported reparse point.[1]
0x000036C4: The private manifest probed has crossed a path with an unsupported reparse point.[1]
0x800736C5: Two or more components referenced directly or indirectly by the application manifest have files by the same name.[1]
0x000036C5: Two or more components referenced directly or indirectly by the application manifest have files by the same name.[1]
0x800736C6: Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.[1]
0x000036C6: Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.[1]
0x800736C7: Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.[1]
0x000036C7: Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.[1]
0x800736C8: Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.[1]
0x000036C8: Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.[1]
0x800736C9: Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.[1]
0x000036C9: Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.[1]
0x800736CA: Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.[1]
0x000036CA: Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.[1]
0x800736CB: Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.[1]
0x000036CB: Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.[1]
0x800736CC: A component's file does not match the verification information present in the component manifest.[1]
0x000036CC: A component's file does not match the verification information present in the component manifest.[1]
0x800736CD: The policy manifest contains one or more syntax errors.[1]
0x000036CD: The policy manifest contains one or more syntax errors.[1]
0x800736CE: Manifest Parse Error : A string literal was expected, but no opening quote character was found.[1]
0x000036CE: Manifest Parse Error : A string literal was expected, but no opening quote character was found.[1]
0x800736CF: Manifest Parse Error : Incorrect syntax was used in a comment.[1]
0x000036CF: Manifest Parse Error : Incorrect syntax was used in a comment.[1]
0x800736D0: Manifest Parse Error : A name was started with an invalid character.[1]
0x000036D0: Manifest Parse Error : A name was started with an invalid character.[1]
0x800736D1: Manifest Parse Error : A name contained an invalid character.[1]
0x000036D1: Manifest Parse Error : A name contained an invalid character.[1]
0x800736D2: Manifest Parse Error : A string literal contained an invalid character.[1]
0x000036D2: Manifest Parse Error : A string literal contained an invalid character.[1]
0x800736D3: Manifest Parse Error : Invalid syntax for an xml declaration.[1]
0x000036D3: Manifest Parse Error : Invalid syntax for an xml declaration.[1]
0x800736D4: Manifest Parse Error : An Invalid character was found in text content.[1]
0x000036D4: Manifest Parse Error : An Invalid character was found in text content.[1]
0x800736D5: Manifest Parse Error : Required white space was missing.[1]
0x000036D5: Manifest Parse Error : Required white space was missing.[1]
0x800736D6: Manifest Parse Error : The character '>' was expected.[1]
0x000036D6: Manifest Parse Error : The character '>' was expected.[1]
0x800736D7: Manifest Parse Error : A semi colon character was expected.[1]
0x000036D7: Manifest Parse Error : A semi colon character was expected.[1]
0x800736E6: Manifest Parse Error : Only one top level element is allowed in an XML document.[1]
0x000036E6: Manifest Parse Error : Only one top level element is allowed in an XML document.[1]
0x800736E7: Manifest Parse Error : Invalid at the top level of the document.[1]
0x000036E7: Manifest Parse Error : Invalid at the top level of the document.[1]
0x800736E8: Manifest Parse Error : Invalid xml declaration.[1]
0x000036E8: Manifest Parse Error : Invalid xml declaration.[1]
0x800736E9: Manifest Parse Error : XML document must have a top level element.[1]
0x000036E9: Manifest Parse Error : XML document must have a top level element.[1]
0x800736EA: Manifest Parse Error : Unexpected end of file.[1]
0x000036EA: Manifest Parse Error : Unexpected end of file.[1]
0x800736EB: Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.[1]
0x000036EB: Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.[1]
0x800736EC: Manifest Parse Error : Element was not closed.[1]
0x000036EC: Manifest Parse Error : Element was not closed.[1]
0x800736ED: Manifest Parse Error : End element was missing the character '>'.[1]
0x000036ED: Manifest Parse Error : End element was missing the character '>'.[1]
0x800736EE: Manifest Parse Error : A string literal was not closed.[1]
0x000036EE: Manifest Parse Error : A string literal was not closed.[1]
0x800736EF: Manifest Parse Error : A comment was not closed.[1]
0x000036EF: Manifest Parse Error : A comment was not closed.[1]
0x800736F0: Manifest Parse Error : A declaration was not closed.[1]
0x000036F0: Manifest Parse Error : A declaration was not closed.[1]
0x800736F1: Manifest Parse Error : A CDATA section was not closed.[1]
0x000036F1: Manifest Parse Error : A CDATA section was not closed.[1]
0x800736F2: Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml".[1]
0x000036F2: Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml".[1]
0x800736F3: Manifest Parse Error : System does not support the specified encoding.[1]
0x000036F3: Manifest Parse Error : System does not support the specified encoding.[1]
0x800736F4: Manifest Parse Error : Switch from current encoding to specified encoding not supported.[1]
0x000036F4: Manifest Parse Error : Switch from current encoding to specified encoding not supported.[1]
0x800736F5: Manifest Parse Error : The name 'xml' is reserved and must be lower case.[1]
0x000036F5: Manifest Parse Error : The name 'xml' is reserved and must be lower case.[1]
0x800736F6: Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'.[1]
0x000036F6: Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'.[1]
0x800736F7: Manifest Parse Error : The standalone attribute cannot be used in external entities.[1]
0x000036F7: Manifest Parse Error : The standalone attribute cannot be used in external entities.[1]
0x800736F8: Manifest Parse Error : Invalid version number.[1]
0x000036F8: Manifest Parse Error : Invalid version number.[1]
0x800736F9: Manifest Parse Error : Missing equals sign between attribute and attribute value.[1]
0x000036F9: Manifest Parse Error : Missing equals sign between attribute and attribute value.[1]
0x800736FA: Assembly Protection Error : Unable to recover the specified assembly.[1]
0x000036FA: Assembly Protection Error : Unable to recover the specified assembly.[1]
0x800736FB: Assembly Protection Error : The public key for an assembly was too short to be allowed.[1]
0x000036FB: Assembly Protection Error : The public key for an assembly was too short to be allowed.[1]
0x800736FC: Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest.[1]
0x000036FC: Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest.[1]
0x800736FD: An HRESULT could not be translated to a corresponding Win32 error code.[1]
0x000036FD: An HRESULT could not be translated to a corresponding Win32 error code.[1]
0x800736FE: Assembly Protection Error : The catalog for an assembly is missing.[1]
0x000036FE: Assembly Protection Error : The catalog for an assembly is missing.[1]
0x800736FF: The supplied assembly identity is missing one or more attributes which must be present in this context.[1]
0x000036FF: The supplied assembly identity is missing one or more attributes which must be present in this context.[1]
0x80073700: The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.[1]
0x00003700: The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.[1]
0x80073701: The referenced assembly could not be found.[1]
0x00003701: The referenced assembly could not be found.[1]
0x80073702: The activation context activation stack for the running thread of execution is corrupt.[1]
0x00003702: The activation context activation stack for the running thread of execution is corrupt.[1]
0x80073703: The application isolation metadata for this process or thread has become corrupt.[1]
0x00003703: The application isolation metadata for this process or thread has become corrupt.[1]
0x80073704: The activation context being deactivated is not the most recently activated one.[1]
0x00003704: The activation context being deactivated is not the most recently activated one.[1]
0x80073705: The activation context being deactivated is not active for the current thread of execution.[1]
0x00003705: The activation context being deactivated is not active for the current thread of execution.[1]
0x80073706: The activation context being deactivated has already been deactivated.[1]
0x00003706: The activation context being deactivated has already been deactivated.[1]
0x80073707: A component used by the isolation facility has requested to terminate the process.[1]
0x00003707: A component used by the isolation facility has requested to terminate the process.[1]
0x80073708: A kernel mode component is releasing a reference on an activation context.[1]
0x00003708: A kernel mode component is releasing a reference on an activation context.[1]
0x80073709: The activation context of system default assembly could not be generated.[1]
0x00003709: The activation context of system default assembly could not be generated.[1]
0x8007370A: The value of an attribute in an identity is not within the legal range.[1]
0x0000370A: The value of an attribute in an identity is not within the legal range.[1]
0x8007370B: The name of an attribute in an identity is not within the legal range.[1]
0x0000370B: The name of an attribute in an identity is not within the legal range.[1]
0x8007370C: An identity contains two definitions for the same attribute.[1]
0x0000370C: An identity contains two definitions for the same attribute.[1]
0x8007370D: The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.[1]
0x0000370D: The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.[1]
0x8007370E: A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.[1]
0x0000370E: A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.[1]
0x8007370F: The public key token does not correspond to the public key specified.[1]
0x0000370F: The public key token does not correspond to the public key specified.[1]
0x80073710: A substitution string had no mapping.[1]
0x00003710: A substitution string had no mapping.[1]
0x80073711: The component must be locked before making the request.[1]
0x00003711: The component must be locked before making the request.[1]
0x80073712: The component store has been corrupted.[1]
0x00003712: The component store has been corrupted.[1]
0x80073713: An advanced installer failed during setup or servicing.[1]
0x00003713: An advanced installer failed during setup or servicing.[1]
0x80073714: The character encoding in the XML declaration did not match the encoding used in the document.[1]
0x00003714: The character encoding in the XML declaration did not match the encoding used in the document.[1]
0x80073715: The identities of the manifests are identical but their contents are different.[1]
0x00003715: The identities of the manifests are identical but their contents are different.[1]
0x80073716: The component identities are different.[1]
0x00003716: The component identities are different.[1]
0x80073A9A: The publisher metadata cannot be found in the resource.[1]
0x00003A9A: The publisher metadata cannot be found in the resource.[1]
0x80073A9B: The template for an event definition cannot be found in the resource (error = %1).[1]
0x00003A9B: The template for an event definition cannot be found in the resource (error = %1).[1]
0x80073A9C: The specified publisher name is invalid.[1]
0x00003A9C: The specified publisher name is invalid.[1]
0x80073A9D: The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest[1]
0x00003A9D: The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest[1]
0x80073A9F: The specified channel could not be found. Check channel configuration.[1]
0x00003A9F: The specified channel could not be found. Check channel configuration.[1]
0x80073AA0: The specified xml text was not well-formed. See Extended Error for more details.[1]
0x00003AA0: The specified xml text was not well-formed. See Extended Error for more details.[1]
0x80073AA1: The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to.[1]
0x00003AA1: The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to.[1]
0x80073AA3: The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query.[1]
0x00003AA3: The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query.[1]
0x80073AA4: Query result is currently at an invalid position.[1]
0x00003AA4: Query result is currently at an invalid position.[1]
0x80073AA5: Registered MSXML doesn't support validation.[1]
0x00003AA5: Registered MSXML doesn't support validation.[1]
0x80073AA6: An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation.[1]
0x00003AA6: An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation.[1]
0x80073AA7: Can't perform a step operation from a term that does not represent an element set.[1]
0x00003AA7: Can't perform a step operation from a term that does not represent an element set.[1]
0x80073AA8: Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants.[1]
0x00003AA8: Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants.[1]
0x80073AA9: A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceeding node set can be evaluated.[1]
0x00003AA9: A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceeding node set can be evaluated.[1]
0x80073AAA: This data type is currently unsupported.[1]
0x00003AAA: This data type is currently unsupported.[1]
0x80073AAB: A syntax error occurred at position %1!d![1]
0x00003AAB: A syntax error occurred at position %1!d![1]
0x80073AAC: This operator is unsupported by this implementation of the filter.[1]
0x00003AAC: This operator is unsupported by this implementation of the filter.[1]
0x80073AAD: The token encountered was unexpected.[1]
0x00003AAD: The token encountered was unexpected.[1]
0x80073AAE: The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation.[1]
0x00003AAE: The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation.[1]
0x80073AAF: Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of channel.[1]
0x00003AAF: Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of channel.[1]
0x80073AB0: Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of publisher.[1]
0x00003AB0: Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of publisher.[1]
0x80073AB2: The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions.[1]
0x00003AB2: The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions.[1]
0x80073AB3: the message resource is present but the message is not found in the string/message table[1]
0x00003AB3: the message resource is present but the message is not found in the string/message table[1]
0x80073AB4: The message id for the desired message could not be found.[1]
0x00003AB4: The message id for the desired message could not be found.[1]
0x80073AB5: The substitution string for insert index (%1) could not be found.[1]
0x00003AB5: The substitution string for insert index (%1) could not be found.[1]
0x80073AB6: The description string for parameter reference (%1) could not be found.[1]
0x00003AB6: The description string for parameter reference (%1) could not be found.[1]
0x80073AB7: The maximum number of replacements has been reached.[1]
0x00003AB7: The maximum number of replacements has been reached.[1]
0x80073AB8: The event definition could not be found for event id (%1).[1]
0x00003AB8: The event definition could not be found for event id (%1).[1]
0x80073AB9: The locale specific resource for the desired message is not present.[1]
0x00003AB9: The locale specific resource for the desired message is not present.[1]
0x80073ABA: The resource is too old to be compatible.[1]
0x00003ABA: The resource is too old to be compatible.[1]
0x80073ABB: The resource is too new to be compatible.[1]
0x00003ABB: The resource is too new to be compatible.[1]
0x80073ABC: The channel at index %1!d! of the query can't be opened.[1]
0x00003ABC: The channel at index %1!d! of the query can't be opened.[1]
0x80073ABD: The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.[1]
0x00003ABD: The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.[1]
0x80073ABE: Attempted to create a numeric type that is outside of its valid range.[1]
0x00003ABE: Attempted to create a numeric type that is outside of its valid range.[1]
0x80073AE9: The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated.[1]
0x00003AE9: The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated.[1]
0x80073AEA: When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription.[1]
0x00003AEA: When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription.[1]
0x80073AEB: The credential store that is used to save credentials is full.[1]
0x00003AEB: The credential store that is used to save credentials is full.[1]
0x80073AEC: The credential used by this subscription can't be found in credential store.[1]
0x00003AEC: The credential used by this subscription can't be found in credential store.[1]
0x80073AED: No active channel is found for the query.[1]
0x00003AED: No active channel is found for the query.[1]
0x80073AFC: The resource loader failed to find MUI file.[1]
0x00003AFC: The resource loader failed to find MUI file.[1]
0x80073AFD: The resource loader failed to load MUI file because the file fail to pass validation.[1]
0x00003AFD: The resource loader failed to load MUI file because the file fail to pass validation.[1]
0x80073AFE: The RC Manifest is corrupted with garbage data or unsupported version or missing required item.[1]
0x00003AFE: The RC Manifest is corrupted with garbage data or unsupported version or missing required item.[1]
0x80073AFF: The RC Manifest has invalid culture name.[1]
0x00003AFF: The RC Manifest has invalid culture name.[1]
0x80073B00: The RC Manifest has invalid ultimatefallback name.[1]
0x00003B00: The RC Manifest has invalid ultimatefallback name.[1]
0x80073B01: The resource loader cache doesn't have loaded MUI entry.[1]
0x00003B01: The resource loader cache doesn't have loaded MUI entry.[1]
0x80073B22: Unable to determine qualifier value or qualifier value has not been set.[1]
0x00003B22: Unable to determine qualifier value or qualifier value has not been set.[1]
0x80073B23: Automerge is enabled in the PRI file.[1]
0x00003B23: Automerge is enabled in the PRI file.[1]
0x80073B24: Too many resources defined for package.[1]
0x00003B24: Too many resources defined for package.[1]
0x80073B25: Resource File can not be used for merge operation.[1]
0x00003B25: Resource File can not be used for merge operation.[1]
0x80073B26: Load/UnloadPriFiles cannot be used with resource packages.[1]
0x00003B26: Load/UnloadPriFiles cannot be used with resource packages.[1]
0x80073B27: Resource Contexts may not be created on threads that do not have a CoreWindow.[1]
0x00003B27: Resource Contexts may not be created on threads that do not have a CoreWindow.[1]
0x80073B28: The singleton Resource Manager with different profile is already created.[1]
0x00003B28: The singleton Resource Manager with different profile is already created.[1]
0x80073B29: The system component cannot operate given API operation[1]
0x00003B29: The system component cannot operate given API operation[1]
0x80073B2A: The resource is a direct reference to a non-default resource candidate.[1]
0x00003B2A: The resource is a direct reference to a non-default resource candidate.[1]
0x80073B2B: Resource Map has been re-generated and the query string is not valid anymore.[1]
0x00003B2B: Resource Map has been re-generated and the query string is not valid anymore.[1]
0x80073B2C: The PRI files to be merged have incompatible versions.[1]
0x00003B2C: The PRI files to be merged have incompatible versions.[1]
0x80073B2D: The primary PRI files to be merged does not contain a schema.[1]
0x00003B2D: The primary PRI files to be merged does not contain a schema.[1]
0x80073B2E: Unable to load one of the PRI files to be merged.[1]
0x00003B2E: Unable to load one of the PRI files to be merged.[1]
0x80073B2F: Unable to add one of the PRI files to the merged file.[1]
0x00003B2F: Unable to add one of the PRI files to the merged file.[1]
0x80073B30: Unable to create the merged PRI file.[1]
0x00003B30: Unable to create the merged PRI file.[1]
0x80073B60: The 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.[1]
0x00003B60: The 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.[1]
0x80073B61: The monitor's VCP Version (0xDF) VCP code returned an invalid version value.[1]
0x00003B61: The monitor's VCP Version (0xDF) VCP code returned an invalid version value.[1]
0x80073B62: The monitor does not comply with the MCCS specification it claims to support.[1]
0x00003B62: The monitor does not comply with the MCCS specification it claims to support.[1]
0x80073B63: The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.[1]
0x00003B63: The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.[1]
0x80073B64: The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.[1]
0x00003B64: The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.[1]
0x80073B65: An internal Monitor Configuration API error occurred.[1]
0x00003B65: An internal Monitor Configuration API error occurred.[1]
0x80073B66: The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0x00003B66: The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0x80073B67: The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0x00003B67: The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[1]
0x80073B92: The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.[1]
0x00003B92: The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.[1]
0x80073BC3: The requested system device cannot be found.[1]
0x00003BC3: The requested system device cannot be found.[1]
0x80073BC4: Hash generation for the specified hash version and hash type is not enabled on the server.[1]
0x00003BC4: Hash generation for the specified hash version and hash type is not enabled on the server.[1]
0x80073BC5: The hash requested from the server is not available or no longer valid.[1]
0x00003BC5: The hash requested from the server is not available or no longer valid.[1]
0x80073BD9: The secondary interrupt controller instance that manages the specified interrupt is not registered.[1]
0x00003BD9: The secondary interrupt controller instance that manages the specified interrupt is not registered.[1]
0x80073BDA: The information supplied by the GPIO client driver is invalid.[1]
0x00003BDA: The information supplied by the GPIO client driver is invalid.[1]
0x80073BDB: The version specified by the GPIO client driver is not supported.[1]
0x00003BDB: The version specified by the GPIO client driver is not supported.[1]
0x80073BDC: The registration packet supplied by the GPIO client driver is not valid.[1]
0x00003BDC: The registration packet supplied by the GPIO client driver is not valid.[1]
0x80073BDD: The requested operation is not suppported for the specified handle.[1]
0x00003BDD: The requested operation is not suppported for the specified handle.[1]
0x80073BDE: The requested connect mode conflicts with an existing mode on one or more of the specified pins.[1]
0x00003BDE: The requested connect mode conflicts with an existing mode on one or more of the specified pins.[1]
0x80073BDF: The interrupt requested to be unmasked is not masked.[1]
0x00003BDF: The interrupt requested to be unmasked is not masked.[1]
0x80073C28: The requested run level switch cannot be completed successfully.[1]
0x00003C28: The requested run level switch cannot be completed successfully.[1]
0x80073C29: must not be higher than the run level of its dependent services.[1]
0x00003C29: must not be higher than the run level of its dependent services.[1]
0x80073C2A: one or more services will not stop or restart within the specified timeout.[1]
0x00003C2A: one or more services will not stop or restart within the specified timeout.[1]
0x80073C2B: A run level switch agent did not respond within the specified timeout.[1]
0x00003C2B: A run level switch agent did not respond within the specified timeout.[1]
0x80073C2C: A run level switch is currently in progress.[1]
0x00003C2C: A run level switch is currently in progress.[1]
0x80073C2D: One or more services failed to start during the service startup phase of a run level switch.[1]
0x00003C2D: One or more services failed to start during the service startup phase of a run level switch.[1]
0x80073CF9: Install failed. Please contact your software vendor.[1]
0x00003CF9: Install failed. Please contact your software vendor.[1]
0x80073CFA: Removal failed. Please contact your software vendor.[1]
0x00003CFA: Removal failed. Please contact your software vendor.[1]
0x80073CFB: The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details.[1]
0x00003CFB: The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details.[1]
0x80073CFC: The application cannot be started. Try reinstalling the application to fix the problem.[1]
0x00003CFC: The application cannot be started. Try reinstalling the application to fix the problem.[1]
0x80073CFD: A Prerequisite for an install could not be satisfied.[1]
0x00003CFD: A Prerequisite for an install could not be satisfied.[1]
0x80073CFF: To install this application you need either a Windows developer license or a sideloading-enabled system.[1]
0x00003CFF: To install this application you need either a Windows developer license or a sideloading-enabled system.[1]
0x80073D00: The application cannot be started because it is currently updating.[1]
0x00003D00: The application cannot be started because it is currently updating.[1]
0x80073D01: The package deployment operation is blocked by policy. Please contact your system administrator.[1]
0x00003D01: The package deployment operation is blocked by policy. Please contact your system administrator.[1]
0x80073D02: The package could not be installed because resources it modifies are currently in use.[1]
0x00003D02: The package could not be installed because resources it modifies are currently in use.[1]
0x80073D03: The package could not be recovered because necessary data for recovery have been corrupted.[1]
0x00003D03: The package could not be recovered because necessary data for recovery have been corrupted.[1]
0x80073D04: The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present.[1]
0x00003D04: The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present.[1]
0x80073D05: An error occurred while deleting the package's previously existing application data.[1]
0x00003D05: An error occurred while deleting the package's previously existing application data.[1]
0x80073D06: The package could not be installed because a higher version of this package is already installed.[1]
0x00003D06: The package could not be installed because a higher version of this package is already installed.[1]
0x80073D07: An error in a system binary was detected. Try refreshing the PC to fix the problem.[1]
0x00003D07: An error in a system binary was detected. Try refreshing the PC to fix the problem.[1]
0x80073D08: A corrupted CLR NGEN binary was detected on the system.[1]
0x00003D08: A corrupted CLR NGEN binary was detected on the system.[1]
0x80073D09: The operation could not be resumed because necessary data for recovery have been corrupted.[1]
0x00003D09: The operation could not be resumed because necessary data for recovery have been corrupted.[1]
0x80073D0A: The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again.[1]
0x00003D0A: The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again.[1]
0x80073D0C: The deployment operation failed because the volume is not empty.[1]
0x00003D0C: The deployment operation failed because the volume is not empty.[1]
0x80073D0D: The deployment operation failed because the volume is offline.[1]
0x00003D0D: The deployment operation failed because the volume is offline.[1]
0x80073D0E: The deployment operation failed because the specified volume is corrupt.[1]
0x00003D0E: The deployment operation failed because the specified volume is corrupt.[1]
0x80073D0F: The deployment operation failed because the specified application needs to be registered first.[1]
0x00003D0F: The deployment operation failed because the specified application needs to be registered first.[1]
0x80073D10: The deployment operation failed because the package targets the wrong processor architecture.[1]
0x00003D10: The deployment operation failed because the package targets the wrong processor architecture.[1]
0x80073D11: You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again.[1]
0x00003D11: You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again.[1]
0x80073D12: A main app package is required to install this optional package. Install the main package first and try again.[1]
0x00003D12: A main app package is required to install this optional package. Install the main package first and try again.[1]
0x80073D13: This app package type is not supported on this filesystem[1]
0x00003D13: This app package type is not supported on this filesystem[1]