KernelBase.dll
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x0 | 78.1 | The operation completed successfully. |
| 0x1 | 78.1 | Incorrect function. |
| 0x2 | 78.1 | The system cannot find the file specified. |
| 0x3 | 78.1 | The system cannot find the path specified. |
| 0x4 | 78.1 | The system cannot open the file. |
| 0x5 | 78.1 | Access is denied. |
| 0x6 | 78.1 | The handle is invalid. |
| 0x7 | 78.1 | The storage control blocks were destroyed. |
| 0x8 | 78.1 | Not enough storage is available to process this command. |
| 0x9 | 78.1 | The storage control block address is invalid. |
| 0xa | 78.1 | The environment is incorrect. |
| 0xb | 78.1 | An attempt was made to load a program with an incorrect format. |
| 0xc | 78.1 | The access code is invalid. |
| 0xd | 78.1 | The data is invalid. |
| 0xe | 78.1 | Not enough storage is available to complete this operation. |
| 0xf | 78.1 | The system cannot find the drive specified. |
| 0x10 | 78.1 | The directory cannot be removed. |
| 0x11 | 78.1 | The system cannot move the file to a different disk drive. |
| 0x12 | 78.1 | There are no more files. |
| 0x13 | 78.1 | The media is write protected. |
| 0x14 | 78.1 | The system cannot find the device specified. |
| 0x15 | 78.1 | The device is not ready. |
| 0x16 | 78.1 | The device does not recognize the command. |
| 0x17 | 78.1 | Data error (cyclic redundancy check). |
| 0x18 | 78.1 | The program issued a command but the command length is incorrect. |
| 0x19 | 78.1 | The drive cannot locate a specific area or track on the disk. |
| 0x1a | 78.1 | The specified disk or diskette cannot be accessed. |
| 0x1b | 78.1 | The drive cannot find the sector requested. |
| 0x1c | 78.1 | The printer is out of paper. |
| 0x1d | 78.1 | The system cannot write to the specified device. |
| 0x1e | 78.1 | The system cannot read from the specified device. |
| 0x1f | 78.1 | A device attached to the system is not functioning. |
| 0x20 | 78.1 | The process cannot access the file because it is being used by another process. |
| 0x21 | 78.1 | The process cannot access the file because another process has locked a portion of the file. |
| 0x22 | 78.1 | The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1. |
| 0x24 | 78.1 | Too many files opened for sharing. |
| 0x26 | 78.1 | Reached the end of the file. |
| 0x27 | 78.1 | The disk is full. |
| 0x32 | 78.1 | The request is not supported. |
| 0x33 | 78.1 | 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. |
| 0x34 | 78.1 | 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. |
| 0x35 | 78.1 | The network path was not found. |
| 0x36 | 78.1 | The network is busy. |
| 0x37 | 78.1 | The specified network resource or device is no longer available. |
| 0x38 | 78.1 | The network BIOS command limit has been reached. |
| 0x39 | 78.1 | A network adapter hardware error occurred. |
| 0x3a | 78.1 | The specified server cannot perform the requested operation. |
| 0x3b | 78.1 | An unexpected network error occurred. |
| 0x3c | 78.1 | The remote adapter is not compatible. |
| 0x3d | 78.1 | The printer queue is full. |
| 0x3e | 78.1 | Space to store the file waiting to be printed is not available on the server. |
| 0x3f | 78.1 | Your file waiting to be printed was deleted. |
| 0x40 | 78.1 | The specified network name is no longer available. |
| 0x41 | 78.1 | Network access is denied. |
| 0x42 | 78.1 | The network resource type is not correct. |
| 0x43 | 78.1 | The network name cannot be found. |
| 0x44 | 78.1 | The name limit for the local computer network adapter card was exceeded. |
| 0x45 | 78.1 | The network BIOS session limit was exceeded. |
| 0x46 | 78.1 | The remote server has been paused or is in the process of being started. |
| 0x47 | 78.1 | 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. |
| 0x48 | 78.1 | The specified printer or disk device has been paused. |
| 0x50 | 78.1 | The file exists. |
| 0x52 | 78.1 | The directory or file cannot be created. |
| 0x53 | 78.1 | Fail on INT 24. |
| 0x54 | 78.1 | Storage to process this request is not available. |
| 0x55 | 78.1 | The local device name is already in use. |
| 0x56 | 78.1 | The specified network password is not correct. |
| 0x57 | 78.1 | The parameter is incorrect. |
| 0x58 | 78.1 | A write fault occurred on the network. |
| 0x59 | 78.1 | The system cannot start another process at this time. |
| 0x64 | 78.1 | Cannot create another system semaphore. |
| 0x65 | 78.1 | The exclusive semaphore is owned by another process. |
| 0x66 | 78.1 | The semaphore is set and cannot be closed. |
| 0x67 | 78.1 | The semaphore cannot be set again. |
| 0x68 | 78.1 | Cannot request exclusive semaphores at interrupt time. |
| 0x69 | 78.1 | The previous ownership of this semaphore has ended. |
| 0x6a | 78.1 | Insert the diskette for drive %1. |
| 0x6b | 78.1 | The program stopped because an alternate diskette was not inserted. |
| 0x6c | 78.1 | The disk is in use or locked by another process. |
| 0x6d | 78.1 | The pipe has been ended. |
| 0x6e | 78.1 | The system cannot open the device or file specified. |
| 0x6f | 78.1 | The file name is too long. |
| 0x70 | 78.1 | There is not enough space on the disk. |
| 0x71 | 78.1 | No more internal file identifiers available. |
| 0x72 | 78.1 | The target internal file identifier is incorrect. |
| 0x75 | 78.1 | The IOCTL call made by the application program is not correct. |
| 0x76 | 78.1 | The verify-on-write switch parameter value is not correct. |
| 0x77 | 78.1 | The system does not support the command requested. |
| 0x78 | 78.1 | This function is not supported on this system. |
| 0x79 | 78.1 | The semaphore timeout period has expired. |
| 0x7a | 78.1 | The data area passed to a system call is too small. |
| 0x7b | 78.1 | The filename, directory name, or volume label syntax is incorrect. |
| 0x7c | 78.1 | The system call level is not correct. |
| 0x7d | 78.1 | The disk has no volume label. |
| 0x7e | 78.1 | The specified module could not be found. |
| 0x7f | 78.1 | The specified procedure could not be found. |
| 0x80 | 78.1 | There are no child processes to wait for. |
| 0x81 | 78.1 | The %1 application cannot be run in Win32 mode. |
| 0x82 | 78.1 | Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O. |
| 0x83 | 78.1 | An attempt was made to move the file pointer before the beginning of the file. |
| 0x84 | 78.1 | The file pointer cannot be set on the specified device or file. |
| 0x85 | 78.1 | A JOIN or SUBST command cannot be used for a drive that contains previously joined drives. |
| 0x86 | 78.1 | An attempt was made to use a JOIN or SUBST command on a drive that has already been joined. |
| 0x87 | 78.1 | An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted. |
| 0x88 | 78.1 | The system tried to delete the JOIN of a drive that is not joined. |
| 0x89 | 78.1 | The system tried to delete the substitution of a drive that is not substituted. |
| 0x8a | 78.1 | The system tried to join a drive to a directory on a joined drive. |
| 0x8b | 78.1 | The system tried to substitute a drive to a directory on a substituted drive. |
| 0x8c | 78.1 | The system tried to join a drive to a directory on a substituted drive. |
| 0x8d | 78.1 | The system tried to SUBST a drive to a directory on a joined drive. |
| 0x8e | 78.1 | The system cannot perform a JOIN or SUBST at this time. |
| 0x8f | 78.1 | The system cannot join or substitute a drive to or for a directory on the same drive. |
| 0x90 | 78.1 | The directory is not a subdirectory of the root directory. |
| 0x91 | 78.1 | The directory is not empty. |
| 0x92 | 78.1 | The path specified is being used in a substitute. |
| 0x93 | 78.1 | Not enough resources are available to process this command. |
| 0x94 | 78.1 | The path specified cannot be used at this time. |
| 0x95 | 78.1 | An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. |
| 0x96 | 78.1 | System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed. |
| 0x97 | 78.1 | The number of specified semaphore events for DosMuxSemWait is not correct. |
| 0x98 | 78.1 | DosMuxSemWait did not execute; too many semaphores are already set. |
| 0x99 | 78.1 | The DosMuxSemWait list is not correct. |
| 0x9a | 78.1 | The volume label you entered exceeds the label character limit of the target file system. |
| 0x9b | 78.1 | Cannot create another thread. |
| 0x9c | 78.1 | The recipient process has refused the signal. |
| 0x9d | 78.1 | The segment is already discarded and cannot be locked. |
| 0x9e | 78.1 | The segment is already unlocked. |
| 0x9f | 78.1 | The address for the thread ID is not correct. |
| 0xa0 | 78.1 | One or more arguments are not correct. |
| 0xa1 | 78.1 | The specified path is invalid. |
| 0xa2 | 78.1 | A signal is already pending. |
| 0xa4 | 78.1 | No more threads can be created in the system. |
| 0xa7 | 78.1 | Unable to lock a region of a file. |
| 0xaa | 78.1 | The requested resource is in use. |
| 0xad | 78.1 | A lock request was not outstanding for the supplied cancel region. |
| 0xae | 78.1 | The file system does not support atomic changes to the lock type. |
| 0xb4 | 78.1 | The system detected a segment number that was not correct. |
| 0xb6 | 78.1 | The operating system cannot run %1. |
| 0xb7 | 78.1 | Cannot create a file when that file already exists. |
| 0xba | 78.1 | The flag passed is not correct. |
| 0xbb | 78.1 | The specified system semaphore name was not found. |
| 0xbc | 78.1 | The operating system cannot run %1. |
| 0xbd | 78.1 | The operating system cannot run %1. |
| 0xbe | 78.1 | The operating system cannot run %1. |
| 0xbf | 78.1 | Cannot run %1 in Win32 mode. |
| 0xc0 | 78.1 | The operating system cannot run %1. |
| 0xc1 | 78.1 | %1 is not a valid Win32 application. |
| 0xc2 | 78.1 | The operating system cannot run %1. |
| 0xc3 | 78.1 | The operating system cannot run %1. |
| 0xc4 | 78.1 | The operating system cannot run this application program. |
| 0xc5 | 78.1 | The operating system is not presently configured to run this application. |
| 0xc6 | 78.1 | The operating system cannot run %1. |
| 0xc7 | 78.1 | The operating system cannot run this application program. |
| 0xc8 | 78.1 | The code segment cannot be greater than or equal to 64K. |
| 0xc9 | 78.1 | The operating system cannot run %1. |
| 0xca | 78.1 | The operating system cannot run %1. |
| 0xcb | 78.1 | The system could not find the environment option that was entered. |
| 0xcd | 78.1 | No process in the command subtree has a signal handler. |
| 0xce | 78.1 | The filename or extension is too long. |
| 0xcf | 78.1 | The ring 2 stack is in use. |
| 0xd0 | 78.1 | The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified. |
| 0xd1 | 78.1 | The signal being posted is not correct. |
| 0xd2 | 78.1 | The signal handler cannot be set. |
| 0xd4 | 78.1 | The segment is locked and cannot be reallocated. |
| 0xd6 | 78.1 | Too many dynamic-link modules are attached to this program or dynamic-link module. |
| 0xd7 | 78.1 | Cannot nest calls to LoadModule. |
| 0xd8 | 7 | This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher. |
| 0xd9 | 78.1 | The image file %1 is signed, unable to modify. |
| 0xda | 78.1 | The image file %1 is strong signed, unable to modify. |
| 0xdc | 78.1 | This file is checked out or locked for editing by another user. |
| 0xdd | 78.1 | The file must be checked out before saving changes. |
| 0xde | 78.1 | The file type being saved or retrieved has been blocked. |
| 0xdf | 78.1 | The file size exceeds the limit allowed and cannot be saved. |
| 0xe0 | 78.1 | 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. |
| 0xe1 | 7 | Operation did not complete successfully because the file contains a virus. |
| 0xe2 | 7 | This file contains a virus and cannot be opened. Due to the nature of this virus, the file has been removed from this location. |
| 0xe5 | 78.1 | The pipe is local. |
| 0xe6 | 78.1 | The pipe state is invalid. |
| 0xe7 | 78.1 | All pipe instances are busy. |
| 0xe8 | 78.1 | The pipe is being closed. |
| 0xe9 | 78.1 | No process is on the other end of the pipe. |
| 0xea | 78.1 | More data is available. |
| 0xf0 | 78.1 | The session was canceled. |
| 0xfe | 78.1 | The specified extended attribute name was invalid. |
| 0xff | 78.1 | The extended attributes are inconsistent. |
| 0x102 | 78.1 | The wait operation timed out. |
| 0x103 | 78.1 | No more data is available. |
| 0x10a | 78.1 | The copy functions cannot be used. |
| 0x10b | 78.1 | The directory name is invalid. |
| 0x113 | 78.1 | The extended attributes did not fit in the buffer. |
| 0x114 | 78.1 | The extended attribute file on the mounted file system is corrupt. |
| 0x115 | 78.1 | The extended attribute table file is full. |
| 0x116 | 78.1 | The specified extended attribute handle is invalid. |
| 0x11a | 78.1 | The mounted file system does not support extended attributes. |
| 0x120 | 78.1 | Attempt to release mutex not owned by caller. |
| 0x12a | 78.1 | Too many posts were made to a semaphore. |
| 0x12b | 78.1 | Only part of a ReadProcessMemory or WriteProcessMemory request was completed. |
| 0x12c | 78.1 | The oplock request is denied. |
| 0x12d | 78.1 | An invalid oplock acknowledgment was received by the system. |
| 0x12e | 78.1 | The volume is too fragmented to complete this operation. |
| 0x12f | 78.1 | The file cannot be opened because it is in the process of being deleted. |
| 0x130 | 78.1 | Short name settings may not be changed on this volume due to the global registry setting. |
| 0x131 | 78.1 | Short names are not enabled on this volume. |
| 0x132 | 78.1 | The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume. |
| 0x133 | 78.1 | A requested file lock operation cannot be processed due to an invalid byte range. |
| 0x134 | 78.1 | The subsystem needed to support the image type is not present. |
| 0x135 | 78.1 | The specified file already has a notification GUID associated with it. |
| 0x13d | 78.1 | The system cannot find message text for message number 0x%1 in the message file for %2. |
| 0x13e | 78.1 | The scope specified was not found. |
| 0x15e | 78.1 | No action was taken as a system reboot is required. |
| 0x15f | 78.1 | The shutdown operation failed. |
| 0x160 | 78.1 | The restart operation failed. |
| 0x161 | 78.1 | The maximum number of sessions has been reached. |
| 0x190 | 78.1 | The thread is already in background processing mode. |
| 0x191 | 78.1 | The thread is not in background processing mode. |
| 0x192 | 78.1 | The process is already in background processing mode. |
| 0x193 | 78.1 | The process is not in background processing mode. |
| 0x1e7 | 78.1 | Attempt to access invalid address. |
| 0x1f4 | 78.1 | User profile cannot be loaded. |
| 0x216 | 78.1 | Arithmetic result exceeded 32 bits. |
| 0x217 | 78.1 | There is a process on other end of the pipe. |
| 0x218 | 78.1 | Waiting for a process to open the other end of the pipe. |
| 0x219 | 78.1 | Application verifier has found an error in the current process. |
| 0x21a | 78.1 | An error occurred in the ABIOS subsystem. |
| 0x21b | 78.1 | A warning occurred in the WX86 subsystem. |
| 0x21c | 78.1 | An error occurred in the WX86 subsystem. |
| 0x21d | 78.1 | 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. |
| 0x21e | 78.1 | Unwind exception code. |
| 0x21f | 78.1 | An invalid or unaligned stack was encountered during an unwind operation. |
| 0x220 | 78.1 | An invalid unwind target was encountered during an unwind operation. |
| 0x221 | 78.1 | Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort |
| 0x222 | 78.1 | Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. |
| 0x223 | 78.1 | An attempt was made to lower a quota limit below the current usage. |
| 0x224 | 78.1 | An attempt was made to attach to a device that was already attached to another device. |
| 0x225 | 78.1 | An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. |
| 0x226 | 78.1 | Profiling not started. |
| 0x227 | 78.1 | Profiling not stopped. |
| 0x228 | 78.1 | The passed ACL did not contain the minimum required information. |
| 0x229 | 78.1 | The number of active profiling objects is at the maximum and no more may be started. |
| 0x22a | 78.1 | Used to indicate that an operation cannot continue without blocking for I/O. |
| 0x22b | 78.1 | Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process. |
| 0x22c | 78.1 | If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. |
| 0x22d | 78.1 | If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. |
| 0x22e | 78.1 | If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. |
| 0x22f | 78.1 | A malformed function table was encountered during an unwind operation. |
| 0x230 | 78.1 | Indicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system. This causes the protection attempt to fail, which may cause a file creation attempt to fail. |
| 0x231 | 78.1 | 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. |
| 0x233 | 78.1 | Indicates that the starting value for the LDT information was not an integral multiple of the selector size. |
| 0x234 | 78.1 | Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. |
| 0x235 | 78.1 | 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. |
| 0x236 | 78.1 | An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. |
| 0x237 | 78.1 | Page file quota was exceeded. |
| 0x238 | 78.1 | The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. |
| 0x239 | 78.1 | The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required. |
| 0x23a | 78.1 | 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. |
| 0x23b | 78.1 | {Privilege Failed} The I/O permissions for the process could not be changed. |
| 0x23c | 78.1 | {Application Exit by CTRL+C} The application terminated as a result of a CTRL+C. |
| 0x23d | 78.1 | {Missing System File} The required system file %hs is bad or missing. |
| 0x23e | 78.1 | {Application Error} The exception %s (0x8lx) occurred in the application at location 0x8lx. |
| 0x23f | 78.1 | {Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application. |
| 0x240 | 78.1 | {Unable to Create Paging File} The creation of the paging file %hs failed (%lx). The requested size was %ld. |
| 0x241 | 78.1 | 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. |
| 0x242 | 78.1 | {No Paging File Specified} No paging file was specified in the system configuration. |
| 0x243 | 78.1 | {EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present. |
| 0x244 | 78.1 | 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. |
| 0x245 | 78.1 | A Windows Server has an incorrect configuration. |
| 0x246 | 78.1 | 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. |
| 0x247 | 78.1 | The Unicode character is not defined in the Unicode character set installed on the system. |
| 0x248 | 78.1 | The paging file cannot be created on a floppy diskette. |
| 0x249 | 78.1 | The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected. |
| 0x24a | 78.1 | This operation is only allowed for the Primary Domain Controller of the domain. |
| 0x24b | 78.1 | An attempt was made to acquire a mutant such that its maximum count would have been exceeded. |
| 0x24c | 78.1 | A volume has been accessed for which a file system driver is required that has not yet been loaded. |
| 0x24d | 78.1 | {Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable. |
| 0x24e | 78.1 | {Unexpected Failure in DebugActiveProcess} An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error. |
| 0x24f | 78.1 | {Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x8x (0x8x 0x8x). The system has been shut down. |
| 0x250 | 78.1 | {Data Not Accepted} The TDI client could not handle the data received during an indication. |
| 0x251 | 78.1 | NTVDM encountered a hard error. |
| 0x252 | 78.1 | {Cancel Timeout} The driver %hs failed to complete a cancelled I/O request in the allotted time. |
| 0x253 | 78.1 | {Reply Message Mismatch} 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. |
| 0x254 | 78.1 | {Delayed Write Failed} Windows was unable to save all the data for the file %hs. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. |
| 0x255 | 78.1 | 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. |
| 0x256 | 78.1 | The stream is not a tiny stream. |
| 0x257 | 78.1 | The request must be handled by the stack overflow code. |
| 0x258 | 78.1 | 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. |
| 0x259 | 78.1 | 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. |
| 0x25a | 78.1 | The bucket array must be grown. Retry transaction after doing so. |
| 0x25b | 78.1 | The user/kernel marshalling buffer has overflowed. |
| 0x25c | 78.1 | The supplied variant structure contains invalid data. |
| 0x25d | 78.1 | The specified buffer contains ill-formed data. |
| 0x25e | 78.1 | {Audit Failed} An attempt to generate a security audit failed. |
| 0x25f | 78.1 | The timer resolution was not previously set by the current process. |
| 0x260 | 78.1 | There is insufficient account information to log you on. |
| 0x261 | 78.1 | {Invalid DLL Entrypoint} The dynamic link library %hs is not written correctly. The stack pointer has been left in an inconsistent state. 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. |
| 0x262 | 78.1 | {Invalid Service Callback Entrypoint} The %hs service is not written correctly. The stack pointer has been left in an inconsistent state. 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. |
| 0x263 | 78.1 | There is an IP address conflict with another system on the network |
| 0x264 | 78.1 | There is an IP address conflict with another system on the network |
| 0x265 | 78.1 | {Low On Registry Space} The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored. |
| 0x266 | 78.1 | A callback return system service cannot be executed when no callback is active. |
| 0x267 | 78.1 | The password provided is too short to meet the policy of your user account. Please choose a longer password. |
| 0x268 | 78.1 | The policy of your user account does not allow you to change passwords too frequently. This is done to prevent users from changing back to a familiar, but potentially discovered, password. If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned. |
| 0x269 | 78.1 | You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used. |
| 0x26a | 78.1 | The specified compression format is unsupported. |
| 0x26b | 78.1 | The specified hardware profile configuration is invalid. |
| 0x26c | 78.1 | The specified Plug and Play registry device path is invalid. |
| 0x26d | 78.1 | The specified quota list is internally inconsistent with its descriptor. |
| 0x26e | 78.1 | {Windows Evaluation Notification} 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. |
| 0x26f | 78.1 | {Illegal System DLL Relocation} The system DLL %hs was relocated in memory. The application will not run properly. 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. |
| 0x270 | 78.1 | {DLL Initialization Failed} The application failed to initialize because the window station is shutting down. |
| 0x271 | 78.1 | The validation process needs to continue on to the next step. |
| 0x272 | 78.1 | There are no more matches for the current index enumeration. |
| 0x273 | 78.1 | The range could not be added to the range list because of a conflict. |
| 0x274 | 78.1 | The server process is running under a SID different than that required by client. |
| 0x275 | 78.1 | A group marked use for deny only cannot be enabled. |
| 0x276 | 78.1 | {EXCEPTION} Multiple floating point faults. |
| 0x277 | 78.1 | {EXCEPTION} Multiple floating point traps. |
| 0x278 | 78.1 | The requested interface is not supported. |
| 0x279 | 78.1 | {System Standby Failed} The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. |
| 0x27a | 78.1 | The system file %1 has become corrupt and has been replaced. |
| 0x27b | 78.1 | {Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. |
| 0x27c | 78.1 | A device was removed so enumeration must be restarted. |
| 0x27d | 78.1 | {Fatal System Error} The system image %s is not properly signed. The file has been replaced with the signed file. The system has been shut down. |
| 0x27e | 78.1 | Device will not start without a reboot. |
| 0x27f | 78.1 | There is not enough power to complete the requested operation. |
| 0x280 | 78.1 | ERROR_MULTIPLE_FAULT_VIOLATION |
| 0x281 | 78.1 | The system is in the process of shutting down. |
| 0x282 | 78.1 | An attempt to remove a processes DebugPort was made, but a port was not already associated with the process. |
| 0x283 | 78.1 | This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |
| 0x284 | 78.1 | The specified range could not be found in the range list. |
| 0x286 | 78.1 | The driver was not loaded because the system is booting into safe mode. |
| 0x287 | 7 | The driver was not loaded because it failed it's initialization call. |
| 0x288 | 78.1 | The "%hs" encountered an error while applying power or reading the device configuration. This may be caused by a failure of your hardware or by a poor connection. |
| 0x289 | 78.1 | 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. |
| 0x28a | 78.1 | The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. |
| 0x28b | 78.1 | A Machine Check Error has occurred. Please check the system eventlog for additional information. |
| 0x28c | 78.1 | There was error [%2] processing the driver database. |
| 0x28d | 78.1 | System hive size has exceeded its limit. |
| 0x28e | 78.1 | The driver could not be loaded because a previous version of the driver is still in memory. |
| 0x28f | 78.1 | {Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. |
| 0x290 | 78.1 | The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. |
| 0x299 | 78.1 | The requested operation could not be completed due to a file system limitation |
| 0x29c | 78.1 | An assertion failure has occurred. |
| 0x29d | 78.1 | An error occurred in the ACPI subsystem. |
| 0x29e | 78.1 | WOW Assertion Error. |
| 0x29f | 78.1 | A device is missing in the system BIOS MPS table. This device will not be used. Please contact your system vendor for system BIOS update. |
| 0x2a0 | 78.1 | A translator failed to translate resources. |
| 0x2a1 | 78.1 | A IRQ translator failed to translate resources. |
| 0x2a2 | 78.1 | Driver %2 returned invalid ID for a child device (%3). |
| 0x2a3 | 78.1 | {Kernel Debugger Awakened} the system debugger was awakened by an interrupt. |
| 0x2a4 | 78.1 | {Handles Closed} Handles to objects have been automatically closed as a result of the requested operation. |
| 0x2a5 | 78.1 | {Too Much Information} The specified access control list (ACL) contained more information than was expected. |
| 0x2a6 | 78.1 | This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired). |
| 0x2a7 | 78.1 | {Media Changed} The media may have changed. |
| 0x2a8 | 78.1 | {GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. |
| 0x2a9 | 78.1 | The create operation stopped after reaching a symbolic link |
| 0x2aa | 78.1 | A long jump has been executed. |
| 0x2ab | 78.1 | The Plug and Play query operation was not successful. |
| 0x2ac | 78.1 | A frame consolidation has been executed. |
| 0x2ad | 78.1 | {Registry Hive Recovered} Registry hive (file): %hs was corrupted and it has been recovered. Some data might have been lost. |
| 0x2ae | 78.1 | 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? |
| 0x2af | 78.1 | 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? |
| 0x2b0 | 78.1 | Debugger did not handle the exception. |
| 0x2b1 | 78.1 | Debugger will reply later. |
| 0x2b2 | 78.1 | Debugger cannot provide handle. |
| 0x2b3 | 78.1 | Debugger terminated thread. |
| 0x2b4 | 78.1 | Debugger terminated process. |
| 0x2b5 | 78.1 | Debugger got control C. |
| 0x2b6 | 78.1 | Debugger printed exception on control C. |
| 0x2b7 | 78.1 | Debugger received RIP exception. |
| 0x2b8 | 78.1 | Debugger received control break. |
| 0x2b9 | 78.1 | Debugger command communication exception. |
| 0x2ba | 78.1 | {Object Exists} An attempt was made to create an object and the object name already existed. |
| 0x2bb | 78.1 | {Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. |
| 0x2bc | 78.1 | {Image Relocated} An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image. |
| 0x2bd | 78.1 | This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. |
| 0x2be | 78.1 | {Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments. |
| 0x2bf | 78.1 | {Invalid Current Directory} The process cannot switch to the startup current directory %hs. Select OK to set current directory to %hs, or select CANCEL to exit. |
| 0x2c0 | 78.1 | {Redundant Read} To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy. 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. |
| 0x2c1 | 78.1 | {Redundant Write} To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information. 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. |
| 0x2c2 | 78.1 | {Machine Type Mismatch} 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. |
| 0x2c3 | 78.1 | {Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later. |
| 0x2c4 | 78.1 | {Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system. |
| 0x2c5 | 78.1 | {Partial Expedited Data Received} 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. |
| 0x2c6 | 78.1 | {TDI Event Done} The TDI indication has completed successfully. |
| 0x2c7 | 78.1 | {TDI Event Pending} The TDI indication has entered the pending state. |
| 0x2c8 | 78.1 | Checking file system on %wZ |
| 0x2c9 | 78.1 | {Fatal Application Exit} %hs |
| 0x2ca | 78.1 | The specified registry key is referenced by a predefined handle. |
| 0x2cb | 78.1 | {Page Unlocked} The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process. |
| 0x2cc | 78.1 | %hs |
| 0x2cd | 78.1 | {Page Locked} One of the pages to lock was already locked. |
| 0x2ce | 78.1 | Application popup: %1 : %2 |
| 0x2cf | 78.1 | ERROR_ALREADY_WIN32 |
| 0x2d0 | 78.1 | {Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine. |
| 0x2d1 | 78.1 | A yield execution was performed and no thread was available to run. |
| 0x2d2 | 78.1 | The resumable flag to a timer API was ignored. |
| 0x2d3 | 78.1 | The arbiter has deferred arbitration of these resources to its parent |
| 0x2d4 | 78.1 | The inserted CardBus device cannot be started because of a configuration error on "%hs". |
| 0x2d5 | 78.1 | 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. |
| 0x2d6 | 78.1 | The system was put into hibernation. |
| 0x2d7 | 78.1 | The system was resumed from hibernation. |
| 0x2d8 | 78.1 | Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. |
| 0x2d9 | 78.1 | 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. |
| 0x2da | 78.1 | The system has awoken |
| 0x2db | 78.1 | ERROR_WAIT_1 |
| 0x2dc | 78.1 | ERROR_WAIT_2 |
| 0x2dd | 78.1 | ERROR_WAIT_3 |
| 0x2de | 78.1 | ERROR_WAIT_63 |
| 0x2df | 78.1 | ERROR_ABANDONED_WAIT_0 |
| 0x2e0 | 78.1 | ERROR_ABANDONED_WAIT_63 |
| 0x2e1 | 78.1 | ERROR_USER_APC |
| 0x2e2 | 78.1 | ERROR_KERNEL_APC |
| 0x2e3 | 78.1 | ERROR_ALERTED |
| 0x2e4 | 78.1 | The requested operation requires elevation. |
| 0x2e5 | 78.1 | A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x2e6 | 78.1 | An open/create operation completed while an oplock break is underway. |
| 0x2e7 | 78.1 | A new volume has been mounted by a file system. |
| 0x2e8 | 78.1 | This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed. |
| 0x2e9 | 78.1 | This indicates that a notify change request has been completed due to closing the handle which made the notify change request. |
| 0x2ea | 78.1 | {Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport. |
| 0x2eb | 78.1 | Page fault was a transition fault. |
| 0x2ec | 78.1 | Page fault was a demand zero fault. |
| 0x2ed | 78.1 | Page fault was a demand zero fault. |
| 0x2ee | 78.1 | Page fault was a demand zero fault. |
| 0x2ef | 78.1 | Page fault was satisfied by reading from a secondary storage device. |
| 0x2f0 | 78.1 | Cached page was locked during operation. |
| 0x2f1 | 78.1 | Crash dump exists in paging file. |
| 0x2f2 | 78.1 | Specified buffer contains all zeros. |
| 0x2f3 | 78.1 | A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x2f4 | 78.1 | The device has succeeded a query-stop and its resource requirements have changed. |
| 0x2f5 | 78.1 | The translator has translated these resources into the global space and no further translations should be performed. |
| 0x2f6 | 78.1 | A process being terminated has no threads to terminate. |
| 0x2f7 | 78.1 | The specified process is not part of a job. |
| 0x2f8 | 78.1 | The specified process is part of a job. |
| 0x2f9 | 78.1 | {Volume Shadow Copy Service} The system is now ready for hibernation. |
| 0x2fa | 78.1 | A file system or file system filter driver has successfully completed an FsFilter operation. |
| 0x2fb | 78.1 | The specified interrupt vector was already connected. |
| 0x2fc | 78.1 | The specified interrupt vector is still connected. |
| 0x2fd | 78.1 | An operation is blocked waiting for an oplock. |
| 0x2fe | 78.1 | Debugger handled exception |
| 0x2ff | 78.1 | Debugger continued |
| 0x300 | 78.1 | An exception occurred in a user mode callback and the kernel callback frame should be removed. |
| 0x301 | 78.1 | Compression is disabled for this volume. |
| 0x302 | 78.1 | The data provider cannot fetch backwards through a result set. |
| 0x303 | 78.1 | The data provider cannot scroll backwards through a result set. |
| 0x304 | 78.1 | The data provider requires that previously fetched data is released before asking for more data. |
| 0x305 | 78.1 | The data provider was not able to interpret the flags set for a column binding in an accessor. |
| 0x306 | 78.1 | One or more errors occurred while processing the request. |
| 0x307 | 78.1 | The implementation is not capable of performing the request. |
| 0x308 | 78.1 | The client of a component requested an operation which is not valid given the state of the component instance. |
| 0x309 | 78.1 | A version number could not be parsed. |
| 0x30a | 78.1 | The iterator's start position is invalid. |
| 0x30b | 78.1 | The hardware has reported an uncorrectable memory error. |
| 0x30c | 78.1 | The attempted operation required self healing to be enabled. |
| 0x30d | 78.1 | The Desktop heap encountered an error while allocating session memory. There is more information in the system event log. |
| 0x30e | 78.1 | The system power state is transitioning from %2 to %3. |
| 0x30f | 78.1 | The system power state is transitioning from %2 to %3 but could enter %4. |
| 0x310 | 78.1 | A thread is getting dispatched with MCA EXCEPTION because of MCA. |
| 0x311 | 78.1 | Access to %1 is monitored by policy rule %2. |
| 0x312 | 78.1 | Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0x313 | 78.1 | A valid hibernation file has been invalidated and should be abandoned. |
| 0x314 | 78.1 | {Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere. |
| 0x315 | 78.1 | {Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere. |
| 0x316 | 78.1 | {Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error may be caused if the device has been removed or the media is write-protected. |
| 0x317 | 78.1 | The resources required for this device conflict with the MCFG table. |
| 0x320 | 78.1 | The oplock that was associated with this handle is now associated with a different handle. |
| 0x321 | 78.1 | An oplock of the requested level cannot be granted. An oplock of a lower level may be available. |
| 0x322 | 78.1 | 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. |
| 0x323 | 78.1 | The handle with which this oplock was associated has been closed. The oplock is now broken. |
| 0x324 | 78.1 | The specified access control entry (ACE) does not contain a condition. |
| 0x325 | 78.1 | The specified access control entry (ACE) contains an invalid condition. |
| 0x3e2 | 78.1 | Access to the extended attribute was denied. |
| 0x3e3 | 78.1 | The I/O operation has been aborted because of either a thread exit or an application request. |
| 0x3e4 | 78.1 | Overlapped I/O event is not in a signaled state. |
| 0x3e5 | 78.1 | Overlapped I/O operation is in progress. |
| 0x3e6 | 78.1 | Invalid access to memory location. |
| 0x3e7 | 78.1 | Error performing inpage operation. |
| 0x3e9 | 78.1 | Recursion too deep; the stack overflowed. |
| 0x3ea | 78.1 | The window cannot act on the sent message. |
| 0x3eb | 78.1 | Cannot complete this function. |
| 0x3ec | 78.1 | Invalid flags. |
| 0x3ed | 78.1 | The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted. |
| 0x3ee | 78.1 | The volume for a file has been externally altered so that the opened file is no longer valid. |
| 0x3ef | 78.1 | The requested operation cannot be performed in full-screen mode. |
| 0x3f0 | 78.1 | An attempt was made to reference a token that does not exist. |
| 0x3f1 | 78.1 | The configuration registry database is corrupt. |
| 0x3f2 | 78.1 | The configuration registry key is invalid. |
| 0x3f3 | 78.1 | The configuration registry key could not be opened. |
| 0x3f4 | 78.1 | The configuration registry key could not be read. |
| 0x3f5 | 78.1 | The configuration registry key could not be written. |
| 0x3f6 | 78.1 | One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. |
| 0x3f7 | 78.1 | 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. |
| 0x3f8 | 78.1 | 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. |
| 0x3f9 | 78.1 | The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format. |
| 0x3fa | 78.1 | Illegal operation attempted on a registry key that has been marked for deletion. |
| 0x3fb | 78.1 | System could not allocate the required space in a registry log. |
| 0x3fc | 78.1 | Cannot create a symbolic link in a registry key that already has subkeys or values. |
| 0x3fd | 78.1 | Cannot create a stable subkey under a volatile parent key. |
| 0x3fe | 78.1 | 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. |
| 0x41b | 78.1 | A stop control has been sent to a service that other running services are dependent on. |
| 0x41c | 78.1 | The requested control is not valid for this service. |
| 0x41d | 78.1 | The service did not respond to the start or control request in a timely fashion. |
| 0x41e | 78.1 | A thread could not be created for the service. |
| 0x41f | 78.1 | The service database is locked. |
| 0x420 | 78.1 | An instance of the service is already running. |
| 0x421 | 78.1 | The account name is invalid or does not exist, or the password is invalid for the account name specified. |
| 0x422 | 78.1 | The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. |
| 0x423 | 78.1 | Circular service dependency was specified. |
| 0x424 | 78.1 | The specified service does not exist as an installed service. |
| 0x425 | 78.1 | The service cannot accept control messages at this time. |
| 0x426 | 78.1 | The service has not been started. |
| 0x427 | 78.1 | The service process could not connect to the service controller. |
| 0x428 | 78.1 | An exception occurred in the service when handling the control request. |
| 0x429 | 78.1 | The database specified does not exist. |
| 0x42a | 78.1 | The service has returned a service-specific error code. |
| 0x42b | 78.1 | The process terminated unexpectedly. |
| 0x42c | 78.1 | The dependency service or group failed to start. |
| 0x42d | 78.1 | The service did not start due to a logon failure. |
| 0x42e | 78.1 | After starting, the service hung in a start-pending state. |
| 0x42f | 78.1 | The specified service database lock is invalid. |
| 0x430 | 78.1 | The specified service has been marked for deletion. |
| 0x431 | 78.1 | The specified service already exists. |
| 0x432 | 78.1 | The system is currently running with the last-known-good configuration. |
| 0x433 | 78.1 | The dependency service does not exist or has been marked for deletion. |
| 0x434 | 78.1 | The current boot has already been accepted for use as the last-known-good control set. |
| 0x435 | 78.1 | No attempts to start the service have been made since the last boot. |
| 0x436 | 78.1 | The name is already in use as either a service name or a service display name. |
| 0x437 | 78.1 | The account specified for this service is different from the account specified for other services running in the same process. |
| 0x438 | 78.1 | Failure actions can only be set for Win32 services, not for drivers. |
| 0x439 | 78.1 | This service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service's process terminates unexpectedly. |
| 0x43a | 78.1 | No recovery program has been configured for this service. |
| 0x43b | 78.1 | The executable program that this service is configured to run in does not implement the service. |
| 0x43c | 78.1 | This service cannot be started in Safe Mode |
| 0x44c | 78.1 | The physical end of the tape has been reached. |
| 0x44d | 78.1 | A tape access reached a filemark. |
| 0x44e | 78.1 | The beginning of the tape or a partition was encountered. |
| 0x44f | 78.1 | A tape access reached the end of a set of files. |
| 0x450 | 78.1 | No more data is on the tape. |
| 0x451 | 78.1 | Tape could not be partitioned. |
| 0x452 | 78.1 | When accessing a new tape of a multivolume partition, the current block size is incorrect. |
| 0x453 | 78.1 | Tape partition information could not be found when loading a tape. |
| 0x454 | 78.1 | Unable to lock the media eject mechanism. |
| 0x455 | 78.1 | Unable to unload the media. |
| 0x456 | 78.1 | The media in the drive may have changed. |
| 0x457 | 78.1 | The I/O bus was reset. |
| 0x458 | 78.1 | No media in drive. |
| 0x459 | 78.1 | No mapping for the Unicode character exists in the target multi-byte code page. |
| 0x45a | 78.1 | A dynamic link library (DLL) initialization routine failed. |
| 0x45b | 78.1 | A system shutdown is in progress. |
| 0x45c | 78.1 | Unable to abort the system shutdown because no shutdown was in progress. |
| 0x45d | 78.1 | The request could not be performed because of an I/O device error. |
| 0x45e | 78.1 | No serial device was successfully initialized. The serial driver will unload. |
| 0x45f | 78.1 | 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. |
| 0x460 | 78.1 | A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.) |
| 0x461 | 78.1 | A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.) |
| 0x462 | 78.1 | No ID address mark was found on the floppy disk. |
| 0x463 | 78.1 | Mismatch between the floppy disk sector ID field and the floppy disk controller track address. |
| 0x464 | 78.1 | The floppy disk controller reported an error that is not recognized by the floppy disk driver. |
| 0x465 | 78.1 | The floppy disk controller returned inconsistent results in its registers. |
| 0x466 | 78.1 | While accessing the hard disk, a recalibrate operation failed, even after retries. |
| 0x467 | 78.1 | While accessing the hard disk, a disk operation failed even after retries. |
| 0x468 | 78.1 | While accessing the hard disk, a disk controller reset was needed, but even that failed. |
| 0x469 | 78.1 | Physical end of tape encountered. |
| 0x46a | 78.1 | Not enough server storage is available to process this command. |
| 0x46b | 78.1 | A potential deadlock condition has been detected. |
| 0x46c | 78.1 | The base address or the file offset specified does not have the proper alignment. |
| 0x474 | 78.1 | An attempt to change the system power state was vetoed by another application or driver. |
| 0x475 | 78.1 | The system BIOS failed an attempt to change the system power state. |
| 0x476 | 78.1 | An attempt was made to create more links on a file than the file system supports. |
| 0x47e | 78.1 | The specified program requires a newer version of Windows. |
| 0x47f | 78.1 | The specified program is not a Windows or MS-DOS program. |
| 0x480 | 78.1 | Cannot start more than one instance of the specified program. |
| 0x481 | 78.1 | The specified program was written for an earlier version of Windows. |
| 0x482 | 78.1 | One of the library files needed to run this application is damaged. |
| 0x483 | 78.1 | No application is associated with the specified file for this operation. |
| 0x484 | 78.1 | An error occurred in sending the command to the application. |
| 0x485 | 78.1 | One of the library files needed to run this application cannot be found. |
| 0x486 | 78.1 | The current process has used all of its system allowance of handles for Window Manager objects. |
| 0x487 | 78.1 | The message can be used only with synchronous operations. |
| 0x488 | 78.1 | The indicated source element has no media. |
| 0x489 | 78.1 | The indicated destination element already contains media. |
| 0x48a | 78.1 | The indicated element does not exist. |
| 0x48b | 78.1 | The indicated element is part of a magazine that is not present. |
| 0x48c | 78.1 | The indicated device requires reinitialization due to hardware errors. |
| 0x48d | 78.1 | The device has indicated that cleaning is required before further operations are attempted. |
| 0x48e | 78.1 | The device has indicated that its door is open. |
| 0x48f | 78.1 | The device is not connected. |
| 0x490 | 78.1 | Element not found. |
| 0x491 | 78.1 | There was no match for the specified key in the index. |
| 0x492 | 78.1 | The property set specified does not exist on the object. |
| 0x493 | 78.1 | The point passed to GetMouseMovePoints is not in the buffer. |
| 0x494 | 78.1 | The tracking (workstation) service is not running. |
| 0x495 | 78.1 | The Volume ID could not be found. |
| 0x497 | 78.1 | Unable to remove the file to be replaced. |
| 0x498 | 78.1 | Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name. |
| 0x499 | 78.1 | Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name. |
| 0x49a | 78.1 | The volume change journal is being deleted. |
| 0x49b | 78.1 | The volume change journal is not active. |
| 0x49c | 78.1 | A file was found, but it may not be the correct file. |
| 0x49d | 78.1 | The journal entry has been deleted from the journal. |
| 0x4a6 | 78.1 | A system shutdown has already been scheduled. |
| 0x4a7 | 78.1 | The system shutdown cannot be initiated because there are other users logged on to the computer. |
| 0x4b0 | 78.1 | The specified device name is invalid. |
| 0x4b1 | 78.1 | The device is not currently connected but it is a remembered connection. |
| 0x4b2 | 78.1 | The local device name has a remembered connection to another network resource. |
| 0x4b3 | 78.1 | 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. |
| 0x4b4 | 78.1 | The specified network provider name is invalid. |
| 0x4b5 | 78.1 | Unable to open the network connection profile. |
| 0x4b6 | 78.1 | The network connection profile is corrupted. |
| 0x4b7 | 78.1 | Cannot enumerate a noncontainer. |
| 0x4b8 | 78.1 | An extended error has occurred. |
| 0x4b9 | 78.1 | The format of the specified group name is invalid. |
| 0x4ba | 78.1 | The format of the specified computer name is invalid. |
| 0x4bb | 78.1 | The format of the specified event name is invalid. |
| 0x4bc | 78.1 | The format of the specified domain name is invalid. |
| 0x4bd | 78.1 | The format of the specified service name is invalid. |
| 0x4be | 78.1 | The format of the specified network name is invalid. |
| 0x4bf | 78.1 | The format of the specified share name is invalid. |
| 0x4c0 | 78.1 | The format of the specified password is invalid. |
| 0x4c1 | 78.1 | The format of the specified message name is invalid. |
| 0x4c2 | 78.1 | The format of the specified message destination is invalid. |
| 0x4c3 | 78.1 | 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. |
| 0x4c4 | 78.1 | An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. |
| 0x4c5 | 78.1 | The workgroup or domain name is already in use by another computer on the network. |
| 0x4c6 | 78.1 | The network is not present or not started. |
| 0x4c7 | 78.1 | The operation was canceled by the user. |
| 0x4c8 | 78.1 | The requested operation cannot be performed on a file with a user-mapped section open. |
| 0x4c9 | 78.1 | The remote computer refused the network connection. |
| 0x4ca | 78.1 | The network connection was gracefully closed. |
| 0x4cb | 78.1 | The network transport endpoint already has an address associated with it. |
| 0x4cc | 78.1 | An address has not yet been associated with the network endpoint. |
| 0x4cd | 78.1 | An operation was attempted on a nonexistent network connection. |
| 0x4ce | 78.1 | An invalid operation was attempted on an active network connection. |
| 0x4cf | 78.1 | The network location cannot be reached. For information about network troubleshooting, see Windows Help. |
| 0x4d0 | 78.1 | The network location cannot be reached. For information about network troubleshooting, see Windows Help. |
| 0x4d1 | 78.1 | The network location cannot be reached. For information about network troubleshooting, see Windows Help. |
| 0x4d2 | 78.1 | No service is operating at the destination network endpoint on the remote system. |
| 0x4d3 | 78.1 | The request was aborted. |
| 0x4d4 | 78.1 | The network connection was aborted by the local system. |
| 0x4d5 | 78.1 | The operation could not be completed. A retry should be performed. |
| 0x4d6 | 78.1 | A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. |
| 0x4d7 | 78.1 | Attempting to log in during an unauthorized time of day for this account. |
| 0x4d8 | 78.1 | The account is not authorized to log in from this station. |
| 0x4d9 | 78.1 | The network address could not be used for the operation requested. |
| 0x4da | 78.1 | The service is already registered. |
| 0x4db | 78.1 | The specified service does not exist. |
| 0x4dc | 78.1 | The operation being requested was not performed because the user has not been authenticated. |
| 0x4dd | 78.1 | The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. |
| 0x4de | 78.1 | Continue with work in progress. |
| 0x4df | 78.1 | An attempt was made to perform an initialization operation when initialization has already been completed. |
| 0x4e0 | 78.1 | No more local devices. |
| 0x4e1 | 78.1 | The specified site does not exist. |
| 0x4e2 | 78.1 | A domain controller with the specified name already exists. |
| 0x4e3 | 78.1 | This operation is supported only when you are connected to the server. |
| 0x4e4 | 78.1 | The group policy framework should call the extension even if there are no changes. |
| 0x4e5 | 78.1 | The specified user does not have a valid profile. |
| 0x4e6 | 78.1 | This operation is not supported on a computer running Windows Server 2003 for Small Business Server |
| 0x4e7 | 78.1 | The server machine is shutting down. |
| 0x4e8 | 78.1 | The remote system is not available. For information about network troubleshooting, see Windows Help. |
| 0x4e9 | 78.1 | The security identifier provided is not from an account domain. |
| 0x4ea | 78.1 | The security identifier provided does not have a domain component. |
| 0x4eb | 78.1 | AppHelp dialog canceled thus preventing the application from starting. |
| 0x4ec | 78.1 | This program is blocked by group policy. For more information, contact your system administrator. |
| 0x4ed | 78.1 | A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific. |
| 0x4ee | 78.1 | The share is currently offline or does not exist. |
| 0x4ef | 78.1 | The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log. |
| 0x4f0 | 78.1 | The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. |
| 0x4f1 | 7 | The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you. |
| 0x4f7 | 78.1 | The machine is locked and cannot be shut down without the force option. |
| 0x4f9 | 78.1 | An application-defined callback gave invalid data when called. |
| 0x4fa | 78.1 | The group policy framework should call the extension in the synchronous foreground policy refresh. |
| 0x4fb | 78.1 | This driver has been blocked from loading |
| 0x4fc | 78.1 | A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. |
| 0x4fd | 78.1 | Windows cannot open this program since it has been disabled. |
| 0x4fe | 78.1 | Windows cannot open this program because the license enforcement system has been tampered with or become corrupted. |
| 0x4ff | 78.1 | A transaction recover failed. |
| 0x500 | 78.1 | The current thread has already been converted to a fiber. |
| 0x501 | 78.1 | The current thread has already been converted from a fiber. |
| 0x502 | 78.1 | 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. |
| 0x503 | 78.1 | Data present in one of the parameters is more than the function can operate on. |
| 0x504 | 78.1 | An attempt to do an operation on a debug object failed because the object is in the process of being deleted. |
| 0x505 | 78.1 | An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. |
| 0x506 | 78.1 | %1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. |
| 0x507 | 78.1 | Insufficient information exists to identify the cause of failure. |
| 0x508 | 78.1 | The parameter passed to a C runtime function is incorrect. |
| 0x509 | 78.1 | The operation occurred beyond the valid data length of the file. |
| 0x50a | 78.1 | 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. |
| 0x50b | 78.1 | The process hosting the driver for this device has been terminated. |
| 0x50c | 78.1 | An operation attempted to exceed an implementation-defined limit. |
| 0x50d | 78.1 | Either the target process, or the target thread's containing process, is a protected process. |
| 0x50e | 78.1 | The service notification client is lagging too far behind the current state of services in the machine. |
| 0x50f | 78.1 | The requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator. |
| 0x510 | 78.1 | The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. |
| 0x511 | 78.1 | A privilege that the service requires to function properly does not exist in the service account configuration. 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. |
| 0x512 | 78.1 | A thread involved in this operation appears to be unresponsive. |
| 0x513 | 78.1 | Indicates a particular Security ID may not be assigned as the label of an object. |
| 0x514 | 78.1 | Not all privileges or groups referenced are assigned to the caller. |
| 0x515 | 78.1 | Some mapping between account names and security IDs was not done. |
| 0x516 | 78.1 | No system quota limits are specifically set for this account. |
| 0x517 | 78.1 | No encryption key is available. A well-known encryption key was returned. |
| 0x518 | 78.1 | The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. |
| 0x519 | 78.1 | The revision level is unknown. |
| 0x51a | 78.1 | Indicates two revision levels are incompatible. |
| 0x51b | 78.1 | This security ID may not be assigned as the owner of this object. |
| 0x51c | 78.1 | This security ID may not be assigned as the primary group of an object. |
| 0x51d | 78.1 | An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. |
| 0x51e | 78.1 | The group may not be disabled. |
| 0x51f | 78.1 | There are currently no logon servers available to service the logon request. |
| 0x520 | 78.1 | A specified logon session does not exist. It may already have been terminated. |
| 0x521 | 78.1 | A specified privilege does not exist. |
| 0x522 | 78.1 | A required privilege is not held by the client. |
| 0x523 | 78.1 | The name provided is not a properly formed account name. |
| 0x524 | 78.1 | The specified account already exists. |
| 0x525 | 78.1 | The specified account does not exist. |
| 0x526 | 78.1 | The specified group already exists. |
| 0x527 | 78.1 | The specified group does not exist. |
| 0x528 | 78.1 | 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. |
| 0x529 | 78.1 | The specified user account is not a member of the specified group account. |
| 0x52a | 7 | The last remaining administration account cannot be disabled or deleted. |
| 0x52b | 78.1 | Unable to update the password. The value provided as the current password is incorrect. |
| 0x52c | 78.1 | Unable to update the password. The value provided for the new password contains values that are not allowed in passwords. |
| 0x52d | 78.1 | Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. |
| 0x52e | 7 | Logon failure: unknown user name or bad password. |
| 0x52f | 7 | Logon failure: user account restriction. Possible reasons are blank passwords not allowed, logon hour restrictions, or a policy restriction has been enforced. |
| 0x530 | 7 | Logon failure: account logon time restriction violation. |
| 0x531 | 7 | Logon failure: user not allowed to log on to this computer. |
| 0x532 | 7 | Logon failure: the specified account password has expired. |
| 0x533 | 7 | Logon failure: account currently disabled. |
| 0x534 | 78.1 | No mapping between account names and security IDs was done. |
| 0x535 | 78.1 | Too many local user identifiers (LUIDs) were requested at one time. |
| 0x536 | 78.1 | No more local user identifiers (LUIDs) are available. |
| 0x537 | 78.1 | The subauthority part of a security ID is invalid for this particular use. |
| 0x538 | 78.1 | The access control list (ACL) structure is invalid. |
| 0x539 | 78.1 | The security ID structure is invalid. |
| 0x53a | 78.1 | The security descriptor structure is invalid. |
| 0x53c | 78.1 | The inherited access control list (ACL) or access control entry (ACE) could not be built. |
| 0x53d | 78.1 | The server is currently disabled. |
| 0x53e | 78.1 | The server is currently enabled. |
| 0x53f | 78.1 | The value provided was an invalid value for an identifier authority. |
| 0x540 | 78.1 | No more memory is available for security information updates. |
| 0x541 | 78.1 | The specified attributes are invalid, or incompatible with the attributes for the group as a whole. |
| 0x542 | 78.1 | Either a required impersonation level was not provided, or the provided impersonation level is invalid. |
| 0x543 | 78.1 | Cannot open an anonymous level security token. |
| 0x544 | 78.1 | The validation information class requested was invalid. |
| 0x545 | 78.1 | The type of the token is inappropriate for its attempted use. |
| 0x546 | 78.1 | Unable to perform a security operation on an object that has no associated security. |
| 0x547 | 78.1 | Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. |
| 0x548 | 78.1 | The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. |
| 0x549 | 78.1 | The domain was in the wrong state to perform the security operation. |
| 0x54a | 78.1 | This operation is only allowed for the Primary Domain Controller of the domain. |
| 0x54b | 78.1 | The specified domain either does not exist or could not be contacted. |
| 0x54c | 78.1 | The specified domain already exists. |
| 0x54d | 78.1 | An attempt was made to exceed the limit on the number of domains per server. |
| 0x54e | 78.1 | Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk. |
| 0x54f | 78.1 | An internal error occurred. |
| 0x550 | 78.1 | Generic access types were contained in an access mask which should already be mapped to nongeneric types. |
| 0x551 | 78.1 | A security descriptor is not in the right format (absolute or self-relative). |
| 0x552 | 78.1 | The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. |
| 0x553 | 78.1 | Cannot start a new logon session with an ID that is already in use. |
| 0x554 | 78.1 | A specified authentication package is unknown. |
| 0x555 | 78.1 | The logon session is not in a state that is consistent with the requested operation. |
| 0x556 | 78.1 | The logon session ID is already in use. |
| 0x557 | 78.1 | A logon request contained an invalid logon type value. |
| 0x558 | 78.1 | Unable to impersonate using a named pipe until data has been read from that pipe. |
| 0x559 | 78.1 | The transaction state of a registry subtree is incompatible with the requested operation. |
| 0x55a | 78.1 | An internal security database corruption has been encountered. |
| 0x55b | 78.1 | Cannot perform this operation on built-in accounts. |
| 0x55c | 78.1 | Cannot perform this operation on this built-in special group. |
| 0x55d | 78.1 | Cannot perform this operation on this built-in special user. |
| 0x55e | 78.1 | The user cannot be removed from a group because the group is currently the user's primary group. |
| 0x55f | 78.1 | The token is already in use as a primary token. |
| 0x560 | 78.1 | The specified local group does not exist. |
| 0x561 | 78.1 | The specified account name is not a member of the group. |
| 0x562 | 78.1 | The specified account name is already a member of the group. |
| 0x563 | 78.1 | The specified local group already exists. |
| 0x564 | 78.1 | Logon failure: the user has not been granted the requested logon type at this computer. |
| 0x565 | 78.1 | The maximum number of secrets that may be stored in a single system has been exceeded. |
| 0x566 | 78.1 | The length of a secret exceeds the maximum length allowed. |
| 0x567 | 78.1 | The local security authority database contains an internal inconsistency. |
| 0x568 | 78.1 | During a logon attempt, the user's security context accumulated too many security IDs. |
| 0x569 | 78.1 | Logon failure: the user has not been granted the requested logon type at this computer. |
| 0x56a | 78.1 | A cross-encrypted password is necessary to change a user password. |
| 0x56b | 78.1 | A member could not be added to or removed from the local group because the member does not exist. |
| 0x56c | 78.1 | A new member could not be added to a local group because the member has the wrong account type. |
| 0x56d | 78.1 | Too many security IDs have been specified. |
| 0x56e | 78.1 | A cross-encrypted password is necessary to change this user password. |
| 0x56f | 78.1 | Indicates an ACL contains no inheritable components. |
| 0x570 | 78.1 | The file or directory is corrupted and unreadable. |
| 0x571 | 78.1 | The disk structure is corrupted and unreadable. |
| 0x572 | 78.1 | There is no user session key for the specified logon session. |
| 0x573 | 78.1 | 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. |
| 0x574 | 7 | Logon Failure: The target account name is incorrect. |
| 0x575 | 78.1 | Mutual Authentication failed. The server's password is out of date at the domain controller. |
| 0x576 | 78.1 | There is a time and/or date difference between the client and server. |
| 0x577 | 78.1 | This operation cannot be performed on the current domain. |
| 0x578 | 78.1 | Invalid window handle. |
| 0x579 | 78.1 | Invalid menu handle. |
| 0x57a | 78.1 | Invalid cursor handle. |
| 0x57b | 78.1 | Invalid accelerator table handle. |
| 0x57c | 78.1 | Invalid hook handle. |
| 0x57d | 78.1 | Invalid handle to a multiple-window position structure. |
| 0x57e | 78.1 | Cannot create a top-level child window. |
| 0x57f | 78.1 | Cannot find window class. |
| 0x580 | 78.1 | Invalid window; it belongs to other thread. |
| 0x581 | 78.1 | Hot key is already registered. |
| 0x582 | 78.1 | Class already exists. |
| 0x583 | 78.1 | Class does not exist. |
| 0x584 | 78.1 | Class still has open windows. |
| 0x585 | 78.1 | Invalid index. |
| 0x586 | 78.1 | Invalid icon handle. |
| 0x587 | 78.1 | Using private DIALOG window words. |
| 0x588 | 78.1 | The list box identifier was not found. |
| 0x589 | 78.1 | No wildcards were found. |
| 0x58a | 78.1 | Thread does not have a clipboard open. |
| 0x58b | 78.1 | Hot key is not registered. |
| 0x58c | 78.1 | The window is not a valid dialog window. |
| 0x58d | 78.1 | Control ID not found. |
| 0x58e | 78.1 | Invalid message for a combo box because it does not have an edit control. |
| 0x58f | 78.1 | The window is not a combo box. |
| 0x590 | 78.1 | Height must be less than 256. |
| 0x591 | 78.1 | Invalid device context (DC) handle. |
| 0x592 | 78.1 | Invalid hook procedure type. |
| 0x593 | 78.1 | Invalid hook procedure. |
| 0x594 | 78.1 | Cannot set nonlocal hook without a module handle. |
| 0x595 | 78.1 | This hook procedure can only be set globally. |
| 0x596 | 78.1 | The journal hook procedure is already installed. |
| 0x597 | 78.1 | The hook procedure is not installed. |
| 0x598 | 78.1 | Invalid message for single-selection list box. |
| 0x599 | 78.1 | LB_SETCOUNT sent to non-lazy list box. |
| 0x59a | 78.1 | This list box does not support tab stops. |
| 0x59b | 78.1 | Cannot destroy object created by another thread. |
| 0x59c | 78.1 | Child windows cannot have menus. |
| 0x59d | 78.1 | The window does not have a system menu. |
| 0x59e | 78.1 | Invalid message box style. |
| 0x59f | 78.1 | Invalid system-wide (SPI_*) parameter. |
| 0x5a0 | 78.1 | Screen already locked. |
| 0x5a1 | 78.1 | All handles to windows in a multiple-window position structure must have the same parent. |
| 0x5a2 | 78.1 | The window is not a child window. |
| 0x5a3 | 78.1 | Invalid GW_* command. |
| 0x5a4 | 78.1 | Invalid thread identifier. |
| 0x5a5 | 78.1 | Cannot process a message from a window that is not a multiple document interface (MDI) window. |
| 0x5a6 | 78.1 | Popup menu already active. |
| 0x5a7 | 78.1 | The window does not have scroll bars. |
| 0x5a8 | 78.1 | Scroll bar range cannot be greater than MAXLONG. |
| 0x5a9 | 78.1 | Cannot show or remove the window in the way specified. |
| 0x5aa | 78.1 | Insufficient system resources exist to complete the requested service. |
| 0x5ab | 78.1 | Insufficient system resources exist to complete the requested service. |
| 0x5ac | 78.1 | Insufficient system resources exist to complete the requested service. |
| 0x5ad | 78.1 | Insufficient quota to complete the requested service. |
| 0x5ae | 78.1 | Insufficient quota to complete the requested service. |
| 0x5af | 78.1 | The paging file is too small for this operation to complete. |
| 0x5b0 | 78.1 | A menu item was not found. |
| 0x5b1 | 78.1 | Invalid keyboard layout handle. |
| 0x5b2 | 78.1 | Hook type not allowed. |
| 0x5b3 | 78.1 | This operation requires an interactive window station. |
| 0x5b4 | 78.1 | This operation returned because the timeout period expired. |
| 0x5b5 | 78.1 | Invalid monitor handle. |
| 0x5b6 | 78.1 | Incorrect size argument. |
| 0x5b7 | 78.1 | The symbolic link cannot be followed because its type is disabled. |
| 0x5b8 | 78.1 | This application does not support the current operation on symbolic links. |
| 0x5b9 | 78.1 | Windows was unable to parse the requested XML data. |
| 0x5ba | 78.1 | An error was encountered while processing an XML digital signature. |
| 0x5bb | 78.1 | This application must be restarted. |
| 0x5bc | 78.1 | The caller made the connection request in the wrong routing compartment. |
| 0x5bd | 78.1 | There was an AuthIP failure when attempting to connect to the remote host. |
| 0x5be | 78.1 | Insufficient NVRAM resources exist to complete the requested service. A reboot might be required. |
| 0x5dc | 78.1 | The event log file is corrupted. |
| 0x5dd | 78.1 | No event log file could be opened, so the event logging service did not start. |
| 0x5de | 78.1 | The event log file is full. |
| 0x5df | 78.1 | The event log file has changed between read operations. |
| 0x60e | 78.1 | The specified task name is invalid. |
| 0x60f | 78.1 | The specified task index is invalid. |
| 0x610 | 78.1 | The specified thread is already joining a task. |
| 0x641 | 78.1 | 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. |
| 0x642 | 78.1 | User cancelled installation. |
| 0x643 | 78.1 | Fatal error during installation. |
| 0x644 | 78.1 | Installation suspended, incomplete. |
| 0x645 | 78.1 | This action is only valid for products that are currently installed. |
| 0x646 | 78.1 | Feature ID not registered. |
| 0x647 | 78.1 | Component ID not registered. |
| 0x648 | 78.1 | Unknown property. |
| 0x649 | 78.1 | Handle is in an invalid state. |
| 0x64a | 78.1 | The configuration data for this product is corrupt. Contact your support personnel. |
| 0x64b | 78.1 | Component qualifier not present. |
| 0x64c | 78.1 | The installation source for this product is not available. Verify that the source exists and that you can access it. |
| 0x64d | 78.1 | 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. |
| 0x64e | 78.1 | Product is uninstalled. |
| 0x64f | 78.1 | SQL query syntax invalid or unsupported. |
| 0x650 | 78.1 | Record field does not exist. |
| 0x651 | 78.1 | The device has been removed. |
| 0x652 | 78.1 | Another installation is already in progress. Complete that installation before proceeding with this install. |
| 0x653 | 78.1 | 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. |
| 0x654 | 78.1 | This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. |
| 0x655 | 78.1 | There was an error starting the Windows Installer service user interface. Contact your support personnel. |
| 0x656 | 78.1 | Error opening installation log file. Verify that the specified log file location exists and that you can write to it. |
| 0x657 | 78.1 | The language of this installation package is not supported by your system. |
| 0x658 | 78.1 | Error applying transforms. Verify that the specified transform paths are valid. |
| 0x659 | 78.1 | This installation is forbidden by system policy. Contact your system administrator. |
| 0x65a | 78.1 | Function could not be executed. |
| 0x65b | 78.1 | Function failed during execution. |
| 0x65c | 78.1 | Invalid or unknown table specified. |
| 0x65d | 78.1 | Data supplied is of wrong type. |
| 0x65e | 78.1 | Data of this type is not supported. |
| 0x65f | 78.1 | The Windows Installer service failed to start. Contact your support personnel. |
| 0x660 | 78.1 | 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. |
| 0x661 | 78.1 | This installation package is not supported by this processor type. Contact your product vendor. |
| 0x662 | 78.1 | Component not used on this computer. |
| 0x663 | 78.1 | 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. |
| 0x664 | 78.1 | This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package. |
| 0x665 | 78.1 | 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. |
| 0x666 | 78.1 | 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. |
| 0x667 | 78.1 | Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. |
| 0x668 | 78.1 | 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. |
| 0x669 | 78.1 | The requested operation completed successfully. The system will be restarted so the changes can take effect. |
| 0x66a | 78.1 | 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. |
| 0x66b | 78.1 | The update package is not permitted by software restriction policy. |
| 0x66c | 78.1 | One or more customizations are not permitted by software restriction policy. |
| 0x66d | 78.1 | The Windows Installer does not permit installation from a Remote Desktop Connection. |
| 0x66e | 78.1 | Uninstallation of the update package is not supported. |
| 0x66f | 78.1 | The update is not applied to this product. |
| 0x670 | 78.1 | No valid sequence could be found for the set of updates. |
| 0x671 | 78.1 | Update removal was disallowed by policy. |
| 0x672 | 78.1 | The XML update data is invalid. |
| 0x673 | 78.1 | Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update. |
| 0x674 | 78.1 | 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. |
| 0x675 | 78.1 | A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
| 0x6a4 | 78.1 | The string binding is invalid. |
| 0x6a5 | 78.1 | The binding handle is not the correct type. |
| 0x6a6 | 78.1 | The binding handle is invalid. |
| 0x6a7 | 78.1 | The RPC protocol sequence is not supported. |
| 0x6a8 | 78.1 | The RPC protocol sequence is invalid. |
| 0x6a9 | 78.1 | The string universal unique identifier (UUID) is invalid. |
| 0x6aa | 78.1 | The endpoint format is invalid. |
| 0x6ab | 78.1 | The network address is invalid. |
| 0x6ac | 78.1 | No endpoint was found. |
| 0x6ad | 78.1 | The timeout value is invalid. |
| 0x6ae | 78.1 | The object universal unique identifier (UUID) was not found. |
| 0x6af | 78.1 | The object universal unique identifier (UUID) has already been registered. |
| 0x6b0 | 78.1 | The type universal unique identifier (UUID) has already been registered. |
| 0x6b1 | 78.1 | The RPC server is already listening. |
| 0x6b2 | 78.1 | No protocol sequences have been registered. |
| 0x6b3 | 78.1 | The RPC server is not listening. |
| 0x6b4 | 78.1 | The manager type is unknown. |
| 0x6b5 | 78.1 | The interface is unknown. |
| 0x6b6 | 78.1 | There are no bindings. |
| 0x6b7 | 78.1 | There are no protocol sequences. |
| 0x6b8 | 78.1 | The endpoint cannot be created. |
| 0x6b9 | 78.1 | Not enough resources are available to complete this operation. |
| 0x6ba | 78.1 | The RPC server is unavailable. |
| 0x6bb | 78.1 | The RPC server is too busy to complete this operation. |
| 0x6bc | 78.1 | The network options are invalid. |
| 0x6bd | 78.1 | There are no remote procedure calls active on this thread. |
| 0x6be | 78.1 | The remote procedure call failed. |
| 0x6bf | 78.1 | The remote procedure call failed and did not execute. |
| 0x6c0 | 78.1 | A remote procedure call (RPC) protocol error occurred. |
| 0x6c1 | 78.1 | Access to the HTTP proxy is denied. |
| 0x6c2 | 78.1 | The transfer syntax is not supported by the RPC server. |
| 0x6c4 | 78.1 | The universal unique identifier (UUID) type is not supported. |
| 0x6c5 | 78.1 | The tag is invalid. |
| 0x6c6 | 78.1 | The array bounds are invalid. |
| 0x6c7 | 78.1 | The binding does not contain an entry name. |
| 0x6c8 | 78.1 | The name syntax is invalid. |
| 0x6c9 | 78.1 | The name syntax is not supported. |
| 0x6cb | 78.1 | No network address is available to use to construct a universal unique identifier (UUID). |
| 0x6cc | 78.1 | The endpoint is a duplicate. |
| 0x6cd | 78.1 | The authentication type is unknown. |
| 0x6ce | 78.1 | The maximum number of calls is too small. |
| 0x6cf | 78.1 | The string is too long. |
| 0x6d0 | 78.1 | The RPC protocol sequence was not found. |
| 0x6d1 | 78.1 | The procedure number is out of range. |
| 0x6d2 | 78.1 | The binding does not contain any authentication information. |
| 0x6d3 | 78.1 | The authentication service is unknown. |
| 0x6d4 | 78.1 | The authentication level is unknown. |
| 0x6d5 | 78.1 | The security context is invalid. |
| 0x6d6 | 78.1 | The authorization service is unknown. |
| 0x6d7 | 78.1 | The entry is invalid. |
| 0x6d8 | 78.1 | The server endpoint cannot perform the operation. |
| 0x6d9 | 78.1 | There are no more endpoints available from the endpoint mapper. |
| 0x6da | 78.1 | No interfaces have been exported. |
| 0x6db | 78.1 | The entry name is incomplete. |
| 0x6dc | 78.1 | The version option is invalid. |
| 0x6dd | 78.1 | There are no more members. |
| 0x6de | 78.1 | There is nothing to unexport. |
| 0x6df | 78.1 | The interface was not found. |
| 0x6e0 | 78.1 | The entry already exists. |
| 0x6e1 | 78.1 | The entry is not found. |
| 0x6e2 | 78.1 | The name service is unavailable. |
| 0x6e3 | 78.1 | The network address family is invalid. |
| 0x6e4 | 78.1 | The requested operation is not supported. |
| 0x6e5 | 78.1 | No security context is available to allow impersonation. |
| 0x6e6 | 78.1 | An internal error occurred in a remote procedure call (RPC). |
| 0x6e7 | 78.1 | The RPC server attempted an integer division by zero. |
| 0x6e8 | 78.1 | An addressing error occurred in the RPC server. |
| 0x6e9 | 78.1 | A floating-point operation at the RPC server caused a division by zero. |
| 0x6ea | 78.1 | A floating-point underflow occurred at the RPC server. |
| 0x6eb | 78.1 | A floating-point overflow occurred at the RPC server. |
| 0x6ec | 78.1 | The list of RPC servers available for the binding of auto handles has been exhausted. |
| 0x6ed | 78.1 | Unable to open the character translation table file. |
| 0x6ee | 78.1 | The file containing the character translation table has fewer than 512 bytes. |
| 0x6ef | 78.1 | A null context handle was passed from the client to the host during a remote procedure call. |
| 0x6f1 | 78.1 | The context handle changed during a remote procedure call. |
| 0x6f2 | 78.1 | The binding handles passed to a remote procedure call do not match. |
| 0x6f3 | 78.1 | The stub is unable to get the remote procedure call handle. |
| 0x6f4 | 78.1 | A null reference pointer was passed to the stub. |
| 0x6f5 | 78.1 | The enumeration value is out of range. |
| 0x6f6 | 78.1 | The byte count is too small. |
| 0x6f7 | 78.1 | The stub received bad data. |
| 0x6f8 | 78.1 | The supplied user buffer is not valid for the requested operation. |
| 0x6f9 | 78.1 | The disk media is not recognized. It may not be formatted. |
| 0x6fa | 78.1 | The workstation does not have a trust secret. |
| 0x6fb | 78.1 | The security database on the server does not have a computer account for this workstation trust relationship. |
| 0x6fc | 78.1 | The trust relationship between the primary domain and the trusted domain failed. |
| 0x6fd | 78.1 | The trust relationship between this workstation and the primary domain failed. |
| 0x6fe | 78.1 | The network logon failed. |
| 0x6ff | 78.1 | A remote procedure call is already in progress for this thread. |
| 0x700 | 78.1 | An attempt was made to logon, but the network logon service was not started. |
| 0x701 | 78.1 | The user's account has expired. |
| 0x702 | 78.1 | The redirector is in use and cannot be unloaded. |
| 0x703 | 78.1 | The specified printer driver is already installed. |
| 0x704 | 78.1 | The specified port is unknown. |
| 0x705 | 78.1 | The printer driver is unknown. |
| 0x706 | 78.1 | The print processor is unknown. |
| 0x707 | 78.1 | The specified separator file is invalid. |
| 0x708 | 78.1 | The specified priority is invalid. |
| 0x709 | 78.1 | The printer name is invalid. |
| 0x70a | 78.1 | The printer already exists. |
| 0x70b | 78.1 | The printer command is invalid. |
| 0x70c | 78.1 | The specified datatype is invalid. |
| 0x70d | 78.1 | The environment specified is invalid. |
| 0x70e | 78.1 | There are no more bindings. |
| 0x70f | 78.1 | The account used is an interdomain trust account. Use your global user account or local user account to access this server. |
| 0x710 | 78.1 | The account used is a computer account. Use your global user account or local user account to access this server. |
| 0x711 | 78.1 | The account used is a server trust account. Use your global user account or local user account to access this server. |
| 0x712 | 78.1 | The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain. |
| 0x713 | 78.1 | The server is in use and cannot be unloaded. |
| 0x714 | 78.1 | The specified image file did not contain a resource section. |
| 0x715 | 78.1 | The specified resource type cannot be found in the image file. |
| 0x716 | 78.1 | The specified resource name cannot be found in the image file. |
| 0x717 | 78.1 | The specified resource language ID cannot be found in the image file. |
| 0x718 | 78.1 | Not enough quota is available to process this command. |
| 0x719 | 78.1 | No interfaces have been registered. |
| 0x71a | 78.1 | The remote procedure call was cancelled. |
| 0x71b | 78.1 | The binding handle does not contain all required information. |
| 0x71c | 78.1 | A communications failure occurred during a remote procedure call. |
| 0x71d | 78.1 | The requested authentication level is not supported. |
| 0x71e | 78.1 | No principal name registered. |
| 0x71f | 78.1 | The error specified is not a valid Windows RPC error code. |
| 0x720 | 78.1 | A UUID that is valid only on this computer has been allocated. |
| 0x721 | 78.1 | A security package specific error occurred. |
| 0x722 | 78.1 | Thread is not canceled. |
| 0x723 | 78.1 | Invalid operation on the encoding/decoding handle. |
| 0x724 | 78.1 | Incompatible version of the serializing package. |
| 0x725 | 78.1 | Incompatible version of the RPC stub. |
| 0x726 | 78.1 | The RPC pipe object is invalid or corrupted. |
| 0x727 | 78.1 | An invalid operation was attempted on an RPC pipe object. |
| 0x728 | 78.1 | Unsupported RPC pipe version. |
| 0x729 | 78.1 | HTTP proxy server rejected the connection because the cookie authentication failed. |
| 0x76a | 78.1 | The group member was not found. |
| 0x76b | 78.1 | The endpoint mapper database entry could not be created. |
| 0x76c | 78.1 | The object universal unique identifier (UUID) is the nil UUID. |
| 0x76d | 78.1 | The specified time is invalid. |
| 0x76e | 78.1 | The specified form name is invalid. |
| 0x76f | 78.1 | The specified form size is invalid. |
| 0x770 | 78.1 | The specified printer handle is already being waited on |
| 0x771 | 78.1 | The specified printer has been deleted. |
| 0x772 | 78.1 | The state of the printer is invalid. |
| 0x773 | 7 | The user's password must be changed before logging on the first time. |
| 0x774 | 78.1 | Could not find the domain controller for this domain. |
| 0x775 | 78.1 | The referenced account is currently locked out and may not be logged on to. |
| 0x776 | 78.1 | The object exporter specified was not found. |
| 0x777 | 78.1 | The object specified was not found. |
| 0x778 | 78.1 | The object resolver set specified was not found. |
| 0x779 | 78.1 | Some data remains to be sent in the request buffer. |
| 0x77a | 78.1 | Invalid asynchronous remote procedure call handle. |
| 0x77b | 78.1 | Invalid asynchronous RPC call handle for this operation. |
| 0x77c | 78.1 | The RPC pipe object has already been closed. |
| 0x77d | 78.1 | The RPC call completed before all pipes were processed. |
| 0x77e | 78.1 | No more data is available from the RPC pipe. |
| 0x77f | 78.1 | No site name is available for this machine. |
| 0x780 | 78.1 | The file cannot be accessed by the system. |
| 0x781 | 78.1 | The name of the file cannot be resolved by the system. |
| 0x782 | 78.1 | The entry is not of the expected type. |
| 0x783 | 78.1 | Not all object UUIDs could be exported to the specified entry. |
| 0x784 | 78.1 | Interface could not be exported to the specified entry. |
| 0x785 | 78.1 | The specified profile entry could not be added. |
| 0x786 | 78.1 | The specified profile element could not be added. |
| 0x787 | 78.1 | The specified profile element could not be removed. |
| 0x788 | 78.1 | The group element could not be added. |
| 0x789 | 78.1 | The group element could not be removed. |
| 0x78a | 78.1 | The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers. |
| 0x78b | 78.1 | The context has expired and can no longer be used. |
| 0x78c | 78.1 | The current user's delegated trust creation quota has been exceeded. |
| 0x78d | 78.1 | The total delegated trust creation quota has been exceeded. |
| 0x78e | 78.1 | The current user's delegated trust deletion quota has been exceeded. |
| 0x78f | 7 | Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine. |
| 0x790 | 78.1 | Remote connections to the Print Spooler are blocked by a policy set on your machine. |
| 0x791 | 7 | Logon Failure: Authentication failed because NTLM authentication has been disabled. |
| 0x7d0 | 78.1 | The pixel format is invalid. |
| 0x7d1 | 78.1 | The specified driver is invalid. |
| 0x7d2 | 78.1 | The window style or class attribute is invalid for this operation. |
| 0x7d3 | 78.1 | The requested metafile operation is not supported. |
| 0x7d4 | 78.1 | The requested transformation operation is not supported. |
| 0x7d5 | 78.1 | The requested clipping operation is not supported. |
| 0x7da | 78.1 | The specified color management module is invalid. |
| 0x7db | 78.1 | The specified color profile is invalid. |
| 0x7dc | 78.1 | The specified tag was not found. |
| 0x7dd | 78.1 | A required tag is not present. |
| 0x7de | 78.1 | The specified tag is already present. |
| 0x7df | 78.1 | The specified color profile is not associated with the specified device. |
| 0x7e0 | 78.1 | The specified color profile was not found. |
| 0x7e1 | 78.1 | The specified color space is invalid. |
| 0x7e2 | 78.1 | Image Color Management is not enabled. |
| 0x7e3 | 78.1 | There was an error while deleting the color transform. |
| 0x7e4 | 78.1 | The specified color transform is invalid. |
| 0x7e5 | 78.1 | The specified transform does not match the bitmap's color space. |
| 0x7e6 | 78.1 | The specified named color index is not present in the profile. |
| 0x7e7 | 78.1 | The specified profile is intended for a device of a different type than the specified device. |
| 0x83c | 78.1 | The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified. |
| 0x83d | 78.1 | The network connection was made successfully using default credentials. |
| 0x89a | 78.1 | The specified username is invalid. |
| 0x8ca | 78.1 | This network connection does not exist. |
| 0x961 | 78.1 | This network connection has files open or requests pending. |
| 0x962 | 78.1 | Active connections still exist. |
| 0x964 | 78.1 | The device is in use by an active process and cannot be disconnected. |
| 0xbb8 | 78.1 | The specified print monitor is unknown. |
| 0xbb9 | 78.1 | The specified printer driver is currently in use. |
| 0xbba | 78.1 | The spool file was not found. |
| 0xbbb | 78.1 | A StartDocPrinter call was not issued. |
| 0xbbc | 78.1 | An AddJob call was not issued. |
| 0xbbd | 78.1 | The specified print processor has already been installed. |
| 0xbbe | 78.1 | The specified print monitor has already been installed. |
| 0xbbf | 78.1 | The specified print monitor does not have the required functions. |
| 0xbc0 | 78.1 | The specified print monitor is currently in use. |
| 0xbc1 | 78.1 | The requested operation is not allowed when there are jobs queued to the printer. |
| 0xbc2 | 78.1 | The requested operation is successful. Changes will not be effective until the system is rebooted. |
| 0xbc3 | 78.1 | The requested operation is successful. Changes will not be effective until the service is restarted. |
| 0xbc4 | 78.1 | No printers were found. |
| 0xbc5 | 78.1 | The printer driver is known to be unreliable. |
| 0xbc6 | 78.1 | The printer driver is known to harm the system. |
| 0xbc7 | 78.1 | The specified printer driver package is currently in use. |
| 0xbc8 | 78.1 | Unable to find a core driver package that is required by the printer driver package. |
| 0xbc9 | 78.1 | The requested operation failed. A system reboot is required to roll back changes made. |
| 0xbca | 78.1 | The requested operation failed. A system reboot has been initiated to roll back changes made. |
| 0xbcb | 78.1 | The specified printer driver was not found on the system and needs to be downloaded. |
| 0xbcc | 78.1 | The requested print job has failed to print. A print system update requires the job to be resubmitted. |
| 0xf6e | 78.1 | Reissue the given operation as a cached IO operation |
| 0xfa0 | 78.1 | WINS encountered an error while processing the command. |
| 0xfa1 | 78.1 | The local WINS cannot be deleted. |
| 0xfa2 | 78.1 | The importation from the file failed. |
| 0xfa3 | 78.1 | The backup failed. Was a full backup done before? |
| 0xfa4 | 78.1 | The backup failed. Check the directory to which you are backing the database. |
| 0xfa5 | 78.1 | The name does not exist in the WINS database. |
| 0xfa6 | 78.1 | Replication with a nonconfigured partner is not allowed. |
| 0xfd2 | 78.1 | The version of the supplied content information is not supported. |
| 0xfd3 | 78.1 | The supplied content information is malformed. |
| 0xfd4 | 78.1 | The requested data cannot be found in local or peer caches. |
| 0xfd5 | 78.1 | No more data is available or required. |
| 0xfd6 | 78.1 | The supplied object has not been initialized. |
| 0xfd7 | 78.1 | The supplied object has already been initialized. |
| 0xfd8 | 78.1 | A shutdown operation is already in progress. |
| 0xfd9 | 78.1 | The supplied object has already been invalidated. |
| 0xfda | 78.1 | An element already exists and was not replaced. |
| 0xfdb | 78.1 | Can not cancel the requested operation as it has already been completed. |
| 0xfdc | 78.1 | Can not perform the reqested operation because it has already been carried out. |
| 0xfdd | 78.1 | An operation accessed data beyond the bounds of valid data. |
| 0xfde | 78.1 | The requested version is not supported. |
| 0xfdf | 78.1 | A configuration value is invalid. |
| 0xfe0 | 78.1 | The SKU is not licensed. |
| 0xfe1 | 78.1 | PeerDist Service is still initializing and will be available shortly. |
| 0x1004 | 78.1 | 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. |
| 0x1068 | 78.1 | The GUID passed was not recognized as valid by a WMI data provider. |
| 0x1069 | 78.1 | The instance name passed was not recognized as valid by a WMI data provider. |
| 0x106a | 78.1 | The data item ID passed was not recognized as valid by a WMI data provider. |
| 0x106b | 78.1 | The WMI request could not be completed and should be retried. |
| 0x106c | 78.1 | The WMI data provider could not be located. |
| 0x106d | 78.1 | The WMI data provider references an instance set that has not been registered. |
| 0x106e | 78.1 | The WMI data block or event notification has already been enabled. |
| 0x106f | 78.1 | The WMI data block is no longer available. |
| 0x1070 | 78.1 | The WMI data service is not available. |
| 0x1071 | 78.1 | The WMI data provider failed to carry out the request. |
| 0x1072 | 78.1 | The WMI MOF information is not valid. |
| 0x1073 | 78.1 | The WMI registration information is not valid. |
| 0x1074 | 78.1 | The WMI data block or event notification has already been disabled. |
| 0x1075 | 78.1 | The WMI data item or data block is read only. |
| 0x1076 | 78.1 | The WMI data item or data block could not be changed. |
| 0x10cc | 78.1 | The media identifier does not represent a valid medium. |
| 0x10cd | 78.1 | The library identifier does not represent a valid library. |
| 0x10ce | 78.1 | The media pool identifier does not represent a valid media pool. |
| 0x10cf | 78.1 | The drive and medium are not compatible or exist in different libraries. |
| 0x10d0 | 78.1 | The medium currently exists in an offline library and must be online to perform this operation. |
| 0x10d1 | 78.1 | The operation cannot be performed on an offline library. |
| 0x10d2 | 78.1 | The library, drive, or media pool is empty. |
| 0x10d3 | 78.1 | The library, drive, or media pool must be empty to perform this operation. |
| 0x10d4 | 78.1 | No media is currently available in this media pool or library. |
| 0x10d5 | 78.1 | A resource required for this operation is disabled. |
| 0x10d6 | 78.1 | The media identifier does not represent a valid cleaner. |
| 0x10d7 | 78.1 | The drive cannot be cleaned or does not support cleaning. |
| 0x10d8 | 78.1 | The object identifier does not represent a valid object. |
| 0x10d9 | 78.1 | Unable to read from or write to the database. |
| 0x10da | 78.1 | The database is full. |
| 0x10db | 78.1 | The medium is not compatible with the device or media pool. |
| 0x10dc | 78.1 | The resource required for this operation does not exist. |
| 0x10dd | 78.1 | The operation identifier is not valid. |
| 0x10de | 78.1 | The media is not mounted or ready for use. |
| 0x10df | 78.1 | The device is not ready for use. |
| 0x10e0 | 78.1 | The operator or administrator has refused the request. |
| 0x10e1 | 78.1 | The drive identifier does not represent a valid drive. |
| 0x10e2 | 78.1 | Library is full. No slot is available for use. |
| 0x10e3 | 78.1 | The transport cannot access the medium. |
| 0x10e4 | 78.1 | Unable to load the medium into the drive. |
| 0x10e5 | 78.1 | Unable to retrieve the drive status. |
| 0x10e6 | 78.1 | Unable to retrieve the slot status. |
| 0x10e7 | 78.1 | Unable to retrieve status about the transport. |
| 0x10e8 | 78.1 | Cannot use the transport because it is already in use. |
| 0x10e9 | 78.1 | Unable to open or close the inject/eject port. |
| 0x10ea | 78.1 | Unable to eject the medium because it is in a drive. |
| 0x10eb | 78.1 | A cleaner slot is already reserved. |
| 0x10ec | 78.1 | A cleaner slot is not reserved. |
| 0x10ed | 78.1 | The cleaner cartridge has performed the maximum number of drive cleanings. |
| 0x10ee | 78.1 | Unexpected on-medium identifier. |
| 0x10ef | 78.1 | The last remaining item in this group or resource cannot be deleted. |
| 0x10f0 | 78.1 | The message provided exceeds the maximum size allowed for this parameter. |
| 0x10f1 | 78.1 | The volume contains system or paging files. |
| 0x10f2 | 78.1 | The media type cannot be removed from this library since at least one drive in the library reports it can support this media type. |
| 0x10f3 | 78.1 | This offline media cannot be mounted on this system since no enabled drives are present which can be used. |
| 0x10f4 | 78.1 | A cleaner cartridge is present in the tape library. |
| 0x10f5 | 78.1 | Cannot use the inject/eject port because it is not empty. |
| 0x10fe | 78.1 | This file is currently not available for use on this computer. |
| 0x10ff | 78.1 | The remote storage service is not operational at this time. |
| 0x1100 | 78.1 | The remote storage service encountered a media error. |
| 0x1126 | 78.1 | The file or directory is not a reparse point. |
| 0x1127 | 78.1 | The reparse point attribute cannot be set because it conflicts with an existing attribute. |
| 0x1128 | 78.1 | The data present in the reparse point buffer is invalid. |
| 0x1129 | 78.1 | The tag present in the reparse point buffer is invalid. |
| 0x112a | 78.1 | There is a mismatch between the tag specified in the request and the tag present in the reparse point. |
| 0x1194 | 78.1 | Single Instance Storage is not available on this volume. |
| 0x1389 | 78.1 | The operation cannot be completed because other resources are dependent on this resource. |
| 0x138a | 78.1 | The cluster resource dependency cannot be found. |
| 0x138b | 78.1 | The cluster resource cannot be made dependent on the specified resource because it is already dependent. |
| 0x138c | 78.1 | The cluster resource is not online. |
| 0x138d | 78.1 | A cluster node is not available for this operation. |
| 0x138e | 78.1 | The cluster resource is not available. |
| 0x138f | 78.1 | The cluster resource could not be found. |
| 0x1390 | 78.1 | The cluster is being shut down. |
| 0x1391 | 78.1 | A cluster node cannot be evicted from the cluster unless the node is down or it is the last node. |
| 0x1392 | 78.1 | The object already exists. |
| 0x1393 | 78.1 | The object is already in the list. |
| 0x1394 | 78.1 | The cluster group is not available for any new requests. |
| 0x1395 | 78.1 | The cluster group could not be found. |
| 0x1396 | 78.1 | The operation could not be completed because the cluster group is not online. |
| 0x1397 | 78.1 | 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. |
| 0x1398 | 78.1 | 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. |
| 0x1399 | 78.1 | The cluster resource could not be created in the specified resource monitor. |
| 0x139a | 78.1 | The cluster resource could not be brought online by the resource monitor. |
| 0x139b | 78.1 | The operation could not be completed because the cluster resource is online. |
| 0x139c | 78.1 | The cluster resource could not be deleted or brought offline because it is the quorum resource. |
| 0x139d | 78.1 | The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. |
| 0x139e | 78.1 | The cluster software is shutting down. |
| 0x139f | 78.1 | The group or resource is not in the correct state to perform the requested operation. |
| 0x13a0 | 78.1 | The properties were stored but not all changes will take effect until the next time the resource is brought online. |
| 0x13a1 | 78.1 | The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. |
| 0x13a2 | 78.1 | The cluster resource could not be deleted since it is a core resource. |
| 0x13a3 | 78.1 | The quorum resource failed to come online. |
| 0x13a4 | 78.1 | The quorum log could not be created or mounted successfully. |
| 0x13a5 | 78.1 | The cluster log is corrupt. |
| 0x13a6 | 78.1 | The record could not be written to the cluster log since it exceeds the maximum size. |
| 0x13a7 | 78.1 | The cluster log exceeds its maximum size. |
| 0x13a8 | 78.1 | No checkpoint record was found in the cluster log. |
| 0x13a9 | 78.1 | The minimum required disk space needed for logging is not available. |
| 0x13aa | 78.1 | The cluster node failed to take control of the quorum resource because the resource is owned by another active node. |
| 0x13ab | 78.1 | A cluster network is not available for this operation. |
| 0x13ac | 78.1 | A cluster node is not available for this operation. |
| 0x13ad | 78.1 | All cluster nodes must be running to perform this operation. |
| 0x13ae | 78.1 | A cluster resource failed. |
| 0x13af | 78.1 | The cluster node is not valid. |
| 0x13b0 | 78.1 | The cluster node already exists. |
| 0x13b1 | 78.1 | A node is in the process of joining the cluster. |
| 0x13b2 | 78.1 | The cluster node was not found. |
| 0x13b3 | 78.1 | The cluster local node information was not found. |
| 0x13b4 | 78.1 | The cluster network already exists. |
| 0x13b5 | 78.1 | The cluster network was not found. |
| 0x13b6 | 78.1 | The cluster network interface already exists. |
| 0x13b7 | 78.1 | The cluster network interface was not found. |
| 0x13b8 | 78.1 | The cluster request is not valid for this object. |
| 0x13b9 | 78.1 | The cluster network provider is not valid. |
| 0x13ba | 78.1 | The cluster node is down. |
| 0x13bb | 78.1 | The cluster node is not reachable. |
| 0x13bc | 78.1 | The cluster node is not a member of the cluster. |
| 0x13bd | 78.1 | A cluster join operation is not in progress. |
| 0x13be | 78.1 | The cluster network is not valid. |
| 0x13c0 | 78.1 | The cluster node is up. |
| 0x13c1 | 78.1 | The cluster IP address is already in use. |
| 0x13c2 | 78.1 | The cluster node is not paused. |
| 0x13c3 | 78.1 | No cluster security context is available. |
| 0x13c4 | 78.1 | The cluster network is not configured for internal cluster communication. |
| 0x13c5 | 78.1 | The cluster node is already up. |
| 0x13c6 | 78.1 | The cluster node is already down. |
| 0x13c7 | 78.1 | The cluster network is already online. |
| 0x13c8 | 78.1 | The cluster network is already offline. |
| 0x13c9 | 78.1 | The cluster node is already a member of the cluster. |
| 0x13ca | 78.1 | 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. |
| 0x13cb | 78.1 | One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network. |
| 0x13cc | 7 | This operation cannot be performed on the cluster resource as it the quorum resource. You may not bring the quorum resource offline or modify its possible owners list. |
| 0x13cd | 78.1 | The cluster quorum resource is not allowed to have any dependencies. |
| 0x13ce | 78.1 | The cluster node is paused. |
| 0x13cf | 78.1 | The cluster resource cannot be brought online. The owner node cannot run this resource. |
| 0x13d0 | 78.1 | The cluster node is not ready to perform the requested operation. |
| 0x13d1 | 78.1 | The cluster node is shutting down. |
| 0x13d2 | 78.1 | The cluster join operation was aborted. |
| 0x13d3 | 78.1 | The cluster join operation failed due to incompatible software versions between the joining node and its sponsor. |
| 0x13d4 | 78.1 | This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor. |
| 0x13d5 | 78.1 | The system configuration changed during the cluster join or form operation. The join or form operation was aborted. |
| 0x13d6 | 78.1 | The specified resource type was not found. |
| 0x13d7 | 78.1 | 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. |
| 0x13d8 | 78.1 | 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. |
| 0x13d9 | 78.1 | No authentication package could be registered with the RPC server. |
| 0x13da | 78.1 | 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. |
| 0x13db | 78.1 | 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. |
| 0x13dc | 78.1 | 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. |
| 0x13dd | 78.1 | A non locker code got a request to reserve the lock for making global updates. |
| 0x13de | 78.1 | The quorum disk could not be located by the cluster service. |
| 0x13df | 78.1 | The backed up cluster database is possibly corrupt. |
| 0x13e0 | 78.1 | A DFS root already exists in this cluster node. |
| 0x13e1 | 78.1 | An attempt to modify a resource property failed because it conflicts with another existing property. |
| 0x1702 | 78.1 | An operation was attempted that is incompatible with the current membership state of the node. |
| 0x1703 | 78.1 | The quorum resource does not contain the quorum log. |
| 0x1704 | 78.1 | The membership engine requested shutdown of the cluster service on this node. |
| 0x1705 | 78.1 | The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node. |
| 0x1706 | 78.1 | A matching cluster network for the specified IP address could not be found. |
| 0x1707 | 78.1 | The actual data type of the property did not match the expected data type of the property. |
| 0x1708 | 78.1 | 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. |
| 0x1709 | 78.1 | Two or more parameter values specified for a resource's properties are in conflict. |
| 0x170a | 78.1 | This computer cannot be made a member of a cluster. |
| 0x170b | 78.1 | This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed. |
| 0x170c | 78.1 | 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. |
| 0x170d | 78.1 | The cluster configuration action has already been committed. |
| 0x170e | 78.1 | The cluster configuration action could not be rolled back. |
| 0x170f | 78.1 | The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node. |
| 0x1710 | 78.1 | One or more nodes in the cluster are running a version of Windows that does not support this operation. |
| 0x1711 | 78.1 | The name of the corresponding computer account doesn't match the Network Name for this resource. |
| 0x1712 | 78.1 | No network adapters are available. |
| 0x1713 | 78.1 | The cluster node has been poisoned. |
| 0x1714 | 78.1 | The group is unable to accept the request since it is moving to another node. |
| 0x1715 | 78.1 | The resource type cannot accept the request since is too busy performing another operation. |
| 0x1716 | 78.1 | The call to the cluster resource DLL timed out. |
| 0x1717 | 78.1 | 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. |
| 0x1718 | 78.1 | An internal cluster error occurred. A call to an invalid function was attempted. |
| 0x1719 | 78.1 | A parameter value is out of acceptable range. |
| 0x171a | 78.1 | A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required. |
| 0x171b | 78.1 | An invalid cluster registry operation was attempted. |
| 0x171c | 78.1 | An input string of characters is not properly terminated. |
| 0x171d | 78.1 | An input string of characters is not in a valid format for the data it represents. |
| 0x171e | 78.1 | An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress. |
| 0x171f | 78.1 | An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress. |
| 0x1720 | 78.1 | An internal cluster error occurred. Data was not properly initialized. |
| 0x1721 | 78.1 | An error occurred while reading from a stream of data. An unexpected number of bytes was returned. |
| 0x1722 | 78.1 | An error occurred while writing to a stream of data. The required number of bytes could not be written. |
| 0x1723 | 78.1 | An error occurred while deserializing a stream of cluster data. |
| 0x1724 | 78.1 | One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s). |
| 0x1725 | 78.1 | A quorum of cluster nodes was not present to form a cluster. |
| 0x1726 | 78.1 | The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address. |
| 0x1727 | 78.1 | 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. |
| 0x1728 | 78.1 | Quorum resource cannot reside in the Available Storage group. |
| 0x1729 | 78.1 | The dependencies for this resource are nested too deeply. |
| 0x172a | 78.1 | The call into the resource DLL raised an unhandled exception. |
| 0x172b | 78.1 | The RHS process failed to initialize. |
| 0x172c | 78.1 | The Failover Clustering feature is not installed on this node. |
| 0x172d | 78.1 | The resources must be online on the same node for this operation |
| 0x172e | 78.1 | A new node can not be added since this cluster is already at its maximum number of nodes. |
| 0x172f | 78.1 | This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit. |
| 0x1730 | 78.1 | An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain. |
| 0x1731 | 78.1 | This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed. |
| 0x1732 | 78.1 | File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes. |
| 0x1733 | 78.1 | Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown. If it is the last node in the cluster, destroy cluster command should be used. |
| 0x1734 | 78.1 | Only one instance of this resource type is allowed in the cluster. |
| 0x1735 | 78.1 | Only one instance of this resource type is allowed per resource group. |
| 0x1736 | 78.1 | The resource failed to come online due to the failure of one or more provider resources. |
| 0x1737 | 78.1 | The resource has indicated that it cannot come online on any node. |
| 0x1738 | 78.1 | The current operation cannot be performed on this group at this time. |
| 0x1739 | 78.1 | The directory or file is not located on a cluster shared volume. |
| 0x173a | 78.1 | The Security Descriptor does not meet the requirements for a cluster. |
| 0x173b | 78.1 | There is one or more shared volumes resources configured in the cluster. Those resources must be moved to available storage in order for operation to succeed. |
| 0x173c | 78.1 | This group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation. |
| 0x173d | 78.1 | Back up is in progress. Please wait for backup completion before trying this operation again. |
| 0x173e | 78.1 | The path does not belong to a cluster shared volume. |
| 0x173f | 78.1 | The cluster shared volume is not locally mounted on this node. |
| 0x1740 | 78.1 | The cluster watchdog is terminating. |
| 0x1770 | 78.1 | The specified file could not be encrypted. |
| 0x1771 | 78.1 | The specified file could not be decrypted. |
| 0x1772 | 78.1 | The specified file is encrypted and the user does not have the ability to decrypt it. |
| 0x1773 | 78.1 | There is no valid encryption recovery policy configured for this system. |
| 0x1774 | 78.1 | The required encryption driver is not loaded for this system. |
| 0x1775 | 78.1 | The file was encrypted with a different encryption driver than is currently loaded. |
| 0x1776 | 78.1 | There are no EFS keys defined for the user. |
| 0x1777 | 78.1 | The specified file is not encrypted. |
| 0x1778 | 78.1 | The specified file is not in the defined EFS export format. |
| 0x1779 | 78.1 | The specified file is read only. |
| 0x177a | 78.1 | The directory has been disabled for encryption. |
| 0x177b | 78.1 | The server is not trusted for remote encryption operation. |
| 0x177c | 78.1 | Recovery policy configured for this system contains invalid recovery certificate. |
| 0x177d | 78.1 | The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file. |
| 0x177e | 78.1 | The disk partition does not support file encryption. |
| 0x177f | 78.1 | This machine is disabled for file encryption. |
| 0x1780 | 78.1 | A newer system is required to decrypt this encrypted file. |
| 0x1781 | 78.1 | The remote server sent an invalid response for a file being opened with Client Side Encryption. |
| 0x1782 | 78.1 | Client Side Encryption is not supported by the remote server even though it claims to support it. |
| 0x1783 | 78.1 | File is encrypted and should be opened in Client Side Encryption mode. |
| 0x1784 | 78.1 | A new encrypted file is being created and a $EFS needs to be provided. |
| 0x1785 | 78.1 | The SMB client requested a CSE FSCTL on a non-CSE file. |
| 0x1786 | 78.1 | The requested operation was blocked by policy. For more information, contact your system administrator. |
| 0x17e6 | 78.1 | The list of servers for this workgroup is not currently available |
| 0x1838 | 78.1 | The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts. |
| 0x19c8 | 78.1 | Log service encountered an invalid log sector. |
| 0x19c9 | 78.1 | Log service encountered a log sector with invalid block parity. |
| 0x19ca | 78.1 | Log service encountered a remapped log sector. |
| 0x19cb | 78.1 | Log service encountered a partial or incomplete log block. |
| 0x19cc | 78.1 | Log service encountered an attempt access data outside the active log range. |
| 0x19cd | 78.1 | Log service user marshalling buffers are exhausted. |
| 0x19ce | 78.1 | Log service encountered an attempt read from a marshalling area with an invalid read context. |
| 0x19cf | 78.1 | Log service encountered an invalid log restart area. |
| 0x19d0 | 78.1 | Log service encountered an invalid log block version. |
| 0x19d1 | 78.1 | Log service encountered an invalid log block. |
| 0x19d2 | 78.1 | Log service encountered an attempt to read the log with an invalid read mode. |
| 0x19d3 | 78.1 | Log service encountered a log stream with no restart area. |
| 0x19d4 | 78.1 | Log service encountered a corrupted metadata file. |
| 0x19d5 | 78.1 | Log service encountered a metadata file that could not be created by the log file system. |
| 0x19d6 | 78.1 | Log service encountered a metadata file with inconsistent data. |
| 0x19d7 | 78.1 | Log service encountered an attempt to erroneous allocate or dispose reservation space. |
| 0x19d8 | 78.1 | Log service cannot delete log file or file system container. |
| 0x19d9 | 78.1 | Log service has reached the maximum allowable containers allocated to a log file. |
| 0x19da | 78.1 | Log service has attempted to read or write backward past the start of the log. |
| 0x19db | 78.1 | Log policy could not be installed because a policy of the same type is already present. |
| 0x19dc | 78.1 | Log policy in question was not installed at the time of the request. |
| 0x19dd | 78.1 | The installed set of policies on the log is invalid. |
| 0x19de | 78.1 | A policy on the log in question prevented the operation from completing. |
| 0x19df | 78.1 | Log space cannot be reclaimed because the log is pinned by the archive tail. |
| 0x19e0 | 78.1 | Log record is not a record in the log file. |
| 0x19e1 | 78.1 | Number of reserved log records or the adjustment of the number of reserved log records is invalid. |
| 0x19e2 | 78.1 | Reserved log space or the adjustment of the log space is invalid. |
| 0x19e3 | 78.1 | An new or existing archive tail or base of the active log is invalid. |
| 0x19e4 | 78.1 | Log space is exhausted. |
| 0x19e5 | 78.1 | The log could not be set to the requested size. |
| 0x19e6 | 78.1 | Log is multiplexed, no direct writes to the physical log is allowed. |
| 0x19e7 | 78.1 | The operation failed because the log is a dedicated log. |
| 0x19e8 | 78.1 | The operation requires an archive context. |
| 0x19e9 | 78.1 | Log archival is in progress. |
| 0x19ea | 78.1 | The operation requires a non-ephemeral log, but the log is ephemeral. |
| 0x19eb | 78.1 | The log must have at least two containers before it can be read from or written to. |
| 0x19ec | 78.1 | A log client has already registered on the stream. |
| 0x19ed | 78.1 | A log client has not been registered on the stream. |
| 0x19ee | 78.1 | A request has already been made to handle the log full condition. |
| 0x19ef | 78.1 | Log service encountered an error when attempting to read from a log container. |
| 0x19f0 | 78.1 | Log service encountered an error when attempting to write to a log container. |
| 0x19f1 | 78.1 | Log service encountered an error when attempting open a log container. |
| 0x19f2 | 78.1 | Log service encountered an invalid container state when attempting a requested action. |
| 0x19f3 | 78.1 | Log service is not in the correct state to perform a requested action. |
| 0x19f4 | 78.1 | Log space cannot be reclaimed because the log is pinned. |
| 0x19f5 | 78.1 | Log metadata flush failed. |
| 0x19f6 | 78.1 | Security on the log and its containers is inconsistent. |
| 0x19f7 | 78.1 | Records were appended to the log or reservation changes were made, but the log could not be flushed. |
| 0x19f8 | 78.1 | The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
| 0x1a2c | 78.1 | The transaction handle associated with this operation is not valid. |
| 0x1a2d | 78.1 | The requested operation was made in the context of a transaction that is no longer active. |
| 0x1a2e | 78.1 | The requested operation is not valid on the Transaction object in its current state. |
| 0x1a2f | 78.1 | 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. |
| 0x1a30 | 78.1 | It is too late to perform the requested operation, since the Transaction has already been aborted. |
| 0x1a31 | 78.1 | It is too late to perform the requested operation, since the Transaction has already been committed. |
| 0x1a32 | 78.1 | The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. |
| 0x1a33 | 78.1 | The specified ResourceManager made no changes or updates to the resource under this transaction. |
| 0x1a34 | 78.1 | The resource manager has attempted to prepare a transaction that it has not successfully joined. |
| 0x1a35 | 78.1 | 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. |
| 0x1a36 | 78.1 | The RM tried to register a protocol that already exists. |
| 0x1a37 | 78.1 | The attempt to propagate the Transaction failed. |
| 0x1a38 | 78.1 | The requested propagation protocol was not registered as a CRM. |
| 0x1a39 | 78.1 | The buffer passed in to PushTransaction or PullTransaction is not in a valid format. |
| 0x1a3a | 78.1 | The current transaction context associated with the thread is not a valid handle to a transaction object. |
| 0x1a3b | 78.1 | The specified Transaction object could not be opened, because it was not found. |
| 0x1a3c | 78.1 | The specified ResourceManager object could not be opened, because it was not found. |
| 0x1a3d | 78.1 | The specified Enlistment object could not be opened, because it was not found. |
| 0x1a3e | 78.1 | The specified TransactionManager object could not be opened, because it was not found. |
| 0x1a3f | 78.1 | 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. |
| 0x1a40 | 78.1 | The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover. |
| 0x1a41 | 78.1 | 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. |
| 0x1a42 | 78.1 | Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
| 0x1a43 | 78.1 | 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. |
| 0x1a44 | 78.1 | 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. |
| 0x1a45 | 78.1 | Implicit transaction are not supported. |
| 0x1a46 | 78.1 | The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
| 0x1a47 | 78.1 | The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. |
| 0x1a48 | 78.1 | This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. |
| 0x1a49 | 78.1 | 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. |
| 0x1a4a | 78.1 | The transaction does not have a superior enlistment. |
| 0x1a4b | 78.1 | 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. |
| 0x1a90 | 78.1 | The function attempted to use a name that is reserved for use by another transaction. |
| 0x1a91 | 78.1 | Transaction support within the specified resource manager is not started or was shut down due to an error. |
| 0x1a92 | 78.1 | The metadata of the RM has been corrupted. The RM will not function. |
| 0x1a93 | 78.1 | The specified directory does not contain a resource manager. |
| 0x1a95 | 78.1 | The remote server or share does not support transacted file operations. |
| 0x1a96 | 78.1 | The requested log size is invalid. |
| 0x1a97 | 78.1 | The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback. |
| 0x1a98 | 78.1 | The specified file miniversion was not found for this transacted file open. |
| 0x1a99 | 78.1 | The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. |
| 0x1a9a | 78.1 | A miniversion may only be opened in the context of the transaction that created it. |
| 0x1a9b | 78.1 | It is not possible to open a miniversion with modify access. |
| 0x1a9c | 78.1 | It is not possible to create any more miniversions for this stream. |
| 0x1a9e | 78.1 | The remote server sent mismatching version number or Fid for a file opened with transactions. |
| 0x1a9f | 78.1 | 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. |
| 0x1aa0 | 78.1 | There is no transaction metadata on the file. |
| 0x1aa1 | 78.1 | The log data is corrupt. |
| 0x1aa2 | 78.1 | The file can't be recovered because there is a handle still open on it. |
| 0x1aa3 | 78.1 | The transaction outcome is unavailable because the resource manager responsible for it has disconnected. |
| 0x1aa4 | 78.1 | The request was rejected because the enlistment in question is not a superior enlistment. |
| 0x1aa5 | 78.1 | The transactional resource manager is already consistent. Recovery is not needed. |
| 0x1aa6 | 78.1 | The transactional resource manager has already been started. |
| 0x1aa7 | 78.1 | The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. |
| 0x1aa8 | 78.1 | The operation cannot be performed because another transaction is depending on the fact that this property will not change. |
| 0x1aa9 | 78.1 | The operation would involve a single file with two transactional resource managers and is therefore not allowed. |
| 0x1aaa | 78.1 | The $Txf directory must be empty for this operation to succeed. |
| 0x1aab | 78.1 | The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
| 0x1aac | 78.1 | The operation could not be completed because the transaction manager does not have a log. |
| 0x1aad | 78.1 | A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
| 0x1aae | 78.1 | The transactional metadata attribute on the file or directory is corrupt and unreadable. |
| 0x1aaf | 78.1 | The encryption operation could not be completed because a transaction is active. |
| 0x1ab0 | 78.1 | This object is not allowed to be opened in a transaction. |
| 0x1ab1 | 78.1 | An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
| 0x1ab2 | 78.1 | Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
| 0x1ab3 | 78.1 | Transaction metadata is already present on this file and cannot be superseded. |
| 0x1ab4 | 78.1 | A transaction scope could not be entered because the scope handler has not been initialized. |
| 0x1ab5 | 78.1 | Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. |
| 0x1ab6 | 78.1 | This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. |
| 0x1ab7 | 78.1 | The request to thaw frozen transactions was ignored because transactions had not previously been frozen. |
| 0x1ab8 | 78.1 | Transactions cannot be frozen because a freeze is already in progress. |
| 0x1ab9 | 78.1 | The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. |
| 0x1aba | 78.1 | The savepoint operation failed because files are open on the transaction. This is not permitted. |
| 0x1abb | 78.1 | Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred. |
| 0x1abc | 78.1 | The sparse operation could not be completed because a transaction is active on the file. |
| 0x1abd | 78.1 | 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. |
| 0x1abe | 78.1 | I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. |
| 0x1abf | 78.1 | The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. |
| 0x1ac0 | 78.1 | The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. |
| 0x1ac1 | 78.1 | The operation could not be completed due to bad clusters on disk. |
| 0x1ac2 | 78.1 | The compression operation could not be completed because a transaction is active on the file. |
| 0x1ac3 | 78.1 | The operation could not be completed because the volume is dirty. Please run chkdsk and try again. |
| 0x1ac4 | 78.1 | The link tracking operation could not be completed because a transaction is active. |
| 0x1ac5 | 78.1 | This operation cannot be performed in a transaction. |
| 0x1ac6 | 78.1 | 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. |
| 0x1ac7 | 78.1 | The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
| 0x1b59 | 78.1 | The specified session name is invalid. |
| 0x1b5a | 78.1 | The specified protocol driver is invalid. |
| 0x1b5b | 78.1 | The specified protocol driver was not found in the system path. |
| 0x1b5c | 78.1 | The specified terminal connection driver was not found in the system path. |
| 0x1b5d | 78.1 | A registry key for event logging could not be created for this session. |
| 0x1b5e | 78.1 | A service with the same name already exists on the system. |
| 0x1b5f | 78.1 | A close operation is pending on the session. |
| 0x1b60 | 78.1 | There are no free output buffers available. |
| 0x1b61 | 78.1 | The MODEM.INF file was not found. |
| 0x1b62 | 78.1 | The modem name was not found in MODEM.INF. |
| 0x1b63 | 78.1 | The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem. |
| 0x1b64 | 78.1 | The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on. |
| 0x1b65 | 78.1 | Carrier detect has failed or carrier has been dropped due to disconnect. |
| 0x1b66 | 78.1 | Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional. |
| 0x1b67 | 78.1 | Busy signal detected at remote site on callback. |
| 0x1b68 | 78.1 | Voice detected at remote site on callback. |
| 0x1b69 | 78.1 | Transport driver error |
| 0x1b6e | 78.1 | The specified session cannot be found. |
| 0x1b6f | 78.1 | The specified session name is already in use. |
| 0x1b70 | 78.1 | 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. |
| 0x1b71 | 78.1 | An attempt has been made to connect to a session whose video mode is not supported by the current client. |
| 0x1b7b | 78.1 | The application attempted to enable DOS graphics mode. DOS graphics mode is not supported. |
| 0x1b7d | 78.1 | Your interactive logon privilege has been disabled. Please contact your administrator. |
| 0x1b7e | 78.1 | 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. |
| 0x1b80 | 78.1 | The client failed to respond to the server connect message. |
| 0x1b81 | 78.1 | Disconnecting the console session is not supported. |
| 0x1b82 | 78.1 | Reconnecting a disconnected session to the console is not supported. |
| 0x1b84 | 78.1 | The request to control another session remotely was denied. |
| 0x1b85 | 78.1 | The requested session access is denied. |
| 0x1b89 | 78.1 | The specified terminal connection driver is invalid. |
| 0x1b8a | 78.1 | The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on. |
| 0x1b8b | 78.1 | The requested session is not configured to allow remote control. |
| 0x1b8c | 78.1 | 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. |
| 0x1b8d | 78.1 | 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. |
| 0x1b8e | 78.1 | 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. |
| 0x1b8f | 78.1 | The client you are using is not licensed to use this system. Your logon request is denied. |
| 0x1b90 | 78.1 | The system license has expired. Your logon request is denied. |
| 0x1b91 | 78.1 | Remote control could not be terminated because the specified session is not currently being remotely controlled. |
| 0x1b92 | 78.1 | 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. |
| 0x1b93 | 78.1 | Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared. |
| 0x1b94 | 78.1 | Remote logins are currently disabled. |
| 0x1b95 | 78.1 | You do not have the proper encryption level to access this Session. |
| 0x1b96 | 78.1 | The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer. |
| 0x1b97 | 78.1 | 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. |
| 0x1b98 | 78.1 | Unable to log you on because of an account restriction. |
| 0x1b99 | 78.1 | The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
| 0x1b9a | 78.1 | The Client Drive Mapping Service Has Connected on Terminal Connection. |
| 0x1b9b | 78.1 | The Client Drive Mapping Service Has Disconnected on Terminal Connection. |
| 0x1b9c | 78.1 | The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. |
| 0x1b9d | 78.1 | The target session is incompatible with the current session. |
| 0x1b9e | 78.1 | 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. |
| 0x1f41 | 78.1 | The file replication service API was called incorrectly. |
| 0x1f42 | 78.1 | The file replication service cannot be started. |
| 0x1f43 | 78.1 | The file replication service cannot be stopped. |
| 0x1f44 | 78.1 | The file replication service API terminated the request. The event log may have more information. |
| 0x1f45 | 78.1 | The file replication service terminated the request. The event log may have more information. |
| 0x1f46 | 78.1 | The file replication service cannot be contacted. The event log may have more information. |
| 0x1f47 | 78.1 | The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information. |
| 0x1f48 | 78.1 | The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information. |
| 0x1f49 | 78.1 | The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information. |
| 0x1f4a | 78.1 | The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information. |
| 0x1f4b | 78.1 | The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information. |
| 0x1f4c | 78.1 | The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information. |
| 0x1f4d | 78.1 | The file replication service cannot populate the system volume because of an internal error. The event log may have more information. |
| 0x1f4e | 78.1 | The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information. |
| 0x1f4f | 78.1 | The file replication service cannot process the request. The system volume is busy with a previous request. |
| 0x1f50 | 78.1 | The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information. |
| 0x1f51 | 78.1 | The file replication service detected an invalid parameter. |
| 0x2008 | 78.1 | An error occurred while installing the directory service. For more information, see the event log. |
| 0x2009 | 78.1 | The directory service evaluated group memberships locally. |
| 0x200a | 78.1 | The specified directory service attribute or value does not exist. |
| 0x200b | 78.1 | The attribute syntax specified to the directory service is invalid. |
| 0x200c | 78.1 | The attribute type specified to the directory service is not defined. |
| 0x200d | 78.1 | The specified directory service attribute or value already exists. |
| 0x200e | 78.1 | The directory service is busy. |
| 0x200f | 78.1 | The directory service is unavailable. |
| 0x2010 | 78.1 | The directory service was unable to allocate a relative identifier. |
| 0x2011 | 78.1 | The directory service has exhausted the pool of relative identifiers. |
| 0x2012 | 78.1 | The requested operation could not be performed because the directory service is not the master for that type of operation. |
| 0x2013 | 78.1 | The directory service was unable to initialize the subsystem that allocates relative identifiers. |
| 0x2014 | 78.1 | The requested operation did not satisfy one or more constraints associated with the class of the object. |
| 0x2015 | 78.1 | The directory service can perform the requested operation only on a leaf object. |
| 0x2016 | 78.1 | The directory service cannot perform the requested operation on the RDN attribute of an object. |
| 0x2017 | 78.1 | The directory service detected an attempt to modify the object class of an object. |
| 0x2018 | 78.1 | The requested cross-domain move operation could not be performed. |
| 0x2019 | 78.1 | Unable to contact the global catalog server. |
| 0x201a | 78.1 | The policy object is shared and can only be modified at the root. |
| 0x201b | 78.1 | The policy object does not exist. |
| 0x201c | 78.1 | The requested policy information is only in the directory service. |
| 0x201d | 78.1 | A domain controller promotion is currently active. |
| 0x201e | 78.1 | A domain controller promotion is not currently active |
| 0x2020 | 78.1 | An operations error occurred. |
| 0x2021 | 78.1 | A protocol error occurred. |
| 0x2022 | 78.1 | The time limit for this request was exceeded. |
| 0x2023 | 78.1 | The size limit for this request was exceeded. |
| 0x2024 | 78.1 | The administrative limit for this request was exceeded. |
| 0x2025 | 78.1 | The compare response was false. |
| 0x2026 | 78.1 | The compare response was true. |
| 0x2027 | 78.1 | The requested authentication method is not supported by the server. |
| 0x2028 | 78.1 | A more secure authentication method is required for this server. |
| 0x2029 | 78.1 | Inappropriate authentication. |
| 0x202a | 78.1 | The authentication mechanism is unknown. |
| 0x202b | 78.1 | A referral was returned from the server. |
| 0x202c | 78.1 | The server does not support the requested critical extension. |
| 0x202d | 78.1 | This request requires a secure connection. |
| 0x202e | 78.1 | Inappropriate matching. |
| 0x202f | 78.1 | A constraint violation occurred. |
| 0x2030 | 78.1 | There is no such object on the server. |
| 0x2031 | 78.1 | There is an alias problem. |
| 0x2032 | 78.1 | An invalid dn syntax has been specified. |
| 0x2033 | 78.1 | The object is a leaf object. |
| 0x2034 | 78.1 | There is an alias dereferencing problem. |
| 0x2035 | 78.1 | The server is unwilling to process the request. |
| 0x2036 | 78.1 | A loop has been detected. |
| 0x2037 | 78.1 | There is a naming violation. |
| 0x2038 | 78.1 | The result set is too large. |
| 0x2039 | 78.1 | The operation affects multiple DSAs |
| 0x203a | 78.1 | The server is not operational. |
| 0x203b | 78.1 | A local error has occurred. |
| 0x203c | 78.1 | An encoding error has occurred. |
| 0x203d | 78.1 | A decoding error has occurred. |
| 0x203e | 78.1 | The search filter cannot be recognized. |
| 0x203f | 78.1 | One or more parameters are illegal. |
| 0x2040 | 78.1 | The specified method is not supported. |
| 0x2041 | 78.1 | No results were returned. |
| 0x2042 | 78.1 | The specified control is not supported by the server. |
| 0x2043 | 78.1 | A referral loop was detected by the client. |
| 0x2044 | 78.1 | The preset referral limit was exceeded. |
| 0x2045 | 78.1 | The search requires a SORT control. |
| 0x2046 | 78.1 | The search results exceed the offset range specified. |
| 0x206d | 78.1 | The root object must be the head of a naming context. The root object cannot have an instantiated parent. |
| 0x206e | 78.1 | The add replica operation cannot be performed. The naming context must be writeable in order to create the replica. |
| 0x206f | 78.1 | A reference to an attribute that is not defined in the schema occurred. |
| 0x2070 | 78.1 | The maximum size of an object has been exceeded. |
| 0x2071 | 78.1 | An attempt was made to add an object to the directory with a name that is already in use. |
| 0x2072 | 78.1 | An attempt was made to add an object of a class that does not have an RDN defined in the schema. |
| 0x2073 | 78.1 | An attempt was made to add an object using an RDN that is not the RDN defined in the schema. |
| 0x2074 | 78.1 | None of the requested attributes were found on the objects. |
| 0x2075 | 78.1 | The user buffer is too small. |
| 0x2076 | 78.1 | The attribute specified in the operation is not present on the object. |
| 0x2077 | 78.1 | Illegal modify operation. Some aspect of the modification is not permitted. |
| 0x2078 | 78.1 | The specified object is too large. |
| 0x2079 | 78.1 | The specified instance type is not valid. |
| 0x207a | 78.1 | The operation must be performed at a master DSA. |
| 0x207b | 78.1 | The object class attribute must be specified. |
| 0x207c | 78.1 | A required attribute is missing. |
| 0x207d | 78.1 | An attempt was made to modify an object to include an attribute that is not legal for its class. |
| 0x207e | 78.1 | The specified attribute is already present on the object. |
| 0x2080 | 78.1 | The specified attribute is not present, or has no values. |
| 0x2081 | 78.1 | Multiple values were specified for an attribute that can have only one value. |
| 0x2082 | 78.1 | A value for the attribute was not in the acceptable range of values. |
| 0x2083 | 78.1 | The specified value already exists. |
| 0x2084 | 78.1 | The attribute cannot be removed because it is not present on the object. |
| 0x2085 | 78.1 | The attribute value cannot be removed because it is not present on the object. |
| 0x2086 | 78.1 | The specified root object cannot be a subref. |
| 0x2087 | 78.1 | Chaining is not permitted. |
| 0x2088 | 78.1 | Chained evaluation is not permitted. |
| 0x2089 | 78.1 | The operation could not be performed because the object's parent is either uninstantiated or deleted. |
| 0x208a | 78.1 | Having a parent that is an alias is not permitted. Aliases are leaf objects. |
| 0x208b | 78.1 | The object and parent must be of the same type, either both masters or both replicas. |
| 0x208c | 78.1 | The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object. |
| 0x208d | 78.1 | Directory object not found. |
| 0x208e | 78.1 | The aliased object is missing. |
| 0x208f | 78.1 | The object name has bad syntax. |
| 0x2090 | 78.1 | It is not permitted for an alias to refer to another alias. |
| 0x2091 | 78.1 | The alias cannot be dereferenced. |
| 0x2092 | 78.1 | The operation is out of scope. |
| 0x2093 | 78.1 | The operation cannot continue because the object is in the process of being removed. |
| 0x2094 | 78.1 | The DSA object cannot be deleted. |
| 0x2095 | 78.1 | A directory service error has occurred. |
| 0x2096 | 78.1 | The operation can only be performed on an internal master DSA object. |
| 0x2097 | 78.1 | The object must be of class DSA. |
| 0x2098 | 78.1 | Insufficient access rights to perform the operation. |
| 0x2099 | 78.1 | The object cannot be added because the parent is not on the list of possible superiors. |
| 0x209a | 78.1 | Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM). |
| 0x209b | 78.1 | The name has too many parts. |
| 0x209c | 78.1 | The name is too long. |
| 0x209d | 78.1 | The name value is too long. |
| 0x209e | 78.1 | The directory service encountered an error parsing a name. |
| 0x209f | 78.1 | The directory service cannot get the attribute type for a name. |
| 0x20a0 | 78.1 | The name does not identify an object; the name identifies a phantom. |
| 0x20a1 | 78.1 | The security descriptor is too short. |
| 0x20a2 | 78.1 | The security descriptor is invalid. |
| 0x20a3 | 78.1 | Failed to create name for deleted object. |
| 0x20a4 | 78.1 | The parent of a new subref must exist. |
| 0x20a5 | 78.1 | The object must be a naming context. |
| 0x20a6 | 78.1 | It is not permitted to add an attribute which is owned by the system. |
| 0x20a7 | 78.1 | The class of the object must be structural; you cannot instantiate an abstract class. |
| 0x20a8 | 78.1 | The schema object could not be found. |
| 0x20a9 | 78.1 | A local object with this GUID (dead or alive) already exists. |
| 0x20aa | 78.1 | The operation cannot be performed on a back link. |
| 0x20ab | 78.1 | The cross reference for the specified naming context could not be found. |
| 0x20ac | 78.1 | The operation could not be performed because the directory service is shutting down. |
| 0x20ad | 78.1 | The directory service request is invalid. |
| 0x20ae | 78.1 | The role owner attribute could not be read. |
| 0x20af | 78.1 | The requested FSMO operation failed. The current FSMO holder could not be contacted. |
| 0x20b0 | 78.1 | Modification of a DN across a naming context is not permitted. |
| 0x20b1 | 78.1 | The attribute cannot be modified because it is owned by the system. |
| 0x20b2 | 78.1 | Only the replicator can perform this function. |
| 0x20b3 | 78.1 | The specified class is not defined. |
| 0x20b4 | 78.1 | The specified class is not a subclass. |
| 0x20b5 | 78.1 | The name reference is invalid. |
| 0x20b6 | 78.1 | A cross reference already exists. |
| 0x20b7 | 78.1 | It is not permitted to delete a master cross reference. |
| 0x20b8 | 78.1 | Subtree notifications are only supported on NC heads. |
| 0x20b9 | 78.1 | Notification filter is too complex. |
| 0x20ba | 78.1 | Schema update failed: duplicate RDN. |
| 0x20bb | 78.1 | Schema update failed: duplicate OID. |
| 0x20bc | 78.1 | Schema update failed: duplicate MAPI identifier. |
| 0x20bd | 78.1 | Schema update failed: duplicate schema-id GUID. |
| 0x20be | 78.1 | Schema update failed: duplicate LDAP display name. |
| 0x20bf | 78.1 | Schema update failed: range-lower less than range upper. |
| 0x20c0 | 78.1 | Schema update failed: syntax mismatch. |
| 0x20c1 | 78.1 | Schema deletion failed: attribute is used in must-contain. |
| 0x20c2 | 78.1 | Schema deletion failed: attribute is used in may-contain. |
| 0x20c3 | 78.1 | Schema update failed: attribute in may-contain does not exist. |
| 0x20c4 | 78.1 | Schema update failed: attribute in must-contain does not exist. |
| 0x20c5 | 78.1 | Schema update failed: class in aux-class list does not exist or is not an auxiliary class. |
| 0x20c6 | 78.1 | Schema update failed: class in poss-superiors does not exist. |
| 0x20c7 | 78.1 | Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules. |
| 0x20c8 | 78.1 | Schema update failed: Rdn-Att-Id has wrong syntax. |
| 0x20c9 | 78.1 | Schema deletion failed: class is used as auxiliary class. |
| 0x20ca | 78.1 | Schema deletion failed: class is used as sub class. |
| 0x20cb | 78.1 | Schema deletion failed: class is used as poss superior. |
| 0x20cc | 78.1 | Schema update failed in recalculating validation cache. |
| 0x20cd | 78.1 | The tree deletion is not finished. The request must be made again to continue deleting the tree. |
| 0x20ce | 78.1 | The requested delete operation could not be performed. |
| 0x20cf | 78.1 | Cannot read the governs class identifier for the schema record. |
| 0x20d0 | 78.1 | The attribute schema has bad syntax. |
| 0x20d1 | 78.1 | The attribute could not be cached. |
| 0x20d2 | 78.1 | The class could not be cached. |
| 0x20d3 | 78.1 | The attribute could not be removed from the cache. |
| 0x20d4 | 78.1 | The class could not be removed from the cache. |
| 0x20d5 | 78.1 | The distinguished name attribute could not be read. |
| 0x20d6 | 78.1 | No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest. |
| 0x20d7 | 78.1 | The instance type attribute could not be retrieved. |
| 0x20d8 | 78.1 | An internal error has occurred. |
| 0x20d9 | 78.1 | A database error has occurred. |
| 0x20da | 78.1 | The attribute GOVERNSID is missing. |
| 0x20db | 78.1 | An expected attribute is missing. |
| 0x20dc | 78.1 | The specified naming context is missing a cross reference. |
| 0x20dd | 78.1 | A security checking error has occurred. |
| 0x20de | 78.1 | The schema is not loaded. |
| 0x20df | 78.1 | Schema allocation failed. Please check if the machine is running low on memory. |
| 0x20e0 | 78.1 | Failed to obtain the required syntax for the attribute schema. |
| 0x20e1 | 78.1 | 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. |
| 0x20e2 | 78.1 | The replication operation failed because of a schema mismatch between the servers involved. |
| 0x20e3 | 78.1 | The DSA object could not be found. |
| 0x20e4 | 78.1 | The naming context could not be found. |
| 0x20e5 | 78.1 | The naming context could not be found in the cache. |
| 0x20e6 | 78.1 | The child object could not be retrieved. |
| 0x20e7 | 78.1 | The modification was not permitted for security reasons. |
| 0x20e8 | 78.1 | The operation cannot replace the hidden record. |
| 0x20e9 | 78.1 | The hierarchy file is invalid. |
| 0x20ea | 78.1 | The attempt to build the hierarchy table failed. |
| 0x20eb | 78.1 | The directory configuration parameter is missing from the registry. |
| 0x20ec | 78.1 | The attempt to count the address book indices failed. |
| 0x20ed | 78.1 | The allocation of the hierarchy table failed. |
| 0x20ee | 78.1 | The directory service encountered an internal failure. |
| 0x20ef | 78.1 | The directory service encountered an unknown failure. |
| 0x20f0 | 78.1 | A root object requires a class of 'top'. |
| 0x20f1 | 78.1 | This directory server is shutting down, and cannot take ownership of new floating single-master operation roles. |
| 0x20f2 | 78.1 | The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles. |
| 0x20f3 | 78.1 | The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers. |
| 0x20f4 | 78.1 | The replication operation failed. |
| 0x20f5 | 78.1 | An invalid parameter was specified for this replication operation. |
| 0x20f6 | 78.1 | The directory service is too busy to complete the replication operation at this time. |
| 0x20f7 | 78.1 | The distinguished name specified for this replication operation is invalid. |
| 0x20f8 | 78.1 | The naming context specified for this replication operation is invalid. |
| 0x20f9 | 78.1 | The distinguished name specified for this replication operation already exists. |
| 0x20fa | 78.1 | The replication system encountered an internal error. |
| 0x20fb | 78.1 | The replication operation encountered a database inconsistency. |
| 0x20fc | 78.1 | The server specified for this replication operation could not be contacted. |
| 0x20fd | 78.1 | The replication operation encountered an object with an invalid instance type. |
| 0x20fe | 78.1 | The replication operation failed to allocate memory. |
| 0x20ff | 78.1 | The replication operation encountered an error with the mail system. |
| 0x2100 | 78.1 | The replication reference information for the target server already exists. |
| 0x2101 | 78.1 | The replication reference information for the target server does not exist. |
| 0x2102 | 78.1 | The naming context cannot be removed because it is replicated to another server. |
| 0x2103 | 78.1 | The replication operation encountered a database error. |
| 0x2104 | 78.1 | The naming context is in the process of being removed or is not replicated from the specified server. |
| 0x2105 | 78.1 | Replication access was denied. |
| 0x2106 | 78.1 | The requested operation is not supported by this version of the directory service. |
| 0x2107 | 78.1 | The replication remote procedure call was cancelled. |
| 0x2108 | 78.1 | The source server is currently rejecting replication requests. |
| 0x2109 | 78.1 | The destination server is currently rejecting replication requests. |
| 0x210a | 78.1 | The replication operation failed due to a collision of object names. |
| 0x210b | 78.1 | The replication source has been reinstalled. |
| 0x210c | 78.1 | The replication operation failed because a required parent object is missing. |
| 0x210d | 78.1 | The replication operation was preempted. |
| 0x210e | 78.1 | The replication synchronization attempt was abandoned because of a lack of updates. |
| 0x210f | 78.1 | The replication operation was terminated because the system is shutting down. |
| 0x2110 | 78.1 | 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. |
| 0x2111 | 78.1 | The replication synchronization attempt failed because a master replica attempted to sync from a partial replica. |
| 0x2112 | 78.1 | The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation. |
| 0x2113 | 78.1 | The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer. |
| 0x2114 | 78.1 | Schema update failed: An attribute with the same link identifier already exists. |
| 0x2115 | 78.1 | Name translation: Generic processing error. |
| 0x2116 | 78.1 | Name translation: Could not find the name or insufficient right to see name. |
| 0x2117 | 78.1 | Name translation: Input name mapped to more than one output name. |
| 0x2118 | 78.1 | Name translation: Input name found, but not the associated output format. |
| 0x2119 | 78.1 | Name translation: Unable to resolve completely, only the domain was found. |
| 0x211a | 78.1 | Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire. |
| 0x211b | 78.1 | Modification of a constructed attribute is not allowed. |
| 0x211c | 78.1 | The OM-Object-Class specified is incorrect for an attribute with the specified syntax. |
| 0x211d | 78.1 | The replication request has been posted; waiting for reply. |
| 0x211e | 78.1 | The requested operation requires a directory service, and none was available. |
| 0x211f | 78.1 | The LDAP display name of the class or attribute contains non-ASCII characters. |
| 0x2120 | 78.1 | The requested search operation is only supported for base searches. |
| 0x2121 | 78.1 | The search failed to retrieve attributes from the database. |
| 0x2122 | 78.1 | The schema update operation tried to add a backward link attribute that has no corresponding forward link. |
| 0x2123 | 78.1 | 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. |
| 0x2124 | 78.1 | 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. |
| 0x2125 | 78.1 | Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation. |
| 0x2126 | 78.1 | 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. |
| 0x2127 | 78.1 | Destination of a cross-domain move is not authoritative for the destination naming context. |
| 0x2128 | 78.1 | 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. |
| 0x2129 | 78.1 | 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. |
| 0x212a | 78.1 | Another operation which requires exclusive access to the PDC FSMO is already in progress. |
| 0x212b | 78.1 | 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. |
| 0x212c | 78.1 | 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. |
| 0x212d | 78.1 | 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. |
| 0x212e | 78.1 | A naming context head must be the immediate child of another naming context head, not of an interior node. |
| 0x212f | 78.1 | 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) |
| 0x2130 | 78.1 | Destination domain must be in native mode. |
| 0x2131 | 78.1 | The operation cannot be performed because the server does not have an infrastructure container in the domain of interest. |
| 0x2132 | 78.1 | Cross-domain move of non-empty account groups is not allowed. |
| 0x2133 | 78.1 | Cross-domain move of non-empty resource groups is not allowed. |
| 0x2134 | 78.1 | The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings. |
| 0x2135 | 78.1 | Tree deletions starting at an object which has an NC head as a descendant are not allowed. |
| 0x2136 | 78.1 | The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use. |
| 0x2137 | 78.1 | The directory service failed to identify the list of objects to delete while attempting a tree deletion. |
| 0x2138 | 78.1 | Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0x2139 | 78.1 | Only an administrator can modify the membership list of an administrative group. |
| 0x213a | 78.1 | Cannot change the primary group ID of a domain controller account. |
| 0x213b | 78.1 | An attempt is made to modify the base schema. |
| 0x213c | 78.1 | 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. |
| 0x213d | 78.1 | Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner. |
| 0x213e | 78.1 | 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. |
| 0x213f | 78.1 | 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. |
| 0x2140 | 78.1 | The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory. |
| 0x2141 | 78.1 | The specified group type is invalid. |
| 0x2142 | 78.1 | You cannot nest global groups in a mixed domain if the group is security-enabled. |
| 0x2143 | 78.1 | You cannot nest local groups in a mixed domain if the group is security-enabled. |
| 0x2144 | 78.1 | A global group cannot have a local group as a member. |
| 0x2145 | 78.1 | A global group cannot have a universal group as a member. |
| 0x2146 | 78.1 | A universal group cannot have a local group as a member. |
| 0x2147 | 78.1 | A global group cannot have a cross-domain member. |
| 0x2148 | 78.1 | A local group cannot have another cross domain local group as a member. |
| 0x2149 | 78.1 | A group with primary members cannot change to a security-disabled group. |
| 0x214a | 78.1 | The schema cache load failed to convert the string default SD on a class-schema object. |
| 0x214b | 78.1 | 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) |
| 0x214c | 78.1 | The DSA operation is unable to proceed because of a DNS lookup failure. |
| 0x214d | 78.1 | While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync. |
| 0x214e | 78.1 | The Security Descriptor attribute could not be read. |
| 0x214f | 78.1 | The object requested was not found, but an object with that key was found. |
| 0x2150 | 78.1 | 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 |
| 0x2151 | 78.1 | Security Account Manager needs to get the boot password. |
| 0x2152 | 78.1 | Security Account Manager needs to get the boot key from floppy disk. |
| 0x2153 | 78.1 | Directory Service cannot start. |
| 0x2154 | 78.1 | Directory Services could not start. |
| 0x2155 | 78.1 | The connection between client and server requires packet privacy or better. |
| 0x2156 | 78.1 | The source domain may not be in the same forest as destination. |
| 0x2157 | 78.1 | The destination domain must be in the forest. |
| 0x2158 | 78.1 | The operation requires that destination domain auditing be enabled. |
| 0x2159 | 78.1 | The operation couldn't locate a DC for the source domain. |
| 0x215a | 78.1 | The source object must be a group or user. |
| 0x215b | 78.1 | The source object's SID already exists in destination forest. |
| 0x215c | 78.1 | The source and destination object must be of the same type. |
| 0x215d | 78.1 | Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information. |
| 0x215e | 78.1 | Schema information could not be included in the replication request. |
| 0x215f | 78.1 | The replication operation could not be completed due to a schema incompatibility. |
| 0x2160 | 78.1 | The replication operation could not be completed due to a previous schema incompatibility. |
| 0x2161 | 78.1 | 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. |
| 0x2162 | 78.1 | The requested domain could not be deleted because there exist domain controllers that still host this domain. |
| 0x2163 | 78.1 | The requested operation can be performed only on a global catalog server. |
| 0x2164 | 78.1 | A local group can only be a member of other local groups in the same domain. |
| 0x2165 | 78.1 | Foreign security principals cannot be members of universal groups. |
| 0x2166 | 78.1 | The attribute is not allowed to be replicated to the GC because of security reasons. |
| 0x2167 | 78.1 | The checkpoint with the PDC could not be taken because there too many modifications being processed currently. |
| 0x2168 | 78.1 | The operation requires that source domain auditing be enabled. |
| 0x2169 | 78.1 | Security principal objects can only be created inside domain naming contexts. |
| 0x216a | 78.1 | A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format. |
| 0x216b | 78.1 | A Filter was passed that uses constructed attributes. |
| 0x216c | 78.1 | The unicodePwd attribute value must be enclosed in double quotes. |
| 0x216d | 78.1 | 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. |
| 0x216e | 78.1 | For security reasons, the operation must be run on the destination DC. |
| 0x216f | 78.1 | For security reasons, the source DC must be NT4SP4 or greater. |
| 0x2170 | 78.1 | Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed. |
| 0x2171 | 78.1 | Directory Services could not start because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0x2172 | 78.1 | Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0x2173 | 78.1 | 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. |
| 0x2174 | 78.1 | 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. |
| 0x2175 | 78.1 | 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. |
| 0x2176 | 78.1 | 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. |
| 0x2177 | 78.1 | The version of the operating system installed on this server is incompatible with the functional level of the domain or forest. |
| 0x2178 | 78.1 | 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. |
| 0x2179 | 78.1 | 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. |
| 0x217a | 78.1 | The sort order requested is not supported. |
| 0x217b | 78.1 | The requested name already exists as a unique identifier. |
| 0x217c | 78.1 | The machine account was created pre-NT4. The account needs to be recreated. |
| 0x217d | 78.1 | The database is out of version store. |
| 0x217e | 78.1 | Unable to continue operation because multiple conflicting controls were used. |
| 0x217f | 78.1 | Unable to find a valid security descriptor reference domain for this partition. |
| 0x2180 | 78.1 | Schema update failed: The link identifier is reserved. |
| 0x2181 | 78.1 | Schema update failed: There are no link identifiers available. |
| 0x2182 | 78.1 | An account group cannot have a universal group as a member. |
| 0x2183 | 78.1 | Rename or move operations on naming context heads or read-only objects are not allowed. |
| 0x2184 | 78.1 | Move operations on objects in the schema naming context are not allowed. |
| 0x2185 | 78.1 | A system flag has been set on the object and does not allow the object to be moved or renamed. |
| 0x2186 | 78.1 | This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers. |
| 0x2187 | 78.1 | Unable to resolve completely, a referral to another forest is generated. |
| 0x2188 | 78.1 | The requested action is not supported on standard server. |
| 0x2189 | 78.1 | 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. |
| 0x218a | 78.1 | 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. |
| 0x218b | 78.1 | The thread limit for this request was exceeded. |
| 0x218c | 78.1 | The Global catalog server is not in the closest site. |
| 0x218d | 78.1 | 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. |
| 0x218e | 78.1 | The Directory Service failed to enter single user mode. |
| 0x218f | 78.1 | The Directory Service cannot parse the script because of a syntax error. |
| 0x2190 | 78.1 | The Directory Service cannot process the script because of an error. |
| 0x2191 | 78.1 | 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). |
| 0x2192 | 78.1 | The directory service binding must be renegotiated due to a change in the server extensions information. |
| 0x2193 | 78.1 | Operation not allowed on a disabled cross ref. |
| 0x2194 | 78.1 | Schema update failed: No values for msDS-IntId are available. |
| 0x2195 | 78.1 | Schema update failed: Duplicate msDS-INtId. Retry the operation. |
| 0x2196 | 78.1 | Schema deletion failed: attribute is used in rDNAttID. |
| 0x2197 | 78.1 | The directory service failed to authorize the request. |
| 0x2198 | 78.1 | The Directory Service cannot process the script because it is invalid. |
| 0x2199 | 78.1 | The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data. |
| 0x219a | 78.1 | A cross reference is in use locally with the same name. |
| 0x219b | 78.1 | 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. |
| 0x219c | 78.1 | Writeable NCs prevent this DC from demoting. |
| 0x219d | 78.1 | The requested object has a non-unique identifier and cannot be retrieved. |
| 0x219e | 78.1 | Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected. |
| 0x219f | 78.1 | The group cannot be converted due to attribute restrictions on the requested group type. |
| 0x21a0 | 78.1 | Cross-domain move of non-empty basic application groups is not allowed. |
| 0x21a1 | 78.1 | Cross-domain move of non-empty query based application groups is not allowed. |
| 0x21a2 | 78.1 | The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner. |
| 0x21a3 | 78.1 | The target container for a redirection of a well known object container cannot already be a special container. |
| 0x21a4 | 78.1 | The Directory Service cannot perform the requested operation because a domain rename operation is in progress. |
| 0x21a5 | 78.1 | The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method. |
| 0x21a6 | 78.1 | The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. |
| 0x21a7 | 78.1 | The requested operation is not allowed on an object under the system container. |
| 0x21a8 | 7 | The LDAP servers network send queue has filled up because the client is not processing the results of it's 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. |
| 0x21a9 | 78.1 | 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. |
| 0x21aa | 78.1 | 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. |
| 0x21ab | 78.1 | The site settings object for the specified site does not exist. |
| 0x21ac | 78.1 | The local account store does not contain secret material for the specified account. |
| 0x21ad | 78.1 | Could not find a writable domain controller in the domain. |
| 0x21ae | 78.1 | The server object for the domain controller does not exist. |
| 0x21af | 78.1 | The NTDS Settings object for the domain controller does not exist. |
| 0x21b0 | 78.1 | The requested search operation is not supported for ASQ searches. |
| 0x21b1 | 78.1 | A required audit event could not be generated for the operation. |
| 0x21b2 | 78.1 | The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes. |
| 0x21b3 | 78.1 | The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings. |
| 0x21b4 | 78.1 | The address books are nested too deeply. Failed to build the hierarchy table. |
| 0x21b5 | 78.1 | The specified up-to-date-ness vector is corrupt. |
| 0x21b6 | 78.1 | The request to replicate secrets is denied. |
| 0x21b7 | 78.1 | Schema update failed: The MAPI identifier is reserved. |
| 0x21b8 | 78.1 | Schema update failed: There are no MAPI identifiers available. |
| 0x21b9 | 78.1 | The replication operation failed because the required attributes of the local krbtgt object are missing. |
| 0x21ba | 78.1 | The domain name of the trusted domain already exists in the forest. |
| 0x21bb | 78.1 | The flat name of the trusted domain already exists in the forest. |
| 0x21bc | 78.1 | The User Principal Name (UPN) is invalid. |
| 0x21bd | 78.1 | OID mapped groups cannot have members. |
| 0x21be | 78.1 | The specified OID cannot be found. |
| 0x21bf | 78.1 | The replication operation failed because the target object referred by a link value is recycled. |
| 0x2329 | 78.1 | DNS server unable to interpret format. |
| 0x232a | 78.1 | DNS server failure. |
| 0x232b | 78.1 | DNS name does not exist. |
| 0x232c | 78.1 | DNS request not supported by name server. |
| 0x232d | 78.1 | DNS operation refused. |
| 0x232e | 78.1 | DNS name that ought not exist, does exist. |
| 0x232f | 78.1 | DNS RR set that ought not exist, does exist. |
| 0x2330 | 78.1 | DNS RR set that ought to exist, does not exist. |
| 0x2331 | 78.1 | DNS server not authoritative for zone. |
| 0x2332 | 78.1 | DNS name in update or prereq is not in zone. |
| 0x2338 | 78.1 | DNS signature failed to verify. |
| 0x2339 | 78.1 | DNS bad key. |
| 0x233a | 78.1 | DNS signature validity expired. |
| 0x251d | 78.1 | No records found for given DNS query. |
| 0x251e | 78.1 | Bad DNS packet. |
| 0x251f | 78.1 | No DNS packet. |
| 0x2520 | 78.1 | DNS error, check rcode. |
| 0x2521 | 78.1 | Unsecured DNS packet. |
| 0x254f | 78.1 | Invalid DNS type. |
| 0x2550 | 78.1 | Invalid IP address. |
| 0x2551 | 78.1 | Invalid property. |
| 0x2552 | 78.1 | Try DNS operation again later. |
| 0x2553 | 78.1 | Record for given name and type is not unique. |
| 0x2554 | 78.1 | DNS name does not comply with RFC specifications. |
| 0x2555 | 78.1 | DNS name is a fully-qualified DNS name. |
| 0x2556 | 78.1 | DNS name is dotted (multi-label). |
| 0x2557 | 78.1 | DNS name is a single-part name. |
| 0x2558 | 78.1 | DNS name contains an invalid character. |
| 0x2559 | 78.1 | DNS name is entirely numeric. |
| 0x255a | 78.1 | The operation requested is not permitted on a DNS root server. |
| 0x255b | 78.1 | The record could not be created because this part of the DNS namespace has been delegated to another server. |
| 0x255c | 78.1 | The DNS server could not find a set of root hints. |
| 0x255d | 78.1 | The DNS server found root hints but they were not consistent across all adapters. |
| 0x255e | 78.1 | The specified value is too small for this parameter. |
| 0x255f | 78.1 | The specified value is too large for this parameter. |
| 0x2560 | 78.1 | This operation is not allowed while the DNS server is loading zones in the background. Please try again later. |
| 0x2561 | 78.1 | The operation requested is not permitted on against a DNS server running on a read-only DC. |
| 0x2562 | 78.1 | No data is allowed to exist underneath a DNAME record. |
| 0x2563 | 78.1 | This operation requires credentials delegation. |
| 0x2564 | 78.1 | Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. |
| 0x2581 | 78.1 | DNS zone does not exist. |
| 0x2582 | 78.1 | DNS zone information not available. |
| 0x2583 | 78.1 | Invalid operation for DNS zone. |
| 0x2584 | 78.1 | Invalid DNS zone configuration. |
| 0x2585 | 78.1 | DNS zone has no start of authority (SOA) record. |
| 0x2586 | 78.1 | DNS zone has no Name Server (NS) record. |
| 0x2587 | 78.1 | DNS zone is locked. |
| 0x2588 | 78.1 | DNS zone creation failed. |
| 0x2589 | 78.1 | DNS zone already exists. |
| 0x258a | 78.1 | DNS automatic zone already exists. |
| 0x258b | 78.1 | Invalid DNS zone type. |
| 0x258c | 78.1 | Secondary DNS zone requires master IP address. |
| 0x258d | 78.1 | DNS zone not secondary. |
| 0x258e | 78.1 | Need secondary IP address. |
| 0x258f | 78.1 | WINS initialization failed. |
| 0x2590 | 78.1 | Need WINS servers. |
| 0x2591 | 78.1 | NBTSTAT initialization call failed. |
| 0x2592 | 78.1 | Invalid delete of start of authority (SOA) |
| 0x2593 | 78.1 | A conditional forwarding zone already exists for that name. |
| 0x2594 | 78.1 | This zone must be configured with one or more master DNS server IP addresses. |
| 0x2595 | 7 | The operation cannot be performed because this zone is shutdown. |
| 0x25b3 | 78.1 | Primary DNS zone requires datafile. |
| 0x25b4 | 78.1 | Invalid datafile name for DNS zone. |
| 0x25b5 | 78.1 | Failed to open datafile for DNS zone. |
| 0x25b6 | 78.1 | Failed to write datafile for DNS zone. |
| 0x25b7 | 78.1 | Failure while reading datafile for DNS zone. |
| 0x25e5 | 78.1 | DNS record does not exist. |
| 0x25e6 | 78.1 | DNS record format error. |
| 0x25e7 | 78.1 | Node creation failure in DNS. |
| 0x25e8 | 78.1 | Unknown DNS record type. |
| 0x25e9 | 78.1 | DNS record timed out. |
| 0x25ea | 78.1 | Name not in DNS zone. |
| 0x25eb | 78.1 | CNAME loop detected. |
| 0x25ec | 78.1 | Node is a CNAME DNS record. |
| 0x25ed | 78.1 | A CNAME record already exists for given name. |
| 0x25ee | 78.1 | Record only at DNS zone root. |
| 0x25ef | 78.1 | DNS record already exists. |
| 0x25f0 | 78.1 | Secondary DNS zone data error. |
| 0x25f1 | 78.1 | Could not create DNS cache data. |
| 0x25f2 | 78.1 | DNS name does not exist. |
| 0x25f3 | 78.1 | Could not create pointer (PTR) record. |
| 0x25f4 | 78.1 | DNS domain was undeleted. |
| 0x25f5 | 78.1 | The directory service is unavailable. |
| 0x25f6 | 78.1 | DNS zone already exists in the directory service. |
| 0x25f7 | 78.1 | DNS server not creating or reading the boot file for the directory service integrated DNS zone. |
| 0x25f8 | 78.1 | Node is a DNAME DNS record. |
| 0x25f9 | 78.1 | A DNAME record already exists for given name. |
| 0x25fa | 78.1 | An alias loop has been detected with either CNAME or DNAME records. |
| 0x2617 | 78.1 | DNS AXFR (zone transfer) complete. |
| 0x2618 | 78.1 | DNS zone transfer failed. |
| 0x2619 | 78.1 | Added local WINS server. |
| 0x2649 | 78.1 | Secure update call needs to continue update request. |
| 0x267b | 78.1 | TCP/IP network protocol not installed. |
| 0x267c | 78.1 | No DNS servers configured for local system. |
| 0x26ad | 78.1 | The specified directory partition does not exist. |
| 0x26ae | 78.1 | The specified directory partition already exists. |
| 0x26af | 78.1 | This DNS server is not enlisted in the specified directory partition. |
| 0x26b0 | 78.1 | This DNS server is already enlisted in the specified directory partition. |
| 0x26b1 | 78.1 | The directory partition is not available at this time. Please wait a few minutes and try again. |
| 0x26b2 | 7 | The application directory partition operation failed. The domain controller holding the domain naming master role is down or unable to service the request or is not running Windows Server 2003. |
| 0x2714 | 78.1 | A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| 0x2719 | 78.1 | The file handle supplied is not valid. |
| 0x271d | 78.1 | An attempt was made to access a socket in a way forbidden by its access permissions. |
| 0x271e | 78.1 | The system detected an invalid pointer address in attempting to use a pointer argument in a call. |
| 0x2726 | 78.1 | An invalid argument was supplied. |
| 0x2728 | 78.1 | Too many open sockets. |
| 0x2733 | 78.1 | A non-blocking socket operation could not be completed immediately. |
| 0x2734 | 78.1 | A blocking operation is currently executing. |
| 0x2735 | 78.1 | An operation was attempted on a non-blocking socket that already had an operation in progress. |
| 0x2736 | 78.1 | An operation was attempted on something that is not a socket. |
| 0x2737 | 78.1 | A required address was omitted from an operation on a socket. |
| 0x2738 | 78.1 | A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. |
| 0x2739 | 78.1 | A protocol was specified in the socket function call that does not support the semantics of the socket type requested. |
| 0x273a | 78.1 | An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call. |
| 0x273b | 78.1 | The requested protocol has not been configured into the system, or no implementation for it exists. |
| 0x273c | 78.1 | The support for the specified socket type does not exist in this address family. |
| 0x273d | 78.1 | The attempted operation is not supported for the type of object referenced. |
| 0x273e | 78.1 | The protocol family has not been configured into the system or no implementation for it exists. |
| 0x273f | 78.1 | An address incompatible with the requested protocol was used. |
| 0x2740 | 78.1 | Only one usage of each socket address (protocol/network address/port) is normally permitted. |
| 0x2741 | 78.1 | The requested address is not valid in its context. |
| 0x2742 | 78.1 | A socket operation encountered a dead network. |
| 0x2743 | 78.1 | A socket operation was attempted to an unreachable network. |
| 0x2744 | 78.1 | The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. |
| 0x2745 | 78.1 | An established connection was aborted by the software in your host machine. |
| 0x2746 | 78.1 | An existing connection was forcibly closed by the remote host. |
| 0x2747 | 78.1 | An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. |
| 0x2748 | 78.1 | A connect request was made on an already connected socket. |
| 0x2749 | 78.1 | A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. |
| 0x274a | 78.1 | A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. |
| 0x274b | 78.1 | Too many references to some kernel object. |
| 0x274c | 78.1 | A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. |
| 0x274d | 78.1 | No connection could be made because the target machine actively refused it. |
| 0x274e | 78.1 | Cannot translate name. |
| 0x274f | 78.1 | Name component or name was too long. |
| 0x2750 | 78.1 | A socket operation failed because the destination host was down. |
| 0x2751 | 78.1 | A socket operation was attempted to an unreachable host. |
| 0x2752 | 78.1 | Cannot remove a directory that is not empty. |
| 0x2753 | 78.1 | A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. |
| 0x2754 | 78.1 | Ran out of quota. |
| 0x2755 | 78.1 | Ran out of disk quota. |
| 0x2756 | 78.1 | File handle reference is no longer available. |
| 0x2757 | 78.1 | Item is not available locally. |
| 0x276b | 78.1 | WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. |
| 0x276c | 78.1 | The Windows Sockets version requested is not supported. |
| 0x276d | 78.1 | Either the application has not called WSAStartup, or WSAStartup failed. |
| 0x2775 | 78.1 | Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence. |
| 0x2776 | 78.1 | No more results can be returned by WSALookupServiceNext. |
| 0x2777 | 78.1 | A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. |
| 0x2778 | 78.1 | The procedure call table is invalid. |
| 0x2779 | 78.1 | The requested service provider is invalid. |
| 0x277a | 78.1 | The requested service provider could not be loaded or initialized. |
| 0x277b | 78.1 | A system call has failed. |
| 0x277c | 78.1 | No such service is known. The service cannot be found in the specified name space. |
| 0x277d | 78.1 | The specified class was not found. |
| 0x277e | 78.1 | No more results can be returned by WSALookupServiceNext. |
| 0x277f | 78.1 | A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. |
| 0x2780 | 78.1 | A database query failed because it was actively refused. |
| 0x2af9 | 78.1 | No such host is known. |
| 0x2afa | 78.1 | This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. |
| 0x2afb | 78.1 | A non-recoverable error occurred during a database lookup. |
| 0x2afc | 78.1 | The requested name is valid, but no data of the requested type was found. |
| 0x2afd | 78.1 | At least one reserve has arrived. |
| 0x2afe | 78.1 | At least one path has arrived. |
| 0x2aff | 78.1 | There are no senders. |
| 0x2b00 | 78.1 | There are no receivers. |
| 0x2b01 | 78.1 | Reserve has been confirmed. |
| 0x2b02 | 78.1 | Error due to lack of resources. |
| 0x2b03 | 78.1 | Rejected for administrative reasons - bad credentials. |
| 0x2b04 | 78.1 | Unknown or conflicting style. |
| 0x2b05 | 78.1 | Problem with some part of the filterspec or providerspecific buffer in general. |
| 0x2b06 | 78.1 | Problem with some part of the flowspec. |
| 0x2b07 | 78.1 | General QOS error. |
| 0x2b08 | 78.1 | An invalid or unrecognized service type was found in the flowspec. |
| 0x2b09 | 78.1 | An invalid or inconsistent flowspec was found in the QOS structure. |
| 0x2b0a | 78.1 | Invalid QOS provider-specific buffer. |
| 0x2b0b | 78.1 | An invalid QOS filter style was used. |
| 0x2b0c | 78.1 | An invalid QOS filter type was used. |
| 0x2b0d | 78.1 | An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR. |
| 0x2b0e | 78.1 | An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer. |
| 0x2b0f | 78.1 | An incorrect number of flow descriptors was specified in the QOS structure. |
| 0x2b10 | 78.1 | An unrecognized object was found in the QOS provider-specific buffer. |
| 0x2b11 | 78.1 | An invalid policy object was found in the QOS provider-specific buffer. |
| 0x2b12 | 78.1 | An invalid QOS flow descriptor was found in the flow descriptor list. |
| 0x2b13 | 78.1 | An invalid or inconsistent flowspec was found in the QOS provider specific buffer. |
| 0x2b14 | 78.1 | An invalid FILTERSPEC was found in the QOS provider-specific buffer. |
| 0x2b15 | 78.1 | An invalid shape discard mode object was found in the QOS provider specific buffer. |
| 0x2b16 | 78.1 | An invalid shaping rate object was found in the QOS provider-specific buffer. |
| 0x2b17 | 78.1 | A reserved policy element was found in the QOS provider-specific buffer. |
| 0x2b18 | 78.1 | No such host is known securely. |
| 0x2b19 | 78.1 | Name based IPSEC policy could not be added. |
| 0x32c8 | 78.1 | The specified quick mode policy already exists. |
| 0x32c9 | 78.1 | The specified quick mode policy was not found. |
| 0x32ca | 78.1 | The specified quick mode policy is being used. |
| 0x32cb | 78.1 | The specified main mode policy already exists. |
| 0x32cc | 78.1 | The specified main mode policy was not found |
| 0x32cd | 78.1 | The specified main mode policy is being used. |
| 0x32ce | 78.1 | The specified main mode filter already exists. |
| 0x32cf | 78.1 | The specified main mode filter was not found. |
| 0x32d0 | 78.1 | The specified transport mode filter already exists. |
| 0x32d1 | 78.1 | The specified transport mode filter does not exist. |
| 0x32d2 | 78.1 | The specified main mode authentication list exists. |
| 0x32d3 | 78.1 | The specified main mode authentication list was not found. |
| 0x32d4 | 78.1 | The specified main mode authentication list is being used. |
| 0x32d5 | 78.1 | The specified default main mode policy was not found. |
| 0x32d6 | 78.1 | The specified default main mode authentication list was not found. |
| 0x32d7 | 78.1 | The specified default quick mode policy was not found. |
| 0x32d8 | 78.1 | The specified tunnel mode filter exists. |
| 0x32d9 | 78.1 | The specified tunnel mode filter was not found. |
| 0x32da | 78.1 | The Main Mode filter is pending deletion. |
| 0x32db | 78.1 | The transport filter is pending deletion. |
| 0x32dc | 78.1 | The tunnel filter is pending deletion. |
| 0x32dd | 78.1 | The Main Mode policy is pending deletion. |
| 0x32de | 78.1 | The Main Mode authentication bundle is pending deletion. |
| 0x32df | 78.1 | The Quick Mode policy is pending deletion. |
| 0x32e0 | 78.1 | The Main Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x32e1 | 78.1 | The Quick Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x35e8 | 78.1 | ERROR_IPSEC_IKE_NEG_STATUS_BEGIN |
| 0x35e9 | 78.1 | IKE authentication credentials are unacceptable |
| 0x35ea | 78.1 | IKE security attributes are unacceptable |
| 0x35eb | 78.1 | IKE Negotiation in progress |
| 0x35ec | 78.1 | General processing error |
| 0x35ed | 78.1 | Negotiation timed out |
| 0x35ee | 78.1 | IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store. |
| 0x35ef | 78.1 | IKE SA deleted by peer before establishment completed |
| 0x35f0 | 78.1 | IKE SA deleted before establishment completed |
| 0x35f1 | 78.1 | Negotiation request sat in Queue too long |
| 0x35f2 | 78.1 | Negotiation request sat in Queue too long |
| 0x35f3 | 78.1 | Negotiation request sat in Queue too long |
| 0x35f4 | 78.1 | Negotiation request sat in Queue too long |
| 0x35f5 | 78.1 | No response from peer |
| 0x35f6 | 78.1 | Negotiation took too long |
| 0x35f7 | 78.1 | Negotiation took too long |
| 0x35f8 | 78.1 | Unknown error occurred |
| 0x35f9 | 78.1 | Certificate Revocation Check failed |
| 0x35fa | 78.1 | Invalid certificate key usage |
| 0x35fb | 78.1 | Invalid certificate type |
| 0x35fc | 78.1 | 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. |
| 0x35fd | 78.1 | Simultaneous rekeys were detected. |
| 0x35fe | 78.1 | Failure in Diffie-Hellman computation |
| 0x35ff | 78.1 | Don't know how to process critical payload |
| 0x3600 | 78.1 | Invalid header |
| 0x3601 | 78.1 | No policy configured |
| 0x3602 | 78.1 | Failed to verify signature |
| 0x3603 | 78.1 | Failed to authenticate using Kerberos |
| 0x3604 | 78.1 | Peer's certificate did not have a public key |
| 0x3605 | 78.1 | Error processing error payload |
| 0x3606 | 78.1 | Error processing SA payload |
| 0x3607 | 78.1 | Error processing Proposal payload |
| 0x3608 | 78.1 | Error processing Transform payload |
| 0x3609 | 78.1 | Error processing KE payload |
| 0x360a | 78.1 | Error processing ID payload |
| 0x360b | 78.1 | Error processing Cert payload |
| 0x360c | 78.1 | Error processing Certificate Request payload |
| 0x360d | 78.1 | Error processing Hash payload |
| 0x360e | 78.1 | Error processing Signature payload |
| 0x360f | 78.1 | Error processing Nonce payload |
| 0x3610 | 78.1 | Error processing Notify payload |
| 0x3611 | 78.1 | Error processing Delete Payload |
| 0x3612 | 78.1 | Error processing VendorId payload |
| 0x3613 | 78.1 | Invalid payload received |
| 0x3614 | 78.1 | Soft SA loaded |
| 0x3615 | 78.1 | Soft SA torn down |
| 0x3616 | 78.1 | Invalid cookie received. |
| 0x3617 | 78.1 | Peer failed to send valid machine certificate |
| 0x3618 | 78.1 | Certification Revocation check of peer's certificate failed |
| 0x3619 | 78.1 | New policy invalidated SAs formed with old policy |
| 0x361a | 78.1 | There is no available Main Mode IKE policy. |
| 0x361b | 78.1 | Failed to enabled TCB privilege. |
| 0x361c | 78.1 | Failed to load SECURITY.DLL. |
| 0x361d | 78.1 | Failed to obtain security function table dispatch address from SSPI. |
| 0x361e | 78.1 | Failed to query Kerberos package to obtain max token size. |
| 0x361f | 78.1 | 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. |
| 0x3620 | 78.1 | Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes). |
| 0x3621 | 7 | 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. |
| 0x3622 | 78.1 | Given filter is invalid |
| 0x3623 | 78.1 | Memory allocation failed. |
| 0x3624 | 7 | 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. |
| 0x3625 | 78.1 | Invalid policy |
| 0x3626 | 78.1 | Invalid DOI |
| 0x3627 | 78.1 | Invalid situation |
| 0x3628 | 78.1 | Diffie-Hellman failure |
| 0x3629 | 78.1 | Invalid Diffie-Hellman group |
| 0x362a | 78.1 | Error encrypting payload |
| 0x362b | 78.1 | Error decrypting payload |
| 0x362c | 78.1 | Policy match error |
| 0x362d | 78.1 | Unsupported ID |
| 0x362e | 78.1 | Hash verification failed |
| 0x362f | 78.1 | Invalid hash algorithm |
| 0x3630 | 78.1 | Invalid hash size |
| 0x3631 | 78.1 | Invalid encryption algorithm |
| 0x3632 | 78.1 | Invalid authentication algorithm |
| 0x3633 | 78.1 | Invalid certificate signature |
| 0x3634 | 78.1 | Load failed |
| 0x3635 | 78.1 | Deleted via RPC call |
| 0x3636 | 7 | Temporary state created to perform reinit. This is not a real failure. |
| 0x3637 | 78.1 | 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. |
| 0x3638 | 78.1 | The recipient cannot handle version of IKE specified in the header. |
| 0x3639 | 78.1 | Key length in certificate is too small for configured security requirements. |
| 0x363a | 78.1 | Max number of established MM SAs to peer exceeded. |
| 0x363b | 78.1 | IKE received a policy that disables negotiation. |
| 0x363c | 78.1 | Reached maximum quick mode limit for the main mode. New main mode will be started. |
| 0x363d | 78.1 | Main mode SA lifetime expired or peer sent a main mode delete. |
| 0x363e | 78.1 | Main mode SA assumed to be invalid because peer stopped responding. |
| 0x363f | 78.1 | Certificate doesn't chain to a trusted root in IPsec policy. |
| 0x3640 | 78.1 | Received unexpected message ID. |
| 0x3641 | 78.1 | Received invalid authentication offers. |
| 0x3642 | 78.1 | Sent DoS cookie notify to initiator. |
| 0x3643 | 78.1 | IKE service is shutting down. |
| 0x3644 | 78.1 | Could not verify binding between CGA address and certificate. |
| 0x3645 | 78.1 | Error processing NatOA payload. |
| 0x3646 | 78.1 | Parameters of the main mode are invalid for this quick mode. |
| 0x3647 | 78.1 | Quick mode SA was expired by IPsec driver. |
| 0x3648 | 78.1 | Too many dynamically added IKEEXT filters were detected. |
| 0x3649 | 78.1 | ERROR_IPSEC_IKE_NEG_STATUS_END |
| 0x364a | 7 | NAP reauth succeeded and must delete the dummy NAP IkeV2 tunnel. |
| 0x364b | 7 | Error in assigning inner IP address to intiator in tunnel mode. |
| 0x364c | 78.1 | Require configuration payload missing. |
| 0x364d | 78.1 | A negotiation running as the security principle who issued the connection is in progress |
| 0x364e | 78.1 | SA was deleted due to IKEv1/AuthIP co-existence suppress check. |
| 0x364f | 78.1 | Incoming SA request was dropped due to peer IP address rate limiting. |
| 0x3650 | 78.1 | Peer does not support MOBIKE. |
| 0x3651 | 78.1 | SA establishment is not authorized. |
| 0x3652 | 78.1 | SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. |
| 0x3653 | 78.1 | SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard. |
| 0x3654 | 78.1 | 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. |
| 0x3655 | 78.1 | ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END |
| 0x3656 | 78.1 | The SPI in the packet does not match a valid IPsec SA. |
| 0x3657 | 78.1 | Packet was received on an IPsec SA whose lifetime has expired. |
| 0x3658 | 78.1 | Packet was received on an IPsec SA that does not match the packet characteristics. |
| 0x3659 | 78.1 | Packet sequence number replay check failed. |
| 0x365a | 78.1 | IPsec header and/or trailer in the packet is invalid. |
| 0x365b | 78.1 | IPsec integrity check failed. |
| 0x365c | 78.1 | IPsec dropped a clear text packet. |
| 0x365d | 78.1 | IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
| 0x365e | 78.1 | IPsec dropped a packet due to DoS throttling. |
| 0x3665 | 78.1 | IPsec DoS Protection matched an explicit block rule. |
| 0x3666 | 78.1 | IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. |
| 0x3667 | 78.1 | IPsec DoS Protection received an incorrectly formatted packet. |
| 0x3668 | 78.1 | IPsec DoS Protection failed to look up state. |
| 0x3669 | 78.1 | IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. |
| 0x366a | 78.1 | IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
| 0x366b | 78.1 | IPsec DoS Protection has not been enabled. |
| 0x366c | 78.1 | 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. |
| 0x36b0 | 78.1 | The requested section was not present in the activation context. |
| 0x36b1 | 78.1 | 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. |
| 0x36b2 | 78.1 | The application binding data format is invalid. |
| 0x36b3 | 78.1 | The referenced assembly is not installed on your system. |
| 0x36b4 | 78.1 | The manifest file does not begin with the required tag and format information. |
| 0x36b5 | 78.1 | The manifest file contains one or more syntax errors. |
| 0x36b6 | 78.1 | The application attempted to activate a disabled activation context. |
| 0x36b7 | 78.1 | The requested lookup key was not found in any active activation context. |
| 0x36b8 | 78.1 | A component version required by the application conflicts with another component version already active. |
| 0x36b9 | 78.1 | The type requested activation context section does not match the query API used. |
| 0x36ba | 78.1 | Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
| 0x36bb | 78.1 | An attempt to set the process default activation context failed because the process default activation context was already set. |
| 0x36bc | 78.1 | The encoding group identifier specified is not recognized. |
| 0x36bd | 78.1 | The encoding requested is not recognized. |
| 0x36be | 78.1 | The manifest contains a reference to an invalid URI. |
| 0x36bf | 78.1 | The application manifest contains a reference to a dependent assembly which is not installed |
| 0x36c0 | 78.1 | The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed |
| 0x36c1 | 78.1 | The manifest contains an attribute for the assembly identity which is not valid. |
| 0x36c2 | 78.1 | The manifest is missing the required default namespace specification on the assembly element. |
| 0x36c3 | 78.1 | The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1". |
| 0x36c4 | 78.1 | The private manifest probed has crossed a path with an unsupported reparse point. |
| 0x36c5 | 78.1 | Two or more components referenced directly or indirectly by the application manifest have files by the same name. |
| 0x36c6 | 78.1 | Two or more components referenced directly or indirectly by the application manifest have window classes with the same name. |
| 0x36c7 | 78.1 | Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs. |
| 0x36c8 | 78.1 | Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs. |
| 0x36c9 | 78.1 | Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs. |
| 0x36ca | 78.1 | Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs. |
| 0x36cb | 78.1 | Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted. |
| 0x36cc | 78.1 | A component's file does not match the verification information present in the component manifest. |
| 0x36cd | 78.1 | The policy manifest contains one or more syntax errors. |
| 0x36ce | 78.1 | Manifest Parse Error : A string literal was expected, but no opening quote character was found. |
| 0x36cf | 78.1 | Manifest Parse Error : Incorrect syntax was used in a comment. |
| 0x36d0 | 78.1 | Manifest Parse Error : A name was started with an invalid character. |
| 0x36d1 | 78.1 | Manifest Parse Error : A name contained an invalid character. |
| 0x36d2 | 78.1 | Manifest Parse Error : A string literal contained an invalid character. |
| 0x36d3 | 78.1 | Manifest Parse Error : Invalid syntax for an xml declaration. |
| 0x36d4 | 78.1 | Manifest Parse Error : An Invalid character was found in text content. |
| 0x36d5 | 78.1 | Manifest Parse Error : Required white space was missing. |
| 0x36d6 | 78.1 | Manifest Parse Error : The character '>' was expected. |
| 0x36d7 | 78.1 | Manifest Parse Error : A semi colon character was expected. |
| 0x36d8 | 78.1 | Manifest Parse Error : Unbalanced parentheses. |
| 0x36d9 | 78.1 | Manifest Parse Error : Internal error. |
| 0x36da | 78.1 | Manifest Parse Error : Whitespace is not allowed at this location. |
| 0x36db | 78.1 | Manifest Parse Error : End of file reached in invalid state for current encoding. |
| 0x36dc | 78.1 | Manifest Parse Error : Missing parenthesis. |
| 0x36dd | 78.1 | Manifest Parse Error : A single or double closing quote character (\' or \") is missing. |
| 0x36de | 78.1 | Manifest Parse Error : Multiple colons are not allowed in a name. |
| 0x36df | 78.1 | Manifest Parse Error : Invalid character for decimal digit. |
| 0x36e0 | 78.1 | Manifest Parse Error : Invalid character for hexadecimal digit. |
| 0x36e1 | 78.1 | Manifest Parse Error : Invalid unicode character value for this platform. |
| 0x36e2 | 78.1 | Manifest Parse Error : Expecting whitespace or '?'. |
| 0x36e3 | 78.1 | Manifest Parse Error : End tag was not expected at this location. |
| 0x36e4 | 78.1 | Manifest Parse Error : The following tags were not closed: %1. |
| 0x36e5 | 78.1 | Manifest Parse Error : Duplicate attribute. |
| 0x36e6 | 78.1 | Manifest Parse Error : Only one top level element is allowed in an XML document. |
| 0x36e7 | 78.1 | Manifest Parse Error : Invalid at the top level of the document. |
| 0x36e8 | 78.1 | Manifest Parse Error : Invalid xml declaration. |
| 0x36e9 | 78.1 | Manifest Parse Error : XML document must have a top level element. |
| 0x36ea | 78.1 | Manifest Parse Error : Unexpected end of file. |
| 0x36eb | 78.1 | Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset. |
| 0x36ec | 78.1 | Manifest Parse Error : Element was not closed. |
| 0x36ed | 78.1 | Manifest Parse Error : End element was missing the character '>'. |
| 0x36ee | 78.1 | Manifest Parse Error : A string literal was not closed. |
| 0x36ef | 78.1 | Manifest Parse Error : A comment was not closed. |
| 0x36f0 | 78.1 | Manifest Parse Error : A declaration was not closed. |
| 0x36f1 | 78.1 | Manifest Parse Error : A CDATA section was not closed. |
| 0x36f2 | 78.1 | Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml". |
| 0x36f3 | 78.1 | Manifest Parse Error : System does not support the specified encoding. |
| 0x36f4 | 78.1 | Manifest Parse Error : Switch from current encoding to specified encoding not supported. |
| 0x36f5 | 78.1 | Manifest Parse Error : The name 'xml' is reserved and must be lower case. |
| 0x36f6 | 78.1 | Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'. |
| 0x36f7 | 78.1 | Manifest Parse Error : The standalone attribute cannot be used in external entities. |
| 0x36f8 | 78.1 | Manifest Parse Error : Invalid version number. |
| 0x36f9 | 78.1 | Manifest Parse Error : Missing equals sign between attribute and attribute value. |
| 0x36fa | 78.1 | Assembly Protection Error : Unable to recover the specified assembly. |
| 0x36fb | 78.1 | Assembly Protection Error : The public key for an assembly was too short to be allowed. |
| 0x36fc | 78.1 | Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest. |
| 0x36fd | 78.1 | An HRESULT could not be translated to a corresponding Win32 error code. |
| 0x36fe | 78.1 | Assembly Protection Error : The catalog for an assembly is missing. |
| 0x36ff | 78.1 | The supplied assembly identity is missing one or more attributes which must be present in this context. |
| 0x3700 | 78.1 | The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names. |
| 0x3701 | 78.1 | The referenced assembly could not be found. |
| 0x3702 | 78.1 | The activation context activation stack for the running thread of execution is corrupt. |
| 0x3703 | 78.1 | The application isolation metadata for this process or thread has become corrupt. |
| 0x3704 | 78.1 | The activation context being deactivated is not the most recently activated one. |
| 0x3705 | 78.1 | The activation context being deactivated is not active for the current thread of execution. |
| 0x3706 | 78.1 | The activation context being deactivated has already been deactivated. |
| 0x3707 | 78.1 | A component used by the isolation facility has requested to terminate the process. |
| 0x3708 | 78.1 | A kernel mode component is releasing a reference on an activation context. |
| 0x3709 | 78.1 | The activation context of system default assembly could not be generated. |
| 0x370a | 78.1 | The value of an attribute in an identity is not within the legal range. |
| 0x370b | 78.1 | The name of an attribute in an identity is not within the legal range. |
| 0x370c | 78.1 | An identity contains two definitions for the same attribute. |
| 0x370d | 78.1 | 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. |
| 0x370e | 78.1 | 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. |
| 0x370f | 78.1 | The public key token does not correspond to the public key specified. |
| 0x3710 | 78.1 | A substitution string had no mapping. |
| 0x3711 | 78.1 | The component must be locked before making the request. |
| 0x3712 | 78.1 | The component store has been corrupted. |
| 0x3713 | 78.1 | An advanced installer failed during setup or servicing. |
| 0x3714 | 78.1 | The character encoding in the XML declaration did not match the encoding used in the document. |
| 0x3715 | 78.1 | The identities of the manifests are identical but their contents are different. |
| 0x3716 | 78.1 | The component identities are different. |
| 0x3717 | 78.1 | The assembly is not a deployment. |
| 0x3718 | 78.1 | The file is not a part of the assembly. |
| 0x3719 | 78.1 | The size of the manifest exceeds the maximum allowed. |
| 0x371a | 78.1 | The setting is not registered. |
| 0x371b | 78.1 | One or more required members of the transaction are not present. |
| 0x371c | 78.1 | The SMI primitive installer failed during setup or servicing. |
| 0x371d | 78.1 | A generic command executable returned a result that indicates failure. |
| 0x371e | 78.1 | A component is missing file verification information in its manifest. |
| 0x3a98 | 78.1 | The specified channel path is invalid. |
| 0x3a99 | 78.1 | The specified query is invalid. |
| 0x3a9a | 78.1 | The publisher metadata cannot be found in the resource. |
| 0x3a9b | 78.1 | The template for an event definition cannot be found in the resource (error = %1). |
| 0x3a9c | 78.1 | The specified publisher name is invalid. |
| 0x3a9d | 78.1 | The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest |
| 0x3a9f | 78.1 | The specified channel could not be found. Check channel configuration. |
| 0x3aa0 | 78.1 | The specified xml text was not well-formed. See Extended Error for more details. |
| 0x3aa1 | 78.1 | 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. |
| 0x3aa2 | 78.1 | Configuration error. |
| 0x3aa3 | 78.1 | 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. |
| 0x3aa4 | 78.1 | Query result is currently at an invalid position. |
| 0x3aa5 | 78.1 | Registered MSXML doesn't support validation. |
| 0x3aa6 | 78.1 | 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. |
| 0x3aa7 | 78.1 | Can't perform a step operation from a term that does not represent an element set. |
| 0x3aa8 | 78.1 | Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants. |
| 0x3aa9 | 78.1 | 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. |
| 0x3aaa | 78.1 | This data type is currently unsupported. |
| 0x3aab | 78.1 | A syntax error occurred at position %1!d! |
| 0x3aac | 78.1 | This operator is unsupported by this implementation of the filter. |
| 0x3aad | 78.1 | The token encountered was unexpected. |
| 0x3aae | 78.1 | The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation. |
| 0x3aaf | 78.1 | 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. |
| 0x3ab0 | 78.1 | 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. |
| 0x3ab1 | 78.1 | The channel fails to activate. |
| 0x3ab2 | 78.1 | The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions. |
| 0x3ab3 | 78.1 | the message resource is present but the message is not found in the string/message table |
| 0x3ab4 | 78.1 | The message id for the desired message could not be found. |
| 0x3ab5 | 78.1 | The substitution string for insert index (%1) could not be found. |
| 0x3ab6 | 78.1 | The description string for parameter reference (%1) could not be found. |
| 0x3ab7 | 78.1 | The maximum number of replacements has been reached. |
| 0x3ab8 | 78.1 | The event definition could not be found for event id (%1). |
| 0x3ab9 | 78.1 | The locale specific resource for the desired message is not present. |
| 0x3aba | 78.1 | The resource is too old to be compatible. |
| 0x3abb | 78.1 | The resource is too new to be compatible. |
| 0x3abc | 78.1 | The channel at index %1!d! of the query can't be opened. |
| 0x3abd | 7 | The publisher has been disabled and its resource is not avaiable. This usually occurs when the publisher is in the process of being uninstalled or upgraded. |
| 0x3abe | 78.1 | Attempted to create a numeric type that is outside of its valid range. |
| 0x3ae8 | 78.1 | The subscription fails to activate. |
| 0x3ae9 | 78.1 | 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. |
| 0x3aea | 78.1 | When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription. |
| 0x3aeb | 78.1 | The credential store that is used to save credentials is full. |
| 0x3aec | 78.1 | The credential used by this subscription can't be found in credential store. |
| 0x3aed | 78.1 | No active channel is found for the query. |
| 0x3afc | 78.1 | The resource loader failed to find MUI file. |
| 0x3afd | 78.1 | The resource loader failed to load MUI file because the file fail to pass validation. |
| 0x3afe | 78.1 | The RC Manifest is corrupted with garbage data or unsupported version or missing required item. |
| 0x3aff | 78.1 | The RC Manifest has invalid culture name. |
| 0x3b00 | 78.1 | The RC Manifest has invalid ultimatefallback name. |
| 0x3b01 | 78.1 | The resource loader cache doesn't have loaded MUI entry. |
| 0x3b02 | 78.1 | User stopped resource enumeration. |
| 0x3b03 | 78.1 | UI language installation failed. |
| 0x3b04 | 78.1 | Locale installation failed. |
| 0x3b60 | 78.1 | 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. |
| 0x3b61 | 78.1 | The monitor's VCP Version (0xDF) VCP code returned an invalid version value. |
| 0x3b62 | 78.1 | The monitor does not comply with the MCCS specification it claims to support. |
| 0x3b63 | 78.1 | 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. |
| 0x3b64 | 78.1 | 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. |
| 0x3b65 | 78.1 | An internal Monitor Configuration API error occurred. |
| 0x3b66 | 78.1 | 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. |
| 0x3b67 | 78.1 | 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. |
| 0x3b92 | 78.1 | The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
| 0x3bc3 | 78.1 | The requested system device cannot be found. |
| 0x3bc4 | 78.1 | Hash generation for the specified hash version and hash type is not enabled on the server. |
| 0x3bc5 | 78.1 | The hash requested from the server is not available or no longer valid. |
| 0x30200 | 78.1 | The underlying file was converted to compound file format. |
| 0x30201 | 78.1 | The storage operation should block until more data is available. |
| 0x30202 | 78.1 | The storage operation should retry immediately. |
| 0x30203 | 78.1 | The notified event sink will not influence the storage operation. |
| 0x30204 | 78.1 | Multiple opens prevent consolidated. (commit succeeded). |
| 0x30205 | 78.1 | Consolidation of the storage file failed. (commit succeeded). |
| 0x30206 | 78.1 | Consolidation of the storage file is inappropriate. (commit succeeded). |
| 0x40000 | 78.1 | Use the registry database to provide the requested information |
| 0x40001 | 78.1 | Success, but static |
| 0x40002 | 78.1 | Macintosh clipboard format |
| 0x40100 | 78.1 | Successful drop took place |
| 0x40101 | 78.1 | Drag-drop operation canceled |
| 0x40102 | 78.1 | Use the default cursor |
| 0x40130 | 78.1 | Data has same FORMATETC |
| 0x40140 | 78.1 | View is already frozen |
| 0x40170 | 78.1 | FORMATETC not supported |
| 0x40171 | 78.1 | Same cache |
| 0x40172 | 78.1 | Some cache(s) not updated |
| 0x40180 | 78.1 | Invalid verb for OLE object |
| 0x40181 | 78.1 | Verb number is valid but verb cannot be done now |
| 0x40182 | 78.1 | Invalid window handle passed |
| 0x401a0 | 78.1 | Message is too long; some of it had to be truncated before displaying |
| 0x401c0 | 78.1 | Unable to convert OLESTREAM to IStorage |
| 0x401e2 | 78.1 | Moniker reduced to itself |
| 0x401e4 | 78.1 | Common prefix is this moniker |
| 0x401e5 | 78.1 | Common prefix is input moniker |
| 0x401e6 | 78.1 | Common prefix is both monikers |
| 0x401e7 | 78.1 | Moniker is already registered in running object table |
| 0x40200 | 78.1 | An event was able to invoke some but not all of the subscribers |
| 0x40202 | 78.1 | An event was delivered but there were no subscribers |
| 0x41300 | 78.1 | The task is ready to run at its next scheduled time. |
| 0x41301 | 78.1 | The task is currently running. |
| 0x41302 | 78.1 | The task will not run at the scheduled times because it has been disabled. |
| 0x41303 | 78.1 | The task has not yet run. |
| 0x41304 | 78.1 | There are no more runs scheduled for this task. |
| 0x41305 | 78.1 | One or more of the properties that are needed to run this task on a schedule have not been set. |
| 0x41306 | 78.1 | The last run of the task was terminated by the user. |
| 0x41307 | 78.1 | Either the task has no triggers or the existing triggers are disabled or not set. |
| 0x41308 | 78.1 | Event triggers don't have set run times. |
| 0x4131b | 7 | The task is registered, but not all specified triggers will start the task. |
| 0x4131c | 78.1 | The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal. |
| 0x41325 | 78.1 | The Task Scheduler service has asked the task to run. |
| 0x4d000 | 78.1 | An asynchronous operation was specified. The operation has begun, but its outcome is not known yet. |
| 0x4d001 | 78.1 | XACT_S_DEFECT |
| 0x4d002 | 78.1 | The method call succeeded because the transaction was read-only. |
| 0x4d003 | 78.1 | 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 |
| 0x4d004 | 78.1 | No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes. |
| 0x4d005 | 78.1 | The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call. |
| 0x4d006 | 78.1 | 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 |
| 0x4d007 | 78.1 | The transaction was successfully aborted. However, the abort was non-retaining. |
| 0x4d008 | 78.1 | An abort operation was already in progress. |
| 0x4d009 | 78.1 | The resource manager has performed a single-phase commit of the transaction. |
| 0x4d00a | 78.1 | The local transaction has not aborted. |
| 0x4d010 | 78.1 | The resource manager has requested to be the coordinator (last resource manager) for the transaction. |
| 0x80012 | 78.1 | Not all the requested interfaces were available |
| 0x80013 | 78.1 | The specified machine name was not found in the cache. |
| 0x90312 | 78.1 | The function completed successfully, but must be called again to complete the context |
| 0x90313 | 78.1 | The function completed successfully, but CompleteToken must be called |
| 0x90314 | 78.1 | The function completed successfully, but both CompleteToken and this function must be called to complete the context |
| 0x90315 | 78.1 | The logon was completed, but no network authority was available. The logon was made using locally known information |
| 0x90317 | 78.1 | The context has expired and can no longer be used. |
| 0x90320 | 78.1 | The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context. |
| 0x90321 | 78.1 | The context data must be renegotiated with the peer. |
| 0x90323 | 78.1 | There is no LSA mode context associated with this context. |
| 0x9035c | 78.1 | A signature operation must be performed before the user can authenticate. |
| 0x90360 | 78.1 | The recipient rejected the renegotiation request. |
| 0x91012 | 78.1 | The protected data needs to be re-protected. |
| 0x1f0001 | 78.1 | The IO was completed by a filter. |
| 0x261001 | 7 | Monitor descriptor could not be obtained. |
| 0x261002 | 7 | Format of the obtained monitor descriptor is not supported by this release. |
| 0x262307 | 78.1 | No mode is pinned on the specified VidPN source/target. |
| 0x26231e | 78.1 | Specified mode set does not specify preference for one of its modes. |
| 0x26234b | 78.1 | Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. |
| 0x26234c | 78.1 | Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. |
| 0x262351 | 78.1 | Specified content transformation is not pinned on the specified VidPN present path. |
| 0x263005 | 78.1 | {GDI redirection surface was returned} GDI redirection surface of the top level window was returned. |
| 0x300100 | 78.1 | Property value will be ignored. |
| 0x340001 | 78.1 | The request will be completed later by NDIS status indication. |
| 0x3c0105 | 78.1 | The troubleshooting pack cannot be executed on this system. |
| 0x3d0000 | 78.1 | The function call is completing asynchronously. |
| 0x3d0001 | 78.1 | There are no more messages available on the channel. |
| 0x4026200a | 78.1 | 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). |
| 0x4026242f | 78.1 | Child device presence was not reliably detected. |
| 0x40262437 | 78.1 | Starting the leadlink adapter has been deferred temporarily. |
| 0x40262439 | 78.1 | The display adapter is being polled for children too frequently at the same polling level. |
| 0x4026243a | 78.1 | Starting the adapter has been deferred temporarily. |
| 0x80000001 | 78.1 | Not implemented |
| 0x80000002 | 78.1 | Ran out of memory |
| 0x80000003 | 78.1 | One or more arguments are invalid |
| 0x80000004 | 78.1 | No such interface supported |
| 0x80000005 | 78.1 | Invalid pointer |
| 0x80000006 | 78.1 | Invalid handle |
| 0x80000007 | 78.1 | Operation aborted |
| 0x80000008 | 78.1 | Unspecified error |
| 0x80000009 | 78.1 | General access denied error |
| 0x8000000a | 78.1 | The data necessary to complete this operation is not yet available. |
| 0x80004001 | 78.1 | Not implemented |
| 0x80004002 | 78.1 | No such interface supported |
| 0x80004003 | 78.1 | Invalid pointer |
| 0x80004004 | 78.1 | Operation aborted |
| 0x80004005 | 78.1 | Unspecified error |
| 0x80004006 | 78.1 | Thread local storage failure |
| 0x80004007 | 78.1 | Get shared memory allocator failure |
| 0x80004008 | 78.1 | Get memory allocator failure |
| 0x80004009 | 78.1 | Unable to initialize class cache |
| 0x8000400a | 78.1 | Unable to initialize RPC services |
| 0x8000400b | 78.1 | Cannot set thread local storage channel control |
| 0x8000400c | 78.1 | Could not allocate thread local storage channel control |
| 0x8000400d | 78.1 | The user supplied memory allocator is unacceptable |
| 0x8000400e | 78.1 | The OLE service mutex already exists |
| 0x8000400f | 78.1 | The OLE service file mapping already exists |
| 0x80004010 | 78.1 | Unable to map view of file for OLE service |
| 0x80004011 | 78.1 | Failure attempting to launch OLE service |
| 0x80004012 | 78.1 | There was an attempt to call CoInitialize a second time while single threaded |
| 0x80004013 | 78.1 | A Remote activation was necessary but was not allowed |
| 0x80004014 | 78.1 | A Remote activation was necessary but the server name provided was invalid |
| 0x80004015 | 78.1 | The class is configured to run as a security id different from the caller |
| 0x80004016 | 78.1 | Use of Ole1 services requiring DDE windows is disabled |
| 0x80004017 | 78.1 | A RunAs specification must be |
| 0x80004018 | 78.1 | The server process could not be started. The pathname may be incorrect. |
| 0x80004019 | 78.1 | The server process could not be started as the configured identity. The pathname may be incorrect or unavailable. |
| 0x8000401a | 78.1 | The server process could not be started because the configured identity is incorrect. Check the username and password. |
| 0x8000401b | 78.1 | The client is not allowed to launch this server. |
| 0x8000401c | 78.1 | The service providing this server could not be started. |
| 0x8000401d | 78.1 | This computer was unable to communicate with the computer providing the server. |
| 0x8000401e | 78.1 | The server did not respond after being launched. |
| 0x8000401f | 78.1 | The registration information for this server is inconsistent or incomplete. |
| 0x80004020 | 78.1 | The registration information for this interface is inconsistent or incomplete. |
| 0x80004021 | 78.1 | The operation attempted is not supported. |
| 0x80004022 | 78.1 | A dll must be loaded. |
| 0x80004023 | 78.1 | A Microsoft Software Installer error was encountered. |
| 0x80004024 | 78.1 | The specified activation could not occur in the client context as specified. |
| 0x80004025 | 78.1 | Activations on the server are paused. |
| 0x80004026 | 78.1 | Activations on the server are not paused. |
| 0x80004027 | 78.1 | The component or application containing the component has been disabled. |
| 0x80004028 | 78.1 | The common language runtime is not available |
| 0x80004029 | 78.1 | The thread-pool rejected the submitted asynchronous work. |
| 0x8000402a | 78.1 | The server started, but did not finish initializing in a timely fashion. |
| 0x8000402b | 78.1 | Unable to complete the call since there is no COM+ security context inside IObjectControl.Activate. |
| 0x80004030 | 78.1 | The provided tracker configuration is invalid |
| 0x80004031 | 78.1 | The provided thread pool configuration is invalid |
| 0x80004032 | 78.1 | The provided side-by-side configuration is invalid |
| 0x80004033 | 78.1 | The server principal name (SPN) obtained during security negotiation is malformed. |
| 0x8000ffff | 78.1 | Catastrophic failure |
| 0x80010001 | 78.1 | Call was rejected by callee. |
| 0x80010002 | 78.1 | Call was canceled by the message filter. |
| 0x80010003 | 78.1 | The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage. |
| 0x80010004 | 78.1 | The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call. |
| 0x80010005 | 78.1 | It is illegal to call out while inside message filter. |
| 0x80010006 | 78.1 | The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid. |
| 0x80010007 | 78.1 | The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. |
| 0x80010008 | 78.1 | The caller (client) disappeared while the callee (server) was processing a call. |
| 0x80010009 | 78.1 | The data packet with the marshalled parameter data is incorrect. |
| 0x8001000a | 78.1 | The call was not transmitted properly; the message queue was full and was not emptied after yielding. |
| 0x8001000b | 78.1 | The client (caller) cannot marshall the parameter data - low memory, etc. |
| 0x8001000c | 78.1 | The client (caller) cannot unmarshall the return data - low memory, etc. |
| 0x8001000d | 78.1 | The server (callee) cannot marshall the return data - low memory, etc. |
| 0x8001000e | 78.1 | The server (callee) cannot unmarshall the parameter data - low memory, etc. |
| 0x8001000f | 78.1 | Received data is invalid; could be server or client data. |
| 0x80010010 | 78.1 | A particular parameter is invalid and cannot be (un)marshalled. |
| 0x80010011 | 78.1 | There is no second outgoing call on same channel in DDE conversation. |
| 0x80010012 | 78.1 | The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute. |
| 0x80010100 | 78.1 | System call failed. |
| 0x80010101 | 78.1 | Could not allocate some required resource (memory, events, ...) |
| 0x80010102 | 78.1 | Attempted to make calls on more than one thread in single threaded mode. |
| 0x80010103 | 78.1 | The requested interface is not registered on the server object. |
| 0x80010104 | 78.1 | RPC could not call the server or could not return the results of calling the server. |
| 0x80010105 | 78.1 | The server threw an exception. |
| 0x80010106 | 78.1 | Cannot change thread mode after it is set. |
| 0x80010107 | 78.1 | The method called does not exist on the server. |
| 0x80010108 | 78.1 | The object invoked has disconnected from its clients. |
| 0x80010109 | 78.1 | The object invoked chose not to process the call now. Try again later. |
| 0x8001010a | 78.1 | The message filter indicated that the application is busy. |
| 0x8001010b | 78.1 | The message filter rejected the call. |
| 0x8001010c | 78.1 | A call control interfaces was called with invalid data. |
| 0x8001010d | 78.1 | An outgoing call cannot be made since the application is dispatching an input-synchronous call. |
| 0x8001010e | 78.1 | The application called an interface that was marshalled for a different thread. |
| 0x8001010f | 78.1 | CoInitialize has not been called on the current thread. |
| 0x80010110 | 78.1 | The version of OLE on the client and server machines does not match. |
| 0x80010111 | 78.1 | OLE received a packet with an invalid header. |
| 0x80010112 | 78.1 | OLE received a packet with an invalid extension. |
| 0x80010113 | 78.1 | The requested object or interface does not exist. |
| 0x80010114 | 78.1 | The requested object does not exist. |
| 0x80010115 | 78.1 | OLE has sent a request and is waiting for a reply. |
| 0x80010116 | 78.1 | OLE is waiting before retrying a request. |
| 0x80010117 | 78.1 | Call context cannot be accessed after call completed. |
| 0x80010118 | 78.1 | Impersonate on unsecure calls is not supported. |
| 0x80010119 | 78.1 | Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized. |
| 0x8001011a | 78.1 | 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. |
| 0x8001011b | 78.1 | Access is denied. |
| 0x8001011c | 78.1 | Remote calls are not allowed for this process. |
| 0x8001011d | 78.1 | The marshaled interface data packet (OBJREF) has an invalid or unknown format. |
| 0x8001011e | 78.1 | No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call. |
| 0x8001011f | 78.1 | This operation returned because the timeout period expired. |
| 0x80010120 | 78.1 | There are no synchronize objects to wait on. |
| 0x80010121 | 78.1 | Full subject issuer chain SSL principal name expected from the server. |
| 0x80010122 | 78.1 | Principal name is not a valid MSSTD name. |
| 0x80010123 | 78.1 | Unable to impersonate DCOM client |
| 0x80010124 | 78.1 | Unable to obtain server's security context |
| 0x80010125 | 78.1 | Unable to open the access token of the current thread |
| 0x80010126 | 78.1 | Unable to obtain user info from an access token |
| 0x80010127 | 78.1 | The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method |
| 0x80010128 | 78.1 | Unable to obtain the client's security blanket |
| 0x80010129 | 78.1 | Unable to set a discretionary ACL into a security descriptor |
| 0x8001012a | 78.1 | The system function, AccessCheck, returned false |
| 0x8001012b | 78.1 | Either NetAccessDel or NetAccessAdd returned an error code. |
| 0x8001012c | 78.1 | One of the trustee strings provided by the user did not conform to the |
| 0x8001012d | 78.1 | One of the security identifiers provided by the user was invalid |
| 0x8001012e | 78.1 | Unable to convert a wide character trustee string to a multibyte trustee string |
| 0x8001012f | 78.1 | Unable to find a security identifier that corresponds to a trustee string provided by the user |
| 0x80010130 | 78.1 | The system function, LookupAccountSID, failed |
| 0x80010131 | 78.1 | Unable to find a trustee name that corresponds to a security identifier provided by the user |
| 0x80010132 | 78.1 | The system function, LookupAccountName, failed |
| 0x80010133 | 78.1 | Unable to set or reset a serialization handle |
| 0x80010134 | 78.1 | Unable to obtain the Windows directory |
| 0x80010135 | 78.1 | Path too long |
| 0x80010136 | 78.1 | Unable to generate a uuid. |
| 0x80010137 | 78.1 | Unable to create file |
| 0x80010138 | 78.1 | Unable to close a serialization handle or a file handle. |
| 0x80010139 | 78.1 | The number of ACEs in an ACL exceeds the system limit. |
| 0x8001013a | 78.1 | Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream. |
| 0x8001013b | 78.1 | The version of ACL format in the stream is not supported by this implementation of IAccessControl |
| 0x8001013c | 78.1 | Unable to open the access token of the server process |
| 0x8001013d | 78.1 | Unable to decode the ACL in the stream provided by the user |
| 0x8001013f | 78.1 | The COM IAccessControl object is not initialized |
| 0x80010140 | 78.1 | Call Cancellation is disabled |
| 0x8001ffff | 78.1 | An internal error occurred. |
| 0x80020001 | 78.1 | Unknown interface. |
| 0x80020003 | 78.1 | Member not found. |
| 0x80020004 | 78.1 | Parameter not found. |
| 0x80020005 | 78.1 | Type mismatch. |
| 0x80020006 | 78.1 | Unknown name. |
| 0x80020007 | 78.1 | No named arguments. |
| 0x80020008 | 78.1 | Bad variable type. |
| 0x80020009 | 78.1 | Exception occurred. |
| 0x8002000a | 78.1 | Out of present range. |
| 0x8002000b | 78.1 | Invalid index. |
| 0x8002000c | 78.1 | Unknown language. |
| 0x8002000d | 78.1 | Memory is locked. |
| 0x8002000e | 78.1 | Invalid number of parameters. |
| 0x8002000f | 78.1 | Parameter not optional. |
| 0x80020010 | 78.1 | Invalid callee. |
| 0x80020011 | 78.1 | Does not support a collection. |
| 0x80020012 | 78.1 | Division by zero. |
| 0x80020013 | 78.1 | Buffer too small |
| 0x80028016 | 78.1 | Buffer too small. |
| 0x80028017 | 78.1 | Field name not defined in the record. |
| 0x80028018 | 78.1 | Old format or invalid type library. |
| 0x80028019 | 78.1 | Old format or invalid type library. |
| 0x8002801c | 78.1 | Error accessing the OLE registry. |
| 0x8002801d | 78.1 | Library not registered. |
| 0x80028027 | 78.1 | Bound to unknown type. |
| 0x80028028 | 78.1 | Qualified name disallowed. |
| 0x80028029 | 78.1 | Invalid forward reference, or reference to uncompiled type. |
| 0x8002802a | 78.1 | Type mismatch. |
| 0x8002802b | 78.1 | Element not found. |
| 0x8002802c | 78.1 | Ambiguous name. |
| 0x8002802d | 78.1 | Name already exists in the library. |
| 0x8002802e | 78.1 | Unknown LCID. |
| 0x8002802f | 78.1 | Function not defined in specified DLL. |
| 0x800288bd | 78.1 | Wrong module kind for the operation. |
| 0x800288c5 | 78.1 | Size may not exceed 64K. |
| 0x800288c6 | 78.1 | Duplicate ID in inheritance hierarchy. |
| 0x800288cf | 78.1 | Incorrect inheritance depth in standard OLE hmember. |
| 0x80028ca0 | 78.1 | Type mismatch. |
| 0x80028ca1 | 78.1 | Invalid number of arguments. |
| 0x80028ca2 | 78.1 | I/O Error. |
| 0x80028ca3 | 78.1 | Error creating unique tmp file. |
| 0x80029c4a | 78.1 | Error loading type library/DLL. |
| 0x80029c83 | 78.1 | Inconsistent property functions. |
| 0x80029c84 | 78.1 | Circular dependency between types/modules. |
| 0x80030001 | 78.1 | Unable to perform requested operation. |
| 0x80030002 | 78.1 | %1 could not be found. |
| 0x80030003 | 78.1 | The path %1 could not be found. |
| 0x80030004 | 78.1 | There are insufficient resources to open another file. |
| 0x80030005 | 78.1 | Access Denied. |
| 0x80030006 | 78.1 | Attempted an operation on an invalid object. |
| 0x80030008 | 78.1 | There is insufficient memory available to complete operation. |
| 0x80030009 | 78.1 | Invalid pointer error. |
| 0x80030012 | 78.1 | There are no more entries to return. |
| 0x80030013 | 78.1 | Disk is write-protected. |
| 0x80030019 | 78.1 | An error occurred during a seek operation. |
| 0x8003001d | 78.1 | A disk error occurred during a write operation. |
| 0x8003001e | 78.1 | A disk error occurred during a read operation. |
| 0x80030020 | 78.1 | A share violation has occurred. |
| 0x80030021 | 78.1 | A lock violation has occurred. |
| 0x80030050 | 78.1 | %1 already exists. |
| 0x80030057 | 78.1 | Invalid parameter error. |
| 0x80030070 | 78.1 | There is insufficient disk space to complete operation. |
| 0x800300f0 | 78.1 | Illegal write of non-simple property to simple property set. |
| 0x800300fa | 78.1 | An API call exited abnormally. |
| 0x800300fb | 78.1 | The file %1 is not a valid compound file. |
| 0x800300fc | 78.1 | The name %1 is not valid. |
| 0x800300fd | 78.1 | An unexpected error occurred. |
| 0x800300fe | 78.1 | That function is not implemented. |
| 0x800300ff | 78.1 | Invalid flag error. |
| 0x80030100 | 78.1 | Attempted to use an object that is busy. |
| 0x80030101 | 78.1 | The storage has been changed since the last commit. |
| 0x80030102 | 78.1 | Attempted to use an object that has ceased to exist. |
| 0x80030103 | 78.1 | Can't save. |
| 0x80030104 | 78.1 | The compound file %1 was produced with an incompatible version of storage. |
| 0x80030105 | 78.1 | The compound file %1 was produced with a newer version of storage. |
| 0x80030106 | 78.1 | Share.exe or equivalent is required for operation. |
| 0x80030107 | 78.1 | Illegal operation called on non-file based storage. |
| 0x80030108 | 78.1 | Illegal operation called on object with extant marshallings. |
| 0x80030109 | 78.1 | The docfile has been corrupted. |
| 0x80030110 | 78.1 | OLE32.DLL has been loaded at the wrong address. |
| 0x80030111 | 78.1 | The compound file is too large for the current implementation |
| 0x80030112 | 78.1 | The compound file was not created with the STGM_SIMPLE flag |
| 0x80030201 | 78.1 | The file download was aborted abnormally. The file is incomplete. |
| 0x80030202 | 78.1 | The file download has been terminated. |
| 0x80030305 | 78.1 | Generic Copy Protection Error. |
| 0x80030306 | 78.1 | Copy Protection Error - DVD CSS Authentication failed. |
| 0x80030307 | 78.1 | Copy Protection Error - The given sector does not have a valid CSS key. |
| 0x80030308 | 78.1 | Copy Protection Error - DVD session key not established. |
| 0x80030309 | 78.1 | Copy Protection Error - The read failed because the sector is encrypted. |
| 0x8003030a | 78.1 | Copy Protection Error - The current DVD's region does not correspond to the region setting of the drive. |
| 0x8003030b | 78.1 | Copy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted. |
| 0x80040000 | 78.1 | Invalid OLEVERB structure |
| 0x80040001 | 78.1 | Invalid advise flags |
| 0x80040002 | 78.1 | Can't enumerate any more, because the associated data is missing |
| 0x80040003 | 78.1 | This implementation doesn't take advises |
| 0x80040004 | 78.1 | There is no connection for this connection ID |
| 0x80040005 | 78.1 | Need to run the object to perform this operation |
| 0x80040006 | 78.1 | There is no cache to operate on |
| 0x80040007 | 78.1 | Uninitialized object |
| 0x80040008 | 78.1 | Linked object's source class has changed |
| 0x80040009 | 78.1 | Not able to get the moniker of the object |
| 0x8004000a | 78.1 | Not able to bind to the source |
| 0x8004000b | 78.1 | Object is static; operation not allowed |
| 0x8004000c | 78.1 | User canceled out of save dialog |
| 0x8004000d | 78.1 | Invalid rectangle |
| 0x8004000e | 78.1 | compobj.dll is too old for the ole2.dll initialized |
| 0x8004000f | 78.1 | Invalid window handle |
| 0x80040010 | 78.1 | Object is not in any of the inplace active states |
| 0x80040011 | 78.1 | Not able to convert object |
| 0x80040012 | 78.1 | Not able to perform the operation because object is not given storage yet |
| 0x80040064 | 78.1 | Invalid FORMATETC structure |
| 0x80040065 | 78.1 | Invalid DVTARGETDEVICE structure |
| 0x80040066 | 78.1 | Invalid STDGMEDIUM structure |
| 0x80040067 | 78.1 | Invalid STATDATA structure |
| 0x80040068 | 78.1 | Invalid lindex |
| 0x80040069 | 78.1 | Invalid tymed |
| 0x8004006a | 78.1 | Invalid clipboard format |
| 0x8004006b | 78.1 | Invalid aspect(s) |
| 0x8004006c | 78.1 | tdSize parameter of the DVTARGETDEVICE structure is invalid |
| 0x8004006d | 78.1 | Object doesn't support IViewObject interface |
| 0x80040100 | 78.1 | Trying to revoke a drop target that has not been registered |
| 0x80040101 | 78.1 | This window has already been registered as a drop target |
| 0x80040102 | 78.1 | Invalid window handle |
| 0x80040110 | 78.1 | Class does not support aggregation (or class object is remote) |
| 0x80040111 | 78.1 | ClassFactory cannot supply requested class |
| 0x80040112 | 78.1 | Class is not licensed for use |
| 0x80040140 | 78.1 | Error drawing view |
| 0x80040150 | 78.1 | Could not read key from registry |
| 0x80040151 | 78.1 | Could not write key to registry |
| 0x80040152 | 78.1 | Could not find the key in the registry |
| 0x80040153 | 78.1 | Invalid value for registry |
| 0x80040154 | 78.1 | Class not registered |
| 0x80040155 | 78.1 | Interface not registered |
| 0x80040156 | 78.1 | Threading model entry is not valid |
| 0x80040160 | 78.1 | CATID does not exist |
| 0x80040161 | 78.1 | Description not found |
| 0x80040164 | 78.1 | No package in the software installation data in the Active Directory meets this criteria. |
| 0x80040165 | 78.1 | Deleting this will break the referential integrity of the software installation data in the Active Directory. |
| 0x80040166 | 78.1 | The CLSID was not found in the software installation data in the Active Directory. |
| 0x80040167 | 78.1 | The software installation data in the Active Directory is corrupt. |
| 0x80040168 | 78.1 | There is no software installation data in the Active Directory. |
| 0x80040169 | 78.1 | There is no software installation data object in the Active Directory. |
| 0x8004016a | 78.1 | The software installation data object in the Active Directory already exists. |
| 0x8004016b | 78.1 | The path to the software installation data in the Active Directory is not correct. |
| 0x8004016c | 78.1 | A network error interrupted the operation. |
| 0x8004016d | 78.1 | The size of this object exceeds the maximum size set by the Administrator. |
| 0x8004016e | 78.1 | The schema for the software installation data in the Active Directory does not match the required schema. |
| 0x8004016f | 78.1 | An error occurred in the software installation data in the Active Directory. |
| 0x80040170 | 78.1 | Cache not updated |
| 0x80040180 | 78.1 | No verbs for OLE object |
| 0x80040181 | 78.1 | Invalid verb for OLE object |
| 0x800401a0 | 78.1 | Undo is not available |
| 0x800401a1 | 78.1 | Space for tools is not available |
| 0x800401c0 | 78.1 | OLESTREAM Get method failed |
| 0x800401c1 | 78.1 | OLESTREAM Put method failed |
| 0x800401c2 | 78.1 | Contents of the OLESTREAM not in correct format |
| 0x800401c3 | 78.1 | There was an error in a Windows GDI call while converting the bitmap to a DIB |
| 0x800401c4 | 78.1 | Contents of the IStorage not in correct format |
| 0x800401c5 | 78.1 | Contents of IStorage is missing one of the standard streams |
| 0x800401c6 | 78.1 | There was an error in a Windows GDI call while converting the DIB to a bitmap. |
| 0x800401d0 | 78.1 | OpenClipboard Failed |
| 0x800401d1 | 78.1 | EmptyClipboard Failed |
| 0x800401d2 | 78.1 | SetClipboard Failed |
| 0x800401d3 | 78.1 | Data on clipboard is invalid |
| 0x800401d4 | 78.1 | CloseClipboard Failed |
| 0x800401e0 | 78.1 | Moniker needs to be connected manually |
| 0x800401e1 | 78.1 | Operation exceeded deadline |
| 0x800401e2 | 78.1 | Moniker needs to be generic |
| 0x800401e3 | 78.1 | Operation unavailable |
| 0x800401e4 | 78.1 | Invalid syntax |
| 0x800401e5 | 78.1 | No object for moniker |
| 0x800401e6 | 78.1 | Bad extension for file |
| 0x800401e7 | 78.1 | Intermediate operation failed |
| 0x800401e8 | 78.1 | Moniker is not bindable |
| 0x800401e9 | 78.1 | Moniker is not bound |
| 0x800401ea | 78.1 | Moniker cannot open file |
| 0x800401eb | 78.1 | User input required for operation to succeed |
| 0x800401ec | 78.1 | Moniker class has no inverse |
| 0x800401ed | 78.1 | Moniker does not refer to storage |
| 0x800401ee | 78.1 | No common prefix |
| 0x800401ef | 78.1 | Moniker could not be enumerated |
| 0x800401f0 | 78.1 | CoInitialize has not been called. |
| 0x800401f1 | 78.1 | CoInitialize has already been called. |
| 0x800401f2 | 78.1 | Class of object cannot be determined |
| 0x800401f3 | 78.1 | Invalid class string |
| 0x800401f4 | 78.1 | Invalid interface string |
| 0x800401f5 | 78.1 | Application not found |
| 0x800401f6 | 78.1 | Application cannot be run more than once |
| 0x800401f7 | 78.1 | Some error in application program |
| 0x800401f8 | 78.1 | DLL for class not found |
| 0x800401f9 | 78.1 | Error in the DLL |
| 0x800401fa | 78.1 | Wrong OS or OS version for application |
| 0x800401fb | 78.1 | Object is not registered |
| 0x800401fc | 78.1 | Object is already registered |
| 0x800401fd | 78.1 | Object is not connected to server |
| 0x800401fe | 78.1 | Application was launched but it didn't register a class factory |
| 0x800401ff | 78.1 | Object has been released |
| 0x80040201 | 78.1 | An event was unable to invoke any of the subscribers |
| 0x80040203 | 78.1 | A syntax error occurred trying to evaluate a query string |
| 0x80040204 | 78.1 | An invalid field name was used in a query string |
| 0x80040205 | 78.1 | An unexpected exception was raised |
| 0x80040206 | 78.1 | An unexpected internal error was detected |
| 0x80040207 | 78.1 | The owner SID on a per-user subscription doesn't exist |
| 0x80040208 | 78.1 | A user-supplied component or subscriber raised an exception |
| 0x80040209 | 78.1 | An interface has too many methods to fire events from |
| 0x8004020a | 78.1 | A subscription cannot be stored unless its event class already exists |
| 0x8004020b | 78.1 | Not all the objects requested could be removed |
| 0x8004020c | 78.1 | COM+ is required for this operation, but is not installed |
| 0x8004020d | 78.1 | Cannot modify or delete an object that was not added using the COM+ Admin SDK |
| 0x8004020e | 78.1 | Cannot modify or delete an object that was added using the COM+ Admin SDK |
| 0x8004020f | 78.1 | The event class for this subscription is in an invalid partition |
| 0x80040210 | 78.1 | The owner of the PerUser subscription is not logged on to the system specified |
| 0x80041309 | 78.1 | Trigger not found. |
| 0x8004130a | 78.1 | One or more of the properties that are needed to run this task have not been set. |
| 0x8004130b | 78.1 | There is no running instance of the task. |
| 0x8004130c | 78.1 | The Task Scheduler Service is not installed on this computer. |
| 0x8004130d | 78.1 | The task object could not be opened. |
| 0x8004130e | 78.1 | The object is either an invalid task object or is not a task object. |
| 0x8004130f | 78.1 | No account information could be found in the Task Scheduler security database for the task indicated. |
| 0x80041310 | 78.1 | Unable to establish existence of the account specified. |
| 0x80041311 | 78.1 | Corruption was detected in the Task Scheduler security database; the database has been reset. |
| 0x80041312 | 78.1 | Task Scheduler security services are available only on Windows NT. |
| 0x80041313 | 78.1 | The task object version is either unsupported or invalid. |
| 0x80041314 | 78.1 | The task has been configured with an unsupported combination of account settings and run time options. |
| 0x80041315 | 78.1 | The Task Scheduler Service is not running. |
| 0x80041316 | 78.1 | The task XML contains an unexpected node. |
| 0x80041317 | 78.1 | The task XML contains an element or attribute from an unexpected namespace. |
| 0x80041318 | 78.1 | The task XML contains a value which is incorrectly formatted or out of range. |
| 0x80041319 | 78.1 | The task XML is missing a required element or attribute. |
| 0x8004131a | 78.1 | The task XML is malformed. |
| 0x8004131d | 78.1 | The task XML contains too many nodes of the same type. |
| 0x8004131e | 78.1 | The task cannot be started after the trigger's end boundary. |
| 0x8004131f | 78.1 | An instance of this task is already running. |
| 0x80041320 | 78.1 | The task will not run because the user is not logged on. |
| 0x80041321 | 78.1 | The task image is corrupt or has been tampered with. |
| 0x80041322 | 78.1 | The Task Scheduler service is not available. |
| 0x80041323 | 78.1 | The Task Scheduler service is too busy to handle your request. Please try again later. |
| 0x80041324 | 78.1 | The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. |
| 0x80041326 | 78.1 | The task is disabled. |
| 0x80041327 | 78.1 | The task has properties that are not compatible with previous versions of Windows. |
| 0x80041328 | 78.1 | The task settings do not allow the task to start on demand. |
| 0x8004d000 | 78.1 | Another single phase resource manager has already been enlisted in this transaction. |
| 0x8004d001 | 78.1 | A retaining commit or abort is not supported |
| 0x8004d002 | 78.1 | The transaction failed to commit for an unknown reason. The transaction was aborted. |
| 0x8004d003 | 78.1 | Cannot call commit on this transaction object because the calling application did not initiate the transaction. |
| 0x8004d004 | 78.1 | Instead of committing, the resource heuristically aborted. |
| 0x8004d005 | 78.1 | Instead of aborting, the resource heuristically committed. |
| 0x8004d006 | 78.1 | Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions. |
| 0x8004d007 | 78.1 | Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions. |
| 0x8004d008 | 78.1 | The requested isolation level is not valid or supported. |
| 0x8004d009 | 78.1 | The transaction manager doesn't support an asynchronous operation for this method. |
| 0x8004d00a | 78.1 | Unable to enlist in the transaction. |
| 0x8004d00b | 78.1 | 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. |
| 0x8004d00c | 78.1 | There is no resource presently associated with this enlistment |
| 0x8004d00d | 78.1 | The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers. |
| 0x8004d00e | 78.1 | The transaction has already been implicitly or explicitly committed or aborted |
| 0x8004d00f | 78.1 | An invalid combination of flags was specified |
| 0x8004d010 | 78.1 | The resource manager id is not associated with this transaction or the transaction manager. |
| 0x8004d011 | 78.1 | This method was called in the wrong state |
| 0x8004d012 | 78.1 | The indicated unit of work does not match the unit of work expected by the resource manager. |
| 0x8004d013 | 78.1 | An enlistment in a transaction already exists. |
| 0x8004d014 | 78.1 | An import object for the transaction could not be found. |
| 0x8004d015 | 78.1 | The transaction cookie is invalid. |
| 0x8004d016 | 78.1 | The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed |
| 0x8004d017 | 78.1 | A time-out was specified, but time-outs are not supported. |
| 0x8004d018 | 78.1 | The requested operation is already in progress for the transaction. |
| 0x8004d019 | 78.1 | The transaction has already been aborted. |
| 0x8004d01a | 78.1 | The Transaction Manager returned a log full error. |
| 0x8004d01b | 78.1 | The Transaction Manager is not available. |
| 0x8004d01c | 78.1 | A connection with the transaction manager was lost. |
| 0x8004d01d | 78.1 | A request to establish a connection with the transaction manager was denied. |
| 0x8004d01e | 78.1 | Resource manager reenlistment to determine transaction status timed out. |
| 0x8004d01f | 78.1 | This transaction manager failed to establish a connection with another TIP transaction manager. |
| 0x8004d020 | 78.1 | This transaction manager encountered a protocol error with another TIP transaction manager. |
| 0x8004d021 | 78.1 | This transaction manager could not propagate a transaction from another TIP transaction manager. |
| 0x8004d022 | 78.1 | The Transaction Manager on the destination machine is not available. |
| 0x8004d023 | 78.1 | The Transaction Manager has disabled its support for TIP. |
| 0x8004d024 | 78.1 | The transaction manager has disabled its support for remote/network transactions. |
| 0x8004d025 | 78.1 | The partner transaction manager has disabled its support for remote/network transactions. |
| 0x8004d026 | 78.1 | The transaction manager has disabled its support for XA transactions. |
| 0x8004d027 | 78.1 | MSDTC was unable to read its configuration information. |
| 0x8004d028 | 78.1 | MSDTC was unable to load the dtc proxy dll. |
| 0x8004d029 | 78.1 | The local transaction has aborted. |
| 0x8004d02a | 78.1 | 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. |
| 0x8004d02b | 78.1 | 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. |
| 0x8004d02c | 78.1 | The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions. |
| 0x8004d080 | 78.1 | XACT_E_CLERKNOTFOUND |
| 0x8004d081 | 78.1 | XACT_E_CLERKEXISTS |
| 0x8004d082 | 78.1 | XACT_E_RECOVERYINPROGRESS |
| 0x8004d083 | 78.1 | XACT_E_TRANSACTIONCLOSED |
| 0x8004d084 | 78.1 | XACT_E_INVALIDLSN |
| 0x8004d085 | 78.1 | XACT_E_REPLAYREQUEST |
| 0x8004d100 | 78.1 | The request to connect to the specified transaction coordinator was denied. |
| 0x8004d101 | 78.1 | The maximum number of enlistments for the specified transaction has been reached. |
| 0x8004d102 | 78.1 | A resource manager with the same identifier is already registered with the specified transaction coordinator. |
| 0x8004d103 | 78.1 | The prepare request given was not eligible for single phase optimizations. |
| 0x8004d104 | 78.1 | RecoveryComplete has already been called for the given resource manager. |
| 0x8004d105 | 78.1 | The interface call made was incorrect for the current state of the protocol. |
| 0x8004d106 | 78.1 | xa_open call failed for the XA resource. |
| 0x8004d107 | 78.1 | xa_recover call failed for the XA resource. |
| 0x8004d108 | 78.1 | The Logical Unit of Work specified cannot be found. |
| 0x8004d109 | 78.1 | The specified Logical Unit of Work already exists. |
| 0x8004d10a | 78.1 | Subordinate creation failed. The specified Logical Unit of Work was not connected. |
| 0x8004d10b | 78.1 | A transaction with the given identifier already exists. |
| 0x8004d10c | 78.1 | The resource is in use. |
| 0x8004d10d | 78.1 | The LU Recovery process is down. |
| 0x8004d10e | 78.1 | The remote session was lost. |
| 0x8004d10f | 78.1 | The resource is currently recovering. |
| 0x8004d110 | 78.1 | There was a mismatch in driving recovery. |
| 0x8004d111 | 78.1 | An error occurred with the XA resource. |
| 0x8004e002 | 78.1 | The root transaction wanted to commit, but transaction aborted |
| 0x8004e003 | 78.1 | You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. |
| 0x8004e004 | 78.1 | There is no MTS object context |
| 0x8004e005 | 78.1 | The component is configured to use synchronization and this method call would cause a deadlock to occur. |
| 0x8004e006 | 78.1 | The component is configured to use synchronization and a thread has timed out waiting to enter the context. |
| 0x8004e007 | 78.1 | You made a method call on a COM+ component that has a transaction that has already committed or aborted. |
| 0x8004e00c | 78.1 | The specified role was not configured for the application |
| 0x8004e00f | 78.1 | COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator |
| 0x8004e021 | 78.1 | An unexpected error occurred during COM+ Activation. |
| 0x8004e022 | 78.1 | COM+ Activation failed. Check the event log for more information |
| 0x8004e023 | 78.1 | COM+ Activation failed due to a catalog or configuration error. |
| 0x8004e024 | 78.1 | COM+ activation failed because the activation could not be completed in the specified amount of time. |
| 0x8004e025 | 78.1 | COM+ Activation failed because an initialization function failed. Check the event log for more information. |
| 0x8004e026 | 78.1 | The requested operation requires that JIT be in the current context and it is not |
| 0x8004e027 | 78.1 | The requested operation requires that the current context have a Transaction, and it does not |
| 0x8004e028 | 78.1 | The components threading model has changed after install into a COM+ Application. Please re-install component. |
| 0x8004e029 | 78.1 | IIS intrinsics not available. Start your work with IIS. |
| 0x8004e02a | 78.1 | An attempt to write a cookie failed. |
| 0x8004e02b | 78.1 | An attempt to use a database generated a database specific error. |
| 0x8004e02c | 78.1 | The COM+ component you created must use object pooling to work. |
| 0x8004e02d | 78.1 | The COM+ component you created must use object construction to work correctly. |
| 0x8004e02e | 78.1 | The COM+ component requires synchronization, and it is not configured for it. |
| 0x8004e02f | 78.1 | 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. |
| 0x8004e030 | 78.1 | 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. |
| 0x8004e031 | 78.1 | The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning. |
| 0x80070005 | 78.1 | General access denied error |
| 0x80070006 | 78.1 | Invalid handle |
| 0x8007000e | 78.1 | Ran out of memory |
| 0x80070057 | 78.1 | One or more arguments are invalid |
| 0x80080001 | 78.1 | Attempt to create a class object failed |
| 0x80080002 | 78.1 | OLE service could not bind object |
| 0x80080003 | 78.1 | RPC communication failed with OLE service |
| 0x80080004 | 78.1 | Bad path to object |
| 0x80080005 | 78.1 | Server execution failed |
| 0x80080006 | 78.1 | OLE service could not communicate with the object server |
| 0x80080007 | 78.1 | Moniker path could not be normalized |
| 0x80080008 | 78.1 | Object server is stopping when OLE service contacts it |
| 0x80080009 | 78.1 | An invalid root block pointer was specified |
| 0x80080010 | 78.1 | An allocation chain contained an invalid link pointer |
| 0x80080011 | 78.1 | The requested allocation size was too large |
| 0x80080015 | 78.1 | The activation requires a display name to be present under the CLSID key. |
| 0x80080016 | 78.1 | The activation requires that the RunAs value for the application is Activate As Activator. |
| 0x80080017 | 78.1 | The class is not configured to support Elevated activation. |
| 0x80090001 | 78.1 | Bad UID. |
| 0x80090002 | 78.1 | Bad Hash. |
| 0x80090003 | 78.1 | Bad Key. |
| 0x80090004 | 78.1 | Bad Length. |
| 0x80090005 | 78.1 | Bad Data. |
| 0x80090006 | 78.1 | Invalid Signature. |
| 0x80090007 | 78.1 | Bad Version of provider. |
| 0x80090008 | 78.1 | Invalid algorithm specified. |
| 0x80090009 | 78.1 | Invalid flags specified. |
| 0x8009000a | 78.1 | Invalid type specified. |
| 0x8009000b | 78.1 | Key not valid for use in specified state. |
| 0x8009000c | 78.1 | Hash not valid for use in specified state. |
| 0x8009000d | 78.1 | Key does not exist. |
| 0x8009000e | 78.1 | Insufficient memory available for the operation. |
| 0x8009000f | 78.1 | Object already exists. |
| 0x80090010 | 78.1 | Access denied. |
| 0x80090011 | 78.1 | Object was not found. |
| 0x80090012 | 78.1 | Data already encrypted. |
| 0x80090013 | 78.1 | Invalid provider specified. |
| 0x80090014 | 78.1 | Invalid provider type specified. |
| 0x80090015 | 78.1 | Provider's public key is invalid. |
| 0x80090016 | 78.1 | Keyset does not exist |
| 0x80090017 | 78.1 | Provider type not defined. |
| 0x80090018 | 78.1 | Provider type as registered is invalid. |
| 0x80090019 | 78.1 | The keyset is not defined. |
| 0x8009001a | 78.1 | Keyset as registered is invalid. |
| 0x8009001b | 78.1 | Provider type does not match registered value. |
| 0x8009001c | 78.1 | The digital signature file is corrupt. |
| 0x8009001d | 78.1 | Provider DLL failed to initialize correctly. |
| 0x8009001e | 78.1 | Provider DLL could not be found. |
| 0x8009001f | 78.1 | The Keyset parameter is invalid. |
| 0x80090020 | 78.1 | An internal error occurred. |
| 0x80090021 | 78.1 | A base error occurred. |
| 0x80090022 | 78.1 | Provider could not perform the action since the context was acquired as silent. |
| 0x80090023 | 78.1 | The security token does not have storage space available for an additional container. |
| 0x80090024 | 78.1 | The profile for the user is a temporary profile. |
| 0x80090025 | 78.1 | The key parameters could not be set because the CSP uses fixed parameters. |
| 0x80090026 | 78.1 | The supplied handle is invalid. |
| 0x80090027 | 78.1 | The parameter is incorrect. |
| 0x80090028 | 78.1 | The buffer supplied to a function was too small. |
| 0x80090029 | 78.1 | The requested operation is not supported. |
| 0x8009002a | 78.1 | No more data is available. |
| 0x8009002b | 78.1 | The supplied buffers overlap incorrectly. |
| 0x8009002c | 78.1 | The specified data could not be decrypted. |
| 0x8009002d | 78.1 | An internal consistency check failed. |
| 0x8009002e | 78.1 | This operation requires input from the user. |
| 0x8009002f | 78.1 | The cryptographic provider does not support HMAC. |
| 0x80090300 | 78.1 | Not enough memory is available to complete this request |
| 0x80090301 | 78.1 | The handle specified is invalid |
| 0x80090302 | 78.1 | The function requested is not supported |
| 0x80090303 | 78.1 | The specified target is unknown or unreachable |
| 0x80090304 | 78.1 | The Local Security Authority cannot be contacted |
| 0x80090305 | 78.1 | The requested security package does not exist |
| 0x80090306 | 78.1 | The caller is not the owner of the desired credentials |
| 0x80090307 | 78.1 | The security package failed to initialize, and cannot be installed |
| 0x80090308 | 78.1 | The token supplied to the function is invalid |
| 0x80090309 | 78.1 | The security package is not able to marshall the logon buffer, so the logon attempt has failed |
| 0x8009030a | 78.1 | The per-message Quality of Protection is not supported by the security package |
| 0x8009030b | 78.1 | The security context does not allow impersonation of the client |
| 0x8009030c | 78.1 | The logon attempt failed |
| 0x8009030d | 78.1 | The credentials supplied to the package were not recognized |
| 0x8009030e | 78.1 | No credentials are available in the security package |
| 0x8009030f | 78.1 | The message or signature supplied for verification has been altered |
| 0x80090310 | 78.1 | The message supplied for verification is out of sequence |
| 0x80090311 | 78.1 | No authority could be contacted for authentication. |
| 0x80090316 | 78.1 | The requested security package does not exist |
| 0x80090317 | 78.1 | The context has expired and can no longer be used. |
| 0x80090318 | 78.1 | The supplied message is incomplete. The signature was not verified. |
| 0x80090320 | 78.1 | The credentials supplied were not complete, and could not be verified. The context could not be initialized. |
| 0x80090321 | 78.1 | The buffers supplied to a function was too small. |
| 0x80090322 | 78.1 | The target principal name is incorrect. |
| 0x80090324 | 78.1 | The clocks on the client and server machines are skewed. |
| 0x80090325 | 78.1 | The certificate chain was issued by an authority that is not trusted. |
| 0x80090326 | 78.1 | The message received was unexpected or badly formatted. |
| 0x80090327 | 78.1 | An unknown error occurred while processing the certificate. |
| 0x80090328 | 78.1 | The received certificate has expired. |
| 0x80090329 | 78.1 | The specified data could not be encrypted. |
| 0x80090330 | 78.1 | The specified data could not be decrypted. |
| 0x80090331 | 78.1 | The client and server cannot communicate, because they do not possess a common algorithm. |
| 0x80090332 | 78.1 | The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation). |
| 0x80090333 | 78.1 | A security context was deleted before the context was completed. This is considered a logon failure. |
| 0x80090334 | 78.1 | The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
| 0x80090335 | 78.1 | Unable to accomplish the requested task because the local machine does not have any IP addresses. |
| 0x80090336 | 78.1 | The supplied credential handle does not match the credential associated with the security context. |
| 0x80090337 | 78.1 | The crypto system or checksum function is invalid because a required function is unavailable. |
| 0x80090338 | 78.1 | The number of maximum ticket referrals has been exceeded. |
| 0x80090339 | 78.1 | The local machine must be a Kerberos KDC (domain controller) and it is not. |
| 0x8009033a | 78.1 | The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
| 0x8009033b | 78.1 | The KDC reply contained more than one principal name. |
| 0x8009033c | 78.1 | Expected to find PA data for a hint of what etype to use, but it was not found. |
| 0x8009033d | 78.1 | The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator. |
| 0x8009033e | 78.1 | Smartcard logon is required and was not used. |
| 0x8009033f | 78.1 | A system shutdown is in progress. |
| 0x80090340 | 78.1 | An invalid request was sent to the KDC. |
| 0x80090341 | 78.1 | The KDC was unable to generate a referral for the service requested. |
| 0x80090342 | 78.1 | The encryption type requested is not supported by the KDC. |
| 0x80090343 | 78.1 | An unsupported preauthentication mechanism was presented to the Kerberos package. |
| 0x80090345 | 78.1 | The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. |
| 0x80090346 | 78.1 | Client's supplied SSPI channel bindings were incorrect. |
| 0x80090347 | 78.1 | The received certificate was mapped to multiple accounts. |
| 0x80090348 | 78.1 | SEC_E_NO_KERB_KEY |
| 0x80090349 | 78.1 | The certificate is not valid for the requested usage. |
| 0x80090350 | 7 | The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you. |
| 0x80090351 | 78.1 | The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
| 0x80090352 | 7 | An untrusted certificate authority was detected While processing the smartcard certificate used for authentication. Please contact your system administrator. |
| 0x80090353 | 78.1 | The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator. |
| 0x80090354 | 78.1 | The smartcard certificate used for authentication was not trusted. Please contact your system administrator. |
| 0x80090355 | 78.1 | The smartcard certificate used for authentication has expired. Please contact your system administrator. |
| 0x80090356 | 78.1 | 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. |
| 0x80090357 | 78.1 | 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. |
| 0x80090358 | 78.1 | 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. |
| 0x80090359 | 78.1 | 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. |
| 0x8009035a | 78.1 | The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log. |
| 0x8009035b | 78.1 | The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log. |
| 0x8009035d | 78.1 | One or more of the parameters passed to the function was invalid. |
| 0x8009035e | 78.1 | Client policy does not allow credential delegation to target server. |
| 0x8009035f | 78.1 | Client policy does not allow credential delegation to target server with NLTM only authentication. |
| 0x80090361 | 78.1 | The required security context does not exist. |
| 0x80090362 | 78.1 | The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
| 0x80090363 | 78.1 | The identity of the server computer could not be verified. |
| 0x80091001 | 78.1 | An error occurred while performing an operation on a cryptographic message. |
| 0x80091002 | 78.1 | Unknown cryptographic algorithm. |
| 0x80091003 | 78.1 | The object identifier is poorly formatted. |
| 0x80091004 | 78.1 | Invalid cryptographic message type. |
| 0x80091005 | 78.1 | Unexpected cryptographic message encoding. |
| 0x80091006 | 78.1 | The cryptographic message does not contain an expected authenticated attribute. |
| 0x80091007 | 78.1 | The hash value is not correct. |
| 0x80091008 | 78.1 | The index value is not valid. |
| 0x80091009 | 78.1 | The content of the cryptographic message has already been decrypted. |
| 0x8009100a | 78.1 | The content of the cryptographic message has not been decrypted yet. |
| 0x8009100b | 78.1 | The enveloped-data message does not contain the specified recipient. |
| 0x8009100c | 78.1 | Invalid control type. |
| 0x8009100d | 78.1 | Invalid issuer and/or serial number. |
| 0x8009100e | 78.1 | Cannot find the original signer. |
| 0x8009100f | 78.1 | The cryptographic message does not contain all of the requested attributes. |
| 0x80091010 | 78.1 | The streamed cryptographic message is not ready to return data. |
| 0x80091011 | 78.1 | The streamed cryptographic message requires more data to complete the decode operation. |
| 0x80092001 | 78.1 | The length specified for the output data was insufficient. |
| 0x80092002 | 78.1 | An error occurred during encode or decode operation. |
| 0x80092003 | 78.1 | An error occurred while reading or writing to a file. |
| 0x80092004 | 78.1 | Cannot find object or property. |
| 0x80092005 | 78.1 | The object or property already exists. |
| 0x80092006 | 78.1 | No provider was specified for the store or object. |
| 0x80092007 | 78.1 | The specified certificate is self signed. |
| 0x80092008 | 78.1 | The previous certificate or CRL context was deleted. |
| 0x80092009 | 78.1 | Cannot find the requested object. |
| 0x8009200a | 78.1 | The certificate does not have a property that references a private key. |
| 0x8009200b | 78.1 | Cannot find the certificate and private key for decryption. |
| 0x8009200c | 78.1 | Cannot find the certificate and private key to use for decryption. |
| 0x8009200d | 78.1 | Not a cryptographic message or the cryptographic message is not formatted correctly. |
| 0x8009200e | 78.1 | The signed cryptographic message does not have a signer for the specified signer index. |
| 0x8009200f | 78.1 | Final closure is pending until additional frees or closes. |
| 0x80092010 | 78.1 | The certificate is revoked. |
| 0x80092011 | 78.1 | No Dll or exported function was found to verify revocation. |
| 0x80092012 | 78.1 | The revocation function was unable to check revocation for the certificate. |
| 0x80092013 | 78.1 | The revocation function was unable to check revocation because the revocation server was offline. |
| 0x80092014 | 78.1 | The certificate is not in the revocation server's database. |
| 0x80092020 | 78.1 | The string contains a non-numeric character. |
| 0x80092021 | 78.1 | The string contains a non-printable character. |
| 0x80092022 | 78.1 | The string contains a character not in the 7 bit ASCII character set. |
| 0x80092023 | 78.1 | The string contains an invalid X500 name attribute key, oid, value or delimiter. |
| 0x80092024 | 7 | 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_TDN_OCTED_STRING. |
| 0x80092025 | 78.1 | 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. |
| 0x80092026 | 78.1 | The cryptographic operation failed due to a local security option setting. |
| 0x80092027 | 78.1 | No DLL or exported function was found to verify subject usage. |
| 0x80092028 | 78.1 | The called function was unable to do a usage check on the subject. |
| 0x80092029 | 78.1 | Since the server was offline, the called function was unable to complete the usage check. |
| 0x8009202a | 78.1 | The subject was not found in a Certificate Trust List (CTL). |
| 0x8009202b | 78.1 | None of the signers of the cryptographic message or certificate trust list is trusted. |
| 0x8009202c | 78.1 | The public key's algorithm parameters are missing. |
| 0x80093000 | 78.1 | 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. |
| 0x80093001 | 78.1 | OSS ASN.1 Error: Output Buffer is too small. |
| 0x80093002 | 78.1 | OSS ASN.1 Error: Signed integer is encoded as a unsigned integer. |
| 0x80093003 | 78.1 | OSS ASN.1 Error: Unknown ASN.1 data type. |
| 0x80093004 | 78.1 | OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated. |
| 0x80093005 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093006 | 78.1 | OSS ASN.1 Error: Invalid argument. |
| 0x80093007 | 78.1 | OSS ASN.1 Error: Encode/Decode version mismatch. |
| 0x80093008 | 78.1 | OSS ASN.1 Error: Out of memory. |
| 0x80093009 | 78.1 | OSS ASN.1 Error: Encode/Decode Error. |
| 0x8009300a | 78.1 | OSS ASN.1 Error: Internal Error. |
| 0x8009300b | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x8009300c | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x8009300d | 78.1 | OSS ASN.1 Error: Unsupported BER indefinite-length encoding. |
| 0x8009300e | 78.1 | OSS ASN.1 Error: Access violation. |
| 0x8009300f | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093010 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093011 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093012 | 78.1 | OSS ASN.1 Error: Internal Error. |
| 0x80093013 | 78.1 | OSS ASN.1 Error: Multi-threading conflict. |
| 0x80093014 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093015 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093016 | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x80093017 | 78.1 | OSS ASN.1 Error: Encode/Decode function not implemented. |
| 0x80093018 | 78.1 | OSS ASN.1 Error: Trace file error. |
| 0x80093019 | 78.1 | OSS ASN.1 Error: Function not implemented. |
| 0x8009301a | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x8009301b | 78.1 | OSS ASN.1 Error: Trace file error. |
| 0x8009301c | 78.1 | OSS ASN.1 Error: Trace file error. |
| 0x8009301d | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x8009301e | 78.1 | OSS ASN.1 Error: Invalid data. |
| 0x8009301f | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093020 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093021 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093022 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093023 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093024 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093025 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093026 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093027 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093028 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x80093029 | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x8009302a | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x8009302b | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x8009302c | 78.1 | OSS ASN.1 Error: Program link error. |
| 0x8009302d | 78.1 | OSS ASN.1 Error: System resource error. |
| 0x8009302e | 78.1 | OSS ASN.1 Error: Trace file error. |
| 0x80093100 | 78.1 | ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR. |
| 0x80093101 | 78.1 | ASN1 internal encode or decode error. |
| 0x80093102 | 78.1 | ASN1 unexpected end of data. |
| 0x80093103 | 78.1 | ASN1 corrupted data. |
| 0x80093104 | 78.1 | ASN1 value too large. |
| 0x80093105 | 78.1 | ASN1 constraint violated. |
| 0x80093106 | 78.1 | ASN1 out of memory. |
| 0x80093107 | 78.1 | ASN1 buffer overflow. |
| 0x80093108 | 78.1 | ASN1 function not supported for this PDU. |
| 0x80093109 | 78.1 | ASN1 bad arguments to function call. |
| 0x8009310a | 78.1 | ASN1 bad real value. |
| 0x8009310b | 78.1 | ASN1 bad tag value met. |
| 0x8009310c | 78.1 | ASN1 bad choice value. |
| 0x8009310d | 78.1 | ASN1 bad encoding rule. |
| 0x8009310e | 78.1 | ASN1 bad unicode (UTF8). |
| 0x80093133 | 78.1 | ASN1 bad PDU type. |
| 0x80093134 | 78.1 | ASN1 not yet implemented. |
| 0x80093201 | 78.1 | ASN1 skipped unknown extension(s). |
| 0x80093202 | 78.1 | ASN1 end of data expected |
| 0x80094001 | 78.1 | The request subject name is invalid or too long. |
| 0x80094002 | 78.1 | The request does not exist. |
| 0x80094003 | 78.1 | The request's current status does not allow this operation. |
| 0x80094004 | 78.1 | The requested property value is empty. |
| 0x80094005 | 78.1 | The certification authority's certificate contains invalid data. |
| 0x80094006 | 78.1 | Certificate service has been suspended for a database restore operation. |
| 0x80094007 | 78.1 | The certificate contains an encoded length that is potentially incompatible with older enrollment software. |
| 0x80094008 | 78.1 | The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation. |
| 0x80094009 | 78.1 | The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester. |
| 0x8009400a | 78.1 | Cannot archive private key. The certification authority is not configured for key archival. |
| 0x8009400b | 78.1 | Cannot archive private key. The certification authority could not verify one or more key recovery certificates. |
| 0x8009400c | 78.1 | The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature. |
| 0x8009400d | 78.1 | At least one security principal must have the permission to manage this CA. |
| 0x8009400e | 78.1 | The request contains an invalid renewal certificate attribute. |
| 0x8009400f | 78.1 | 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. |
| 0x80094010 | 78.1 | A memory reference caused a data alignment fault. |
| 0x80094011 | 78.1 | The permissions on this certification authority do not allow the current user to enroll for certificates. |
| 0x80094012 | 78.1 | The permissions on the certificate template do not allow the current user to enroll for this type of certificate. |
| 0x80094013 | 78.1 | The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access. |
| 0x80094014 | 78.1 | The request was denied by a certificate manager or CA administrator. |
| 0x80094015 | 78.1 | An enrollment policy server cannot be located. |
| 0x80094800 | 78.1 | The requested certificate template is not supported by this CA. |
| 0x80094801 | 78.1 | The request contains no certificate template information. |
| 0x80094802 | 78.1 | The request contains conflicting template information. |
| 0x80094803 | 78.1 | The request is missing a required Subject Alternate name extension. |
| 0x80094804 | 78.1 | The request is missing a required private key for archival by the server. |
| 0x80094805 | 78.1 | The request is missing a required SMIME capabilities extension. |
| 0x80094806 | 78.1 | 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. |
| 0x80094807 | 78.1 | The request template version is newer than the supported template version. |
| 0x80094808 | 78.1 | The template is missing a required signature policy attribute. |
| 0x80094809 | 78.1 | The request is missing required signature policy information. |
| 0x8009480a | 78.1 | The request is missing one or more required signatures. |
| 0x8009480b | 78.1 | One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures. |
| 0x8009480c | 78.1 | The request is missing one or more required signature issuance policies. |
| 0x8009480d | 78.1 | The UPN is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480e | 78.1 | The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480f | 78.1 | The DNS name is unavailable and cannot be added to the Subject Alternate name. |
| 0x80094810 | 78.1 | The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template. |
| 0x80094811 | 78.1 | The public key does not meet the minimum size required by the specified certificate template. |
| 0x80094812 | 78.1 | The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name. |
| 0x80094813 | 78.1 | One or more certificate templates to be enabled on this certification authority could not be found. |
| 0x80094814 | 78.1 | The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed. |
| 0x80094815 | 78.1 | The certificate template requires too many RA signatures. Only one RA signature is allowed. |
| 0x80095000 | 78.1 | The key is not exportable. |
| 0x80095001 | 78.1 | You cannot add the root CA certificate into your local store. |
| 0x80095002 | 78.1 | The key archival hash attribute was not found in the response. |
| 0x80095003 | 78.1 | An unexpected key archival hash attribute was found in the response. |
| 0x80095004 | 78.1 | There is a key archival hash mismatch between the request and the response. |
| 0x80095005 | 78.1 | Signing certificate cannot include SMIME extension. |
| 0x80096001 | 78.1 | A system-level error occurred while verifying trust. |
| 0x80096002 | 78.1 | The certificate for the signer of the message is invalid or not found. |
| 0x80096003 | 78.1 | One of the counter signatures was invalid. |
| 0x80096004 | 78.1 | The signature of the certificate cannot be verified. |
| 0x80096005 | 78.1 | The timestamp signature and/or certificate could not be verified or is malformed. |
| 0x80096010 | 78.1 | The digital signature of the object did not verify. |
| 0x80096019 | 78.1 | A certificate's basic constraint extension has not been observed. |
| 0x8009601e | 78.1 | The certificate does not meet or contain the Authenticode(tm) financial extensions. |
| 0x80097001 | 78.1 | Tried to reference a part of the file outside the proper range. |
| 0x80097002 | 78.1 | Could not retrieve an object from the file. |
| 0x80097003 | 78.1 | Could not find the head table in the file. |
| 0x80097004 | 78.1 | The magic number in the head table is incorrect. |
| 0x80097005 | 78.1 | The offset table has incorrect values. |
| 0x80097006 | 78.1 | Duplicate table tags or tags out of alphabetical order. |
| 0x80097007 | 78.1 | A table does not start on a long word boundary. |
| 0x80097008 | 78.1 | First table does not appear after header information. |
| 0x80097009 | 78.1 | Two or more tables overlap. |
| 0x8009700a | 78.1 | Too many pad bytes between tables or pad bytes are not 0. |
| 0x8009700b | 78.1 | File is too small to contain the last table. |
| 0x8009700c | 78.1 | A table checksum is incorrect. |
| 0x8009700d | 78.1 | The file checksum is incorrect. |
| 0x80097010 | 78.1 | The signature does not have the correct attributes for the policy. |
| 0x80097011 | 78.1 | The file did not pass the hints check. |
| 0x80097012 | 78.1 | The file is not an OpenType file. |
| 0x80097013 | 78.1 | Failed on a file operation (open, map, read, write). |
| 0x80097014 | 78.1 | A call to a CryptoAPI function failed. |
| 0x80097015 | 78.1 | There is a bad version number in the file. |
| 0x80097016 | 78.1 | The structure of the DSIG table is incorrect. |
| 0x80097017 | 78.1 | A check failed in a partially constant table. |
| 0x80097018 | 78.1 | Some kind of structural error. |
| 0x80097019 | 78.1 | The requested credential requires confirmation. |
| 0x800b0001 | 78.1 | Unknown trust provider. |
| 0x800b0002 | 78.1 | The trust verification action specified is not supported by the specified trust provider. |
| 0x800b0003 | 78.1 | The form specified for the subject is not one supported or known by the specified trust provider. |
| 0x800b0004 | 78.1 | The subject is not trusted for the specified action. |
| 0x800b0005 | 78.1 | Error due to problem in ASN.1 encoding process. |
| 0x800b0006 | 78.1 | Error due to problem in ASN.1 decoding process. |
| 0x800b0007 | 7 | Reading / writing Extensions where Attributes are appropriate, and visa versa. |
| 0x800b0008 | 78.1 | Unspecified cryptographic failure. |
| 0x800b0009 | 78.1 | The size of the data could not be determined. |
| 0x800b000a | 78.1 | The size of the indefinite-sized data could not be determined. |
| 0x800b000b | 78.1 | This object does not read and write self-sizing data. |
| 0x800b0100 | 78.1 | No signature was present in the subject. |
| 0x800b0101 | 78.1 | A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. |
| 0x800b0102 | 78.1 | The validity periods of the certification chain do not nest correctly. |
| 0x800b0103 | 7 | A certificate that can only be used as an end-entity is being used as a CA or visa versa. |
| 0x800b0104 | 78.1 | A path length constraint in the certification chain has been violated. |
| 0x800b0105 | 78.1 | A certificate contains an unknown extension that is marked 'critical'. |
| 0x800b0106 | 78.1 | A certificate being used for a purpose other than the ones specified by its CA. |
| 0x800b0107 | 78.1 | A parent of a given certificate in fact did not issue that child certificate. |
| 0x800b0108 | 78.1 | A certificate is missing or has an empty value for an important field, such as a subject or issuer name. |
| 0x800b0109 | 78.1 | A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. |
| 0x800b010a | 78.1 | A certificate chain could not be built to a trusted root authority. |
| 0x800b010b | 78.1 | Generic trust failure. |
| 0x800b010c | 78.1 | A certificate was explicitly revoked by its issuer. |
| 0x800b010d | 78.1 | The certification path terminates with the test root which is not trusted with the current policy settings. |
| 0x800b010e | 78.1 | The revocation process could not continue - the certificate(s) could not be checked. |
| 0x800b010f | 78.1 | The certificate's CN name does not match the passed value. |
| 0x800b0110 | 78.1 | The certificate is not valid for the requested usage. |
| 0x800b0111 | 78.1 | The certificate was explicitly marked as untrusted by the user. |
| 0x800b0112 | 78.1 | A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider. |
| 0x800b0113 | 78.1 | The certificate has invalid policy. |
| 0x800b0114 | 78.1 | The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded. |
| 0x800f0000 | 78.1 | A non-empty line was encountered in the INF before the start of a section. |
| 0x800f0001 | 78.1 | A section name marker in the INF is not complete, or does not exist on a line by itself. |
| 0x800f0002 | 78.1 | An INF section was encountered whose name exceeds the maximum section name length. |
| 0x800f0003 | 78.1 | The syntax of the INF is invalid. |
| 0x800f0100 | 78.1 | The style of the INF is different than what was requested. |
| 0x800f0101 | 78.1 | The required section was not found in the INF. |
| 0x800f0102 | 78.1 | The required line was not found in the INF. |
| 0x800f0103 | 78.1 | The files affected by the installation of this file queue have not been backed up for uninstall. |
| 0x800f0200 | 78.1 | The INF or the device information set or element does not have an associated install class. |
| 0x800f0201 | 78.1 | The INF or the device information set or element does not match the specified install class. |
| 0x800f0202 | 78.1 | An existing device was found that is a duplicate of the device being manually installed. |
| 0x800f0203 | 78.1 | There is no driver selected for the device information set or element. |
| 0x800f0204 | 78.1 | The requested device registry key does not exist. |
| 0x800f0205 | 78.1 | The device instance name is invalid. |
| 0x800f0206 | 78.1 | The install class is not present or is invalid. |
| 0x800f0207 | 78.1 | The device instance cannot be created because it already exists. |
| 0x800f0208 | 78.1 | The operation cannot be performed on a device information element that has not been registered. |
| 0x800f0209 | 78.1 | The device property code is invalid. |
| 0x800f020a | 78.1 | The INF from which a driver list is to be built does not exist. |
| 0x800f020b | 78.1 | The device instance does not exist in the hardware tree. |
| 0x800f020c | 78.1 | The icon representing this install class cannot be loaded. |
| 0x800f020d | 78.1 | The class installer registry entry is invalid. |
| 0x800f020e | 78.1 | The class installer has indicated that the default action should be performed for this installation request. |
| 0x800f020f | 78.1 | The operation does not require any files to be copied. |
| 0x800f0210 | 78.1 | The specified hardware profile does not exist. |
| 0x800f0211 | 78.1 | There is no device information element currently selected for this device information set. |
| 0x800f0212 | 78.1 | The operation cannot be performed because the device information set is locked. |
| 0x800f0213 | 78.1 | The operation cannot be performed because the device information element is locked. |
| 0x800f0214 | 78.1 | The specified path does not contain any applicable device INFs. |
| 0x800f0215 | 78.1 | No class installer parameters have been set for the device information set or element. |
| 0x800f0216 | 78.1 | The operation cannot be performed because the file queue is locked. |
| 0x800f0217 | 78.1 | A service installation section in this INF is invalid. |
| 0x800f0218 | 78.1 | There is no class driver list for the device information element. |
| 0x800f0219 | 78.1 | The installation failed because a function driver was not specified for this device instance. |
| 0x800f021a | 78.1 | There is presently no default device interface designated for this interface class. |
| 0x800f021b | 78.1 | The operation cannot be performed because the device interface is currently active. |
| 0x800f021c | 78.1 | The operation cannot be performed because the device interface has been removed from the system. |
| 0x800f021d | 78.1 | An interface installation section in this INF is invalid. |
| 0x800f021e | 78.1 | This interface class does not exist in the system. |
| 0x800f021f | 78.1 | The reference string supplied for this interface device is invalid. |
| 0x800f0220 | 78.1 | The specified machine name does not conform to UNC naming conventions. |
| 0x800f0221 | 78.1 | A general remote communication error occurred. |
| 0x800f0222 | 78.1 | The machine selected for remote communication is not available at this time. |
| 0x800f0223 | 78.1 | The Plug and Play service is not available on the remote machine. |
| 0x800f0224 | 78.1 | The property page provider registry entry is invalid. |
| 0x800f0225 | 78.1 | The requested device interface is not present in the system. |
| 0x800f0226 | 78.1 | The device's co-installer has additional work to perform after installation is complete. |
| 0x800f0227 | 78.1 | The device's co-installer is invalid. |
| 0x800f0228 | 78.1 | There are no compatible drivers for this device. |
| 0x800f0229 | 78.1 | There is no icon that represents this device or device type. |
| 0x800f022a | 78.1 | A logical configuration specified in this INF is invalid. |
| 0x800f022b | 78.1 | The class installer has denied the request to install or upgrade this device. |
| 0x800f022c | 78.1 | One of the filter drivers installed for this device is invalid. |
| 0x800f022d | 78.1 | The driver selected for this device does not support this version of Windows. |
| 0x800f022e | 78.1 | The driver selected for this device does not support Windows. |
| 0x800f022f | 78.1 | The third-party INF does not contain digital signature information. |
| 0x800f0230 | 78.1 | An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms. |
| 0x800f0231 | 78.1 | The device cannot be disabled. |
| 0x800f0232 | 78.1 | The device could not be dynamically removed. |
| 0x800f0233 | 78.1 | Cannot copy to specified target. |
| 0x800f0234 | 78.1 | Driver is not intended for this platform. |
| 0x800f0235 | 78.1 | Operation not allowed in WOW64. |
| 0x800f0236 | 78.1 | The operation involving unsigned file copying was rolled back, so that a system restore point could be set. |
| 0x800f0237 | 78.1 | An INF was copied into the Windows INF directory in an improper manner. |
| 0x800f0238 | 78.1 | The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product. |
| 0x800f0239 | 78.1 | An unknown exception was encountered. |
| 0x800f023a | 78.1 | A problem was encountered when accessing the Plug and Play registry database. |
| 0x800f023b | 78.1 | The requested operation is not supported for a remote machine. |
| 0x800f023c | 78.1 | The specified file is not an installed OEM INF. |
| 0x800f023d | 78.1 | One or more devices are presently installed using the specified INF. |
| 0x800f023e | 78.1 | The requested device install operation is obsolete. |
| 0x800f023f | 78.1 | A file could not be verified because it does not have an associated catalog signed via Authenticode(tm). |
| 0x800f0240 | 78.1 | Authenticode(tm) signature verification is not supported for the specified INF. |
| 0x800f0241 | 78.1 | The INF was signed with an Authenticode(tm) catalog from a trusted publisher. |
| 0x800f0242 | 78.1 | The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. |
| 0x800f0243 | 78.1 | The publisher of an Authenticode(tm) signed catalog was not established as trusted. |
| 0x800f0244 | 78.1 | The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version. |
| 0x800f0245 | 78.1 | The file may only be validated by a catalog signed via Authenticode(tm). |
| 0x800f0246 | 78.1 | One of the installers for this device cannot perform the installation at this time. |
| 0x800f0247 | 78.1 | A problem was encountered while attempting to add the driver to the store. |
| 0x800f0248 | 78.1 | The installation of this device is forbidden by system policy. Contact your system administrator. |
| 0x800f0249 | 78.1 | The installation of this driver is forbidden by system policy. Contact your system administrator. |
| 0x800f024a | 78.1 | The specified INF is the wrong type for this operation. |
| 0x800f024b | 78.1 | The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. |
| 0x800f024c | 78.1 | A problem was encountered while attempting to delete the driver from the store. |
| 0x800f0300 | 78.1 | An unrecoverable stack overflow was encountered. |
| 0x800f1000 | 78.1 | No installed components were detected. |
| 0x80100001 | 78.1 | An internal consistency check failed. |
| 0x80100002 | 78.1 | The action was cancelled by an SCardCancel request. |
| 0x80100003 | 78.1 | The supplied handle was invalid. |
| 0x80100004 | 78.1 | One or more of the supplied parameters could not be properly interpreted. |
| 0x80100005 | 78.1 | Registry startup information is missing or invalid. |
| 0x80100006 | 78.1 | Not enough memory available to complete this command. |
| 0x80100007 | 78.1 | An internal consistency timer has expired. |
| 0x80100008 | 78.1 | The data buffer to receive returned data is too small for the returned data. |
| 0x80100009 | 78.1 | The specified reader name is not recognized. |
| 0x8010000a | 78.1 | The user-specified timeout value has expired. |
| 0x8010000b | 78.1 | The smart card cannot be accessed because of other connections outstanding. |
| 0x8010000c | 7 | The operation requires a Smart Card, but no Smart Card is currently in the device. |
| 0x8010000d | 78.1 | The specified smart card name is not recognized. |
| 0x8010000e | 78.1 | The system could not dispose of the media in the requested manner. |
| 0x8010000f | 78.1 | The requested protocols are incompatible with the protocol currently in use with the smart card. |
| 0x80100010 | 78.1 | The reader or smart card is not ready to accept commands. |
| 0x80100011 | 78.1 | One or more of the supplied parameters values could not be properly interpreted. |
| 0x80100012 | 78.1 | The action was cancelled by the system, presumably to log off or shut down. |
| 0x80100013 | 78.1 | An internal communications error has been detected. |
| 0x80100014 | 78.1 | An internal error has been detected, but the source is unknown. |
| 0x80100015 | 78.1 | An ATR obtained from the registry is not a valid ATR string. |
| 0x80100016 | 78.1 | An attempt was made to end a non-existent transaction. |
| 0x80100017 | 78.1 | The specified reader is not currently available for use. |
| 0x80100018 | 78.1 | The operation has been aborted to allow the server application to exit. |
| 0x80100019 | 78.1 | The PCI Receive buffer was too small. |
| 0x8010001a | 78.1 | The reader driver does not meet minimal requirements for support. |
| 0x8010001b | 78.1 | The reader driver did not produce a unique reader name. |
| 0x8010001c | 78.1 | The smart card does not meet minimal requirements for support. |
| 0x8010001d | 7 | The Smart card resource manager is not running. |
| 0x8010001e | 7 | The Smart card resource manager has shut down. |
| 0x8010001f | 78.1 | An unexpected card error has occurred. |
| 0x80100020 | 78.1 | No Primary Provider can be found for the smart card. |
| 0x80100021 | 78.1 | The requested order of object creation is not supported. |
| 0x80100022 | 78.1 | This smart card does not support the requested feature. |
| 0x80100023 | 78.1 | The identified directory does not exist in the smart card. |
| 0x80100024 | 78.1 | The identified file does not exist in the smart card. |
| 0x80100025 | 78.1 | The supplied path does not represent a smart card directory. |
| 0x80100026 | 78.1 | The supplied path does not represent a smart card file. |
| 0x80100027 | 78.1 | Access is denied to this file. |
| 0x80100028 | 7 | The smartcard does not have enough memory to store the information. |
| 0x80100029 | 78.1 | There was an error trying to set the smart card file object pointer. |
| 0x8010002a | 78.1 | The supplied PIN is incorrect. |
| 0x8010002b | 78.1 | An unrecognized error code was returned from a layered component. |
| 0x8010002c | 78.1 | The requested certificate does not exist. |
| 0x8010002d | 78.1 | The requested certificate could not be obtained. |
| 0x8010002e | 78.1 | Cannot find a smart card reader. |
| 0x8010002f | 78.1 | A communications error with the smart card has been detected. Retry the operation. |
| 0x80100030 | 78.1 | The requested key container does not exist on the smart card. |
| 0x80100031 | 7 | The Smart card resource manager is too busy to complete this operation. |
| 0x80100032 | 78.1 | The smart card PIN cache has expired. |
| 0x80100033 | 78.1 | The smart card PIN cannot be cached. |
| 0x80100034 | 78.1 | The smart card is read only and cannot be written to. |
| 0x80100065 | 78.1 | The reader cannot communicate with the smart card, due to ATR configuration conflicts. |
| 0x80100066 | 78.1 | The smart card is not responding to a reset. |
| 0x80100067 | 78.1 | Power has been removed from the smart card, so that further communication is not possible. |
| 0x80100068 | 78.1 | The smart card has been reset, so any shared state information is invalid. |
| 0x80100069 | 78.1 | The smart card has been removed, so that further communication is not possible. |
| 0x8010006a | 78.1 | Access was denied because of a security violation. |
| 0x8010006b | 78.1 | The card cannot be accessed because the wrong PIN was presented. |
| 0x8010006c | 78.1 | The card cannot be accessed because the maximum number of PIN entry attempts has been reached. |
| 0x8010006d | 78.1 | The end of the smart card file has been reached. |
| 0x8010006e | 78.1 | The action was cancelled by the user. |
| 0x8010006f | 78.1 | No PIN was presented to the smart card. |
| 0x80100070 | 78.1 | The requested item could not be found in the cache. |
| 0x80100071 | 78.1 | The requested cache item is too old and was deleted from the cache. |
| 0x80100072 | 78.1 | The new cache item exceeds the maximum per-item size defined for the cache. |
| 0x80110401 | 78.1 | Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail |
| 0x80110402 | 78.1 | One or more of the object's properties are missing or invalid |
| 0x80110403 | 78.1 | The object was not found in the catalog |
| 0x80110404 | 78.1 | The object is already registered |
| 0x80110407 | 78.1 | Error occurred writing to the application file |
| 0x80110408 | 78.1 | Error occurred reading the application file |
| 0x80110409 | 78.1 | Invalid version number in application file |
| 0x8011040a | 78.1 | The file path is invalid |
| 0x8011040b | 78.1 | The application is already installed |
| 0x8011040c | 78.1 | The role already exists |
| 0x8011040d | 78.1 | An error occurred copying the file |
| 0x8011040f | 78.1 | One or more users are not valid |
| 0x80110410 | 78.1 | One or more users in the application file are not valid |
| 0x80110411 | 78.1 | The component's CLSID is missing or corrupt |
| 0x80110412 | 78.1 | The component's progID is missing or corrupt |
| 0x80110413 | 78.1 | Unable to set required authentication level for update request |
| 0x80110414 | 78.1 | The identity or password set on the application is not valid |
| 0x80110418 | 78.1 | Application file CLSIDs or IIDs do not match corresponding DLLs |
| 0x80110419 | 78.1 | Interface information is either missing or changed |
| 0x8011041a | 78.1 | DllRegisterServer failed on component install |
| 0x8011041b | 78.1 | No server file share available |
| 0x8011041d | 78.1 | DLL could not be loaded |
| 0x8011041e | 78.1 | The registered TypeLib ID is not valid |
| 0x8011041f | 78.1 | Application install directory not found |
| 0x80110423 | 78.1 | Errors occurred while in the component registrar |
| 0x80110424 | 78.1 | The file does not exist |
| 0x80110425 | 78.1 | The DLL could not be loaded |
| 0x80110426 | 78.1 | GetClassObject failed in the DLL |
| 0x80110427 | 78.1 | The DLL does not support the components listed in the TypeLib |
| 0x80110428 | 78.1 | The TypeLib could not be loaded |
| 0x80110429 | 78.1 | The file does not contain components or component information |
| 0x8011042a | 78.1 | Changes to this object and its sub-objects have been disabled |
| 0x8011042b | 78.1 | The delete function has been disabled for this object |
| 0x8011042c | 78.1 | The server catalog version is not supported |
| 0x8011042d | 78.1 | The component move was disallowed, because the source or destination application is either a system application or currently locked against changes |
| 0x8011042e | 78.1 | The component move failed because the destination application no longer exists |
| 0x80110430 | 78.1 | The system was unable to register the TypeLib |
| 0x80110433 | 78.1 | This operation cannot be performed on the system application |
| 0x80110434 | 78.1 | The component registrar referenced in this file is not available |
| 0x80110435 | 78.1 | A component in the same DLL is already installed |
| 0x80110436 | 78.1 | The service is not installed |
| 0x80110437 | 78.1 | One or more property settings are either invalid or in conflict with each other |
| 0x80110438 | 78.1 | The object you are attempting to add or rename already exists |
| 0x80110439 | 78.1 | The component already exists |
| 0x8011043b | 78.1 | The registration file is corrupt |
| 0x8011043c | 78.1 | The property value is too large |
| 0x8011043e | 78.1 | Object was not found in registry |
| 0x8011043f | 78.1 | This object is not poolable |
| 0x80110446 | 78.1 | A CLSID with the same GUID as the new application ID is already installed on this machine |
| 0x80110447 | 78.1 | A role assigned to a component, interface, or method did not exist in the application |
| 0x80110448 | 78.1 | You must have components in an application in order to start the application |
| 0x80110449 | 78.1 | This operation is not enabled on this platform |
| 0x8011044a | 78.1 | Application Proxy is not exportable |
| 0x8011044b | 78.1 | Failed to start application because it is either a library application or an application proxy |
| 0x8011044c | 78.1 | System application is not exportable |
| 0x8011044d | 78.1 | Cannot subscribe to this component (the component may have been imported) |
| 0x8011044e | 78.1 | An event class cannot also be a subscriber component |
| 0x8011044f | 78.1 | Library applications and application proxies are incompatible |
| 0x80110450 | 78.1 | This function is valid for the base partition only |
| 0x80110451 | 78.1 | You cannot start an application that has been disabled |
| 0x80110457 | 78.1 | The specified partition name is already in use on this computer |
| 0x80110458 | 78.1 | The specified partition name is invalid. Check that the name contains at least one visible character |
| 0x80110459 | 78.1 | The partition cannot be deleted because it is the default partition for one or more users |
| 0x8011045a | 78.1 | The partition cannot be exported, because one or more components in the partition have the same file name |
| 0x8011045b | 78.1 | Applications that contain one or more imported components cannot be installed into a non-base partition |
| 0x8011045c | 78.1 | The application name is not unique and cannot be resolved to an application id |
| 0x8011045d | 78.1 | The partition name is not unique and cannot be resolved to a partition id |
| 0x80110472 | 78.1 | The COM+ registry database has not been initialized |
| 0x80110473 | 78.1 | The COM+ registry database is not open |
| 0x80110474 | 78.1 | The COM+ registry database detected a system error |
| 0x80110475 | 78.1 | The COM+ registry database is already running |
| 0x80110480 | 78.1 | This version of the COM+ registry database cannot be migrated |
| 0x80110481 | 78.1 | The schema version to be migrated could not be found in the COM+ registry database |
| 0x80110482 | 78.1 | There was a type mismatch between binaries |
| 0x80110483 | 78.1 | A binary of unknown or invalid type was provided |
| 0x80110484 | 78.1 | There was a type mismatch between a binary and an application |
| 0x80110485 | 78.1 | The application cannot be paused or resumed |
| 0x80110486 | 78.1 | The COM+ Catalog Server threw an exception during execution |
| 0x80110600 | 78.1 | Only COM+ Applications marked "queued" can be invoked using the "queue" moniker |
| 0x80110601 | 78.1 | At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker |
| 0x80110602 | 78.1 | MSMQ is required for the requested operation and is not installed |
| 0x80110603 | 78.1 | Unable to marshal an interface that does not support IPersistStream |
| 0x80110604 | 78.1 | The message is improperly formatted or was damaged in transit |
| 0x80110605 | 78.1 | An unauthenticated message was received by an application that accepts only authenticated messages |
| 0x80110606 | 78.1 | The message was requeued or moved by a user not in the "QC Trusted User" role |
| 0x80110701 | 78.1 | Cannot create a duplicate resource of type Distributed Transaction Coordinator |
| 0x80110808 | 78.1 | One of the objects being inserted or updated does not belong to a valid parent collection |
| 0x80110809 | 78.1 | One of the specified objects cannot be found |
| 0x8011080a | 78.1 | The specified application is not currently running |
| 0x8011080b | 78.1 | The partition(s) specified are not valid. |
| 0x8011080d | 78.1 | COM+ applications that run as NT service may not be pooled or recycled |
| 0x8011080e | 78.1 | One or more users are already assigned to a local partition set. |
| 0x8011080f | 78.1 | Library applications may not be recycled. |
| 0x80110811 | 78.1 | Applications running as NT services may not be recycled. |
| 0x80110812 | 78.1 | The process has already been recycled. |
| 0x80110813 | 78.1 | A paused process may not be recycled. |
| 0x80110814 | 78.1 | Library applications may not be NT services. |
| 0x80110815 | 78.1 | The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID. |
| 0x80110816 | 78.1 | The partition specified as default is not a member of the partition set. |
| 0x80110817 | 78.1 | A recycled process may not be paused. |
| 0x80110818 | 78.1 | Access to the specified partition is denied. |
| 0x80110819 | 78.1 | Only Application Files (*.MSI files) can be installed into partitions. |
| 0x8011081a | 78.1 | Applications containing one or more legacy components may not be exported to 1.0 format. |
| 0x8011081b | 78.1 | Legacy components may not exist in non-base partitions. |
| 0x8011081c | 78.1 | A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application |
| 0x8011081d | 78.1 | A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application |
| 0x8011081e | 78.1 | A private component cannot be moved (or copied) to a library application or to the base partition |
| 0x8011081f | 78.1 | The Base Application Partition exists in all partition sets and cannot be removed. |
| 0x80110820 | 78.1 | Alas, Event Class components cannot be aliased. |
| 0x80110821 | 78.1 | Access is denied because the component is private. |
| 0x80110822 | 78.1 | The specified SAFER level is invalid. |
| 0x80110823 | 78.1 | The specified user cannot write to the system registry |
| 0x80110824 | 78.1 | COM+ partitions are currently disabled. |
| 0x801f0001 | 78.1 | A handler was not defined by the filter for this operation. |
| 0x801f0002 | 78.1 | A context is already defined for this object. |
| 0x801f0003 | 78.1 | Asynchronous requests are not valid for this operation. |
| 0x801f0004 | 78.1 | Disallow the Fast IO path for this operation. |
| 0x801f0005 | 78.1 | An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0x801f0006 | 78.1 | Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0x801f0007 | 78.1 | The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0x801f0008 | 78.1 | The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0x801f0009 | 78.1 | 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. |
| 0x801f000a | 78.1 | 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. |
| 0x801f000b | 78.1 | The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0x801f000c | 78.1 | Non-paged pool must be used for this type of context. |
| 0x801f000d | 78.1 | A duplicate handler definition has been provided for an operation. |
| 0x801f000e | 78.1 | The callback data queue has been disabled. |
| 0x801f000f | 78.1 | Do not attach the filter to the volume at this time. |
| 0x801f0010 | 78.1 | Do not detach the filter from the volume at this time. |
| 0x801f0011 | 78.1 | An instance already exists at this altitude on the volume specified. |
| 0x801f0012 | 78.1 | An instance already exists with this name on the volume specified. |
| 0x801f0013 | 78.1 | The system could not find the filter specified. |
| 0x801f0014 | 78.1 | The system could not find the volume specified. |
| 0x801f0015 | 78.1 | The system could not find the instance specified. |
| 0x801f0016 | 78.1 | No registered context allocation definition was found for the given request. |
| 0x801f0017 | 78.1 | An invalid parameter was specified during context registration. |
| 0x801f0018 | 78.1 | The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0x801f0019 | 78.1 | The requested device object does not exist for the given volume. |
| 0x801f001a | 78.1 | The specified volume is already mounted. |
| 0x801f001b | 78.1 | The specified Transaction Context is already enlisted in a transaction |
| 0x801f001c | 78.1 | The specifiec context is already attached to another object |
| 0x801f0020 | 78.1 | No waiter is present for the filter's reply to this message. |
| 0x80260001 | 78.1 | {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. |
| 0x80263001 | 78.1 | {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. |
| 0x80263002 | 78.1 | {Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session. |
| 0x80263003 | 78.1 | {No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present. |
| 0x80263004 | 78.1 | {DWM is not queuing presents for the specified window} The window specified is not currently using queued presents. |
| 0x80263005 | 78.1 | {The adapter specified by the LUID is not found} DWM can not find the adapter specified by the LUID. |
| 0x80280000 | 78.1 | This is an error mask to convert TPM hardware errors to win errors. |
| 0x80280001 | 78.1 | Authentication failed. |
| 0x80280002 | 78.1 | The index to a PCR, DIR or other register is incorrect. |
| 0x80280003 | 78.1 | One or more parameter is bad. |
| 0x80280004 | 78.1 | An operation completed successfully but the auditing of that operation failed. |
| 0x80280005 | 78.1 | The clear disable flag is set and all clear operations now require physical access. |
| 0x80280006 | 78.1 | Activate the Trusted Platform Module (TPM). |
| 0x80280007 | 78.1 | Enable the Trusted Platform Module (TPM). |
| 0x80280008 | 78.1 | The target command has been disabled. |
| 0x80280009 | 78.1 | The operation failed. |
| 0x8028000a | 78.1 | The ordinal was unknown or inconsistent. |
| 0x8028000b | 78.1 | The ability to install an owner is disabled. |
| 0x8028000c | 78.1 | The key handle cannot be interpreted. |
| 0x8028000d | 78.1 | The key handle points to an invalid key. |
| 0x8028000e | 78.1 | Unacceptable encryption scheme. |
| 0x8028000f | 78.1 | Migration authorization failed. |
| 0x80280010 | 78.1 | PCR information could not be interpreted. |
| 0x80280011 | 78.1 | No room to load key. |
| 0x80280012 | 78.1 | There is no Storage Root Key (SRK) set. |
| 0x80280013 | 78.1 | An encrypted blob is invalid or was not created by this TPM. |
| 0x80280014 | 78.1 | The Trusted Platform Module (TPM) already has an owner. |
| 0x80280015 | 78.1 | The TPM has insufficient internal resources to perform the requested action. |
| 0x80280016 | 78.1 | A random string was too short. |
| 0x80280017 | 78.1 | The TPM does not have the space to perform the operation. |
| 0x80280018 | 78.1 | The named PCR value does not match the current PCR value. |
| 0x80280019 | 78.1 | The paramSize argument to the command has the incorrect value . |
| 0x8028001a | 78.1 | There is no existing SHA-1 thread. |
| 0x8028001b | 78.1 | The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
| 0x8028001c | 7 | The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, you might need to replace your TPM hardware or motherboard. |
| 0x8028001d | 78.1 | The authorization for the second key in a 2 key function failed authorization. |
| 0x8028001e | 78.1 | The tag value sent to for a command is invalid. |
| 0x8028001f | 78.1 | An IO error occurred transmitting information to the TPM. |
| 0x80280020 | 78.1 | The encryption process had a problem. |
| 0x80280021 | 78.1 | The decryption process did not complete. |
| 0x80280022 | 78.1 | An invalid handle was used. |
| 0x80280023 | 78.1 | The TPM does not have an Endorsement Key (EK) installed. |
| 0x80280024 | 78.1 | The usage of a key is not allowed. |
| 0x80280025 | 78.1 | The submitted entity type is not allowed. |
| 0x80280026 | 78.1 | The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. |
| 0x80280027 | 78.1 | Signed data cannot include additional DER information. |
| 0x80280028 | 78.1 | The key properties in TPM_KEY_PARMs are not supported by this TPM. |
| 0x80280029 | 78.1 | The migration properties of this key are incorrect. |
| 0x8028002a | 78.1 | The signature or encryption scheme for this key is incorrect or not permitted in this situation. |
| 0x8028002b | 78.1 | The size of the data (or blob) parameter is bad or inconsistent with the referenced key. |
| 0x8028002c | 78.1 | A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob. |
| 0x8028002d | 78.1 | Either the physicalPresence or physicalPresenceLock bits have the wrong value. |
| 0x8028002e | 78.1 | The TPM cannot perform this version of the capability. |
| 0x8028002f | 78.1 | The TPM does not allow for wrapped transport sessions. |
| 0x80280030 | 78.1 | TPM audit construction failed and the underlying command was returning a failure code also. |
| 0x80280031 | 78.1 | TPM audit construction failed and the underlying command was returning success. |
| 0x80280032 | 78.1 | Attempt to reset a PCR register that does not have the resettable attribute. |
| 0x80280033 | 78.1 | Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. |
| 0x80280034 | 78.1 | Make identity blob not properly typed. |
| 0x80280035 | 78.1 | When saving context identified resource type does not match actual resource. |
| 0x80280036 | 78.1 | The TPM is attempting to execute a command only available when in FIPS mode. |
| 0x80280037 | 78.1 | The command is attempting to use an invalid family ID. |
| 0x80280038 | 78.1 | The permission to manipulate the NV storage is not available. |
| 0x80280039 | 78.1 | The operation requires a signed command. |
| 0x8028003a | 78.1 | Wrong operation to load an NV key. |
| 0x8028003b | 78.1 | NV_LoadKey blob requires both owner and blob authorization. |
| 0x8028003c | 78.1 | The NV area is locked and not writtable. |
| 0x8028003d | 78.1 | The locality is incorrect for the attempted operation. |
| 0x8028003e | 78.1 | The NV area is read only and can't be written to. |
| 0x8028003f | 78.1 | There is no protection on the write to the NV area. |
| 0x80280040 | 78.1 | The family count value does not match. |
| 0x80280041 | 78.1 | The NV area has already been written to. |
| 0x80280042 | 78.1 | The NV area attributes conflict. |
| 0x80280043 | 78.1 | The structure tag and version are invalid or inconsistent. |
| 0x80280044 | 78.1 | The key is under control of the TPM Owner and can only be evicted by the TPM Owner. |
| 0x80280045 | 78.1 | The counter handle is incorrect. |
| 0x80280046 | 78.1 | The write is not a complete write of the area. |
| 0x80280047 | 78.1 | The gap between saved context counts is too large. |
| 0x80280048 | 78.1 | The maximum number of NV writes without an owner has been exceeded. |
| 0x80280049 | 78.1 | No operator AuthData value is set. |
| 0x8028004a | 78.1 | The resource pointed to by context is not loaded. |
| 0x8028004b | 78.1 | The delegate administration is locked. |
| 0x8028004c | 78.1 | Attempt to manage a family other then the delegated family. |
| 0x8028004d | 78.1 | Delegation table management not enabled. |
| 0x8028004e | 78.1 | There was a command executed outside of an exclusive transport session. |
| 0x8028004f | 78.1 | Attempt to context save a owner evict controlled key. |
| 0x80280050 | 78.1 | The DAA command has no resources availble to execute the command. |
| 0x80280051 | 78.1 | The consistency check on DAA parameter inputData0 has failed. |
| 0x80280052 | 78.1 | The consistency check on DAA parameter inputData1 has failed. |
| 0x80280053 | 78.1 | The consistency check on DAA_issuerSettings has failed. |
| 0x80280054 | 78.1 | The consistency check on DAA_tpmSpecific has failed. |
| 0x80280055 | 78.1 | The atomic process indicated by the submitted DAA command is not the expected process. |
| 0x80280056 | 78.1 | The issuer's validity check has detected an inconsistency. |
| 0x80280057 | 78.1 | The consistency check on w has failed. |
| 0x80280058 | 78.1 | The handle is incorrect. |
| 0x80280059 | 78.1 | Delegation is not correct. |
| 0x8028005a | 78.1 | The context blob is invalid. |
| 0x8028005b | 78.1 | Too many contexts held by the TPM. |
| 0x8028005c | 78.1 | Migration authority signature validation failure. |
| 0x8028005d | 78.1 | Migration destination not authenticated. |
| 0x8028005e | 78.1 | Migration source incorrect. |
| 0x8028005f | 78.1 | Incorrect migration authority. |
| 0x80280061 | 78.1 | Attempt to revoke the EK and the EK is not revocable. |
| 0x80280062 | 78.1 | Bad signature of CMK ticket. |
| 0x80280063 | 78.1 | There is no room in the context list for additional contexts. |
| 0x80280400 | 78.1 | The command was blocked. |
| 0x80280401 | 78.1 | The specified handle was not found. |
| 0x80280402 | 78.1 | The TPM returned a duplicate handle and the command needs to be resubmitted. |
| 0x80280403 | 78.1 | The command within the transport was blocked. |
| 0x80280404 | 78.1 | The command within the transport is not supported. |
| 0x80280800 | 78.1 | The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. |
| 0x80280801 | 78.1 | SelfTestFull has not been run. |
| 0x80280802 | 78.1 | The TPM is currently executing a full selftest. |
| 0x80280803 | 78.1 | The TPM is defending against dictionary attacks and is in a time-out period. |
| 0x80284001 | 7 | An internal software error has been detected. |
| 0x80284002 | 78.1 | One or more input parameters is bad. |
| 0x80284003 | 78.1 | A specified output pointer is bad. |
| 0x80284004 | 78.1 | The specified context handle does not refer to a valid context. |
| 0x80284005 | 78.1 | A specified output buffer is too small. |
| 0x80284006 | 78.1 | An error occurred while communicating with the TPM. |
| 0x80284007 | 78.1 | One or more context parameters is invalid. |
| 0x80284008 | 78.1 | The TBS service is not running and could not be started. |
| 0x80284009 | 78.1 | A new context could not be created because there are too many open contexts. |
| 0x8028400a | 78.1 | A new virtual resource could not be created because there are too many open virtual resources. |
| 0x8028400b | 78.1 | The TBS service has been started but is not yet running. |
| 0x8028400c | 78.1 | The physical presence interface is not supported. |
| 0x8028400d | 78.1 | The command was canceled. |
| 0x8028400e | 78.1 | The input or output buffer is too large. |
| 0x8028400f | 78.1 | A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer. |
| 0x80284010 | 78.1 | The TBS service has been disabled. |
| 0x80284011 | 78.1 | No TCG event log is available. |
| 0x80290100 | 78.1 | The command buffer is not in the correct state. |
| 0x80290101 | 78.1 | The command buffer does not contain enough data to satisfy the request. |
| 0x80290102 | 78.1 | The command buffer cannot contain any more data. |
| 0x80290103 | 78.1 | One or more output parameters was NULL or invalid. |
| 0x80290104 | 78.1 | One or more input parameters is invalid. |
| 0x80290105 | 78.1 | Not enough memory was available to satisfy the request. |
| 0x80290106 | 78.1 | The specified buffer was too small. |
| 0x80290107 | 78.1 | An internal error was detected. |
| 0x80290108 | 78.1 | The caller does not have the appropriate rights to perform the requested operation. |
| 0x80290109 | 78.1 | The specified authorization information was invalid. |
| 0x8029010a | 78.1 | The specified context handle was not valid. |
| 0x8029010b | 78.1 | An error occurred while communicating with the TBS. |
| 0x8029010c | 78.1 | The TPM returned an unexpected result. |
| 0x8029010d | 78.1 | The message was too large for the encoding scheme. |
| 0x8029010e | 78.1 | The encoding in the blob was not recognized. |
| 0x8029010f | 78.1 | The key size is not valid. |
| 0x80290110 | 78.1 | The encryption operation failed. |
| 0x80290111 | 78.1 | The key parameters structure was not valid |
| 0x80290112 | 78.1 | The requested supplied data does not appear to be a valid migration authorization blob. |
| 0x80290113 | 78.1 | The specified PCR index was invalid |
| 0x80290114 | 78.1 | The data given does not appear to be a valid delegate blob. |
| 0x80290115 | 78.1 | One or more of the specified context parameters was not valid. |
| 0x80290116 | 78.1 | The data given does not appear to be a valid key blob |
| 0x80290117 | 78.1 | The specified PCR data was invalid. |
| 0x80290118 | 78.1 | The format of the owner auth data was invalid. |
| 0x80290119 | 78.1 | The random number generated did not pass FIPS RNG check. |
| 0x8029011a | 78.1 | The TCG Event Log does not contain any data. |
| 0x8029011b | 78.1 | An entry in the TCG Event Log was invalid. |
| 0x8029011c | 78.1 | A TCG Separator was not found. |
| 0x8029011d | 78.1 | A digest value in a TCG Log entry did not match hashed data. |
| 0x80290200 | 78.1 | The specified buffer was too small. |
| 0x80290201 | 78.1 | The context could not be cleaned up. |
| 0x80290202 | 78.1 | The specified context handle is invalid. |
| 0x80290203 | 78.1 | An invalid context parameter was specified. |
| 0x80290204 | 78.1 | An error occurred while communicating with the TPM |
| 0x80290205 | 78.1 | No entry with the specified key was found. |
| 0x80290206 | 78.1 | The specified virtual handle matches a virtual handle already in use. |
| 0x80290207 | 78.1 | The pointer to the returned handle location was NULL or invalid |
| 0x80290208 | 78.1 | One or more parameters is invalid |
| 0x80290209 | 78.1 | The RPC subsystem could not be initialized. |
| 0x8029020a | 78.1 | The TBS scheduler is not running. |
| 0x8029020b | 78.1 | The command was canceled. |
| 0x8029020c | 78.1 | There was not enough memory to fulfill the request |
| 0x8029020d | 78.1 | The specified list is empty, or the iteration has reached the end of the list. |
| 0x8029020e | 78.1 | The specified item was not found in the list. |
| 0x8029020f | 78.1 | The TPM does not have enough space to load the requested resource. |
| 0x80290210 | 78.1 | There are too many TPM contexts in use. |
| 0x80290211 | 78.1 | The TPM command failed. |
| 0x80290212 | 78.1 | The TBS does not recognize the specified ordinal. |
| 0x80290213 | 78.1 | The requested resource is no longer available. |
| 0x80290214 | 78.1 | The resource type did not match. |
| 0x80290215 | 78.1 | No resources can be unloaded. |
| 0x80290216 | 78.1 | No new entries can be added to the hash table. |
| 0x80290217 | 78.1 | A new TBS context could not be created because there are too many open contexts. |
| 0x80290218 | 78.1 | A new virtual resource could not be created because there are too many open virtual resources. |
| 0x80290219 | 78.1 | The physical presence interface is not supported. |
| 0x8029021a | 78.1 | TBS is not compatible with the version of TPM found on the system. |
| 0x8029021b | 78.1 | No TCG event log is available. |
| 0x80290300 | 78.1 | A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command. |
| 0x80290301 | 78.1 | The user failed to confirm the TPM operation request. |
| 0x80290302 | 78.1 | The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM). |
| 0x80290303 | 78.1 | The BIOS does not support the physical presence interface. |
| 0x802a0001 | 78.1 | The object could not be created. |
| 0x802a0002 | 78.1 | Shutdown was already called on this object or the object that owns it. |
| 0x802a0003 | 78.1 | This method cannot be called during this type of callback. |
| 0x802a0004 | 78.1 | This object has been sealed, so this change is no longer allowed. |
| 0x802a0005 | 78.1 | The requested value was never set. |
| 0x802a0006 | 78.1 | The requested value cannot be determined. |
| 0x802a0007 | 78.1 | A callback returned an invalid output parameter. |
| 0x802a0008 | 78.1 | A callback returned a success code other than S_OK or S_FALSE. |
| 0x802a0009 | 78.1 | A parameter that should be owned by this object is owned by a different object. |
| 0x802a000a | 78.1 | More than one item matched the search criteria. |
| 0x802a000b | 78.1 | A floating-point overflow occurred. |
| 0x802a000c | 78.1 | This method can only be called from the thread that created the object. |
| 0x802a0101 | 78.1 | The storyboard is currently in the schedule. |
| 0x802a0102 | 78.1 | The storyboard is not playing. |
| 0x802a0103 | 78.1 | The start keyframe might occur after the end keyframe. |
| 0x802a0104 | 78.1 | It might not be possible to determine the end keyframe time when the start keyframe is reached. |
| 0x802a0105 | 78.1 | Two repeated portions of a storyboard might overlap. |
| 0x802a0106 | 78.1 | The transition has already been added to a storyboard. |
| 0x802a0107 | 78.1 | The transition has not been added to a storyboard. |
| 0x802a0108 | 78.1 | The transition might eclipse the beginning of another transition in the storyboard. |
| 0x802a0109 | 78.1 | The given time is earlier than the time passed to the last update. |
| 0x802a010a | 78.1 | This client is already connected to a timer. |
| 0x80300002 | 78.1 | Data Collector Set was not found. |
| 0x80300045 | 78.1 | Unable to start Data Collector Set because there are too many folders. |
| 0x80300070 | 78.1 | Not enough free disk space to start Data Collector Set. |
| 0x803000aa | 78.1 | The Data Collector Set or one of its dependencies is already in use. |
| 0x803000b7 | 78.1 | Data Collector Set already exists. |
| 0x80300101 | 78.1 | Property value conflict. |
| 0x80300102 | 78.1 | The current configuration for this Data Collector Set requires that it contain exactly one Data Collector. |
| 0x80300103 | 78.1 | A user account is required in order to commit the current Data Collector Set properties. |
| 0x80300104 | 78.1 | Data Collector Set is not running. |
| 0x80300105 | 78.1 | A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list. |
| 0x80300106 | 78.1 | The executable path you have specified refers to a network share or UNC path. |
| 0x80300107 | 78.1 | The executable path you have specified is already configured for API tracing. |
| 0x80300108 | 78.1 | The executable path you have specified does not exist. Verify that the specified path is correct. |
| 0x80300109 | 78.1 | Data Collector already exists. |
| 0x8030010a | 78.1 | The wait for the Data Collector Set start notification has timed out. |
| 0x8030010b | 78.1 | The wait for the Data Collector to start has timed out. |
| 0x8030010c | 78.1 | The wait for the report generation tool to finish has timed out. |
| 0x8030010d | 78.1 | Duplicate items are not allowed. |
| 0x8030010e | 78.1 | When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename. |
| 0x8030010f | 78.1 | The session name provided is invalid. |
| 0x80300110 | 78.1 | The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation. |
| 0x80300111 | 78.1 | The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation. |
| 0x80300112 | 78.1 | The execution of the Rules Manager failed. |
| 0x80300113 | 78.1 | An error occurred while attempting to compress or extract the data. |
| 0x80310000 | 78.1 | This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel. |
| 0x80310001 | 78.1 | This drive is not encrypted. |
| 0x80310002 | 78.1 | The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310003 | 78.1 | The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310004 | 78.1 | 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. |
| 0x80310005 | 78.1 | 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). |
| 0x80310006 | 78.1 | 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). |
| 0x80310007 | 78.1 | At least one secure key protector is required for this operation to be performed. |
| 0x80310008 | 78.1 | BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker. |
| 0x80310009 | 78.1 | 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. |
| 0x8031000a | 78.1 | 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. |
| 0x8031000b | 78.1 | The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000c | 78.1 | The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000d | 78.1 | The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000e | 78.1 | 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. |
| 0x8031000f | 78.1 | 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. |
| 0x80310010 | 78.1 | The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access. |
| 0x80310011 | 78.1 | 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. |
| 0x80310012 | 78.1 | 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. |
| 0x80310013 | 78.1 | The drive cannot be encrypted because the file system is not supported. |
| 0x80310014 | 78.1 | 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. |
| 0x80310015 | 78.1 | This drive cannot be encrypted. |
| 0x80310016 | 78.1 | The data is not valid. |
| 0x80310017 | 78.1 | The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically. |
| 0x80310018 | 78.1 | You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption. |
| 0x80310019 | 78.1 | The operation attempted cannot be performed on an operating system drive. |
| 0x8031001a | 78.1 | The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again. |
| 0x8031001b | 78.1 | A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. |
| 0x8031001c | 78.1 | A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. |
| 0x8031001d | 78.1 | One or more BitLocker key protectors are required. You cannot delete the last key on this drive. |
| 0x8031001e | 78.1 | Cluster configurations are not supported by BitLocker Drive Encryption. |
| 0x8031001f | 78.1 | The drive specified is already configured to be automatically unlocked on the current computer. |
| 0x80310020 | 78.1 | The operating system drive is not protected by BitLocker Drive Encryption. |
| 0x80310021 | 78.1 | 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. |
| 0x80310022 | 78.1 | 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. |
| 0x80310023 | 78.1 | BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive. |
| 0x80310024 | 78.1 | The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again. |
| 0x80310025 | 78.1 | 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. |
| 0x80310026 | 78.1 | The drive encryption algorithm cannot be used on this sector size. |
| 0x80310027 | 78.1 | The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again. |
| 0x80310028 | 78.1 | The drive specified is not the operating system drive. |
| 0x80310029 | 78.1 | 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. |
| 0x8031002a | 78.1 | 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. |
| 0x8031002b | 78.1 | 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. |
| 0x8031002c | 78.1 | Group Policy settings require that a recovery password be specified before encrypting the drive. |
| 0x8031002d | 78.1 | 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. |
| 0x8031002e | 78.1 | BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive. |
| 0x80310030 | 78.1 | BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker. |
| 0x80310031 | 78.1 | This key protector cannot be added. Only one key protector of this type is allowed for this drive. |
| 0x80310032 | 78.1 | 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. |
| 0x80310033 | 78.1 | The specified key protector was not found on the drive. Try another key protector. |
| 0x80310034 | 78.1 | 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. |
| 0x80310035 | 78.1 | 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. |
| 0x80310036 | 78.1 | The random number generator check test failed. |
| 0x80310037 | 78.1 | 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. |
| 0x80310038 | 78.1 | 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. |
| 0x80310039 | 78.1 | The drive must be fully decrypted to complete this operation. |
| 0x8031003a | 78.1 | The key protector specified cannot be used for this operation. |
| 0x8031003b | 78.1 | No key protectors exist on the drive to perform the hardware test. |
| 0x8031003c | 78.1 | 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. |
| 0x8031003d | 78.1 | 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. |
| 0x8031003e | 78.1 | 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. |
| 0x8031003f | 78.1 | 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. |
| 0x80310040 | 78.1 | 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. |
| 0x80310041 | 7 | The Trusted Platform Module (TPM) was not able to unlock the drive because the system boot information has changed or a PIN was not provided correctly. Verify that the drive has not been tampered with and that changes to the system boot information were caused by a trusted source. After verifying that the drive is safe to access, use the BitLocker recovery console to unlock the drive and then suspend and resume BitLocker to update system boot information that BitLocker associates with this drive. |
| 0x80310042 | 78.1 | The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM). |
| 0x80310043 | 78.1 | The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN. |
| 0x80310044 | 78.1 | A boot application has changed since BitLocker Drive Encryption was enabled. |
| 0x80310045 | 78.1 | The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled. |
| 0x80310046 | 78.1 | 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. |
| 0x80310047 | 78.1 | 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. |
| 0x80310048 | 78.1 | BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310049 | 78.1 | This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system. |
| 0x8031004a | 78.1 | 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. |
| 0x8031004b | 78.1 | The drive cannot be locked when the drive is in use. |
| 0x8031004c | 78.1 | The access token associated with the current thread is not an impersonated token. |
| 0x8031004d | 78.1 | 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. |
| 0x8031004e | 78.1 | You must restart your computer before continuing with BitLocker Drive Encryption. |
| 0x8031004f | 78.1 | Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging. |
| 0x80310050 | 78.1 | No action was taken as BitLocker Drive Encryption is in raw access mode. |
| 0x80310051 | 78.1 | BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use. |
| 0x80310052 | 78.1 | 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. |
| 0x80310053 | 7 | BitLocker Drive Encryption can only be used for recovery purposes when the computer is running Windows Recovery Environment. |
| 0x80310054 | 78.1 | The auto-unlock master key was not available from the operating system drive. |
| 0x80310055 | 78.1 | The system firmware failed to enable clearing of system memory when the computer was restarted. |
| 0x80310056 | 78.1 | The hidden drive cannot be encrypted. |
| 0x80310057 | 78.1 | BitLocker encryption keys were ignored because the drive was in a transient state. |
| 0x80310058 | 78.1 | Public key based protectors are not allowed on this drive. |
| 0x80310059 | 78.1 | BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing. |
| 0x8031005a | 7 | This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.. |
| 0x8031005b | 78.1 | The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information. |
| 0x8031005c | 78.1 | Group Policy settings do not permit the creation of a recovery password. |
| 0x8031005d | 78.1 | Group Policy settings require the creation of a recovery password. |
| 0x8031005e | 78.1 | Group Policy settings do not permit the creation of a recovery key. |
| 0x8031005f | 78.1 | Group Policy settings require the creation of a recovery key. |
| 0x80310060 | 78.1 | Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option. |
| 0x80310061 | 78.1 | Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option. |
| 0x80310062 | 78.1 | Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option. |
| 0x80310063 | 78.1 | Group Policy settings require the use of a startup key. Please choose this BitLocker startup option. |
| 0x80310064 | 78.1 | Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option. |
| 0x80310065 | 78.1 | Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option. |
| 0x80310066 | 78.1 | Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option. |
| 0x80310067 | 78.1 | Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option. |
| 0x80310068 | 78.1 | The PIN provided does not meet minimum or maximum length requirements. |
| 0x80310069 | 78.1 | 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. |
| 0x8031006a | 78.1 | Group Policy settings do not permit the creation of a password. |
| 0x8031006b | 78.1 | Group Policy settings require the creation of a password. |
| 0x8031006c | 78.1 | The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information. |
| 0x8031006d | 78.1 | A password cannot be added to the operating system drive. |
| 0x8031006e | 78.1 | The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive. |
| 0x8031006f | 78.1 | The drive is too small to be protected using BitLocker Drive Encryption. |
| 0x80310070 | 78.1 | 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. |
| 0x80310071 | 78.1 | 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. |
| 0x80310072 | 78.1 | Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption. |
| 0x80310073 | 78.1 | Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption. |
| 0x80310074 | 78.1 | Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption. |
| 0x80310075 | 78.1 | Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked. |
| 0x80310076 | 78.1 | Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked. |
| 0x80310077 | 78.1 | Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives. |
| 0x80310078 | 78.1 | 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. |
| 0x80310079 | 78.1 | 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. |
| 0x80310080 | 78.1 | 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. |
| 0x80310081 | 78.1 | Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols. |
| 0x80310082 | 78.1 | This drive cannot be encrypted because it is reserved for Windows System Recovery Options. |
| 0x80310083 | 78.1 | 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. |
| 0x80310084 | 7 | BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occured, please ask your system administrator to resolve the settings conflict before enabling BitLocker. |
| 0x80310085 | 78.1 | 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. |
| 0x80310086 | 78.1 | 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. |
| 0x80310087 | 78.1 | 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. |
| 0x80310088 | 78.1 | 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. |
| 0x80310089 | 78.1 | The requested virtualization size is too big. |
| 0x80310090 | 78.1 | 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. |
| 0x80310091 | 78.1 | 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. |
| 0x80310092 | 78.1 | 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. |
| 0x80310093 | 78.1 | 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. |
| 0x80310094 | 78.1 | 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. |
| 0x80310095 | 78.1 | Removal of the data recovery agent certificate must be done using the Certificates snap-in. |
| 0x80310096 | 78.1 | 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. |
| 0x80310097 | 78.1 | The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive. |
| 0x80310098 | 78.1 | 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. |
| 0x80310099 | 78.1 | The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals. |
| 0x8031009a | 78.1 | The requested TPM PIN contains invalid characters. |
| 0x8031009b | 78.1 | 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. |
| 0x80320001 | 78.1 | The callout does not exist. |
| 0x80320002 | 78.1 | The filter condition does not exist. |
| 0x80320003 | 78.1 | The filter does not exist. |
| 0x80320004 | 78.1 | The layer does not exist. |
| 0x80320005 | 78.1 | The provider does not exist. |
| 0x80320006 | 78.1 | The provider context does not exist. |
| 0x80320007 | 78.1 | The sublayer does not exist. |
| 0x80320008 | 78.1 | The object does not exist. |
| 0x80320009 | 78.1 | An object with that GUID or LUID already exists. |
| 0x8032000a | 78.1 | The object is referenced by other objects so cannot be deleted. |
| 0x8032000b | 78.1 | The call is not allowed from within a dynamic session. |
| 0x8032000c | 78.1 | The call was made from the wrong session so cannot be completed. |
| 0x8032000d | 78.1 | The call must be made from within an explicit transaction. |
| 0x8032000e | 78.1 | The call is not allowed from within an explicit transaction. |
| 0x8032000f | 78.1 | The explicit transaction has been forcibly cancelled. |
| 0x80320010 | 78.1 | The session has been cancelled. |
| 0x80320011 | 78.1 | The call is not allowed from within a read-only transaction. |
| 0x80320012 | 78.1 | The call timed out while waiting to acquire the transaction lock. |
| 0x80320013 | 78.1 | Collection of network diagnostic events is disabled. |
| 0x80320014 | 78.1 | The operation is not supported by the specified layer. |
| 0x80320015 | 78.1 | The call is allowed for kernel-mode callers only. |
| 0x80320016 | 78.1 | The call tried to associate two objects with incompatible lifetimes. |
| 0x80320017 | 78.1 | The object is built in so cannot be deleted. |
| 0x80320018 | 78.1 | The maximum number of callouts has been reached. |
| 0x80320019 | 78.1 | A notification could not be delivered because a message queue is at its maximum capacity. |
| 0x8032001a | 78.1 | The traffic parameters do not match those for the security association context. |
| 0x8032001b | 78.1 | The call is not allowed for the current security association state. |
| 0x8032001c | 78.1 | A required pointer is null. |
| 0x8032001d | 78.1 | An enumerator is not valid. |
| 0x8032001e | 78.1 | The flags field contains an invalid value. |
| 0x8032001f | 78.1 | A network mask is not valid. |
| 0x80320020 | 78.1 | An FWP_RANGE is not valid. |
| 0x80320021 | 78.1 | The time interval is not valid. |
| 0x80320022 | 78.1 | An array that must contain at least one element is zero length. |
| 0x80320023 | 78.1 | The displayData.name field cannot be null. |
| 0x80320024 | 78.1 | The action type is not one of the allowed action types for a filter. |
| 0x80320025 | 78.1 | The filter weight is not valid. |
| 0x80320026 | 78.1 | A filter condition contains a match type that is not compatible with the operands. |
| 0x80320027 | 78.1 | An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
| 0x80320028 | 78.1 | An integer value is outside the allowed range. |
| 0x80320029 | 78.1 | A reserved field is non-zero. |
| 0x8032002a | 78.1 | A filter cannot contain multiple conditions operating on a single field. |
| 0x8032002b | 78.1 | A policy cannot contain the same keying module more than once. |
| 0x8032002c | 78.1 | The action type is not compatible with the layer. |
| 0x8032002d | 78.1 | The action type is not compatible with the sublayer. |
| 0x8032002e | 78.1 | The raw context or the provider context is not compatible with the layer. |
| 0x8032002f | 78.1 | The raw context or the provider context is not compatible with the callout. |
| 0x80320030 | 78.1 | The authentication method is not compatible with the policy type. |
| 0x80320031 | 78.1 | The Diffie-Hellman group is not compatible with the policy type. |
| 0x80320032 | 78.1 | An IKE policy cannot contain an Extended Mode policy. |
| 0x80320033 | 78.1 | The enumeration template or subscription will never match any objects. |
| 0x80320034 | 78.1 | The provider context is of the wrong type. |
| 0x80320035 | 78.1 | The parameter is incorrect. |
| 0x80320036 | 78.1 | The maximum number of sublayers has been reached. |
| 0x80320037 | 78.1 | The notification function for a callout returned an error. |
| 0x80320038 | 78.1 | The IPsec authentication transform is not valid. |
| 0x80320039 | 78.1 | The IPsec cipher transform is not valid. |
| 0x8032003a | 78.1 | The IPsec cipher transform is not compatible with the policy. |
| 0x8032003b | 78.1 | The combination of IPsec transform types is not valid. |
| 0x8032003c | 78.1 | A policy cannot contain the same auth method more than once. |
| 0x80320104 | 78.1 | The packet should be dropped, no ICMP should be sent. |
| 0x80340002 | 78.1 | The binding to the network interface is being closed. |
| 0x80340004 | 78.1 | An invalid version was specified. |
| 0x80340005 | 78.1 | An invalid characteristics table was used. |
| 0x80340006 | 78.1 | Failed to find the network interface or network interface is not ready. |
| 0x80340007 | 78.1 | Failed to open the network interface. |
| 0x80340008 | 78.1 | Network interface has encountered an internal unrecoverable failure. |
| 0x80340009 | 78.1 | The multicast list on the network interface is full. |
| 0x8034000a | 78.1 | An attempt was made to add a duplicate multicast address to the list. |
| 0x8034000b | 78.1 | At attempt was made to remove a multicast address that was never added. |
| 0x8034000c | 78.1 | Netowork interface aborted the request. |
| 0x8034000d | 78.1 | Network interface can not process the request because it is being reset. |
| 0x8034000f | 78.1 | An attempt was made to send an invalid packet on a network interface. |
| 0x80340010 | 78.1 | The specified request is not a valid operation for the target device. |
| 0x80340011 | 78.1 | Network interface is not ready to complete this operation. |
| 0x80340014 | 78.1 | The length of the buffer submitted for this operation is not valid. |
| 0x80340015 | 78.1 | The data used for this operation is not valid. |
| 0x80340016 | 78.1 | The length of buffer submitted for this operation is too small. |
| 0x80340017 | 78.1 | Network interface does not support this OID (Object Identifier) |
| 0x80340018 | 78.1 | The network interface has been removed. |
| 0x80340019 | 78.1 | Network interface does not support this media type. |
| 0x8034001a | 78.1 | An attempt was made to remove a token ring group address that is in use by other components. |
| 0x8034001b | 78.1 | An attempt was made to map a file that can not be found. |
| 0x8034001c | 7 | An error occured while NDIS tried to map the file. |
| 0x8034001d | 78.1 | An attempt was made to map a file that is alreay mapped. |
| 0x8034001e | 78.1 | An attempt to allocate a hardware resource failed because the resource is used by another component. |
| 0x8034001f | 78.1 | The I/O operation failed because network media is disconnected or wireless access point is out of range. |
| 0x80340022 | 78.1 | The network address used in the request is invalid. |
| 0x8034002a | 78.1 | The offload operation on the network interface has been paused. |
| 0x8034002b | 78.1 | Network interface was not found. |
| 0x8034002c | 78.1 | The revision number specified in the structure is not supported. |
| 0x8034002d | 78.1 | The specified port does not exist on this network interface. |
| 0x8034002e | 78.1 | The current state of the specified port on this network interface does not support the requested operation. |
| 0x8034002f | 78.1 | The miniport adapter is in low power state. |
| 0x803400bb | 78.1 | Netword interface does not support this request. |
| 0x80342000 | 78.1 | The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
| 0x80342001 | 78.1 | The wireless local area network interface is busy and can not perform the requested operation. |
| 0x80342002 | 7 | The wireless local area network interface is power down and doesn't support the requested operation. |
| 0x80342003 | 78.1 | The list of wake on LAN patterns is full. |
| 0x80342004 | 78.1 | The list of low power protocol offloads is full. |
| 0x80370001 | 7 | 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. For detailed information, see http://go.microsoft.com/fwlink/?LinkId=92362. |
| 0x80380001 | 78.1 | The regeneration operation was not able to copy all data from the active plexes due to bad sectors. |
| 0x80380002 | 78.1 | One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems. |
| 0x80390001 | 78.1 | Some BCD entries were not imported correctly from the BCD store. |
| 0x80390003 | 78.1 | Some BCD entries were not synchronized correctly with the firmware. |
| 0x803a0001 | 78.1 | The virtualization storage subsystem has generated an error. |
| 0x803c0100 | 78.1 | The operation was cancelled. |
| 0x803c0101 | 78.1 | An error occurred when running a PowerShell script. |
| 0x803c0102 | 78.1 | An error occurred when interacting with PowerShell runtime. |
| 0x803c0103 | 78.1 | An error occurred in the Scripted Diagnostic Managed Host. |
| 0x803c0104 | 78.1 | The troubleshooting pack does not contain a required verifier to complete the verification. |
| 0x803c0106 | 78.1 | Scripted diagnostics is disabled by group policy. |
| 0x803c0107 | 78.1 | Trust validation of the troubleshooting pack failed. |
| 0x803c0108 | 78.1 | The troubleshooting pack cannot be executed on this system. |
| 0x803c0109 | 78.1 | This version of the troubleshooting pack is not supported. |
| 0x803c010a | 78.1 | A required resource cannot be loaded. |
| 0x803c010b | 78.1 | The troubleshooting pack reported information for a root cause without adding the root cause. |
| 0x803d0000 | 78.1 | The input data was not in the expected format or did not have the expected value. |
| 0x803d0001 | 78.1 | The operation could not be completed because the object is in a faulted state due to a previous error. |
| 0x803d0002 | 78.1 | The operation could not be completed because it would lead to numeric overflow. |
| 0x803d0003 | 78.1 | The operation is not allowed due to the current state of the object. |
| 0x803d0004 | 78.1 | The operation was aborted. |
| 0x803d0005 | 78.1 | Access was denied by the remote endpoint. |
| 0x803d0006 | 78.1 | The operation did not complete within the time allotted. |
| 0x803d0007 | 78.1 | The operation was abandoned. |
| 0x803d0008 | 78.1 | A quota was exceeded. |
| 0x803d0009 | 78.1 | The information was not available in the specified language. |
| 0x803d000a | 78.1 | Security verification was not successful for the received data. |
| 0x803d000b | 78.1 | The address is already being used. |
| 0x803d000c | 78.1 | The address is not valid for this context. |
| 0x803d000d | 78.1 | The remote endpoint does not exist or could not be located. |
| 0x803d000e | 78.1 | The remote endpoint is not currently in service at this location. |
| 0x803d000f | 78.1 | The remote endpoint could not process the request. |
| 0x803d0010 | 78.1 | The remote endpoint was not reachable. |
| 0x803d0011 | 78.1 | The operation was not supported by the remote endpoint. |
| 0x803d0012 | 78.1 | The remote endpoint is unable to process the request due to being overloaded. |
| 0x803d0013 | 78.1 | A message containing a fault was received from the remote endpoint. |
| 0x803d0014 | 78.1 | The connection with the remote endpoint was terminated. |
| 0x803d0015 | 78.1 | The HTTP proxy server could not process the request. |
| 0x803d0016 | 78.1 | Access was denied by the HTTP proxy server. |
| 0x803d0017 | 78.1 | The requested feature is not available on this platform. |
| 0x803d0018 | 78.1 | The HTTP proxy server requires HTTP authentication scheme 'basic'. |
| 0x803d0019 | 78.1 | The HTTP proxy server requires HTTP authentication scheme 'digest'. |
| 0x803d001a | 78.1 | The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
| 0x803d001b | 78.1 | The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
| 0x803d001c | 78.1 | The remote endpoint requires HTTP authentication scheme 'basic'. |
| 0x803d001d | 78.1 | The remote endpoint requires HTTP authentication scheme 'digest'. |
| 0x803d001e | 78.1 | The remote endpoint requires HTTP authentication scheme 'NTLM'. |
| 0x803d001f | 78.1 | The remote endpoint requires HTTP authentication scheme 'negotiate'. |
| 0x803d0020 | 78.1 | The endpoint address URL is invalid. |
| 0x803d0021 | 7 | Unrecognized error occured in the Windows Web Services framework. |
| 0x803d0022 | 78.1 | A security token was rejected by the server because it has expired. |
| 0x803d0023 | 78.1 | A security operation failed in the Windows Web Services framework. |
| 0x80548201 | 78.1 | Context is not activated. |
| 0x80548202 | 78.1 | Bad SIM is inserted. |
| 0x80548203 | 78.1 | Requested data class is not avaialable. |
| 0x80548204 | 78.1 | Access point name (APN) or Access string is incorrect. |
| 0x80548205 | 78.1 | Max activated contexts have reached. |
| 0x80548206 | 78.1 | Device is in packet detach state. |
| 0x80548207 | 78.1 | Provider is not visible. |
| 0x80548208 | 78.1 | Radio is powered off. |
| 0x80548209 | 78.1 | MBN subscription is not activated. |
| 0x8054820a | 78.1 | SIM is not inserted. |
| 0x8054820b | 78.1 | Voice call in progress. |
| 0x8054820c | 78.1 | Visible provider cache is invalid. |
| 0x8054820d | 78.1 | Device is not registered. |
| 0x8054820e | 78.1 | Providers not found. |
| 0x8054820f | 78.1 | Pin is not supported. |
| 0x80548210 | 78.1 | Pin is required. |
| 0x80548211 | 78.1 | PIN is disabled. |
| 0x80548212 | 78.1 | Generic Failure. |
| 0x80548218 | 78.1 | Profile is invalid. |
| 0x80548219 | 78.1 | Default profile exist. |
| 0x80548220 | 78.1 | SMS encoding is not supported. |
| 0x80548221 | 78.1 | SMS filter is not supported. |
| 0x80548222 | 78.1 | Invalid SMS memory index is used. |
| 0x80548223 | 78.1 | SMS language is not supported. |
| 0x80548224 | 78.1 | SMS memory failure occurred. |
| 0x80548225 | 78.1 | SMS network timeout happened. |
| 0x80548226 | 78.1 | Unknown SMSC address is used. |
| 0x80548227 | 78.1 | SMS format is not supported. |
| 0x80548228 | 78.1 | SMS operation is not allowed. |
| 0x80548229 | 78.1 | Device SMS memory is full. |
| 0xc0090001 | 78.1 | The specified event is currently not being audited. |
| 0xc0090002 | 78.1 | The SID filtering operation removed all SIDs. |
| 0xc0090003 | 78.1 | Business rule scripts are disabled for the calling application. |
| 0xc02605e8 | 78.1 | 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. |
| 0xc0261003 | 78.1 | Checksum of the obtained monitor descriptor is invalid. |
| 0xc0261004 | 78.1 | Monitor descriptor contains an invalid standard timing block. |
| 0xc0261005 | 78.1 | WMI data block registration failed for one of the MSMonitorClass WMI subclasses. |
| 0xc0261006 | 78.1 | Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. |
| 0xc0261007 | 78.1 | Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. |
| 0xc0261008 | 78.1 | There is no monitor descriptor data at the specified (offset, size) region. |
| 0xc0261009 | 78.1 | Monitor descriptor contains an invalid detailed timing block. |
| 0xc026100a | 78.1 | Monitor descriptor contains invalid manufacture date. |
| 0xc0262000 | 78.1 | Exclusive mode ownership is needed to create unmanaged primary allocation. |
| 0xc0262001 | 78.1 | The driver needs more DMA buffer space in order to complete the requested operation. |
| 0xc0262002 | 78.1 | Specified display adapter handle is invalid. |
| 0xc0262003 | 78.1 | Specified display adapter and all of its state has been reset. |
| 0xc0262004 | 78.1 | The driver stack doesn't match the expected driver model. |
| 0xc0262005 | 78.1 | Present happened but ended up into the changed desktop mode |
| 0xc0262006 | 78.1 | Nothing to present due to desktop occlusion |
| 0xc0262007 | 78.1 | Not able to present due to denial of desktop access |
| 0xc0262008 | 78.1 | Not able to present with color convertion |
| 0xc0262009 | 78.1 | The kernel driver detected a version mismatch between it and the user mode driver. |
| 0xc026200b | 78.1 | Present redirection is disabled (desktop windowing management subsystem is off). |
| 0xc026200c | 78.1 | Previous exclusive VidPn source owner has released its ownership |
| 0xc0262100 | 78.1 | Not enough video memory available to complete the operation. |
| 0xc0262101 | 78.1 | Couldn't probe and lock the underlying memory of an allocation. |
| 0xc0262102 | 78.1 | The allocation is currently busy. |
| 0xc0262103 | 78.1 | An object being referenced has reach the maximum reference count already and can't be reference further. |
| 0xc0262104 | 78.1 | A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. |
| 0xc0262105 | 78.1 | A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. |
| 0xc0262106 | 78.1 | The allocation is invalid. |
| 0xc0262107 | 78.1 | No more unswizzling aperture are currently available. |
| 0xc0262108 | 78.1 | The current allocation can't be unswizzled by an aperture. |
| 0xc0262109 | 78.1 | The request failed because a pinned allocation can't be evicted. |
| 0xc0262110 | 7 | The allocation can't be used from it's current segment location for the specified operation. |
| 0xc0262111 | 78.1 | A locked allocation can't be used in the current command buffer. |
| 0xc0262112 | 78.1 | The allocation being referenced has been closed permanently. |
| 0xc0262113 | 78.1 | An invalid allocation instance is being referenced. |
| 0xc0262114 | 78.1 | An invalid allocation handle is being referenced. |
| 0xc0262115 | 78.1 | The allocation being referenced doesn't belong to the current device. |
| 0xc0262116 | 78.1 | The specified allocation lost its content. |
| 0xc0262200 | 78.1 | GPU exception is detected on the given device. The device is not able to be scheduled. |
| 0xc0262300 | 78.1 | Specified VidPN topology is invalid. |
| 0xc0262301 | 78.1 | Specified VidPN topology is valid but is not supported by this model of the display adapter. |
| 0xc0262302 | 78.1 | Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. |
| 0xc0262303 | 78.1 | Specified VidPN handle is invalid. |
| 0xc0262304 | 78.1 | Specified video present source is invalid. |
| 0xc0262305 | 78.1 | Specified video present target is invalid. |
| 0xc0262306 | 78.1 | Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). |
| 0xc0262308 | 78.1 | Specified VidPN source mode set is invalid. |
| 0xc0262309 | 78.1 | Specified VidPN target mode set is invalid. |
| 0xc026230a | 78.1 | Specified video signal frequency is invalid. |
| 0xc026230b | 78.1 | Specified video signal active region is invalid. |
| 0xc026230c | 78.1 | Specified video signal total region is invalid. |
| 0xc0262310 | 78.1 | Specified video present source mode is invalid. |
| 0xc0262311 | 78.1 | Specified video present target mode is invalid. |
| 0xc0262312 | 78.1 | Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. |
| 0xc0262313 | 78.1 | Specified video present path is already in VidPN's topology. |
| 0xc0262314 | 78.1 | Specified mode is already in the mode set. |
| 0xc0262315 | 78.1 | Specified video present source set is invalid. |
| 0xc0262316 | 78.1 | Specified video present target set is invalid. |
| 0xc0262317 | 78.1 | Specified video present source is already in the video present source set. |
| 0xc0262318 | 78.1 | Specified video present target is already in the video present target set. |
| 0xc0262319 | 78.1 | Specified VidPN present path is invalid. |
| 0xc026231a | 78.1 | Miniport has no recommendation for augmentation of the specified VidPN's topology. |
| 0xc026231b | 78.1 | Specified monitor frequency range set is invalid. |
| 0xc026231c | 78.1 | Specified monitor frequency range is invalid. |
| 0xc026231d | 78.1 | Specified frequency range is not in the specified monitor frequency range set. |
| 0xc026231f | 78.1 | Specified frequency range is already in the specified monitor frequency range set. |
| 0xc0262320 | 78.1 | Specified mode set is stale. Please reacquire the new mode set. |
| 0xc0262321 | 78.1 | Specified monitor source mode set is invalid. |
| 0xc0262322 | 78.1 | Specified monitor source mode is invalid. |
| 0xc0262323 | 78.1 | Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
| 0xc0262324 | 78.1 | ID of the specified mode is already used by another mode in the set. |
| 0xc0262325 | 78.1 | System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
| 0xc0262326 | 78.1 | Number of video present targets must be greater than or equal to the number of video present sources. |
| 0xc0262327 | 78.1 | Specified present path is not in VidPN's topology. |
| 0xc0262328 | 78.1 | Display adapter must have at least one video present source. |
| 0xc0262329 | 78.1 | Display adapter must have at least one video present target. |
| 0xc026232a | 78.1 | Specified monitor descriptor set is invalid. |
| 0xc026232b | 78.1 | Specified monitor descriptor is invalid. |
| 0xc026232c | 78.1 | Specified descriptor is not in the specified monitor descriptor set. |
| 0xc026232d | 78.1 | Specified descriptor is already in the specified monitor descriptor set. |
| 0xc026232e | 78.1 | ID of the specified monitor descriptor is already used by another descriptor in the set. |
| 0xc026232f | 78.1 | Specified video present target subset type is invalid. |
| 0xc0262330 | 78.1 | Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
| 0xc0262331 | 78.1 | ID of the specified video present source is already used by another source in the set. |
| 0xc0262332 | 78.1 | ID of the specified video present target is already used by another target in the set. |
| 0xc0262333 | 78.1 | Specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
| 0xc0262334 | 78.1 | Newly arrived monitor could not be associated with a display adapter. |
| 0xc0262335 | 78.1 | Display adapter in question does not have an associated VidPN manager. |
| 0xc0262336 | 78.1 | VidPN manager of the display adapter in question does not have an active VidPN. |
| 0xc0262337 | 78.1 | Specified VidPN topology is stale. Please reacquire the new topology. |
| 0xc0262338 | 78.1 | There is no monitor connected on the specified video present target. |
| 0xc0262339 | 78.1 | Specified source is not part of the specified VidPN's topology. |
| 0xc026233a | 78.1 | Specified primary surface size is invalid. |
| 0xc026233b | 78.1 | Specified visible region size is invalid. |
| 0xc026233c | 78.1 | Specified stride is invalid. |
| 0xc026233d | 78.1 | Specified pixel format is invalid. |
| 0xc026233e | 78.1 | Specified color basis is invalid. |
| 0xc026233f | 78.1 | Specified pixel value access mode is invalid. |
| 0xc0262340 | 78.1 | Specified target is not part of the specified VidPN's topology. |
| 0xc0262341 | 78.1 | Failed to acquire display mode management interface. |
| 0xc0262342 | 78.1 | Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
| 0xc0262343 | 78.1 | Specified VidPN is active and cannot be accessed. |
| 0xc0262344 | 78.1 | Specified VidPN present path importance ordinal is invalid. |
| 0xc0262345 | 78.1 | Specified VidPN present path content geometry transformation is invalid. |
| 0xc0262346 | 78.1 | Specified content geometry transformation is not supported on the respective VidPN present path. |
| 0xc0262347 | 78.1 | Specified gamma ramp is invalid. |
| 0xc0262348 | 78.1 | Specified gamma ramp is not supported on the respective VidPN present path. |
| 0xc0262349 | 78.1 | Multi-sampling is not supported on the respective VidPN present path. |
| 0xc026234a | 78.1 | Specified mode is not in the specified mode set. |
| 0xc026234d | 78.1 | Specified VidPN topology recommendation reason is invalid. |
| 0xc026234e | 78.1 | Specified VidPN present path content type is invalid. |
| 0xc026234f | 78.1 | Specified VidPN present path copy protection type is invalid. |
| 0xc0262350 | 78.1 | No more than one unassigned mode set can exist at any given time for a given VidPN source/target. |
| 0xc0262352 | 78.1 | Specified scanline ordering type is invalid. |
| 0xc0262353 | 78.1 | Topology changes are not allowed for the specified VidPN. |
| 0xc0262354 | 78.1 | All available importance ordinals are already used in specified topology. |
| 0xc0262355 | 78.1 | Specified primary surface has a different private format attribute than the current primary surface |
| 0xc0262356 | 78.1 | Specified mode pruning algorithm is invalid |
| 0xc0262357 | 78.1 | Specified monitor capability origin is invalid. |
| 0xc0262358 | 78.1 | Specified monitor frequency range constraint is invalid. |
| 0xc0262359 | 78.1 | Maximum supported number of present paths has been reached. |
| 0xc026235a | 78.1 | Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. |
| 0xc026235b | 78.1 | Specified client type was not recognized. |
| 0xc026235c | 78.1 | Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). |
| 0xc0262400 | 78.1 | Specified display adapter child device already has an external device connected to it. |
| 0xc0262401 | 78.1 | Specified display adapter child device does not support descriptor exposure. |
| 0xc0262430 | 78.1 | The display adapter is not linked to any other adapters. |
| 0xc0262431 | 78.1 | Lead adapter in a linked configuration was not enumerated yet. |
| 0xc0262432 | 78.1 | Some chain adapters in a linked configuration were not enumerated yet. |
| 0xc0262433 | 78.1 | The chain of linked adapters is not ready to start because of an unknown failure. |
| 0xc0262434 | 78.1 | An attempt was made to start a lead link display adapter when the chain links were not started yet. |
| 0xc0262435 | 78.1 | An attempt was made to power up a lead link display adapter when the chain links were powered down. |
| 0xc0262436 | 78.1 | The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. |
| 0xc0262438 | 78.1 | The driver trying to start is not the same as the driver for the POSTed display adapter. |
| 0xc026243b | 78.1 | An operation is being attempted that requires the display adapter to be in a quiescent state. |
| 0xc0262500 | 78.1 | The driver does not support OPM. |
| 0xc0262501 | 78.1 | The driver does not support COPP. |
| 0xc0262502 | 78.1 | The driver does not support UAB. |
| 0xc0262503 | 78.1 | The specified encrypted parameters are invalid. |
| 0xc0262505 | 78.1 | The GDI display device passed to this function does not have any active video outputs. |
| 0xc026250b | 78.1 | An internal error caused this operation to fail. |
| 0xc026250c | 78.1 | The function failed because the caller passed in an invalid OPM user mode handle. |
| 0xc026250e | 78.1 | A certificate could not be returned because the certificate buffer passed to the function was too small. |
| 0xc026250f | 78.1 | A video output could not be created because the frame buffer is in spanning mode. |
| 0xc0262510 | 78.1 | A video output could not be created because the frame buffer is in theater mode. |
| 0xc0262511 | 78.1 | The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. |
| 0xc0262512 | 78.1 | The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification. |
| 0xc0262513 | 78.1 | The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. |
| 0xc0262514 | 78.1 | The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. |
| 0xc0262515 | 78.1 | The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. |
| 0xc0262516 | 78.1 | 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. |
| 0xc0262517 | 78.1 | The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high. |
| 0xc0262518 | 78.1 | The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. |
| 0xc026251a | 78.1 | 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. |
| 0xc026251b | 78.1 | 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. |
| 0xc026251c | 78.1 | 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. |
| 0xc026251d | 78.1 | 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. |
| 0xc026251e | 78.1 | The method failed because an unexpected error occurred inside of a display driver. |
| 0xc026251f | 78.1 | 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. |
| 0xc0262520 | 78.1 | 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. |
| 0xc0262521 | 78.1 | 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. |
| 0xc0262580 | 78.1 | The monitor connected to the specified video output does not have an I2C bus. |
| 0xc0262581 | 78.1 | No device on the I2C bus has the specified address. |
| 0xc0262582 | 78.1 | An error occurred while transmitting data to the device on the I2C bus. |
| 0xc0262583 | 78.1 | An error occurred while receiving data from the device on the I2C bus. |
| 0xc0262584 | 78.1 | The monitor does not support the specified VCP code. |
| 0xc0262585 | 78.1 | The data received from the monitor is invalid. |
| 0xc0262586 | 78.1 | 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. |
| 0xc0262587 | 78.1 | 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. |
| 0xc0262588 | 7 | An internal Monitor Configuration API error occured. |
| 0xc0262589 | 78.1 | An operation failed because a DDC/CI message had an invalid value in its command field. |
| 0xc026258a | 78.1 | An error occurred because the field length of a DDC/CI message contained an invalid value. |
| 0xc026258b | 78.1 | 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. |
| 0xc026258c | 78.1 | This function failed because an invalid monitor handle was passed to it. |
| 0xc026258d | 78.1 | 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. |
| 0xc02625d8 | 78.1 | A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value. |
| 0xc02625d9 | 78.1 | The monitor's VCP Version (0xDF) VCP code returned an invalid version value. |
| 0xc02625da | 78.1 | The monitor does not comply with the MCCS specification it claims to support. |
| 0xc02625db | 78.1 | 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. |
| 0xc02625dc | 78.1 | 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. |
| 0xc02625de | 78.1 | 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. |
| 0xc02625df | 78.1 | 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. |
| 0xc02625e0 | 78.1 | 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. |
| 0xc02625e1 | 78.1 | This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. |
| 0xc02625e2 | 78.1 | The function failed because the specified GDI display device was not attached to the Windows desktop. |
| 0xc02625e3 | 78.1 | This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. |
| 0xc02625e4 | 78.1 | 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. |
| 0xc02625e5 | 78.1 | The function failed because the specified GDI device did not have any monitors associated with it. |
| 0xc02625e6 | 78.1 | An array passed to the function cannot hold all of the data that the function must copy into the array. |
| 0xc02625e7 | 78.1 | An internal error caused an operation to fail. |
| 0xc034100f | 78.1 | The TCP connection is not offloadable because of a local policy setting. |
| 0xc0341012 | 78.1 | The TCP connection is not offloadable by the Chimney Offload target. |
| 0xc0341013 | 78.1 | The IP Path object is not in an offloadable state. |
| 0xc0350002 | 78.1 | The hypervisor does not support the operation because the specified hypercall code is not supported. |
| 0xc0350003 | 78.1 | The hypervisor does not support the operation because the encoding for the hypercall input register is not supported. |
| 0xc0350004 | 78.1 | The hypervisor could not perform the operation beacuse a parameter has an invalid alignment. |
| 0xc0350005 | 78.1 | The hypervisor could not perform the operation beacuse an invalid parameter was specified. |
| 0xc0350006 | 78.1 | Access to the specified object was denied. |
| 0xc0350007 | 78.1 | The hypervisor could not perform the operation because the partition is entering or in an invalid state. |
| 0xc0350008 | 78.1 | The operation is not allowed in the current state. |
| 0xc0350009 | 78.1 | The hypervisor does not recognize the specified partition property. |
| 0xc035000a | 78.1 | The specified value of a partition property is out of range or violates an invariant. |
| 0xc035000b | 78.1 | There is not enough memory in the hypervisor pool to complete the operation. |
| 0xc035000c | 78.1 | The maximum partition depth has been exceeded for the partition hierarchy. |
| 0xc035000d | 78.1 | A partition with the specified partition Id does not exist. |
| 0xc035000e | 78.1 | The hypervisor could not perform the operation because the specified VP index is invalid. |
| 0xc0350011 | 78.1 | The hypervisor could not perform the operation because the specified port identifier is invalid. |
| 0xc0350012 | 78.1 | The hypervisor could not perform the operation because the specified connection identifier is invalid. |
| 0xc0350013 | 78.1 | Not enough buffers were supplied to send a message. |
| 0xc0350014 | 78.1 | The previous virtual interrupt has not been acknowledged. |
| 0xc0350016 | 78.1 | The previous virtual interrupt has already been acknowledged. |
| 0xc0350017 | 78.1 | The indicated partition is not in a valid state for saving or restoring. |
| 0xc0350018 | 78.1 | The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled. |
| 0xc0350019 | 78.1 | 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. |
| 0xc035001a | 78.1 | The proximity domain information is invalid. |
| 0xc035001b | 78.1 | An attempt to retrieve debugging data failed because none was available. |
| 0xc035001c | 78.1 | The physical connection being used for debuggging has not recorded any receive activity since the last operation. |
| 0xc035001d | 78.1 | There are not enough resources to complete the operation. |
| 0xc035001e | 78.1 | A hypervisor feature is not available to the user. |
| 0xc0351000 | 78.1 | No hypervisor is present on this system. |
| 0xc0370001 | 78.1 | 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. |
| 0xc0370002 | 78.1 | 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. |
| 0xc0370003 | 78.1 | 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. |
| 0xc0370004 | 78.1 | 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. |
| 0xc0370005 | 78.1 | 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. |
| 0xc0370006 | 78.1 | The partition name of the virtualization infrastructure driver exceeds the maximum. |
| 0xc0370007 | 78.1 | The message queue name of the virtualization infrastructure driver exceeds the maximum. |
| 0xc0370008 | 78.1 | Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists. |
| 0xc0370009 | 78.1 | 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. |
| 0xc037000a | 78.1 | 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. |
| 0xc037000b | 78.1 | A message queue with the same name already exists for the virtualization infrastructure driver. |
| 0xc037000c | 78.1 | 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. |
| 0xc037000d | 78.1 | The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed. |
| 0xc037000e | 78.1 | 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. |
| 0xc037000f | 7 | 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. For detailed information, see http://go.microsoft.com/fwlink/?LinkId=92362. |
| 0xc0370010 | 78.1 | The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology. |
| 0xc0370011 | 78.1 | The memory block for the virtualization infrastructure driver is already associated with a message queue. |
| 0xc0370012 | 78.1 | The handle is not a valid memory block handle for the virtualization infrastructure driver. |
| 0xc0370013 | 78.1 | 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. |
| 0xc0370014 | 78.1 | The handle is not a valid message queue handle for the virtualization infrastructure driver. |
| 0xc0370015 | 78.1 | The handle is not a valid page range handle for the virtualization infrastructure driver. |
| 0xc0370016 | 78.1 | Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block. |
| 0xc0370017 | 78.1 | 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. |
| 0xc0370018 | 78.1 | The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver. |
| 0xc0370019 | 78.1 | Notifications cannot be created on the memory block because it is use. |
| 0xc037001a | 78.1 | 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. |
| 0xc037001b | 78.1 | Cannot add a virtual processor to the partition because the maximum has been reached. |
| 0xc037001c | 78.1 | Cannot stop the virtual processor immediately because of a pending intercept. |
| 0xc037001d | 78.1 | Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xc037001e | 78.1 | 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. |
| 0xc037001f | 78.1 | 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. |
| 0xc0370020 | 78.1 | 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. |
| 0xc0370021 | 78.1 | 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. |
| 0xc0370022 | 78.1 | 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. |
| 0xc0370023 | 78.1 | 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. |
| 0xc0370024 | 78.1 | 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. |
| 0xc0370025 | 78.1 | 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. |
| 0xc0370026 | 78.1 | 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. |
| 0xc0370027 | 78.1 | 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. |
| 0xc0370028 | 78.1 | 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. |
| 0xc0370029 | 78.1 | 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. |
| 0xc0380001 | 78.1 | The configuration database is full. |
| 0xc0380002 | 78.1 | The configuration data on the disk is corrupted. |
| 0xc0380003 | 78.1 | The configuration on the disk is not insync with the in-memory configuration. |
| 0xc0380004 | 78.1 | A majority of disks failed to be updated with the new configuration. |
| 0xc0380005 | 78.1 | The disk contains non-simple volumes. |
| 0xc0380006 | 78.1 | The same disk was specified more than once in the migration list. |
| 0xc0380007 | 78.1 | The disk is already dynamic. |
| 0xc0380008 | 78.1 | The specified disk id is invalid. There are no disks with the specified disk id. |
| 0xc0380009 | 78.1 | The specified disk is an invalid disk. Operation cannot complete on an invalid disk. |
| 0xc038000a | 78.1 | The specified disk(s) cannot be removed since it is the last remaining voter. |
| 0xc038000b | 78.1 | The specified disk has an invalid disk layout. |
| 0xc038000c | 78.1 | The disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout. |
| 0xc038000d | 78.1 | The disk layout contains partitions which are not cylinder aligned. |
| 0xc038000e | 78.1 | The disk layout contains partitions which are samller than the minimum size. |
| 0xc038000f | 78.1 | The disk layout contains primary partitions in between logical drives. This is an invalid disk layout. |
| 0xc0380010 | 78.1 | The disk layout contains more than the maximum number of supported partitions. |
| 0xc0380011 | 78.1 | The specified disk is missing. The operation cannot complete on a missing disk. |
| 0xc0380012 | 78.1 | The specified disk is not empty. |
| 0xc0380013 | 78.1 | There is not enough usable space for this operation. |
| 0xc0380014 | 78.1 | The force revectoring of bad sectors failed. |
| 0xc0380015 | 78.1 | The specified disk has an invalid sector size. |
| 0xc0380016 | 78.1 | The specified disk set contains volumes which exist on disks outside of the set. |
| 0xc0380017 | 78.1 | A disk in the volume layout provides extents to more than one member of a plex. |
| 0xc0380018 | 78.1 | A disk in the volume layout provides extents to more than one plex. |
| 0xc0380019 | 78.1 | Dynamic disks are not supported on this system. |
| 0xc038001a | 78.1 | The specified extent is already used by other volumes. |
| 0xc038001b | 78.1 | 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. |
| 0xc038001c | 78.1 | The specified volume extent is not within the public region of the disk. |
| 0xc038001d | 78.1 | The specifed volume extent is not sector aligned. |
| 0xc038001e | 78.1 | The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks). |
| 0xc038001f | 78.1 | The specified extent lengths cannot be used to construct a volume with specified length. |
| 0xc0380020 | 78.1 | The system does not support fault tolerant volumes. |
| 0xc0380021 | 78.1 | The specified interleave length is invalid. |
| 0xc0380022 | 78.1 | There is already a maximum number of registered users. |
| 0xc0380023 | 78.1 | The specified member is already in-sync with the other active members. It does not need to be regenerated. |
| 0xc0380024 | 78.1 | The same member index was specified more than once. |
| 0xc0380025 | 78.1 | The specified member index is greater or equal than the number of members in the volume plex. |
| 0xc0380026 | 78.1 | The specified member is missing. It cannot be regenerated. |
| 0xc0380027 | 78.1 | The specified member is not detached. Cannot replace a member which is not detached. |
| 0xc0380028 | 78.1 | The specified member is already regenerating. |
| 0xc0380029 | 78.1 | All disks belonging to the pack failed. |
| 0xc038002a | 78.1 | There are currently no registered users for notifications. The task number is irrelevant unless there are registered users. |
| 0xc038002b | 78.1 | The specified notification user does not exist. Failed to unregister user for notifications. |
| 0xc038002c | 78.1 | The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications. |
| 0xc038002d | 78.1 | The specified number of members is invalid. |
| 0xc038002e | 78.1 | The specified number of plexes is invalid. |
| 0xc038002f | 78.1 | The specified source and target packs are identical. |
| 0xc0380030 | 78.1 | The specified pack id is invalid. There are no packs with the specified pack id. |
| 0xc0380031 | 78.1 | The specified pack is the invalid pack. The operation cannot complete with the invalid pack. |
| 0xc0380032 | 78.1 | The specified pack name is invalid. |
| 0xc0380033 | 78.1 | The specified pack is offline. |
| 0xc0380034 | 78.1 | The specified pack already has a quorum of healthy disks. |
| 0xc0380035 | 78.1 | The pack does not have a quorum of healthy disks. |
| 0xc0380036 | 78.1 | The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported. |
| 0xc0380037 | 78.1 | Failed to update the disk's partition layout. |
| 0xc0380038 | 78.1 | The specified plex is already in-sync with the other active plexes. It does not need to be regenerated. |
| 0xc0380039 | 78.1 | The same plex index was specified more than once. |
| 0xc038003a | 78.1 | The specified plex index is greater or equal than the number of plexes in the volume. |
| 0xc038003b | 78.1 | The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. |
| 0xc038003c | 78.1 | The specified plex is missing. |
| 0xc038003d | 78.1 | The specified plex is currently regenerating. |
| 0xc038003e | 78.1 | The specified plex type is invalid. |
| 0xc038003f | 78.1 | The operation is only supported on RAID-5 plexes. |
| 0xc0380040 | 78.1 | The operation is only supported on simple plexes. |
| 0xc0380041 | 78.1 | The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set. |
| 0xc0380042 | 78.1 | There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications. |
| 0xc0380043 | 78.1 | There is currently a transaction in process. |
| 0xc0380044 | 78.1 | An unexpected layout change occurred outside of the volume manager. |
| 0xc0380045 | 78.1 | The specified volume contains a missing disk. |
| 0xc0380046 | 78.1 | The specified volume id is invalid. There are no volumes with the specified volume id. |
| 0xc0380047 | 78.1 | The specified volume length is invalid. |
| 0xc0380048 | 78.1 | The specified size for the volume is not a multiple of the sector size. |
| 0xc0380049 | 78.1 | The operation is only supported on mirrored volumes. |
| 0xc038004a | 78.1 | The specified volume does not have a retain partition. |
| 0xc038004b | 78.1 | The specified volume is offline. |
| 0xc038004c | 78.1 | The specified volume already has a retain partition. |
| 0xc038004d | 78.1 | The specified number of extents is invalid. |
| 0xc038004e | 78.1 | All disks participating to the volume must have the same sector size. |
| 0xc038004f | 78.1 | The boot disk experienced failures. |
| 0xc0380050 | 78.1 | The configuration of the pack is offline. |
| 0xc0380051 | 78.1 | The configuration of the pack is online. |
| 0xc0380052 | 78.1 | The specified pack is not the primary pack. |
| 0xc0380053 | 78.1 | All disks failed to be updated with the new content of the log. |
| 0xc0380054 | 78.1 | The specified number of disks in a plex is invalid. |
| 0xc0380055 | 78.1 | The specified number of disks in a plex member is invalid. |
| 0xc0380056 | 78.1 | The operation is not supported on mirrored volumes. |
| 0xc0380057 | 78.1 | The operation is only supported on simple and spanned plexes. |
| 0xc0380058 | 78.1 | The pack has no valid log copies. |
| 0xc0380059 | 78.1 | A primary pack is already present. |
| 0xc038005a | 78.1 | The specified number of disks is invalid. |
| 0xc038005b | 78.1 | The system does not support mirrored volumes. |
| 0xc038005c | 78.1 | The system does not support RAID-5 volumes. |
| 0xc0390002 | 78.1 | Entries enumerated have exceeded the allowed threshold. |
| 0xc03a0001 | 78.1 | The virtual hard disk is corrupted. The virtual hard disk drive footer is missing. |
| 0xc03a0002 | 78.1 | The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum. |
| 0xc03a0003 | 78.1 | The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted. |
| 0xc03a0004 | 78.1 | The system does not recognize the file format of this virtual hard disk. |
| 0xc03a0005 | 78.1 | The version does not support this version of the file format. |
| 0xc03a0006 | 78.1 | The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum. |
| 0xc03a0007 | 78.1 | The system does not support this version of the virtual hard disk.This version of the sparse header is not supported. |
| 0xc03a0008 | 78.1 | The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt. |
| 0xc03a0009 | 78.1 | Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. |
| 0xc03a000a | 78.1 | The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt. |
| 0xc03a000b | 78.1 | The system does not support this version of the virtual hard disk. The block size is invalid. |
| 0xc03a000c | 78.1 | The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. |
| 0xc03a000d | 78.1 | The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk. |
| 0xc03a000e | 78.1 | The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. |
| 0xc03a000f | 78.1 | 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. |
| 0xc03a0010 | 78.1 | Failed to read the metadata of the virtual hard disk. |
| 0xc03a0011 | 78.1 | Failed to write to the metadata of the virtual hard disk. |
| 0xc03a0012 | 78.1 | The size of the virtual hard disk is not valid. |
| 0xc03a0013 | 78.1 | The file size of this virtual hard disk is not valid. |
| 0xc03a0014 | 78.1 | A virtual disk support provider for the specified file was not found. |
| 0xc03a0015 | 78.1 | The specified disk is not a virtual disk. |
| 0xc03a0016 | 78.1 | The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk. |
| 0xc03a0017 | 78.1 | The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. |
| 0xc03a0018 | 78.1 | The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. |
| 0xc03a0019 | 78.1 | The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. |
| 0xc03a001a | 7 | The requested operation could not be completed due to a virtual disk system limitation. Virtual disks are only supported on NTFS volumes and must be both uncompressed and unencrypted. |
| 0xc03a001b | 78.1 | The requested operation cannot be performed on a virtual disk of this type. |
| 0xc03a001c | 78.1 | The requested operation cannot be performed on the virtual disk in its current state. |
| 0xc03a001d | 78.1 | The sector size of the physical disk on which the virtual disk resides is not supported. |
| 0xab | 8.1 | Device's command support detection is in progress. |
| 0xd8 | 8.1 | 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. |
| 0xe1 | 8.1 | Operation did not complete successfully because the file contains a virus or potentially unwanted software. |
| 0xe2 | 8.1 | 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. |
| 0x136 | 8.1 | An invalid exception handler routine has been detected. |
| 0x137 | 8.1 | Duplicate privileges were specified for the token. |
| 0x138 | 8.1 | No ranges for the specified operation were able to be processed. |
| 0x139 | 8.1 | Operation is not allowed on a file system internal file. |
| 0x13a | 8.1 | The physical resources of this disk have been exhausted. |
| 0x13b | 8.1 | The token representing the data is invalid. |
| 0x13c | 8.1 | The device does not support the command feature. |
| 0x13f | 8.1 | The Central Access Policy specified is not defined on the target machine. |
| 0x140 | 8.1 | The Central Access Policy obtained from Active Directory is invalid. |
| 0x141 | 8.1 | The device is unreachable. |
| 0x142 | 8.1 | The target device has insufficient resources to complete the operation. |
| 0x143 | 8.1 | A data integrity checksum error occurred. Data in the file stream is corrupt. |
| 0x144 | 8.1 | An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. |
| 0x146 | 8.1 | Device does not support file-level TRIM. |
| 0x147 | 8.1 | The command specified a data offset that does not align to the device's granularity/alignment. |
| 0x148 | 8.1 | The command specified an invalid field in its parameter list. |
| 0x149 | 8.1 | An operation is currently in progress with the device. |
| 0x14a | 8.1 | An attempt was made to send down the command via an invalid path to the target device. |
| 0x14b | 8.1 | The command specified a number of descriptors that exceeded the maximum supported by the device. |
| 0x14c | 8.1 | Scrub is disabled on the specified file. |
| 0x14d | 8.1 | The storage device does not provide redundancy. |
| 0x14e | 8.1 | An operation is not supported on a resident file. |
| 0x14f | 8.1 | An operation is not supported on a compressed file. |
| 0x150 | 8.1 | An operation is not supported on a directory. |
| 0x151 | 8.1 | The specified copy of the requested data could not be read. |
| 0x152 | 8.1 | The specified data could not be written to any of the copies. |
| 0x153 | 8.1 | One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed. |
| 0x154 | 8.1 | The supplied kernel information version is invalid. |
| 0x155 | 8.1 | The supplied PEP information version is invalid. |
| 0x156 | 8.1 | This object is not externally backed by any provider. |
| 0x157 | 8.1 | The external backing provider is not recognized. |
| 0x1e3 | 8.1 | The request failed due to a fatal device hardware error. |
| 0x287 | 8.1 | The driver was not loaded because it failed its initialization call. |
| 0x291 | 8.1 | The password provided is too long to meet the policy of your user account. Please choose a shorter password. |
| 0x318 | 8.1 | The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired. |
| 0x319 | 8.1 | The volume repair was not successful. |
| 0x31a | 8.1 | One of the volume corruption logs is full. Further corruptions that may be detected won't be logged. |
| 0x31b | 8.1 | One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. |
| 0x31c | 8.1 | One of the volume corruption logs is unavailable for being operated on. |
| 0x31d | 8.1 | One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. |
| 0x31e | 8.1 | One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. |
| 0x31f | 8.1 | 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. |
| 0x326 | 8.1 | Access to the specified file handle has been revoked. |
| 0x327 | 8.1 | {Image Relocated} 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. |
| 0x328 | 8.1 | The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. |
| 0x4f1 | 8.1 | The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0x52a | 8.1 | This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon. |
| 0x52e | 8.1 | The user name or password is incorrect. |
| 0x52f | 8.1 | 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. |
| 0x530 | 8.1 | Your account has time restrictions that keep you from signing in right now. |
| 0x531 | 8.1 | This user isn't allowed to sign in to this computer. |
| 0x532 | 8.1 | The password for this account has expired. |
| 0x533 | 8.1 | This user can't sign in because this account is currently disabled. |
| 0x574 | 8.1 | The target account name is incorrect. |
| 0x5bf | 8.1 | Unable to finish the requested operation because the specified process is not a GUI process. |
| 0x676 | 8.1 | The app that you are trying to run is not supported on this version of Windows. |
| 0x677 | 8.1 | The operation was blocked as the process prohibits dynamic code generation. |
| 0x773 | 8.1 | The user's password must be changed before signing in. |
| 0x78f | 8.1 | The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer. |
| 0x791 | 8.1 | Authentication failed because NTLM authentication has been disabled. |
| 0x792 | 8.1 | Logon Failure: EAS policy requires that the user change their password before this operation can be performed. |
| 0xbcd | 8.1 | The printer driver does not contain a valid manifest, or contains too many manifests. |
| 0xbce | 8.1 | The specified printer cannot be shared. |
| 0xbea | 8.1 | The operation was paused. |
| 0xfe2 | 8.1 | Communication with one or more computers will be temporarily blocked due to recent errors. |
| 0x109a | 8.1 | This operation is only valid in the context of an app container. |
| 0x109b | 8.1 | This application can only run in the context of an app container. |
| 0x109c | 8.1 | This functionality is not supported in the context of an app container. |
| 0x109d | 8.1 | The length of the SID supplied is not a valid length for app container SIDs. |
| 0x1130 | 8.1 | Fast Cache data not found. |
| 0x1131 | 8.1 | Fast Cache data expired. |
| 0x1132 | 8.1 | Fast Cache data corrupt. |
| 0x1133 | 8.1 | Fast Cache data has exceeded its max size and cannot be updated. |
| 0x1134 | 8.1 | Fast Cache has been ReArmed and requires a reboot until it can be updated. |
| 0x1144 | 8.1 | Secure Boot detected that rollback of protected data has been attempted. |
| 0x1145 | 8.1 | The value is protected by Secure Boot policy and cannot be modified or deleted. |
| 0x1146 | 8.1 | The Secure Boot policy is invalid. |
| 0x1147 | 8.1 | A new Secure Boot policy did not contain the current publisher on its update list. |
| 0x1148 | 8.1 | The Secure Boot policy is either not signed or is signed by a non-trusted signer. |
| 0x1149 | 8.1 | Secure Boot is not enabled on this machine. |
| 0x114a | 8.1 | Secure Boot requires that certain files and drivers are not replaced by other files or drivers. |
| 0x1158 | 8.1 | The copy offload read operation is not supported by a filter. |
| 0x1159 | 8.1 | The copy offload write operation is not supported by a filter. |
| 0x115a | 8.1 | The copy offload read operation is not supported for the file. |
| 0x115b | 8.1 | The copy offload write operation is not supported for the file. |
| 0x13cc | 8.1 | This operation cannot currently be performed on the cluster group containing the quorum resource. |
| 0x13e2 | 8.1 | This operation is not supported on a cluster without an Administrator Access Point. |
| 0x1741 | 8.1 | A resource vetoed a move between two nodes because they are incompatible. |
| 0x1742 | 8.1 | 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. |
| 0x1743 | 8.1 | The resource vetoed the call. |
| 0x1744 | 8.1 | Resource could not start or run because it could not reserve sufficient system resources. |
| 0x1745 | 8.1 | A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation. |
| 0x1746 | 8.1 | A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation. |
| 0x1747 | 8.1 | The requested operation can not be completed because the group is queued for an operation. |
| 0x1748 | 8.1 | The requested operation can not be completed because a resource has locked status. |
| 0x1749 | 8.1 | The resource cannot move to another node because a cluster shared volume vetoed the operation. |
| 0x174a | 8.1 | A node drain is already in progress. |
| 0x174b | 8.1 | Clustered storage is not connected to the node. |
| 0x174c | 8.1 | 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. |
| 0x174d | 8.1 | The resource must be part of the Available Storage group to complete this action. |
| 0x174e | 8.1 | CSVFS failed operation as volume is in redirected mode. |
| 0x174f | 8.1 | CSVFS failed operation as volume is not in redirected mode. |
| 0x1750 | 8.1 | Cluster properties cannot be returned at this time. |
| 0x1751 | 8.1 | The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes. |
| 0x1752 | 8.1 | The operation cannot be completed because the resource is in maintenance mode. |
| 0x1753 | 8.1 | The operation cannot be completed because of cluster affinity conflicts |
| 0x1754 | 8.1 | The operation cannot be completed because the resource is a replica virtual machine. |
| 0x2047 | 8.1 | 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. |
| 0x21a8 | 8.1 | 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. |
| 0x21c0 | 8.1 | The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller. |
| 0x21c1 | 8.1 | The functional level of the AD LDS configuration set cannot be lowered to the requested value. |
| 0x21c2 | 8.1 | The functional level of the domain (or forest) cannot be lowered to the requested value. |
| 0x21c3 | 8.1 | 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. |
| 0x21c4 | 8.1 | 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. |
| 0x21c5 | 8.1 | 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. |
| 0x21c6 | 8.1 | 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. |
| 0x21c7 | 8.1 | The operation failed because SPN value provided for addition/modification is not unique forest-wide. |
| 0x21c8 | 8.1 | The operation failed because UPN value provided for addition/modification is not unique forest-wide. |
| 0x238d | 8.1 | Only the DNS server acting as the key master for the zone may perform this operation. |
| 0x238e | 8.1 | This operation is not allowed on a zone that is signed or has signing keys. |
| 0x238f | 8.1 | NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC. |
| 0x2390 | 8.1 | The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK). |
| 0x2391 | 8.1 | The specified algorithm is not supported. |
| 0x2392 | 8.1 | The specified key size is not supported. |
| 0x2393 | 8.1 | One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved. |
| 0x2394 | 8.1 | The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved. |
| 0x2395 | 8.1 | An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved. |
| 0x2396 | 8.1 | An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved. |
| 0x2397 | 8.1 | The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved. |
| 0x2398 | 8.1 | The specified key service provider cannot be opened by the DNS server. |
| 0x2399 | 8.1 | The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone. |
| 0x239a | 8.1 | The specified rollover period is invalid. |
| 0x239b | 8.1 | The specified initial rollover offset is invalid. |
| 0x239c | 8.1 | The specified signing key is already in process of rolling over keys. |
| 0x239d | 8.1 | The specified signing key does not have a standby key to revoke. |
| 0x239e | 8.1 | This operation is not allowed on a zone signing key (ZSK). |
| 0x239f | 8.1 | This operation is not allowed on an active signing key. |
| 0x23a0 | 8.1 | The specified signing key is already queued for rollover. |
| 0x23a1 | 8.1 | This operation is not allowed on an unsigned zone. |
| 0x23a2 | 8.1 | This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role. |
| 0x23a3 | 8.1 | The specified signature validity period is invalid. |
| 0x23a4 | 8.1 | The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone. |
| 0x23a5 | 8.1 | This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server. |
| 0x23a6 | 8.1 | This operation could not be completed because the XML stream received is empty or syntactically invalid. |
| 0x23a7 | 8.1 | This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days. |
| 0x23a8 | 8.1 | The specified signing key is not waiting for parental DS update. |
| 0x23a9 | 8.1 | Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again. |
| 0x23aa | 8.1 | NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3. |
| 0x2522 | 8.1 | DNS query request is pending. |
| 0x2595 | 8.1 | The operation cannot be performed because this zone is shut down. |
| 0x2596 | 8.1 | This operation cannot be performed because the zone is currently being signed. Please try again later. |
| 0x26b2 | 8.1 | The operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later. |
| 0x26df | 8.1 | The scope already exists for the zone. |
| 0x26e0 | 8.1 | The scope does not exist for the zone. |
| 0x26e1 | 8.1 | The scope is the same as the default zone scope. |
| 0x26e2 | 8.1 | The scope name contains invalid characters. |
| 0x26e3 | 8.1 | Operation not allowed when the zone has scopes. |
| 0x26e4 | 8.1 | Failed to load zone scope. |
| 0x26e5 | 8.1 | Failed to write data file for DNS zone scope. Please verify the file exists and is writable. |
| 0x26e6 | 8.1 | The scope name contains invalid characters. |
| 0x26e7 | 8.1 | The scope does not exist. |
| 0x26e8 | 8.1 | The scope is the same as the default scope. |
| 0x26e9 | 8.1 | The operation is invalid on the scope. |
| 0x26ea | 8.1 | The scope is locked. |
| 0x26eb | 8.1 | The scope already exists. |
| 0x3621 | 8.1 | 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. |
| 0x3624 | 8.1 | 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. |
| 0x3636 | 8.1 | Temporary state created to perform reinitialization. This is not a real failure. |
| 0x364a | 8.1 | NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel. |
| 0x364b | 8.1 | Error in assigning inner IP address to initiator in tunnel mode. |
| 0x3abd | 8.1 | 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. |
| 0x3b06 | 8.1 | A resource does not have default or neutral value. |
| 0x3b07 | 8.1 | Invalid PRI config file. |
| 0x3b08 | 8.1 | Invalid file type. |
| 0x3b09 | 8.1 | Unknown qualifier. |
| 0x3b0a | 8.1 | Invalid qualifier value. |
| 0x3b0b | 8.1 | No Candidate found. |
| 0x3b0c | 8.1 | The ResourceMap or NamedResource has an item that does not have default or neutral resource.. |
| 0x3b0d | 8.1 | Invalid ResourceCandidate type. |
| 0x3b0e | 8.1 | Duplicate Resource Map. |
| 0x3b0f | 8.1 | Duplicate Entry. |
| 0x3b10 | 8.1 | Invalid Resource Identifier. |
| 0x3b11 | 8.1 | Filepath too long. |
| 0x3b12 | 8.1 | Unsupported directory type. |
| 0x3b16 | 8.1 | Invalid PRI File. |
| 0x3b17 | 8.1 | NamedResource Not Found. |
| 0x3b1f | 8.1 | ResourceMap Not Found. |
| 0x3b20 | 8.1 | Unsupported MRT profile type. |
| 0x3b21 | 8.1 | Invalid qualifier operator. |
| 0x3b22 | 8.1 | Unable to determine qualifier value or qualifier value has not been set. |
| 0x3b23 | 8.1 | Automerge is enabled in the PRI file. |
| 0x3b24 | 8.1 | Too many resources defined for package. |
| 0x3b25 | 8.1 | Resource File can not be used for merge operation. |
| 0x3b26 | 8.1 | Load/UnloadPriFiles cannot be used with resource packages. |
| 0x3b27 | 8.1 | Resource Contexts may not be created on threads that do not have a CoreWindow. |
| 0x3b28 | 8.1 | The singleton Resource Manager with different profile is already created. |
| 0x3b29 | 8.1 | The system component cannot operate given API operation |
| 0x3b2a | 8.1 | The resource is a direct reference to a non-default resource candidate. |
| 0x3b2b | 8.1 | Resource Map has been re-generated and the query string is not valid anymore. |
| 0x3bd9 | 8.1 | The secondary interrupt controller instance that manages the specified interrupt is not registered. |
| 0x3bda | 8.1 | The information supplied by the GPIO client driver is invalid. |
| 0x3bdb | 8.1 | The version specified by the GPIO client driver is not supported. |
| 0x3bdc | 8.1 | The registration packet supplied by the GPIO client driver is not valid. |
| 0x3bdd | 8.1 | The requested operation is not suppported for the specified handle. |
| 0x3bde | 8.1 | The requested connect mode conflicts with an existing mode on one or more of the specified pins. |
| 0x3bdf | 8.1 | The interrupt requested to be unmasked is not masked. |
| 0x3c28 | 8.1 | The requested run level switch cannot be completed successfully. |
| 0x3c29 | 8.1 | The service has an invalid run level setting. The run level for a service must not be higher than the run level of its dependent services. |
| 0x3c2a | 8.1 | The requested run level switch cannot be completed successfully since one or more services will not stop or restart within the specified timeout. |
| 0x3c2b | 8.1 | A run level switch agent did not respond within the specified timeout. |
| 0x3c2c | 8.1 | A run level switch is currently in progress. |
| 0x3c2d | 8.1 | One or more services failed to start during the service startup phase of a run level switch. |
| 0x3c8d | 8.1 | The task stop request cannot be completed immediately since task needs more time to shutdown. |
| 0x3cf0 | 8.1 | Package could not be opened. |
| 0x3cf1 | 8.1 | Package was not found. |
| 0x3cf2 | 8.1 | Package data is invalid. |
| 0x3cf3 | 8.1 | Package failed updates, dependency or conflict validation. |
| 0x3cf4 | 8.1 | There is not enough disk space on your computer. Please free up some space and try again. |
| 0x3cf5 | 8.1 | There was a problem downloading your product. |
| 0x3cf6 | 8.1 | Package could not be registered. |
| 0x3cf7 | 8.1 | Package could not be unregistered. |
| 0x3cf8 | 8.1 | User cancelled the install request. |
| 0x3cf9 | 8.1 | Install failed. Please contact your software vendor. |
| 0x3cfa | 8.1 | Removal failed. Please contact your software vendor. |
| 0x3cfb | 8.1 | The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. |
| 0x3cfc | 8.1 | The application cannot be started. Try reinstalling the application to fix the problem. |
| 0x3cfd | 8.1 | A Prerequisite for an install could not be satisfied. |
| 0x3cfe | 8.1 | The package repository is corrupted. |
| 0x3cff | 8.1 | To install this application you need either a Windows developer license or a sideloading-enabled system. |
| 0x3d00 | 8.1 | The application cannot be started because it is currently updating. |
| 0x3d01 | 8.1 | The package deployment operation is blocked by policy. Please contact your system administrator. |
| 0x3d02 | 8.1 | The package could not be installed because resources it modifies are currently in use. |
| 0x3d03 | 8.1 | The package could not be recovered because necessary data for recovery have been corrupted. |
| 0x3d04 | 8.1 | The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present. |
| 0x3d05 | 8.1 | An error occurred while deleting the package's previously existing application data. |
| 0x3d06 | 8.1 | The package could not be installed because a higher version of this package is already installed. |
| 0x3d07 | 8.1 | An error in a system binary was detected. Try refreshing the PC to fix the problem. |
| 0x3d08 | 8.1 | A corrupted CLR NGEN binary was detected on the system. |
| 0x3d09 | 8.1 | The operation could not be resumed because necessary data for recovery have been corrupted. |
| 0x3d0a | 8.1 | The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again. |
| 0x3d54 | 8.1 | The process has no package identity. |
| 0x3d55 | 8.1 | The package runtime information is corrupted. |
| 0x3d56 | 8.1 | The package identity is corrupted. |
| 0x3d57 | 8.1 | The process has no application identity. |
| 0x3d58 | 8.1 | One or more AppModel Runtime group policy values could not be read. Please contact your system administrator with the contents of your AppModel Runtime event log. |
| 0x3d59 | 8.1 | One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log. |
| 0x3db8 | 8.1 | Loading the state store failed. |
| 0x3db9 | 8.1 | Retrieving the state version for the application failed. |
| 0x3dba | 8.1 | Setting the state version for the application failed. |
| 0x3dbb | 8.1 | Resetting the structured state of the application failed. |
| 0x3dbc | 8.1 | State Manager failed to open the container. |
| 0x3dbd | 8.1 | State Manager failed to create the container. |
| 0x3dbe | 8.1 | State Manager failed to delete the container. |
| 0x3dbf | 8.1 | State Manager failed to read the setting. |
| 0x3dc0 | 8.1 | State Manager failed to write the setting. |
| 0x3dc1 | 8.1 | State Manager failed to delete the setting. |
| 0x3dc2 | 8.1 | State Manager failed to query the setting. |
| 0x3dc3 | 8.1 | State Manager failed to read the composite setting. |
| 0x3dc4 | 8.1 | State Manager failed to write the composite setting. |
| 0x3dc5 | 8.1 | State Manager failed to enumerate the containers. |
| 0x3dc6 | 8.1 | State Manager failed to enumerate the settings. |
| 0x3dc7 | 8.1 | The size of the state manager composite setting value has exceeded the limit. |
| 0x3dc8 | 8.1 | The size of the state manager setting value has exceeded the limit. |
| 0x3dc9 | 8.1 | The length of the state manager setting name has exceeded the limit. |
| 0x3dca | 8.1 | The length of the state manager container name has exceeded the limit. |
| 0x3de1 | 8.1 | This API cannot be used in the context of the caller's application type. |
| 0x3df5 | 8.1 | This PC does not have a valid license for the application or product. |
| 0x3df6 | 8.1 | The authenticated user does not have a valid license for the application or product. |
| 0x3df7 | 8.1 | The commerce transaction associated with this license is still pending verification. |
| 0x3df8 | 8.1 | The license has been revoked for this user. |
| 0x40252 | 8.1 | TabletPC inking error code. String was truncated |
| 0x40253 | 8.1 | TabletPC inking error code. Recognition or training was interrupted |
| 0x40254 | 8.1 | TabletPC inking error code. No personalization update to the recognizer because no training data found |
| 0x4131b | 8.1 | The task is registered, but not all specified triggers will start the task, check task scheduler event log for detailed information. |
| 0x90364 | 8.1 | The returned buffer is only a fragment of the message. More fragments need to be returned. |
| 0x90366 | 8.1 | The function completed successfully, but must be called again to complete the context. Early start can be used. |
| 0x1b0000 | 8.1 | Debugger was attached. |
| 0x1b0001 | 8.1 | Report was uploaded. |
| 0x1b0002 | 8.1 | Report was queued. |
| 0x1b0003 | 8.1 | Reporting was disabled. |
| 0x1b0004 | 8.1 | Reporting was temporarily suspended. |
| 0x1b0005 | 8.1 | Report was not queued to queueing being disabled. |
| 0x1b0006 | 8.1 | Report was uploaded, but not archived due to archiving being disabled. |
| 0x1b0007 | 8.1 | Reporting was successfully spun off as an asynchronous operation. |
| 0x1b0008 | 8.1 | The assertion was handled. |
| 0x1b0009 | 8.1 | The assertion was handled and added to a permanent ignore list. |
| 0x1b000a | 8.1 | The assertion was resumed as unhandled. |
| 0x1b000b | 8.1 | Report was throttled. |
| 0x27000d | 8.1 | A certificate is already present in the cert store. |
| 0x270258 | 8.1 | The Store was launched instead of the specified app because the app's package was in an invalid state. |
| 0x270259 | 8.1 | This app failed to launch, but the error was handled with a dialog. |
| 0x630001 | 8.1 | The graph data was created. |
| 0x630002 | 8.1 | There is not more event data. |
| 0x630005 | 8.1 | No connectivity. |
| 0x630006 | 8.1 | Already a member. |
| 0x632000 | 8.1 | The graph is already connect. |
| 0x636000 | 8.1 | The subscription already exists. |
| 0xe70001 | 8.1 | The storage pool was deleted by the driver. The object cache should be updated. |
| 0x87a0001 | 8.1 | The Present operation was invisible to the user. |
| 0x87a0002 | 8.1 | The Present operation was partially invisible to the user. |
| 0x87a0004 | 8.1 | The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager. |
| 0x87a0005 | 8.1 | The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del). |
| 0x87a0006 | 8.1 | The Present operation was not visible because the target monitor was being used for some other purpose. |
| 0x87a0007 | 8.1 | The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation. |
| 0x87a0008 | 8.1 | The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time. |
| 0x87a0009 | 8.1 | The swapchain has become unoccluded. |
| 0x87a000a | 8.1 | 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 |
| 0x40262201 | 8.1 | Skip preparation of allocations referenced by the DMA buffer. |
| 0x8000000b | 8.1 | The operation attempted to access data outside the valid range |
| 0x8000000c | 8.1 | A concurrent or interleaved operation changed the state of the object, invalidating this operation. |
| 0x8000000d | 8.1 | An illegal state change was requested. |
| 0x8000000e | 8.1 | A method was called at an unexpected time. |
| 0x8000000f | 8.1 | Typename or Namespace was not found in metadata file. |
| 0x80000010 | 8.1 | Name is an existing namespace rather than a typename. |
| 0x80000011 | 8.1 | Typename has an invalid format. |
| 0x80000012 | 8.1 | Metadata file is invalid or corrupted. |
| 0x80000013 | 8.1 | The object has been closed. |
| 0x80000014 | 8.1 | Only one thread may access the object during a write operation. |
| 0x80000015 | 8.1 | Operation is prohibited during change notification. |
| 0x80000016 | 8.1 | The text associated with this error code could not be found. |
| 0x80000017 | 8.1 | String not null terminated. |
| 0x80000018 | 8.1 | A delegate was assigned when not allowed. |
| 0x80000019 | 8.1 | An async operation was not properly started. |
| 0x8000001a | 8.1 | The application is exiting and cannot service this request |
| 0x8000001b | 8.1 | The application view is exiting and cannot service this request |
| 0x8000001c | 8.1 | The object must support the IAgileObject interface |
| 0x8000001d | 8.1 | Activating a single-threaded class from MTA is not supported |
| 0x8000001e | 8.1 | The object has been committed. |
| 0x8000001f | 8.1 | 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. |
| 0x80004034 | 8.1 | The caller failed to revoke a per-apartment registration before apartment shutdown. |
| 0x80004035 | 8.1 | The object has been rundown by the stub manager while there are external clients. |
| 0x80040103 | 8.1 | A drag operation is already in progress |
| 0x80040212 | 8.1 | TabletPC inking error code. No default tablet |
| 0x80040219 | 8.1 | TabletPC inking error code. An invalid input rectangle was specified |
| 0x8004021b | 8.1 | TabletPC inking error code. Unknown property specified |
| 0x80040222 | 8.1 | TabletPC inking error code. The stroke object was deleted |
| 0x80040223 | 8.1 | TabletPC inking error code. Initialization failure |
| 0x80040232 | 8.1 | TabletPC inking error code. The data required for the operation was not supplied |
| 0x80040233 | 8.1 | TabletPC inking error code. Invalid packet description |
| 0x80040235 | 8.1 | TabletPC inking error code. There are no handwriting recognizers registered |
| 0x80040236 | 8.1 | TabletPC inking error code. User does not have the necessary rights to read recognizer information |
| 0x80040237 | 8.1 | TabletPC inking error code. API calls were made in an incorrect order |
| 0x80040238 | 8.1 | TabletPC inking error code. Queue is full |
| 0x80040239 | 8.1 | TabletPC inking error code. RtpEnabled called multiple times |
| 0x8004023a | 8.1 | TabletPC inking error code. A recognizer returned invalid data |
| 0x80040241 | 8.1 | TabletPC inking error code. The property was not found, or supported by the recognizer |
| 0x80041329 | 8.1 | The combination of properties that task is using is not compatible with the scheduling engine. |
| 0x80041330 | 8.1 | The task definition uses a deprecated feature. |
| 0x80072ee1 | 8.1 | No more Internet handles can be allocated |
| 0x80072ee2 | 8.1 | The operation timed out |
| 0x80072ee3 | 8.1 | The server returned extended information |
| 0x80072ee4 | 8.1 | An internal error occurred in the Microsoft Internet extensions |
| 0x80072ee5 | 8.1 | The URL is invalid |
| 0x80072ee6 | 8.1 | The URL does not use a recognized protocol |
| 0x80072ee7 | 8.1 | The server name or address could not be resolved |
| 0x80072ee8 | 8.1 | A protocol with the required capabilities was not found |
| 0x80072ee9 | 8.1 | The option is invalid |
| 0x80072eea | 8.1 | The length is incorrect for the option type |
| 0x80072eeb | 8.1 | The option value cannot be set |
| 0x80072eec | 8.1 | Microsoft Internet Extension support has been shut down |
| 0x80072eed | 8.1 | The user name was not allowed |
| 0x80072eee | 8.1 | The password was not allowed |
| 0x80072eef | 8.1 | The login request was denied |
| 0x80072ef0 | 8.1 | The requested operation is invalid |
| 0x80072ef1 | 8.1 | The operation has been canceled |
| 0x80072ef2 | 8.1 | The supplied handle is the wrong type for the requested operation |
| 0x80072ef3 | 8.1 | The handle is in the wrong state for the requested operation |
| 0x80072ef4 | 8.1 | The request cannot be made on a Proxy session |
| 0x80072ef5 | 8.1 | The registry value could not be found |
| 0x80072ef6 | 8.1 | The registry parameter is incorrect |
| 0x80072ef7 | 8.1 | Direct Internet access is not available |
| 0x80072ef8 | 8.1 | No context value was supplied |
| 0x80072ef9 | 8.1 | No status callback was supplied |
| 0x80072efa | 8.1 | There are outstanding requests |
| 0x80072efb | 8.1 | The information format is incorrect |
| 0x80072efc | 8.1 | The requested item could not be found |
| 0x80072efd | 8.1 | A connection with the server could not be established |
| 0x80072efe | 8.1 | The connection with the server was terminated abnormally |
| 0x80072eff | 8.1 | The connection with the server was reset |
| 0x80072f00 | 8.1 | The action must be retried |
| 0x80072f01 | 8.1 | The proxy request is invalid |
| 0x80072f02 | 8.1 | User interaction is required to complete the operation |
| 0x80072f04 | 8.1 | The handle already exists |
| 0x80072f05 | 8.1 | The date in the certificate is invalid or has expired |
| 0x80072f06 | 8.1 | The host name in the certificate is invalid or does not match |
| 0x80072f07 | 8.1 | A redirect request will change a non-secure to a secure connection |
| 0x80072f08 | 8.1 | A redirect request will change a secure to a non-secure connection |
| 0x80072f09 | 8.1 | Mixed secure and non-secure connections |
| 0x80072f0a | 8.1 | Changing to non-secure post |
| 0x80072f0b | 8.1 | Data is being posted on a non-secure connection |
| 0x80072f0c | 8.1 | A certificate is required to complete client authentication |
| 0x80072f0d | 8.1 | The certificate authority is invalid or incorrect |
| 0x80072f0e | 8.1 | Client authentication has not been correctly installed |
| 0x80072f0f | 8.1 | An error has occurred in a Wininet asynchronous thread. You may need to restart |
| 0x80072f10 | 8.1 | The protocol scheme has changed during a redirect operaiton |
| 0x80072f11 | 8.1 | There are operations awaiting retry |
| 0x80072f12 | 8.1 | The operation must be retried |
| 0x80072f13 | 8.1 | There are no new cache containers |
| 0x80072f14 | 8.1 | A security zone check indicates the operation must be retried |
| 0x80072f17 | 8.1 | The SSL certificate contains errors. |
| 0x80072f19 | 8.1 | It was not possible to connect to the revocation server or a definitive response could not be obtained. |
| 0x80072f76 | 8.1 | The requested header was not found |
| 0x80072f77 | 8.1 | The server does not support the requested protocol level |
| 0x80072f78 | 8.1 | The server returned an invalid or unrecognized response |
| 0x80072f79 | 8.1 | The supplied HTTP header is invalid |
| 0x80072f7a | 8.1 | The request for a HTTP header is invalid |
| 0x80072f7b | 8.1 | The HTTP header already exists |
| 0x80072f7c | 8.1 | The HTTP redirect request failed |
| 0x80072f7d | 8.1 | An error occurred in the secure channel support |
| 0x80072f7e | 8.1 | The file could not be written to the cache |
| 0x80072f7f | 8.1 | The TCP/IP protocol is not installed properly |
| 0x80072f80 | 8.1 | The HTTP request was not redirected |
| 0x80072f81 | 8.1 | A cookie from the server must be confirmed by the user |
| 0x80072f82 | 8.1 | A cookie from the server has been declined acceptance |
| 0x80072f83 | 8.1 | The computer is disconnected from the network |
| 0x80072f84 | 8.1 | The server is unreachable |
| 0x80072f85 | 8.1 | The proxy server is unreachable |
| 0x80072f86 | 8.1 | The proxy auto-configuration script is in error |
| 0x80072f87 | 8.1 | Could not download the proxy auto-configuration script file |
| 0x80072f88 | 8.1 | The HTTP redirect request must be confirmed by the user |
| 0x80072f89 | 8.1 | The supplied certificate is invalid |
| 0x80072f8a | 8.1 | The supplied certificate has been revoked |
| 0x80072f8b | 8.1 | The Dialup failed because file sharing was turned on and a failure was requested if security check was needed |
| 0x80072f8c | 8.1 | Initialization of the WinINet API has not occurred |
| 0x80072f8e | 8.1 | Login failed and the client should display the entity body to the user |
| 0x80072f8f | 8.1 | Content decoding has failed |
| 0x80080200 | 8.1 | Appx packaging API has encountered an internal error. |
| 0x80080201 | 8.1 | The file is not a valid Appx package because its contents are interleaved. |
| 0x80080202 | 8.1 | The file is not a valid Appx package because it contains OPC relationships. |
| 0x80080203 | 8.1 | 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. |
| 0x80080204 | 8.1 | The Appx package's manifest is invalid. |
| 0x80080205 | 8.1 | The Appx package's block map is invalid. |
| 0x80080206 | 8.1 | The Appx package's content cannot be read because it is corrupt. |
| 0x80080207 | 8.1 | The computed hash value of the block does not match the one stored in the block map. |
| 0x80080208 | 8.1 | The requested byte range is over 4GB when translated to byte range of blocks. |
| 0x80080209 | 8.1 | The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data. |
| 0x80080300 | 8.1 | The background task activation is spurious. |
| 0x80090030 | 8.1 | The device that is required by this cryptographic provider is not ready for use. |
| 0x80090031 | 8.1 | The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. |
| 0x80090032 | 8.1 | The validation of the provided data failed the integrity or signature validation. |
| 0x80090033 | 8.1 | Incorrect password. |
| 0x80090034 | 8.1 | Encryption failed. |
| 0x80090035 | 8.1 | The device that is required by this cryptographic provider is not found on this platform. |
| 0x80090350 | 8.1 | The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0x80090352 | 8.1 | An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator. |
| 0x80090365 | 8.1 | Only https scheme is allowed. |
| 0x80090367 | 8.1 | No common application protocol exists between the client and the server. Application protocol negotiation failed. |
| 0x80092024 | 8.1 | 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. |
| 0x8009202d | 8.1 | An object could not be located using the object locator infrastructure with the given name. |
| 0x80094016 | 8.1 | A signature algorithm or public key length does not meet the system's minimum required strength. |
| 0x80094017 | 8.1 | Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation. |
| 0x80094018 | 8.1 | No encryption certificate was specified. |
| 0x80094816 | 8.1 | The certificate template requires renewal with the same public key, but the request uses a different public key. |
| 0x80094817 | 8.1 | The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent. |
| 0x80094818 | 8.1 | The certification authority cannot validate the Attestation Identity Key Id Binding. |
| 0x80094819 | 8.1 | The certification authority cannot validate the private key attestation data. |
| 0x8009481a | 8.1 | The request does not support private key attestation as defined in the certificate template. |
| 0x8009481b | 8.1 | The request public key is not consistent with the private key attestation data. |
| 0x8009481c | 8.1 | The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable. |
| 0x8009481d | 8.1 | The attestation response could not be validated. It is either unexpected or incorrect. |
| 0x8009481e | 8.1 | A valid Request ID was not detected in the request attributes, or an invalid one was submitted. |
| 0x800b0007 | 8.1 | Reading / writing Extensions where Attributes are appropriate, and vice versa. |
| 0x800b0103 | 8.1 | A certificate that can only be used as an end-entity is being used as a CA or vice versa. |
| 0x800c0002 | 8.1 | The URL is invalid. |
| 0x800c0003 | 8.1 | No Internet session has been established. |
| 0x800c0004 | 8.1 | Unable to connect to the target server. |
| 0x800c0005 | 8.1 | The system cannot locate the resource specified. |
| 0x800c0006 | 8.1 | The system cannot locate the object specified. |
| 0x800c0007 | 8.1 | No data is available for the requested resource. |
| 0x800c0008 | 8.1 | The download of the specified resource has failed. |
| 0x800c0009 | 8.1 | Authentication is required to access this resource. |
| 0x800c000a | 8.1 | The server could not recognize the provided mime type. |
| 0x800c000b | 8.1 | The operation was timed out. |
| 0x800c000c | 8.1 | The server did not understand the request, or the request was invalid. |
| 0x800c000d | 8.1 | The specified protocol is unknown. |
| 0x800c000e | 8.1 | A security problem occurred. |
| 0x800c000f | 8.1 | The system could not load the persisted data. |
| 0x800c0010 | 8.1 | Unable to instantiate the object. |
| 0x800c0014 | 8.1 | A redirection problem occurred. |
| 0x800c0015 | 8.1 | The requested resource is a directory, not a file. |
| 0x800c0019 | 8.1 | Security certificate required to access this resource is invalid. |
| 0x8010000c | 8.1 | The operation requires a smart card, but no smart card is currently in the device. |
| 0x8010001d | 8.1 | The Smart Card Resource Manager is not running. |
| 0x8010001e | 8.1 | The Smart Card Resource Manager has shut down. |
| 0x80100028 | 8.1 | The smart card does not have enough memory to store the information. |
| 0x80100031 | 8.1 | The Smart Card Resource Manager is too busy to complete this operation. |
| 0x80190001 | 8.1 | Unexpected HTTP status code. |
| 0x80190003 | 8.1 | Unexpected redirection status code (3xx). |
| 0x80190004 | 8.1 | Unexpected client error status code (4xx). |
| 0x80190005 | 8.1 | Unexpected server error status code (5xx). |
| 0x8019012c | 8.1 | Multiple choices (300). |
| 0x8019012d | 8.1 | Moved permanently (301). |
| 0x8019012e | 8.1 | Found (302). |
| 0x8019012f | 8.1 | See Other (303). |
| 0x80190130 | 8.1 | Not modified (304). |
| 0x80190131 | 8.1 | Use proxy (305). |
| 0x80190133 | 8.1 | Temporary redirect (307). |
| 0x80190190 | 8.1 | Bad request (400). |
| 0x80190191 | 8.1 | Unauthorized (401). |
| 0x80190192 | 8.1 | Payment required (402). |
| 0x80190193 | 8.1 | Forbidden (403). |
| 0x80190194 | 8.1 | Not found (404). |
| 0x80190195 | 8.1 | Method not allowed (405). |
| 0x80190196 | 8.1 | Not acceptable (406). |
| 0x80190197 | 8.1 | Proxy authentication required (407). |
| 0x80190198 | 8.1 | Request timeout (408). |
| 0x80190199 | 8.1 | Conflict (409). |
| 0x8019019a | 8.1 | Gone (410). |
| 0x8019019b | 8.1 | Length required (411). |
| 0x8019019c | 8.1 | Precondition failed (412). |
| 0x8019019d | 8.1 | Request entity too large (413). |
| 0x8019019e | 8.1 | Request-URI too long (414). |
| 0x8019019f | 8.1 | Unsupported media type (415). |
| 0x801901a0 | 8.1 | Requested range not satisfiable (416). |
| 0x801901a1 | 8.1 | Expectation failed (417). |
| 0x801901f4 | 8.1 | Internal server error (500). |
| 0x801901f5 | 8.1 | Not implemented (501). |
| 0x801901f6 | 8.1 | Bad gateway (502). |
| 0x801901f7 | 8.1 | Service unavailable (503). |
| 0x801901f8 | 8.1 | Gateway timeout (504). |
| 0x801901f9 | 8.1 | Version not supported (505). |
| 0x801b8000 | 8.1 | Crash reporting failed. |
| 0x801b8001 | 8.1 | Report aborted due to user cancelation. |
| 0x801b8002 | 8.1 | Report aborted due to network failure. |
| 0x801b8003 | 8.1 | Report not initialized. |
| 0x801b8004 | 8.1 | Reporting is already in progress for the specified process. |
| 0x801b8005 | 8.1 | Dump not generated due to a throttle. |
| 0x801f0023 | 8.1 | The filesystem database resource is in use. Registration cannot complete at this time. |
| 0x80261001 | 8.1 | Monitor descriptor could not be obtained. |
| 0x80261002 | 8.1 | Format of the obtained monitor descriptor is not supported by this release. |
| 0x80263007 | 8.1 | {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. |
| 0x80270001 | 8.1 | The NAP SoH packet is invalid. |
| 0x80270002 | 8.1 | An SoH was missing from the NAP packet. |
| 0x80270003 | 8.1 | The entity ID conflicts with an already registered id. |
| 0x80270004 | 8.1 | No cached SoH is present. |
| 0x80270005 | 8.1 | The entity is still bound to the NAP system. |
| 0x80270006 | 8.1 | The entity is not registered with the NAP system. |
| 0x80270007 | 8.1 | The entity is not initialized with the NAP system. |
| 0x80270008 | 8.1 | The correlation id in the SoH-Request and SoH-Response do not match up. |
| 0x80270009 | 8.1 | Completion was indicated on a request that is not currently pending. |
| 0x8027000a | 8.1 | The NAP component's id was not found. |
| 0x8027000b | 8.1 | The maximum size of the connection is too small for an SoH packet. |
| 0x8027000c | 8.1 | The NapAgent service is not running. |
| 0x8027000e | 8.1 | The entity is disabled with the NapAgent service. |
| 0x8027000f | 8.1 | Group Policy is not configured. |
| 0x80270010 | 8.1 | Too many simultaneous calls. |
| 0x80270011 | 8.1 | SHV configuration already existed. |
| 0x80270012 | 8.1 | SHV configuration is not found. |
| 0x80270013 | 8.1 | SHV timed out on the request. |
| 0x80270220 | 8.1 | The maximum number of items for the access list has been reached. An item must be removed before another item is added. |
| 0x80270222 | 8.1 | Cannot access Homegroup. Homegroup may not be set up or may have encountered an error. |
| 0x80270250 | 8.1 | This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again. |
| 0x80270251 | 8.1 | This app can't be activated from an elevated context. |
| 0x80270252 | 8.1 | This app can't be activated when UAC is disabled. |
| 0x80270253 | 8.1 | This app can't be activated by the Built-in Administrator. |
| 0x80270254 | 8.1 | This app does not support the contract specified or is not installed. |
| 0x80270255 | 8.1 | This app has mulitple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous. |
| 0x80270256 | 8.1 | This app's package family has more than one package installed. This is not supported. |
| 0x80270257 | 8.1 | The app manager is required to activate applications, but is not running. |
| 0x8027025a | 8.1 | The app didn't start in the required time. |
| 0x8027025b | 8.1 | The app didn't start. |
| 0x8027025c | 8.1 | This app failed to launch because of an issue with its license. Please try again in a moment. |
| 0x8027025d | 8.1 | This app failed to launch because its trial license has expired. |
| 0x80270260 | 8.1 | Please choose a folder on a drive that's formatted with the NTFS file system. |
| 0x80270261 | 8.1 | This location is already being used. Please choose a different location. |
| 0x80270262 | 8.1 | This location cannot be indexed. Please choose a different location. |
| 0x80270263 | 8.1 | Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later. |
| 0x80270264 | 8.1 | Sorry, the action couldn't be completed. |
| 0x80270265 | 8.1 | This content can only be moved to a folder. To move the content to this drive, please choose or create a folder. |
| 0x8028001c | 8.1 | 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. |
| 0x80284001 | 8.1 | An internal error has occurred within the Trusted Platform Module support program. |
| 0x80284012 | 8.1 | The caller does not have the appropriate rights to perform the requested operation. |
| 0x80284013 | 8.1 | 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.) |
| 0x80284014 | 8.1 | The Physical Presence Interface of this firmware does not support the requested method. |
| 0x80284015 | 8.1 | The requested TPM OwnerAuth value was not found. |
| 0x80284016 | 8.1 | 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. |
| 0x8029011e | 8.1 | The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance. |
| 0x80290304 | 8.1 | 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. |
| 0x80290400 | 8.1 | This is an error mask to convert Platform Crypto Provider errors to win errors. |
| 0x80290401 | 8.1 | The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. |
| 0x80290402 | 8.1 | The handle provided to the Platform Crypto Provider is invalid. |
| 0x80290403 | 8.1 | A parameter provided to the Platform Crypto Provider is invalid. |
| 0x80290404 | 8.1 | A provided flag to the Platform Crypto Provider is not supported. |
| 0x80290405 | 8.1 | The requested operation is not supported by this Platform Crypto Provider. |
| 0x80290406 | 8.1 | The buffer is too small to contain all data. No information has been written to the buffer. |
| 0x80290407 | 8.1 | An unexpected internal error has occurred in the Platform Crypto Provider. |
| 0x80290408 | 8.1 | The authorization to use a provider object has failed. |
| 0x80290409 | 8.1 | The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. |
| 0x8029040a | 8.1 | The referenced policy was not found. |
| 0x8029040b | 8.1 | The referenced profile was not found. |
| 0x8029040c | 8.1 | The validation was not succesful. |
| 0x802a010b | 8.1 | The passed dimension is invalid or does not match the object's dimension. |
| 0x802a010c | 8.1 | The added primitive begins at or beyond the duration of the interpolator. |
| 0x802a0201 | 8.1 | The operation cannot be completed because the window is being closed. |
| 0x80310041 | 8.1 | 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. |
| 0x80310053 | 8.1 | BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments. |
| 0x8031005a | 8.1 | This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system. |
| 0x80310084 | 8.1 | 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. |
| 0x8031009c | 8.1 | The feature is only supported on EFI systems. |
| 0x8031009d | 8.1 | More than one Network Key Protector certificate has been found on the system. |
| 0x8031009e | 8.1 | Removal of the Network Key Protector certificate must be done using the Certificates snap-in. |
| 0x8031009f | 8.1 | An invalid certificate has been found in the Network Key Protector certificate store. |
| 0x803100a0 | 8.1 | This drive isn't protected with a PIN. |
| 0x803100a1 | 8.1 | Please enter the correct current PIN. |
| 0x803100a2 | 8.1 | You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator. |
| 0x803100a3 | 8.1 | BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator. |
| 0x803100a4 | 8.1 | 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: # $ & @ ^ _ ~ . |
| 0x803100a5 | 8.1 | BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. |
| 0x803100a6 | 8.1 | BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. |
| 0x803100a7 | 8.1 | The required authentication key length is not supported by the drive. |
| 0x803100a8 | 8.1 | This drive isn't protected with a password. |
| 0x803100a9 | 8.1 | Please enter the correct current password. |
| 0x803100aa | 8.1 | The password cannot exceed 256 characters. |
| 0x803100ab | 8.1 | A password key protector cannot be added because a TPM protector exists on the drive. |
| 0x803100ac | 8.1 | A TPM key protector cannot be added because a password protector exists on the drive. |
| 0x803100ad | 8.1 | This command can only be performed from the coordinator node for the specified CSV volume. |
| 0x803100ae | 8.1 | This command cannot be performed on a volume when it is part of a cluster. |
| 0x803100af | 8.1 | BitLocker did not revert to using BitLocker software encryption due to group policy configuration. |
| 0x803100b0 | 8.1 | The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use. |
| 0x803100b1 | 8.1 | Group Policy settings do not allow the use of hardware-based encryption. |
| 0x803100b2 | 8.1 | The drive specified does not support hardware-based encryption. |
| 0x803100b3 | 8.1 | BitLocker cannot be upgraded during disk encryption or decryption. |
| 0x803100b4 | 8.1 | Discovery Volumes are not supported for volumes using hardware encryption. |
| 0x803100b5 | 8.1 | No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100b6 | 8.1 | No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100b7 | 8.1 | 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. |
| 0x803100b8 | 8.1 | 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. |
| 0x803100b9 | 8.1 | Wipe of free space is not currently taking place. |
| 0x803100ba | 8.1 | BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled. |
| 0x803100bb | 8.1 | BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker. |
| 0x803100bc | 8.1 | Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. |
| 0x803100bd | 8.1 | BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume. |
| 0x803100be | 8.1 | 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. |
| 0x803100bf | 8.1 | This PC's firmware is not capable of supporting hardware encryption. |
| 0x803100c0 | 8.1 | BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator. |
| 0x803100c1 | 8.1 | You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator. |
| 0x803100c2 | 8.1 | BitLocker cannot save the recovery password because the specified Microsoft account is Suspended. |
| 0x803100c3 | 8.1 | BitLocker cannot save the recovery password because the specified Microsoft account is Blocked. |
| 0x803100c4 | 8.1 | This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy. |
| 0x803100c5 | 8.1 | This PC cannot support device encryption because unencrypted fixed data volumes are present. |
| 0x803100c6 | 8.1 | This PC does not meet the hardware requirements to support device encryption. |
| 0x803100c7 | 8.1 | This PC cannot support device encryption because WinRE is not properly configured. |
| 0x803100c8 | 8.1 | 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. |
| 0x803100c9 | 8.1 | This PC is not provisioned to support device encryption. |
| 0x803100ca | 8.1 | Device Lock has been triggered due to too many incorrect password attempts. |
| 0x803100cb | 8.1 | 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. |
| 0x803100cc | 8.1 | Your PIN can only contain numbers from 0 to 9. |
| 0x803100cd | 8.1 | BitLocker cannot use hardware replay protection because no counter is available on your PC. |
| 0x803100ce | 8.1 | Device Lockout state validation failed due to counter mismatch. |
| 0x803100cf | 8.1 | The input buffer is too large. |
| 0x803100d0 | 8.1 | The target of an invocation does not support requested capability. |
| 0x803100d1 | 8.1 | Device encryption is currently blocked by this PC's configuration. |
| 0x803100d2 | 8.1 | This drive has been opted out of device encryption. |
| 0x803100d3 | 8.1 | Device encryption isn't available for this drive. |
| 0x803100d4 | 8.1 | 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. |
| 0x803100d5 | 8.1 | Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator. |
| 0x803100d6 | 8.1 | Device encryption can't be turned off while this drive is being encrypted. Please try again later. |
| 0x803100d7 | 8.1 | This action isn't supported because this drive isn't automatically managed with device encryption. |
| 0x803100d8 | 8.1 | BitLocker can't be suspended on this drive until the next restart. |
| 0x8032003d | 8.1 | A tunnel endpoint configuration is invalid. |
| 0x8032003e | 8.1 | The WFP MAC Layers are not ready. |
| 0x8032003f | 8.1 | A key manager capable of key dictation is already registered |
| 0x80320040 | 8.1 | A key manager dictated invalid keys |
| 0x80320041 | 8.1 | The BFE IPsec Connection Tracking is disabled. |
| 0x80320042 | 8.1 | The DNS name is invalid. |
| 0x80320043 | 8.1 | The engine option is still enabled due to other configuration settings. |
| 0x80320044 | 8.1 | The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
| 0x8034001c | 8.1 | An error occurred while NDIS tried to map the file. |
| 0x80340030 | 8.1 | This operation requires the miniport adapter to be reinitialized. |
| 0x80342002 | 8.1 | The wireless local area network interface is powered down and doesn't support the requested operation. |
| 0x80370001 | 8.1 | 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. |
| 0x803d0021 | 8.1 | Unrecognized error occurred in the Windows Web Services framework. |
| 0x803e0100 | 8.1 | The notification channel has already been closed. |
| 0x803e0101 | 8.1 | The notification channel request did not complete successfully. |
| 0x803e0102 | 8.1 | The application identifier provided is invalid. |
| 0x803e0103 | 8.1 | A notification channel request for the provided application identifier is in progress. |
| 0x803e0104 | 8.1 | The channel identifier is already tied to another application endpoint. |
| 0x803e0105 | 8.1 | The notification platform is unavailable. |
| 0x803e0106 | 8.1 | The notification has already been posted. |
| 0x803e0107 | 8.1 | The notification has already been hidden. |
| 0x803e0108 | 8.1 | The notification cannot be hidden until it has been shown. |
| 0x803e0109 | 8.1 | Cloud notifications have been turned off. |
| 0x803e0110 | 8.1 | The application does not have the cloud notification capability. |
| 0x803e0111 | 8.1 | Settings prevent the notification from being delivered. |
| 0x803e0112 | 8.1 | Application capabilities prevent the notification from being delivered. |
| 0x803e0113 | 8.1 | The application does not have the internet access capability. |
| 0x803e0114 | 8.1 | Settings prevent the notification type from being delivered. |
| 0x803e0115 | 8.1 | The size of the notification content is too large. |
| 0x803e0116 | 8.1 | The size of the notification tag is too large. |
| 0x803e0117 | 8.1 | The notification platform doesn't have appropriate privilege on resources. |
| 0x803e0118 | 8.1 | The notification platform found application is already registered. |
| 0x803e0119 | 8.1 | The application background task does not have the push notification capability. |
| 0x803e011a | 8.1 | The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. |
| 0x803e011b | 8.1 | The notification platform is unable to connect to the cloud notification service. |
| 0x803e011c | 8.1 | The notification platform is unable to initialize a callback for lock screen updates. |
| 0x803e0120 | 8.1 | The size of the developer id for scheduled notification is too large. |
| 0x803e012a | 8.1 | The notification tag is not alphanumeric. |
| 0x803e012b | 8.1 | The notification platform has received invalid HTTP status code other than 2xx for polling. |
| 0x803e0200 | 8.1 | The notification platform has run out of presentation layer sessions. |
| 0x803e0201 | 8.1 | The notification platform rejects image download request due to system in power save mode. |
| 0x803e0202 | 8.1 | The notification platform doesn't have the requested image in its cache. |
| 0x803e0203 | 8.1 | The notification platform cannot complete all of requested image. |
| 0x803e0204 | 8.1 | A cloud image downloaded from the notification platform is invalid. |
| 0x803e0205 | 8.1 | Notification Id provided as filter is matched with what the notification platform maintains. |
| 0x803e0206 | 8.1 | Notification callback interface is already registered. |
| 0x803e0207 | 8.1 | Toast Notification was dropped without being displayed to the user. |
| 0x803e0208 | 8.1 | The notification platform does not have the proper privileges to complete the request. |
| 0x80400000 | 8.1 | Input data cannot be processed in the non-chronological order. |
| 0x80400001 | 8.1 | Requested operation cannot be performed inside the callback or event handler. |
| 0x80400002 | 8.1 | Input cannot be processed because there is ongoing interaction with another pointer type. |
| 0x80400003 | 8.1 | One or more fields in the input packet are invalid. |
| 0x80400004 | 8.1 | 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. |
| 0x80400005 | 8.1 | 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. |
| 0x80400006 | 8.1 | Failed to retrieve information about the input device. |
| 0x80400007 | 8.1 | Coordinate system transformation failed to transform the data. |
| 0x80400008 | 8.1 | The property is not supported or not reported correctly by the input device. |
| 0x80550001 | 8.1 | Windows cannot evaluate this EAS policy since this is not managed by the operating system. |
| 0x80550002 | 8.1 | The system can be made compliant to this EAS policy if certain actions are performed by the user. |
| 0x80550003 | 8.1 | The EAS policy being evaluated cannot be enforced by the system. |
| 0x80550004 | 8.1 | EAS password policies for the user cannot be evaluated as the user has a blank password. |
| 0x80550005 | 8.1 | EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system. |
| 0x80550006 | 8.1 | The user is not allowed to change her password. |
| 0x80550007 | 8.1 | EAS password policies cannot be evaluated as one or more admins have blank passwords. |
| 0x80550008 | 8.1 | One or more admins are not allowed to change their password. |
| 0x80550009 | 8.1 | There are other standard users present who are not allowed to change their password. |
| 0x8055000a | 8.1 | The EAS password policy cannot be enforced by the connected account provider of at least one administrator. |
| 0x8055000b | 8.1 | There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance. |
| 0x8055000c | 8.1 | The EAS password policy cannot be enforced by the connected account provider of the current user. |
| 0x8055000d | 8.1 | The connected account password of the current user needs to be changed for EAS password policy compliance. |
| 0x80630001 | 8.1 | The IPv6 protocol is not installed. |
| 0x80630002 | 8.1 | The compoment has not been initialized. |
| 0x80630003 | 8.1 | The required service canot be started. |
| 0x80630004 | 8.1 | The P2P protocol is not licensed to run on this OS. |
| 0x80630010 | 8.1 | The graph handle is invalid. |
| 0x80630011 | 8.1 | The graph database name has changed. |
| 0x80630012 | 8.1 | A graph with the same ID already exists. |
| 0x80630013 | 8.1 | The graph is not ready. |
| 0x80630014 | 8.1 | The graph is shutting down. |
| 0x80630015 | 8.1 | The graph is still in use. |
| 0x80630016 | 8.1 | The graph database is corrupt. |
| 0x80630017 | 8.1 | Too many attributes have been used. |
| 0x80630103 | 8.1 | The connection can not be found. |
| 0x80630106 | 8.1 | The peer attempted to connect to itself. |
| 0x80630107 | 8.1 | The peer is already listening for connections. |
| 0x80630108 | 8.1 | The node was not found. |
| 0x80630109 | 8.1 | The Connection attempt failed. |
| 0x8063010a | 8.1 | The peer connection could not be authenticated. |
| 0x8063010b | 8.1 | The connection was refused. |
| 0x80630201 | 8.1 | The peer name classifier is too long. |
| 0x80630202 | 8.1 | The maximum number of identities have been created. |
| 0x80630203 | 8.1 | Unable to access a key. |
| 0x80630204 | 8.1 | The group already exists. |
| 0x80630301 | 8.1 | The requested record could not be found. |
| 0x80630302 | 8.1 | Access to the database was denied. |
| 0x80630303 | 8.1 | The Database could not be initialized. |
| 0x80630304 | 8.1 | The record is too big. |
| 0x80630305 | 8.1 | The database already exists. |
| 0x80630306 | 8.1 | The database could not be found. |
| 0x80630401 | 8.1 | The identity could not be found. |
| 0x80630501 | 8.1 | The event handle could not be found. |
| 0x80630601 | 8.1 | Invalid search. |
| 0x80630602 | 8.1 | The search atributes are invalid. |
| 0x80630701 | 8.1 | The invitiation is not trusted. |
| 0x80630703 | 8.1 | The certchain is too long. |
| 0x80630705 | 8.1 | The time period is invalid. |
| 0x80630706 | 8.1 | A circular cert chain was detected. |
| 0x80630801 | 8.1 | The certstore is corrupted. |
| 0x80631001 | 8.1 | The specified PNRP cloud deos not exist. |
| 0x80631005 | 8.1 | The cloud name is ambiguous. |
| 0x80632010 | 8.1 | The record is invlaid. |
| 0x80632020 | 8.1 | Not authorized. |
| 0x80632021 | 8.1 | The password does not meet policy requirements. |
| 0x80632030 | 8.1 | The record validation has been defered. |
| 0x80632040 | 8.1 | The group properies are invalid. |
| 0x80632050 | 8.1 | The peername is invalid. |
| 0x80632060 | 8.1 | The classifier is invalid. |
| 0x80632070 | 8.1 | The friendly name is invalid. |
| 0x80632071 | 8.1 | Invalid role property. |
| 0x80632072 | 8.1 | Invalid classifer property. |
| 0x80632080 | 8.1 | Invlaid record expiration. |
| 0x80632081 | 8.1 | Invlaid credential info. |
| 0x80632082 | 8.1 | Invalid credential. |
| 0x80632083 | 8.1 | Invalid record size. |
| 0x80632090 | 8.1 | Unsupported version. |
| 0x80632091 | 8.1 | The group is not ready. |
| 0x80632092 | 8.1 | The group is still in use. |
| 0x80632093 | 8.1 | The group is invalid. |
| 0x80632094 | 8.1 | No members were found. |
| 0x80632095 | 8.1 | There are no member connections. |
| 0x80632096 | 8.1 | Unable to listen. |
| 0x806320a0 | 8.1 | The identity does not exist. |
| 0x806320a1 | 8.1 | The service is not availible. |
| 0x80634001 | 8.1 | The peername could not be converted to a DNS pnrp name. |
| 0x80634002 | 8.1 | Invalid peer host name. |
| 0x80634003 | 8.1 | No more data could be found. |
| 0x80634005 | 8.1 | The existing peer name is already registered. |
| 0x80636001 | 8.1 | THe contact could not be found. |
| 0x80637000 | 8.1 | The app invite request was cancelled by the user. |
| 0x80637001 | 8.1 | No response of the invite was received. |
| 0x80637003 | 8.1 | User is not signed into serverless presence. |
| 0x80637004 | 8.1 | The user declined the privacy policy prompt. |
| 0x80637005 | 8.1 | A timeout occurred. |
| 0x80637007 | 8.1 | The address is invalid. |
| 0x80637008 | 8.1 | A required firewall exception is disabled. |
| 0x80637009 | 8.1 | The service is blocked by a firewall policy. |
| 0x8063700a | 8.1 | Firewall exceptions are disabled. |
| 0x8063700b | 8.1 | The user declined to enable the firewall exceptions. |
| 0x80650001 | 8.1 | The attribute handle given was not valid on this server. |
| 0x80650002 | 8.1 | The attribute cannot be read. |
| 0x80650003 | 8.1 | The attribute cannot be written. |
| 0x80650004 | 8.1 | The attribute PDU was invalid. |
| 0x80650005 | 8.1 | The attribute requires authentication before it can be read or written. |
| 0x80650006 | 8.1 | Attribute server does not support the request received from the client. |
| 0x80650007 | 8.1 | Offset specified was past the end of the attribute. |
| 0x80650008 | 8.1 | The attribute requires authorization before it can be read or written. |
| 0x80650009 | 8.1 | Too many prepare writes have been queued. |
| 0x8065000a | 8.1 | No attribute found within the given attribute handle range. |
| 0x8065000b | 8.1 | The attribute cannot be read or written using the Read Blob Request. |
| 0x8065000c | 8.1 | The Encryption Key Size used for encrypting this link is insufficient. |
| 0x8065000d | 8.1 | The attribute value length is invalid for the operation. |
| 0x8065000e | 8.1 | The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. |
| 0x8065000f | 8.1 | The attribute requires encryption before it can be read or written. |
| 0x80650010 | 8.1 | The attribute type is not a supported grouping attribute as defined by a higher layer specification. |
| 0x80650011 | 8.1 | Insufficient Resources to complete the request. |
| 0x80651000 | 8.1 | An error that lies in the reserved range has been received. |
| 0x80660001 | 8.1 | PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. |
| 0x80660002 | 8.1 | HD Audio widget encountered an unexpected empty connection list. |
| 0x80660003 | 8.1 | HD Audio widget does not support the connection list parameter. |
| 0x80660004 | 8.1 | No HD Audio subdevices were successfully created. |
| 0x80660005 | 8.1 | An unexpected NULL pointer was encountered in a linked list. |
| 0x80820001 | 8.1 | The bootfile is too small to support persistent snapshots. |
| 0x80830001 | 8.1 | The specified volume does not support storage tiers. |
| 0x80830002 | 8.1 | The Storage Tiers Management service detected that the specified volume is in the process of being dismounted. |
| 0x80830003 | 8.1 | The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid. |
| 0x80830004 | 8.1 | The file identifier specified is not valid on the volume. |
| 0x80830005 | 8.1 | Storage tier operations must be called on the clustering node that owns the metadata volume. |
| 0x80830006 | 8.1 | The Storage Tiers Management service is already optimizing the storage tiers on the specified volume. |
| 0x80830007 | 8.1 | The requested object type cannot be assigned to a storage tier. |
| 0x80860001 | 8.1 | Authentication target is invalid or not configured correctly. |
| 0x80860002 | 8.1 | Your application cannot get the Online Id properties due to the Terms of Use accepted by the user. |
| 0x80860003 | 8.1 | The application requesting authentication tokens is either disabled or incorrectly configured. |
| 0x80860004 | 8.1 | Online Id password must be updated before signin. |
| 0x80860005 | 8.1 | Online Id account properties must be updated before signin. |
| 0x80860006 | 8.1 | To help protect your Online Id account you must signin again. |
| 0x80860007 | 8.1 | Online Id account was locked because there have been too many attempts to sign in. |
| 0x80860008 | 8.1 | Online Id account requires parental consent before proceeding. |
| 0x80860009 | 8.1 | Online Id signin name is not yet verified. Email verification is required before signin. |
| 0x8086000a | 8.1 | We have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account. |
| 0x8086000b | 8.1 | We detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account. |
| 0x8086000c | 8.1 | User interaction is required for authentication. |
| 0x8086000d | 8.1 | User has reached the maximum device associations per user limit. |
| 0x8086000e | 8.1 | Cannot sign out from the application since the user account is connected. |
| 0x8086000f | 8.1 | User authentication is required for this operation. |
| 0x80860010 | 8.1 | We want to make sure this is you. User interaction is required for authentication. |
| 0x80b00001 | 8.1 | Could not create new process from ARM architecture device. |
| 0x80b00002 | 8.1 | Could not attach to the application process from ARM architecture device. |
| 0x80b00003 | 8.1 | Could not connect to dbgsrv server from ARM architecture device. |
| 0x80b00004 | 8.1 | Could not start dbgsrv server from ARM architecture device. |
| 0x80e70003 | 8.1 | The specified resiliency type is not valid. |
| 0x80e70004 | 8.1 | The physical disk's sector size is not supported by the storage pool. |
| 0x80e70006 | 8.1 | The requested redundancy is outside of the supported range of values. |
| 0x80e70007 | 8.1 | The number of data copies requested is outside of the supported range of values. |
| 0x80e70008 | 8.1 | The value for ParityLayout is outside of the supported range of values. |
| 0x80e70009 | 8.1 | The value for interleave length is outside of the supported range of values. |
| 0x80e7000a | 8.1 | The number of columns specified is outside of the supported range of values. |
| 0x80e7000b | 8.1 | There were not enough physical disks to complete the requested operation. |
| 0x83750001 | 8.1 | Unsupported format. |
| 0x83750002 | 8.1 | Invalid XML. |
| 0x83750003 | 8.1 | Missing required element. |
| 0x83750004 | 8.1 | Missing required attribute. |
| 0x83750005 | 8.1 | Unexpected content. |
| 0x83750006 | 8.1 | Resource too large. |
| 0x83750007 | 8.1 | Invalid JSON string. |
| 0x83750008 | 8.1 | Invalid JSON number. |
| 0x83750009 | 8.1 | JSON value not found. |
| 0x83760001 | 8.1 | Invalid operation performed by the protocol. |
| 0x83760002 | 8.1 | Invalid data format for the specific protocol operation. |
| 0x83760003 | 8.1 | Protocol extensions are not supported. |
| 0x83760004 | 8.1 | Subrotocol is not supported. |
| 0x83760005 | 8.1 | Incorrect protocol version. |
| 0x88010001 | 8.1 | 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. |
| 0x88010002 | 8.1 | This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption. |
| 0x88010003 | 8.1 | This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider. |
| 0x88010004 | 8.1 | This computer cannot support device encryption because the requisites for the device lock feature are not configured. |
| 0x88010005 | 8.1 | Protection is enabled on this volume but is not in the active state. |
| 0x88010006 | 8.1 | The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated. |
| 0x88010007 | 8.1 | The operating system drive is not protected by 3rd party drive encryption. |
| 0x88010008 | 8.1 | Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin. |
| 0x88010009 | 8.1 | The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large. |
| 0x8802b001 | 8.1 | The file size is larger than supported by the sync engine. |
| 0x8802b002 | 8.1 | The file cannot be uploaded because it doesn't fit in the user's available service provided storage space. |
| 0x8802b003 | 8.1 | The file name contains invalid characters. |
| 0x8802b004 | 8.1 | The maximum file count has been reached for this folder in the sync engine. |
| 0x8802b005 | 8.1 | The file sync has been delegated to another program and has run into an issue. |
| 0x8802b006 | 8.1 | Sync has been delayed due to a throttling request from the service. |
| 0x8802c002 | 8.1 | We can't seem to find that file. Please try again later. |
| 0x8802c003 | 8.1 | The account you're signed in with doesn't have permission to open this file. |
| 0x8802c004 | 8.1 | There was a problem connecting to the service. Please try again later. |
| 0x8802c005 | 8.1 | Sorry, there was a problem downloading the file. |
| 0x8802c006 | 8.1 | We're having trouble downloading the file right now. Please try again later. |
| 0x8802c007 | 8.1 | We're having trouble downloading the file right now. Please try again later. |
| 0x8802d001 | 8.1 | The sync engine does not have permissions to access a local folder under the sync root. |
| 0x8802d002 | 8.1 | The folder name contains invalid characters. |
| 0x8802d003 | 8.1 | The sync engine is not allowed to run in your current market. |
| 0x8802d004 | 8.1 | All files and folders can't be uploaded because a path of a file or folder is too long. |
| 0x8802d005 | 8.1 | All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit. |
| 0x8802d006 | 8.1 | Updates are needed in order to use the sync engine. |
| 0x8802d007 | 8.1 | The sync engine needs to authenticate with a proxy server. |
| 0x8802d008 | 8.1 | There was a problem setting up the storage services for the account. |
| 0x8802d009 | 8.1 | Files can't be uploaded because there's an unsupported reparse point. |
| 0x8802d00a | 8.1 | The service has blocked your account from accessing the storage service. |
| 0x8802d00b | 8.1 | The action can't be performed right now because this folder is being moved. Please try again later. |
| 0x88790001 | 8.1 | 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. |
| 0x88790002 | 8.1 | The specified file was not found. |
| 0x887a0001 | 8.1 | 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. |
| 0x887a0002 | 8.1 | The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal. |
| 0x887a0003 | 8.1 | The caller did not supply a sufficiently large buffer. |
| 0x887a0004 | 8.1 | The specified device interface or feature level is not supported on this system. |
| 0x887a0005 | 8.1 | The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. |
| 0x887a0006 | 8.1 | The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. |
| 0x887a0007 | 8.1 | 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. |
| 0x887a000a | 8.1 | The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled. |
| 0x887a000b | 8.1 | An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should be considered invalid. |
| 0x887a000c | 8.1 | Fullscreen mode could not be achieved because the specified output was already in use. |
| 0x887a0020 | 8.1 | 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. |
| 0x887a0021 | 8.1 | A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time. |
| 0x887a0022 | 8.1 | A resource is not available at the time of the call, but may become available later. |
| 0x887a0023 | 8.1 | 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. |
| 0x887a0024 | 8.1 | The device has been removed during a remote session because the remote computer ran out of memory. |
| 0x887a0025 | 8.1 | An on-going mode change prevented completion of the call. The call may succeed if attempted later. |
| 0x887a0026 | 8.1 | The keyed mutex was abandoned. |
| 0x887a0027 | 8.1 | The timeout value has elapsed and the resource is not yet available. |
| 0x887a0028 | 8.1 | 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. |
| 0x887a0029 | 8.1 | The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed. |
| 0x887a002a | 8.1 | 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. |
| 0x887a002b | 8.1 | 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. |
| 0x887a002c | 8.1 | The application is trying to create a shared handle using a name that is already associated with some other resource. |
| 0x887a002d | 8.1 | The application requested an operation that depends on an SDK component that is missing or mismatched. |
| 0x887b0001 | 8.1 | The GPU was busy when the operation was requested. |
| 0x887b0002 | 8.1 | The driver has rejected the creation of this resource. |
| 0x887b0003 | 8.1 | The GPU counter was in use by another process or d3d device when application requested access to it. |
| 0x887c0001 | 8.1 | 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. |
| 0x887c0002 | 8.1 | The specified file was not found. |
| 0x887c0003 | 8.1 | 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. |
| 0x887c0004 | 8.1 | The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD. |
| 0x88980001 | 8.1 | MILERR_OBJECTBUSY |
| 0x88980002 | 8.1 | MILERR_INSUFFICIENTBUFFER |
| 0x88980003 | 8.1 | MILERR_WIN32ERROR |
| 0x88980004 | 8.1 | MILERR_SCANNER_FAILED |
| 0x88980005 | 8.1 | MILERR_SCREENACCESSDENIED |
| 0x88980006 | 8.1 | MILERR_DISPLAYSTATEINVALID |
| 0x88980007 | 8.1 | MILERR_NONINVERTIBLEMATRIX |
| 0x88980008 | 8.1 | MILERR_ZEROVECTOR |
| 0x88980009 | 8.1 | MILERR_TERMINATED |
| 0x8898000a | 8.1 | MILERR_BADNUMBER |
| 0x88980080 | 8.1 | An internal error (MIL bug) occurred. On checked builds, an assert would be raised. |
| 0x88980084 | 8.1 | The display format we need to render is not supported by the hardware device. |
| 0x88980085 | 8.1 | A call to this method is invalid. |
| 0x88980086 | 8.1 | Lock attempted on an already locked object. |
| 0x88980087 | 8.1 | Unlock attempted on an unlocked object. |
| 0x88980088 | 8.1 | No algorithm avaliable to render text with this device |
| 0x88980089 | 8.1 | Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache. |
| 0x8898008a | 8.1 | Some glyph bitmaps in glyph cache are unexpectedly big. |
| 0x8898008b | 8.1 | 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. |
| 0x8898008c | 8.1 | Guideline coordinates are not sorted properly or contain NaNs. |
| 0x8898008d | 8.1 | No HW rendering device is available for this operation. |
| 0x8898008e | 8.1 | 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 |
| 0x8898008f | 8.1 | The object has already been initialized. |
| 0x88980090 | 8.1 | The size of the object does not match the expected size. |
| 0x88980091 | 8.1 | No Redirection surface available. |
| 0x88980092 | 8.1 | Remoting of this content is not supported. |
| 0x88980093 | 8.1 | Queued Presents are not supported. |
| 0x88980094 | 8.1 | Queued Presents are not being used. |
| 0x88980095 | 8.1 | No redirection surface was available. Caller should retry the call. |
| 0x88980096 | 8.1 | Shader construction failed because it was too complex. |
| 0x88980097 | 8.1 | MROW attempt to get a read lock failed. |
| 0x88980098 | 8.1 | MROW attempt to update the data failed because another update was outstanding. |
| 0x88980099 | 8.1 | Shader compilation failed. |
| 0x8898009a | 8.1 | Requested DX redirection surface size exceeded maximum texture size. |
| 0x8898009b | 8.1 | QueryPerformanceCounter returned a time in the past. |
| 0x8898009d | 8.1 | Primary Display device returned an invalid refresh rate. |
| 0x8898009e | 8.1 | DWM can not find the adapter specified by the LUID. |
| 0x8898009f | 8.1 | The requested bitmap color space is not supported. |
| 0x889800a0 | 8.1 | The requested bitmap pre-filtering state is not supported. |
| 0x889800a1 | 8.1 | Access is denied to the requested bitmap for the specified display id. |
| 0x88980400 | 8.1 | UCEERR_INVALIDPACKETHEADER |
| 0x88980401 | 8.1 | UCEERR_UNKNOWNPACKET |
| 0x88980402 | 8.1 | UCEERR_ILLEGALPACKET |
| 0x88980403 | 8.1 | UCEERR_MALFORMEDPACKET |
| 0x88980404 | 8.1 | UCEERR_ILLEGALHANDLE |
| 0x88980405 | 8.1 | UCEERR_HANDLELOOKUPFAILED |
| 0x88980406 | 8.1 | UCEERR_RENDERTHREADFAILURE |
| 0x88980407 | 8.1 | UCEERR_CTXSTACKFRSTTARGETNULL |
| 0x88980408 | 8.1 | UCEERR_CONNECTIONIDLOOKUPFAILED |
| 0x88980409 | 8.1 | UCEERR_BLOCKSFULL |
| 0x8898040a | 8.1 | UCEERR_MEMORYFAILURE |
| 0x8898040b | 8.1 | UCEERR_PACKETRECORDOUTOFRANGE |
| 0x8898040c | 8.1 | UCEERR_ILLEGALRECORDTYPE |
| 0x8898040d | 8.1 | UCEERR_OUTOFHANDLES |
| 0x8898040e | 8.1 | UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED |
| 0x8898040f | 8.1 | UCEERR_NO_MULTIPLE_WORKER_THREADS |
| 0x88980410 | 8.1 | UCEERR_REMOTINGNOTSUPPORTED |
| 0x88980411 | 8.1 | UCEERR_MISSINGENDCOMMAND |
| 0x88980412 | 8.1 | UCEERR_MISSINGBEGINCOMMAND |
| 0x88980413 | 8.1 | UCEERR_CHANNELSYNCTIMEDOUT |
| 0x88980414 | 8.1 | UCEERR_CHANNELSYNCABANDONED |
| 0x88980415 | 8.1 | UCEERR_UNSUPPORTEDTRANSPORTVERSION |
| 0x88980416 | 8.1 | UCEERR_TRANSPORTUNAVAILABLE |
| 0x88980417 | 8.1 | UCEERR_FEEDBACK_UNSUPPORTED |
| 0x88980418 | 8.1 | UCEERR_COMMANDTRANSPORTDENIED |
| 0x88980419 | 8.1 | UCEERR_GRAPHICSSTREAMUNAVAILABLE |
| 0x88980420 | 8.1 | UCEERR_GRAPHICSSTREAMALREADYOPEN |
| 0x88980421 | 8.1 | UCEERR_TRANSPORTDISCONNECTED |
| 0x88980422 | 8.1 | UCEERR_TRANSPORTOVERLOADED |
| 0x88980423 | 8.1 | UCEERR_PARTITION_ZOMBIED |
| 0x88980500 | 8.1 | MILAVERR_NOCLOCK |
| 0x88980501 | 8.1 | MILAVERR_NOMEDIATYPE |
| 0x88980502 | 8.1 | MILAVERR_NOVIDEOMIXER |
| 0x88980503 | 8.1 | MILAVERR_NOVIDEOPRESENTER |
| 0x88980504 | 8.1 | MILAVERR_NOREADYFRAMES |
| 0x88980505 | 8.1 | MILAVERR_MODULENOTLOADED |
| 0x88980506 | 8.1 | MILAVERR_WMPFACTORYNOTREGISTERED |
| 0x88980507 | 8.1 | MILAVERR_INVALIDWMPVERSION |
| 0x88980508 | 8.1 | MILAVERR_INSUFFICIENTVIDEORESOURCES |
| 0x88980509 | 8.1 | MILAVERR_VIDEOACCELERATIONNOTAVAILABLE |
| 0x8898050a | 8.1 | MILAVERR_REQUESTEDTEXTURETOOBIG |
| 0x8898050b | 8.1 | MILAVERR_SEEKFAILED |
| 0x8898050c | 8.1 | MILAVERR_UNEXPECTEDWMPFAILURE |
| 0x8898050d | 8.1 | MILAVERR_MEDIAPLAYERCLOSED |
| 0x8898050e | 8.1 | MILAVERR_UNKNOWNHARDWAREERROR |
| 0x8898060e | 8.1 | MILEFFECTSERR_UNKNOWNPROPERTY |
| 0x8898060f | 8.1 | MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
| 0x88980610 | 8.1 | MILEFFECTSERR_NOINPUTSOURCEATTACHED |
| 0x88980611 | 8.1 | MILEFFECTSERR_CONNECTORNOTCONNECTED |
| 0x88980612 | 8.1 | MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
| 0x88980613 | 8.1 | MILEFFECTSERR_RESERVED |
| 0x88980614 | 8.1 | MILEFFECTSERR_CYCLEDETECTED |
| 0x88980615 | 8.1 | MILEFFECTSERR_EFFECTINMORETHANONEGRAPH |
| 0x88980616 | 8.1 | MILEFFECTSERR_EFFECTALREADYINAGRAPH |
| 0x88980617 | 8.1 | MILEFFECTSERR_EFFECTHASNOCHILDREN |
| 0x88980618 | 8.1 | MILEFFECTSERR_ALREADYATTACHEDTOLISTENER |
| 0x88980619 | 8.1 | MILEFFECTSERR_NOTAFFINETRANSFORM |
| 0x8898061a | 8.1 | MILEFFECTSERR_EMPTYBOUNDS |
| 0x8898061b | 8.1 | MILEFFECTSERR_OUTPUTSIZETOOLARGE |
| 0x88980700 | 8.1 | DWMERR_STATE_TRANSITION_FAILED |
| 0x88980701 | 8.1 | DWMERR_THEME_FAILED |
| 0x88980702 | 8.1 | DWMERR_CATASTROPHIC_FAILURE |
| 0x88980800 | 8.1 | DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
| 0x88980801 | 8.1 | DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED |
| 0x88980802 | 8.1 | DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
| 0x88982f04 | 8.1 | The codec is in the wrong state. |
| 0x88982f05 | 8.1 | The value is out of range. |
| 0x88982f07 | 8.1 | The image format is unknown. |
| 0x88982f0b | 8.1 | The SDK version is unsupported. |
| 0x88982f0c | 8.1 | The component is not initialized. |
| 0x88982f0d | 8.1 | There is already an outstanding read or write lock. |
| 0x88982f40 | 8.1 | The specified bitmap property cannot be found. |
| 0x88982f41 | 8.1 | The bitmap codec does not support the bitmap property. |
| 0x88982f42 | 8.1 | The bitmap property size is invalid. |
| 0x88982f43 | 8.1 | An unknown error has occurred. |
| 0x88982f44 | 8.1 | The bitmap codec does not support a thumbnail. |
| 0x88982f45 | 8.1 | The bitmap palette is unavailable. |
| 0x88982f46 | 8.1 | Too many scanlines were requested. |
| 0x88982f48 | 8.1 | An internal error occurred. |
| 0x88982f49 | 8.1 | The bitmap bounds do not match the bitmap dimensions. |
| 0x88982f50 | 8.1 | The component cannot be found. |
| 0x88982f51 | 8.1 | The bitmap size is outside the valid range. |
| 0x88982f52 | 8.1 | There is too much metadata to be written to the bitmap. |
| 0x88982f60 | 8.1 | The image is unrecognized. |
| 0x88982f61 | 8.1 | The image header is unrecognized. |
| 0x88982f62 | 8.1 | The bitmap frame is missing. |
| 0x88982f63 | 8.1 | The image metadata header is unrecognized. |
| 0x88982f70 | 8.1 | The stream data is unrecognized. |
| 0x88982f71 | 8.1 | Failed to write to the stream. |
| 0x88982f72 | 8.1 | Failed to read from the stream. |
| 0x88982f73 | 8.1 | The stream is not available. |
| 0x88982f80 | 8.1 | The bitmap pixel format is unsupported. |
| 0x88982f81 | 8.1 | The operation is unsupported. |
| 0x88982f8a | 8.1 | The component registration is invalid. |
| 0x88982f8b | 8.1 | The component initialization has failed. |
| 0x88982f8c | 8.1 | The buffer allocated is insufficient. |
| 0x88982f8d | 8.1 | Duplicate metadata is present. |
| 0x88982f8e | 8.1 | The bitmap property type is unexpected. |
| 0x88982f8f | 8.1 | The size is unexpected. |
| 0x88982f90 | 8.1 | The property query is invalid. |
| 0x88982f91 | 8.1 | The metadata type is unexpected. |
| 0x88982f92 | 8.1 | The specified bitmap property is only valid at root level. |
| 0x88982f93 | 8.1 | The query string contains an invalid character. |
| 0x88982f94 | 8.1 | Windows Codecs received an error from the Win32 system. |
| 0x88982f95 | 8.1 | The requested level of detail is not present. |
| 0x88985000 | 8.1 | Indicates an error in an input file such as a font file. |
| 0x88985001 | 8.1 | Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from. |
| 0x88985002 | 8.1 | Indicates the specified font does not exist. |
| 0x88985003 | 8.1 | A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable. |
| 0x88985004 | 8.1 | A font file exists but could not be opened due to access denied, sharing violation, or similar error. |
| 0x88985005 | 8.1 | A font collection is obsolete due to changes in the system. |
| 0x88985006 | 8.1 | The given interface is already registered. |
| 0x88985007 | 8.1 | The font cache contains invalid data. |
| 0x88985008 | 8.1 | A font cache file corresponds to a different version of DirectWrite. |
| 0x88985009 | 8.1 | The operation is not supported for this type of font. |
| 0x8898500a | 8.1 | The version of the text renderer interface is not compatible. |
| 0x8898500b | 8.1 | The flow direction conflicts with the reading direction. They must be perpendicular to each other. |
| 0x8898500c | 8.1 | The font or glyph run does not contain any colored glyphs. |
| 0x88990001 | 8.1 | The object was not in the correct state to process the method. |
| 0x88990002 | 8.1 | The object has not yet been initialized. |
| 0x88990003 | 8.1 | The requested operation is not supported. |
| 0x88990004 | 8.1 | The geometry scanner failed to process the data. |
| 0x88990005 | 8.1 | Direct2D could not access the screen. |
| 0x88990006 | 8.1 | A valid display state could not be determined. |
| 0x88990007 | 8.1 | The supplied vector is zero. |
| 0x88990008 | 8.1 | 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. |
| 0x88990009 | 8.1 | The display format Direct2D needs to render is not supported by the hardware device. |
| 0x8899000a | 8.1 | A call to this method is invalid. |
| 0x8899000b | 8.1 | No hardware rendering device is available for this operation. |
| 0x8899000c | 8.1 | There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. |
| 0x8899000d | 8.1 | Shader construction failed because it was too complex. |
| 0x8899000e | 8.1 | Shader compilation failed. |
| 0x8899000f | 8.1 | Requested DirectX surface size exceeded maximum texture size. |
| 0x88990010 | 8.1 | The requested Direct2D version is not supported. |
| 0x88990011 | 8.1 | Invalid number. |
| 0x88990012 | 8.1 | Objects used together must be created from the same factory instance. |
| 0x88990013 | 8.1 | A layer resource can only be in use once at any point in time. |
| 0x88990014 | 8.1 | The pop call did not match the corresponding push call. |
| 0x88990015 | 8.1 | The resource was realized on the wrong render target. |
| 0x88990016 | 8.1 | The push and pop calls were unbalanced. |
| 0x88990017 | 8.1 | Attempt to copy from a render target while a layer or clip rect is applied. |
| 0x88990018 | 8.1 | The brush types are incompatible for the call. |
| 0x88990019 | 8.1 | An unknown win32 failure occurred. |
| 0x8899001a | 8.1 | The render target is not compatible with GDI. |
| 0x8899001b | 8.1 | A text client drawing effect object is of the wrong type. |
| 0x8899001c | 8.1 | 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. |
| 0x8899001d | 8.1 | The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level. |
| 0x8899001e | 8.1 | There was a configuration error in the graph. |
| 0x8899001f | 8.1 | There was a internal configuration error in the graph. |
| 0x88990020 | 8.1 | There was a cycle in the graph. |
| 0x88990021 | 8.1 | Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option. |
| 0x88990022 | 8.1 | The operation cannot complete while there are outstanding references to the target bitmap. |
| 0x88990023 | 8.1 | The operation failed because the original target is not currently bound as a target. |
| 0x88990024 | 8.1 | 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. |
| 0x88990025 | 8.1 | Cannot draw with a bitmap that is currently bound as the target bitmap. |
| 0x88990026 | 8.1 | D3D Device does not have sufficient capabilities to perform the requested action. |
| 0x88990027 | 8.1 | The graph could not be rendered with the context's current tiling settings. |
| 0x88990028 | 8.1 | The CLSID provided to Unregister did not correspond to a registered effect. |
| 0x88990029 | 8.1 | The specified property does not exist. |
| 0x8899002a | 8.1 | The specified sub-property does not exist. |
| 0x8899002b | 8.1 | AddPage or Close called after print job is already closed. |
| 0x8899002c | 8.1 | Error during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control. |
| 0x8899002d | 8.1 | An effect attempted to use a transform with too many inputs. |
| 0x89010001 | 8.1 | The operation was preempted by a higher priority operation. It must be resumed later. |
| 0x89020001 | 8.1 | Function could not execute because it was deleted or garbage collected. |
| 0xc026200d | 8.1 | Window DC is not available for presentation |
| 0xc026200e | 8.1 | Windowless present is disabled (desktop windowing management subsystem is off). |
| 0xc0262110 | 8.1 | The allocation can't be used from its current segment location for the specified operation. |
| 0xc0262588 | 8.1 | An internal Monitor Configuration API error occurred. |
| 0xc0350033 | 8.1 | The specified buffer was too small to contain all of the requested data. |
| 0xc0350038 | 8.1 | 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. |
| 0xc0350041 | 8.1 | The hypervisor could not perform the operation because the specified LP index is invalid. |
| 0xc037000f | 8.1 | 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. |
| 0xc03a001a | 8.1 | The requested operation could not be completed due to a virtual disk system limitation. On NTFS, virtual hard disk files must be uncompressed and unencrypted. On ReFS, virtual hard disk files must not have the integrity bit set. |
| 0xc03a001e | 8.1 | The disk is already owned by a different owner. |
| 0xc03a001f | 8.1 | The disk must be offline or read-only. |
| 0xc03a0020 | 8.1 | Change Tracking is not initialized for this virtual disk. |
| 0xc03a0021 | 8.1 | Size of change tracking file exceeded the maximum size limit. |
| 0xc03a0022 | 8.1 | VHD file is changed due to compaction, expansion, or offline updates. |
| 0xc03a0023 | 8.1 | 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. |
| 0xc03a0024 | 8.1 | Change Tracking file for the virtual disk is not in a valid state. |
| 0xc03a0025 | 8.1 | The requested resize operation could not be completed because it might truncate user data residing on the virtual disk. |
| 0xc03a0026 | 8.1 | 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. |
| 0xc03a0027 | 8.1 | The requested operation could not be completed because the virtual disk's size cannot be safely reduced further. |
| 0xc03a0028 | 8.1 | There is not enough space in the virtual disk file for the provided metadata item. |
| 0xc05c0000 | 8.1 | The proper error code with sense data was stored on server side. |
| 0xc05cff00 | 8.1 | The requested error data is not available on the server. |
| 0xc05cff01 | 8.1 | Unit Attention data is available for the initiator to query. |
| 0xc05cff02 | 8.1 | The data capacity of the device has changed, resulting in a Unit Attention condition. |
| 0xc05cff03 | 8.1 | A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. |
| 0xc05cff04 | 8.1 | A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. |
| 0xc05cff05 | 8.1 | A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. |
| 0xc05cff06 | 8.1 | The data storage format of the device has changed, resulting in a Unit Attention condition. |
| 0xc05cff07 | 8.1 | The current initiator is not allowed to perform the SCSI command because of a reservation conflict. |
| 0xc05cff08 | 8.1 | Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks. |
| 0xc05cff09 | 8.1 | The server version does not match the requested version. |
| 0xc05cff0a | 8.1 | The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. |
| 5895 entries | ||