kernel32.dll

Windows (User-Mode)

Associated Error Codes

Below lists error codes and symbolic names found for this module.

Code	Description
0x00000001	Incorrect function.
0x00000002	The system cannot find the file specified.
0x00000003	The system cannot find the path specified.
0x00000004	The system cannot open the file.
0x00000005	Access is denied.
0x00000006	The handle is invalid.
0x00000007	The storage control blocks were destroyed.
0x00000008	Not enough memory resources are available to process this command.
0x00000009	The storage control block address is invalid.
0x0000000A	The environment is incorrect.
0x0000000B	An attempt was made to load a program with an incorrect format.
0x0000000C	The access code is invalid.
0x0000000D	The data is invalid.
0x0000000E	Not enough memory resources are available to complete this operation.
0x0000000F	The system cannot find the drive specified.
0x00000010	The directory cannot be removed.
0x00000011	The system cannot move the file to a different disk drive.
0x00000012	There are no more files.
0x00000013	The media is write protected.
0x00000014	The system cannot find the device specified.
0x00000015	The device is not ready.
0x00000016	The device does not recognize the command.
0x00000017	Data error (cyclic redundancy check).
0x00000018	The program issued a command but the command length is incorrect.
0x00000019	The drive cannot locate a specific area or track on the disk.
0x0000001A	The specified disk or diskette cannot be accessed.
0x0000001B	The drive cannot find the sector requested.
0x0000001C	The printer is out of paper.
0x0000001D	The system cannot write to the specified device.
0x0000001E	The system cannot read from the specified device.
0x0000001F	A device attached to the system is not functioning.
0x00000020	The process cannot access the file because it is being used by another process.
0x00000021	The process cannot access the file because another process has locked a portion of the file.
0x00000022	The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1.
0x00000024	Too many files opened for sharing.
0x00000026	Reached the end of the file.
0x00000027	The disk is full.
0x0000002C	The path cannot be traversed because it contains an untrusted mount point.
0x00000032	The request is not supported.
0x00000033	Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator.
0x00000034	You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.
0x00000035	The network path was not found.
0x00000036	The network is busy.
0x00000037	The specified network resource or device is no longer available.
0x00000038	The network BIOS command limit has been reached.
0x00000039	A network adapter hardware error occurred.
0x0000003A	The specified server cannot perform the requested operation.
0x0000003B	An unexpected network error occurred.
0x0000003C	The remote adapter is not compatible.
0x0000003D	The printer queue is full.
0x0000003E	Space to store the file waiting to be printed is not available on the server.
0x0000003F	Your file waiting to be printed was deleted.
0x00000040	The specified network name is no longer available.
0x00000041	Network access is denied.
0x00000042	The network resource type is not correct.
0x00000043	The network name cannot be found.
0x00000044	The name limit for the local computer network adapter card was exceeded.
0x00000045	The network BIOS session limit was exceeded.
0x00000046	The remote server has been paused or is in the process of being started.
0x00000047	No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept.
0x00000048	The specified printer or disk device has been paused.
0x00000050	The file exists.
0x00000052	The directory or file cannot be created.
0x00000053	Fail on INT 24.
0x00000054	Storage to process this request is not available.
0x00000055	The local device name is already in use.
0x00000056	The specified network password is not correct.
0x00000057	The parameter is incorrect.
0x00000058	A write fault occurred on the network.
0x00000059	The system cannot start another process at this time.
0x00000064	Cannot create another system semaphore.
0x00000065	The exclusive semaphore is owned by another process.
0x00000066	The semaphore is set and cannot be closed.
0x00000067	The semaphore cannot be set again.
0x00000068	Cannot request exclusive semaphores at interrupt time.
0x00000069	The previous ownership of this semaphore has ended.
0x0000006A	Insert the diskette for drive %1.
0x0000006B	The program stopped because an alternate diskette was not inserted.
0x0000006C	The disk is in use or locked by another process.
0x0000006D	The pipe has been ended.
0x0000006E	The system cannot open the device or file specified.
0x0000006F	The file name is too long.
0x00000070	There is not enough space on the disk.
0x00000071	No more internal file identifiers available.
0x00000072	The target internal file identifier is incorrect.
0x00000075	The IOCTL call made by the application program is not correct.
0x00000076	The verify-on-write switch parameter value is not correct.
0x00000077	The system does not support the command requested.
0x00000078	This function is not supported on this system.
0x00000079	The semaphore timeout period has expired.
0x0000007A	The data area passed to a system call is too small.
0x0000007B	The filename, directory name, or volume label syntax is incorrect.
0x0000007C	The system call level is not correct.
0x0000007D	The disk has no volume label.
0x0000007E	The specified module could not be found.
0x0000007F	The specified procedure could not be found.
0x00000080	There are no child processes to wait for.
0x00000081	The %1 application cannot be run in Win32 mode.
0x00000082	Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O.
0x00000083	An attempt was made to move the file pointer before the beginning of the file.
0x00000084	The file pointer cannot be set on the specified device or file.
0x00000085	A JOIN or SUBST command cannot be used for a drive that contains previously joined drives.
0x00000086	An attempt was made to use a JOIN or SUBST command on a drive that has already been joined.
0x00000087	An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted.
0x00000088	The system tried to delete the JOIN of a drive that is not joined.
0x00000089	The system tried to delete the substitution of a drive that is not substituted.
0x0000008A	The system tried to join a drive to a directory on a joined drive.
0x0000008B	The system tried to substitute a drive to a directory on a substituted drive.
0x0000008C	The system tried to join a drive to a directory on a substituted drive.
0x0000008D	The system tried to SUBST a drive to a directory on a joined drive.
0x0000008E	The system cannot perform a JOIN or SUBST at this time.
0x0000008F	The system cannot join or substitute a drive to or for a directory on the same drive.
0x00000090	The directory is not a subdirectory of the root directory.
0x00000091	The directory is not empty.
0x00000092	The path specified is being used in a substitute.
0x00000093	Not enough resources are available to process this command.
0x00000094	The path specified cannot be used at this time.
0x00000095	An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute.
0x00000096	System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.
0x00000097	The number of specified semaphore events for DosMuxSemWait is not correct.
0x00000098	DosMuxSemWait did not execute; too many semaphores are already set.
0x00000099	The DosMuxSemWait list is not correct.
0x0000009A	The volume label you entered exceeds the label character limit of the target file system.
0x0000009B	Cannot create another thread.
0x0000009C	The recipient process has refused the signal.
0x0000009D	The segment is already discarded and cannot be locked.
0x0000009E	The segment is already unlocked.
0x0000009F	The address for the thread ID is not correct.
0x000000A0	One or more arguments are not correct.
0x000000A1	The specified path is invalid.
0x000000A2	A signal is already pending.
0x000000A4	No more threads can be created in the system.
0x000000A7	Unable to lock a region of a file.
0x000000AA	The requested resource is in use.
0x000000AB	Device's command support detection is in progress.
0x000000AD	A lock request was not outstanding for the supplied cancel region.
0x000000AE	The file system does not support atomic changes to the lock type.
0x000000B4	The system detected a segment number that was not correct.
0x000000B6	The operating system cannot run %1.
0x000000B7	Cannot create a file when that file already exists.
0x000000BA	The flag passed is not correct.
0x000000BB	The specified system semaphore name was not found.
0x000000BC	The operating system cannot run %1.
0x000000BD	The operating system cannot run %1.
0x000000BE	The operating system cannot run %1.
0x000000BF	Cannot run %1 in Win32 mode.
0x000000C0	The operating system cannot run %1.
0x000000C1	%1 is not a valid Win32 application.
0x000000C2	The operating system cannot run %1.
0x000000C3	The operating system cannot run %1.
0x000000C4	The operating system cannot run this application program.
0x000000C5	The operating system is not presently configured to run this application.
0x000000C6	The operating system cannot run %1.
0x000000C7	The operating system cannot run this application program.
0x000000C8	The code segment cannot be greater than or equal to 64K.
0x000000C9	The operating system cannot run %1.
0x000000CA	The operating system cannot run %1.
0x000000CB	The system could not find the environment option that was entered.
0x000000CD	No process in the command subtree has a signal handler.
0x000000CE	The filename or extension is too long.
0x000000CF	The ring 2 stack is in use.
0x000000D0	The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
0x000000D1	The signal being posted is not correct.
0x000000D2	The signal handler cannot be set.
0x000000D4	The segment is locked and cannot be reallocated.
0x000000D6	Too many dynamic-link modules are attached to this program or dynamic-link module.
0x000000D7	Cannot nest calls to LoadModule.
0x000000D8	This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher.
0x000000D9	The image file %1 is signed, unable to modify.
0x000000DA	The image file %1 is strong signed, unable to modify.
0x000000DC	This file is checked out or locked for editing by another user.
0x000000DD	The file must be checked out before saving changes.
0x000000DE	The file type being saved or retrieved has been blocked.
0x000000DF	The file size exceeds the limit allowed and cannot be saved.
0x000000E0	Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically.
0x000000E1	Operation did not complete successfully because the file contains a virus or potentially unwanted software.
0x000000E2	This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location.
0x000000E5	The pipe is local.
0x000000E6	The pipe state is invalid.
0x000000E7	All pipe instances are busy.
0x000000E8	The pipe is being closed.
0x000000E9	No process is on the other end of the pipe.
0x000000EA	More data is available.
0x000000EB	The action requested resulted in no work being done. Error-style clean-up has been performed.
0x000000F0	The session was canceled.
0x000000FE	The specified extended attribute name was invalid.
0x000000FF	The extended attributes are inconsistent.
0x00000102	The wait operation timed out.
0x00000103	No more data is available.
0x0000010A	The copy functions cannot be used.
0x0000010B	The directory name is invalid.
0x00000113	The extended attributes did not fit in the buffer.
0x00000114	The extended attribute file on the mounted file system is corrupt.
0x00000115	The extended attribute table file is full.
0x00000116	The specified extended attribute handle is invalid.
0x0000011A	The mounted file system does not support extended attributes.
0x00000120	Attempt to release mutex not owned by caller.
0x0000012A	Too many posts were made to a semaphore.
0x0000012B	Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
0x0000012C	The oplock request is denied.
0x0000012D	An invalid oplock acknowledgment was received by the system.
0x0000012E	The volume is too fragmented to complete this operation.
0x0000012F	The file cannot be opened because it is in the process of being deleted.
0x00000130	Short name settings may not be changed on this volume due to the global registry setting.
0x00000131	Short names are not enabled on this volume.
0x00000132	The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume.
0x00000133	A requested file lock operation cannot be processed due to an invalid byte range.
0x00000134	The subsystem needed to support the image type is not present.
0x00000135	The specified file already has a notification GUID associated with it.
0x00000136	An invalid exception handler routine has been detected.
0x00000137	Duplicate privileges were specified for the token.
0x00000138	No ranges for the specified operation were able to be processed.
0x00000139	Operation is not allowed on a file system internal file.
0x0000013A	The physical resources of this disk have been exhausted.
0x0000013B	The token representing the data is invalid.
0x0000013C	The device does not support the command feature.
0x0000013D	The system cannot find message text for message number 0x%1 in the message file for %2.
0x0000013E	The scope specified was not found.
0x0000013F	The Central Access Policy specified is not defined on the target machine.
0x00000140	The Central Access Policy obtained from Active Directory is invalid.
0x00000141	The device is unreachable.
0x00000142	The target device has insufficient resources to complete the operation.
0x00000143	A data integrity checksum error occurred. Data in the file stream is corrupt.
0x00000144	An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation.
0x00000146	Device does not support file-level TRIM.
0x00000147	The command specified a data offset that does not align to the device's granularity/alignment.
0x00000148	The command specified an invalid field in its parameter list.
0x00000149	An operation is currently in progress with the device.
0x0000014A	An attempt was made to send down the command via an invalid path to the target device.
0x0000014B	The command specified a number of descriptors that exceeded the maximum supported by the device.
0x0000014C	Scrub is disabled on the specified file.
0x0000014D	The storage device does not provide redundancy.
0x0000014E	An operation is not supported on a resident file.
0x0000014F	An operation is not supported on a compressed file.
0x00000150	An operation is not supported on a directory.
0x00000151	The specified copy of the requested data could not be read.
0x00000152	The specified data could not be written to any of the copies.
0x00000153	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.
0x00000154	The supplied kernel information version is invalid.
0x00000155	The supplied PEP information version is invalid.
0x00000156	This object is not externally backed by any provider.
0x00000157	The external backing provider is not recognized.
0x00000158	Compressing this object would not save space.
0x00000159	The request failed due to a storage topology ID mismatch.
0x0000015A	The operation was blocked by parental controls.
0x0000015B	A file system block being referenced has already reached the maximum reference count and can't be referenced any further.
0x0000015C	The requested operation failed because the file stream is marked to disallow writes.
0x0000015D	The requested operation failed with an architecture-specific failure code.
0x0000015E	No action was taken as a system reboot is required.
0x0000015F	The shutdown operation failed.
0x00000160	The restart operation failed.
0x00000161	The maximum number of sessions has been reached.
0x00000162	Windows Information Protection policy does not allow access to this network resource.
0x00000163	The device hint name buffer is too small to receive the remaining name.
0x00000164	The requested operation was blocked by Windows Information Protection policy. For more information, contact your system administrator.
0x00000165	The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator.
0x00000166	The cloud sync root metadata is corrupted.
0x00000167	The device is in maintenance mode.
0x00000168	This operation is not supported on a DAX volume.
0x00000169	The volume has active DAX mappings.
0x0000016A	The cloud file provider is not running.
0x0000016B	The cloud file metadata is corrupt and unreadable.
0x0000016C	The cloud file metadata is too large.
0x0000016D	The cloud file property is too large.
0x0000016E	The cloud file property is possibly corrupt. The on-disk checksum does not match the computed checksum.
0x0000016F	The process creation has been blocked.
0x00000170	The storage device has lost data or persistence.
0x00000171	The provider that supports file system virtualization is temporarily unavailable.
0x00000172	The metadata for file system virtualization is corrupt and unreadable.
0x00000173	The provider that supports file system virtualization is too busy to complete this operation.
0x00000174	The provider that supports file system virtualization is unknown.
0x00000175	GDI handles were potentially leaked by the application.
0x00000176	The maximum number of cloud file properties has been reached.
0x00000177	The version of the cloud file property store is not supported.
0x00000178	The file is not a cloud file.
0x00000179	The file is not in sync with the cloud.
0x0000017A	The cloud sync root is already connected with another cloud sync provider.
0x0000017B	The operation is not supported by the cloud sync provider.
0x0000017C	The cloud operation is invalid.
0x0000017D	The cloud operation is not supported on a read-only volume.
0x0000017E	The operation is reserved for a connected cloud sync provider.
0x0000017F	The cloud sync provider failed to validate the downloaded data.
0x00000180	You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747
0x00000181	The virtualization operation is not allowed on the file in its current state.
0x00000182	The cloud sync provider failed user authentication.
0x00000183	The cloud sync provider failed to perform the operation due to low system resources.
0x00000184	The cloud sync provider failed to perform the operation due to network being unavailable.
0x00000185	The cloud operation was unsuccessful.
0x00000186	The operation is only supported on files under a cloud sync root.
0x00000187	The operation cannot be performed on cloud files in use.
0x00000188	The operation cannot be performed on pinned cloud files.
0x00000189	The cloud operation was aborted.
0x0000018A	The cloud file's property store is corrupt.
0x0000018B	Access to the cloud file is denied.
0x0000018C	The cloud operation cannot be performed on a file with incompatible hardlinks.
0x0000018D	The operation failed due to a conflicting cloud file property lock.
0x0000018E	The cloud operation was canceled by user.
0x0000018F	An externally encrypted syskey has been configured, but the system no longer supports this feature. Please see https://go.microsoft.com/fwlink/?linkid=851152 for more information.
0x00000190	The thread is already in background processing mode.
0x00000191	The thread is not in background processing mode.
0x00000192	The process is already in background processing mode.
0x00000193	The process is not in background processing mode.
0x00000194	The cloud file provider exited unexpectedly.
0x00000195	The file is not a cloud sync root.
0x00000196	The read or write operation to an encrypted file could not be completed because the file can only be accessed when the device is unlocked.
0x00000197	The volume is not cluster aligned on the disk.
0x00000198	No physically aligned free space was found on the volume.
0x00000199	The APPX file can not be accessed because it is not encrypted as expected.
0x0000019A	A read or write of raw encrypted data cannot be performed because the file is not encrypted.
0x0000019B	An invalid file offset in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
0x0000019C	An invalid offset and length combination in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
0x0000019D	An invalid parameter in the encrypted data info block was passed for read or write operation of file's raw encrypted data.
0x0000019E	The Windows Subsystem for Linux has not been enabled.
0x0000019F	The specified data could not be read from any of the copies.
0x000001A0	The specified storage reserve ID is invalid.
0x000001A1	The specified storage reserve does not exist.
0x000001A2	The specified storage reserve already exists.
0x000001A3	The specified storage reserve is not empty.
0x000001A4	This operation requires a DAX volume.
0x000001A5	This stream is not DAX mappable.
0x000001A6	Operation cannot be performed on a time critical thread.
0x000001A7	User data protection is not supported for the current or provided user.
0x000001A8	This directory contains entries whose names differ only in case.
0x000001A9	The file cannot be safely opened because it is not supported by this version of Windows.
0x000001AA	The cloud operation was not completed before the time-out period expired.
0x000001AB	A task queue is required for this operation but none is available.
0x000001AC	Failed loading a valid version of srcsrv.dll.
0x000001AD	This operation is not supported with BTT enabled.
0x000001AE	This operation cannot be performed because encryption is currently disabled.
0x000001AF	This encryption operation cannot be performed on filesystem metadata.
0x000001B0	Encryption cannot be cleared on this file/directory because it still has an encrypted attribute.
0x000001B1	A device which does not exist was specified.
0x000001B2	Dehydration of the cloud file is disallowed by the cloud sync provider.
0x000001B3	A file snapshot operation was attempted when one is already in progress.
0x000001B4	A snapshot of the file cannot be taken because a user-mapped section is present.
0x000001B5	The file snapshot operation was terminated because one of the files was modified in a way incompatible with a snapshot operation. Please try again.
0x000001B6	An I/O request could not be coordinated with a file snapshot operation.
0x000001B7	An unexpected error occurred while processing a file snapshot operation.
0x000001B8	A file snapshot operation received an invalid parameter.
0x000001B9	The operation could not be completed due to one or more unsatisfied dependencies.
0x000001BA	The file cannot be opened because the path has a case-sensitive directory.
0x000001BB	The filesystem couldn't handle one of the CacheManager's callback error codes.
0x000001BC	WSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel
0x000001BD	This action is blocked, but you can choose to allow it. Please refer to the data loss prevention notification for further information.
0x000001BE	This action is blocked. Please refer to the data loss prevention notification for further information.
0x000001C1	This action is blocked. Please refer to the data loss prevention notification for further information.
0x000001C2	Neither developer unlocked mode nor side loading mode is enabled on the device.
0x000001C3	Can not change application type during upgrade or re-provision.
0x000001C4	The application has not been provisioned.
0x000001C5	The requested capability can not be authorized for this application.
0x000001C6	There is no capability authorization policy on the device.
0x000001C7	The capability authorization database has been corrupted.
0x000001C8	The custom capability's SCCD has an invalid catalog.
0x000001C9	None of the authorized entity elements in the SCCD matched the app being installed; either the PFNs don't match, or the element's signature hash doesn't validate.
0x000001CA	The custom capability's SCCD failed to parse.
0x000001CB	The custom capability's SCCD requires developer mode.
0x000001CC	There not all declared custom capabilities are found in the SCCD.
0x000001D6	The CimFS image is corrupt.
0x000001DB	The cloud provider failed to acknowledge a message before the time-out expired.
0x000001E0	The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request.
0x000001E1	The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation.
0x000001E2	The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation.
0x000001E3	The request failed due to a fatal device hardware error.
0x000001E7	Attempt to access invalid address.
0x000001E8	The volume contains paging, crash dump or other system critical files.
0x000001F4	User profile cannot be loaded.
0x000001FE	The file system encountered a metadata file with inconsistent data.
0x00000216	Arithmetic result exceeded 32 bits.
0x00000217	There is a process on other end of the pipe.
0x00000218	Waiting for a process to open the other end of the pipe.
0x00000219	Application verifier has found an error in the current process.
0x0000021A	An error occurred in the ABIOS subsystem.
0x0000021B	A warning occurred in the WX86 subsystem.
0x0000021C	An error occurred in the WX86 subsystem.
0x0000021D	An attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine.
0x0000021E	Unwind exception code.
0x0000021F	An invalid or unaligned stack was encountered during an unwind operation.
0x00000220	An invalid unwind target was encountered during an unwind operation.
0x00000221	Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
0x00000222	Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port.
0x00000223	An attempt was made to lower a quota limit below the current usage.
0x00000224	An attempt was made to attach to a device that was already attached to another device.
0x00000225	An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references.
0x00000226	Profiling not started.
0x00000227	Profiling not stopped.
0x00000228	The passed ACL did not contain the minimum required information.
0x00000229	The number of active profiling objects is at the maximum and no more may be started.
0x0000022A	Used to indicate that an operation cannot continue without blocking for I/O.
0x0000022B	Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process.
0x0000022C	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.
0x0000022D	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.
0x0000022E	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.
0x0000022F	A malformed function table was encountered during an unwind operation.
0x00000230	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.
0x00000231	Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors.
0x00000233	Indicates that the starting value for the LDT information was not an integral multiple of the selector size.
0x00000234	Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.
0x00000235	Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads.
0x00000236	An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified.
0x00000237	Page file quota was exceeded.
0x00000238	The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.
0x00000239	The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.
0x0000023A	The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines.
0x0000023B	{Privilege Failed} The I/O permissions for the process could not be changed.
0x0000023C	{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.
0x0000023D	{Missing System File} The required system file %hs is bad or missing.
0x0000023E	{Application Error} The exception %s (0x%08lx) occurred in the application at location 0x%08lx.
0x0000023F	{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application.
0x00000240	{Unable to Create Paging File} The creation of the paging file %hs failed (%lx). The requested size was %ld.
0x00000241	Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
0x00000242	{No Paging File Specified} No paging file was specified in the system configuration.
0x00000243	{EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present.
0x00000244	An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread.
0x00000245	A Windows Server has an incorrect configuration.
0x00000246	An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE.
0x00000247	The Unicode character is not defined in the Unicode character set installed on the system.
0x00000248	The paging file cannot be created on a floppy diskette.
0x00000249	The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected.
0x0000024A	This operation is only allowed for the Primary Domain Controller of the domain.
0x0000024B	An attempt was made to acquire a mutant such that its maximum count would have been exceeded.
0x0000024C	A volume has been accessed for which a file system driver is required that has not yet been loaded.
0x0000024D	{Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable.
0x0000024E	{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.
0x0000024F	{Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down.
0x00000250	{Data Not Accepted} The TDI client could not handle the data received during an indication.
0x00000251	NTVDM encountered a hard error.
0x00000252	{Cancel Timeout} The driver %hs failed to complete a cancelled I/O request in the allotted time.
0x00000253	{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.
0x00000254	{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.
0x00000255	The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window.
0x00000256	The stream is not a tiny stream.
0x00000257	The request must be handled by the stack overflow code.
0x00000258	Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream.
0x00000259	The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation.
0x0000025A	The bucket array must be grown. Retry transaction after doing so.
0x0000025B	The user/kernel marshalling buffer has overflowed.
0x0000025C	The supplied variant structure contains invalid data.
0x0000025D	The specified buffer contains ill-formed data.
0x0000025E	{Audit Failed} An attempt to generate a security audit failed.
0x0000025F	The timer resolution was not previously set by the current process.
0x00000260	There is insufficient account information to log you on.
0x00000261	{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.
0x00000262	{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.
0x00000263	There is an IP address conflict with another system on the network
0x00000264	There is an IP address conflict with another system on the network
0x00000265	{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.
0x00000266	A callback return system service cannot be executed when no callback is active.
0x00000267	The password provided is too short to meet the policy of your user account. Please choose a longer password.
0x00000268	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.
0x00000269	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.
0x0000026A	The specified compression format is unsupported.
0x0000026B	The specified hardware profile configuration is invalid.
0x0000026C	The specified Plug and Play registry device path is invalid.
0x0000026D	The specified quota list is internally inconsistent with its descriptor.
0x0000026E	{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.
0x0000026F	{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.
0x00000270	{DLL Initialization Failed} The application failed to initialize because the window station is shutting down.
0x00000271	The validation process needs to continue on to the next step.
0x00000272	There are no more matches for the current index enumeration.
0x00000273	The range could not be added to the range list because of a conflict.
0x00000274	The server process is running under a SID different than that required by client.
0x00000275	A group marked use for deny only cannot be enabled.
0x00000276	{EXCEPTION} Multiple floating point faults.
0x00000277	{EXCEPTION} Multiple floating point traps.
0x00000278	The requested interface is not supported.
0x00000279	{System Standby Failed} The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode.
0x0000027A	The system file %1 has become corrupt and has been replaced.
0x0000027B	{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.
0x0000027C	A device was removed so enumeration must be restarted.
0x0000027D	{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.
0x0000027E	Device will not start without a reboot.
0x0000027F	There is not enough power to complete the requested operation.
0x00000280	ERROR_MULTIPLE_FAULT_VIOLATION
0x00000281	The system is in the process of shutting down.
0x00000282	An attempt to remove a processes DebugPort was made, but a port was not already associated with the process.
0x00000283	This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller.
0x00000284	The specified range could not be found in the range list.
0x00000286	The driver was not loaded because the system is booting into safe mode.
0x00000287	The driver was not loaded because it failed its initialization call.
0x00000288	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.
0x00000289	The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached.
0x0000028A	The device object parameter is either not a valid device object or is not attached to the volume specified by the file name.
0x0000028B	A Machine Check Error has occurred. Please check the system eventlog for additional information.
0x0000028C	There was error [%2] processing the driver database.
0x0000028D	System hive size has exceeded its limit.
0x0000028E	The driver could not be loaded because a previous version of the driver is still in memory.
0x0000028F	{Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation.
0x00000290	The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted.
0x00000291	The password provided is too long to meet the policy of your user account. Please choose a shorter password.
0x00000299	The requested operation could not be completed due to a file system limitation
0x0000029C	An assertion failure has occurred.
0x0000029D	An error occurred in the ACPI subsystem.
0x0000029E	WOW Assertion Error.
0x0000029F	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.
0x000002A0	A translator failed to translate resources.
0x000002A1	A IRQ translator failed to translate resources.
0x000002A2	Driver %2 returned invalid ID for a child device (%3).
0x000002A3	{Kernel Debugger Awakened} the system debugger was awakened by an interrupt.
0x000002A4	{Handles Closed} Handles to objects have been automatically closed as a result of the requested operation.
0x000002A5	{Too Much Information} The specified access control list (ACL) contained more information than was expected.
0x000002A6	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).
0x000002A7	{Media Changed} The media may have changed.
0x000002A8	{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.
0x000002A9	The create operation stopped after reaching a symbolic link
0x000002AA	A long jump has been executed.
0x000002AB	The Plug and Play query operation was not successful.
0x000002AC	A frame consolidation has been executed.
0x000002AD	{Registry Hive Recovered} Registry hive (file): %hs was corrupted and it has been recovered. Some data might have been lost.
0x000002AE	The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?
0x000002AF	The application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?
0x000002B0	Debugger did not handle the exception.
0x000002B1	Debugger will reply later.
0x000002B2	Debugger cannot provide handle.
0x000002B3	Debugger terminated thread.
0x000002B4	Debugger terminated process.
0x000002B5	Debugger got control C.
0x000002B6	Debugger printed exception on control C.
0x000002B7	Debugger received RIP exception.
0x000002B8	Debugger received control break.
0x000002B9	Debugger command communication exception.
0x000002BA	{Object Exists} An attempt was made to create an object and the object name already existed.
0x000002BB	{Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.
0x000002BC	{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.
0x000002BD	This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created.
0x000002BE	{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.
0x000002BF	{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.
0x000002C0	{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.
0x000002C1	{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.
0x000002C2	{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.
0x000002C3	{Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later.
0x000002C4	{Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system.
0x000002C5	{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.
0x000002C6	{TDI Event Done} The TDI indication has completed successfully.
0x000002C7	{TDI Event Pending} The TDI indication has entered the pending state.
0x000002C8	Checking file system on %wZ
0x000002C9	{Fatal Application Exit} %hs
0x000002CA	The specified registry key is referenced by a predefined handle.
0x000002CB	{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.
0x000002CC	%hs
0x000002CD	{Page Locked} One of the pages to lock was already locked.
0x000002CE	Application popup: %1 : %2
0x000002CF	ERROR_ALREADY_WIN32
0x000002D0	{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine.
0x000002D1	A yield execution was performed and no thread was available to run.
0x000002D2	The resumable flag to a timer API was ignored.
0x000002D3	The arbiter has deferred arbitration of these resources to its parent
0x000002D4	The inserted CardBus device cannot be started because of a configuration error on "%hs".
0x000002D5	The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported.
0x000002D6	The system was put into hibernation.
0x000002D7	The system was resumed from hibernation.
0x000002D8	Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].
0x000002D9	A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit.
0x000002DA	The system has awoken
0x000002DB	ERROR_WAIT_1
0x000002DC	ERROR_WAIT_2
0x000002DD	ERROR_WAIT_3
0x000002DE	ERROR_WAIT_63
0x000002DF	ERROR_ABANDONED_WAIT_0
0x000002E0	ERROR_ABANDONED_WAIT_63
0x000002E1	ERROR_USER_APC
0x000002E2	ERROR_KERNEL_APC
0x000002E3	ERROR_ALERTED
0x000002E4	The requested operation requires elevation.
0x000002E5	A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.
0x000002E6	An open/create operation completed while an oplock break is underway.
0x000002E7	A new volume has been mounted by a file system.
0x000002E8	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.
0x000002E9	This indicates that a notify change request has been completed due to closing the handle which made the notify change request.
0x000002EA	{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.
0x000002EB	Page fault was a transition fault.
0x000002EC	Page fault was a demand zero fault.
0x000002ED	Page fault was a demand zero fault.
0x000002EE	Page fault was a demand zero fault.
0x000002EF	Page fault was satisfied by reading from a secondary storage device.
0x000002F0	Cached page was locked during operation.
0x000002F1	Crash dump exists in paging file.
0x000002F2	Specified buffer contains all zeros.
0x000002F3	A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.
0x000002F4	The device has succeeded a query-stop and its resource requirements have changed.
0x000002F5	The translator has translated these resources into the global space and no further translations should be performed.
0x000002F6	A process being terminated has no threads to terminate.
0x000002F7	The specified process is not part of a job.
0x000002F8	The specified process is part of a job.
0x000002F9	{Volume Shadow Copy Service} The system is now ready for hibernation.
0x000002FA	A file system or file system filter driver has successfully completed an FsFilter operation.
0x000002FB	The specified interrupt vector was already connected.
0x000002FC	The specified interrupt vector is still connected.
0x000002FD	An operation is blocked waiting for an oplock.
0x000002FE	Debugger handled exception
0x000002FF	Debugger continued
0x00000300	An exception occurred in a user mode callback and the kernel callback frame should be removed.
0x00000301	Compression is disabled for this volume.
0x00000302	The data provider cannot fetch backwards through a result set.
0x00000303	The data provider cannot scroll backwards through a result set.
0x00000304	The data provider requires that previously fetched data is released before asking for more data.
0x00000305	The data provider was not able to interpret the flags set for a column binding in an accessor.
0x00000306	One or more errors occurred while processing the request.
0x00000307	The implementation is not capable of performing the request.
0x00000308	The client of a component requested an operation which is not valid given the state of the component instance.
0x00000309	A version number could not be parsed.
0x0000030A	The iterator's start position is invalid.
0x0000030B	The hardware has reported an uncorrectable memory error.
0x0000030C	The attempted operation required self healing to be enabled.
0x0000030D	The Desktop heap encountered an error while allocating session memory. There is more information in the system event log.
0x0000030E	The system power state is transitioning from %2 to %3.
0x0000030F	The system power state is transitioning from %2 to %3 but could enter %4.
0x00000310	A thread is getting dispatched with MCA EXCEPTION because of MCA.
0x00000311	Access to %1 is monitored by policy rule %2.
0x00000312	Access to %1 has been restricted by your Administrator by policy rule %2.
0x00000313	A valid hibernation file has been invalidated and should be abandoned.
0x00000314	{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.
0x00000315	{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.
0x00000316	{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.
0x00000317	The resources required for this device conflict with the MCFG table.
0x00000318	The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired.
0x00000319	The volume repair was not successful.
0x0000031A	One of the volume corruption logs is full. Further corruptions that may be detected won't be logged.
0x0000031B	One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.
0x0000031C	One of the volume corruption logs is unavailable for being operated on.
0x0000031D	One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned.
0x0000031E	One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions.
0x0000031F	Orphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory.
0x00000320	The oplock that was associated with this handle is now associated with a different handle.
0x00000321	An oplock of the requested level cannot be granted. An oplock of a lower level may be available.
0x00000322	The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken.
0x00000323	The handle with which this oplock was associated has been closed. The oplock is now broken.
0x00000324	The specified access control entry (ACE) does not contain a condition.
0x00000325	The specified access control entry (ACE) contains an invalid condition.
0x00000326	Access to the specified file handle has been revoked.
0x00000327	{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.
0x00000328	The read or write operation to an encrypted file could not be completed because the file has not been opened for data access.
0x00000329	File metadata optimization is already in progress.
0x0000032A	The requested operation failed due to quota operation is still in progress.
0x0000032B	Access to the specified handle has been revoked.
0x0000032C	The callback function must be invoked inline.
0x0000032D	The specified CPU Set IDs are invalid.
0x0000032E	The specified enclave has not yet been terminated.
0x0000032F	An attempt was made to access protected memory in violation of its secure access policy.
0x000003E2	Access to the extended attribute was denied.
0x000003E3	The I/O operation has been aborted because of either a thread exit or an application request.
0x000003E4	Overlapped I/O event is not in a signaled state.
0x000003E5	Overlapped I/O operation is in progress.
0x000003E6	Invalid access to memory location.
0x000003E7	Error performing inpage operation.
0x000003E9	Recursion too deep; the stack overflowed.
0x000003EA	The window cannot act on the sent message.
0x000003EB	Cannot complete this function.
0x000003EC	Invalid flags.
0x000003ED	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.
0x000003EE	The volume for a file has been externally altered so that the opened file is no longer valid.
0x000003EF	The requested operation cannot be performed in full-screen mode.
0x000003F0	An attempt was made to reference a token that does not exist.
0x000003F1	The configuration registry database is corrupt.
0x000003F2	The configuration registry key is invalid.
0x000003F3	The configuration registry key could not be opened.
0x000003F4	The configuration registry key could not be read.
0x000003F5	The configuration registry key could not be written.
0x000003F6	One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful.
0x000003F7	The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted.
0x000003F8	An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
0x000003F9	The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format.
0x000003FA	Illegal operation attempted on a registry key that has been marked for deletion.
0x000003FB	System could not allocate the required space in a registry log.
0x000003FC	Cannot create a symbolic link in a registry key that already has subkeys or values.
0x000003FD	Cannot create a stable subkey under a volatile parent key.
0x000003FE	A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes.
0x0000041B	A stop control has been sent to a service that other running services are dependent on.
0x0000041C	The requested control is not valid for this service.
0x0000041D	The service did not respond to the start or control request in a timely fashion.
0x0000041E	A thread could not be created for the service.
0x0000041F	The service database is locked.
0x00000420	An instance of the service is already running.
0x00000421	The account name is invalid or does not exist, or the password is invalid for the account name specified.
0x00000422	The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
0x00000423	Circular service dependency was specified.
0x00000424	The specified service does not exist as an installed service.
0x00000425	The service cannot accept control messages at this time.
0x00000426	The service has not been started.
0x00000427	The service process could not connect to the service controller.
0x00000428	An exception occurred in the service when handling the control request.
0x00000429	The database specified does not exist.
0x0000042A	The service has returned a service-specific error code.
0x0000042B	The process terminated unexpectedly.
0x0000042C	The dependency service or group failed to start.
0x0000042D	The service did not start due to a logon failure.
0x0000042E	After starting, the service hung in a start-pending state.
0x0000042F	The specified service database lock is invalid.
0x00000430	The specified service has been marked for deletion.
0x00000431	The specified service already exists.
0x00000432	The system is currently running with the last-known-good configuration.
0x00000433	The dependency service does not exist or has been marked for deletion.
0x00000434	The current boot has already been accepted for use as the last-known-good control set.
0x00000435	No attempts to start the service have been made since the last boot.
0x00000436	The name is already in use as either a service name or a service display name.
0x00000437	The account specified for this service is different from the account specified for other services running in the same process.
0x00000438	Failure actions can only be set for Win32 services, not for drivers.
0x00000439	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.
0x0000043A	No recovery program has been configured for this service.
0x0000043B	The executable program that this service is configured to run in does not implement the service.
0x0000043C	This service cannot be started in Safe Mode
0x0000044C	The physical end of the tape has been reached.
0x0000044D	A tape access reached a filemark.
0x0000044E	The beginning of the tape or a partition was encountered.
0x0000044F	A tape access reached the end of a set of files.
0x00000450	No more data is on the tape.
0x00000451	Tape could not be partitioned.
0x00000452	When accessing a new tape of a multivolume partition, the current block size is incorrect.
0x00000453	Tape partition information could not be found when loading a tape.
0x00000454	Unable to lock the media eject mechanism.
0x00000455	Unable to unload the media.
0x00000456	The media in the drive may have changed.
0x00000457	The I/O bus was reset.
0x00000458	No media in drive.
0x00000459	No mapping for the Unicode character exists in the target multi-byte code page.
0x0000045A	A dynamic link library (DLL) initialization routine failed.
0x0000045B	A system shutdown is in progress.
0x0000045C	Unable to abort the system shutdown because no shutdown was in progress.
0x0000045D	The request could not be performed because of an I/O device error.
0x0000045E	No serial device was successfully initialized. The serial driver will unload.
0x0000045F	Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened.
0x00000460	A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
0x00000461	A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
0x00000462	No ID address mark was found on the floppy disk.
0x00000463	Mismatch between the floppy disk sector ID field and the floppy disk controller track address.
0x00000464	The floppy disk controller reported an error that is not recognized by the floppy disk driver.
0x00000465	The floppy disk controller returned inconsistent results in its registers.
0x00000466	While accessing the hard disk, a recalibrate operation failed, even after retries.
0x00000467	While accessing the hard disk, a disk operation failed even after retries.
0x00000468	While accessing the hard disk, a disk controller reset was needed, but even that failed.
0x00000469	Physical end of tape encountered.
0x0000046A	Not enough server memory resources are available to process this command.
0x0000046B	A potential deadlock condition has been detected.
0x0000046C	The base address or the file offset specified does not have the proper alignment.
0x00000474	An attempt to change the system power state was vetoed by another application or driver.
0x00000475	The system BIOS failed an attempt to change the system power state.
0x00000476	An attempt was made to create more links on a file than the file system supports.
0x0000047E	The specified program requires a newer version of Windows.
0x0000047F	The specified program is not a Windows or MS-DOS program.
0x00000480	Cannot start more than one instance of the specified program.
0x00000481	The specified program was written for an earlier version of Windows.
0x00000482	One of the library files needed to run this application is damaged.
0x00000483	No application is associated with the specified file for this operation.
0x00000484	An error occurred in sending the command to the application.
0x00000485	One of the library files needed to run this application cannot be found.
0x00000486	The current process has used all of its system allowance of handles for Window Manager objects.
0x00000487	The message can be used only with synchronous operations.
0x00000488	The indicated source element has no media.
0x00000489	The indicated destination element already contains media.
0x0000048A	The indicated element does not exist.
0x0000048B	The indicated element is part of a magazine that is not present.
0x0000048C	The indicated device requires reinitialization due to hardware errors.
0x0000048D	The device has indicated that cleaning is required before further operations are attempted.
0x0000048E	The device has indicated that its door is open.
0x0000048F	The device is not connected.
0x00000490	Element not found.
0x00000491	There was no match for the specified key in the index.
0x00000492	The property set specified does not exist on the object.
0x00000493	The point passed to GetMouseMovePoints is not in the buffer.
0x00000494	The tracking (workstation) service is not running.
0x00000495	The Volume ID could not be found.
0x00000497	Unable to remove the file to be replaced.
0x00000498	Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name.
0x00000499	Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name.
0x0000049A	The volume change journal is being deleted.
0x0000049B	The volume change journal is not active.
0x0000049C	A file was found, but it may not be the correct file.
0x0000049D	The journal entry has been deleted from the journal.
0x0000049F	Driver Verifier Volatile settings cannot be set when CFG and IO are enabled.
0x000004A0	An attempt was made to access a partition that has begun termination.
0x000004A6	A system shutdown has already been scheduled.
0x000004A7	The system shutdown cannot be initiated because there are other users logged on to the computer.
0x000004B0	The specified device name is invalid.
0x000004B1	The device is not currently connected but it is a remembered connection.
0x000004B2	The local device name has a remembered connection to another network resource.
0x000004B3	The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.
0x000004B4	The specified network provider name is invalid.
0x000004B5	Unable to open the network connection profile.
0x000004B6	The network connection profile is corrupted.
0x000004B7	Cannot enumerate a noncontainer.
0x000004B8	An extended error has occurred.
0x000004B9	The format of the specified group name is invalid.
0x000004BA	The format of the specified computer name is invalid.
0x000004BB	The format of the specified event name is invalid.
0x000004BC	The format of the specified domain name is invalid.
0x000004BD	The format of the specified service name is invalid.
0x000004BE	The format of the specified network name is invalid.
0x000004BF	The format of the specified share name is invalid.
0x000004C0	The format of the specified password is invalid.
0x000004C1	The format of the specified message name is invalid.
0x000004C2	The format of the specified message destination is invalid.
0x000004C3	Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.
0x000004C4	An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.
0x000004C5	The workgroup or domain name is already in use by another computer on the network.
0x000004C6	The network is not present or not started.
0x000004C7	The operation was canceled by the user.
0x000004C8	The requested operation cannot be performed on a file with a user-mapped section open.
0x000004C9	The remote computer refused the network connection.
0x000004CA	The network connection was gracefully closed.
0x000004CB	The network transport endpoint already has an address associated with it.
0x000004CC	An address has not yet been associated with the network endpoint.
0x000004CD	An operation was attempted on a nonexistent network connection.
0x000004CE	An invalid operation was attempted on an active network connection.
0x000004CF	The network location cannot be reached. For information about network troubleshooting, see Windows Help.
0x000004D0	The network location cannot be reached. For information about network troubleshooting, see Windows Help.
0x000004D1	The network location cannot be reached. For information about network troubleshooting, see Windows Help.
0x000004D2	No service is operating at the destination network endpoint on the remote system.
0x000004D3	The request was aborted.
0x000004D4	The network connection was aborted by the local system.
0x000004D5	The operation could not be completed. A retry should be performed.
0x000004D6	A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.
0x000004D7	Attempting to log in during an unauthorized time of day for this account.
0x000004D8	The account is not authorized to log in from this station.
0x000004D9	The network address could not be used for the operation requested.
0x000004DA	The service is already registered.
0x000004DB	The specified service does not exist.
0x000004DC	The operation being requested was not performed because the user has not been authenticated.
0x000004DD	The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.
0x000004DE	Continue with work in progress.
0x000004DF	An attempt was made to perform an initialization operation when initialization has already been completed.
0x000004E0	No more local devices.
0x000004E1	The specified site does not exist.
0x000004E2	A domain controller with the specified name already exists.
0x000004E3	This operation is supported only when you are connected to the server.
0x000004E4	The group policy framework should call the extension even if there are no changes.
0x000004E5	The specified user does not have a valid profile.
0x000004E6	This operation is not supported on a computer running Windows Server 2003 for Small Business Server
0x000004E7	The server machine is shutting down.
0x000004E8	The remote system is not available. For information about network troubleshooting, see Windows Help.
0x000004E9	The security identifier provided is not from an account domain.
0x000004EA	The security identifier provided does not have a domain component.
0x000004EB	AppHelp dialog canceled thus preventing the application from starting.
0x000004EC	This program is blocked by group policy. For more information, contact your system administrator.
0x000004ED	A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific.
0x000004EE	The share is currently offline or does not exist.
0x000004EF	The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log.
0x000004F0	The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.
0x000004F1	The system cannot contact a domain controller to service the authentication request. Please try again later.
0x000004F7	The machine is locked and cannot be shut down without the force option.
0x000004F8	You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
0x000004F9	An application-defined callback gave invalid data when called.
0x000004FA	The group policy framework should call the extension in the synchronous foreground policy refresh.
0x000004FB	This driver has been blocked from loading
0x000004FC	A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image.
0x000004FD	Windows cannot open this program since it has been disabled.
0x000004FE	Windows cannot open this program because the license enforcement system has been tampered with or become corrupted.
0x000004FF	A transaction recover failed.
0x00000500	The current thread has already been converted to a fiber.
0x00000501	The current thread has already been converted from a fiber.
0x00000502	The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
0x00000503	Data present in one of the parameters is more than the function can operate on.
0x00000504	An attempt to do an operation on a debug object failed because the object is in the process of being deleted.
0x00000505	An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.
0x00000506	%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator.
0x00000507	Insufficient information exists to identify the cause of failure.
0x00000508	The parameter passed to a C runtime function is incorrect.
0x00000509	The operation occurred beyond the valid data length of the file.
0x0000050A	The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service.
0x0000050B	The process hosting the driver for this device has been terminated.
0x0000050C	An operation attempted to exceed an implementation-defined limit.
0x0000050D	Either the target process, or the target thread's containing process, is a protected process.
0x0000050E	The service notification client is lagging too far behind the current state of services in the machine.
0x0000050F	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.
0x00000510	The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.
0x00000511	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.
0x00000512	A thread involved in this operation appears to be unresponsive.
0x00000513	Indicates a particular Security ID may not be assigned as the label of an object.
0x00000514	Not all privileges or groups referenced are assigned to the caller.
0x00000515	Some mapping between account names and security IDs was not done.
0x00000516	No system quota limits are specifically set for this account.
0x00000517	No encryption key is available. A well-known encryption key was returned.
0x00000518	The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.
0x00000519	The revision level is unknown.
0x0000051A	Indicates two revision levels are incompatible.
0x0000051B	This security ID may not be assigned as the owner of this object.
0x0000051C	This security ID may not be assigned as the primary group of an object.
0x0000051D	An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
0x0000051E	The group may not be disabled.
0x0000051F	We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.
0x00000520	A specified logon session does not exist. It may already have been terminated.
0x00000521	A specified privilege does not exist.
0x00000522	A required privilege is not held by the client.
0x00000523	The name provided is not a properly formed account name.
0x00000524	The specified account already exists.
0x00000525	The specified account does not exist.
0x00000526	The specified group already exists.
0x00000527	The specified group does not exist.
0x00000528	Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.
0x00000529	The specified user account is not a member of the specified group account.
0x0000052A	This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon.
0x0000052B	Unable to update the password. The value provided as the current password is incorrect.
0x0000052C	Unable to update the password. The value provided for the new password contains values that are not allowed in passwords.
0x0000052D	Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain.
0x0000052E	The user name or password is incorrect.
0x0000052F	Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.
0x00000530	Your account has time restrictions that keep you from signing in right now.
0x00000531	This user isn't allowed to sign in to this computer.
0x00000532	The password for this account has expired.
0x00000533	This user can't sign in because this account is currently disabled.
0x00000534	No mapping between account names and security IDs was done.
0x00000535	Too many local user identifiers (LUIDs) were requested at one time.
0x00000536	No more local user identifiers (LUIDs) are available.
0x00000537	The subauthority part of a security ID is invalid for this particular use.
0x00000538	The access control list (ACL) structure is invalid.
0x00000539	The security ID structure is invalid.
0x0000053A	The security descriptor structure is invalid.
0x0000053C	The inherited access control list (ACL) or access control entry (ACE) could not be built.
0x0000053D	The server is currently disabled.
0x0000053E	The server is currently enabled.
0x0000053F	The value provided was an invalid value for an identifier authority.
0x00000540	No more memory is available for security information updates.
0x00000541	The specified attributes are invalid, or incompatible with the attributes for the group as a whole.
0x00000542	Either a required impersonation level was not provided, or the provided impersonation level is invalid.
0x00000543	Cannot open an anonymous level security token.
0x00000544	The validation information class requested was invalid.
0x00000545	The type of the token is inappropriate for its attempted use.
0x00000546	Unable to perform a security operation on an object that has no associated security.
0x00000547	Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
0x00000548	The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation.
0x00000549	The domain was in the wrong state to perform the security operation.
0x0000054A	This operation is only allowed for the Primary Domain Controller of the domain.
0x0000054B	The specified domain either does not exist or could not be contacted.
0x0000054C	The specified domain already exists.
0x0000054D	An attempt was made to exceed the limit on the number of domains per server.
0x0000054E	Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk.
0x0000054F	An internal error occurred.
0x00000550	Generic access types were contained in an access mask which should already be mapped to nongeneric types.
0x00000551	A security descriptor is not in the right format (absolute or self-relative).
0x00000552	The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.
0x00000553	Cannot start a new logon session with an ID that is already in use.
0x00000554	A specified authentication package is unknown.
0x00000555	The logon session is not in a state that is consistent with the requested operation.
0x00000556	The logon session ID is already in use.
0x00000557	A logon request contained an invalid logon type value.
0x00000558	Unable to impersonate using a named pipe until data has been read from that pipe.
0x00000559	The transaction state of a registry subtree is incompatible with the requested operation.
0x0000055A	An internal security database corruption has been encountered.
0x0000055B	Cannot perform this operation on built-in accounts.
0x0000055C	Cannot perform this operation on this built-in special group.
0x0000055D	Cannot perform this operation on this built-in special user.
0x0000055E	The user cannot be removed from a group because the group is currently the user's primary group.
0x0000055F	The token is already in use as a primary token.
0x00000560	The specified local group does not exist.
0x00000561	The specified account name is not a member of the group.
0x00000562	The specified account name is already a member of the group.
0x00000563	The specified local group already exists.
0x00000564	Logon failure: the user has not been granted the requested logon type at this computer.
0x00000565	The maximum number of secrets that may be stored in a single system has been exceeded.
0x00000566	The length of a secret exceeds the maximum length allowed.
0x00000567	The local security authority database contains an internal inconsistency.
0x00000568	During a logon attempt, the user's security context accumulated too many security IDs.
0x00000569	Logon failure: the user has not been granted the requested logon type at this computer.
0x0000056A	A cross-encrypted password is necessary to change a user password.
0x0000056B	A member could not be added to or removed from the local group because the member does not exist.
0x0000056C	A new member could not be added to a local group because the member has the wrong account type.
0x0000056D	Too many security IDs have been specified.
0x0000056E	A cross-encrypted password is necessary to change this user password.
0x0000056F	Indicates an ACL contains no inheritable components.
0x00000570	The file or directory is corrupted and unreadable.
0x00000571	The disk structure is corrupted and unreadable.
0x00000572	There is no user session key for the specified logon session.
0x00000573	The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept.
0x00000574	The target account name is incorrect.
0x00000575	Mutual Authentication failed. The server's password is out of date at the domain controller.
0x00000576	There is a time and/or date difference between the client and server.
0x00000577	This operation cannot be performed on the current domain.
0x00000578	Invalid window handle.
0x00000579	Invalid menu handle.
0x0000057A	Invalid cursor handle.
0x0000057B	Invalid accelerator table handle.
0x0000057C	Invalid hook handle.
0x0000057D	Invalid handle to a multiple-window position structure.
0x0000057E	Cannot create a top-level child window.
0x0000057F	Cannot find window class.
0x00000580	Invalid window; it belongs to other thread.
0x00000581	Hot key is already registered.
0x00000582	Class already exists.
0x00000583	Class does not exist.
0x00000584	Class still has open windows.
0x00000585	Invalid index.
0x00000586	Invalid icon handle.
0x00000587	Using private DIALOG window words.
0x00000588	The list box identifier was not found.
0x00000589	No wildcards were found.
0x0000058A	Thread does not have a clipboard open.
0x0000058B	Hot key is not registered.
0x0000058C	The window is not a valid dialog window.
0x0000058D	Control ID not found.
0x0000058E	Invalid message for a combo box because it does not have an edit control.
0x0000058F	The window is not a combo box.
0x00000590	Height must be less than 256.
0x00000591	Invalid device context (DC) handle.
0x00000592	Invalid hook procedure type.
0x00000593	Invalid hook procedure.
0x00000594	Cannot set nonlocal hook without a module handle.
0x00000595	This hook procedure can only be set globally.
0x00000596	The journal hook procedure is already installed.
0x00000597	The hook procedure is not installed.
0x00000598	Invalid message for single-selection list box.
0x00000599	LB_SETCOUNT sent to non-lazy list box.
0x0000059A	This list box does not support tab stops.
0x0000059B	Cannot destroy object created by another thread.
0x0000059C	Child windows cannot have menus.
0x0000059D	The window does not have a system menu.
0x0000059E	Invalid message box style.
0x0000059F	Invalid system-wide (SPI_*) parameter.
0x000005A0	Screen already locked.
0x000005A1	All handles to windows in a multiple-window position structure must have the same parent.
0x000005A2	The window is not a child window.
0x000005A3	Invalid GW_* command.
0x000005A4	Invalid thread identifier.
0x000005A5	Cannot process a message from a window that is not a multiple document interface (MDI) window.
0x000005A6	Popup menu already active.
0x000005A7	The window does not have scroll bars.
0x000005A8	Scroll bar range cannot be greater than MAXLONG.
0x000005A9	Cannot show or remove the window in the way specified.
0x000005AA	Insufficient system resources exist to complete the requested service.
0x000005AB	Insufficient system resources exist to complete the requested service.
0x000005AC	Insufficient system resources exist to complete the requested service.
0x000005AD	Insufficient quota to complete the requested service.
0x000005AE	Insufficient quota to complete the requested service.
0x000005AF	The paging file is too small for this operation to complete.
0x000005B0	A menu item was not found.
0x000005B1	Invalid keyboard layout handle.
0x000005B2	Hook type not allowed.
0x000005B3	This operation requires an interactive window station.
0x000005B4	This operation returned because the timeout period expired.
0x000005B5	Invalid monitor handle.
0x000005B6	Incorrect size argument.
0x000005B7	The symbolic link cannot be followed because its type is disabled.
0x000005B8	This application does not support the current operation on symbolic links.
0x000005B9	Windows was unable to parse the requested XML data.
0x000005BA	An error was encountered while processing an XML digital signature.
0x000005BB	This application must be restarted.
0x000005BC	The caller made the connection request in the wrong routing compartment.
0x000005BD	There was an AuthIP failure when attempting to connect to the remote host.
0x000005BE	Insufficient NVRAM resources exist to complete the requested service. A reboot might be required.
0x000005BF	Unable to finish the requested operation because the specified process is not a GUI process.
0x000005DC	The event log file is corrupted.
0x000005DD	No event log file could be opened, so the event logging service did not start.
0x000005DE	The event log file is full.
0x000005DF	The event log file has changed between read operations.
0x000005E0	The specified Job already has a container assigned to it.
0x000005E1	The specified Job does not have a container assigned to it.
0x0000060E	The specified task name is invalid.
0x0000060F	The specified task index is invalid.
0x00000610	The specified thread is already joining a task.
0x00000641	The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.
0x00000642	User cancelled installation.
0x00000643	Fatal error during installation.
0x00000644	Installation suspended, incomplete.
0x00000645	This action is only valid for products that are currently installed.
0x00000646	Feature ID not registered.
0x00000647	Component ID not registered.
0x00000648	Unknown property.
0x00000649	Handle is in an invalid state.
0x0000064A	The configuration data for this product is corrupt. Contact your support personnel.
0x0000064B	Component qualifier not present.
0x0000064C	The installation source for this product is not available. Verify that the source exists and that you can access it.
0x0000064D	This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
0x0000064E	Product is uninstalled.
0x0000064F	SQL query syntax invalid or unsupported.
0x00000650	Record field does not exist.
0x00000651	The device has been removed.
0x00000652	Another installation is already in progress. Complete that installation before proceeding with this install.
0x00000653	This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package.
0x00000654	This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
0x00000655	There was an error starting the Windows Installer service user interface. Contact your support personnel.
0x00000656	Error opening installation log file. Verify that the specified log file location exists and that you can write to it.
0x00000657	The language of this installation package is not supported by your system.
0x00000658	Error applying transforms. Verify that the specified transform paths are valid.
0x00000659	This installation is forbidden by system policy. Contact your system administrator.
0x0000065A	Function could not be executed.
0x0000065B	Function failed during execution.
0x0000065C	Invalid or unknown table specified.
0x0000065D	Data supplied is of wrong type.
0x0000065E	Data of this type is not supported.
0x0000065F	The Windows Installer service failed to start. Contact your support personnel.
0x00000660	The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder.
0x00000661	This installation package is not supported by this processor type. Contact your product vendor.
0x00000662	Component not used on this computer.
0x00000663	This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package.
0x00000664	This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.
0x00000665	This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service.
0x00000666	Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.
0x00000667	Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
0x00000668	Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator.
0x00000669	The requested operation completed successfully. The system will be restarted so the changes can take effect.
0x0000066A	The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade.
0x0000066B	The update package is not permitted by software restriction policy.
0x0000066C	One or more customizations are not permitted by software restriction policy.
0x0000066D	The Windows Installer does not permit installation from a Remote Desktop Connection.
0x0000066E	Uninstallation of the update package is not supported.
0x0000066F	The update is not applied to this product.
0x00000670	No valid sequence could be found for the set of updates.
0x00000671	Update removal was disallowed by policy.
0x00000672	The XML update data is invalid.
0x00000673	Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update.
0x00000674	The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state.
0x00000675	A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.
0x00000676	The app that you are trying to run is not supported on this version of Windows.
0x00000677	The operation was blocked as the process prohibits dynamic code generation.
0x00000678	The objects are not identical.
0x00000679	The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard.
0x0000067C	The thread context could not be updated because this has been restricted for the process.
0x0000067D	An invalid cross-partition private file/section access was attempted.
0x0000067E	A return address hijack is being attempted. This is supported by the operating system when user-mode shadow stacks are enabled.
0x000006A4	The string binding is invalid.
0x000006A5	The binding handle is not the correct type.
0x000006A6	The binding handle is invalid.
0x000006A7	The RPC protocol sequence is not supported.
0x000006A8	The RPC protocol sequence is invalid.
0x000006A9	The string universal unique identifier (UUID) is invalid.
0x000006AA	The endpoint format is invalid.
0x000006AB	The network address is invalid.
0x000006AC	No endpoint was found.
0x000006AD	The timeout value is invalid.
0x000006AE	The object universal unique identifier (UUID) was not found.
0x000006AF	The object universal unique identifier (UUID) has already been registered.
0x000006B0	The type universal unique identifier (UUID) has already been registered.
0x000006B1	The RPC server is already listening.
0x000006B2	No protocol sequences have been registered.
0x000006B3	The RPC server is not listening.
0x000006B4	The manager type is unknown.
0x000006B5	The interface is unknown.
0x000006B6	There are no bindings.
0x000006B7	There are no protocol sequences.
0x000006B8	The endpoint cannot be created.
0x000006B9	Not enough resources are available to complete this operation.
0x000006BA	The RPC server is unavailable.
0x000006BB	The RPC server is too busy to complete this operation.
0x000006BC	The network options are invalid.
0x000006BD	There are no remote procedure calls active on this thread.
0x000006BE	The remote procedure call failed.
0x000006BF	The remote procedure call failed and did not execute.
0x000006C0	A remote procedure call (RPC) protocol error occurred.
0x000006C1	Access to the HTTP proxy is denied.
0x000006C2	The transfer syntax is not supported by the RPC server.
0x000006C4	The universal unique identifier (UUID) type is not supported.
0x000006C5	The tag is invalid.
0x000006C6	The array bounds are invalid.
0x000006C7	The binding does not contain an entry name.
0x000006C8	The name syntax is invalid.
0x000006C9	The name syntax is not supported.
0x000006CB	No network address is available to use to construct a universal unique identifier (UUID).
0x000006CC	The endpoint is a duplicate.
0x000006CD	The authentication type is unknown.
0x000006CE	The maximum number of calls is too small.
0x000006CF	The string is too long.
0x000006D0	The RPC protocol sequence was not found.
0x000006D1	The procedure number is out of range.
0x000006D2	The binding does not contain any authentication information.
0x000006D3	The authentication service is unknown.
0x000006D4	The authentication level is unknown.
0x000006D5	The security context is invalid.
0x000006D6	The authorization service is unknown.
0x000006D7	The entry is invalid.
0x000006D8	The server endpoint cannot perform the operation.
0x000006D9	There are no more endpoints available from the endpoint mapper.
0x000006DA	No interfaces have been exported.
0x000006DB	The entry name is incomplete.
0x000006DC	The version option is invalid.
0x000006DD	There are no more members.
0x000006DE	There is nothing to unexport.
0x000006DF	The interface was not found.
0x000006E0	The entry already exists.
0x000006E1	The entry is not found.
0x000006E2	The name service is unavailable.
0x000006E3	The network address family is invalid.
0x000006E4	The requested operation is not supported.
0x000006E5	No security context is available to allow impersonation.
0x000006E6	An internal error occurred in a remote procedure call (RPC).
0x000006E7	The RPC server attempted an integer division by zero.
0x000006E8	An addressing error occurred in the RPC server.
0x000006E9	A floating-point operation at the RPC server caused a division by zero.
0x000006EA	A floating-point underflow occurred at the RPC server.
0x000006EB	A floating-point overflow occurred at the RPC server.
0x000006EC	The list of RPC servers available for the binding of auto handles has been exhausted.
0x000006ED	Unable to open the character translation table file.
0x000006EE	The file containing the character translation table has fewer than 512 bytes.
0x000006EF	A null context handle was passed from the client to the host during a remote procedure call.
0x000006F1	The context handle changed during a remote procedure call.
0x000006F2	The binding handles passed to a remote procedure call do not match.
0x000006F3	The stub is unable to get the remote procedure call handle.
0x000006F4	A null reference pointer was passed to the stub.
0x000006F5	The enumeration value is out of range.
0x000006F6	The byte count is too small.
0x000006F7	The stub received bad data.
0x000006F8	The supplied user buffer is not valid for the requested operation.
0x000006F9	The disk media is not recognized. It may not be formatted.
0x000006FA	The workstation does not have a trust secret.
0x000006FB	The security database on the server does not have a computer account for this workstation trust relationship.
0x000006FC	The trust relationship between the primary domain and the trusted domain failed.
0x000006FD	The trust relationship between this workstation and the primary domain failed.
0x000006FE	The network logon failed.
0x000006FF	A remote procedure call is already in progress for this thread.
0x00000700	An attempt was made to logon, but the network logon service was not started.
0x00000701	The user's account has expired.
0x00000702	The redirector is in use and cannot be unloaded.
0x00000703	The specified printer driver is already installed.
0x00000704	The specified port is unknown.
0x00000705	The printer driver is unknown.
0x00000706	The print processor is unknown.
0x00000707	The specified separator file is invalid.
0x00000708	The specified priority is invalid.
0x00000709	The printer name is invalid.
0x0000070A	The printer already exists.
0x0000070B	The printer command is invalid.
0x0000070C	The specified datatype is invalid.
0x0000070D	The environment specified is invalid.
0x0000070E	There are no more bindings.
0x0000070F	The account used is an interdomain trust account. Use your global user account or local user account to access this server.
0x00000710	The account used is a computer account. Use your global user account or local user account to access this server.
0x00000711	The account used is a server trust account. Use your global user account or local user account to access this server.
0x00000712	The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain.
0x00000713	The server is in use and cannot be unloaded.
0x00000714	The specified image file did not contain a resource section.
0x00000715	The specified resource type cannot be found in the image file.
0x00000716	The specified resource name cannot be found in the image file.
0x00000717	The specified resource language ID cannot be found in the image file.
0x00000718	Not enough quota is available to process this command.
0x00000719	No interfaces have been registered.
0x0000071A	The remote procedure call was cancelled.
0x0000071B	The binding handle does not contain all required information.
0x0000071C	A communications failure occurred during a remote procedure call.
0x0000071D	The requested authentication level is not supported.
0x0000071E	No principal name registered.
0x0000071F	The error specified is not a valid Windows RPC error code.
0x00000720	A UUID that is valid only on this computer has been allocated.
0x00000721	A security package specific error occurred.
0x00000722	Thread is not canceled.
0x00000723	Invalid operation on the encoding/decoding handle.
0x00000724	Incompatible version of the serializing package.
0x00000725	Incompatible version of the RPC stub.
0x00000726	The RPC pipe object is invalid or corrupted.
0x00000727	An invalid operation was attempted on an RPC pipe object.
0x00000728	Unsupported RPC pipe version.
0x00000729	HTTP proxy server rejected the connection because the cookie authentication failed.
0x0000072A	The RPC server is suspended, and could not be resumed for this request. The call did not execute.
0x0000072B	The RPC call contains too many handles to be transmitted in a single request.
0x0000072C	The RPC call contains a handle that differs from the declared handle type.
0x0000076A	The group member was not found.
0x0000076B	The endpoint mapper database entry could not be created.
0x0000076C	The object universal unique identifier (UUID) is the nil UUID.
0x0000076D	The specified time is invalid.
0x0000076E	The specified form name is invalid.
0x0000076F	The specified form size is invalid.
0x00000770	The specified printer handle is already being waited on
0x00000771	The specified printer has been deleted.
0x00000772	The state of the printer is invalid.
0x00000773	The user's password must be changed before signing in.
0x00000774	Could not find the domain controller for this domain.
0x00000775	The referenced account is currently locked out and may not be logged on to.
0x00000776	The object exporter specified was not found.
0x00000777	The object specified was not found.
0x00000778	The object resolver set specified was not found.
0x00000779	Some data remains to be sent in the request buffer.
0x0000077A	Invalid asynchronous remote procedure call handle.
0x0000077B	Invalid asynchronous RPC call handle for this operation.
0x0000077C	The RPC pipe object has already been closed.
0x0000077D	The RPC call completed before all pipes were processed.
0x0000077E	No more data is available from the RPC pipe.
0x0000077F	No site name is available for this machine.
0x00000780	The file cannot be accessed by the system.
0x00000781	The name of the file cannot be resolved by the system.
0x00000782	The entry is not of the expected type.
0x00000783	Not all object UUIDs could be exported to the specified entry.
0x00000784	Interface could not be exported to the specified entry.
0x00000785	The specified profile entry could not be added.
0x00000786	The specified profile element could not be added.
0x00000787	The specified profile element could not be removed.
0x00000788	The group element could not be added.
0x00000789	The group element could not be removed.
0x0000078A	The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers.
0x0000078B	The context has expired and can no longer be used.
0x0000078C	The current user's delegated trust creation quota has been exceeded.
0x0000078D	The total delegated trust creation quota has been exceeded.
0x0000078E	The current user's delegated trust deletion quota has been exceeded.
0x0000078F	The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer.
0x00000790	Remote connections to the Print Spooler are blocked by a policy set on your machine.
0x00000791	Authentication failed because NTLM authentication has been disabled.
0x00000792	Logon Failure: EAS policy requires that the user change their password before this operation can be performed.
0x00000793	An administrator has restricted sign in. To sign in, make sure your device is connected to the Internet, and have your administrator sign in first.
0x000007D0	The pixel format is invalid.
0x000007D1	The specified driver is invalid.
0x000007D2	The window style or class attribute is invalid for this operation.
0x000007D3	The requested metafile operation is not supported.
0x000007D4	The requested transformation operation is not supported.
0x000007D5	The requested clipping operation is not supported.
0x000007DA	The specified color management module is invalid.
0x000007DB	The specified color profile is invalid.
0x000007DC	The specified tag was not found.
0x000007DD	A required tag is not present.
0x000007DE	The specified tag is already present.
0x000007DF	The specified color profile is not associated with the specified device.
0x000007E0	The specified color profile was not found.
0x000007E1	The specified color space is invalid.
0x000007E2	Image Color Management is not enabled.
0x000007E3	There was an error while deleting the color transform.
0x000007E4	The specified color transform is invalid.
0x000007E5	The specified transform does not match the bitmap's color space.
0x000007E6	The specified named color index is not present in the profile.
0x000007E7	The specified profile is intended for a device of a different type than the specified device.
0x0000083C	The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified.
0x0000083D	The network connection was made successfully using default credentials.
0x0000089A	The specified username is invalid.
0x000008CA	This network connection does not exist.
0x00000961	This network connection has files open or requests pending.
0x00000962	Active connections still exist.
0x00000964	The device is in use by an active process and cannot be disconnected.
0x00000BB8	The specified print monitor is unknown.
0x00000BB9	The specified printer driver is currently in use.
0x00000BBA	The spool file was not found.
0x00000BBB	A StartDocPrinter call was not issued.
0x00000BBC	An AddJob call was not issued.
0x00000BBD	The specified print processor has already been installed.
0x00000BBE	The specified print monitor has already been installed.
0x00000BBF	The specified print monitor does not have the required functions.
0x00000BC0	The specified print monitor is currently in use.
0x00000BC1	The requested operation is not allowed when there are jobs queued to the printer.
0x00000BC2	The requested operation is successful. Changes will not be effective until the system is rebooted.
0x00000BC3	The requested operation is successful. Changes will not be effective until the service is restarted.
0x00000BC4	No printers were found.
0x00000BC5	The printer driver is known to be unreliable.
0x00000BC6	The printer driver is known to harm the system.
0x00000BC7	The specified printer driver package is currently in use.
0x00000BC8	Unable to find a core driver package that is required by the printer driver package.
0x00000BC9	The requested operation failed. A system reboot is required to roll back changes made.
0x00000BCA	The requested operation failed. A system reboot has been initiated to roll back changes made.
0x00000BCB	The specified printer driver was not found on the system and needs to be downloaded.
0x00000BCC	The requested print job has failed to print. A print system update requires the job to be resubmitted.
0x00000BCD	The printer driver does not contain a valid manifest, or contains too many manifests.
0x00000BCE	The specified printer cannot be shared.
0x00000BEA	The operation was paused.
0x00000BF4	The condition supplied for the app execution request was not satisfied, so the request was not performed.
0x00000BF5	The supplied handle has been invalidated and may not be used for the requested operation.
0x00000BF6	The supplied host generation has been invalidated and may not be used for the requested operation.
0x00000BF7	An attempt to register a process failed because the target host was not in a valid state to receive process registrations.
0x00000BF8	The host is not in a valid state to support the execution request.
0x00000BF9	The operation was not completed because a required resource donor was not found for the host.
0x00000BFA	The operation was not completed because an unexpected host ID was encountered.
0x00000BFB	The operation was not completed because the specified user was not known to the service.
0x00000F6E	Reissue the given operation as a cached IO operation
0x00000FA0	WINS encountered an error while processing the command.
0x00000FA1	The local WINS cannot be deleted.
0x00000FA2	The importation from the file failed.
0x00000FA3	The backup failed. Was a full backup done before?
0x00000FA4	The backup failed. Check the directory to which you are backing the database.
0x00000FA5	The name does not exist in the WINS database.
0x00000FA6	Replication with a nonconfigured partner is not allowed.
0x00000FD2	The version of the supplied content information is not supported.
0x00000FD3	The supplied content information is malformed.
0x00000FD4	The requested data cannot be found in local or peer caches.
0x00000FD5	No more data is available or required.
0x00000FD6	The supplied object has not been initialized.
0x00000FD7	The supplied object has already been initialized.
0x00000FD8	A shutdown operation is already in progress.
0x00000FD9	The supplied object has already been invalidated.
0x00000FDA	An element already exists and was not replaced.
0x00000FDB	Can not cancel the requested operation as it has already been completed.
0x00000FDC	Can not perform the requested operation because it has already been carried out.
0x00000FDD	An operation accessed data beyond the bounds of valid data.
0x00000FDE	The requested version is not supported.
0x00000FDF	A configuration value is invalid.
0x00000FE0	The SKU is not licensed.
0x00000FE1	PeerDist Service is still initializing and will be available shortly.
0x00000FE2	Communication with one or more computers will be temporarily blocked due to recent errors.
0x00001004	The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address.
0x00001068	The GUID passed was not recognized as valid by a WMI data provider.
0x00001069	The instance name passed was not recognized as valid by a WMI data provider.
0x0000106A	The data item ID passed was not recognized as valid by a WMI data provider.
0x0000106B	The WMI request could not be completed and should be retried.
0x0000106C	The WMI data provider could not be located.
0x0000106D	The WMI data provider references an instance set that has not been registered.
0x0000106E	The WMI data block or event notification has already been enabled.
0x0000106F	The WMI data block is no longer available.
0x00001070	The WMI data service is not available.
0x00001071	The WMI data provider failed to carry out the request.
0x00001072	The WMI MOF information is not valid.
0x00001073	The WMI registration information is not valid.
0x00001074	The WMI data block or event notification has already been disabled.
0x00001075	The WMI data item or data block is read only.
0x00001076	The WMI data item or data block could not be changed.
0x0000109A	This operation is only valid in the context of an app container.
0x0000109B	This application can only run in the context of an app container.
0x0000109C	This functionality is not supported in the context of an app container.
0x0000109D	The length of the SID supplied is not a valid length for app container SIDs.
0x000010CC	The media identifier does not represent a valid medium.
0x000010CD	The library identifier does not represent a valid library.
0x000010CE	The media pool identifier does not represent a valid media pool.
0x000010CF	The drive and medium are not compatible or exist in different libraries.
0x000010D0	The medium currently exists in an offline library and must be online to perform this operation.
0x000010D1	The operation cannot be performed on an offline library.
0x000010D2	The library, drive, or media pool is empty.
0x000010D3	The library, drive, or media pool must be empty to perform this operation.
0x000010D4	No media is currently available in this media pool or library.
0x000010D5	A resource required for this operation is disabled.
0x000010D6	The media identifier does not represent a valid cleaner.
0x000010D7	The drive cannot be cleaned or does not support cleaning.
0x000010D8	The object identifier does not represent a valid object.
0x000010D9	Unable to read from or write to the database.
0x000010DA	The database is full.
0x000010DB	The medium is not compatible with the device or media pool.
0x000010DC	The resource required for this operation does not exist.
0x000010DD	The operation identifier is not valid.
0x000010DE	The media is not mounted or ready for use.
0x000010DF	The device is not ready for use.
0x000010E0	The operator or administrator has refused the request.
0x000010E1	The drive identifier does not represent a valid drive.
0x000010E2	Library is full. No slot is available for use.
0x000010E3	The transport cannot access the medium.
0x000010E4	Unable to load the medium into the drive.
0x000010E5	Unable to retrieve the drive status.
0x000010E6	Unable to retrieve the slot status.
0x000010E7	Unable to retrieve status about the transport.
0x000010E8	Cannot use the transport because it is already in use.
0x000010E9	Unable to open or close the inject/eject port.
0x000010EA	Unable to eject the medium because it is in a drive.
0x000010EB	A cleaner slot is already reserved.
0x000010EC	A cleaner slot is not reserved.
0x000010ED	The cleaner cartridge has performed the maximum number of drive cleanings.
0x000010EE	Unexpected on-medium identifier.
0x000010EF	The last remaining item in this group or resource cannot be deleted.
0x000010F0	The message provided exceeds the maximum size allowed for this parameter.
0x000010F1	The volume contains system or paging files.
0x000010F2	The media type cannot be removed from this library since at least one drive in the library reports it can support this media type.
0x000010F3	This offline media cannot be mounted on this system since no enabled drives are present which can be used.
0x000010F4	A cleaner cartridge is present in the tape library.
0x000010F5	Cannot use the inject/eject port because it is not empty.
0x000010FE	This file is currently not available for use on this computer.
0x000010FF	The remote storage service is not operational at this time.
0x00001100	The remote storage service encountered a media error.
0x00001126	The file or directory is not a reparse point.
0x00001127	The reparse point attribute cannot be set because it conflicts with an existing attribute.
0x00001128	The data present in the reparse point buffer is invalid.
0x00001129	The tag present in the reparse point buffer is invalid.
0x0000112A	There is a mismatch between the tag specified in the request and the tag present in the reparse point.
0x0000112B	The object manager encountered a reparse point while retrieving an object.
0x00001130	Fast Cache data not found.
0x00001131	Fast Cache data expired.
0x00001132	Fast Cache data corrupt.
0x00001133	Fast Cache data has exceeded its max size and cannot be updated.
0x00001134	Fast Cache has been ReArmed and requires a reboot until it can be updated.
0x00001144	Secure Boot detected that rollback of protected data has been attempted.
0x00001145	The value is protected by Secure Boot policy and cannot be modified or deleted.
0x00001146	The Secure Boot policy is invalid.
0x00001147	A new Secure Boot policy did not contain the current publisher on its update list.
0x00001148	The Secure Boot policy is either not signed or is signed by a non-trusted signer.
0x00001149	Secure Boot is not enabled on this machine.
0x0000114A	Secure Boot requires that certain files and drivers are not replaced by other files or drivers.
0x0000114B	The Secure Boot Supplemental Policy file was not authorized on this machine.
0x0000114C	The Supplemental Policy is not recognized on this device.
0x0000114D	The Antirollback version was not found in the Secure Boot Policy.
0x0000114E	The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device.
0x0000114F	The Secure Boot policy file has an older Antirollback Version than this device.
0x00001150	The Secure Boot policy file does not match the upgraded legacy policy.
0x00001151	The Secure Boot policy file is required but could not be found.
0x00001152	Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy.
0x00001153	Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy.
0x00001158	The copy offload read operation is not supported by a filter.
0x00001159	The copy offload write operation is not supported by a filter.
0x0000115A	The copy offload read operation is not supported for the file.
0x0000115B	The copy offload write operation is not supported for the file.
0x0000115C	This file is currently associated with a different stream id.
0x0000115D	The volume must undergo garbage collection.
0x0000115E	The WOF driver encountered a corruption in WIM image's Header.
0x0000115F	The WOF driver encountered a corruption in WIM image's Resource Table.
0x00001160	The WOF driver encountered a corruption in the compressed file's Resource Table.
0x00001194	Single Instance Storage is not available on this volume.
0x000011C6	System Integrity detected that policy rollback has been attempted.
0x000011C7	Your organization used Device Guard to block this app. Contact your support person for more info.
0x000011C8	The System Integrity policy is invalid.
0x000011C9	The System Integrity policy is either not signed or is signed by a non-trusted signer.
0x000011CA	The number of System Integrity policies is out of limit.
0x000011CB	The Code Integrity supplemental policy is not authorized by a Code Integrity base policy.
0x000011D0	Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled.
0x000011D1	The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS.
0x000011DA	The Platform Manifest file was not authorized on this machine.
0x000011DB	The Platform Manifest file was not valid.
0x000011DC	The file is not authorized on this platform because an entry was not found in the Platform Manifest.
0x000011DD	The catalog is not authorized on this platform because an entry was not found in the Platform Manifest.
0x000011DE	The file is not authorized on this platform because a Binary ID was not found in the embedded signature.
0x000011DF	No active Platform Manifest exists on this system.
0x000011E0	The Platform Manifest file was not properly signed.
0x00001389	The operation cannot be completed because other resources are dependent on this resource.
0x0000138A	The cluster resource dependency cannot be found.
0x0000138B	The cluster resource cannot be made dependent on the specified resource because it is already dependent.
0x0000138C	The cluster resource is not online.
0x0000138D	A cluster node is not available for this operation.
0x0000138E	The cluster resource is not available.
0x0000138F	The cluster resource could not be found.
0x00001390	The cluster is being shut down.
0x00001391	A cluster node cannot be evicted from the cluster unless the node is down or it is the last node.
0x00001392	The object already exists.
0x00001393	The object is already in the list.
0x00001394	The cluster group is not available for any new requests.
0x00001395	The cluster group could not be found.
0x00001396	The operation could not be completed because the cluster group is not online.
0x00001397	The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource.
0x00001398	The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group.
0x00001399	The cluster resource could not be created in the specified resource monitor.
0x0000139A	The cluster resource could not be brought online by the resource monitor.
0x0000139B	The operation could not be completed because the cluster resource is online.
0x0000139C	The cluster resource could not be deleted or brought offline because it is the quorum resource.
0x0000139D	The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource.
0x0000139E	The cluster software is shutting down.
0x0000139F	The group or resource is not in the correct state to perform the requested operation.
0x000013A0	The properties were stored but not all changes will take effect until the next time the resource is brought online.
0x000013A1	The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class.
0x000013A2	The cluster resource could not be deleted since it is a core resource.
0x000013A3	The quorum resource failed to come online.
0x000013A4	The quorum log could not be created or mounted successfully.
0x000013A5	The cluster log is corrupt.
0x000013A6	The record could not be written to the cluster log since it exceeds the maximum size.
0x000013A7	The cluster log exceeds its maximum size.
0x000013A8	No checkpoint record was found in the cluster log.
0x000013A9	The minimum required disk space needed for logging is not available.
0x000013AA	The cluster node failed to take control of the quorum resource because the resource is owned by another active node.
0x000013AB	A cluster network is not available for this operation.
0x000013AC	A cluster node is not available for this operation.
0x000013AD	All cluster nodes must be running to perform this operation.
0x000013AE	A cluster resource failed.
0x000013AF	The cluster node is not valid.
0x000013B0	The cluster node already exists.
0x000013B1	A node is in the process of joining the cluster.
0x000013B2	The cluster node was not found.
0x000013B3	The cluster local node information was not found.
0x000013B4	The cluster network already exists.
0x000013B5	The cluster network was not found.
0x000013B6	The cluster network interface already exists.
0x000013B7	The cluster network interface was not found.
0x000013B8	The cluster request is not valid for this object.
0x000013B9	The cluster network provider is not valid.
0x000013BA	The cluster node is down.
0x000013BB	The cluster node is not reachable.
0x000013BC	The cluster node is not a member of the cluster.
0x000013BD	A cluster join operation is not in progress.
0x000013BE	The cluster network is not valid.
0x000013C0	The cluster node is up.
0x000013C1	The cluster IP address is already in use.
0x000013C2	The cluster node is not paused.
0x000013C3	No cluster security context is available.
0x000013C4	The cluster network is not configured for internal cluster communication.
0x000013C5	The cluster node is already up.
0x000013C6	The cluster node is already down.
0x000013C7	The cluster network is already online.
0x000013C8	The cluster network is already offline.
0x000013C9	The cluster node is already a member of the cluster.
0x000013CA	The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network.
0x000013CB	One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network.
0x000013CC	This operation cannot currently be performed on the cluster group containing the quorum resource.
0x000013CD	The cluster quorum resource is not allowed to have any dependencies.
0x000013CE	The cluster node is paused.
0x000013CF	The cluster resource cannot be brought online. The owner node cannot run this resource.
0x000013D0	The cluster node is not ready to perform the requested operation.
0x000013D1	The cluster node is shutting down.
0x000013D2	The cluster join operation was aborted.
0x000013D3	The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet.
0x000013D4	This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor.
0x000013D5	The system configuration changed during the cluster join or form operation. The join or form operation was aborted.
0x000013D6	The specified resource type was not found.
0x000013D7	The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node.
0x000013D8	The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL.
0x000013D9	No authentication package could be registered with the RPC server.
0x000013DA	You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group.
0x000013DB	The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join.
0x000013DC	The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state.
0x000013DD	A non locker code got a request to reserve the lock for making global updates.
0x000013DE	The quorum disk could not be located by the cluster service.
0x000013DF	The backed up cluster database is possibly corrupt.
0x000013E0	A DFS root already exists in this cluster node.
0x000013E1	An attempt to modify a resource property failed because it conflicts with another existing property.
0x000013E2	This operation is not supported on a cluster without an Administrator Access Point.
0x00001702	An operation was attempted that is incompatible with the current membership state of the node.
0x00001703	The quorum resource does not contain the quorum log.
0x00001704	The membership engine requested shutdown of the cluster service on this node.
0x00001705	The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.
0x00001706	A matching cluster network for the specified IP address could not be found.
0x00001707	The actual data type of the property did not match the expected data type of the property.
0x00001708	The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer.
0x00001709	Two or more parameter values specified for a resource's properties are in conflict.
0x0000170A	This computer cannot be made a member of a cluster.
0x0000170B	This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed.
0x0000170C	A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster.
0x0000170D	The cluster configuration action has already been committed.
0x0000170E	The cluster configuration action could not be rolled back.
0x0000170F	The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node.
0x00001710	One or more nodes in the cluster are running a version of Windows that does not support this operation.
0x00001711	The name of the corresponding computer account doesn't match the Network Name for this resource.
0x00001712	No network adapters are available.
0x00001713	The cluster node has been poisoned.
0x00001714	The group is unable to accept the request since it is moving to another node.
0x00001715	The resource type cannot accept the request since is too busy performing another operation.
0x00001716	The call to the cluster resource DLL timed out.
0x00001717	The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted.
0x00001718	An internal cluster error occurred. A call to an invalid function was attempted.
0x00001719	A parameter value is out of acceptable range.
0x0000171A	A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required.
0x0000171B	An invalid cluster registry operation was attempted.
0x0000171C	An input string of characters is not properly terminated.
0x0000171D	An input string of characters is not in a valid format for the data it represents.
0x0000171E	An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress.
0x0000171F	An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress.
0x00001720	An internal cluster error occurred. Data was not properly initialized.
0x00001721	An error occurred while reading from a stream of data. An unexpected number of bytes was returned.
0x00001722	An error occurred while writing to a stream of data. The required number of bytes could not be written.
0x00001723	An error occurred while deserializing a stream of cluster data.
0x00001724	One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s).
0x00001725	A quorum of cluster nodes was not present to form a cluster.
0x00001726	The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address.
0x00001727	The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends.
0x00001728	Quorum resource cannot reside in the Available Storage group.
0x00001729	The dependencies for this resource are nested too deeply.
0x0000172A	The call into the resource DLL raised an unhandled exception.
0x0000172B	The RHS process failed to initialize.
0x0000172C	The Failover Clustering feature is not installed on this node.
0x0000172D	The resources must be online on the same node for this operation
0x0000172E	A new node can not be added since this cluster is already at its maximum number of nodes.
0x0000172F	This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit.
0x00001730	An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain.
0x00001731	This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed.
0x00001732	File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes.
0x00001733	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.
0x00001734	Only one instance of this resource type is allowed in the cluster.
0x00001735	Only one instance of this resource type is allowed per resource group.
0x00001736	The resource failed to come online due to the failure of one or more provider resources.
0x00001737	The resource has indicated that it cannot come online on any node.
0x00001738	The current operation cannot be performed on this group at this time.
0x00001739	The directory or file is not located on a cluster shared volume.
0x0000173A	The Security Descriptor does not meet the requirements for a cluster.
0x0000173B	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.
0x0000173C	This group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation.
0x0000173D	Back up is in progress. Please wait for backup completion before trying this operation again.
0x0000173E	The path does not belong to a cluster shared volume.
0x0000173F	The cluster shared volume is not locally mounted on this node.
0x00001740	The cluster watchdog is terminating.
0x00001741	A resource vetoed a move between two nodes because they are incompatible.
0x00001742	The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements.
0x00001743	The resource vetoed the call.
0x00001744	Resource could not start or run because it could not reserve sufficient system resources.
0x00001745	A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation.
0x00001746	A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation.
0x00001747	The requested operation can not be completed because the group is queued for an operation.
0x00001748	The requested operation can not be completed because a resource has locked status.
0x00001749	The resource cannot move to another node because a cluster shared volume vetoed the operation.
0x0000174A	A node drain is already in progress.
0x0000174B	Clustered storage is not connected to the node.
0x0000174C	The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS.
0x0000174D	The resource must be part of the Available Storage group to complete this action.
0x0000174E	CSVFS failed operation as volume is in redirected mode.
0x0000174F	CSVFS failed operation as volume is not in redirected mode.
0x00001750	Cluster properties cannot be returned at this time.
0x00001751	The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes.
0x00001752	The operation cannot be completed because the resource is in maintenance mode.
0x00001753	The operation cannot be completed because of cluster affinity conflicts
0x00001754	The operation cannot be completed because the resource is a replica virtual machine.
0x00001755	The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version.
0x00001756	Updating the cluster functional level failed because the cluster is running in fix quorum mode. Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automatically switch out of fix quorum mode, or stop and restart the cluster without the FixQuorum switch. Once the cluster is out of fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level.
0x00001757	The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster by using the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features will be available.
0x00001758	The cluster is currently performing a version upgrade.
0x00001759	The cluster did not successfully complete the version upgrade.
0x0000175A	The cluster node is in grace period.
0x0000175B	The operation has failed because CSV volume was not able to recover in time specified on this file object.
0x0000175C	The operation failed because the requested node is not currently part of active cluster membership.
0x0000175D	The operation failed because the requested cluster resource is currently unmonitored.
0x0000175E	The operation failed because a resource does not support running in an unmonitored state.
0x0000175F	The operation cannot be completed because a resource participates in replication.
0x00001760	The operation failed because the requested cluster node has been isolated
0x00001761	The operation failed because the requested cluster node has been quarantined
0x00001762	The operation failed because the specified database update condition was not met
0x00001763	A clustered space is in a degraded condition and the requested action cannot be completed at this time.
0x00001764	The operation failed because token delegation for this control is not supported.
0x00001765	The operation has failed because CSV has invalidated this file object.
0x00001766	This operation is supported only on the CSV coordinator node.
0x00001767	The cluster group set is not available for any further requests.
0x00001768	The cluster group set could not be found.
0x00001769	The action cannot be completed at this time because the cluster group set would fall below quorum and not be able to act as a provider.
0x0000176A	The specified parent fault domain is not found.
0x0000176B	The fault domain cannot be a child of the parent specified.
0x0000176C	Storage Spaces Direct has rejected the proposed fault domain changes because it impacts the fault tolerance of the storage.
0x0000176D	Storage Spaces Direct has rejected the proposed fault domain changes because it reduces the storage connected to the system.
0x0000176E	Cluster infrastructure file server creation failed because a valid non-empty file server name was not provided.
0x0000176F	The action cannot be completed because the cluster set management cluster is unreachable.
0x00001770	The specified file could not be encrypted.
0x00001771	The specified file could not be decrypted.
0x00001772	The specified file is encrypted and the user does not have the ability to decrypt it.
0x00001773	There is no valid encryption recovery policy configured for this system.
0x00001774	The required encryption driver is not loaded for this system.
0x00001775	The file was encrypted with a different encryption driver than is currently loaded.
0x00001776	There are no EFS keys defined for the user.
0x00001777	The specified file is not encrypted.
0x00001778	The specified file is not in the defined EFS export format.
0x00001779	The specified file is read only.
0x0000177A	The directory has been disabled for encryption.
0x0000177B	The server is not trusted for remote encryption operation.
0x0000177C	Recovery policy configured for this system contains invalid recovery certificate.
0x0000177D	The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file.
0x0000177E	The disk partition does not support file encryption.
0x0000177F	This machine is disabled for file encryption.
0x00001780	A newer system is required to decrypt this encrypted file.
0x00001781	The remote server sent an invalid response for a file being opened with Client Side Encryption.
0x00001782	Client Side Encryption is not supported by the remote server even though it claims to support it.
0x00001783	File is encrypted and should be opened in Client Side Encryption mode.
0x00001784	A new encrypted file is being created and a $EFS needs to be provided.
0x00001785	The SMB client requested a CSE FSCTL on a non-CSE file.
0x00001786	The requested operation was blocked by policy. For more information, contact your system administrator.
0x00001787	The specified file could not be encrypted with Windows Information Protection.
0x000017E6	The list of servers for this workgroup is not currently available
0x00001838	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.
0x0000186A	The object cannot be deleted from the local cluster because it is registered with the cluster set.
0x000019C8	Log service encountered an invalid log sector.
0x000019C9	Log service encountered a log sector with invalid block parity.
0x000019CA	Log service encountered a remapped log sector.
0x000019CB	Log service encountered a partial or incomplete log block.
0x000019CC	Log service encountered an attempt access data outside the active log range.
0x000019CD	Log service user marshalling buffers are exhausted.
0x000019CE	Log service encountered an attempt read from a marshalling area with an invalid read context.
0x000019CF	Log service encountered an invalid log restart area.
0x000019D0	Log service encountered an invalid log block version.
0x000019D1	Log service encountered an invalid log block.
0x000019D2	Log service encountered an attempt to read the log with an invalid read mode.
0x000019D3	Log service encountered a log stream with no restart area.
0x000019D4	Log service encountered a corrupted metadata file.
0x000019D5	Log service encountered a metadata file that could not be created by the log file system.
0x000019D6	Log service encountered a metadata file with inconsistent data.
0x000019D7	Log service encountered an attempt to erroneous allocate or dispose reservation space.
0x000019D8	Log service cannot delete log file or file system container.
0x000019D9	Log service has reached the maximum allowable containers allocated to a log file.
0x000019DA	Log service has attempted to read or write backward past the start of the log.
0x000019DB	Log policy could not be installed because a policy of the same type is already present.
0x000019DC	Log policy in question was not installed at the time of the request.
0x000019DD	The installed set of policies on the log is invalid.
0x000019DE	A policy on the log in question prevented the operation from completing.
0x000019DF	Log space cannot be reclaimed because the log is pinned by the archive tail.
0x000019E0	Log record is not a record in the log file.
0x000019E1	Number of reserved log records or the adjustment of the number of reserved log records is invalid.
0x000019E2	Reserved log space or the adjustment of the log space is invalid.
0x000019E3	An new or existing archive tail or base of the active log is invalid.
0x000019E4	Log space is exhausted.
0x000019E5	The log could not be set to the requested size.
0x000019E6	Log is multiplexed, no direct writes to the physical log is allowed.
0x000019E7	The operation failed because the log is a dedicated log.
0x000019E8	The operation requires an archive context.
0x000019E9	Log archival is in progress.
0x000019EA	The operation requires a non-ephemeral log, but the log is ephemeral.
0x000019EB	The log must have at least two containers before it can be read from or written to.
0x000019EC	A log client has already registered on the stream.
0x000019ED	A log client has not been registered on the stream.
0x000019EE	A request has already been made to handle the log full condition.
0x000019EF	Log service encountered an error when attempting to read from a log container.
0x000019F0	Log service encountered an error when attempting to write to a log container.
0x000019F1	Log service encountered an error when attempting open a log container.
0x000019F2	Log service encountered an invalid container state when attempting a requested action.
0x000019F3	Log service is not in the correct state to perform a requested action.
0x000019F4	Log space cannot be reclaimed because the log is pinned.
0x000019F5	Log metadata flush failed.
0x000019F6	Security on the log and its containers is inconsistent.
0x000019F7	Records were appended to the log or reservation changes were made, but the log could not be flushed.
0x000019F8	The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.
0x00001A2C	The transaction handle associated with this operation is not valid.
0x00001A2D	The requested operation was made in the context of a transaction that is no longer active.
0x00001A2E	The requested operation is not valid on the Transaction object in its current state.
0x00001A2F	The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller.
0x00001A30	It is too late to perform the requested operation, since the Transaction has already been aborted.
0x00001A31	It is too late to perform the requested operation, since the Transaction has already been committed.
0x00001A32	The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.
0x00001A33	The specified ResourceManager made no changes or updates to the resource under this transaction.
0x00001A34	The resource manager has attempted to prepare a transaction that it has not successfully joined.
0x00001A35	The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow.
0x00001A36	The RM tried to register a protocol that already exists.
0x00001A37	The attempt to propagate the Transaction failed.
0x00001A38	The requested propagation protocol was not registered as a CRM.
0x00001A39	The buffer passed in to PushTransaction or PullTransaction is not in a valid format.
0x00001A3A	The current transaction context associated with the thread is not a valid handle to a transaction object.
0x00001A3B	The specified Transaction object could not be opened, because it was not found.
0x00001A3C	The specified ResourceManager object could not be opened, because it was not found.
0x00001A3D	The specified Enlistment object could not be opened, because it was not found.
0x00001A3E	The specified TransactionManager object could not be opened, because it was not found.
0x00001A3F	The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline.
0x00001A40	The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.
0x00001A41	The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior.
0x00001A42	Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.
0x00001A43	The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.
0x00001A44	The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long.
0x00001A45	Implicit transaction are not supported.
0x00001A46	The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.
0x00001A47	The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.
0x00001A48	This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.
0x00001A49	The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed.
0x00001A4A	The transaction does not have a superior enlistment.
0x00001A4B	The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data.
0x00001A90	The function attempted to use a name that is reserved for use by another transaction.
0x00001A91	Transaction support within the specified resource manager is not started or was shut down due to an error.
0x00001A92	The metadata of the RM has been corrupted. The RM will not function.
0x00001A93	The specified directory does not contain a resource manager.
0x00001A95	The remote server or share does not support transacted file operations.
0x00001A96	The requested log size is invalid.
0x00001A97	The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.
0x00001A98	The specified file miniversion was not found for this transacted file open.
0x00001A99	The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.
0x00001A9A	A miniversion may only be opened in the context of the transaction that created it.
0x00001A9B	It is not possible to open a miniversion with modify access.
0x00001A9C	It is not possible to create any more miniversions for this stream.
0x00001A9E	The remote server sent mismatching version number or Fid for a file opened with transactions.
0x00001A9F	The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint.
0x00001AA0	There is no transaction metadata on the file.
0x00001AA1	The log data is corrupt.
0x00001AA2	The file can't be recovered because there is a handle still open on it.
0x00001AA3	The transaction outcome is unavailable because the resource manager responsible for it has disconnected.
0x00001AA4	The request was rejected because the enlistment in question is not a superior enlistment.
0x00001AA5	The transactional resource manager is already consistent. Recovery is not needed.
0x00001AA6	The transactional resource manager has already been started.
0x00001AA7	The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.
0x00001AA8	The operation cannot be performed because another transaction is depending on the fact that this property will not change.
0x00001AA9	The operation would involve a single file with two transactional resource managers and is therefore not allowed.
0x00001AAA	The $Txf directory must be empty for this operation to succeed.
0x00001AAB	The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.
0x00001AAC	The operation could not be completed because the transaction manager does not have a log.
0x00001AAD	A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.
0x00001AAE	The transactional metadata attribute on the file or directory is corrupt and unreadable.
0x00001AAF	The encryption operation could not be completed because a transaction is active.
0x00001AB0	This object is not allowed to be opened in a transaction.
0x00001AB1	An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
0x00001AB2	Memory mapping (creating a mapped section) a remote file under a transaction is not supported.
0x00001AB3	Transaction metadata is already present on this file and cannot be superseded.
0x00001AB4	A transaction scope could not be entered because the scope handler has not been initialized.
0x00001AB5	Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.
0x00001AB6	This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.
0x00001AB7	The request to thaw frozen transactions was ignored because transactions had not previously been frozen.
0x00001AB8	Transactions cannot be frozen because a freeze is already in progress.
0x00001AB9	The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.
0x00001ABA	The savepoint operation failed because files are open on the transaction. This is not permitted.
0x00001ABB	Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred.
0x00001ABC	The sparse operation could not be completed because a transaction is active on the file.
0x00001ABD	The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument.
0x00001ABE	I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.
0x00001ABF	The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.
0x00001AC0	The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manger has been shut down.
0x00001AC1	The operation could not be completed due to bad clusters on disk.
0x00001AC2	The compression operation could not be completed because a transaction is active on the file.
0x00001AC3	The operation could not be completed because the volume is dirty. Please run chkdsk and try again.
0x00001AC4	The link tracking operation could not be completed because a transaction is active.
0x00001AC5	This operation cannot be performed in a transaction.
0x00001AC6	The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one.
0x00001AC7	The specified operation could not be performed because the resource manager is not enlisted in the transaction.
0x00001B59	The specified session name is invalid.
0x00001B5A	The specified protocol driver is invalid.
0x00001B5B	The specified protocol driver was not found in the system path.
0x00001B5C	The specified terminal connection driver was not found in the system path.
0x00001B5D	A registry key for event logging could not be created for this session.
0x00001B5E	A service with the same name already exists on the system.
0x00001B5F	A close operation is pending on the session.
0x00001B60	There are no free output buffers available.
0x00001B61	The MODEM.INF file was not found.
0x00001B62	The modem name was not found in MODEM.INF.
0x00001B63	The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem.
0x00001B64	The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on.
0x00001B65	Carrier detect has failed or carrier has been dropped due to disconnect.
0x00001B66	Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional.
0x00001B67	Busy signal detected at remote site on callback.
0x00001B68	Voice detected at remote site on callback.
0x00001B69	Transport driver error
0x00001B6E	The specified session cannot be found.
0x00001B6F	The specified session name is already in use.
0x00001B70	The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on.
0x00001B71	An attempt has been made to connect to a session whose video mode is not supported by the current client.
0x00001B7B	The application attempted to enable DOS graphics mode. DOS graphics mode is not supported.
0x00001B7D	Your interactive logon privilege has been disabled. Please contact your administrator.
0x00001B7E	The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access.
0x00001B80	The client failed to respond to the server connect message.
0x00001B81	Disconnecting the console session is not supported.
0x00001B82	Reconnecting a disconnected session to the console is not supported.
0x00001B84	The request to control another session remotely was denied.
0x00001B85	The requested session access is denied.
0x00001B89	The specified terminal connection driver is invalid.
0x00001B8A	The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on.
0x00001B8B	The requested session is not configured to allow remote control.
0x00001B8C	Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number.
0x00001B8D	Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator.
0x00001B8E	The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.
0x00001B8F	The client you are using is not licensed to use this system. Your logon request is denied.
0x00001B90	The system license has expired. Your logon request is denied.
0x00001B91	Remote control could not be terminated because the specified session is not currently being remotely controlled.
0x00001B92	The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported.
0x00001B93	Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared.
0x00001B94	Remote logins are currently disabled.
0x00001B95	You do not have the proper encryption level to access this Session.
0x00001B96	The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer.
0x00001B97	The user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\%s and have them log off.
0x00001B98	Unable to log you on because of an account restriction.
0x00001B99	The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.
0x00001B9A	The Client Drive Mapping Service Has Connected on Terminal Connection.
0x00001B9B	The Client Drive Mapping Service Has Disconnected on Terminal Connection.
0x00001B9C	The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.
0x00001B9D	The target session is incompatible with the current session.
0x00001B9E	Windows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance.
0x00001F41	The file replication service API was called incorrectly.
0x00001F42	The file replication service cannot be started.
0x00001F43	The file replication service cannot be stopped.
0x00001F44	The file replication service API terminated the request. The event log may have more information.
0x00001F45	The file replication service terminated the request. The event log may have more information.
0x00001F46	The file replication service cannot be contacted. The event log may have more information.
0x00001F47	The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information.
0x00001F48	The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information.
0x00001F49	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.
0x00001F4A	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.
0x00001F4B	The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information.
0x00001F4C	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.
0x00001F4D	The file replication service cannot populate the system volume because of an internal error. The event log may have more information.
0x00001F4E	The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information.
0x00001F4F	The file replication service cannot process the request. The system volume is busy with a previous request.
0x00001F50	The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information.
0x00001F51	The file replication service detected an invalid parameter.
0x00002008	An error occurred while installing the directory service. For more information, see the event log.
0x00002009	The directory service evaluated group memberships locally.
0x0000200A	The specified directory service attribute or value does not exist.
0x0000200B	The attribute syntax specified to the directory service is invalid.
0x0000200C	The attribute type specified to the directory service is not defined.
0x0000200D	The specified directory service attribute or value already exists.
0x0000200E	The directory service is busy.
0x0000200F	The directory service is unavailable.
0x00002010	The directory service was unable to allocate a relative identifier.
0x00002011	The directory service has exhausted the pool of relative identifiers.
0x00002012	The requested operation could not be performed because the directory service is not the master for that type of operation.
0x00002013	The directory service was unable to initialize the subsystem that allocates relative identifiers.
0x00002014	The requested operation did not satisfy one or more constraints associated with the class of the object.
0x00002015	The directory service can perform the requested operation only on a leaf object.
0x00002016	The directory service cannot perform the requested operation on the RDN attribute of an object.
0x00002017	The directory service detected an attempt to modify the object class of an object.
0x00002018	The requested cross-domain move operation could not be performed.
0x00002019	Unable to contact the global catalog server.
0x0000201A	The policy object is shared and can only be modified at the root.
0x0000201B	The policy object does not exist.
0x0000201C	The requested policy information is only in the directory service.
0x0000201D	A domain controller promotion is currently active.
0x0000201E	A domain controller promotion is not currently active
0x00002020	An operations error occurred.
0x00002021	A protocol error occurred.
0x00002022	The time limit for this request was exceeded.
0x00002023	The size limit for this request was exceeded.
0x00002024	The administrative limit for this request was exceeded.
0x00002025	The compare response was false.
0x00002026	The compare response was true.
0x00002027	The requested authentication method is not supported by the server.
0x00002028	A more secure authentication method is required for this server.
0x00002029	Inappropriate authentication.
0x0000202A	The authentication mechanism is unknown.
0x0000202B	A referral was returned from the server.
0x0000202C	The server does not support the requested critical extension.
0x0000202D	This request requires a secure connection.
0x0000202E	Inappropriate matching.
0x0000202F	A constraint violation occurred.
0x00002030	There is no such object on the server.
0x00002031	There is an alias problem.
0x00002032	An invalid dn syntax has been specified.
0x00002033	The object is a leaf object.
0x00002034	There is an alias dereferencing problem.
0x00002035	The server is unwilling to process the request.
0x00002036	A loop has been detected.
0x00002037	There is a naming violation.
0x00002038	The result set is too large.
0x00002039	The operation affects multiple DSAs
0x0000203A	The server is not operational.
0x0000203B	A local error has occurred.
0x0000203C	An encoding error has occurred.
0x0000203D	A decoding error has occurred.
0x0000203E	The search filter cannot be recognized.
0x0000203F	One or more parameters are illegal.
0x00002040	The specified method is not supported.
0x00002041	No results were returned.
0x00002042	The specified control is not supported by the server.
0x00002043	A referral loop was detected by the client.
0x00002044	The preset referral limit was exceeded.
0x00002045	The search requires a SORT control.
0x00002046	The search results exceed the offset range specified.
0x00002047	The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation.
0x0000206D	The root object must be the head of a naming context. The root object cannot have an instantiated parent.
0x0000206E	The add replica operation cannot be performed. The naming context must be writeable in order to create the replica.
0x0000206F	A reference to an attribute that is not defined in the schema occurred.
0x00002070	The maximum size of an object has been exceeded.
0x00002071	An attempt was made to add an object to the directory with a name that is already in use.
0x00002072	An attempt was made to add an object of a class that does not have an RDN defined in the schema.
0x00002073	An attempt was made to add an object using an RDN that is not the RDN defined in the schema.
0x00002074	None of the requested attributes were found on the objects.
0x00002075	The user buffer is too small.
0x00002076	The attribute specified in the operation is not present on the object.
0x00002077	Illegal modify operation. Some aspect of the modification is not permitted.
0x00002078	The specified object is too large.
0x00002079	The specified instance type is not valid.
0x0000207A	The operation must be performed at a master DSA.
0x0000207B	The object class attribute must be specified.
0x0000207C	A required attribute is missing.
0x0000207D	An attempt was made to modify an object to include an attribute that is not legal for its class.
0x0000207E	The specified attribute is already present on the object.
0x00002080	The specified attribute is not present, or has no values.
0x00002081	Multiple values were specified for an attribute that can have only one value.
0x00002082	A value for the attribute was not in the acceptable range of values.
0x00002083	The specified value already exists.
0x00002084	The attribute cannot be removed because it is not present on the object.
0x00002085	The attribute value cannot be removed because it is not present on the object.
0x00002086	The specified root object cannot be a subref.
0x00002087	Chaining is not permitted.
0x00002088	Chained evaluation is not permitted.
0x00002089	The operation could not be performed because the object's parent is either uninstantiated or deleted.
0x0000208A	Having a parent that is an alias is not permitted. Aliases are leaf objects.
0x0000208B	The object and parent must be of the same type, either both masters or both replicas.
0x0000208C	The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object.
0x0000208D	Directory object not found.
0x0000208E	The aliased object is missing.
0x0000208F	The object name has bad syntax.
0x00002090	It is not permitted for an alias to refer to another alias.
0x00002091	The alias cannot be dereferenced.
0x00002092	The operation is out of scope.
0x00002093	The operation cannot continue because the object is in the process of being removed.
0x00002094	The DSA object cannot be deleted.
0x00002095	A directory service error has occurred.
0x00002096	The operation can only be performed on an internal master DSA object.
0x00002097	The object must be of class DSA.
0x00002098	Insufficient access rights to perform the operation.
0x00002099	The object cannot be added because the parent is not on the list of possible superiors.
0x0000209A	Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM).
0x0000209B	The name has too many parts.
0x0000209C	The name is too long.
0x0000209D	The name value is too long.
0x0000209E	The directory service encountered an error parsing a name.
0x0000209F	The directory service cannot get the attribute type for a name.
0x000020A0	The name does not identify an object; the name identifies a phantom.
0x000020A1	The security descriptor is too short.
0x000020A2	The security descriptor is invalid.
0x000020A3	Failed to create name for deleted object.
0x000020A4	The parent of a new subref must exist.
0x000020A5	The object must be a naming context.
0x000020A6	It is not permitted to add an attribute which is owned by the system.
0x000020A7	The class of the object must be structural; you cannot instantiate an abstract class.
0x000020A8	The schema object could not be found.
0x000020A9	A local object with this GUID (dead or alive) already exists.
0x000020AA	The operation cannot be performed on a back link.
0x000020AB	The cross reference for the specified naming context could not be found.
0x000020AC	The operation could not be performed because the directory service is shutting down.
0x000020AD	The directory service request is invalid.
0x000020AE	The role owner attribute could not be read.
0x000020AF	The requested FSMO operation failed. The current FSMO holder could not be contacted.
0x000020B0	Modification of a DN across a naming context is not permitted.
0x000020B1	The attribute cannot be modified because it is owned by the system.
0x000020B2	Only the replicator can perform this function.
0x000020B3	The specified class is not defined.
0x000020B4	The specified class is not a subclass.
0x000020B5	The name reference is invalid.
0x000020B6	A cross reference already exists.
0x000020B7	It is not permitted to delete a master cross reference.
0x000020B8	Subtree notifications are only supported on NC heads.
0x000020B9	Notification filter is too complex.
0x000020BA	Schema update failed: duplicate RDN.
0x000020BB	Schema update failed: duplicate OID.
0x000020BC	Schema update failed: duplicate MAPI identifier.
0x000020BD	Schema update failed: duplicate schema-id GUID.
0x000020BE	Schema update failed: duplicate LDAP display name.
0x000020BF	Schema update failed: range-lower less than range upper.
0x000020C0	Schema update failed: syntax mismatch.
0x000020C1	Schema deletion failed: attribute is used in must-contain.
0x000020C2	Schema deletion failed: attribute is used in may-contain.
0x000020C3	Schema update failed: attribute in may-contain does not exist.
0x000020C4	Schema update failed: attribute in must-contain does not exist.
0x000020C5	Schema update failed: class in aux-class list does not exist or is not an auxiliary class.
0x000020C6	Schema update failed: class in poss-superiors does not exist.
0x000020C7	Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules.
0x000020C8	Schema update failed: Rdn-Att-Id has wrong syntax.
0x000020C9	Schema deletion failed: class is used as auxiliary class.
0x000020CA	Schema deletion failed: class is used as sub class.
0x000020CB	Schema deletion failed: class is used as poss superior.
0x000020CC	Schema update failed in recalculating validation cache.
0x000020CD	The tree deletion is not finished. The request must be made again to continue deleting the tree.
0x000020CE	The requested delete operation could not be performed.
0x000020CF	Cannot read the governs class identifier for the schema record.
0x000020D0	The attribute schema has bad syntax.
0x000020D1	The attribute could not be cached.
0x000020D2	The class could not be cached.
0x000020D3	The attribute could not be removed from the cache.
0x000020D4	The class could not be removed from the cache.
0x000020D5	The distinguished name attribute could not be read.
0x000020D6	No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest.
0x000020D7	The instance type attribute could not be retrieved.
0x000020D8	An internal error has occurred.
0x000020D9	A database error has occurred.
0x000020DA	The attribute GOVERNSID is missing.
0x000020DB	An expected attribute is missing.
0x000020DC	The specified naming context is missing a cross reference.
0x000020DD	A security checking error has occurred.
0x000020DE	The schema is not loaded.
0x000020DF	Schema allocation failed. Please check if the machine is running low on memory.
0x000020E0	Failed to obtain the required syntax for the attribute schema.
0x000020E1	The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available.
0x000020E2	The replication operation failed because of a schema mismatch between the servers involved.
0x000020E3	The DSA object could not be found.
0x000020E4	The naming context could not be found.
0x000020E5	The naming context could not be found in the cache.
0x000020E6	The child object could not be retrieved.
0x000020E7	The modification was not permitted for security reasons.
0x000020E8	The operation cannot replace the hidden record.
0x000020E9	The hierarchy file is invalid.
0x000020EA	The attempt to build the hierarchy table failed.
0x000020EB	The directory configuration parameter is missing from the registry.
0x000020EC	The attempt to count the address book indices failed.
0x000020ED	The allocation of the hierarchy table failed.
0x000020EE	The directory service encountered an internal failure.
0x000020EF	The directory service encountered an unknown failure.
0x000020F0	A root object requires a class of 'top'.
0x000020F1	This directory server is shutting down, and cannot take ownership of new floating single-master operation roles.
0x000020F2	The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles.
0x000020F3	The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers.
0x000020F4	The replication operation failed.
0x000020F5	An invalid parameter was specified for this replication operation.
0x000020F6	The directory service is too busy to complete the replication operation at this time.
0x000020F7	The distinguished name specified for this replication operation is invalid.
0x000020F8	The naming context specified for this replication operation is invalid.
0x000020F9	The distinguished name specified for this replication operation already exists.
0x000020FA	The replication system encountered an internal error.
0x000020FB	The replication operation encountered a database inconsistency.
0x000020FC	The server specified for this replication operation could not be contacted.
0x000020FD	The replication operation encountered an object with an invalid instance type.
0x000020FE	The replication operation failed to allocate memory.
0x000020FF	The replication operation encountered an error with the mail system.
0x00002100	The replication reference information for the target server already exists.
0x00002101	The replication reference information for the target server does not exist.
0x00002102	The naming context cannot be removed because it is replicated to another server.
0x00002103	The replication operation encountered a database error.
0x00002104	The naming context is in the process of being removed or is not replicated from the specified server.
0x00002105	Replication access was denied.
0x00002106	The requested operation is not supported by this version of the directory service.
0x00002107	The replication remote procedure call was cancelled.
0x00002108	The source server is currently rejecting replication requests.
0x00002109	The destination server is currently rejecting replication requests.
0x0000210A	The replication operation failed due to a collision of object names.
0x0000210B	The replication source has been reinstalled.
0x0000210C	The replication operation failed because a required parent object is missing.
0x0000210D	The replication operation was preempted.
0x0000210E	The replication synchronization attempt was abandoned because of a lack of updates.
0x0000210F	The replication operation was terminated because the system is shutting down.
0x00002110	Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set.
0x00002111	The replication synchronization attempt failed because a master replica attempted to sync from a partial replica.
0x00002112	The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation.
0x00002113	The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer.
0x00002114	Schema update failed: An attribute with the same link identifier already exists.
0x00002115	Name translation: Generic processing error.
0x00002116	Name translation: Could not find the name or insufficient right to see name.
0x00002117	Name translation: Input name mapped to more than one output name.
0x00002118	Name translation: Input name found, but not the associated output format.
0x00002119	Name translation: Unable to resolve completely, only the domain was found.
0x0000211A	Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire.
0x0000211B	Modification of a constructed attribute is not allowed.
0x0000211C	The OM-Object-Class specified is incorrect for an attribute with the specified syntax.
0x0000211D	The replication request has been posted; waiting for reply.
0x0000211E	The requested operation requires a directory service, and none was available.
0x0000211F	The LDAP display name of the class or attribute contains non-ASCII characters.
0x00002120	The requested search operation is only supported for base searches.
0x00002121	The search failed to retrieve attributes from the database.
0x00002122	The schema update operation tried to add a backward link attribute that has no corresponding forward link.
0x00002123	Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object.
0x00002124	Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object.
0x00002125	Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation.
0x00002126	Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container.
0x00002127	Destination of a cross-domain move is not authoritative for the destination naming context.
0x00002128	Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object.
0x00002129	Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object.
0x0000212A	Another operation which requires exclusive access to the PDC FSMO is already in progress.
0x0000212B	A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state.
0x0000212C	This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move.
0x0000212D	Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry.
0x0000212E	A naming context head must be the immediate child of another naming context head, not of an interior node.
0x0000212F	The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)
0x00002130	Destination domain must be in native mode.
0x00002131	The operation cannot be performed because the server does not have an infrastructure container in the domain of interest.
0x00002132	Cross-domain move of non-empty account groups is not allowed.
0x00002133	Cross-domain move of non-empty resource groups is not allowed.
0x00002134	The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings.
0x00002135	Tree deletions starting at an object which has an NC head as a descendant are not allowed.
0x00002136	The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use.
0x00002137	The directory service failed to identify the list of objects to delete while attempting a tree deletion.
0x00002138	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.
0x00002139	Only an administrator can modify the membership list of an administrative group.
0x0000213A	Cannot change the primary group ID of a domain controller account.
0x0000213B	An attempt is made to modify the base schema.
0x0000213C	Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed.
0x0000213D	Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner.
0x0000213E	An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container.
0x0000213F	The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it.
0x00002140	The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory.
0x00002141	The specified group type is invalid.
0x00002142	You cannot nest global groups in a mixed domain if the group is security-enabled.
0x00002143	You cannot nest local groups in a mixed domain if the group is security-enabled.
0x00002144	A global group cannot have a local group as a member.
0x00002145	A global group cannot have a universal group as a member.
0x00002146	A universal group cannot have a local group as a member.
0x00002147	A global group cannot have a cross-domain member.
0x00002148	A local group cannot have another cross domain local group as a member.
0x00002149	A group with primary members cannot change to a security-disabled group.
0x0000214A	The schema cache load failed to convert the string default SD on a class-schema object.
0x0000214B	Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
0x0000214C	The DSA operation is unable to proceed because of a DNS lookup failure.
0x0000214D	While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync.
0x0000214E	The Security Descriptor attribute could not be read.
0x0000214F	The object requested was not found, but an object with that key was found.
0x00002150	The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1
0x00002151	Security Account Manager needs to get the boot password.
0x00002152	Security Account Manager needs to get the boot key from floppy disk.
0x00002153	Directory Service cannot start.
0x00002154	Directory Services could not start.
0x00002155	The connection between client and server requires packet privacy or better.
0x00002156	The source domain may not be in the same forest as destination.
0x00002157	The destination domain must be in the forest.
0x00002158	The operation requires that destination domain auditing be enabled.
0x00002159	The operation couldn't locate a DC for the source domain.
0x0000215A	The source object must be a group or user.
0x0000215B	The source object's SID already exists in destination forest.
0x0000215C	The source and destination object must be of the same type.
0x0000215D	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.
0x0000215E	Schema information could not be included in the replication request.
0x0000215F	The replication operation could not be completed due to a schema incompatibility.
0x00002160	The replication operation could not be completed due to a previous schema incompatibility.
0x00002161	The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation.
0x00002162	The requested domain could not be deleted because there exist domain controllers that still host this domain.
0x00002163	The requested operation can be performed only on a global catalog server.
0x00002164	A local group can only be a member of other local groups in the same domain.
0x00002165	Foreign security principals cannot be members of universal groups.
0x00002166	The attribute is not allowed to be replicated to the GC because of security reasons.
0x00002167	The checkpoint with the PDC could not be taken because there too many modifications being processed currently.
0x00002168	The operation requires that source domain auditing be enabled.
0x00002169	Security principal objects can only be created inside domain naming contexts.
0x0000216A	A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format.
0x0000216B	A Filter was passed that uses constructed attributes.
0x0000216C	The unicodePwd attribute value must be enclosed in double quotes.
0x0000216D	Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased.
0x0000216E	For security reasons, the operation must be run on the destination DC.
0x0000216F	For security reasons, the source DC must be NT4SP4 or greater.
0x00002170	Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed.
0x00002171	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.
0x00002172	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.
0x00002173	The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set.
0x00002174	The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain.
0x00002175	The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set.
0x00002176	The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain.
0x00002177	The version of the operating system installed on this server is incompatible with the functional level of the domain or forest.
0x00002178	The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level.
0x00002179	The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level.
0x0000217A	The sort order requested is not supported.
0x0000217B	The requested name already exists as a unique identifier.
0x0000217C	The machine account was created pre-NT4. The account needs to be recreated.
0x0000217D	The database is out of version store.
0x0000217E	Unable to continue operation because multiple conflicting controls were used.
0x0000217F	Unable to find a valid security descriptor reference domain for this partition.
0x00002180	Schema update failed: The link identifier is reserved.
0x00002181	Schema update failed: There are no link identifiers available.
0x00002182	An account group cannot have a universal group as a member.
0x00002183	Rename or move operations on naming context heads or read-only objects are not allowed.
0x00002184	Move operations on objects in the schema naming context are not allowed.
0x00002185	A system flag has been set on the object and does not allow the object to be moved or renamed.
0x00002186	This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers.
0x00002187	Unable to resolve completely, a referral to another forest is generated.
0x00002188	The requested action is not supported on standard server.
0x00002189	Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question.
0x0000218A	The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master.
0x0000218B	The thread limit for this request was exceeded.
0x0000218C	The Global catalog server is not in the closest site.
0x0000218D	The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute.
0x0000218E	The Directory Service failed to enter single user mode.
0x0000218F	The Directory Service cannot parse the script because of a syntax error.
0x00002190	The Directory Service cannot process the script because of an error.
0x00002191	The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress).
0x00002192	The directory service binding must be renegotiated due to a change in the server extensions information.
0x00002193	Operation not allowed on a disabled cross ref.
0x00002194	Schema update failed: No values for msDS-IntId are available.
0x00002195	Schema update failed: Duplicate msDS-INtId. Retry the operation.
0x00002196	Schema deletion failed: attribute is used in rDNAttID.
0x00002197	The directory service failed to authorize the request.
0x00002198	The Directory Service cannot process the script because it is invalid.
0x00002199	The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data.
0x0000219A	A cross reference is in use locally with the same name.
0x0000219B	The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest.
0x0000219C	Writeable NCs prevent this DC from demoting.
0x0000219D	The requested object has a non-unique identifier and cannot be retrieved.
0x0000219E	Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected.
0x0000219F	The group cannot be converted due to attribute restrictions on the requested group type.
0x000021A0	Cross-domain move of non-empty basic application groups is not allowed.
0x000021A1	Cross-domain move of non-empty query based application groups is not allowed.
0x000021A2	The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.
0x000021A3	The target container for a redirection of a well known object container cannot already be a special container.
0x000021A4	The Directory Service cannot perform the requested operation because a domain rename operation is in progress.
0x000021A5	The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method.
0x000021A6	The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
0x000021A7	The requested operation is not allowed on an object under the system container.
0x000021A8	The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected.
0x000021A9	The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency.
0x000021AA	At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies.
0x000021AB	The site settings object for the specified site does not exist.
0x000021AC	The local account store does not contain secret material for the specified account.
0x000021AD	Could not find a writable domain controller in the domain.
0x000021AE	The server object for the domain controller does not exist.
0x000021AF	The NTDS Settings object for the domain controller does not exist.
0x000021B0	The requested search operation is not supported for ASQ searches.
0x000021B1	A required audit event could not be generated for the operation.
0x000021B2	The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes.
0x000021B3	The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings.
0x000021B4	The address books are nested too deeply. Failed to build the hierarchy table.
0x000021B5	The specified up-to-date-ness vector is corrupt.
0x000021B6	The request to replicate secrets is denied.
0x000021B7	Schema update failed: The MAPI identifier is reserved.
0x000021B8	Schema update failed: There are no MAPI identifiers available.
0x000021B9	The replication operation failed because the required attributes of the local krbtgt object are missing.
0x000021BA	The domain name of the trusted domain already exists in the forest.
0x000021BB	The flat name of the trusted domain already exists in the forest.
0x000021BC	The User Principal Name (UPN) is invalid.
0x000021BD	OID mapped groups cannot have members.
0x000021BE	The specified OID cannot be found.
0x000021BF	The replication operation failed because the target object referred by a link value is recycled.
0x000021C0	The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller.
0x000021C1	The functional level of the AD LDS configuration set cannot be lowered to the requested value.
0x000021C2	The functional level of the domain (or forest) cannot be lowered to the requested value.
0x000021C3	The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level.
0x000021C4	The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information.
0x000021C5	The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object.
0x000021C6	The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site.
0x000021C7	The operation failed because SPN value provided for addition/modification is not unique forest-wide.
0x000021C8	The operation failed because UPN value provided for addition/modification is not unique forest-wide.
0x000021C9	The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present.
0x000021CA	The link value specified was not found, but a link value with that key was found.
0x000021CC	The add object operation failed because the caller was not authorized to add one or more attributes included in the request.
0x000021CD	The local account policy modification request was rejected because the policy is controlled by a regional authority.
0x00002329	DNS server unable to interpret format.
0x0000232A	DNS server failure.
0x0000232B	DNS name does not exist.
0x0000232C	DNS request not supported by name server.
0x0000232D	DNS operation refused.
0x0000232E	DNS name that ought not exist, does exist.
0x0000232F	DNS RR set that ought not exist, does exist.
0x00002330	DNS RR set that ought to exist, does not exist.
0x00002331	DNS server not authoritative for zone.
0x00002332	DNS name in update or prereq is not in zone.
0x00002338	DNS signature failed to verify.
0x00002339	DNS bad key.
0x0000233A	DNS signature validity expired.
0x0000238D	Only the DNS server acting as the key master for the zone may perform this operation.
0x0000238E	This operation is not allowed on a zone that is signed or has signing keys.
0x0000238F	NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC.
0x00002390	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).
0x00002391	The specified algorithm is not supported.
0x00002392	The specified key size is not supported.
0x00002393	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.
0x00002394	The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved.
0x00002395	An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved.
0x00002396	An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved.
0x00002397	The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved.
0x00002398	The specified key service provider cannot be opened by the DNS server.
0x00002399	The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone.
0x0000239A	The specified rollover period is invalid.
0x0000239B	The specified initial rollover offset is invalid.
0x0000239C	The specified signing key is already in process of rolling over keys.
0x0000239D	The specified signing key does not have a standby key to revoke.
0x0000239E	This operation is not allowed on a zone signing key (ZSK).
0x0000239F	This operation is not allowed on an active signing key.
0x000023A0	The specified signing key is already queued for rollover.
0x000023A1	This operation is not allowed on an unsigned zone.
0x000023A2	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.
0x000023A3	The specified signature validity period is invalid.
0x000023A4	The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone.
0x000023A5	This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server.
0x000023A6	This operation could not be completed because the XML stream received is empty or syntactically invalid.
0x000023A7	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.
0x000023A8	The specified signing key is not waiting for parental DS update.
0x000023A9	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.
0x000023AA	NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3.
0x0000251D	No records found for given DNS query.
0x0000251E	Bad DNS packet.
0x0000251F	No DNS packet.
0x00002520	DNS error, check rcode.
0x00002521	Unsecured DNS packet.
0x00002522	DNS query request is pending.
0x0000254F	Invalid DNS type.
0x00002550	Invalid IP address.
0x00002551	Invalid property.
0x00002552	Try DNS operation again later.
0x00002553	Record for given name and type is not unique.
0x00002554	DNS name does not comply with RFC specifications.
0x00002555	DNS name is a fully-qualified DNS name.
0x00002556	DNS name is dotted (multi-label).
0x00002557	DNS name is a single-part name.
0x00002558	DNS name contains an invalid character.
0x00002559	DNS name is entirely numeric.
0x0000255A	The operation requested is not permitted on a DNS root server.
0x0000255B	The record could not be created because this part of the DNS namespace has been delegated to another server.
0x0000255C	The DNS server could not find a set of root hints.
0x0000255D	The DNS server found root hints but they were not consistent across all adapters.
0x0000255E	The specified value is too small for this parameter.
0x0000255F	The specified value is too large for this parameter.
0x00002560	This operation is not allowed while the DNS server is loading zones in the background. Please try again later.
0x00002561	The operation requested is not permitted on against a DNS server running on a read-only DC.
0x00002562	No data is allowed to exist underneath a DNAME record.
0x00002563	This operation requires credentials delegation.
0x00002564	Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator.
0x00002565	Not allowed to remove all addresses.
0x00002581	DNS zone does not exist.
0x00002582	DNS zone information not available.
0x00002583	Invalid operation for DNS zone.
0x00002584	Invalid DNS zone configuration.
0x00002585	DNS zone has no start of authority (SOA) record.
0x00002586	DNS zone has no Name Server (NS) record.
0x00002587	DNS zone is locked.
0x00002588	DNS zone creation failed.
0x00002589	DNS zone already exists.
0x0000258A	DNS automatic zone already exists.
0x0000258B	Invalid DNS zone type.
0x0000258C	Secondary DNS zone requires master IP address.
0x0000258D	DNS zone not secondary.
0x0000258E	Need secondary IP address.
0x0000258F	WINS initialization failed.
0x00002590	Need WINS servers.
0x00002591	NBTSTAT initialization call failed.
0x00002592	Invalid delete of start of authority (SOA)
0x00002593	A conditional forwarding zone already exists for that name.
0x00002594	This zone must be configured with one or more master DNS server IP addresses.
0x00002595	The operation cannot be performed because this zone is shut down.
0x00002596	This operation cannot be performed because the zone is currently being signed. Please try again later.
0x000025B3	Primary DNS zone requires datafile.
0x000025B4	Invalid datafile name for DNS zone.
0x000025B5	Failed to open datafile for DNS zone.
0x000025B6	Failed to write datafile for DNS zone.
0x000025B7	Failure while reading datafile for DNS zone.
0x000025E5	DNS record does not exist.
0x000025E6	DNS record format error.
0x000025E7	Node creation failure in DNS.
0x000025E8	Unknown DNS record type.
0x000025E9	DNS record timed out.
0x000025EA	Name not in DNS zone.
0x000025EB	CNAME loop detected.
0x000025EC	Node is a CNAME DNS record.
0x000025ED	A CNAME record already exists for given name.
0x000025EE	Record only at DNS zone root.
0x000025EF	DNS record already exists.
0x000025F0	Secondary DNS zone data error.
0x000025F1	Could not create DNS cache data.
0x000025F2	DNS name does not exist.
0x000025F3	Could not create pointer (PTR) record.
0x000025F4	DNS domain was undeleted.
0x000025F5	The directory service is unavailable.
0x000025F6	DNS zone already exists in the directory service.
0x000025F7	DNS server not creating or reading the boot file for the directory service integrated DNS zone.
0x000025F8	Node is a DNAME DNS record.
0x000025F9	A DNAME record already exists for given name.
0x000025FA	An alias loop has been detected with either CNAME or DNAME records.
0x00002617	DNS AXFR (zone transfer) complete.
0x00002618	DNS zone transfer failed.
0x00002619	Added local WINS server.
0x00002649	Secure update call needs to continue update request.
0x0000267B	TCP/IP network protocol not installed.
0x0000267C	No DNS servers configured for local system.
0x000026AD	The specified directory partition does not exist.
0x000026AE	The specified directory partition already exists.
0x000026AF	This DNS server is not enlisted in the specified directory partition.
0x000026B0	This DNS server is already enlisted in the specified directory partition.
0x000026B1	The directory partition is not available at this time. Please wait a few minutes and try again.
0x000026B2	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.
0x000026B7	The RRL is not enabled.
0x000026B8	The window size parameter is invalid. It should be greater than or equal to 1.
0x000026B9	The IPv4 prefix length parameter is invalid. It should be less than or equal to 32.
0x000026BA	The IPv6 prefix length parameter is invalid. It should be less than or equal to 128.
0x000026BB	The TC Rate parameter is invalid. It should be less than 10.
0x000026BC	The Leak Rate parameter is invalid. It should be either 0, or between 2 and 10.
0x000026BD	The Leak Rate or TC Rate parameter is invalid. Leak Rate should be greater than TC Rate.
0x000026C1	The virtualization instance already exists.
0x000026C2	The virtualization instance does not exist.
0x000026C3	The virtualization tree is locked.
0x000026C4	Invalid virtualization instance name.
0x000026C5	The default virtualization instance cannot be added, removed or modified.
0x000026DF	The scope already exists for the zone.
0x000026E0	The scope does not exist for the zone.
0x000026E1	The scope is the same as the default zone scope.
0x000026E2	The scope name contains invalid characters.
0x000026E3	Operation not allowed when the zone has scopes.
0x000026E4	Failed to load zone scope.
0x000026E5	Failed to write data file for DNS zone scope. Please verify the file exists and is writable.
0x000026E6	The scope name contains invalid characters.
0x000026E7	The scope does not exist.
0x000026E8	The scope is the same as the default scope.
0x000026E9	The operation is invalid on the scope.
0x000026EA	The scope is locked.
0x000026EB	The scope already exists.
0x000026F3	A policy with the same name already exists on this level (server level or zone level) on the DNS server.
0x000026F4	No policy with this name exists on this level (server level or zone level) on the DNS server.
0x000026F5	The criteria provided in the policy are invalid.
0x000026F6	At least one of the settings of this policy is invalid.
0x000026F7	The client subnet cannot be deleted while it is being accessed by a policy.
0x000026F8	The client subnet does not exist on the DNS server.
0x000026F9	A client subnet with this name already exists on the DNS server.
0x000026FA	The IP subnet specified does not exist in the client subnet.
0x000026FB	The IP subnet that is being added, already exists in the client subnet.
0x000026FC	The policy is locked.
0x000026FD	The weight of the scope in the policy is invalid.
0x000026FE	The DNS policy name is invalid.
0x000026FF	The policy is missing criteria.
0x00002700	The name of the the client subnet record is invalid.
0x00002701	Invalid policy processing order.
0x00002702	The scope information has not been provided for a policy that requires it.
0x00002703	The scope information has been provided for a policy that does not require it.
0x00002704	The server scope cannot be deleted because it is referenced by a DNS Policy.
0x00002705	The zone scope cannot be deleted because it is referenced by a DNS Policy.
0x00002706	The criterion client subnet provided in the policy is invalid.
0x00002707	The criterion transport protocol provided in the policy is invalid.
0x00002708	The criterion network protocol provided in the policy is invalid.
0x00002709	The criterion interface provided in the policy is invalid.
0x0000270A	The criterion FQDN provided in the policy is invalid.
0x0000270B	The criterion query type provided in the policy is invalid.
0x0000270C	The criterion time of day provided in the policy is invalid.
0x00002714	A blocking operation was interrupted by a call to WSACancelBlockingCall.
0x00002719	The file handle supplied is not valid.
0x0000271D	An attempt was made to access a socket in a way forbidden by its access permissions.
0x0000271E	The system detected an invalid pointer address in attempting to use a pointer argument in a call.
0x00002726	An invalid argument was supplied.
0x00002728	Too many open sockets.
0x00002733	A non-blocking socket operation could not be completed immediately.
0x00002734	A blocking operation is currently executing.
0x00002735	An operation was attempted on a non-blocking socket that already had an operation in progress.
0x00002736	An operation was attempted on something that is not a socket.
0x00002737	A required address was omitted from an operation on a socket.
0x00002738	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.
0x00002739	A protocol was specified in the socket function call that does not support the semantics of the socket type requested.
0x0000273A	An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.
0x0000273B	The requested protocol has not been configured into the system, or no implementation for it exists.
0x0000273C	The support for the specified socket type does not exist in this address family.
0x0000273D	The attempted operation is not supported for the type of object referenced.
0x0000273E	The protocol family has not been configured into the system or no implementation for it exists.
0x0000273F	An address incompatible with the requested protocol was used.
0x00002740	Only one usage of each socket address (protocol/network address/port) is normally permitted.
0x00002741	The requested address is not valid in its context.
0x00002742	A socket operation encountered a dead network.
0x00002743	A socket operation was attempted to an unreachable network.
0x00002744	The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.
0x00002745	An established connection was aborted by the software in your host machine.
0x00002746	An existing connection was forcibly closed by the remote host.
0x00002747	An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
0x00002748	A connect request was made on an already connected socket.
0x00002749	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.
0x0000274A	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.
0x0000274B	Too many references to some kernel object.
0x0000274C	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.
0x0000274D	No connection could be made because the target machine actively refused it.
0x0000274E	Cannot translate name.
0x0000274F	Name component or name was too long.
0x00002750	A socket operation failed because the destination host was down.
0x00002751	A socket operation was attempted to an unreachable host.
0x00002752	Cannot remove a directory that is not empty.
0x00002753	A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.
0x00002754	Ran out of quota.
0x00002755	Ran out of disk quota.
0x00002756	File handle reference is no longer available.
0x00002757	Item is not available locally.
0x0000276B	WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.
0x0000276C	The Windows Sockets version requested is not supported.
0x0000276D	Either the application has not called WSAStartup, or WSAStartup failed.
0x00002775	Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.
0x00002776	No more results can be returned by WSALookupServiceNext.
0x00002777	A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
0x00002778	The procedure call table is invalid.
0x00002779	The requested service provider is invalid.
0x0000277A	The requested service provider could not be loaded or initialized.
0x0000277B	A system call has failed.
0x0000277C	No such service is known. The service cannot be found in the specified name space.
0x0000277D	The specified class was not found.
0x0000277E	No more results can be returned by WSALookupServiceNext.
0x0000277F	A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.
0x00002780	A database query failed because it was actively refused.
0x00002AF9	No such host is known.
0x00002AFA	This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.
0x00002AFB	A non-recoverable error occurred during a database lookup.
0x00002AFC	The requested name is valid, but no data of the requested type was found.
0x00002AFD	At least one reserve has arrived.
0x00002AFE	At least one path has arrived.
0x00002AFF	There are no senders.
0x00002B00	There are no receivers.
0x00002B01	Reserve has been confirmed.
0x00002B02	Error due to lack of resources.
0x00002B03	Rejected for administrative reasons - bad credentials.
0x00002B04	Unknown or conflicting style.
0x00002B05	Problem with some part of the filterspec or providerspecific buffer in general.
0x00002B06	Problem with some part of the flowspec.
0x00002B07	General QOS error.
0x00002B08	An invalid or unrecognized service type was found in the flowspec.
0x00002B09	An invalid or inconsistent flowspec was found in the QOS structure.
0x00002B0A	Invalid QOS provider-specific buffer.
0x00002B0B	An invalid QOS filter style was used.
0x00002B0C	An invalid QOS filter type was used.
0x00002B0D	An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR.
0x00002B0E	An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.
0x00002B0F	An incorrect number of flow descriptors was specified in the QOS structure.
0x00002B10	An unrecognized object was found in the QOS provider-specific buffer.
0x00002B11	An invalid policy object was found in the QOS provider-specific buffer.
0x00002B12	An invalid QOS flow descriptor was found in the flow descriptor list.
0x00002B13	An invalid or inconsistent flowspec was found in the QOS provider specific buffer.
0x00002B14	An invalid FILTERSPEC was found in the QOS provider-specific buffer.
0x00002B15	An invalid shape discard mode object was found in the QOS provider specific buffer.
0x00002B16	An invalid shaping rate object was found in the QOS provider-specific buffer.
0x00002B17	A reserved policy element was found in the QOS provider-specific buffer.
0x00002B18	No such host is known securely.
0x00002B19	Name based IPSEC policy could not be added.
0x000032C8	The specified quick mode policy already exists.
0x000032C9	The specified quick mode policy was not found.
0x000032CA	The specified quick mode policy is being used.
0x000032CB	The specified main mode policy already exists.
0x000032CC	The specified main mode policy was not found
0x000032CD	The specified main mode policy is being used.
0x000032CE	The specified main mode filter already exists.
0x000032CF	The specified main mode filter was not found.
0x000032D0	The specified transport mode filter already exists.
0x000032D1	The specified transport mode filter does not exist.
0x000032D2	The specified main mode authentication list exists.
0x000032D3	The specified main mode authentication list was not found.
0x000032D4	The specified main mode authentication list is being used.
0x000032D5	The specified default main mode policy was not found.
0x000032D6	The specified default main mode authentication list was not found.
0x000032D7	The specified default quick mode policy was not found.
0x000032D8	The specified tunnel mode filter exists.
0x000032D9	The specified tunnel mode filter was not found.
0x000032DA	The Main Mode filter is pending deletion.
0x000032DB	The transport filter is pending deletion.
0x000032DC	The tunnel filter is pending deletion.
0x000032DD	The Main Mode policy is pending deletion.
0x000032DE	The Main Mode authentication bundle is pending deletion.
0x000032DF	The Quick Mode policy is pending deletion.
0x000032E0	The Main Mode policy was successfully added, but some of the requested offers are not supported.
0x000032E1	The Quick Mode policy was successfully added, but some of the requested offers are not supported.
0x000035E8	ERROR_IPSEC_IKE_NEG_STATUS_BEGIN
0x000035E9	IKE authentication credentials are unacceptable
0x000035EA	IKE security attributes are unacceptable
0x000035EB	IKE Negotiation in progress
0x000035EC	General processing error
0x000035ED	Negotiation timed out
0x000035EE	IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store.
0x000035EF	IKE SA deleted by peer before establishment completed
0x000035F0	IKE SA deleted before establishment completed
0x000035F1	Negotiation request sat in Queue too long
0x000035F2	Negotiation request sat in Queue too long
0x000035F3	Negotiation request sat in Queue too long
0x000035F4	Negotiation request sat in Queue too long
0x000035F5	No response from peer
0x000035F6	Negotiation took too long
0x000035F7	Negotiation took too long
0x000035F8	Unknown error occurred
0x000035F9	Certificate Revocation Check failed
0x000035FA	Invalid certificate key usage
0x000035FB	Invalid certificate type
0x000035FC	IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key.
0x000035FD	Simultaneous rekeys were detected.
0x000035FE	Failure in Diffie-Hellman computation
0x000035FF	Don't know how to process critical payload
0x00003600	Invalid header
0x00003601	No policy configured
0x00003602	Failed to verify signature
0x00003603	Failed to authenticate using Kerberos
0x00003604	Peer's certificate did not have a public key
0x00003605	Error processing error payload
0x00003606	Error processing SA payload
0x00003607	Error processing Proposal payload
0x00003608	Error processing Transform payload
0x00003609	Error processing KE payload
0x0000360A	Error processing ID payload
0x0000360B	Error processing Cert payload
0x0000360C	Error processing Certificate Request payload
0x0000360D	Error processing Hash payload
0x0000360E	Error processing Signature payload
0x0000360F	Error processing Nonce payload
0x00003610	Error processing Notify payload
0x00003611	Error processing Delete Payload
0x00003612	Error processing VendorId payload
0x00003613	Invalid payload received
0x00003614	Soft SA loaded
0x00003615	Soft SA torn down
0x00003616	Invalid cookie received.
0x00003617	Peer failed to send valid machine certificate
0x00003618	Certification Revocation check of peer's certificate failed
0x00003619	New policy invalidated SAs formed with old policy
0x0000361A	There is no available Main Mode IKE policy.
0x0000361B	Failed to enabled TCB privilege.
0x0000361C	Failed to load SECURITY.DLL.
0x0000361D	Failed to obtain security function table dispatch address from SSPI.
0x0000361E	Failed to query Kerberos package to obtain max token size.
0x0000361F	Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup.
0x00003620	Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes).
0x00003621	Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters.
0x00003622	Given filter is invalid
0x00003623	Memory allocation failed.
0x00003624	Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine.
0x00003625	Invalid policy
0x00003626	Invalid DOI
0x00003627	Invalid situation
0x00003628	Diffie-Hellman failure
0x00003629	Invalid Diffie-Hellman group
0x0000362A	Error encrypting payload
0x0000362B	Error decrypting payload
0x0000362C	Policy match error
0x0000362D	Unsupported ID
0x0000362E	Hash verification failed
0x0000362F	Invalid hash algorithm
0x00003630	Invalid hash size
0x00003631	Invalid encryption algorithm
0x00003632	Invalid authentication algorithm
0x00003633	Invalid certificate signature
0x00003634	Load failed
0x00003635	Deleted via RPC call
0x00003636	Temporary state created to perform reinitialization. This is not a real failure.
0x00003637	The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine.
0x00003638	The recipient cannot handle version of IKE specified in the header.
0x00003639	Key length in certificate is too small for configured security requirements.
0x0000363A	Max number of established MM SAs to peer exceeded.
0x0000363B	IKE received a policy that disables negotiation.
0x0000363C	Reached maximum quick mode limit for the main mode. New main mode will be started.
0x0000363D	Main mode SA lifetime expired or peer sent a main mode delete.
0x0000363E	Main mode SA assumed to be invalid because peer stopped responding.
0x0000363F	Certificate doesn't chain to a trusted root in IPsec policy.
0x00003640	Received unexpected message ID.
0x00003641	Received invalid authentication offers.
0x00003642	Sent DoS cookie notify to initiator.
0x00003643	IKE service is shutting down.
0x00003644	Could not verify binding between CGA address and certificate.
0x00003645	Error processing NatOA payload.
0x00003646	Parameters of the main mode are invalid for this quick mode.
0x00003647	Quick mode SA was expired by IPsec driver.
0x00003648	Too many dynamically added IKEEXT filters were detected.
0x00003649	ERROR_IPSEC_IKE_NEG_STATUS_END
0x0000364A	NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel.
0x0000364B	Error in assigning inner IP address to initiator in tunnel mode.
0x0000364C	Require configuration payload missing.
0x0000364D	A negotiation running as the security principle who issued the connection is in progress
0x0000364E	SA was deleted due to IKEv1/AuthIP co-existence suppress check.
0x0000364F	Incoming SA request was dropped due to peer IP address rate limiting.
0x00003650	Peer does not support MOBIKE.
0x00003651	SA establishment is not authorized.
0x00003652	SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential.
0x00003653	SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard.
0x00003654	SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA.
0x00003655	ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END
0x00003656	The SPI in the packet does not match a valid IPsec SA.
0x00003657	Packet was received on an IPsec SA whose lifetime has expired.
0x00003658	Packet was received on an IPsec SA that does not match the packet characteristics.
0x00003659	Packet sequence number replay check failed.
0x0000365A	IPsec header and/or trailer in the packet is invalid.
0x0000365B	IPsec integrity check failed.
0x0000365C	IPsec dropped a clear text packet.
0x0000365D	IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.
0x0000365E	IPsec dropped a packet due to DoS throttling.
0x00003665	IPsec DoS Protection matched an explicit block rule.
0x00003666	IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.
0x00003667	IPsec DoS Protection received an incorrectly formatted packet.
0x00003668	IPsec DoS Protection failed to look up state.
0x00003669	IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.
0x0000366A	IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.
0x0000366B	IPsec DoS Protection has not been enabled.
0x0000366C	IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached.
0x000036B0	The requested section was not present in the activation context.
0x000036B1	The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.
0x000036B2	The application binding data format is invalid.
0x000036B3	The referenced assembly is not installed on your system.
0x000036B4	The manifest file does not begin with the required tag and format information.
0x000036B5	The manifest file contains one or more syntax errors.
0x000036B6	The application attempted to activate a disabled activation context.
0x000036B7	The requested lookup key was not found in any active activation context.
0x000036B8	A component version required by the application conflicts with another component version already active.
0x000036B9	The type requested activation context section does not match the query API used.
0x000036BA	Lack of system resources has required isolated activation to be disabled for the current thread of execution.
0x000036BB	An attempt to set the process default activation context failed because the process default activation context was already set.
0x000036BC	The encoding group identifier specified is not recognized.
0x000036BD	The encoding requested is not recognized.
0x000036BE	The manifest contains a reference to an invalid URI.
0x000036BF	The application manifest contains a reference to a dependent assembly which is not installed
0x000036C0	The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed
0x000036C1	The manifest contains an attribute for the assembly identity which is not valid.
0x000036C2	The manifest is missing the required default namespace specification on the assembly element.
0x000036C3	The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1".
0x000036C4	The private manifest probed has crossed a path with an unsupported reparse point.
0x000036C5	Two or more components referenced directly or indirectly by the application manifest have files by the same name.
0x000036C6	Two or more components referenced directly or indirectly by the application manifest have window classes with the same name.
0x000036C7	Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs.
0x000036C8	Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs.
0x000036C9	Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs.
0x000036CA	Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs.
0x000036CB	Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted.
0x000036CC	A component's file does not match the verification information present in the component manifest.
0x000036CD	The policy manifest contains one or more syntax errors.
0x000036CE	Manifest Parse Error : A string literal was expected, but no opening quote character was found.
0x000036CF	Manifest Parse Error : Incorrect syntax was used in a comment.
0x000036D0	Manifest Parse Error : A name was started with an invalid character.
0x000036D1	Manifest Parse Error : A name contained an invalid character.
0x000036D2	Manifest Parse Error : A string literal contained an invalid character.
0x000036D3	Manifest Parse Error : Invalid syntax for an xml declaration.
0x000036D4	Manifest Parse Error : An Invalid character was found in text content.
0x000036D5	Manifest Parse Error : Required white space was missing.
0x000036D6	Manifest Parse Error : The character '>' was expected.
0x000036D7	Manifest Parse Error : A semi colon character was expected.
0x000036D8	Manifest Parse Error : Unbalanced parentheses.
0x000036D9	Manifest Parse Error : Internal error.
0x000036DA	Manifest Parse Error : Whitespace is not allowed at this location.
0x000036DB	Manifest Parse Error : End of file reached in invalid state for current encoding.
0x000036DC	Manifest Parse Error : Missing parenthesis.
0x000036DD	Manifest Parse Error : A single or double closing quote character (\' or \") is missing.
0x000036DE	Manifest Parse Error : Multiple colons are not allowed in a name.
0x000036DF	Manifest Parse Error : Invalid character for decimal digit.
0x000036E0	Manifest Parse Error : Invalid character for hexadecimal digit.
0x000036E1	Manifest Parse Error : Invalid unicode character value for this platform.
0x000036E2	Manifest Parse Error : Expecting whitespace or '?'.
0x000036E3	Manifest Parse Error : End tag was not expected at this location.
0x000036E4	Manifest Parse Error : The following tags were not closed: %1.
0x000036E5	Manifest Parse Error : Duplicate attribute.
0x000036E6	Manifest Parse Error : Only one top level element is allowed in an XML document.
0x000036E7	Manifest Parse Error : Invalid at the top level of the document.
0x000036E8	Manifest Parse Error : Invalid xml declaration.
0x000036E9	Manifest Parse Error : XML document must have a top level element.
0x000036EA	Manifest Parse Error : Unexpected end of file.
0x000036EB	Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset.
0x000036EC	Manifest Parse Error : Element was not closed.
0x000036ED	Manifest Parse Error : End element was missing the character '>'.
0x000036EE	Manifest Parse Error : A string literal was not closed.
0x000036EF	Manifest Parse Error : A comment was not closed.
0x000036F0	Manifest Parse Error : A declaration was not closed.
0x000036F1	Manifest Parse Error : A CDATA section was not closed.
0x000036F2	Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml".
0x000036F3	Manifest Parse Error : System does not support the specified encoding.
0x000036F4	Manifest Parse Error : Switch from current encoding to specified encoding not supported.
0x000036F5	Manifest Parse Error : The name 'xml' is reserved and must be lower case.
0x000036F6	Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'.
0x000036F7	Manifest Parse Error : The standalone attribute cannot be used in external entities.
0x000036F8	Manifest Parse Error : Invalid version number.
0x000036F9	Manifest Parse Error : Missing equals sign between attribute and attribute value.
0x000036FA	Assembly Protection Error : Unable to recover the specified assembly.
0x000036FB	Assembly Protection Error : The public key for an assembly was too short to be allowed.
0x000036FC	Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest.
0x000036FD	An HRESULT could not be translated to a corresponding Win32 error code.
0x000036FE	Assembly Protection Error : The catalog for an assembly is missing.
0x000036FF	The supplied assembly identity is missing one or more attributes which must be present in this context.
0x00003700	The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names.
0x00003701	The referenced assembly could not be found.
0x00003702	The activation context activation stack for the running thread of execution is corrupt.
0x00003703	The application isolation metadata for this process or thread has become corrupt.
0x00003704	The activation context being deactivated is not the most recently activated one.
0x00003705	The activation context being deactivated is not active for the current thread of execution.
0x00003706	The activation context being deactivated has already been deactivated.
0x00003707	A component used by the isolation facility has requested to terminate the process.
0x00003708	A kernel mode component is releasing a reference on an activation context.
0x00003709	The activation context of system default assembly could not be generated.
0x0000370A	The value of an attribute in an identity is not within the legal range.
0x0000370B	The name of an attribute in an identity is not within the legal range.
0x0000370C	An identity contains two definitions for the same attribute.
0x0000370D	The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.
0x0000370E	A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found.
0x0000370F	The public key token does not correspond to the public key specified.
0x00003710	A substitution string had no mapping.
0x00003711	The component must be locked before making the request.
0x00003712	The component store has been corrupted.
0x00003713	An advanced installer failed during setup or servicing.
0x00003714	The character encoding in the XML declaration did not match the encoding used in the document.
0x00003715	The identities of the manifests are identical but their contents are different.
0x00003716	The component identities are different.
0x00003717	The assembly is not a deployment.
0x00003718	The file is not a part of the assembly.
0x00003719	The size of the manifest exceeds the maximum allowed.
0x0000371A	The setting is not registered.
0x0000371B	One or more required members of the transaction are not present.
0x0000371C	The SMI primitive installer failed during setup or servicing.
0x0000371D	A generic command executable returned a result that indicates failure.
0x0000371E	A component is missing file verification information in its manifest.
0x0000371F	Two or more components referenced directly or indirectly by the application manifest have the same WinRT ActivatableClass IDs.
0x00003A98	The specified channel path is invalid.
0x00003A99	The specified query is invalid.
0x00003A9A	The publisher metadata cannot be found in the resource.
0x00003A9B	The template for an event definition cannot be found in the resource (error = %1).
0x00003A9C	The specified publisher name is invalid.
0x00003A9D	The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest.
0x00003A9F	The specified channel could not be found.
0x00003AA0	The specified XML text was not well-formed. See Extended Error for more details.
0x00003AA1	The events for a direct channel go directly to a log file and cannot be subscribed to.
0x00003AA2	Configuration error.
0x00003AA3	The query result is stale or invalid and must be recreated. This may be due to the log being cleared or rolling over after the query result was created.
0x00003AA4	The query result is currently at an invalid position.
0x00003AA5	Registered MSXML doesn't support validation.
0x00003AA6	An expression can only be followed by a change-of-scope operation if the expression evaluates to a node set and is not already part of another change-of-scope operation.
0x00003AA7	Cannot perform a step operation from a term that does not represent an element set.
0x00003AA8	Left-hand side arguments to binary operators must be either attributes, nodes or variables. Right-hand side arguments must be constants.
0x00003AA9	A step operation must involve a node test or, in the case of a predicate, an algebraic expression against which to test each node in the preceeding node set.
0x00003AAA	This data type is currently unsupported.
0x00003AAB	A syntax error occurred at position %1!d!
0x00003AAC	This operator is unsupported by this implementation of the filter.
0x00003AAD	An unexpected token was encountered.
0x00003AAE	The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled.
0x00003AAF	Channel property %1!s! contains an invalid value. The value has an invalid type, is outside of its valid range, cannot be changed, or is not supported by this type of channel.
0x00003AB0	Publisher property %1!s! contains an invalid value. The value has an invalid type, is outside of its valid range, cannot be changed, or is not supported by this type of publisher.
0x00003AB1	The channel failed to activate.
0x00003AB2	The XPath expression exceeded the supported complexity. Simplify the expression or split it into multiple expressions.
0x00003AB3	The message resource is present but the message was not found in the message table.
0x00003AB4	The message ID for the desired message could not be found.
0x00003AB5	The substitution string for insert index (%1) could not be found.
0x00003AB6	The description string for parameter reference (%1) could not be found.
0x00003AB7	The maximum number of replacements has been reached.
0x00003AB8	The event definition could not be found for event ID (%1).
0x00003AB9	The locale specific resource for the desired message is not present.
0x00003ABA	The resource is too old and is not supported.
0x00003ABB	The resource is too new and is not supported.
0x00003ABC	The channel at index %1!d! of the query can't be opened.
0x00003ABD	The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded.
0x00003ABE	Attempted to create a numeric type that is outside of its valid range.
0x00003AE8	The subscription fails to activate.
0x00003AE9	The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated.
0x00003AEA	When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription.
0x00003AEB	The credential store that is used to save credentials is full.
0x00003AEC	The credential used by this subscription can't be found in credential store.
0x00003AED	No active channel is found for the query.
0x00003AFC	The resource loader failed to find MUI file.
0x00003AFD	The resource loader failed to load MUI file because the file fail to pass validation.
0x00003AFE	The RC Manifest is corrupted with garbage data or unsupported version or missing required item.
0x00003AFF	The RC Manifest has invalid culture name.
0x00003B00	The RC Manifest has invalid ultimatefallback name.
0x00003B01	The resource loader cache doesn't have loaded MUI entry.
0x00003B02	User stopped resource enumeration.
0x00003B03	UI language installation failed.
0x00003B04	Locale installation failed.
0x00003B06	A resource does not have default or neutral value.
0x00003B07	Invalid PRI config file.
0x00003B08	Invalid file type.
0x00003B09	Unknown qualifier.
0x00003B0A	Invalid qualifier value.
0x00003B0B	No Candidate found.
0x00003B0C	The ResourceMap or NamedResource has an item that does not have default or neutral resource..
0x00003B0D	Invalid ResourceCandidate type.
0x00003B0E	Duplicate Resource Map.
0x00003B0F	Duplicate Entry.
0x00003B10	Invalid Resource Identifier.
0x00003B11	Filepath too long.
0x00003B12	Unsupported directory type.
0x00003B16	Invalid PRI File.
0x00003B17	NamedResource Not Found.
0x00003B1F	ResourceMap Not Found.
0x00003B20	Unsupported MRT profile type.
0x00003B21	Invalid qualifier operator.
0x00003B22	Unable to determine qualifier value or qualifier value has not been set.
0x00003B23	Automerge is enabled in the PRI file.
0x00003B24	Too many resources defined for package.
0x00003B25	Resource File can not be used for merge operation.
0x00003B26	Load/UnloadPriFiles cannot be used with resource packages.
0x00003B27	Resource Contexts may not be created on threads that do not have a CoreWindow.
0x00003B28	The singleton Resource Manager with different profile is already created.
0x00003B29	The system component cannot operate given API operation
0x00003B2A	The resource is a direct reference to a non-default resource candidate.
0x00003B2B	Resource Map has been re-generated and the query string is not valid anymore.
0x00003B2C	The PRI files to be merged have incompatible versions.
0x00003B2D	The primary PRI files to be merged does not contain a schema.
0x00003B2E	Unable to load one of the PRI files to be merged.
0x00003B2F	Unable to add one of the PRI files to the merged file.
0x00003B30	Unable to create the merged PRI file.
0x00003B31	Packages for a PRI file merge must all be from the same package family.
0x00003B32	Packages for a PRI file merge must not include multiple main packages.
0x00003B33	Packages for a PRI file merge must not include bundle packages.
0x00003B34	Packages for a PRI file merge must include one main package.
0x00003B35	Packages for a PRI file merge must include at least one resource package.
0x00003B36	Invalid name supplied for a canonical merged PRI file.
0x00003B37	Unable to find the specified package.
0x00003B38	No default value for language was specified.
0x00003B60	The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification.
0x00003B61	The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
0x00003B62	The monitor does not comply with the MCCS specification it claims to support.
0x00003B63	The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
0x00003B64	The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
0x00003B65	An internal Monitor Configuration API error occurred.
0x00003B66	The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0x00003B67	The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0x00003B92	The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.
0x00003BC3	The requested system device cannot be found.
0x00003BC4	Hash generation for the specified hash version and hash type is not enabled on the server.
0x00003BC5	The hash requested from the server is not available or no longer valid.
0x00003BD9	The secondary interrupt controller instance that manages the specified interrupt is not registered.
0x00003BDA	The information supplied by the GPIO client driver is invalid.
0x00003BDB	The version specified by the GPIO client driver is not supported.
0x00003BDC	The registration packet supplied by the GPIO client driver is not valid.
0x00003BDD	The requested operation is not supported for the specified handle.
0x00003BDE	The requested connect mode conflicts with an existing mode on one or more of the specified pins.
0x00003BDF	The interrupt requested to be unmasked is not masked.
0x00003C28	The requested run level switch cannot be completed successfully.
0x00003C29	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.
0x00003C2A	The requested run level switch cannot be completed successfully since one or more services will not stop or restart within the specified timeout.
0x00003C2B	A run level switch agent did not respond within the specified timeout.
0x00003C2C	A run level switch is currently in progress.
0x00003C2D	One or more services failed to start during the service startup phase of a run level switch.
0x00003C8D	The task stop request cannot be completed immediately since task needs more time to shutdown.
0x00003CF0	Package could not be opened.
0x00003CF1	Package was not found.
0x00003CF2	Package data is invalid.
0x00003CF3	Package failed updates, dependency or conflict validation.
0x00003CF4	There is not enough disk space on your computer. Please free up some space and try again.
0x00003CF5	There was a problem downloading your product.
0x00003CF6	Package could not be registered.
0x00003CF7	Package could not be unregistered.
0x00003CF8	User cancelled the install request.
0x00003CF9	Install failed. Please contact your software vendor.
0x00003CFA	Removal failed. Please contact your software vendor.
0x00003CFB	The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details.
0x00003CFC	The application cannot be started. Try reinstalling the application to fix the problem.
0x00003CFD	A Prerequisite for an install could not be satisfied.
0x00003CFE	The package repository is corrupted.
0x00003CFF	To install this application you need either a Windows developer license or a sideloading-enabled system.
0x00003D00	The application cannot be started because it is currently updating.
0x00003D01	The package deployment operation is blocked by policy. Please contact your system administrator.
0x00003D02	The package could not be installed because resources it modifies are currently in use.
0x00003D03	The package could not be recovered because necessary data for recovery have been corrupted.
0x00003D04	The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present.
0x00003D05	An error occurred while deleting the package's previously existing application data.
0x00003D06	The package could not be installed because a higher version of this package is already installed.
0x00003D07	An error in a system binary was detected. Try refreshing the PC to fix the problem.
0x00003D08	A corrupted CLR NGEN binary was detected on the system.
0x00003D09	The operation could not be resumed because necessary data for recovery have been corrupted.
0x00003D0A	The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again.
0x00003D0B	Package move failed.
0x00003D0C	The deployment operation failed because the volume is not empty.
0x00003D0D	The deployment operation failed because the volume is offline. For a package update, the volume refers to the installed volume of all package versions.
0x00003D0E	The deployment operation failed because the specified volume is corrupt.
0x00003D0F	The deployment operation failed because the specified application needs to be registered first.
0x00003D10	The deployment operation failed because the package targets the wrong processor architecture.
0x00003D11	You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again.
0x00003D12	A main app package is required to install this optional package. Install the main package first and try again.
0x00003D13	This app package type is not supported on this filesystem
0x00003D14	Package move operation is blocked until the application has finished streaming
0x00003D15	A main or another optional app package has the same application ID as this optional package. Change the application ID for the optional package to avoid conflicts.
0x00003D16	This staging session has been held to allow another staging operation to be prioritized.
0x00003D17	A related set cannot be updated because the updated set is invalid. All packages in the related set must be updated at the same time.
0x00003D18	An optional package with a FullTrust entry point requires the main package to have the runFullTrust capability.
0x00003D19	An error occurred because a user was logged off.
0x00003D1A	An optional package provision requires the dependency main package to also be provisioned.
0x00003D1B	The packages failed the SmartScreen reputation check.
0x00003D1C	The SmartScreen reputation check operation timed out.
0x00003D1D	The current deployment option is not supported.
0x00003D1E	Activation is blocked due to the .appinstaller update settings for this app.
0x00003D1F	Remote drives are not supported; use \\server\share to register a remote package.
0x00003D20	Failed to process and write downloaded APPX package data to disk.
0x00003D21	The deployment operation was blocked due to a per-package-family policy restricting deployments on a non-system volume. Per policy, this app must be installed to the system drive, but that's not set as the default. In Storage Settings, make the system drive the default location to save new content, then retry the install.
0x00003D22	The deployment operation was blocked due to a machine-wide policy restricting deployments on a non-system volume. Per policy, this app must be installed to the system drive, but that's not set as the default. In Storage Settings, make the system drive the default location to save new content, then retry the install.
0x00003D23	The deployment operation was blocked because Special profile deployment is not allowed. Please try logging into an account that is not a Special profile. You can try logging out and logging back into the current account, or try logging into a different account.
0x00003D24	The deployment operation failed due to a conflicting package's mutable package directory. To install this package remove the existing package with the conflicting mutable package directory.
0x00003D25	The package installation failed because a singleton resource was specified and another user with that package installed is logged in. Please make sure that all active users with the package installed are logged out and retry installation.
0x00003D26	The package installation failed because a different version of the service is installed. Try installing a newer version of the package.
0x00003D27	The package installation failed because a version of the service exists outside of APPX packaging. Please contact your software vendor.
0x00003D28	The package installation failed because administrator privileges are required. Please contact an administrator to install this package.
0x00003D29	The package deployment failed because the operation would have redirected to default account, when the caller said not to do so.
0x00003D2A	The package deployment failed because the package requires a capability to natively target this host.
0x00003D2B	The package deployment failed because its content is not valid for an unsigned package.
0x00003D2C	The package deployment failed because its publisher is not in the unsigned namespace.
0x00003D2D	The package deployment failed because its publisher is not in the signed namespace.
0x00003D2E	The package deployment failed because its publisher is not in the signed namespace.
0x00003D2F	A host runtime dependency resolving to a package with full trust content requires the main package to have the runFullTrust capability.
0x00003D30	The application cannot be started for the target user. Please have the user explicitly install this package.
0x00003D54	The process has no package identity.
0x00003D55	The package runtime information is corrupted.
0x00003D56	The package identity is corrupted.
0x00003D57	The process has no application identity.
0x00003D58	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.
0x00003D59	One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log.
0x00003D5A	The package is currently not available.
0x00003D5B	The package does not have a mutable directory.
0x00003DB8	Loading the state store failed.
0x00003DB9	Retrieving the state version for the application failed.
0x00003DBA	Setting the state version for the application failed.
0x00003DBB	Resetting the structured state of the application failed.
0x00003DBC	State Manager failed to open the container.
0x00003DBD	State Manager failed to create the container.
0x00003DBE	State Manager failed to delete the container.
0x00003DBF	State Manager failed to read the setting.
0x00003DC0	State Manager failed to write the setting.
0x00003DC1	State Manager failed to delete the setting.
0x00003DC2	State Manager failed to query the setting.
0x00003DC3	State Manager failed to read the composite setting.
0x00003DC4	State Manager failed to write the composite setting.
0x00003DC5	State Manager failed to enumerate the containers.
0x00003DC6	State Manager failed to enumerate the settings.
0x00003DC7	The size of the state manager composite setting value has exceeded the limit.
0x00003DC8	The size of the state manager setting value has exceeded the limit.
0x00003DC9	The length of the state manager setting name has exceeded the limit.
0x00003DCA	The length of the state manager container name has exceeded the limit.
0x00003DE1	This API cannot be used in the context of the caller's application type.
0x00003DF5	This PC does not have a valid license for the application or product.
0x00003DF6	The authenticated user does not have a valid license for the application or product.
0x00003DF7	The commerce transaction associated with this license is still pending verification.
0x00003DF8	The license has been revoked for this user.
0x00007858	er-Mode) 0x00000000 The operation completed successfully.
0x00030200	The underlying file was converted to compound file format.
0x00030201	The storage operation should block until more data is available.
0x00030202	The storage operation should retry immediately.
0x00030203	The notified event sink will not influence the storage operation.
0x00030204	Multiple opens prevent consolidated. (commit succeeded).
0x00030205	Consolidation of the storage file failed. (commit succeeded).
0x00030206	Consolidation of the storage file is inappropriate. (commit succeeded).
0x00030207	The device needs to be power cycled. (commit succeeded).
0x00040000	Use the registry database to provide the requested information
0x00040001	Success, but static
0x00040002	Macintosh clipboard format
0x00040100	Successful drop took place
0x00040101	Drag-drop operation canceled
0x00040102	Use the default cursor
0x00040130	Data has same FORMATETC
0x00040140	View is already frozen
0x00040170	FORMATETC not supported
0x00040171	Same cache
0x00040172	Some cache(s) not updated
0x00040180	Invalid verb for OLE object
0x00040181	Verb number is valid but verb cannot be done now
0x00040182	Invalid window handle passed
0x000401A0	Message is too long; some of it had to be truncated before displaying
0x000401C0	Unable to convert OLESTREAM to IStorage
0x000401E2	Moniker reduced to itself
0x000401E4	Common prefix is this moniker
0x000401E5	Common prefix is input moniker
0x000401E6	Common prefix is both monikers
0x000401E7	Moniker is already registered in running object table
0x00040200	An event was able to invoke some but not all of the subscribers
0x00040202	An event was delivered but there were no subscribers
0x00040252	TabletPC inking error code. String was truncated
0x00040253	TabletPC inking error code. Recognition or training was interrupted
0x00040254	TabletPC inking error code. No personalization update to the recognizer because no training data found
0x00041300	The task is ready to run at its next scheduled time.
0x00041301	The task is currently running.
0x00041302	The task will not run at the scheduled times because it has been disabled.
0x00041303	The task has not yet run.
0x00041304	There are no more runs scheduled for this task.
0x00041305	One or more of the properties that are needed to run this task on a schedule have not been set.
0x00041306	The last run of the task was terminated by the user.
0x00041307	Either the task has no triggers or the existing triggers are disabled or not set.
0x00041308	Event triggers don't have set run times.
0x0004131B	The task is registered, but not all specified triggers will start the task, check task scheduler event log for detailed information.
0x0004131C	The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal.
0x00041325	The Task Scheduler service has asked the task to run.
0x0004D000	An asynchronous operation was specified. The operation has begun, but its outcome is not known yet.
0x0004D001	XACT_S_DEFECT
0x0004D002	The method call succeeded because the transaction was read-only.
0x0004D003	The transaction was successfully aborted. However, this is a coordinated transaction, and some number of enlisted resources were aborted outright because they could not support abort-retaining semantics
0x0004D004	No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes.
0x0004D005	The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call.
0x0004D006	The sink is for the moment and wishes the transaction to proceed, but if other changes are made following this return by other event sinks then this sink wants another chance to look
0x0004D007	The transaction was successfully aborted. However, the abort was non-retaining.
0x0004D008	An abort operation was already in progress.
0x0004D009	The resource manager has performed a single-phase commit of the transaction.
0x0004D00A	The local transaction has not aborted.
0x0004D010	The resource manager has requested to be the coordinator (last resource manager) for the transaction.
0x00080012	Not all the requested interfaces were available
0x00080013	The specified machine name was not found in the cache.
0x00090312	The function completed successfully, but must be called again to complete the context
0x00090313	The function completed successfully, but CompleteToken must be called
0x00090314	The function completed successfully, but both CompleteToken and this function must be called to complete the context
0x00090315	The logon was completed, but no network authority was available. The logon was made using locally known information
0x00090316	Schannel has received a TLS extension the SSPI caller subscribed to.
0x00090317	The context has expired and can no longer be used.
0x00090320	The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context.
0x00090321	The context data must be renegotiated with the peer.
0x00090323	There is no LSA mode context associated with this context.
0x0009035C	A signature operation must be performed before the user can authenticate.
0x00090360	The recipient rejected the renegotiation request.
0x00090364	The returned buffer is only a fragment of the message. More fragments need to be returned.
0x00090366	The function completed successfully, but must be called again to complete the context. Early start can be used.
0x00090368	An asynchronous SSPI routine has been called and the work is pending completion.
0x00091012	The protected data needs to be re-protected.
0x001B0000	Debugger was attached.
0x001B0001	Report was uploaded.
0x001B0002	Report was queued.
0x001B0003	Reporting was disabled.
0x001B0004	Reporting was temporarily suspended.
0x001B0005	Report was not queued to queuing being disabled.
0x001B0006	Report was uploaded, but not archived due to archiving being disabled.
0x001B0007	Reporting was successfully spun off as an asynchronous operation.
0x001B0008	The assertion was handled.
0x001B0009	The assertion was handled and added to a permanent ignore list.
0x001B000A	The assertion was resumed as unhandled.
0x001B000B	Report was throttled.
0x001B000C	Report was uploaded with cab.
0x001F0001	The IO was completed by a filter.
0x00261001	Monitor descriptor could not be obtained.
0x00261002	Format of the obtained monitor descriptor is not supported by this release.
0x00262307	No mode is pinned on the specified VidPN source/target.
0x0026231E	Specified mode set does not specify preference for one of its modes.
0x0026234B	Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty.
0x0026234C	Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements.
0x00262351	Specified content transformation is not pinned on the specified VidPN present path.
0x00263005	{GDI redirection surface was returned} GDI redirection surface of the top level window was returned.
0x00263008	{GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI} GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI.
0x0027000D	A certificate is already present in the cert store.
0x00270258	The Store was launched instead of the specified app because the app's package was in an invalid state.
0x00270259	This app failed to launch, but the error was handled with a dialog.
0x00300100	Property value will be ignored.
0x00340001	The request will be completed later by NDIS status indication.
0x00350059	The device had pending page requests which were discarded.
0x003C0105	The troubleshooting pack cannot be executed on this system.
0x003D0000	The function call is completing asynchronously.
0x003D0001	There are no more messages available on the channel.
0x00630001	The graph data was created.
0x00630002	There is not more event data.
0x00630005	No connectivity.
0x00630006	Already a member.
0x00632000	The graph is already connect.
0x00636000	The subscription already exists.
0x00670013	The transaction caller id has changed.
0x00670014	A transaction is in progress for the database connection.
0x00E70001	The storage pool was deleted by the driver. The object cache should be updated.
0x087A0001	The Present operation was invisible to the user.
0x087A0002	The Present operation was partially invisible to the user.
0x087A0004	The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager.
0x087A0005	The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del).
0x087A0006	The Present operation was not visible because the target monitor was being used for some other purpose.
0x087A0007	The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation.
0x087A0008	The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time.
0x087A0009	The swapchain has become unoccluded.
0x087A000A	The adapter did not have access to the required resources to complete the Desktop Duplication Present() call, the Present() call needs to be made again
0x087A002F	The present succeeded but the caller should present again on the next V-sync, even if there are no changes to the content.
0x4026200A	Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific).
0x40262201	Skip preparation of allocations referenced by the DMA buffer.
0x4026242F	Child device presence was not reliably detected.
0x40262437	Starting the leadlink adapter has been deferred temporarily.
0x40262439	The display adapter is being polled for children too frequently at the same polling level.
0x4026243A	Starting the adapter has been deferred temporarily.
0x4026243C	We can depend on the child device presence returned by the driver.
0x40290423	The requested salt size for signing with RSAPSS does not match what the TPM uses.
0x40290424	Validation of the platform claim failed.
0x40290425	The requested platform claim is for a previous boot.
0x40290426	The platform claim is for a previous boot, and cannot be created without reboot.
0x80000001	Not implemented
0x80000002	Ran out of memory
0x80000003	One or more arguments are invalid
0x80000004	No such interface supported
0x80000005	Invalid pointer
0x80000006	Invalid handle
0x80000007	Operation aborted
0x80000008	Unspecified error
0x80000009	General access denied error
0x8000000A	The data necessary to complete this operation is not yet available.
0x8000000B	The operation attempted to access data outside the valid range
0x8000000C	A concurrent or interleaved operation changed the state of the object, invalidating this operation.
0x8000000D	An illegal state change was requested.
0x8000000E	A method was called at an unexpected time.
0x8000000F	Typename or Namespace was not found in metadata file.
0x80000010	Name is an existing namespace rather than a typename.
0x80000011	Typename has an invalid format.
0x80000012	Metadata file is invalid or corrupted.
0x80000013	The object has been closed.
0x80000014	Only one thread may access the object during a write operation.
0x80000015	Operation is prohibited during change notification.
0x80000016	The text associated with this error code could not be found.
0x80000017	String not null terminated.
0x80000018	A delegate was assigned when not allowed.
0x80000019	An async operation was not properly started.
0x8000001A	The application is exiting and cannot service this request
0x8000001B	The application view is exiting and cannot service this request
0x8000001C	The object must support the IAgileObject interface
0x8000001D	Activating a single-threaded class from MTA is not supported
0x8000001E	The object has been committed.
0x8000001F	A COM call to an ASTA was blocked because the call chain originated in or passed through another ASTA. This call pattern is deadlock-prone and disallowed by apartment call control.
0x80000020	A universal application process cannot activate a packaged WinRT server that is declared to run full trust.
0x80000021	A full trust packaged application process cannot activate a packaged WinRT server unless it is also declared to run full trust.
0x80004001	Not implemented
0x80004002	No such interface supported
0x80004003	Invalid pointer
0x80004004	Operation aborted
0x80004005	Unspecified error
0x80004006	Thread local storage failure
0x80004007	Get shared memory allocator failure
0x80004008	Get memory allocator failure
0x80004009	Unable to initialize class cache
0x8000400A	Unable to initialize RPC services
0x8000400B	Cannot set thread local storage channel control
0x8000400C	Could not allocate thread local storage channel control
0x8000400D	The user supplied memory allocator is unacceptable
0x8000400E	The OLE service mutex already exists
0x8000400F	The OLE service file mapping already exists
0x80004010	Unable to map view of file for OLE service
0x80004011	Failure attempting to launch OLE service
0x80004012	There was an attempt to call CoInitialize a second time while single threaded
0x80004013	A Remote activation was necessary but was not allowed
0x80004014	A Remote activation was necessary but the server name provided was invalid
0x80004015	The class is configured to run as a security id different from the caller
0x80004016	Use of Ole1 services requiring DDE windows is disabled
0x80004017	A RunAs specification must be \ or simply
0x80004018	The server process could not be started. The pathname may be incorrect.
0x80004019	The server process could not be started as the configured identity. The pathname may be incorrect or unavailable.
0x8000401A	The server process could not be started because the configured identity is incorrect. Check the username and password.
0x8000401B	The client is not allowed to launch this server.
0x8000401C	The service providing this server could not be started.
0x8000401D	This computer was unable to communicate with the computer providing the server.
0x8000401E	The server did not respond after being launched.
0x8000401F	The registration information for this server is inconsistent or incomplete.
0x80004020	The registration information for this interface is inconsistent or incomplete.
0x80004021	The operation attempted is not supported.
0x80004022	A dll must be loaded.
0x80004023	A Microsoft Software Installer error was encountered.
0x80004024	The specified activation could not occur in the client context as specified.
0x80004025	Activations on the server are paused.
0x80004026	Activations on the server are not paused.
0x80004027	The component or application containing the component has been disabled.
0x80004028	The common language runtime is not available
0x80004029	The thread-pool rejected the submitted asynchronous work.
0x8000402A	The server started, but did not finish initializing in a timely fashion.
0x8000402B	Unable to complete the call since there is no COM+ security context inside IObjectControl.Activate.
0x80004030	The provided tracker configuration is invalid
0x80004031	The provided thread pool configuration is invalid
0x80004032	The provided side-by-side configuration is invalid
0x80004033	The server principal name (SPN) obtained during security negotiation is malformed.
0x80004034	The caller failed to revoke a per-apartment registration before apartment shutdown.
0x80004035	The object has been rundown by the stub manager while there are external clients.
0x8000FFFF	Catastrophic failure
0x80010001	Call was rejected by callee.
0x80010002	Call was canceled by the message filter.
0x80010003	The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage.
0x80010004	The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call.
0x80010005	It is illegal to call out while inside message filter.
0x80010006	The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid.
0x80010007	The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.
0x80010008	The caller (client) disappeared while the callee (server) was processing a call.
0x80010009	The data packet with the marshalled parameter data is incorrect.
0x8001000A	The call was not transmitted properly; the message queue was full and was not emptied after yielding.
0x8001000B	The client (caller) cannot marshall the parameter data - low memory, etc.
0x8001000C	The client (caller) cannot unmarshall the return data - low memory, etc.
0x8001000D	The server (callee) cannot marshall the return data - low memory, etc.
0x8001000E	The server (callee) cannot unmarshall the parameter data - low memory, etc.
0x8001000F	Received data is invalid; could be server or client data.
0x80010010	A particular parameter is invalid and cannot be (un)marshalled.
0x80010011	There is no second outgoing call on same channel in DDE conversation.
0x80010012	The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute.
0x80010100	System call failed.
0x80010101	Could not allocate some required resource (memory, events, ...)
0x80010102	Attempted to make calls on more than one thread in single threaded mode.
0x80010103	The requested interface is not registered on the server object.
0x80010104	RPC could not call the server or could not return the results of calling the server.
0x80010105	The server threw an exception.
0x80010106	Cannot change thread mode after it is set.
0x80010107	The method called does not exist on the server.
0x80010108	The object invoked has disconnected from its clients.
0x80010109	The object invoked chose not to process the call now. Try again later.
0x8001010A	The message filter indicated that the application is busy.
0x8001010B	The message filter rejected the call.
0x8001010C	A call control interfaces was called with invalid data.
0x8001010D	An outgoing call cannot be made since the application is dispatching an input-synchronous call.
0x8001010E	The application called an interface that was marshalled for a different thread.
0x8001010F	CoInitialize has not been called on the current thread.
0x80010110	The version of OLE on the client and server machines does not match.
0x80010111	OLE received a packet with an invalid header.
0x80010112	OLE received a packet with an invalid extension.
0x80010113	The requested object or interface does not exist.
0x80010114	The requested object does not exist.
0x80010115	OLE has sent a request and is waiting for a reply.
0x80010116	OLE is waiting before retrying a request.
0x80010117	Call context cannot be accessed after call completed.
0x80010118	Impersonate on unsecure calls is not supported.
0x80010119	Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized.
0x8001011A	No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server.
0x8001011B	Access is denied.
0x8001011C	Remote calls are not allowed for this process.
0x8001011D	The marshaled interface data packet (OBJREF) has an invalid or unknown format.
0x8001011E	No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call.
0x8001011F	This operation returned because the timeout period expired.
0x80010120	There are no synchronize objects to wait on.
0x80010121	Full subject issuer chain SSL principal name expected from the server.
0x80010122	Principal name is not a valid MSSTD name.
0x80010123	Unable to impersonate DCOM client
0x80010124	Unable to obtain server's security context
0x80010125	Unable to open the access token of the current thread
0x80010126	Unable to obtain user info from an access token
0x80010127	The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method
0x80010128	Unable to obtain the client's security blanket
0x80010129	Unable to set a discretionary ACL into a security descriptor
0x8001012A	The system function, AccessCheck, returned false
0x8001012B	Either NetAccessDel or NetAccessAdd returned an error code.
0x8001012C	One of the trustee strings provided by the user did not conform to the \ syntax and it was not the "*" string
0x8001012D	One of the security identifiers provided by the user was invalid
0x8001012E	Unable to convert a wide character trustee string to a multibyte trustee string
0x8001012F	Unable to find a security identifier that corresponds to a trustee string provided by the user
0x80010130	The system function, LookupAccountSID, failed
0x80010131	Unable to find a trustee name that corresponds to a security identifier provided by the user
0x80010132	The system function, LookupAccountName, failed
0x80010133	Unable to set or reset a serialization handle
0x80010134	Unable to obtain the Windows directory
0x80010135	Path too long
0x80010136	Unable to generate a uuid.
0x80010137	Unable to create file
0x80010138	Unable to close a serialization handle or a file handle.
0x80010139	The number of ACEs in an ACL exceeds the system limit.
0x8001013A	Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream.
0x8001013B	The version of ACL format in the stream is not supported by this implementation of IAccessControl
0x8001013C	Unable to open the access token of the server process
0x8001013D	Unable to decode the ACL in the stream provided by the user
0x8001013F	The COM IAccessControl object is not initialized
0x80010140	Call Cancellation is disabled
0x8001FFFF	An internal error occurred.
0x80020001	Unknown interface.
0x80020003	Member not found.
0x80020004	Parameter not found.
0x80020005	Type mismatch.
0x80020006	Unknown name.
0x80020007	No named arguments.
0x80020008	Bad variable type.
0x80020009	Exception occurred.
0x8002000A	Out of present range.
0x8002000B	Invalid index.
0x8002000C	Unknown language.
0x8002000D	Memory is locked.
0x8002000E	Invalid number of parameters.
0x8002000F	Parameter not optional.
0x80020010	Invalid callee.
0x80020011	Does not support a collection.
0x80020012	Division by zero.
0x80020013	Buffer too small
0x80028016	Buffer too small.
0x80028017	Field name not defined in the record.
0x80028018	Old format or invalid type library.
0x80028019	Old format or invalid type library.
0x8002801C	Error accessing the OLE registry.
0x8002801D	Library not registered.
0x80028027	Bound to unknown type.
0x80028028	Qualified name disallowed.
0x80028029	Invalid forward reference, or reference to uncompiled type.
0x8002802A	Type mismatch.
0x8002802B	Element not found.
0x8002802C	Ambiguous name.
0x8002802D	Name already exists in the library.
0x8002802E	Unknown LCID.
0x8002802F	Function not defined in specified DLL.
0x800288BD	Wrong module kind for the operation.
0x800288C5	Size may not exceed 64K.
0x800288C6	Duplicate ID in inheritance hierarchy.
0x800288CF	Incorrect inheritance depth in standard OLE hmember.
0x80028CA0	Type mismatch.
0x80028CA1	Invalid number of arguments.
0x80028CA2	I/O Error.
0x80028CA3	Error creating unique tmp file.
0x80029C4A	Error loading type library/DLL.
0x80029C83	Inconsistent property functions.
0x80029C84	Circular dependency between types/modules.
0x80030001	Unable to perform requested operation.
0x80030002	%1 could not be found.
0x80030003	The path %1 could not be found.
0x80030004	There are insufficient resources to open another file.
0x80030005	Access Denied.
0x80030006	Attempted an operation on an invalid object.
0x80030008	There is insufficient memory available to complete operation.
0x80030009	Invalid pointer error.
0x80030012	There are no more entries to return.
0x80030013	Disk is write-protected.
0x80030019	An error occurred during a seek operation.
0x8003001D	A disk error occurred during a write operation.
0x8003001E	A disk error occurred during a read operation.
0x80030020	A share violation has occurred.
0x80030021	A lock violation has occurred.
0x80030050	%1 already exists.
0x80030057	Invalid parameter error.
0x80030070	There is insufficient disk space to complete operation.
0x800300F0	Illegal write of non-simple property to simple property set.
0x800300FA	An API call exited abnormally.
0x800300FB	The file %1 is not a valid compound file.
0x800300FC	The name %1 is not valid.
0x800300FD	An unexpected error occurred.
0x800300FE	That function is not implemented.
0x800300FF	Invalid flag error.
0x80030100	Attempted to use an object that is busy.
0x80030101	The storage has been changed since the last commit.
0x80030102	Attempted to use an object that has ceased to exist.
0x80030103	Can't save.
0x80030104	The compound file %1 was produced with an incompatible version of storage.
0x80030105	The compound file %1 was produced with a newer version of storage.
0x80030106	Share.exe or equivalent is required for operation.
0x80030107	Illegal operation called on non-file based storage.
0x80030108	Illegal operation called on object with extant marshallings.
0x80030109	The docfile has been corrupted.
0x80030110	OLE32.DLL has been loaded at the wrong address.
0x80030111	The compound file is too large for the current implementation
0x80030112	The compound file was not created with the STGM_SIMPLE flag
0x80030201	The file download was aborted abnormally. The file is incomplete.
0x80030202	The file download has been terminated.
0x80030208	The specified firmware slot is invalid.
0x80030209	The specified firmware image is invalid.
0x8003020A	The storage device is unresponsive.
0x80030305	Generic Copy Protection Error.
0x80030306	Copy Protection Error - DVD CSS Authentication failed.
0x80030307	Copy Protection Error - The given sector does not have a valid CSS key.
0x80030308	Copy Protection Error - DVD session key not established.
0x80030309	Copy Protection Error - The read failed because the sector is encrypted.
0x8003030A	Copy Protection Error - The current DVD's region does not correspond to the region setting of the drive.
0x8003030B	Copy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted.
0x80040000	Invalid OLEVERB structure
0x80040001	Invalid advise flags
0x80040002	Can't enumerate any more, because the associated data is missing
0x80040003	This implementation doesn't take advises
0x80040004	There is no connection for this connection ID
0x80040005	Need to run the object to perform this operation
0x80040006	There is no cache to operate on
0x80040007	Uninitialized object
0x80040008	Linked object's source class has changed
0x80040009	Not able to get the moniker of the object
0x8004000A	Not able to bind to the source
0x8004000B	Object is static; operation not allowed
0x8004000C	User canceled out of save dialog
0x8004000D	Invalid rectangle
0x8004000E	compobj.dll is too old for the ole2.dll initialized
0x8004000F	Invalid window handle
0x80040010	Object is not in any of the inplace active states
0x80040011	Not able to convert object
0x80040012	Not able to perform the operation because object is not given storage yet
0x80040064	Invalid FORMATETC structure
0x80040065	Invalid DVTARGETDEVICE structure
0x80040066	Invalid STDGMEDIUM structure
0x80040067	Invalid STATDATA structure
0x80040068	Invalid lindex
0x80040069	Invalid tymed
0x8004006A	Invalid clipboard format
0x8004006B	Invalid aspect(s)
0x8004006C	tdSize parameter of the DVTARGETDEVICE structure is invalid
0x8004006D	Object doesn't support IViewObject interface
0x80040100	Trying to revoke a drop target that has not been registered
0x80040101	This window has already been registered as a drop target
0x80040102	Invalid window handle
0x80040103	A drag operation is already in progress
0x80040110	Class does not support aggregation (or class object is remote)
0x80040111	ClassFactory cannot supply requested class
0x80040112	Class is not licensed for use
0x80040140	Error drawing view
0x80040150	Could not read key from registry
0x80040151	Could not write key to registry
0x80040152	Could not find the key in the registry
0x80040153	Invalid value for registry
0x80040154	Class not registered
0x80040155	Interface not registered
0x80040156	Threading model entry is not valid
0x80040157	A registration in a package violates package-specific policies
0x80040160	CATID does not exist
0x80040161	Description not found
0x80040164	No package in the software installation data in the Active Directory meets this criteria.
0x80040165	Deleting this will break the referential integrity of the software installation data in the Active Directory.
0x80040166	The CLSID was not found in the software installation data in the Active Directory.
0x80040167	The software installation data in the Active Directory is corrupt.
0x80040168	There is no software installation data in the Active Directory.
0x80040169	There is no software installation data object in the Active Directory.
0x8004016A	The software installation data object in the Active Directory already exists.
0x8004016B	The path to the software installation data in the Active Directory is not correct.
0x8004016C	A network error interrupted the operation.
0x8004016D	The size of this object exceeds the maximum size set by the Administrator.
0x8004016E	The schema for the software installation data in the Active Directory does not match the required schema.
0x8004016F	An error occurred in the software installation data in the Active Directory.
0x80040170	Cache not updated
0x80040180	No verbs for OLE object
0x80040181	Invalid verb for OLE object
0x800401A0	Undo is not available
0x800401A1	Space for tools is not available
0x800401C0	OLESTREAM Get method failed
0x800401C1	OLESTREAM Put method failed
0x800401C2	Contents of the OLESTREAM not in correct format
0x800401C3	There was an error in a Windows GDI call while converting the bitmap to a DIB
0x800401C4	Contents of the IStorage not in correct format
0x800401C5	Contents of IStorage is missing one of the standard streams
0x800401C6	There was an error in a Windows GDI call while converting the DIB to a bitmap.
0x800401D0	OpenClipboard Failed
0x800401D1	EmptyClipboard Failed
0x800401D2	SetClipboard Failed
0x800401D3	Data on clipboard is invalid
0x800401D4	CloseClipboard Failed
0x800401E0	Moniker needs to be connected manually
0x800401E1	Operation exceeded deadline
0x800401E2	Moniker needs to be generic
0x800401E3	Operation unavailable
0x800401E4	Invalid syntax
0x800401E5	No object for moniker
0x800401E6	Bad extension for file
0x800401E7	Intermediate operation failed
0x800401E8	Moniker is not bindable
0x800401E9	Moniker is not bound
0x800401EA	Moniker cannot open file
0x800401EB	User input required for operation to succeed
0x800401EC	Moniker class has no inverse
0x800401ED	Moniker does not refer to storage
0x800401EE	No common prefix
0x800401EF	Moniker could not be enumerated
0x800401F0	CoInitialize has not been called.
0x800401F1	CoInitialize has already been called.
0x800401F2	Class of object cannot be determined
0x800401F3	Invalid class string
0x800401F4	Invalid interface string
0x800401F5	Application not found
0x800401F6	Application cannot be run more than once
0x800401F7	Some error in application program
0x800401F8	DLL for class not found
0x800401F9	Error in the DLL
0x800401FA	Wrong OS or OS version for application
0x800401FB	Object is not registered
0x800401FC	Object is already registered
0x800401FD	Object is not connected to server
0x800401FE	Application was launched but it didn't register a class factory
0x800401FF	Object has been released
0x80040201	An event was unable to invoke any of the subscribers
0x80040203	A syntax error occurred trying to evaluate a query string
0x80040204	An invalid field name was used in a query string
0x80040205	An unexpected exception was raised
0x80040206	An unexpected internal error was detected
0x80040207	The owner SID on a per-user subscription doesn't exist
0x80040208	A user-supplied component or subscriber raised an exception
0x80040209	An interface has too many methods to fire events from
0x8004020A	A subscription cannot be stored unless its event class already exists
0x8004020B	Not all the objects requested could be removed
0x8004020C	COM+ is required for this operation, but is not installed
0x8004020D	Cannot modify or delete an object that was not added using the COM+ Admin SDK
0x8004020E	Cannot modify or delete an object that was added using the COM+ Admin SDK
0x8004020F	The event class for this subscription is in an invalid partition
0x80040210	The owner of the PerUser subscription is not logged on to the system specified
0x80040212	TabletPC inking error code. No default tablet
0x80040219	TabletPC inking error code. An invalid input rectangle was specified
0x8004021B	TabletPC inking error code. Unknown property specified
0x80040222	TabletPC inking error code. The stroke object was deleted
0x80040223	TabletPC inking error code. Initialization failure
0x80040232	TabletPC inking error code. The data required for the operation was not supplied
0x80040233	TabletPC inking error code. Invalid packet description
0x80040235	TabletPC inking error code. There are no handwriting recognizers registered
0x80040236	TabletPC inking error code. User does not have the necessary rights to read recognizer information
0x80040237	TabletPC inking error code. API calls were made in an incorrect order
0x80040238	TabletPC inking error code. Queue is full
0x80040239	TabletPC inking error code. RtpEnabled called multiple times
0x8004023A	TabletPC inking error code. A recognizer returned invalid data
0x80040241	TabletPC inking error code. The property was not found, or supported by the recognizer
0x80041309	Trigger not found.
0x8004130A	One or more of the properties that are needed to run this task have not been set.
0x8004130B	There is no running instance of the task.
0x8004130C	The Task Scheduler Service is not installed on this computer.
0x8004130D	The task object could not be opened.
0x8004130E	The object is either an invalid task object or is not a task object.
0x8004130F	No account information could be found in the Task Scheduler security database for the task indicated.
0x80041310	Unable to establish existence of the account specified.
0x80041311	Corruption was detected in the Task Scheduler security database; the database has been reset.
0x80041312	Task Scheduler security services are available only on Windows NT.
0x80041313	The task object version is either unsupported or invalid.
0x80041314	The task has been configured with an unsupported combination of account settings and run time options.
0x80041315	The Task Scheduler Service is not running.
0x80041316	The task XML contains an unexpected node.
0x80041317	The task XML contains an element or attribute from an unexpected namespace.
0x80041318	The task XML contains a value which is incorrectly formatted or out of range.
0x80041319	The task XML is missing a required element or attribute.
0x8004131A	The task XML is malformed.
0x8004131D	The task XML contains too many nodes of the same type.
0x8004131E	The task cannot be started after the trigger's end boundary.
0x8004131F	An instance of this task is already running.
0x80041320	The task will not run because the user is not logged on.
0x80041321	The task image is corrupt or has been tampered with.
0x80041322	The Task Scheduler service is not available.
0x80041323	The Task Scheduler service is too busy to handle your request. Please try again later.
0x80041324	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	The task is disabled.
0x80041327	The task has properties that are not compatible with previous versions of Windows.
0x80041328	The task settings do not allow the task to start on demand.
0x80041329	The combination of properties that task is using is not compatible with the scheduling engine.
0x80041330	The task definition uses a deprecated feature.
0x8004D000	Another single phase resource manager has already been enlisted in this transaction.
0x8004D001	A retaining commit or abort is not supported
0x8004D002	The transaction failed to commit for an unknown reason. The transaction was aborted.
0x8004D003	Cannot call commit on this transaction object because the calling application did not initiate the transaction.
0x8004D004	Instead of committing, the resource heuristically aborted.
0x8004D005	Instead of aborting, the resource heuristically committed.
0x8004D006	Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions.
0x8004D007	Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions.
0x8004D008	The requested isolation level is not valid or supported.
0x8004D009	The transaction manager doesn't support an asynchronous operation for this method.
0x8004D00A	Unable to enlist in the transaction.
0x8004D00B	The requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero.
0x8004D00C	There is no resource presently associated with this enlistment
0x8004D00D	The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers.
0x8004D00E	The transaction has already been implicitly or explicitly committed or aborted
0x8004D00F	An invalid combination of flags was specified
0x8004D010	The resource manager id is not associated with this transaction or the transaction manager.
0x8004D011	This method was called in the wrong state
0x8004D012	The indicated unit of work does not match the unit of work expected by the resource manager.
0x8004D013	An enlistment in a transaction already exists.
0x8004D014	An import object for the transaction could not be found.
0x8004D015	The transaction cookie is invalid.
0x8004D016	The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed
0x8004D017	A time-out was specified, but time-outs are not supported.
0x8004D018	The requested operation is already in progress for the transaction.
0x8004D019	The transaction has already been aborted.
0x8004D01A	The Transaction Manager returned a log full error.
0x8004D01B	The Transaction Manager is not available.
0x8004D01C	A connection with the transaction manager was lost.
0x8004D01D	A request to establish a connection with the transaction manager was denied.
0x8004D01E	Resource manager reenlistment to determine transaction status timed out.
0x8004D01F	This transaction manager failed to establish a connection with another TIP transaction manager.
0x8004D020	This transaction manager encountered a protocol error with another TIP transaction manager.
0x8004D021	This transaction manager could not propagate a transaction from another TIP transaction manager.
0x8004D022	The Transaction Manager on the destination machine is not available.
0x8004D023	The Transaction Manager has disabled its support for TIP.
0x8004D024	The transaction manager has disabled its support for remote/network transactions.
0x8004D025	The partner transaction manager has disabled its support for remote/network transactions.
0x8004D026	The transaction manager has disabled its support for XA transactions.
0x8004D027	MSDTC was unable to read its configuration information.
0x8004D028	MSDTC was unable to load the dtc proxy dll.
0x8004D029	The local transaction has aborted.
0x8004D02A	The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.
0x8004D02B	The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.
0x8004D02C	The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions.
0x8004D080	XACT_E_CLERKNOTFOUND
0x8004D081	XACT_E_CLERKEXISTS
0x8004D082	XACT_E_RECOVERYINPROGRESS
0x8004D083	XACT_E_TRANSACTIONCLOSED
0x8004D084	XACT_E_INVALIDLSN
0x8004D085	XACT_E_REPLAYREQUEST
0x8004D100	The request to connect to the specified transaction coordinator was denied.
0x8004D101	The maximum number of enlistments for the specified transaction has been reached.
0x8004D102	A resource manager with the same identifier is already registered with the specified transaction coordinator.
0x8004D103	The prepare request given was not eligible for single phase optimizations.
0x8004D104	RecoveryComplete has already been called for the given resource manager.
0x8004D105	The interface call made was incorrect for the current state of the protocol.
0x8004D106	xa_open call failed for the XA resource.
0x8004D107	xa_recover call failed for the XA resource.
0x8004D108	The Logical Unit of Work specified cannot be found.
0x8004D109	The specified Logical Unit of Work already exists.
0x8004D10A	Subordinate creation failed. The specified Logical Unit of Work was not connected.
0x8004D10B	A transaction with the given identifier already exists.
0x8004D10C	The resource is in use.
0x8004D10D	The LU Recovery process is down.
0x8004D10E	The remote session was lost.
0x8004D10F	The resource is currently recovering.
0x8004D110	There was a mismatch in driving recovery.
0x8004D111	An error occurred with the XA resource.
0x8004E002	The root transaction wanted to commit, but transaction aborted
0x8004E003	You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting.
0x8004E004	There is no MTS object context
0x8004E005	The component is configured to use synchronization and this method call would cause a deadlock to occur.
0x8004E006	The component is configured to use synchronization and a thread has timed out waiting to enter the context.
0x8004E007	You made a method call on a COM+ component that has a transaction that has already committed or aborted.
0x8004E00C	The specified role was not configured for the application
0x8004E00F	COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator
0x8004E021	An unexpected error occurred during COM+ Activation.
0x8004E022	COM+ Activation failed. Check the event log for more information
0x8004E023	COM+ Activation failed due to a catalog or configuration error.
0x8004E024	COM+ activation failed because the activation could not be completed in the specified amount of time.
0x8004E025	COM+ Activation failed because an initialization function failed. Check the event log for more information.
0x8004E026	The requested operation requires that JIT be in the current context and it is not
0x8004E027	The requested operation requires that the current context have a Transaction, and it does not
0x8004E028	The components threading model has changed after install into a COM+ Application. Please re-install component.
0x8004E029	IIS intrinsics not available. Start your work with IIS.
0x8004E02A	An attempt to write a cookie failed.
0x8004E02B	An attempt to use a database generated a database specific error.
0x8004E02C	The COM+ component you created must use object pooling to work.
0x8004E02D	The COM+ component you created must use object construction to work correctly.
0x8004E02E	The COM+ component requires synchronization, and it is not configured for it.
0x8004E02F	The TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the "root" component for the transaction. The creation failed.
0x8004E030	The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope.
0x8004E031	The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning.
0x80070005	General access denied error
0x80070006	Invalid handle
0x8007000E	Ran out of memory
0x80070057	One or more arguments are invalid
0x80072EE1	No more Internet handles can be allocated
0x80072EE2	The operation timed out
0x80072EE3	The server returned extended information
0x80072EE4	An internal error occurred in the Microsoft Internet extensions
0x80072EE5	The URL is invalid
0x80072EE6	The URL does not use a recognized protocol
0x80072EE7	The server name or address could not be resolved
0x80072EE8	A protocol with the required capabilities was not found
0x80072EE9	The option is invalid
0x80072EEA	The length is incorrect for the option type
0x80072EEB	The option value cannot be set
0x80072EEC	Microsoft Internet Extension support has been shut down
0x80072EED	The user name was not allowed
0x80072EEE	The password was not allowed
0x80072EEF	The login request was denied
0x80072EF0	The requested operation is invalid
0x80072EF1	The operation has been canceled
0x80072EF2	The supplied handle is the wrong type for the requested operation
0x80072EF3	The handle is in the wrong state for the requested operation
0x80072EF4	The request cannot be made on a Proxy session
0x80072EF5	The registry value could not be found
0x80072EF6	The registry parameter is incorrect
0x80072EF7	Direct Internet access is not available
0x80072EF8	No context value was supplied
0x80072EF9	No status callback was supplied
0x80072EFA	There are outstanding requests
0x80072EFB	The information format is incorrect
0x80072EFC	The requested item could not be found
0x80072EFD	A connection with the server could not be established
0x80072EFE	The connection with the server was terminated abnormally
0x80072EFF	The connection with the server was reset
0x80072F00	The action must be retried
0x80072F01	The proxy request is invalid
0x80072F02	User interaction is required to complete the operation
0x80072F04	The handle already exists
0x80072F05	The date in the certificate is invalid or has expired
0x80072F06	The host name in the certificate is invalid or does not match
0x80072F07	A redirect request will change a non-secure to a secure connection
0x80072F08	A redirect request will change a secure to a non-secure connection
0x80072F09	Mixed secure and non-secure connections
0x80072F0A	Changing to non-secure post
0x80072F0B	Data is being posted on a non-secure connection
0x80072F0C	A certificate is required to complete client authentication
0x80072F0D	The certificate authority is invalid or incorrect
0x80072F0E	Client authentication has not been correctly installed
0x80072F0F	An error has occurred in a Wininet asynchronous thread. You may need to restart
0x80072F10	The protocol scheme has changed during a redirect operation
0x80072F11	There are operations awaiting retry
0x80072F12	The operation must be retried
0x80072F13	There are no new cache containers
0x80072F14	A security zone check indicates the operation must be retried
0x80072F17	The SSL certificate contains errors.
0x80072F19	It was not possible to connect to the revocation server or a definitive response could not be obtained.
0x80072F76	The requested header was not found
0x80072F77	The server does not support the requested protocol level
0x80072F78	The server returned an invalid or unrecognized response
0x80072F79	The supplied HTTP header is invalid
0x80072F7A	The request for a HTTP header is invalid
0x80072F7B	The HTTP header already exists
0x80072F7C	The HTTP redirect request failed
0x80072F7D	An error occurred in the secure channel support
0x80072F7E	The file could not be written to the cache
0x80072F7F	The TCP/IP protocol is not installed properly
0x80072F80	The HTTP request was not redirected
0x80072F81	A cookie from the server must be confirmed by the user
0x80072F82	A cookie from the server has been declined acceptance
0x80072F83	The computer is disconnected from the network
0x80072F84	The server is unreachable
0x80072F85	The proxy server is unreachable
0x80072F86	The proxy auto-configuration script is in error
0x80072F87	Could not download the proxy auto-configuration script file
0x80072F88	The HTTP redirect request must be confirmed by the user
0x80072F89	The supplied certificate is invalid
0x80072F8A	The supplied certificate has been revoked
0x80072F8B	The Dialup failed because file sharing was turned on and a failure was requested if security check was needed
0x80072F8C	Initialization of the WinINet API has not occurred
0x80072F8E	Login failed and the client should display the entity body to the user
0x80072F8F	Content decoding has failed
0x80080001	Attempt to create a class object failed
0x80080002	OLE service could not bind object
0x80080003	RPC communication failed with OLE service
0x80080004	Bad path to object
0x80080005	Server execution failed
0x80080006	OLE service could not communicate with the object server
0x80080007	Moniker path could not be normalized
0x80080008	Object server is stopping when OLE service contacts it
0x80080009	An invalid root block pointer was specified
0x80080010	An allocation chain contained an invalid link pointer
0x80080011	The requested allocation size was too large
0x80080015	The activation requires a display name to be present under the CLSID key.
0x80080016	The activation requires that the RunAs value for the application is Activate As Activator.
0x80080017	The class is not configured to support Elevated activation.
0x80080200	Appx packaging API has encountered an internal error.
0x80080201	The file is not a valid Appx package because its contents are interleaved.
0x80080202	The file is not a valid Appx package because it contains OPC relationships.
0x80080203	The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present.
0x80080204	The Appx package's manifest is invalid.
0x80080205	The Appx package's block map is invalid.
0x80080206	The Appx package's content cannot be read because it is corrupt.
0x80080207	The computed hash value of the block does not match the one stored in the block map.
0x80080208	The requested byte range is over 4GB when translated to byte range of blocks.
0x80080209	The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data.
0x8008020A	The APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data.
0x8008020B	The Appx package's content group map is invalid.
0x8008020C	The .appinstaller file is invalid.
0x8008020D	The baseline package version in delta package does not match the version in the baseline package to be updated.
0x8008020E	The delta package is missing a file from the updated package.
0x8008020F	The delta package is invalid.
0x80080210	The delta appended package is not allowed for the current operation.
0x80080211	The packaging layout file is invalid.
0x80080212	The packageSignConfig file is invalid.
0x80080213	The resources.pri file is not allowed when there are no resource elements in the package manifest.
0x80080214	The compression state of file in baseline and updated package does not match.
0x80080215	Non appx extensions are not allowed for payload packages targeting older platforms.
0x80080216	The encryptionExclusionFileList file is invalid.
0x80080300	The background task activation is spurious.
0x80090001	Bad UID.
0x80090002	Bad Hash.
0x80090003	Bad Key.
0x80090004	Bad Length.
0x80090005	Bad Data.
0x80090006	Invalid Signature.
0x80090007	Bad Version of provider.
0x80090008	Invalid algorithm specified.
0x80090009	Invalid flags specified.
0x8009000A	Invalid type specified.
0x8009000B	Key not valid for use in specified state.
0x8009000C	Hash not valid for use in specified state.
0x8009000D	Key does not exist.
0x8009000E	Insufficient memory available for the operation.
0x8009000F	Object already exists.
0x80090010	Access denied.
0x80090011	Object was not found.
0x80090012	Data already encrypted.
0x80090013	Invalid provider specified.
0x80090014	Invalid provider type specified.
0x80090015	Provider's public key is invalid.
0x80090016	Keyset does not exist
0x80090017	Provider type not defined.
0x80090018	Provider type as registered is invalid.
0x80090019	The keyset is not defined.
0x8009001A	Keyset as registered is invalid.
0x8009001B	Provider type does not match registered value.
0x8009001C	The digital signature file is corrupt.
0x8009001D	Provider DLL failed to initialize correctly.
0x8009001E	Provider DLL could not be found.
0x8009001F	The Keyset parameter is invalid.
0x80090020	An internal error occurred.
0x80090021	A base error occurred.
0x80090022	Provider could not perform the action since the context was acquired as silent.
0x80090023	The security token does not have storage space available for an additional container.
0x80090024	The profile for the user is a temporary profile.
0x80090025	The key parameters could not be set because the CSP uses fixed parameters.
0x80090026	The supplied handle is invalid.
0x80090027	The parameter is incorrect.
0x80090028	The buffer supplied to a function was too small.
0x80090029	The requested operation is not supported.
0x8009002A	No more data is available.
0x8009002B	The supplied buffers overlap incorrectly.
0x8009002C	The specified data could not be decrypted.
0x8009002D	An internal consistency check failed.
0x8009002E	This operation requires input from the user.
0x8009002F	The cryptographic provider does not support HMAC.
0x80090030	The device that is required by this cryptographic provider is not ready for use.
0x80090031	The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider.
0x80090032	The validation of the provided data failed the integrity or signature validation.
0x80090033	Incorrect password.
0x80090034	Encryption failed.
0x80090035	The device that is required by this cryptographic provider is not found on this platform.
0x80090036	The action was cancelled by the user.
0x80090037	The password is no longer valid and must be changed.
0x80090038	The operation cannot be completed from Terminal Server client sessions.
0x80090300	Not enough memory is available to complete this request
0x80090301	The handle specified is invalid
0x80090302	The function requested is not supported
0x80090303	The specified target is unknown or unreachable
0x80090304	The Local Security Authority cannot be contacted
0x80090305	The requested security package does not exist
0x80090306	The caller is not the owner of the desired credentials
0x80090307	The security package failed to initialize, and cannot be installed
0x80090308	The token supplied to the function is invalid
0x80090309	The security package is not able to marshall the logon buffer, so the logon attempt has failed
0x8009030A	The per-message Quality of Protection is not supported by the security package
0x8009030B	The security context does not allow impersonation of the client
0x8009030C	The logon attempt failed
0x8009030D	The credentials supplied to the package were not recognized
0x8009030E	No credentials are available in the security package
0x8009030F	The message or signature supplied for verification has been altered
0x80090310	The message supplied for verification is out of sequence
0x80090311	No authority could be contacted for authentication.
0x80090316	The requested security package does not exist
0x80090317	The context has expired and can no longer be used.
0x80090318	The supplied message is incomplete. The signature was not verified.
0x80090320	The credentials supplied were not complete, and could not be verified. The context could not be initialized.
0x80090321	The buffers supplied to a function was too small.
0x80090322	The target principal name is incorrect.
0x80090324	The clocks on the client and server machines are skewed.
0x80090325	The certificate chain was issued by an authority that is not trusted.
0x80090326	The message received was unexpected or badly formatted.
0x80090327	An unknown error occurred while processing the certificate.
0x80090328	The received certificate has expired.
0x80090329	The specified data could not be encrypted.
0x80090330	The specified data could not be decrypted.
0x80090331	The client and server cannot communicate, because they do not possess a common algorithm.
0x80090332	The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation).
0x80090333	A security context was deleted before the context was completed. This is considered a logon failure.
0x80090334	The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply.
0x80090335	Unable to accomplish the requested task because the local machine does not have any IP addresses.
0x80090336	The supplied credential handle does not match the credential associated with the security context.
0x80090337	The crypto system or checksum function is invalid because a required function is unavailable.
0x80090338	The number of maximum ticket referrals has been exceeded.
0x80090339	The local machine must be a Kerberos KDC (domain controller) and it is not.
0x8009033A	The other end of the security negotiation is requires strong crypto but it is not supported on the local machine.
0x8009033B	The KDC reply contained more than one principal name.
0x8009033C	Expected to find PA data for a hint of what etype to use, but it was not found.
0x8009033D	The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator.
0x8009033E	Smartcard logon is required and was not used.
0x8009033F	A system shutdown is in progress.
0x80090340	An invalid request was sent to the KDC.
0x80090341	The KDC was unable to generate a referral for the service requested.
0x80090342	The encryption type requested is not supported by the KDC.
0x80090343	An unsupported preauthentication mechanism was presented to the Kerberos package.
0x80090345	The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation.
0x80090346	Client's supplied SSPI channel bindings were incorrect.
0x80090347	The received certificate was mapped to multiple accounts.
0x80090348	SEC_E_NO_KERB_KEY
0x80090349	The certificate is not valid for the requested usage.
0x80090350	The system cannot contact a domain controller to service the authentication request. Please try again later.
0x80090351	The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log.
0x80090352	An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator.
0x80090353	The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator.
0x80090354	The smartcard certificate used for authentication was not trusted. Please contact your system administrator.
0x80090355	The smartcard certificate used for authentication has expired. Please contact your system administrator.
0x80090356	The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user.
0x80090357	An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator.
0x80090358	The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator.
0x80090359	An untrusted certificate authority was detected while processing the domain controller certificate used for authentication. There is additional information in the system event log. Please contact your system administrator.
0x8009035A	The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log.
0x8009035B	The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log.
0x8009035D	One or more of the parameters passed to the function was invalid.
0x8009035E	Client policy does not allow credential delegation to target server.
0x8009035F	Client policy does not allow credential delegation to target server with NLTM only authentication.
0x80090361	The required security context does not exist.
0x80090362	The PKU2U protocol encountered an error while attempting to utilize the associated certificates.
0x80090363	The identity of the server computer could not be verified.
0x80090365	Only https scheme is allowed.
0x80090367	No common application protocol exists between the client and the server. Application protocol negotiation failed.
0x80090369	You can't sign in with a user ID in this format. Try using your email address instead.
0x8009036A	The buffer supplied by the SSPI caller to receive generic extensions is too small.
0x8009036B	Not enough secbuffers were supplied to generate a token.
0x80091001	An error occurred while performing an operation on a cryptographic message.
0x80091002	Unknown cryptographic algorithm.
0x80091003	The object identifier is poorly formatted.
0x80091004	Invalid cryptographic message type.
0x80091005	Unexpected cryptographic message encoding.
0x80091006	The cryptographic message does not contain an expected authenticated attribute.
0x80091007	The hash value is not correct.
0x80091008	The index value is not valid.
0x80091009	The content of the cryptographic message has already been decrypted.
0x8009100A	The content of the cryptographic message has not been decrypted yet.
0x8009100B	The enveloped-data message does not contain the specified recipient.
0x8009100C	Invalid control type.
0x8009100D	Invalid issuer and/or serial number.
0x8009100E	Cannot find the original signer.
0x8009100F	The cryptographic message does not contain all of the requested attributes.
0x80091010	The streamed cryptographic message is not ready to return data.
0x80091011	The streamed cryptographic message requires more data to complete the decode operation.
0x80092001	The length specified for the output data was insufficient.
0x80092002	An error occurred during encode or decode operation.
0x80092003	An error occurred while reading or writing to a file.
0x80092004	Cannot find object or property.
0x80092005	The object or property already exists.
0x80092006	No provider was specified for the store or object.
0x80092007	The specified certificate is self signed.
0x80092008	The previous certificate or CRL context was deleted.
0x80092009	Cannot find the requested object.
0x8009200A	The certificate does not have a property that references a private key.
0x8009200B	Cannot find the certificate and private key for decryption.
0x8009200C	Cannot find the certificate and private key to use for decryption.
0x8009200D	Not a cryptographic message or the cryptographic message is not formatted correctly.
0x8009200E	The signed cryptographic message does not have a signer for the specified signer index.
0x8009200F	Final closure is pending until additional frees or closes.
0x80092010	The certificate is revoked.
0x80092011	No Dll or exported function was found to verify revocation.
0x80092012	The revocation function was unable to check revocation for the certificate.
0x80092013	The revocation function was unable to check revocation because the revocation server was offline.
0x80092014	The certificate is not in the revocation server's database.
0x80092020	The string contains a non-numeric character.
0x80092021	The string contains a non-printable character.
0x80092022	The string contains a character not in the 7 bit ASCII character set.
0x80092023	The string contains an invalid X500 name attribute key, oid, value or delimiter.
0x80092024	The dwValueType for the CERT_NAME_VALUE is not one of the character strings. Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_RDN_OCTET_STRING.
0x80092025	The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done.
0x80092026	The cryptographic operation failed due to a local security option setting.
0x80092027	No DLL or exported function was found to verify subject usage.
0x80092028	The called function was unable to do a usage check on the subject.
0x80092029	Since the server was offline, the called function was unable to complete the usage check.
0x8009202A	The subject was not found in a Certificate Trust List (CTL).
0x8009202B	None of the signers of the cryptographic message or certificate trust list is trusted.
0x8009202C	The public key's algorithm parameters are missing.
0x8009202D	An object could not be located using the object locator infrastructure with the given name.
0x80093000	OSS Certificate encode/decode error code base See asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR.
0x80093001	OSS ASN.1 Error: Output Buffer is too small.
0x80093002	OSS ASN.1 Error: Signed integer is encoded as a unsigned integer.
0x80093003	OSS ASN.1 Error: Unknown ASN.1 data type.
0x80093004	OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated.
0x80093005	OSS ASN.1 Error: Invalid data.
0x80093006	OSS ASN.1 Error: Invalid argument.
0x80093007	OSS ASN.1 Error: Encode/Decode version mismatch.
0x80093008	OSS ASN.1 Error: Out of memory.
0x80093009	OSS ASN.1 Error: Encode/Decode Error.
0x8009300A	OSS ASN.1 Error: Internal Error.
0x8009300B	OSS ASN.1 Error: Invalid data.
0x8009300C	OSS ASN.1 Error: Invalid data.
0x8009300D	OSS ASN.1 Error: Unsupported BER indefinite-length encoding.
0x8009300E	OSS ASN.1 Error: Access violation.
0x8009300F	OSS ASN.1 Error: Invalid data.
0x80093010	OSS ASN.1 Error: Invalid data.
0x80093011	OSS ASN.1 Error: Invalid data.
0x80093012	OSS ASN.1 Error: Internal Error.
0x80093013	OSS ASN.1 Error: Multi-threading conflict.
0x80093014	OSS ASN.1 Error: Invalid data.
0x80093015	OSS ASN.1 Error: Invalid data.
0x80093016	OSS ASN.1 Error: Invalid data.
0x80093017	OSS ASN.1 Error: Encode/Decode function not implemented.
0x80093018	OSS ASN.1 Error: Trace file error.
0x80093019	OSS ASN.1 Error: Function not implemented.
0x8009301A	OSS ASN.1 Error: Program link error.
0x8009301B	OSS ASN.1 Error: Trace file error.
0x8009301C	OSS ASN.1 Error: Trace file error.
0x8009301D	OSS ASN.1 Error: Invalid data.
0x8009301E	OSS ASN.1 Error: Invalid data.
0x8009301F	OSS ASN.1 Error: Program link error.
0x80093020	OSS ASN.1 Error: Program link error.
0x80093021	OSS ASN.1 Error: Program link error.
0x80093022	OSS ASN.1 Error: Program link error.
0x80093023	OSS ASN.1 Error: Program link error.
0x80093024	OSS ASN.1 Error: Program link error.
0x80093025	OSS ASN.1 Error: Program link error.
0x80093026	OSS ASN.1 Error: Program link error.
0x80093027	OSS ASN.1 Error: Program link error.
0x80093028	OSS ASN.1 Error: Program link error.
0x80093029	OSS ASN.1 Error: Program link error.
0x8009302A	OSS ASN.1 Error: Program link error.
0x8009302B	OSS ASN.1 Error: Program link error.
0x8009302C	OSS ASN.1 Error: Program link error.
0x8009302D	OSS ASN.1 Error: System resource error.
0x8009302E	OSS ASN.1 Error: Trace file error.
0x80093100	ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR.
0x80093101	ASN1 internal encode or decode error.
0x80093102	ASN1 unexpected end of data.
0x80093103	ASN1 corrupted data.
0x80093104	ASN1 value too large.
0x80093105	ASN1 constraint violated.
0x80093106	ASN1 out of memory.
0x80093107	ASN1 buffer overflow.
0x80093108	ASN1 function not supported for this PDU.
0x80093109	ASN1 bad arguments to function call.
0x8009310A	ASN1 bad real value.
0x8009310B	ASN1 bad tag value met.
0x8009310C	ASN1 bad choice value.
0x8009310D	ASN1 bad encoding rule.
0x8009310E	ASN1 bad unicode (UTF8).
0x80093133	ASN1 bad PDU type.
0x80093134	ASN1 not yet implemented.
0x80093201	ASN1 skipped unknown extension(s).
0x80093202	ASN1 end of data expected
0x80094001	The request subject name is invalid or too long.
0x80094002	The request does not exist.
0x80094003	The request's current status does not allow this operation.
0x80094004	The requested property value is empty.
0x80094005	The certification authority's certificate contains invalid data.
0x80094006	Certificate service has been suspended for a database restore operation.
0x80094007	The certificate contains an encoded length that is potentially incompatible with older enrollment software.
0x80094008	The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation.
0x80094009	The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester.
0x8009400A	Cannot archive private key. The certification authority is not configured for key archival.
0x8009400B	Cannot archive private key. The certification authority could not verify one or more key recovery certificates.
0x8009400C	The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature.
0x8009400D	At least one security principal must have the permission to manage this CA.
0x8009400E	The request contains an invalid renewal certificate attribute.
0x8009400F	An attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions.
0x80094010	A memory reference caused a data alignment fault.
0x80094011	The permissions on this certification authority do not allow the current user to enroll for certificates.
0x80094012	The permissions on the certificate template do not allow the current user to enroll for this type of certificate.
0x80094013	The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access.
0x80094014	The request was denied by a certificate manager or CA administrator.
0x80094015	An enrollment policy server cannot be located.
0x80094016	A signature algorithm or public key length does not meet the system's minimum required strength.
0x80094017	Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation.
0x80094018	No encryption certificate was specified.
0x80094800	The requested certificate template is not supported by this CA.
0x80094801	The request contains no certificate template information.
0x80094802	The request contains conflicting template information.
0x80094803	The request is missing a required Subject Alternate name extension.
0x80094804	The request is missing a required private key for archival by the server.
0x80094805	The request is missing a required SMIME capabilities extension.
0x80094806	The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request.
0x80094807	The request template version is newer than the supported template version.
0x80094808	The template is missing a required signature policy attribute.
0x80094809	The request is missing required signature policy information.
0x8009480A	The request is missing one or more required signatures.
0x8009480B	One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures.
0x8009480C	The request is missing one or more required signature issuance policies.
0x8009480D	The UPN is unavailable and cannot be added to the Subject Alternate name.
0x8009480E	The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name.
0x8009480F	The DNS name is unavailable and cannot be added to the Subject Alternate name.
0x80094810	The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template.
0x80094811	The public key does not meet the minimum size required by the specified certificate template.
0x80094812	The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name.
0x80094813	One or more certificate templates to be enabled on this certification authority could not be found.
0x80094814	The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed.
0x80094815	The certificate template requires too many RA signatures. Only one RA signature is allowed.
0x80094816	The certificate template requires renewal with the same public key, but the request uses a different public key.
0x80094817	The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent.
0x80094818	The certification authority cannot validate the Attestation Identity Key Id Binding.
0x80094819	The certification authority cannot validate the private key attestation data.
0x8009481A	The request does not support private key attestation as defined in the certificate template.
0x8009481B	The request public key is not consistent with the private key attestation data.
0x8009481C	The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable.
0x8009481D	The client's response could not be validated. It is either unexpected or incorrect.
0x8009481E	A valid Request ID was not detected in the request attributes, or an invalid one was submitted.
0x8009481F	The request is not consistent with the previously generated precertificate.
0x80094820	The request is locked against edits until a response is received from the client.
0x80094821	The Active Directory SID is unavailable and cannot be added to the custom security extension.
0x80095000	The key is not exportable.
0x80095001	You cannot add the root CA certificate into your local store.
0x80095002	The key archival hash attribute was not found in the response.
0x80095003	An unexpected key archival hash attribute was found in the response.
0x80095004	There is a key archival hash mismatch between the request and the response.
0x80095005	Signing certificate cannot include SMIME extension.
0x80096001	A system-level error occurred while verifying trust.
0x80096002	The certificate for the signer of the message is invalid or not found.
0x80096003	One of the counter signatures was invalid.
0x80096004	The signature of the certificate cannot be verified.
0x80096005	The timestamp signature and/or certificate could not be verified or is malformed.
0x80096010	The digital signature of the object did not verify.
0x80096011	The digital signature of the object is malformed. For technical detail, see security bulletin MS13-098.
0x80096019	A certificate's basic constraint extension has not been observed.
0x8009601E	The certificate does not meet or contain the Authenticode(tm) financial extensions.
0x80097001	Tried to reference a part of the file outside the proper range.
0x80097002	Could not retrieve an object from the file.
0x80097003	Could not find the head table in the file.
0x80097004	The magic number in the head table is incorrect.
0x80097005	The offset table has incorrect values.
0x80097006	Duplicate table tags or tags out of alphabetical order.
0x80097007	A table does not start on a long word boundary.
0x80097008	First table does not appear after header information.
0x80097009	Two or more tables overlap.
0x8009700A	Too many pad bytes between tables or pad bytes are not 0.
0x8009700B	File is too small to contain the last table.
0x8009700C	A table checksum is incorrect.
0x8009700D	The file checksum is incorrect.
0x80097010	The signature does not have the correct attributes for the policy.
0x80097011	The file did not pass the hints check.
0x80097012	The file is not an OpenType file.
0x80097013	Failed on a file operation (open, map, read, write).
0x80097014	A call to a CryptoAPI function failed.
0x80097015	There is a bad version number in the file.
0x80097016	The structure of the DSIG table is incorrect.
0x80097017	A check failed in a partially constant table.
0x80097018	Some kind of structural error.
0x80097019	The requested credential requires confirmation.
0x800B0001	Unknown trust provider.
0x800B0002	The trust verification action specified is not supported by the specified trust provider.
0x800B0003	The form specified for the subject is not one supported or known by the specified trust provider.
0x800B0004	The subject is not trusted for the specified action.
0x800B0005	Error due to problem in ASN.1 encoding process.
0x800B0006	Error due to problem in ASN.1 decoding process.
0x800B0007	Reading / writing Extensions where Attributes are appropriate, and vice versa.
0x800B0008	Unspecified cryptographic failure.
0x800B0009	The size of the data could not be determined.
0x800B000A	The size of the indefinite-sized data could not be determined.
0x800B000B	This object does not read and write self-sizing data.
0x800B0100	No signature was present in the subject.
0x800B0101	A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.
0x800B0102	The validity periods of the certification chain do not nest correctly.
0x800B0103	A certificate that can only be used as an end-entity is being used as a CA or vice versa.
0x800B0104	A path length constraint in the certification chain has been violated.
0x800B0105	A certificate contains an unknown extension that is marked 'critical'.
0x800B0106	A certificate being used for a purpose other than the ones specified by its CA.
0x800B0107	A parent of a given certificate in fact did not issue that child certificate.
0x800B0108	A certificate is missing or has an empty value for an important field, such as a subject or issuer name.
0x800B0109	A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
0x800B010A	A certificate chain could not be built to a trusted root authority.
0x800B010B	Generic trust failure.
0x800B010C	A certificate was explicitly revoked by its issuer.
0x800B010D	The certification path terminates with the test root which is not trusted with the current policy settings.
0x800B010E	The revocation process could not continue - the certificate(s) could not be checked.
0x800B010F	The certificate's CN name does not match the passed value.
0x800B0110	The certificate is not valid for the requested usage.
0x800B0111	The certificate was explicitly marked as untrusted by the user.
0x800B0112	A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.
0x800B0113	The certificate has invalid policy.
0x800B0114	The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded.
0x800C0002	The URL is invalid.
0x800C0003	No Internet session has been established.
0x800C0004	Unable to connect to the target server.
0x800C0005	The system cannot locate the resource specified.
0x800C0006	The system cannot locate the object specified.
0x800C0007	No data is available for the requested resource.
0x800C0008	The download of the specified resource has failed.
0x800C0009	Authentication is required to access this resource.
0x800C000A	The server could not recognize the provided mime type.
0x800C000B	The operation was timed out.
0x800C000C	The server did not understand the request, or the request was invalid.
0x800C000D	The specified protocol is unknown.
0x800C000E	A security problem occurred.
0x800C000F	The system could not load the persisted data.
0x800C0010	Unable to instantiate the object.
0x800C0014	A redirection problem occurred.
0x800C0015	The requested resource is a directory, not a file.
0x800C0019	Security certificate required to access this resource is invalid.
0x800F0000	A non-empty line was encountered in the INF before the start of a section.
0x800F0001	A section name marker in the INF is not complete, or does not exist on a line by itself.
0x800F0002	An INF section was encountered whose name exceeds the maximum section name length.
0x800F0003	The syntax of the INF is invalid.
0x800F0100	The style of the INF is different than what was requested.
0x800F0101	The required section was not found in the INF.
0x800F0102	The required line was not found in the INF.
0x800F0103	The files affected by the installation of this file queue have not been backed up for uninstall.
0x800F0200	The INF or the device information set or element does not have an associated install class.
0x800F0201	The INF or the device information set or element does not match the specified install class.
0x800F0202	An existing device was found that is a duplicate of the device being manually installed.
0x800F0203	There is no driver selected for the device information set or element.
0x800F0204	The requested device registry key does not exist.
0x800F0205	The device instance name is invalid.
0x800F0206	The install class is not present or is invalid.
0x800F0207	The device instance cannot be created because it already exists.
0x800F0208	The operation cannot be performed on a device information element that has not been registered.
0x800F0209	The device property code is invalid.
0x800F020A	The INF from which a driver list is to be built does not exist.
0x800F020B	The device instance does not exist in the hardware tree.
0x800F020C	The icon representing this install class cannot be loaded.
0x800F020D	The class installer registry entry is invalid.
0x800F020E	The class installer has indicated that the default action should be performed for this installation request.
0x800F020F	The operation does not require any files to be copied.
0x800F0210	The specified hardware profile does not exist.
0x800F0211	There is no device information element currently selected for this device information set.
0x800F0212	The operation cannot be performed because the device information set is locked.
0x800F0213	The operation cannot be performed because the device information element is locked.
0x800F0214	The specified path does not contain any applicable device INFs.
0x800F0215	No class installer parameters have been set for the device information set or element.
0x800F0216	The operation cannot be performed because the file queue is locked.
0x800F0217	A service installation section in this INF is invalid.
0x800F0218	There is no class driver list for the device information element.
0x800F0219	The installation failed because a function driver was not specified for this device instance.
0x800F021A	There is presently no default device interface designated for this interface class.
0x800F021B	The operation cannot be performed because the device interface is currently active.
0x800F021C	The operation cannot be performed because the device interface has been removed from the system.
0x800F021D	An interface installation section in this INF is invalid.
0x800F021E	This interface class does not exist in the system.
0x800F021F	The reference string supplied for this interface device is invalid.
0x800F0220	The specified machine name does not conform to UNC naming conventions.
0x800F0221	A general remote communication error occurred.
0x800F0222	The machine selected for remote communication is not available at this time.
0x800F0223	The Plug and Play service is not available on the remote machine.
0x800F0224	The property page provider registry entry is invalid.
0x800F0225	The requested device interface is not present in the system.
0x800F0226	The device's co-installer has additional work to perform after installation is complete.
0x800F0227	The device's co-installer is invalid.
0x800F0228	There are no compatible drivers for this device.
0x800F0229	There is no icon that represents this device or device type.
0x800F022A	A logical configuration specified in this INF is invalid.
0x800F022B	The class installer has denied the request to install or upgrade this device.
0x800F022C	One of the filter drivers installed for this device is invalid.
0x800F022D	The driver selected for this device does not support this version of Windows.
0x800F022E	The driver selected for this device does not support Windows.
0x800F022F	The third-party INF does not contain digital signature information.
0x800F0230	An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms.
0x800F0231	The device cannot be disabled.
0x800F0232	The device could not be dynamically removed.
0x800F0233	Cannot copy to specified target.
0x800F0234	Driver is not intended for this platform.
0x800F0235	Operation not allowed in WOW64.
0x800F0236	The operation involving unsigned file copying was rolled back, so that a system restore point could be set.
0x800F0237	An INF was copied into the Windows INF directory in an improper manner.
0x800F0238	The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product.
0x800F0239	An unknown exception was encountered.
0x800F023A	A problem was encountered when accessing the Plug and Play registry database.
0x800F023B	The requested operation is not supported for a remote machine.
0x800F023C	The specified file is not an installed OEM INF.
0x800F023D	One or more devices are presently installed using the specified INF.
0x800F023E	The requested device install operation is obsolete.
0x800F023F	A file could not be verified because it does not have an associated catalog signed via Authenticode(tm).
0x800F0240	Authenticode(tm) signature verification is not supported for the specified INF.
0x800F0241	The INF was signed with an Authenticode(tm) catalog from a trusted publisher.
0x800F0242	The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted.
0x800F0243	The publisher of an Authenticode(tm) signed catalog was not established as trusted.
0x800F0244	The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.
0x800F0245	The file may only be validated by a catalog signed via Authenticode(tm).
0x800F0246	One of the installers for this device cannot perform the installation at this time.
0x800F0247	A problem was encountered while attempting to add the driver to the store.
0x800F0248	The installation of this device is forbidden by system policy. Contact your system administrator.
0x800F0249	The installation of this driver is forbidden by system policy. Contact your system administrator.
0x800F024A	The specified INF is the wrong type for this operation.
0x800F024B	The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
0x800F024C	A problem was encountered while attempting to delete the driver from the store.
0x800F0300	An unrecoverable stack overflow was encountered.
0x800F1000	No installed components were detected.
0x80100001	An internal consistency check failed.
0x80100002	The action was cancelled by an SCardCancel request.
0x80100003	The supplied handle was invalid.
0x80100004	One or more of the supplied parameters could not be properly interpreted.
0x80100005	Registry startup information is missing or invalid.
0x80100006	Not enough memory available to complete this command.
0x80100007	An internal consistency timer has expired.
0x80100008	The data buffer to receive returned data is too small for the returned data.
0x80100009	The specified reader name is not recognized.
0x8010000A	The user-specified timeout value has expired.
0x8010000B	The smart card cannot be accessed because of other connections outstanding.
0x8010000C	The operation requires a smart card, but no smart card is currently in the device.
0x8010000D	The specified smart card name is not recognized.
0x8010000E	The system could not dispose of the media in the requested manner.
0x8010000F	The requested protocols are incompatible with the protocol currently in use with the smart card.
0x80100010	The reader or smart card is not ready to accept commands.
0x80100011	One or more of the supplied parameters values could not be properly interpreted.
0x80100012	The action was cancelled by the system, presumably to log off or shut down.
0x80100013	An internal communications error has been detected.
0x80100014	An internal error has been detected, but the source is unknown.
0x80100015	An ATR obtained from the registry is not a valid ATR string.
0x80100016	An attempt was made to end a non-existent transaction.
0x80100017	The specified reader is not currently available for use.
0x80100018	The operation has been aborted to allow the server application to exit.
0x80100019	The PCI Receive buffer was too small.
0x8010001A	The reader driver does not meet minimal requirements for support.
0x8010001B	The reader driver did not produce a unique reader name.
0x8010001C	The smart card does not meet minimal requirements for support.
0x8010001D	The Smart Card Resource Manager is not running.
0x8010001E	The Smart Card Resource Manager has shut down.
0x8010001F	An unexpected card error has occurred.
0x80100020	No Primary Provider can be found for the smart card.
0x80100021	The requested order of object creation is not supported.
0x80100022	This smart card does not support the requested feature.
0x80100023	The identified directory does not exist in the smart card.
0x80100024	The identified file does not exist in the smart card.
0x80100025	The supplied path does not represent a smart card directory.
0x80100026	The supplied path does not represent a smart card file.
0x80100027	Access is denied to this file.
0x80100028	The smart card does not have enough memory to store the information.
0x80100029	There was an error trying to set the smart card file object pointer.
0x8010002A	The supplied PIN is incorrect.
0x8010002B	An unrecognized error code was returned from a layered component.
0x8010002C	The requested certificate does not exist.
0x8010002D	The requested certificate could not be obtained.
0x8010002E	Cannot find a smart card reader.
0x8010002F	A communications error with the smart card has been detected. Retry the operation.
0x80100030	The requested key container does not exist on the smart card.
0x80100031	The Smart Card Resource Manager is too busy to complete this operation.
0x80100032	The smart card PIN cache has expired.
0x80100033	The smart card PIN cannot be cached.
0x80100034	The smart card is read only and cannot be written to.
0x80100065	The reader cannot communicate with the smart card, due to ATR configuration conflicts.
0x80100066	The smart card is not responding to a reset.
0x80100067	Power has been removed from the smart card, so that further communication is not possible.
0x80100068	The smart card has been reset, so any shared state information is invalid.
0x80100069	The smart card has been removed, so that further communication is not possible.
0x8010006A	Access was denied because of a security violation.
0x8010006B	The card cannot be accessed because the wrong PIN was presented.
0x8010006C	The card cannot be accessed because the maximum number of PIN entry attempts has been reached.
0x8010006D	The end of the smart card file has been reached.
0x8010006E	The action was cancelled by the user.
0x8010006F	No PIN was presented to the smart card.
0x80100070	The requested item could not be found in the cache.
0x80100071	The requested cache item is too old and was deleted from the cache.
0x80100072	The new cache item exceeds the maximum per-item size defined for the cache.
0x80110401	Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail
0x80110402	One or more of the object's properties are missing or invalid
0x80110403	The object was not found in the catalog
0x80110404	The object is already registered
0x80110407	Error occurred writing to the application file
0x80110408	Error occurred reading the application file
0x80110409	Invalid version number in application file
0x8011040A	The file path is invalid
0x8011040B	The application is already installed
0x8011040C	The role already exists
0x8011040D	An error occurred copying the file
0x8011040F	One or more users are not valid
0x80110410	One or more users in the application file are not valid
0x80110411	The component's CLSID is missing or corrupt
0x80110412	The component's progID is missing or corrupt
0x80110413	Unable to set required authentication level for update request
0x80110414	The identity or password set on the application is not valid
0x80110418	Application file CLSIDs or IIDs do not match corresponding DLLs
0x80110419	Interface information is either missing or changed
0x8011041A	DllRegisterServer failed on component install
0x8011041B	No server file share available
0x8011041D	DLL could not be loaded
0x8011041E	The registered TypeLib ID is not valid
0x8011041F	Application install directory not found
0x80110423	Errors occurred while in the component registrar
0x80110424	The file does not exist
0x80110425	The DLL could not be loaded
0x80110426	GetClassObject failed in the DLL
0x80110427	The DLL does not support the components listed in the TypeLib
0x80110428	The TypeLib could not be loaded
0x80110429	The file does not contain components or component information
0x8011042A	Changes to this object and its sub-objects have been disabled
0x8011042B	The delete function has been disabled for this object
0x8011042C	The server catalog version is not supported
0x8011042D	The component move was disallowed, because the source or destination application is either a system application or currently locked against changes
0x8011042E	The component move failed because the destination application no longer exists
0x80110430	The system was unable to register the TypeLib
0x80110433	This operation cannot be performed on the system application
0x80110434	The component registrar referenced in this file is not available
0x80110435	A component in the same DLL is already installed
0x80110436	The service is not installed
0x80110437	One or more property settings are either invalid or in conflict with each other
0x80110438	The object you are attempting to add or rename already exists
0x80110439	The component already exists
0x8011043B	The registration file is corrupt
0x8011043C	The property value is too large
0x8011043E	Object was not found in registry
0x8011043F	This object is not poolable
0x80110446	A CLSID with the same GUID as the new application ID is already installed on this machine
0x80110447	A role assigned to a component, interface, or method did not exist in the application
0x80110448	You must have components in an application in order to start the application
0x80110449	This operation is not enabled on this platform
0x8011044A	Application Proxy is not exportable
0x8011044B	Failed to start application because it is either a library application or an application proxy
0x8011044C	System application is not exportable
0x8011044D	Cannot subscribe to this component (the component may have been imported)
0x8011044E	An event class cannot also be a subscriber component
0x8011044F	Library applications and application proxies are incompatible
0x80110450	This function is valid for the base partition only
0x80110451	You cannot start an application that has been disabled
0x80110457	The specified partition name is already in use on this computer
0x80110458	The specified partition name is invalid. Check that the name contains at least one visible character
0x80110459	The partition cannot be deleted because it is the default partition for one or more users
0x8011045A	The partition cannot be exported, because one or more components in the partition have the same file name
0x8011045B	Applications that contain one or more imported components cannot be installed into a non-base partition
0x8011045C	The application name is not unique and cannot be resolved to an application id
0x8011045D	The partition name is not unique and cannot be resolved to a partition id
0x80110472	The COM+ registry database has not been initialized
0x80110473	The COM+ registry database is not open
0x80110474	The COM+ registry database detected a system error
0x80110475	The COM+ registry database is already running
0x80110480	This version of the COM+ registry database cannot be migrated
0x80110481	The schema version to be migrated could not be found in the COM+ registry database
0x80110482	There was a type mismatch between binaries
0x80110483	A binary of unknown or invalid type was provided
0x80110484	There was a type mismatch between a binary and an application
0x80110485	The application cannot be paused or resumed
0x80110486	The COM+ Catalog Server threw an exception during execution
0x80110600	Only COM+ Applications marked "queued" can be invoked using the "queue" moniker
0x80110601	At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker
0x80110602	MSMQ is required for the requested operation and is not installed
0x80110603	Unable to marshal an interface that does not support IPersistStream
0x80110604	The message is improperly formatted or was damaged in transit
0x80110605	An unauthenticated message was received by an application that accepts only authenticated messages
0x80110606	The message was requeued or moved by a user not in the "QC Trusted User" role
0x80110701	Cannot create a duplicate resource of type Distributed Transaction Coordinator
0x80110808	One of the objects being inserted or updated does not belong to a valid parent collection
0x80110809	One of the specified objects cannot be found
0x8011080A	The specified application is not currently running
0x8011080B	The partition(s) specified are not valid.
0x8011080D	COM+ applications that run as NT service may not be pooled or recycled
0x8011080E	One or more users are already assigned to a local partition set.
0x8011080F	Library applications may not be recycled.
0x80110811	Applications running as NT services may not be recycled.
0x80110812	The process has already been recycled.
0x80110813	A paused process may not be recycled.
0x80110814	Library applications may not be NT services.
0x80110815	The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID.
0x80110816	The partition specified as default is not a member of the partition set.
0x80110817	A recycled process may not be paused.
0x80110818	Access to the specified partition is denied.
0x80110819	Only Application Files (*.MSI files) can be installed into partitions.
0x8011081A	Applications containing one or more legacy components may not be exported to 1.0 format.
0x8011081B	Legacy components may not exist in non-base partitions.
0x8011081C	A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application
0x8011081D	A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application
0x8011081E	A private component cannot be moved (or copied) to a library application or to the base partition
0x8011081F	The Base Application Partition exists in all partition sets and cannot be removed.
0x80110820	Alas, Event Class components cannot be aliased.
0x80110821	Access is denied because the component is private.
0x80110822	The specified SAFER level is invalid.
0x80110823	The specified user cannot write to the system registry
0x80110824	COM+ partitions are currently disabled.
0x80190001	Unexpected HTTP status code.
0x80190003	Unexpected redirection status code (3xx).
0x80190004	Unexpected client error status code (4xx).
0x80190005	Unexpected server error status code (5xx).
0x8019012C	Multiple choices (300).
0x8019012D	Moved permanently (301).
0x8019012E	Found (302).
0x8019012F	See Other (303).
0x80190130	Not modified (304).
0x80190131	Use proxy (305).
0x80190133	Temporary redirect (307).
0x80190190	Bad request (400).
0x80190191	Unauthorized (401).
0x80190192	Payment required (402).
0x80190193	Forbidden (403).
0x80190194	Not found (404).
0x80190195	Method not allowed (405).
0x80190196	Not acceptable (406).
0x80190197	Proxy authentication required (407).
0x80190198	Request timeout (408).
0x80190199	Conflict (409).
0x8019019A	Gone (410).
0x8019019B	Length required (411).
0x8019019C	Precondition failed (412).
0x8019019D	Request entity too large (413).
0x8019019E	Request-URI too long (414).
0x8019019F	Unsupported media type (415).
0x801901A0	Requested range not satisfiable (416).
0x801901A1	Expectation failed (417).
0x801901F4	Internal server error (500).
0x801901F5	Not implemented (501).
0x801901F6	Bad gateway (502).
0x801901F7	Service unavailable (503).
0x801901F8	Gateway timeout (504).
0x801901F9	Version not supported (505).
0x801B8000	Crash reporting failed.
0x801B8001	Report aborted due to user cancellation.
0x801B8002	Report aborted due to network failure.
0x801B8003	Report not initialized.
0x801B8004	Reporting is already in progress for the specified process.
0x801B8005	Dump not generated due to a throttle.
0x801B8006	Operation failed due to insufficient user consent.
0x801B8007	Report aborted due to performance criteria.
0x801F0001	A handler was not defined by the filter for this operation.
0x801F0002	A context is already defined for this object.
0x801F0003	Asynchronous requests are not valid for this operation.
0x801F0004	Disallow the Fast IO path for this operation.
0x801F0005	An invalid name request was made. The name requested cannot be retrieved at this time.
0x801F0006	Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.
0x801F0007	The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver.
0x801F0008	The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).
0x801F0009	The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers.
0x801F000A	The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback.
0x801F000B	The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.
0x801F000C	Non-paged pool must be used for this type of context.
0x801F000D	A duplicate handler definition has been provided for an operation.
0x801F000E	The callback data queue has been disabled.
0x801F000F	Do not attach the filter to the volume at this time.
0x801F0010	Do not detach the filter from the volume at this time.
0x801F0011	An instance already exists at this altitude on the volume specified.
0x801F0012	An instance already exists with this name on the volume specified.
0x801F0013	The system could not find the filter specified.
0x801F0014	The system could not find the volume specified.
0x801F0015	The system could not find the instance specified.
0x801F0016	No registered context allocation definition was found for the given request.
0x801F0017	An invalid parameter was specified during context registration.
0x801F0018	The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.
0x801F0019	The requested device object does not exist for the given volume.
0x801F001A	The specified volume is already mounted.
0x801F001B	The specified Transaction Context is already enlisted in a transaction
0x801F001C	The specified context is already attached to another object
0x801F0020	No waiter is present for the filter's reply to this message.
0x801F0023	The filesystem database resource is in use. Registration cannot complete at this time.
0x80260001	{Display Driver Stopped Responding} The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft.
0x80263001	{Desktop composition is disabled} The operation could not be completed because desktop composition is disabled.
0x80263002	{Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session.
0x80263003	{No DWM redirection surface is available} The DWM was unable to provide a redirection surface to complete the DirectX present.
0x80263004	{DWM is not queuing presents for the specified window} The window specified is not currently using queued presents.
0x80263005	{The adapter specified by the LUID is not found} DWM can not find the adapter specified by the LUID.
0x80263007	{Redirection surface can not be created. The size of the surface is larger than what is supported on this machine} Redirection surface can not be created. The size of the surface is larger than what is supported on this machine.
0x80270001	The NAP SoH packet is invalid.
0x80270002	An SoH was missing from the NAP packet.
0x80270003	The entity ID conflicts with an already registered id.
0x80270004	No cached SoH is present.
0x80270005	The entity is still bound to the NAP system.
0x80270006	The entity is not registered with the NAP system.
0x80270007	The entity is not initialized with the NAP system.
0x80270008	The correlation id in the SoH-Request and SoH-Response do not match up.
0x80270009	Completion was indicated on a request that is not currently pending.
0x8027000A	The NAP component's id was not found.
0x8027000B	The maximum size of the connection is too small for an SoH packet.
0x8027000C	The NapAgent service is not running.
0x8027000E	The entity is disabled with the NapAgent service.
0x8027000F	Group Policy is not configured.
0x80270010	Too many simultaneous calls.
0x80270011	SHV configuration already existed.
0x80270012	SHV configuration is not found.
0x80270013	SHV timed out on the request.
0x80270220	The maximum number of items for the access list has been reached. An item must be removed before another item is added.
0x80270222	Cannot access Homegroup. Homegroup may not be set up or may have encountered an error.
0x80270250	This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again.
0x80270251	This app can't be activated from an elevated context.
0x80270252	This app can't be activated when UAC is disabled.
0x80270253	This app can't be activated by the Built-in Administrator.
0x80270254	This app does not support the contract specified or is not installed.
0x80270255	This app has multiple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous.
0x80270256	This app's package family has more than one package installed. This is not supported.
0x80270257	The app manager is required to activate applications, but is not running.
0x8027025A	The app didn't start in the required time.
0x8027025B	The app didn't start.
0x8027025C	This app failed to launch because of an issue with its license. Please try again in a moment.
0x8027025D	This app failed to launch because its trial license has expired.
0x80270260	Please choose a folder on a drive that's formatted with the NTFS file system.
0x80270261	This location is already being used. Please choose a different location.
0x80270262	This location cannot be indexed. Please choose a different location.
0x80270263	Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later.
0x80270264	Sorry, the action couldn't be completed.
0x80270265	This content can only be moved to a folder. To move the content to this drive, please choose or create a folder.
0x80280000	This is an error mask to convert TPM hardware errors to win errors.
0x80280001	TPM 1.2: Authentication failed.
0x80280002	TPM 1.2: The index to a PCR, DIR or other register is incorrect.
0x80280003	TPM 1.2: One or more parameter is bad.
0x80280004	TPM 1.2: An operation completed successfully but the auditing of that operation failed.
0x80280005	TPM 1.2: The clear disable flag is set and all clear operations now require physical access.
0x80280006	TPM 1.2: Activate the Trusted Platform Module (TPM).
0x80280007	TPM 1.2: Enable the Trusted Platform Module (TPM).
0x80280008	TPM 1.2: The target command has been disabled.
0x80280009	TPM 1.2: The operation failed.
0x8028000A	TPM 1.2: The ordinal was unknown or inconsistent.
0x8028000B	TPM 1.2: The ability to install an owner is disabled.
0x8028000C	TPM 1.2: The key handle cannot be interpreted.
0x8028000D	TPM 1.2: The key handle points to an invalid key.
0x8028000E	TPM 1.2: Unacceptable encryption scheme.
0x8028000F	TPM 1.2: Migration authorization failed.
0x80280010	TPM 1.2: PCR information could not be interpreted.
0x80280011	TPM 1.2: No room to load key.
0x80280012	TPM 1.2: There is no Storage Root Key (SRK) set.
0x80280013	TPM 1.2: An encrypted blob is invalid or was not created by this TPM.
0x80280014	TPM 1.2: The Trusted Platform Module (TPM) already has an owner.
0x80280015	TPM 1.2: The TPM has insufficient internal resources to perform the requested action.
0x80280016	TPM 1.2: A random string was too short.
0x80280017	TPM 1.2: The TPM does not have the space to perform the operation.
0x80280018	TPM 1.2: The named PCR value does not match the current PCR value.
0x80280019	TPM 1.2: The paramSize argument to the command has the incorrect value .
0x8028001A	TPM 1.2: There is no existing SHA-1 thread.
0x8028001B	TPM 1.2: The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error.
0x8028001C	TPM 1.2: 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.
0x8028001D	TPM 1.2: The authorization for the second key in a 2 key function failed authorization.
0x8028001E	TPM 1.2: The tag value sent to for a command is invalid.
0x8028001F	TPM 1.2: An IO error occurred transmitting information to the TPM.
0x80280020	TPM 1.2: The encryption process had a problem.
0x80280021	TPM 1.2: The decryption process did not complete.
0x80280022	TPM 1.2: An invalid handle was used.
0x80280023	TPM 1.2: The TPM does not have an Endorsement Key (EK) installed.
0x80280024	TPM 1.2: The usage of a key is not allowed.
0x80280025	TPM 1.2: The submitted entity type is not allowed.
0x80280026	TPM 1.2: The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup.
0x80280027	TPM 1.2: Signed data cannot include additional DER information.
0x80280028	TPM 1.2: The key properties in TPM_KEY_PARMs are not supported by this TPM.
0x80280029	TPM 1.2: The migration properties of this key are incorrect.
0x8028002A	TPM 1.2: The signature or encryption scheme for this key is incorrect or not permitted in this situation.
0x8028002B	TPM 1.2: The size of the data (or blob) parameter is bad or inconsistent with the referenced key.
0x8028002C	TPM 1.2: A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob.
0x8028002D	TPM 1.2: Either the physicalPresence or physicalPresenceLock bits have the wrong value.
0x8028002E	TPM 1.2: The TPM cannot perform this version of the capability.
0x8028002F	TPM 1.2: The TPM does not allow for wrapped transport sessions.
0x80280030	TPM 1.2: TPM audit construction failed and the underlying command was returning a failure code also.
0x80280031	TPM 1.2: TPM audit construction failed and the underlying command was returning success.
0x80280032	TPM 1.2: Attempt to reset a PCR register that does not have the resettable attribute.
0x80280033	TPM 1.2: Attempt to reset a PCR register that requires locality and locality modifier not part of command transport.
0x80280034	TPM 1.2: Make identity blob not properly typed.
0x80280035	TPM 1.2: When saving context identified resource type does not match actual resource.
0x80280036	TPM 1.2: The TPM is attempting to execute a command only available when in FIPS mode.
0x80280037	TPM 1.2: The command is attempting to use an invalid family ID.
0x80280038	TPM 1.2: The permission to manipulate the NV storage is not available.
0x80280039	TPM 1.2: The operation requires a signed command.
0x8028003A	TPM 1.2: Wrong operation to load an NV key.
0x8028003B	TPM 1.2: NV_LoadKey blob requires both owner and blob authorization.
0x8028003C	TPM 1.2: The NV area is locked and not writable.
0x8028003D	TPM 1.2: The locality is incorrect for the attempted operation.
0x8028003E	TPM 1.2: The NV area is read only and can't be written to.
0x8028003F	TPM 1.2: There is no protection on the write to the NV area.
0x80280040	TPM 1.2: The family count value does not match.
0x80280041	TPM 1.2: The NV area has already been written to.
0x80280042	TPM 1.2: The NV area attributes conflict.
0x80280043	TPM 1.2: The structure tag and version are invalid or inconsistent.
0x80280044	TPM 1.2: The key is under control of the TPM Owner and can only be evicted by the TPM Owner.
0x80280045	TPM 1.2: The counter handle is incorrect.
0x80280046	TPM 1.2: The write is not a complete write of the area.
0x80280047	TPM 1.2: The gap between saved context counts is too large.
0x80280048	TPM 1.2: The maximum number of NV writes without an owner has been exceeded.
0x80280049	TPM 1.2: No operator AuthData value is set.
0x8028004A	TPM 1.2: The resource pointed to by context is not loaded.
0x8028004B	TPM 1.2: The delegate administration is locked.
0x8028004C	TPM 1.2: Attempt to manage a family other then the delegated family.
0x8028004D	TPM 1.2: Delegation table management not enabled.
0x8028004E	TPM 1.2: There was a command executed outside of an exclusive transport session.
0x8028004F	TPM 1.2: Attempt to context save a owner evict controlled key.
0x80280050	TPM 1.2: The DAA command has no resources available to execute the command.
0x80280051	TPM 1.2: The consistency check on DAA parameter inputData0 has failed.
0x80280052	TPM 1.2: The consistency check on DAA parameter inputData1 has failed.
0x80280053	TPM 1.2: The consistency check on DAA_issuerSettings has failed.
0x80280054	TPM 1.2: The consistency check on DAA_tpmSpecific has failed.
0x80280055	TPM 1.2: The atomic process indicated by the submitted DAA command is not the expected process.
0x80280056	TPM 1.2: The issuer's validity check has detected an inconsistency.
0x80280057	TPM 1.2: The consistency check on w has failed.
0x80280058	TPM 1.2: The handle is incorrect.
0x80280059	TPM 1.2: Delegation is not correct.
0x8028005A	TPM 1.2: The context blob is invalid.
0x8028005B	TPM 1.2: Too many contexts held by the TPM.
0x8028005C	TPM 1.2: Migration authority signature validation failure.
0x8028005D	TPM 1.2: Migration destination not authenticated.
0x8028005E	TPM 1.2: Migration source incorrect.
0x8028005F	TPM 1.2: Incorrect migration authority.
0x80280061	TPM 1.2: Attempt to revoke the EK and the EK is not revocable.
0x80280062	TPM 1.2: Bad signature of CMK ticket.
0x80280063	TPM 1.2: There is no room in the context list for additional contexts.
0x80280081	TPM 2.0: Asymmetric algorithm not supported or not correct.
0x80280082	TPM 2.0: Inconsistent attributes.
0x80280083	TPM 2.0: Hash algorithm not supported or not appropriate.
0x80280084	TPM 2.0: Value is out of range or is not correct for the context.
0x80280085	TPM 2.0: Hierarchy is not enabled or is not correct for the use.
0x80280087	TPM 2.0: Key size is not supported.
0x80280088	TPM 2.0: Mask generation function not supported.
0x80280089	TPM 2.0: Mode of operation not supported.
0x8028008A	TPM 2.0: The type of the value is not appropriate for the use.
0x8028008B	TPM 2.0: The Handle is not correct for the use.
0x8028008C	TPM 2.0: Unsupported key derivation function or function not appropriate for use.
0x8028008D	TPM 2.0: Value was out of allowed range.
0x8028008E	TPM 2.0: The authorization HMAC check failed and DA counter incremented.
0x8028008F	TPM 2.0: Invalid nonce size.
0x80280090	TPM 2.0: Authorization requires assertion of PP.
0x80280092	TPM 2.0: Unsupported or incompatible scheme.
0x80280095	TPM 2.0: Structure is wrong size.
0x80280096	TPM 2.0: Unsupported symmetric algorithm or key size, or not appropriate for instance.
0x80280097	TPM 2.0: Incorrect structure tag.
0x80280098	TPM 2.0: Union selector is incorrect.
0x8028009A	TPM 2.0: The TPM was unable to unmarshal a value because there were not enough octets in the input buffer.
0x8028009B	TPM 2.0: The signature is not valid.
0x8028009C	TPM 2.0: Key fields are not compatible with the selected use.
0x8028009D	TPM 2.0: A policy check failed.
0x8028009F	TPM 2.0: Integrity check failed.
0x802800A0	TPM 2.0: Invalid ticket.
0x802800A1	TPM 2.0: Reserved bits not set to zero as required.
0x802800A2	TPM 2.0: Authorization failure without DA implications.
0x802800A3	TPM 2.0: The policy has expired.
0x802800A4	TPM 2.0: The command code in the policy is not the command code of the command or the command code in a policy command references a command that is not implemented.
0x802800A5	TPM 2.0: Public and sensitive portions of an object are not cryptographically bound.
0x802800A6	TPM 2.0: Curve not supported.
0x802800A7	TPM 2.0: Point is not on the required curve.
0x80280100	TPM 2.0: TPM not initialized.
0x80280101	TPM 2.0: Commands not being accepted because of a TPM failure.
0x80280103	TPM 2.0: Improper use of a sequence handle.
0x8028010B	TPM 2.0: TPM_RC_PRIVATE error.
0x80280119	TPM 2.0: TPM_RC_HMAC.
0x80280120	TPM 2.0: TPM_RC_DISABLED.
0x80280121	TPM 2.0: Command failed because audit sequence required exclusivity.
0x80280123	TPM 2.0: Unsupported ECC curve.
0x80280124	TPM 2.0: Authorization handle is not correct for command.
0x80280125	TPM 2.0: Command requires an authorization session for handle and is not present.
0x80280126	TPM 2.0: Policy failure in Math Operation or an invalid authPolicy value.
0x80280127	TPM 2.0: PCR check fail.
0x80280128	TPM 2.0: PCR have changed since checked.
0x8028012D	TPM 2.0: The TPM is not in the right mode for upgrade.
0x8028012E	TPM 2.0: Context ID counter is at maximum.
0x8028012F	TPM 2.0: authValue or authPolicy is not available for selected entity.
0x80280130	TPM 2.0: A _TPM_Init and Startup(CLEAR) is required before the TPM can resume operation.
0x80280131	TPM 2.0: The protection algorithms (hash and symmetric) are not reasonably balanced. The digest size of the hash must be larger than the key size of the symmetric algorithm.
0x80280142	TPM 2.0: The TPM command's commandSize value is inconsistent with contents of the command buffer; either the size is not the same as the bytes loaded by the hardware interface layer or the value is not large enough to hold a command header.
0x80280143	TPM 2.0: Command code not supported.
0x80280144	TPM 2.0: The value of authorizationSize is out of range or the number of octets in the authorization Area is greater than required.
0x80280145	TPM 2.0: Use of an authorization session with a context command or another command that cannot have an authorization session.
0x80280146	TPM 2.0: NV offset+size is out of range.
0x80280147	TPM 2.0: Requested allocation size is larger than allowed.
0x80280148	TPM 2.0: NV access locked.
0x80280149	TPM 2.0: NV access authorization fails in command actions
0x8028014A	TPM 2.0: An NV index is used before being initialized or the state saved by TPM2_Shutdown(STATE) could not be restored.
0x8028014B	TPM 2.0: Insufficient space for NV allocation.
0x8028014C	TPM 2.0: NV index or persistent object already defined.
0x80280150	TPM 2.0: Context in TPM2_ContextLoad() is not valid.
0x80280151	TPM 2.0: chHash value already set or not correct for use.
0x80280152	TPM 2.0: Handle for parent is not a valid parent.
0x80280153	TPM 2.0: Some function needs testing.
0x80280154	TPM 2.0: returned when an internal function cannot process a request due to an unspecified problem. This code is usually related to invalid parameters that are not properly filtered by the input unmarshaling code.
0x80280155	TPM 2.0: The sensitive area did not unmarshal correctly after decryption - this code is used in lieu of the other unmarshaling errors so that an attacker cannot determine where the unmarshaling error occurred.
0x80280400	The command was blocked.
0x80280401	The specified handle was not found.
0x80280402	The TPM returned a duplicate handle and the command needs to be resubmitted.
0x80280403	The command within the transport was blocked.
0x80280404	The command within the transport is not supported.
0x80280800	The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time.
0x80280801	SelfTestFull has not been run.
0x80280802	The TPM is currently executing a full selftest.
0x80280803	The TPM is defending against dictionary attacks and is in a time-out period.
0x80280901	TPM 2.0: Gap for context ID is too large.
0x80280902	TPM 2.0: Out of memory for object contexts.
0x80280903	TPM 2.0: Out of memory for session contexts.
0x80280904	TPM 2.0: Out of shared object/session memory or need space for internal operations.
0x80280905	TPM 2.0: Out of session handles - a session must be flushed before a nes session may be created.
0x80280906	TPM 2.0: Out of object handles - the handle space for objects is depleted and a reboot is required.
0x80280907	TPM 2.0: Bad locality.
0x80280908	TPM 2.0: The TPM has suspended operation on the command; forward progress was made and the command may be retried.
0x80280909	TPM 2.0: The command was canceled.
0x8028090A	TPM 2.0: TPM is performing self-tests.
0x80280920	TPM 2.0: The TPM is rate-limiting accesses to prevent wearout of NV
0x80280921	TPM 2.0: Authorization for objects subject to DA protection are not allowed at this time because the TPM is in DA lockout mode.
0x80280922	TPM 2.0: The TPM was not able to start the command.
0x80280923	TPM 2.0: the command may require writing of NV and NV is not current accessible.
0x80284001	An internal error has occurred within the Trusted Platform Module support program.
0x80284002	One or more input parameters is bad.
0x80284003	A specified output pointer is bad.
0x80284004	The specified context handle does not refer to a valid context.
0x80284005	A specified output buffer is too small.
0x80284006	An error occurred while communicating with the TPM.
0x80284007	One or more context parameters is invalid.
0x80284008	The TBS service is not running and could not be started.
0x80284009	A new context could not be created because there are too many open contexts.
0x8028400A	A new virtual resource could not be created because there are too many open virtual resources.
0x8028400B	The TBS service has been started but is not yet running.
0x8028400C	The physical presence interface is not supported.
0x8028400D	The command was canceled.
0x8028400E	The input or output buffer is too large.
0x8028400F	A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer.
0x80284010	The TBS service has been disabled.
0x80284011	No TCG event log is available.
0x80284012	The caller does not have the appropriate rights to perform the requested operation.
0x80284013	The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions may be required. The TPM management console (tpm.msc) action to make the TPM Ready may help. For further information, see the documentation for the Win32_Tpm WMI method 'Provision'. (The actions that may be required include importing the TPM Owner Authorization value into the system, calling the Win32_Tpm WMI method for provisioning the TPM and specifying TRUE for either 'ForceClear_Allowed' or 'PhysicalPresencePrompts_Allowed' (as indicated by the value returned in the Additional Information), or enabling the TPM in the system BIOS.)
0x80284014	The Physical Presence Interface of this firmware does not support the requested method.
0x80284015	The requested TPM OwnerAuth value was not found.
0x80284016	The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information.
0x80290100	The command buffer is not in the correct state.
0x80290101	The command buffer does not contain enough data to satisfy the request.
0x80290102	The command buffer cannot contain any more data.
0x80290103	One or more output parameters was NULL or invalid.
0x80290104	One or more input parameters is invalid.
0x80290105	Not enough memory was available to satisfy the request.
0x80290106	The specified buffer was too small.
0x80290107	An internal error was detected.
0x80290108	The caller does not have the appropriate rights to perform the requested operation.
0x80290109	The specified authorization information was invalid.
0x8029010A	The specified context handle was not valid.
0x8029010B	An error occurred while communicating with the TBS.
0x8029010C	The TPM returned an unexpected result.
0x8029010D	The message was too large for the encoding scheme.
0x8029010E	The encoding in the blob was not recognized.
0x8029010F	The key size is not valid.
0x80290110	The encryption operation failed.
0x80290111	The key parameters structure was not valid
0x80290112	The requested supplied data does not appear to be a valid migration authorization blob.
0x80290113	The specified PCR index was invalid
0x80290114	The data given does not appear to be a valid delegate blob.
0x80290115	One or more of the specified context parameters was not valid.
0x80290116	The data given does not appear to be a valid key blob
0x80290117	The specified PCR data was invalid.
0x80290118	The format of the owner auth data was invalid.
0x80290119	The random number generated did not pass FIPS RNG check.
0x8029011A	The TCG Event Log does not contain any data.
0x8029011B	An entry in the TCG Event Log was invalid.
0x8029011C	A TCG Separator was not found.
0x8029011D	A digest value in a TCG Log entry did not match hashed data.
0x8029011E	The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance.
0x8029011F	The Windows TPM NV Bits index is not defined.
0x80290120	The Windows TPM NV Bits index is not ready for use.
0x80290121	The TPM key that was used to seal the data is no longer available.
0x80290122	An authorization chain could not be found that authorizes the PolicyAuthorize unseal.
0x80290123	The SVN counter to which the authorization was bound is not available.
0x80290124	The TPM Storage hierarchy (Owner) auth value is required to be NULL for this operation.
0x80290125	The TPM Endorsement hierarchy auth value is required to be NULL for this operation.
0x80290126	The authorization to perform this operation has been revoked.
0x80290127	The authorization public key is malformed.
0x80290128	The authorization public key is not supported.
0x80290129	The authorization signature is invalid.
0x8029012A	The authorization policy is malformed.
0x8029012B	The authorization data is malformed.
0x8029012C	The key used to unseal this data has changed since sealing the data. This may be the result of a TPM clear.
0x8029012D	The TPM version is invalid.
0x8029012E	The policy authorization blob type is invalid.
0x80290200	The specified buffer was too small.
0x80290201	The context could not be cleaned up.
0x80290202	The specified context handle is invalid.
0x80290203	An invalid context parameter was specified.
0x80290204	An error occurred while communicating with the TPM
0x80290205	No entry with the specified key was found.
0x80290206	The specified virtual handle matches a virtual handle already in use.
0x80290207	The pointer to the returned handle location was NULL or invalid
0x80290208	One or more parameters is invalid
0x80290209	The RPC subsystem could not be initialized.
0x8029020A	The TBS scheduler is not running.
0x8029020B	The command was canceled.
0x8029020C	There was not enough memory to fulfill the request
0x8029020D	The specified list is empty, or the iteration has reached the end of the list.
0x8029020E	The specified item was not found in the list.
0x8029020F	The TPM does not have enough space to load the requested resource.
0x80290210	There are too many TPM contexts in use.
0x80290211	The TPM command failed.
0x80290212	The TBS does not recognize the specified ordinal.
0x80290213	The requested resource is no longer available.
0x80290214	The resource type did not match.
0x80290215	No resources can be unloaded.
0x80290216	No new entries can be added to the hash table.
0x80290217	A new TBS context could not be created because there are too many open contexts.
0x80290218	A new virtual resource could not be created because there are too many open virtual resources.
0x80290219	The physical presence interface is not supported.
0x8029021A	TBS is not compatible with the version of TPM found on the system.
0x8029021B	No TCG event log is available.
0x80290300	A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command.
0x80290301	The user failed to confirm the TPM operation request.
0x80290302	The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM).
0x80290303	The BIOS does not support the physical presence interface.
0x80290304	The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command.
0x80290400	This is an error mask to convert Platform Crypto Provider errors to win errors.
0x80290401	The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational.
0x80290402	The handle provided to the Platform Crypto Provider is invalid.
0x80290403	A parameter provided to the Platform Crypto Provider is invalid.
0x80290404	A provided flag to the Platform Crypto Provider is not supported.
0x80290405	The requested operation is not supported by this Platform Crypto Provider.
0x80290406	The buffer is too small to contain all data. No information has been written to the buffer.
0x80290407	An unexpected internal error has occurred in the Platform Crypto Provider.
0x80290408	The authorization to use a provider object has failed.
0x80290409	The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack.
0x8029040A	The referenced policy was not found.
0x8029040B	The referenced profile was not found.
0x8029040C	The validation was not succesful.
0x8029040E	An attempt was made to import or load a key under an incorrect storage parent.
0x8029040F	The TPM key is not loaded.
0x80290410	The TPM key certification has not been generated.
0x80290411	The TPM key is not yet finalized.
0x80290412	The TPM attestation challenge is not set.
0x80290413	The TPM PCR info is not available.
0x80290414	The TPM key is already finalized.
0x80290415	The TPM key usage policy is not supported.
0x80290416	The TPM key usage policy is invalid.
0x80290417	There was a problem with the software key being imported into the TPM.
0x80290418	The TPM key is not authenticated.
0x80290419	The TPM key is not an AIK.
0x8029041A	The TPM key is not a signing key.
0x8029041B	The TPM is locked out.
0x8029041C	The claim type requested is not supported.
0x8029041D	TPM version is not supported.
0x8029041E	The buffer lengths do not match.
0x8029041F	The RSA key creation is blocked on this TPM due to known security vulnerabilities.
0x80290420	A ticket required to use a key was not provided.
0x80290421	This key has a raw policy so the KSP can't authenticate against it.
0x80290422	The TPM key's handle was unexpectedly invalidated due to a hardware or firmware issue.
0x80290500	TPM related network operations are blocked as Zero Exhaust mode is enabled on client.
0x80290600	TPM provisioning did not run to completion.
0x80290601	An invalid owner authorization value was specified.
0x80290602	TPM command returned too much data.
0x802A0001	The object could not be created.
0x802A0002	Shutdown was already called on this object or the object that owns it.
0x802A0003	This method cannot be called during this type of callback.
0x802A0004	This object has been sealed, so this change is no longer allowed.
0x802A0005	The requested value was never set.
0x802A0006	The requested value cannot be determined.
0x802A0007	A callback returned an invalid output parameter.
0x802A0008	A callback returned a success code other than S_OK or S_FALSE.
0x802A0009	A parameter that should be owned by this object is owned by a different object.
0x802A000A	More than one item matched the search criteria.
0x802A000B	A floating-point overflow occurred.
0x802A000C	This method can only be called from the thread that created the object.
0x802A0101	The storyboard is currently in the schedule.
0x802A0102	The storyboard is not playing.
0x802A0103	The start keyframe might occur after the end keyframe.
0x802A0104	It might not be possible to determine the end keyframe time when the start keyframe is reached.
0x802A0105	Two repeated portions of a storyboard might overlap.
0x802A0106	The transition has already been added to a storyboard.
0x802A0107	The transition has not been added to a storyboard.
0x802A0108	The transition might eclipse the beginning of another transition in the storyboard.
0x802A0109	The given time is earlier than the time passed to the last update.
0x802A010A	This client is already connected to a timer.
0x802A010B	The passed dimension is invalid or does not match the object's dimension.
0x802A010C	The added primitive begins at or beyond the duration of the interpolator.
0x802A0201	The operation cannot be completed because the window is being closed.
0x80300002	Data Collector Set was not found.
0x80300045	Unable to start Data Collector Set because there are too many folders.
0x80300070	Not enough free disk space to start Data Collector Set.
0x803000AA	The Data Collector Set or one of its dependencies is already in use.
0x803000B7	Data Collector Set already exists.
0x80300101	Property value conflict.
0x80300102	The current configuration for this Data Collector Set requires that it contain exactly one Data Collector.
0x80300103	A user account is required in order to commit the current Data Collector Set properties.
0x80300104	Data Collector Set is not running.
0x80300105	A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list.
0x80300106	The executable path you have specified refers to a network share or UNC path.
0x80300107	The executable path you have specified is already configured for API tracing.
0x80300108	The executable path you have specified does not exist. Verify that the specified path is correct.
0x80300109	Data Collector already exists.
0x8030010A	The wait for the Data Collector Set start notification has timed out.
0x8030010B	The wait for the Data Collector to start has timed out.
0x8030010C	The wait for the report generation tool to finish has timed out.
0x8030010D	Duplicate items are not allowed.
0x8030010E	When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename.
0x8030010F	The session name provided is invalid.
0x80300110	The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation.
0x80300111	The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation.
0x80300112	The execution of the Rules Manager failed.
0x80300113	An error occurred while attempting to compress or extract the data.
0x80310000	This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel.
0x80310001	This drive is not encrypted.
0x80310002	The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions.
0x80310003	The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions.
0x80310004	A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date.
0x80310005	The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).
0x80310006	The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR).
0x80310007	At least one secure key protector is required for this operation to be performed.
0x80310008	BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker.
0x80310009	BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again.
0x8031000A	The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.
0x8031000B	The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.
0x8031000C	The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted.
0x8031000D	The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted.
0x8031000E	The attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects.
0x8031000F	The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed.
0x80310010	The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access.
0x80310011	The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again.
0x80310012	The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive.
0x80310013	The drive cannot be encrypted because the file system is not supported.
0x80310014	The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition.
0x80310015	This drive cannot be encrypted.
0x80310016	The data is not valid.
0x80310017	The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically.
0x80310018	You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption.
0x80310019	The operation attempted cannot be performed on an operating system drive.
0x8031001A	The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again.
0x8031001B	A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.
0x8031001C	A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker.
0x8031001D	One or more BitLocker key protectors are required. You cannot delete the last key on this drive.
0x8031001E	Cluster configurations are not supported by BitLocker Drive Encryption.
0x8031001F	The drive specified is already configured to be automatically unlocked on the current computer.
0x80310020	The operating system drive is not protected by BitLocker Drive Encryption.
0x80310021	BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key.
0x80310022	The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive.
0x80310023	BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive.
0x80310024	The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again.
0x80310025	The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker.
0x80310026	The drive encryption algorithm cannot be used on this sector size.
0x80310027	The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again.
0x80310028	The drive specified is not the operating system drive.
0x80310029	BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer.
0x8031002A	The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector.
0x8031002B	BitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker.
0x8031002C	Group Policy settings require that a recovery password be specified before encrypting the drive.
0x8031002D	The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker.
0x8031002E	BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive.
0x80310030	BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker.
0x80310031	This key protector cannot be added. Only one key protector of this type is allowed for this drive.
0x80310032	The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path.
0x80310033	The specified key protector was not found on the drive. Try another key protector.
0x80310034	The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive.
0x80310035	The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again.
0x80310036	The random number generator check test failed.
0x80310037	The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent.
0x80310038	The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration.
0x80310039	The drive must be fully decrypted to complete this operation.
0x8031003A	The key protector specified cannot be used for this operation.
0x8031003B	No key protectors exist on the drive to perform the hardware test.
0x8031003C	The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions.
0x8031003D	The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again.
0x8031003E	The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again.
0x8031003F	The Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption.
0x80310040	The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes.
0x80310041	The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem.
0x80310042	The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM).
0x80310043	The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN.
0x80310044	A boot application has changed since BitLocker Drive Encryption was enabled.
0x80310045	The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled.
0x80310046	The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information.
0x80310047	This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again.
0x80310048	BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions.
0x80310049	This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system.
0x8031004A	BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer.
0x8031004B	The drive cannot be locked when the drive is in use.
0x8031004C	The access token associated with the current thread is not an impersonated token.
0x8031004D	The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available.
0x8031004E	You must restart your computer before continuing with BitLocker Drive Encryption.
0x8031004F	Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging.
0x80310050	No action was taken as BitLocker Drive Encryption is in raw access mode.
0x80310051	BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use.
0x80310052	The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again.
0x80310053	BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments.
0x80310054	The auto-unlock master key was not available from the operating system drive.
0x80310055	The system firmware failed to enable clearing of system memory when the computer was restarted.
0x80310056	The hidden drive cannot be encrypted.
0x80310057	BitLocker encryption keys were ignored because the drive was in a transient state.
0x80310058	Public key based protectors are not allowed on this drive.
0x80310059	BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing.
0x8031005A	This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system.
0x8031005B	The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information.
0x8031005C	Group Policy settings do not permit the creation of a recovery password.
0x8031005D	Group Policy settings require the creation of a recovery password.
0x8031005E	Group Policy settings do not permit the creation of a recovery key.
0x8031005F	Group Policy settings require the creation of a recovery key.
0x80310060	Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option.
0x80310061	Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option.
0x80310062	Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option.
0x80310063	Group Policy settings require the use of a startup key. Please choose this BitLocker startup option.
0x80310064	Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option.
0x80310065	Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option.
0x80310066	Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option.
0x80310067	Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option.
0x80310068	The PIN provided does not meet minimum or maximum length requirements.
0x80310069	The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector.
0x8031006A	Group Policy settings do not permit the creation of a password.
0x8031006B	Group Policy settings require the creation of a password.
0x8031006C	The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information.
0x8031006D	A password cannot be added to the operating system drive.
0x8031006E	The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive.
0x8031006F	The drive is too small to be protected using BitLocker Drive Encryption.
0x80310070	The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives.
0x80310071	The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go.
0x80310072	Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption.
0x80310073	Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption.
0x80310074	Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption.
0x80310075	Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked.
0x80310076	Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked.
0x80310077	Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives.
0x80310078	Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker.
0x80310079	Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker.
0x80310080	Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization.
0x80310081	Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols.
0x80310082	This drive cannot be encrypted because it is reserved for Windows System Recovery Options.
0x80310083	BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.
0x80310084	BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker.
0x80310085	The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker.
0x80310086	BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker.
0x80310087	BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
0x80310088	BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.
0x80310089	The requested virtualization size is too big.
0x80310090	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
0x80310091	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
0x80310092	BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker.
0x80310093	The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement.
0x80310094	The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid.
0x80310095	Removal of the data recovery agent certificate must be done using the Certificates snap-in.
0x80310096	This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command.
0x80310097	The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive.
0x80310098	The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments.
0x80310099	The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals.
0x8031009A	The requested TPM PIN contains invalid characters.
0x8031009B	The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version.
0x8031009C	The feature is only supported on EFI systems.
0x8031009D	More than one Network Key Protector certificate has been found on the system.
0x8031009E	Removal of the Network Key Protector certificate must be done using the Certificates snap-in.
0x8031009F	An invalid certificate has been found in the Network Key Protector certificate store.
0x803100A0	This drive isn't protected with a PIN.
0x803100A1	Please enter the correct current PIN.
0x803100A2	You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator.
0x803100A3	BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator.
0x803100A4	Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ .
0x803100A5	BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.
0x803100A6	BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.
0x803100A7	The required authentication key length is not supported by the drive.
0x803100A8	This drive isn't protected with a password.
0x803100A9	Please enter the correct current password.
0x803100AA	The password cannot exceed 256 characters.
0x803100AB	A password key protector cannot be added because a TPM protector exists on the drive.
0x803100AC	A TPM key protector cannot be added because a password protector exists on the drive.
0x803100AD	This command can only be performed from the coordinator node for the specified CSV volume.
0x803100AE	This command cannot be performed on a volume when it is part of a cluster.
0x803100AF	BitLocker did not revert to using BitLocker software encryption due to group policy configuration.
0x803100B0	The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use.
0x803100B1	Group Policy settings do not allow the use of hardware-based encryption.
0x803100B2	The drive specified does not support hardware-based encryption.
0x803100B3	BitLocker cannot be upgraded during disk encryption or decryption.
0x803100B4	Discovery Volumes are not supported for volumes using hardware encryption.
0x803100B5	No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume.
0x803100B6	No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume.
0x803100B7	Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume.
0x803100B8	Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume.
0x803100B9	Wipe of free space is not currently taking place.
0x803100BA	BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled.
0x803100BB	BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker.
0x803100BC	Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.
0x803100BD	BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume.
0x803100BE	BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker.
0x803100BF	This PC's firmware is not capable of supporting hardware encryption.
0x803100C0	BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator.
0x803100C1	You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator.
0x803100C2	BitLocker cannot save the recovery password because the specified Microsoft account is Suspended.
0x803100C3	BitLocker cannot save the recovery password because the specified Microsoft account is Blocked.
0x803100C4	This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy.
0x803100C5	This PC cannot support device encryption because unencrypted fixed data volumes are present.
0x803100C6	This PC does not meet the hardware requirements to support device encryption.
0x803100C7	This PC cannot support device encryption because WinRE is not properly configured.
0x803100C8	Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot.
0x803100C9	This PC is not provisioned to support device encryption.
0x803100CA	Device Lock has been triggered due to too many incorrect password attempts.
0x803100CB	Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information.
0x803100CC	Your PIN can only contain numbers from 0 to 9.
0x803100CD	BitLocker cannot use hardware replay protection because no counter is available on your PC.
0x803100CE	Device Lockout state validation failed due to counter mismatch.
0x803100CF	The input buffer is too large.
0x803100D0	The target of an invocation does not support requested capability.
0x803100D1	Device encryption is currently blocked by this PC's configuration.
0x803100D2	This drive has been opted out of device encryption.
0x803100D3	Device encryption isn't available for this drive.
0x803100D4	The encrypt on write mode for BitLocker is not supported in this version of Windows. You can turn on BitLocker without using the encrypt on write mode.
0x803100D5	Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator.
0x803100D6	Device encryption can't be turned off while this drive is being encrypted. Please try again later.
0x803100D7	This action isn't supported because this drive isn't automatically managed with device encryption.
0x803100D8	BitLocker can't be suspended on this drive until the next restart.
0x803100D9	BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume.
0x803100DA	BitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for the OS drive.
0x803100DB	BitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for fixed data drives.
0x803100DC	BitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for removable data drives
0x803100DD	BitLocker recovery password rotation not supported.
0x803100DE	A server issued BitLocker recovery password rotation was denied because requests must be 15 minutes apart.
0x803100DF	BitLocker recovery password key rotation policy is not enabled.
0x803100E0	BitLocker recovery password key rotation could not be performed because the device is neither Azure AD joined nor Hybrid Azure AD joined.
0x803100E1	BitLocker recovery key backup endpoint is busy and cannot perform requested operation. Please retry after sometime.
0x803100E5	Adding BitLocker predicted TPM based protector is not supported.
0x803100E6	Registeration for TPM callback is not supported.
0x803100E7	Creating new TPM context is not supported.
0x803100E8	The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration.
0x80320001	The callout does not exist.
0x80320002	The filter condition does not exist.
0x80320003	The filter does not exist.
0x80320004	The layer does not exist.
0x80320005	The provider does not exist.
0x80320006	The provider context does not exist.
0x80320007	The sublayer does not exist.
0x80320008	The object does not exist.
0x80320009	An object with that GUID or LUID already exists.
0x8032000A	The object is referenced by other objects so cannot be deleted.
0x8032000B	The call is not allowed from within a dynamic session.
0x8032000C	The call was made from the wrong session so cannot be completed.
0x8032000D	The call must be made from within an explicit transaction.
0x8032000E	The call is not allowed from within an explicit transaction.
0x8032000F	The explicit transaction has been forcibly cancelled.
0x80320010	The session has been cancelled.
0x80320011	The call is not allowed from within a read-only transaction.
0x80320012	The call timed out while waiting to acquire the transaction lock.
0x80320013	Collection of network diagnostic events is disabled.
0x80320014	The operation is not supported by the specified layer.
0x80320015	The call is allowed for kernel-mode callers only.
0x80320016	The call tried to associate two objects with incompatible lifetimes.
0x80320017	The object is built in so cannot be deleted.
0x80320018	The maximum number of callouts has been reached.
0x80320019	A notification could not be delivered because a message queue is at its maximum capacity.
0x8032001A	The traffic parameters do not match those for the security association context.
0x8032001B	The call is not allowed for the current security association state.
0x8032001C	A required pointer is null.
0x8032001D	An enumerator is not valid.
0x8032001E	The flags field contains an invalid value.
0x8032001F	A network mask is not valid.
0x80320020	An FWP_RANGE is not valid.
0x80320021	The time interval is not valid.
0x80320022	An array that must contain at least one element is zero length.
0x80320023	The displayData.name field cannot be null.
0x80320024	The action type is not one of the allowed action types for a filter.
0x80320025	The filter weight is not valid.
0x80320026	A filter condition contains a match type that is not compatible with the operands.
0x80320027	An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type.
0x80320028	An integer value is outside the allowed range.
0x80320029	A reserved field is non-zero.
0x8032002A	A filter cannot contain multiple conditions operating on a single field.
0x8032002B	A policy cannot contain the same keying module more than once.
0x8032002C	The action type is not compatible with the layer.
0x8032002D	The action type is not compatible with the sublayer.
0x8032002E	The raw context or the provider context is not compatible with the layer.
0x8032002F	The raw context or the provider context is not compatible with the callout.
0x80320030	The authentication method is not compatible with the policy type.
0x80320031	The Diffie-Hellman group is not compatible with the policy type.
0x80320032	An IKE policy cannot contain an Extended Mode policy.
0x80320033	The enumeration template or subscription will never match any objects.
0x80320034	The provider context is of the wrong type.
0x80320035	The parameter is incorrect.
0x80320036	The maximum number of sublayers has been reached.
0x80320037	The notification function for a callout returned an error.
0x80320038	The IPsec authentication transform is not valid.
0x80320039	The IPsec cipher transform is not valid.
0x8032003A	The IPsec cipher transform is not compatible with the policy.
0x8032003B	The combination of IPsec transform types is not valid.
0x8032003C	A policy cannot contain the same auth method more than once.
0x8032003D	A tunnel endpoint configuration is invalid.
0x8032003E	The WFP MAC Layers are not ready.
0x8032003F	A key manager capable of key dictation is already registered
0x80320040	A key manager dictated invalid keys
0x80320041	The BFE IPsec Connection Tracking is disabled.
0x80320042	The DNS name is invalid.
0x80320043	The engine option is still enabled due to other configuration settings.
0x80320044	The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine.
0x80320104	The packet should be dropped, no ICMP should be sent.
0x80340002	The binding to the network interface is being closed.
0x80340004	An invalid version was specified.
0x80340005	An invalid characteristics table was used.
0x80340006	Failed to find the network interface or network interface is not ready.
0x80340007	Failed to open the network interface.
0x80340008	Network interface has encountered an internal unrecoverable failure.
0x80340009	The multicast list on the network interface is full.
0x8034000A	An attempt was made to add a duplicate multicast address to the list.
0x8034000B	At attempt was made to remove a multicast address that was never added.
0x8034000C	Netowork interface aborted the request.
0x8034000D	Network interface can not process the request because it is being reset.
0x8034000F	An attempt was made to send an invalid packet on a network interface.
0x80340010	The specified request is not a valid operation for the target device.
0x80340011	Network interface is not ready to complete this operation.
0x80340014	The length of the buffer submitted for this operation is not valid.
0x80340015	The data used for this operation is not valid.
0x80340016	The length of buffer submitted for this operation is too small.
0x80340017	Network interface does not support this OID (Object Identifier)
0x80340018	The network interface has been removed.
0x80340019	Network interface does not support this media type.
0x8034001A	An attempt was made to remove a token ring group address that is in use by other components.
0x8034001B	An attempt was made to map a file that can not be found.
0x8034001C	An error occurred while NDIS tried to map the file.
0x8034001D	An attempt was made to map a file that is alreay mapped.
0x8034001E	An attempt to allocate a hardware resource failed because the resource is used by another component.
0x8034001F	The I/O operation failed because network media is disconnected or wireless access point is out of range.
0x80340022	The network address used in the request is invalid.
0x8034002A	The offload operation on the network interface has been paused.
0x8034002B	Network interface was not found.
0x8034002C	The revision number specified in the structure is not supported.
0x8034002D	The specified port does not exist on this network interface.
0x8034002E	The current state of the specified port on this network interface does not support the requested operation.
0x8034002F	The miniport adapter is in low power state.
0x80340030	This operation requires the miniport adapter to be reinitialized.
0x80340031	There are not enough queues to complete the operation.
0x803400BB	Netword interface does not support this request.
0x80342000	The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation.
0x80342001	The wireless local area network interface is busy and can not perform the requested operation.
0x80342002	The wireless local area network interface is powered down and doesn't support the requested operation.
0x80342003	The list of wake on LAN patterns is full.
0x80342004	The list of low power protocol offloads is full.
0x80342005	The wireless local area network interface cannot start an AP on the specified channel right now.
0x80342006	The wireless local area network interface cannot start an AP on the specified band right now.
0x80342007	The wireless local area network interface cannot start an AP on this channel due to regulatory reasons.
0x80342008	The wireless local area network interface cannot start an AP on this band due to regulatory reasons.
0x80370001	A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration.
0x80370100	The virtual machine or container exited unexpectedly while starting.
0x80370101	The container operating system does not match the host operating system.
0x80370102	The virtual machine could not be started because a required feature is not installed.
0x80370105	The requested virtual machine or container operation is not valid in the current state.
0x80370106	The virtual machine or container exited unexpectedly.
0x80370107	The virtual machine or container was forcefully exited.
0x80370108	A connection could not be established with the container or virtual machine.
0x80370109	The operation timed out because a response was not received from the virtual machine or container.
0x8037010A	The connection with the virtual machine or container was closed.
0x8037010B	An unknown internal message was received by the virtual machine or container.
0x8037010C	The virtual machine or container does not support an available version of the communication protocol with the host.
0x8037010D	The virtual machine or container JSON document is invalid.
0x8037010E	A virtual machine or container with the specified identifier does not exist.
0x8037010F	A virtual machine or container with the specified identifier already exists.
0x80370110	The virtual machine or container with the specified identifier is not running.
0x80370111	A communication protocol error has occurred between the virtual machine or container and the host.
0x80370112	The container image contains a layer with an unrecognized format.
0x80370113	To use this container image, you must join the Windows Insider Program. Please see https://go.microsoft.com/fwlink/?linkid=850659 for more information.
0x80370114	The operation could not be started because a required feature is not installed.
0x80370115	The operation has not started.
0x80370116	The operation is already running.
0x80370117	The operation is still running.
0x80370118	The operation did not complete in time.
0x80370119	An event callback has already been registered on this handle.
0x8037011A	Not enough memory available to return the result of the operation.
0x8037011B	Insufficient privileges. Only administrators or users that are members of the Hyper-V Administrators user group are permitted to access virtual machines or containers. To add yourself to the Hyper-V Administrators user group, please see https://aka.ms/hcsadmin for more information.
0x8037011C	The virtual machine or container reported a critical error and was stopped or restarted.
0x8037011D	The process information is not available.
0x8037011E	The host compute system service has disconnected unexpectedly.
0x8037011F	The process has already exited.
0x80370300	The specified capability does not exist.
0x80370301	The specified buffer is too small for the requested data.
0x80370302	The specified property does not exist.
0x80370303	The configuration of the hypervisor on this system is not supported.
0x80370304	The configuration of the partition is not valid.
0x80370305	The specified GPA range was not found.
0x80370306	A virtual processor with the specified index already exists.
0x80370307	A virtual processor with the specified index does not exist.
0x80370308	The virtual processor is not in the correct state to perform the requested operation.
0x80370309	A virtual processor register with the specified name does not exist.
0x80370310	The Windows Hypervisor Platform is not supported due to a processor limitation.
0x80380001	The regeneration operation was not able to copy all data from the active plexes due to bad sectors.
0x80380002	One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems.
0x80390001	Some BCD entries were not imported correctly from the BCD store.
0x80390003	Some BCD entries were not synchronized correctly with the firmware.
0x803A0001	The virtualization storage subsystem has generated an error.
0x803B0001	The network was not found.
0x803B0002	The endpoint was not found.
0x803B0003	The network's underlying layer was not found.
0x803B0004	The virtual switch was not found.
0x803B0005	The network does not have a subnet for this endpoint.
0x803B0006	An adapter was not found.
0x803B0007	The switch-port was not found.
0x803B0008	An expected policy was not found.
0x803B0009	A required VFP port setting was not found.
0x803B000A	The provided network configuration is invalid or missing parameters.
0x803B000B	Invalid network type.
0x803B000C	The provided endpoint configuration is invalid or missing parameters.
0x803B000D	The provided policy configuration is invalid or missing parameters.
0x803B000E	Invalid policy type.
0x803B000F	This requested operation is invalid for a remote endpoint.
0x803B0010	A network with this name already exists.
0x803B0011	A network with this name already exists.
0x803B0012	Policy information already exists on this object.
0x803B0013	The specified port already exists.
0x803B0014	This endpoint is already attached to the switch.
0x803B0015	The specified request is unsupported.
0x803B0016	Port mapping is not supported on the given network.
0x803B0017	There was an operation attempted on a degraded object.
0x803B0018	Cannot modify a switch shared by multiple networks.
0x803B0019	Failed to interpret a parameter as a GUID.
0x803B001A	Failed to process registry key.
0x803B001B	Invalid JSON document string.
0x803B001C	The reference is invalid in the JSON document.
0x803B001D	Endpoint sharing is disabled.
0x803B001E	IP address is either invalid or not part of any configured subnet(s).
0x803B001F	The specified switch extension does not exist on this switch.
0x803B0020	Operation cannot be performed while service is stopping.
0x803B0021	Operation cannot be performed while service module not found.
0x803B0022	Request Handlers not present to handle the JSON request.
0x803B0023	The specified request is unsupported.
0x803B0024	Add runtime keys to container failed.
0x803B0025	Timeout while waiting for network adapter with the given instance id
0x803B0026	Network adapter not found for the given instance id
0x803B0027	Network compartment not found for the given id
0x803B0028	Network interface not found for the given id
0x803B0029	Default Namespace already exists
0x803B002A	Internet Connection Sharing service (SharedAccess) is disabled and cannot be started
0x803B002B	This requested operation is invalid as endpoint is already part of a network namespace.
0x803B002C	The specified entity cannot be removed while it still has references.
0x803B002D	The internal port must exist and cannot be zero.
0x803B002E	The requested operation for attach namespace failed.
0x803B002F	An address provided is invalid or reserved.
0x803B0030	The prefix provided is invalid.
0x803B0031	A call was performed against an object that was torn down.
0x803B0032	The provided subnet configuration is invalid or missing parameters.
0x803B0033	The provided IP subnet configuration is invalid or missing parameters.
0x803B0034	The endpoint must be attached to complete the operation.
0x803B0035	The endpoint must be local to complete the operation.
0x803B0036	Cannot apply more than one InterfaceParameters policy.
0x803C0100	The operation was cancelled.
0x803C0101	An error occurred when running a PowerShell script.
0x803C0102	An error occurred when interacting with PowerShell runtime.
0x803C0103	An error occurred in the Scripted Diagnostic Managed Host.
0x803C0104	The troubleshooting pack does not contain a required verifier to complete the verification.
0x803C0106	Scripted diagnostics is disabled by group policy.
0x803C0107	Trust validation of the troubleshooting pack failed.
0x803C0108	The troubleshooting pack cannot be executed on this system.
0x803C0109	This version of the troubleshooting pack is not supported.
0x803C010A	A required resource cannot be loaded.
0x803C010B	The troubleshooting pack reported information for a root cause without adding the root cause.
0x803D0000	The input data was not in the expected format or did not have the expected value.
0x803D0001	The operation could not be completed because the object is in a faulted state due to a previous error.
0x803D0002	The operation could not be completed because it would lead to numeric overflow.
0x803D0003	The operation is not allowed due to the current state of the object.
0x803D0004	The operation was aborted.
0x803D0005	Access was denied by the remote endpoint.
0x803D0006	The operation did not complete within the time allotted.
0x803D0007	The operation was abandoned.
0x803D0008	A quota was exceeded.
0x803D0009	The information was not available in the specified language.
0x803D000A	Security verification was not successful for the received data.
0x803D000B	The address is already being used.
0x803D000C	The address is not valid for this context.
0x803D000D	The remote endpoint does not exist or could not be located.
0x803D000E	The remote endpoint is not currently in service at this location.
0x803D000F	The remote endpoint could not process the request.
0x803D0010	The remote endpoint was not reachable.
0x803D0011	The operation was not supported by the remote endpoint.
0x803D0012	The remote endpoint is unable to process the request due to being overloaded.
0x803D0013	A message containing a fault was received from the remote endpoint.
0x803D0014	The connection with the remote endpoint was terminated.
0x803D0015	The HTTP proxy server could not process the request.
0x803D0016	Access was denied by the HTTP proxy server.
0x803D0017	The requested feature is not available on this platform.
0x803D0018	The HTTP proxy server requires HTTP authentication scheme 'basic'.
0x803D0019	The HTTP proxy server requires HTTP authentication scheme 'digest'.
0x803D001A	The HTTP proxy server requires HTTP authentication scheme 'NTLM'.
0x803D001B	The HTTP proxy server requires HTTP authentication scheme 'negotiate'.
0x803D001C	The remote endpoint requires HTTP authentication scheme 'basic'.
0x803D001D	The remote endpoint requires HTTP authentication scheme 'digest'.
0x803D001E	The remote endpoint requires HTTP authentication scheme 'NTLM'.
0x803D001F	The remote endpoint requires HTTP authentication scheme 'negotiate'.
0x803D0020	The endpoint address URL is invalid.
0x803D0021	Unrecognized error occurred in the Windows Web Services framework.
0x803D0022	A security token was rejected by the server because it has expired.
0x803D0023	A security operation failed in the Windows Web Services framework.
0x803E0100	The notification channel has already been closed.
0x803E0101	The notification channel request did not complete successfully.
0x803E0102	The application identifier provided is invalid.
0x803E0103	A notification channel request for the provided application identifier is in progress.
0x803E0104	The channel identifier is already tied to another application endpoint.
0x803E0105	The notification platform is unavailable.
0x803E0106	The notification has already been posted.
0x803E0107	The notification has already been hidden.
0x803E0108	The notification cannot be hidden until it has been shown.
0x803E0109	Cloud notifications have been turned off.
0x803E0110	The application does not have the cloud notification capability.
0x803E0111	Settings prevent the notification from being delivered.
0x803E0112	Application capabilities prevent the notification from being delivered.
0x803E0113	The application does not have the internet access capability.
0x803E0114	Settings prevent the notification type from being delivered.
0x803E0115	The size of the notification content is too large.
0x803E0116	The size of the notification tag is too large.
0x803E0117	The notification platform doesn't have appropriate privilege on resources.
0x803E0118	The notification platform found application is already registered.
0x803E0119	The application background task does not have the push notification capability.
0x803E011A	The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service.
0x803E011B	The notification platform is unable to connect to the cloud notification service.
0x803E011C	The notification platform is unable to initialize a callback for lock screen updates.
0x803E0120	The size of the developer id for scheduled notification is too large.
0x803E012A	The notification tag is not alphanumeric.
0x803E012B	The notification platform has received invalid HTTP status code other than 2xx for polling.
0x803E0200	The notification platform has run out of presentation layer sessions.
0x803E0201	The notification platform rejects image download request due to system in power save mode.
0x803E0202	The notification platform doesn't have the requested image in its cache.
0x803E0203	The notification platform cannot complete all of requested image.
0x803E0204	A cloud image downloaded from the notification platform is invalid.
0x803E0205	Notification Id provided as filter is matched with what the notification platform maintains.
0x803E0206	Notification callback interface is already registered.
0x803E0207	Toast Notification was dropped without being displayed to the user.
0x803E0208	The notification platform does not have the proper privileges to complete the request.
0x803E0209	The size of the notification group is too large.
0x803E020A	The notification group is not alphanumeric.
0x803E020B	Cloud notifications have been disabled for the application due to a policy setting.
0x80400000	Input data cannot be processed in the non-chronological order.
0x80400001	Requested operation cannot be performed inside the callback or event handler.
0x80400002	Input cannot be processed because there is ongoing interaction with another pointer type.
0x80400003	One or more fields in the input packet are invalid.
0x80400004	Packets in the frame are inconsistent. Either pointer ids are not unique or there is a discrepancy in timestamps, frame ids, pointer types or source devices.
0x80400005	The history of frames is inconsistent. Pointer ids, types, source devices don't match, or frame ids are not unique, or timestamps are out of order.
0x80400006	Failed to retrieve information about the input device.
0x80400007	Coordinate system transformation failed to transform the data.
0x80400008	The property is not supported or not reported correctly by the input device.
0x80410000	The QUIC connection handshake failed.
0x80410001	The QUIC connection failed to negotiate a compatible protocol version.
0x80548201	Context is not activated.
0x80548202	Bad SIM is inserted.
0x80548203	Requested data class is not available.
0x80548204	Access point name (APN) or Access string is incorrect.
0x80548205	Max activated contexts have reached.
0x80548206	Device is in packet detach state.
0x80548207	Provider is not visible.
0x80548208	Radio is powered off.
0x80548209	MBN subscription is not activated.
0x8054820A	SIM is not inserted.
0x8054820B	Voice call in progress.
0x8054820C	Visible provider cache is invalid.
0x8054820D	Device is not registered.
0x8054820E	Providers not found.
0x8054820F	Pin is not supported.
0x80548210	Pin is required.
0x80548211	PIN is disabled.
0x80548212	Generic Failure.
0x80548218	Profile is invalid.
0x80548219	Default profile exist.
0x80548220	SMS encoding is not supported.
0x80548221	SMS filter is not supported.
0x80548222	Invalid SMS memory index is used.
0x80548223	SMS language is not supported.
0x80548224	SMS memory failure occurred.
0x80548225	SMS network timeout happened.
0x80548226	Unknown SMSC address is used.
0x80548227	SMS format is not supported.
0x80548228	SMS operation is not allowed.
0x80548229	Device SMS memory is full.
0x80550001	Windows cannot evaluate this EAS policy since this is not managed by the operating system.
0x80550002	The system can be made compliant to this EAS policy if certain actions are performed by the user.
0x80550003	The EAS policy being evaluated cannot be enforced by the system.
0x80550004	EAS password policies for the user cannot be evaluated as the user has a blank password.
0x80550005	EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system.
0x80550006	The user is not allowed to change her password.
0x80550007	EAS password policies cannot be evaluated as one or more admins have blank passwords.
0x80550008	One or more admins are not allowed to change their password.
0x80550009	There are other standard users present who are not allowed to change their password.
0x8055000A	The EAS password policy cannot be enforced by the connected account provider of at least one administrator.
0x8055000B	There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance.
0x8055000C	The EAS password policy cannot be enforced by the connected account provider of the current user.
0x8055000D	The connected account password of the current user needs to be changed for EAS password policy compliance.
0x80630001	The IPv6 protocol is not installed.
0x80630002	The component has not been initialized.
0x80630003	The required service cannot be started.
0x80630004	The P2P protocol is not licensed to run on this OS.
0x80630010	The graph handle is invalid.
0x80630011	The graph database name has changed.
0x80630012	A graph with the same ID already exists.
0x80630013	The graph is not ready.
0x80630014	The graph is shutting down.
0x80630015	The graph is still in use.
0x80630016	The graph database is corrupt.
0x80630017	Too many attributes have been used.
0x80630103	The connection can not be found.
0x80630106	The peer attempted to connect to itself.
0x80630107	The peer is already listening for connections.
0x80630108	The node was not found.
0x80630109	The Connection attempt failed.
0x8063010A	The peer connection could not be authenticated.
0x8063010B	The connection was refused.
0x80630201	The peer name classifier is too long.
0x80630202	The maximum number of identities have been created.
0x80630203	Unable to access a key.
0x80630204	The group already exists.
0x80630301	The requested record could not be found.
0x80630302	Access to the database was denied.
0x80630303	The Database could not be initialized.
0x80630304	The record is too big.
0x80630305	The database already exists.
0x80630306	The database could not be found.
0x80630401	The identity could not be found.
0x80630501	The event handle could not be found.
0x80630601	Invalid search.
0x80630602	The search attributes are invalid.
0x80630701	The invitation is not trusted.
0x80630703	The certchain is too long.
0x80630705	The time period is invalid.
0x80630706	A circular cert chain was detected.
0x80630801	The certstore is corrupted.
0x80631001	The specified PNRP cloud does not exist.
0x80631005	The cloud name is ambiguous.
0x80632010	The record is invalid.
0x80632020	Not authorized.
0x80632021	The password does not meet policy requirements.
0x80632030	The record validation has been deferred.
0x80632040	The group properties are invalid.
0x80632050	The peername is invalid.
0x80632060	The classifier is invalid.
0x80632070	The friendly name is invalid.
0x80632071	Invalid role property.
0x80632072	Invalid classifier property.
0x80632080	Invalid record expiration.
0x80632081	Invalid credential info.
0x80632082	Invalid credential.
0x80632083	Invalid record size.
0x80632090	Unsupported version.
0x80632091	The group is not ready.
0x80632092	The group is still in use.
0x80632093	The group is invalid.
0x80632094	No members were found.
0x80632095	There are no member connections.
0x80632096	Unable to listen.
0x806320A0	The identity does not exist.
0x806320A1	The service is not available.
0x80634001	The peername could not be converted to a DNS pnrp name.
0x80634002	Invalid peer host name.
0x80634003	No more data could be found.
0x80634005	The existing peer name is already registered.
0x80636001	THe contact could not be found.
0x80637000	The app invite request was cancelled by the user.
0x80637001	No response of the invite was received.
0x80637003	User is not signed into serverless presence.
0x80637004	The user declined the privacy policy prompt.
0x80637005	A timeout occurred.
0x80637007	The address is invalid.
0x80637008	A required firewall exception is disabled.
0x80637009	The service is blocked by a firewall policy.
0x8063700A	Firewall exceptions are disabled.
0x8063700B	The user declined to enable the firewall exceptions.
0x80650001	The attribute handle given was not valid on this server.
0x80650002	The attribute cannot be read.
0x80650003	The attribute cannot be written.
0x80650004	The attribute PDU was invalid.
0x80650005	The attribute requires authentication before it can be read or written.
0x80650006	Attribute server does not support the request received from the client.
0x80650007	Offset specified was past the end of the attribute.
0x80650008	The attribute requires authorization before it can be read or written.
0x80650009	Too many prepare writes have been queued.
0x8065000A	No attribute found within the given attribute handle range.
0x8065000B	The attribute cannot be read or written using the Read Blob Request.
0x8065000C	The Encryption Key Size used for encrypting this link is insufficient.
0x8065000D	The attribute value length is invalid for the operation.
0x8065000E	The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested.
0x8065000F	The attribute requires encryption before it can be read or written.
0x80650010	The attribute type is not a supported grouping attribute as defined by a higher layer specification.
0x80650011	Insufficient Resources to complete the request.
0x80651000	An error that lies in the reserved range has been received.
0x80660001	PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode.
0x80660002	HD Audio widget encountered an unexpected empty connection list.
0x80660003	HD Audio widget does not support the connection list parameter.
0x80660004	No HD Audio subdevices were successfully created.
0x80660005	An unexpected NULL pointer was encountered in a linked list.
0x80670001	Optimistic locking failure. Data cannot be updated if it has changed since it was read.
0x80670002	A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits.
0x80670003	The StateRepository configuration is not valid.
0x80670004	The StateRepository schema version is not known.
0x80670005	A StateRepository dictionary is not valid.
0x80670006	The request failed because the StateRepository is actively blocking requests.
0x80670007	The database file is locked. The request will be retried.
0x80670008	The database file is locked because another process is busy recovering the database. The request will be retried.
0x80670009	A table in the database is locked. The request will be retried.
0x8067000A	The shared cache for the database is locked by another connection. The request will be retried.
0x8067000B	A transaction is required to perform the request operation.
0x8067000C	The database file is locked. The request has exceeded the allowed threshold.
0x8067000D	The database file is locked because another process is busy recovering the database. The request has exceeded the allowed threshold.
0x8067000E	A table in the database is locked. The request has exceeded the allowed threshold.
0x8067000F	The shared cache for the database is locked by another connection. The request has exceeded the allowed threshold.
0x80670010	The StateRepository service Stop event is in progress.
0x80670011	Nested transactions are not supported.
0x80670012	The StateRepository cache is not valid.
0x80820001	The bootfile is too small to support persistent snapshots.
0x80820002	Activation of persistent snapshots on this volume took longer than was allowed.
0x80830001	The specified volume does not support storage tiers.
0x80830002	The Storage Tiers Management service detected that the specified volume is in the process of being dismounted.
0x80830003	The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid.
0x80830004	The file identifier specified is not valid on the volume.
0x80830005	Storage tier operations must be called on the clustering node that owns the metadata volume.
0x80830006	The Storage Tiers Management service is already optimizing the storage tiers on the specified volume.
0x80830007	The requested object type cannot be assigned to a storage tier.
0x80830008	The requested file is not pinned to a tier.
0x80830009	The volume is not a tiered volume.
0x8083000A	The requested attribute is not present on the specified file or directory.
0x80860001	Authentication target is invalid or not configured correctly.
0x80860002	Your application cannot get the Online Id properties due to the Terms of Use accepted by the user.
0x80860003	The application requesting authentication tokens is either disabled or incorrectly configured.
0x80860004	Online Id password must be updated before signin.
0x80860005	Online Id account properties must be updated before signin.
0x80860006	To help protect your Online Id account you must signin again.
0x80860007	Online Id account was locked because there have been too many attempts to sign in.
0x80860008	Online Id account requires parental consent before proceeding.
0x80860009	Online Id signin name is not yet verified. Email verification is required before signin.
0x8086000A	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	We detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account.
0x8086000C	User interaction is required for authentication.
0x8086000D	User has reached the maximum device associations per user limit.
0x8086000E	Cannot sign out from the application since the user account is connected.
0x8086000F	User authentication is required for this operation.
0x80860010	We want to make sure this is you. User interaction is required for authentication.
0x80B00001	Could not create new process from ARM architecture device.
0x80B00002	Could not attach to the application process from ARM architecture device.
0x80B00003	Could not connect to dbgsrv server from ARM architecture device.
0x80B00004	Could not start dbgsrv server from ARM architecture device.
0x80E70001	The specified fault domain type or combination of minimum / maximum fault domain type is not valid.
0x80E70002	A Storage Spaces internal error occurred.
0x80E70003	The specified resiliency type is not valid.
0x80E70004	The physical disk's sector size is not supported by the storage pool.
0x80E70006	The requested redundancy is outside of the supported range of values.
0x80E70007	The number of data copies requested is outside of the supported range of values.
0x80E70008	The value for ParityLayout is outside of the supported range of values.
0x80E70009	The value for interleave length is outside of the supported range of values or is not a power of 2.
0x80E7000A	The number of columns specified is outside of the supported range of values.
0x80E7000B	There were not enough physical disks to complete the requested operation.
0x80E7000C	Extended error information is available.
0x80E7000D	The specified provisioning type is not valid.
0x80E7000E	The allocation size is outside of the supported range of values.
0x80E7000F	Enclosure awareness is not supported for this virtual disk.
0x80E70010	The write cache size is outside of the supported range of values.
0x80E70011	The value for number of groups is outside of the supported range of values.
0x80E70012	The OperationalState of the physical disk is invalid for this operation.
0x80E70013	The specified log entry is not complete.
0x80E70014	The specified log entry is not valid.
0x83750001	Unsupported format.
0x83750002	Invalid XML.
0x83750003	Missing required element.
0x83750004	Missing required attribute.
0x83750005	Unexpected content.
0x83750006	Resource too large.
0x83750007	Invalid JSON string.
0x83750008	Invalid JSON number.
0x83750009	JSON value not found.
0x83760001	Invalid operation performed by the protocol.
0x83760002	Invalid data format for the specific protocol operation.
0x83760003	Protocol extensions are not supported.
0x83760004	Subprotocol is not supported.
0x83760005	Incorrect protocol version.
0x87AF0001	SQL error or missing database
0x87AF0002	Internal logic error in SQLite
0x87AF0003	Access permission denied
0x87AF0004	Callback routine requested an abort
0x87AF0005	The database file is locked
0x87AF0006	A table in the database is locked
0x87AF0007	A malloc() failed
0x87AF0008	Attempt to write a readonly database
0x87AF0009	Operation terminated by sqlite3_interrupt()
0x87AF000A	Some kind of disk I/O error occurred
0x87AF000B	The database disk image is malformed
0x87AF000C	Unknown opcode in sqlite3_file_control()
0x87AF000D	Insertion failed because database is full
0x87AF000E	Unable to open the database file
0x87AF000F	Database lock protocol error
0x87AF0010	Database is empty
0x87AF0011	The database schema changed
0x87AF0012	String or BLOB exceeds size limit
0x87AF0013	Abort due to constraint violation
0x87AF0014	Data type mismatch
0x87AF0015	Library used incorrectly
0x87AF0016	Uses OS features not supported on host
0x87AF0017	Authorization denied
0x87AF0018	Auxiliary database format error
0x87AF0019	2nd parameter to sqlite3_bind out of range
0x87AF001A	File opened that is not a database file
0x87AF001B	Notifications from sqlite3_log()
0x87AF001C	Warnings from sqlite3_log()
0x87AF0064	sqlite3_step() has another row ready
0x87AF0065	sqlite3_step() has finished executing
0x87AF0105	SQLITE_BUSY_RECOVERY
0x87AF0106	SQLITE_LOCKED_SHAREDCACHE
0x87AF0108	SQLITE_READONLY_RECOVERY
0x87AF010A	SQLITE_IOERR_READ
0x87AF010B	SQLITE_CORRUPT_VTAB
0x87AF010E	SQLITE_CANTOPEN_NOTEMPDIR
0x87AF0113	SQLITE_CONSTRAINT_CHECK
0x87AF011B	SQLITE_NOTICE_RECOVER_WAL
0x87AF011C	SQLITE_WARNING_AUTOINDEX
0x87AF0204	SQLITE_ABORT_ROLLBACK
0x87AF0205	SQLITE_BUSY_SNAPSHOT
0x87AF0208	SQLITE_READONLY_CANTLOCK
0x87AF020A	SQLITE_IOERR_SHORT_READ
0x87AF020E	SQLITE_CANTOPEN_ISDIR
0x87AF0213	SQLITE_CONSTRAINT_COMMITHOOK
0x87AF021B	SQLITE_NOTICE_RECOVER_ROLLBACK
0x87AF0308	SQLITE_READONLY_ROLLBACK
0x87AF030A	SQLITE_IOERR_WRITE
0x87AF030E	SQLITE_CANTOPEN_FULLPATH
0x87AF0313	SQLITE_CONSTRAINT_FOREIGNKEY
0x87AF0408	SQLITE_READONLY_DBMOVED
0x87AF040A	SQLITE_IOERR_FSYNC
0x87AF040E	SQLITE_CANTOPEN_CONVPATH
0x87AF0413	SQLITE_CONSTRAINT_FUNCTION
0x87AF050A	SQLITE_IOERR_DIR_FSYNC
0x87AF0513	SQLITE_CONSTRAINT_NOTNULL
0x87AF060A	SQLITE_IOERR_TRUNCATE
0x87AF0613	SQLITE_CONSTRAINT_PRIMARYKEY
0x87AF070A	SQLITE_IOERR_FSTAT
0x87AF0713	SQLITE_CONSTRAINT_TRIGGER
0x87AF080A	SQLITE_IOERR_UNLOCK
0x87AF0813	SQLITE_CONSTRAINT_UNIQUE
0x87AF090A	SQLITE_IOERR_RDLOCK
0x87AF0913	SQLITE_CONSTRAINT_VTAB
0x87AF0A0A	SQLITE_IOERR_DELETE
0x87AF0A13	SQLITE_CONSTRAINT_ROWID
0x87AF0B0A	SQLITE_IOERR_BLOCKED
0x87AF0C0A	SQLITE_IOERR_NOMEM
0x87AF0D0A	SQLITE_IOERR_ACCESS
0x87AF0E0A	SQLITE_IOERR_CHECKRESERVEDLOCK
0x87AF0F0A	SQLITE_IOERR_LOCK
0x87AF100A	SQLITE_IOERR_CLOSE
0x87AF110A	SQLITE_IOERR_DIR_CLOSE
0x87AF120A	SQLITE_IOERR_SHMOPEN
0x87AF130A	SQLITE_IOERR_SHMSIZE
0x87AF140A	SQLITE_IOERR_SHMLOCK
0x87AF150A	SQLITE_IOERR_SHMMAP
0x87AF160A	SQLITE_IOERR_SEEK
0x87AF170A	SQLITE_IOERR_DELETE_NOENT
0x87AF180A	SQLITE_IOERR_MMAP
0x87AF190A	SQLITE_IOERR_GETTEMPPATH
0x87AF1A02	SQLITE_IOERR_VNODE
0x87AF1A03	SQLITE_IOERR_AUTH
0x87AF1A0A	SQLITE_IOERR_CONVPATH
0x87C51001	Toggle (alternative) trace started
0x87C51002	Cannot pre-empt running trace: The current trace has a higher priority
0x87C51003	The always-on-trace is not running
0x87C51004	RunScriptAction contains an invalid script type
0x87C51005	Requested scenario definition cannot be found
0x87C51006	Requested trace profile cannot be found
0x87C51007	Trigger forwarder is already enabled
0x87C51008	Trigger forwarder is already disabled
0x87C51009	Cannot parse EventLog XML: The entry is malformed
0x87C5100A	node contains a schemaversion which is not compatible with this client
0x87C5100B	RunScriptAction was forced to terminate a script
0x87C5100C	ToggleTraceWithCustomFilterAction contains an invalid custom filter
0x87C5100D	The trace is not running
0x87C5100E	A scenario failed to escalate: This scenario has escalated too recently
0x87C5100F	A scenario failed to escalate: This scenario is already running an escalation
0x87C51010	Cannot start tracing: PerfTrack component is already tracing
0x87C51011	A scenario failed to escalate: This scenario has reached max escalations for this escalation type
0x87C51012	Cannot update forwarder: The forwarder passed to the function is of a different type
0x87C51013	RunScriptAction failed intentionally to force this escalation to terminate
0x87C51014	Failed to initialize SQM logger
0x87C51015	Failed to initialize WER logger: This system does not support WER for UTC
0x87C51016	The TraceManager has attempted to take a tracing action without initializing tracers
0x87C51017	WinRT initialization failed
0x87C51018	node contains a schemaversion that is not compatible with this client
0x87C51019	Scenario contains an invalid filter that can never be satisfied
0x87C5101A	RunExeWithArgsAction was forced to terminate a running executable
0x87C5101B	Escalation for scenario failed due to insufficient permissions
0x87C5101C	Setup for scenario failed due to insufficient permissions
0x87C5101D	A process launched by UTC failed with a non-zero exit code.
0x87C5101E	A RunExeWithArgs action contains an unauthorized command line.
0x87C5101F	UTC cannot load Scenario Editor XML. Convert the scenario file to a DiagTrack XML using the editor.
0x87C51020	Escalation for scenario has timed out
0x87C51021	Setup for scenario has timed out
0x87C51022	The given trigger does not match the expected trigger type
0x87C51023	Requested trigger cannot be found
0x87C51024	SIF is not supported on the machine
0x87C51025	The delay action was terminated
0x87C51026	The device ticket was not obtained
0x87C51027	The trace profile needs more memory than is available for tracing
0x87C51028	The API was not completed successfully so the result is unavailable
0x87C51029	The requested API encountered a timeout in the API manager
0x87C5102A	The synchronous API encountered a wait failure
0x87C5102B	The UTC API is busy with another request
0x87C5102C	The running trace profile does not have a sufficient runtime to fulfill the escalation request
0x87C5102D	The trace profile could not be started because it requires exclusivity and another higher priority trace is already running
0x87C5102E	The file path is not approved for the GetFile escalation action
0x87C5102F	The escalation working directory for the requested escalation could not be created because it already exists
0x87C51030	Time triggers cannot be used on a transition originating from the "_start" state
0x87C51031	Time triggers can only be attached to a single transition
0x87C51032	Time trigger duration must fall within an inclusive range of one second and 15 minutes
0x87C51033	Only one Time Trigger is allowed per state
0x87C51034	A RunExeWithArgs action contains a binary which is not present on the targeted device.
0x87C51036	UTC failed to identify the container id to use for a scenario escalation action.
0x87C51037	Failed to resolve session ID during API invocation.
0x87C51038	UTC has throttled the event for firing too often.
0x87C51039	The script is not approved to run as part of DiagTrack scenario.
0x87C5103A	The script referenced in DiagTrack scenario is not present on the system.
0x87C5103B	A trigger in this scenario is throttled, blocking the scenario from being loaded.
0x87C5103C	The requested UTC API call is not supported on this device.
0x87C5103D	The file path is not approved for collection on external rings for the GetFile escalation action.
0x87C5103E	Querying a scenario definition exceeded the specified maximum timeout.
0x87C5103F	Certification revocation checking has been enabled, but the revocation check failed to verify whether a certificate has been revoked. The server used to check for revocation might be unreachable.
0x87C51040	Failed to start NDISCAP service for network packet capture trace.
0x87C51041	UTC can perform no more than one KernelDump action on a device every 24 hours.
0x87C51042	The event contained an aggregation or differential privacy structure, but did not specify MICROSOFT_EVENTTAG_AGGREGATE.
0x87C51043	The event contained an invalid aggregation or differential privacy structure.
0x87C51044	The action cannot be completed in the specified destination.
0x87C51045	Filter command is missing a required attribute.
0x87C51046	Filter command contains an unsupported type.
0x87C51047	Filter variable does not exist at point of evaluation.
0x87C51048	Filter command is not allowed in the current context.
0x87C51049	Requested filter version is incompatible with available version.
0x87C51050	Filter does not support this function.
0x87C51051	Filter function does not accept the provided parameter types and/or count.
0x87C51052	Filter command does not exist or is incorrectly formatted.
0x87C51053	Filter types can not be compared to each other.
0x87C51054	TTTracer executable returned a code other than ERROR_SUCCESS.
0x87C51055	The total size of the compressed escalation data payload exceeded the allowable limit.
0x87C51056	Escalation data was not completely transferred from agent to host.
0x87C51057	An escalation was requested for a scenario which has no actions for the passed type.
0x87C51058	UTC allocated space for TTTracer escalations is full.
0x87C51059	Disk needs minimum of 15GB to start TTD recording session.
0x87C5105A	Escalation was cancelled due to component shutdown.
0x87C5105B	The file for the GetFileInfo action must be under the \Windows, \Program Files, or \Program Files (x86) directories.
0x87C5105C	The registry value type for SetRegKey action must be REG_SZ, REG_MULTI_SZ, REG_EXPAND_SZ, REG_BINARY, REG_DWORD, or REG_QWORD.
0x88010001	One or more fixed volumes are not provisioned with the 3rd party encryption providers to support device encryption. Enable encryption with the 3rd party provider to comply with policy.
0x88010002	This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption.
0x88010003	This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider.
0x88010004	This computer cannot support device encryption because the requisites for the device lock feature are not configured.
0x88010005	Protection is enabled on this volume but is not in the active state.
0x88010006	The 3rd party provider has been installed, but cannot activate encryption because a license has not been activated.
0x88010007	The operating system drive is not protected by 3rd party drive encryption.
0x88010008	Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin.
0x88010009	The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large.
0x8802B001	The file size is larger than supported by the sync engine.
0x8802B002	The file cannot be uploaded because it doesn't fit in the user's available service provided storage space.
0x8802B003	The file name contains invalid characters.
0x8802B004	The maximum file count has been reached for this folder in the sync engine.
0x8802B005	The file sync has been delegated to another program and has run into an issue.
0x8802B006	Sync has been delayed due to a throttling request from the service.
0x8802C002	We can't seem to find that file. Please try again later.
0x8802C003	The account you're signed in with doesn't have permission to open this file.
0x8802C004	There was a problem connecting to the service. Please try again later.
0x8802C005	Sorry, there was a problem downloading the file.
0x8802C006	We're having trouble downloading the file right now. Please try again later.
0x8802C007	We're having trouble downloading the file right now. Please try again later.
0x8802D001	The sync engine does not have permissions to access a local folder under the sync root.
0x8802D002	The folder name contains invalid characters.
0x8802D003	The sync engine is not allowed to run in your current market.
0x8802D004	All files and folders can't be uploaded because a path of a file or folder is too long.
0x8802D005	All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit.
0x8802D006	Updates are needed in order to use the sync engine.
0x8802D007	The sync engine needs to authenticate with a proxy server.
0x8802D008	There was a problem setting up the storage services for the account.
0x8802D009	Files can't be uploaded because there's an unsupported reparse point.
0x8802D00A	The service has blocked your account from accessing the storage service.
0x8802D00B	The action can't be performed right now because this folder is being moved. Please try again later.
0x88790001	The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1.
0x88790002	The specified file was not found.
0x887A0001	The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect. Enable the D3D debug layer in order to see details via debug messages.
0x887A0002	The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal.
0x887A0003	The caller did not supply a sufficiently large buffer.
0x887A0004	The specified device interface or feature level is not supported on this system.
0x887A0005	The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.
0x887A0006	The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application.
0x887A0007	The GPU will not respond to more commands, most likely because some other application submitted invalid commands. The calling application should re-create the device and continue.
0x887A000A	The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled.
0x887A000B	An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should be considered invalid.
0x887A000C	Fullscreen mode could not be achieved because the specified output was already in use.
0x887A0020	An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect, and the application should not continue.
0x887A0021	A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time.
0x887A0022	A resource is not available at the time of the call, but may become available later.
0x887A0023	The application's remote device has been removed due to session disconnect or network disconnect. The application should call IDXGIFactory1::IsCurrent to find out when the remote device becomes available again.
0x887A0024	The device has been removed during a remote session because the remote computer ran out of memory.
0x887A0025	An on-going mode change prevented completion of the call. The call may succeed if attempted later.
0x887A0026	The keyed mutex was abandoned.
0x887A0027	The timeout value has elapsed and the resource is not yet available.
0x887A0028	The output duplication has been turned off because the Windows session ended or was disconnected. This happens when a remote user disconnects, or when "switch user" is used locally.
0x887A0029	The DXGI output (monitor) to which the swapchain content was restricted, has been disconnected or changed.
0x887A002A	DXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver, or by the application using a swapchain that is incompatible with content protection.
0x887A002B	The application is trying to use a resource to which it does not have the required access privileges. This is most commonly caused by writing to a shared resource with read-only access.
0x887A002C	The application is trying to create a shared handle using a name that is already associated with some other resource.
0x887A002D	The application requested an operation that depends on an SDK component that is missing or mismatched.
0x887A002E	The DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed.
0x887A0030	Insufficient HW protected memory exits for proper function.
0x887A0031	Creating this device would violate the process's dynamic code policy.
0x887A0032	The operation failed because the compositor is not in control of the output.
0x887A0033	The cache is corrupt and either could not be opened or could not be reset.
0x887A0034	This entry would cause the cache to exceed its quota. On a load operation, this may indicate exceeding the maximum in-memory size.
0x887A0035	A cache entry was found, but the key provided does not match the key stored in the entry.
0x887A0036	The desired element already exists.
0x887B0001	The GPU was busy when the operation was requested.
0x887B0002	The driver has rejected the creation of this resource.
0x887B0003	The GPU counter was in use by another process or d3d device when application requested access to it.
0x887C0001	The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1.
0x887C0002	The specified file was not found.
0x887C0003	The application has exceeded the maximum number of unique view objects per Direct3D device. The limit is 2^20 for feature levels up to 11.1.
0x887C0004	The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD.
0x887E0001	The blob provided does not match the adapter that the device was created on.
0x887E0002	The blob provided was created for a different version of the driver, and must be re-created.
0x887E0003	The D3D12 SDK version configuration of the host exe is invalid.
0x88800001	The application failed to unregister from an event it registered for.
0x88900001	The device is invalid or does not support machine learning.
0x88900002	The binding is incomplete or does not match the input/output description.
0x88900003	An attempt was made to bind an unknown input or output.
0x88900004	The size of the buffer provided for a bound variable is invalid.
0x88980001	MILERR_OBJECTBUSY
0x88980002	MILERR_INSUFFICIENTBUFFER
0x88980003	MILERR_WIN32ERROR
0x88980004	MILERR_SCANNER_FAILED
0x88980005	MILERR_SCREENACCESSDENIED
0x88980006	MILERR_DISPLAYSTATEINVALID
0x88980007	MILERR_NONINVERTIBLEMATRIX
0x88980008	MILERR_ZEROVECTOR
0x88980009	MILERR_TERMINATED
0x8898000A	MILERR_BADNUMBER
0x88980080	An internal error (MIL bug) occurred. On checked builds, an assert would be raised.
0x88980084	The display format we need to render is not supported by the hardware device.
0x88980085	A call to this method is invalid.
0x88980086	Lock attempted on an already locked object.
0x88980087	Unlock attempted on an unlocked object.
0x88980088	No algorithm available to render text with this device
0x88980089	Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache.
0x8898008A	Some glyph bitmaps in glyph cache are unexpectedly big.
0x8898008B	Marker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred, but still unwind the stack in the correct location.
0x8898008C	Guideline coordinates are not sorted properly or contain NaNs.
0x8898008D	No HW rendering device is available for this operation.
0x8898008E	There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. There are two known case for this: 1) D3D Driver Internal error 2) D3D E_FAIL 2a) Unknown root cause b) When resizing too quickly for DWM and D3D stay in sync
0x8898008F	The object has already been initialized.
0x88980090	The size of the object does not match the expected size.
0x88980091	No Redirection surface available.
0x88980092	Remoting of this content is not supported.
0x88980093	Queued Presents are not supported.
0x88980094	Queued Presents are not being used.
0x88980095	No redirection surface was available. Caller should retry the call.
0x88980096	Shader construction failed because it was too complex.
0x88980097	MROW attempt to get a read lock failed.
0x88980098	MROW attempt to update the data failed because another update was outstanding.
0x88980099	Shader compilation failed.
0x8898009A	Requested DX redirection surface size exceeded maximum texture size.
0x8898009B	QueryPerformanceCounter returned a time in the past.
0x8898009D	Primary Display device returned an invalid refresh rate.
0x8898009E	DWM can not find the adapter specified by the LUID.
0x8898009F	The requested bitmap color space is not supported.
0x889800A0	The requested bitmap pre-filtering state is not supported.
0x889800A1	Access is denied to the requested bitmap for the specified display id.
0x88980400	UCEERR_INVALIDPACKETHEADER
0x88980401	UCEERR_UNKNOWNPACKET
0x88980402	UCEERR_ILLEGALPACKET
0x88980403	UCEERR_MALFORMEDPACKET
0x88980404	UCEERR_ILLEGALHANDLE
0x88980405	UCEERR_HANDLELOOKUPFAILED
0x88980406	UCEERR_RENDERTHREADFAILURE
0x88980407	UCEERR_CTXSTACKFRSTTARGETNULL
0x88980408	UCEERR_CONNECTIONIDLOOKUPFAILED
0x88980409	UCEERR_BLOCKSFULL
0x8898040A	UCEERR_MEMORYFAILURE
0x8898040B	UCEERR_PACKETRECORDOUTOFRANGE
0x8898040C	UCEERR_ILLEGALRECORDTYPE
0x8898040D	UCEERR_OUTOFHANDLES
0x8898040E	UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED
0x8898040F	UCEERR_NO_MULTIPLE_WORKER_THREADS
0x88980410	UCEERR_REMOTINGNOTSUPPORTED
0x88980411	UCEERR_MISSINGENDCOMMAND
0x88980412	UCEERR_MISSINGBEGINCOMMAND
0x88980413	UCEERR_CHANNELSYNCTIMEDOUT
0x88980414	UCEERR_CHANNELSYNCABANDONED
0x88980415	UCEERR_UNSUPPORTEDTRANSPORTVERSION
0x88980416	UCEERR_TRANSPORTUNAVAILABLE
0x88980417	UCEERR_FEEDBACK_UNSUPPORTED
0x88980418	UCEERR_COMMANDTRANSPORTDENIED
0x88980419	UCEERR_GRAPHICSSTREAMUNAVAILABLE
0x88980420	UCEERR_GRAPHICSSTREAMALREADYOPEN
0x88980421	UCEERR_TRANSPORTDISCONNECTED
0x88980422	UCEERR_TRANSPORTOVERLOADED
0x88980423	UCEERR_PARTITION_ZOMBIED
0x88980500	MILAVERR_NOCLOCK
0x88980501	MILAVERR_NOMEDIATYPE
0x88980502	MILAVERR_NOVIDEOMIXER
0x88980503	MILAVERR_NOVIDEOPRESENTER
0x88980504	MILAVERR_NOREADYFRAMES
0x88980505	MILAVERR_MODULENOTLOADED
0x88980506	MILAVERR_WMPFACTORYNOTREGISTERED
0x88980507	MILAVERR_INVALIDWMPVERSION
0x88980508	MILAVERR_INSUFFICIENTVIDEORESOURCES
0x88980509	MILAVERR_VIDEOACCELERATIONNOTAVAILABLE
0x8898050A	MILAVERR_REQUESTEDTEXTURETOOBIG
0x8898050B	MILAVERR_SEEKFAILED
0x8898050C	MILAVERR_UNEXPECTEDWMPFAILURE
0x8898050D	MILAVERR_MEDIAPLAYERCLOSED
0x8898050E	MILAVERR_UNKNOWNHARDWAREERROR
0x8898060E	MILEFFECTSERR_UNKNOWNPROPERTY
0x8898060F	MILEFFECTSERR_EFFECTNOTPARTOFGROUP
0x88980610	MILEFFECTSERR_NOINPUTSOURCEATTACHED
0x88980611	MILEFFECTSERR_CONNECTORNOTCONNECTED
0x88980612	MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT
0x88980613	MILEFFECTSERR_RESERVED
0x88980614	MILEFFECTSERR_CYCLEDETECTED
0x88980615	MILEFFECTSERR_EFFECTINMORETHANONEGRAPH
0x88980616	MILEFFECTSERR_EFFECTALREADYINAGRAPH
0x88980617	MILEFFECTSERR_EFFECTHASNOCHILDREN
0x88980618	MILEFFECTSERR_ALREADYATTACHEDTOLISTENER
0x88980619	MILEFFECTSERR_NOTAFFINETRANSFORM
0x8898061A	MILEFFECTSERR_EMPTYBOUNDS
0x8898061B	MILEFFECTSERR_OUTPUTSIZETOOLARGE
0x88980700	DWMERR_STATE_TRANSITION_FAILED
0x88980701	DWMERR_THEME_FAILED
0x88980702	DWMERR_CATASTROPHIC_FAILURE
0x88980800	DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED
0x88980801	DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED
0x88980802	DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED
0x88982F04	The codec is in the wrong state.
0x88982F05	The value is out of range.
0x88982F07	The image format is unknown.
0x88982F0B	The SDK version is unsupported.
0x88982F0C	The component is not initialized.
0x88982F0D	There is already an outstanding read or write lock.
0x88982F40	The specified bitmap property cannot be found.
0x88982F41	The bitmap codec does not support the bitmap property.
0x88982F42	The bitmap property size is invalid.
0x88982F43	An unknown error has occurred.
0x88982F44	The bitmap codec does not support a thumbnail.
0x88982F45	The bitmap palette is unavailable.
0x88982F46	Too many scanlines were requested.
0x88982F48	An internal error occurred.
0x88982F49	The bitmap bounds do not match the bitmap dimensions.
0x88982F50	The component cannot be found.
0x88982F51	The bitmap size is outside the valid range.
0x88982F52	There is too much metadata to be written to the bitmap.
0x88982F60	The image is unrecognized.
0x88982F61	The image header is unrecognized.
0x88982F62	The bitmap frame is missing.
0x88982F63	The image metadata header is unrecognized.
0x88982F70	The stream data is unrecognized.
0x88982F71	Failed to write to the stream.
0x88982F72	Failed to read from the stream.
0x88982F73	The stream is not available.
0x88982F80	The bitmap pixel format is unsupported.
0x88982F81	The operation is unsupported.
0x88982F8A	The component registration is invalid.
0x88982F8B	The component initialization has failed.
0x88982F8C	The buffer allocated is insufficient.
0x88982F8D	Duplicate metadata is present.
0x88982F8E	The bitmap property type is unexpected.
0x88982F8F	The size is unexpected.
0x88982F90	The property query is invalid.
0x88982F91	The metadata type is unexpected.
0x88982F92	The specified bitmap property is only valid at root level.
0x88982F93	The query string contains an invalid character.
0x88982F94	Windows Codecs received an error from the Win32 system.
0x88982F95	The requested level of detail is not present.
0x88982F96	The scan index is invalid.
0x88985000	Indicates an error in an input file such as a font file.
0x88985001	Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from.
0x88985002	Indicates the specified font does not exist.
0x88985003	A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable.
0x88985004	A font file exists but could not be opened due to access denied, sharing violation, or similar error.
0x88985005	A font collection is obsolete due to changes in the system.
0x88985006	The given interface is already registered.
0x88985007	The font cache contains invalid data.
0x88985008	A font cache file corresponds to a different version of DirectWrite.
0x88985009	The operation is not supported for this type of font.
0x8898500A	The version of the text renderer interface is not compatible.
0x8898500B	The flow direction conflicts with the reading direction. They must be perpendicular to each other.
0x8898500C	The font or glyph run does not contain any colored glyphs.
0x8898500D	A font resource could not be accessed because it is remote.
0x8898500E	A font download was canceled.
0x8898500F	A font download failed.
0x88985010	A font download request was not added or a download failed because there are too many active downloads.
0x88990001	The object was not in the correct state to process the method.
0x88990002	The object has not yet been initialized.
0x88990003	The requested operation is not supported.
0x88990004	The geometry scanner failed to process the data.
0x88990005	Direct2D could not access the screen.
0x88990006	A valid display state could not be determined.
0x88990007	The supplied vector is zero.
0x88990008	An internal error (Direct2D bug) occurred. On checked builds, we would assert. The application should close this instance of Direct2D and should consider restarting its process.
0x88990009	The display format Direct2D needs to render is not supported by the hardware device.
0x8899000A	A call to this method is invalid.
0x8899000B	No hardware rendering device is available for this operation.
0x8899000C	There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present.
0x8899000D	Shader construction failed because it was too complex.
0x8899000E	Shader compilation failed.
0x8899000F	Requested DirectX surface size exceeded maximum texture size.
0x88990010	The requested Direct2D version is not supported.
0x88990011	Invalid number.
0x88990012	Objects used together must be created from the same factory instance.
0x88990013	A layer resource can only be in use once at any point in time.
0x88990014	The pop call did not match the corresponding push call.
0x88990015	The resource was realized on the wrong render target.
0x88990016	The push and pop calls were unbalanced.
0x88990017	Attempt to copy from a render target while a layer or clip rect is applied.
0x88990018	The brush types are incompatible for the call.
0x88990019	An unknown win32 failure occurred.
0x8899001A	The render target is not compatible with GDI.
0x8899001B	A text client drawing effect object is of the wrong type.
0x8899001C	The application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid.
0x8899001D	The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level.
0x8899001E	There was a configuration error in the graph.
0x8899001F	There was a internal configuration error in the graph.
0x88990020	There was a cycle in the graph.
0x88990021	Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option.
0x88990022	The operation cannot complete while there are outstanding references to the target bitmap.
0x88990023	The operation failed because the original target is not currently bound as a target.
0x88990024	Cannot set the image as a target because it is either an effect or is a bitmap that does not have the D2D1_BITMAP_OPTIONS_TARGET flag set.
0x88990025	Cannot draw with a bitmap that is currently bound as the target bitmap.
0x88990026	D3D Device does not have sufficient capabilities to perform the requested action.
0x88990027	The graph could not be rendered with the context's current tiling settings.
0x88990028	The CLSID provided to Unregister did not correspond to a registered effect.
0x88990029	The specified property does not exist.
0x8899002A	The specified sub-property does not exist.
0x8899002B	AddPage or Close called after print job is already closed.
0x8899002C	Error during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control.
0x8899002D	An effect attempted to use a transform with too many inputs.
0x8899002E	An error was encountered while decoding or parsing the requested glyph image.
0x89010001	The operation was preempted by a higher priority operation. It must be resumed later.
0x89020001	Function could not execute because it was deleted or garbage collected.
0xC0090001	The specified event is currently not being audited.
0xC0090002	The SID filtering operation removed all SIDs.
0xC0090003	Business rule scripts are disabled for the calling application.
0xC02605E8	The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote.
0xC0261003	Checksum of the obtained monitor descriptor is invalid.
0xC0261004	Monitor descriptor contains an invalid standard timing block.
0xC0261005	WMI data block registration failed for one of the MSMonitorClass WMI subclasses.
0xC0261006	Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.
0xC0261007	Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.
0xC0261008	There is no monitor descriptor data at the specified (offset, size) region.
0xC0261009	Monitor descriptor contains an invalid detailed timing block.
0xC026100A	Monitor descriptor contains invalid manufacture date.
0xC0262000	Exclusive mode ownership is needed to create unmanaged primary allocation.
0xC0262001	The driver needs more DMA buffer space in order to complete the requested operation.
0xC0262002	Specified display adapter handle is invalid.
0xC0262003	Specified display adapter and all of its state has been reset.
0xC0262004	The driver stack doesn't match the expected driver model.
0xC0262005	Present happened but ended up into the changed desktop mode
0xC0262006	Nothing to present due to desktop occlusion
0xC0262007	Not able to present due to denial of desktop access
0xC0262008	Not able to present with color conversion
0xC0262009	The kernel driver detected a version mismatch between it and the user mode driver.
0xC026200B	Present redirection is disabled (desktop windowing management subsystem is off).
0xC026200C	Previous exclusive VidPn source owner has released its ownership
0xC026200D	Window DC is not available for presentation
0xC026200E	Windowless present is disabled (desktop windowing management subsystem is off).
0xC026200F	Window handle is invalid
0xC0262010	No buffer is bound to composition surface
0xC0262011	Vail state has been changed
0xC0262012	Notifying indirect display UMDF class driver to abandon current swapchain.
0xC0262013	Notifying indirect display UMDF class driver that indirect display device has been stopped.
0xC0262014	Failed to send Create Vail Super Wet Ink message.
0xC0262015	Failed to send Destroy Vail Super Wet Ink message.
0xC0262100	Not enough video memory available to complete the operation.
0xC0262101	Couldn't probe and lock the underlying memory of an allocation.
0xC0262102	The allocation is currently busy.
0xC0262103	An object being referenced has reach the maximum reference count already and can't be reference further.
0xC0262104	A problem couldn't be solved due to some currently existing condition. The problem should be tried again later.
0xC0262105	A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately.
0xC0262106	The allocation is invalid.
0xC0262107	No more unswizzling aperture are currently available.
0xC0262108	The current allocation can't be unswizzled by an aperture.
0xC0262109	The request failed because a pinned allocation can't be evicted.
0xC0262110	The allocation can't be used from its current segment location for the specified operation.
0xC0262111	A locked allocation can't be used in the current command buffer.
0xC0262112	The allocation being referenced has been closed permanently.
0xC0262113	An invalid allocation instance is being referenced.
0xC0262114	An invalid allocation handle is being referenced.
0xC0262115	The allocation being referenced doesn't belong to the current device.
0xC0262116	The specified allocation lost its content.
0xC0262200	GPU exception is detected on the given device. The device is not able to be scheduled.
0xC0262300	Specified VidPN topology is invalid.
0xC0262301	Specified VidPN topology is valid but is not supported by this model of the display adapter.
0xC0262302	Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources.
0xC0262303	Specified VidPN handle is invalid.
0xC0262304	Specified video present source is invalid.
0xC0262305	Specified video present target is invalid.
0xC0262306	Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).
0xC0262308	Specified VidPN source mode set is invalid.
0xC0262309	Specified VidPN target mode set is invalid.
0xC026230A	Specified video signal frequency is invalid.
0xC026230B	Specified video signal active region is invalid.
0xC026230C	Specified video signal total region is invalid.
0xC0262310	Specified video present source mode is invalid.
0xC0262311	Specified video present target mode is invalid.
0xC0262312	Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.
0xC0262313	Specified video present path is already in VidPN's topology.
0xC0262314	Specified mode is already in the mode set.
0xC0262315	Specified video present source set is invalid.
0xC0262316	Specified video present target set is invalid.
0xC0262317	Specified video present source is already in the video present source set.
0xC0262318	Specified video present target is already in the video present target set.
0xC0262319	Specified VidPN present path is invalid.
0xC026231A	Miniport has no recommendation for augmentation of the specified VidPN's topology.
0xC026231B	Specified monitor frequency range set is invalid.
0xC026231C	Specified monitor frequency range is invalid.
0xC026231D	Specified frequency range is not in the specified monitor frequency range set.
0xC026231F	Specified frequency range is already in the specified monitor frequency range set.
0xC0262320	Specified mode set is stale. Please reacquire the new mode set.
0xC0262321	Specified monitor source mode set is invalid.
0xC0262322	Specified monitor source mode is invalid.
0xC0262323	Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.
0xC0262324	ID of the specified mode is already used by another mode in the set.
0xC0262325	System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.
0xC0262326	Number of video present targets must be greater than or equal to the number of video present sources.
0xC0262327	Specified present path is not in VidPN's topology.
0xC0262328	Display adapter must have at least one video present source.
0xC0262329	Display adapter must have at least one video present target.
0xC026232A	Specified monitor descriptor set is invalid.
0xC026232B	Specified monitor descriptor is invalid.
0xC026232C	Specified descriptor is not in the specified monitor descriptor set.
0xC026232D	Specified descriptor is already in the specified monitor descriptor set.
0xC026232E	ID of the specified monitor descriptor is already used by another descriptor in the set.
0xC026232F	Specified video present target subset type is invalid.
0xC0262330	Two or more of the specified resources are not related to each other, as defined by the interface semantics.
0xC0262331	ID of the specified video present source is already used by another source in the set.
0xC0262332	ID of the specified video present target is already used by another target in the set.
0xC0262333	Specified VidPN source cannot be used because there is no available VidPN target to connect it to.
0xC0262334	Newly arrived monitor could not be associated with a display adapter.
0xC0262335	Display adapter in question does not have an associated VidPN manager.
0xC0262336	VidPN manager of the display adapter in question does not have an active VidPN.
0xC0262337	Specified VidPN topology is stale. Please reacquire the new topology.
0xC0262338	There is no monitor connected on the specified video present target.
0xC0262339	Specified source is not part of the specified VidPN's topology.
0xC026233A	Specified primary surface size is invalid.
0xC026233B	Specified visible region size is invalid.
0xC026233C	Specified stride is invalid.
0xC026233D	Specified pixel format is invalid.
0xC026233E	Specified color basis is invalid.
0xC026233F	Specified pixel value access mode is invalid.
0xC0262340	Specified target is not part of the specified VidPN's topology.
0xC0262341	Failed to acquire display mode management interface.
0xC0262342	Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it.
0xC0262343	Specified VidPN is active and cannot be accessed.
0xC0262344	Specified VidPN present path importance ordinal is invalid.
0xC0262345	Specified VidPN present path content geometry transformation is invalid.
0xC0262346	Specified content geometry transformation is not supported on the respective VidPN present path.
0xC0262347	Specified gamma ramp is invalid.
0xC0262348	Specified gamma ramp is not supported on the respective VidPN present path.
0xC0262349	Multi-sampling is not supported on the respective VidPN present path.
0xC026234A	Specified mode is not in the specified mode set.
0xC026234D	Specified VidPN topology recommendation reason is invalid.
0xC026234E	Specified VidPN present path content type is invalid.
0xC026234F	Specified VidPN present path copy protection type is invalid.
0xC0262350	No more than one unassigned mode set can exist at any given time for a given VidPN source/target.
0xC0262352	Specified scanline ordering type is invalid.
0xC0262353	Topology changes are not allowed for the specified VidPN.
0xC0262354	All available importance ordinals are already used in specified topology.
0xC0262355	Specified primary surface has a different private format attribute than the current primary surface
0xC0262356	Specified mode pruning algorithm is invalid
0xC0262357	Specified monitor capability origin is invalid.
0xC0262358	Specified monitor frequency range constraint is invalid.
0xC0262359	Maximum supported number of present paths has been reached.
0xC026235A	Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology.
0xC026235B	Specified client type was not recognized.
0xC026235C	Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).
0xC0262400	Specified display adapter child device already has an external device connected to it.
0xC0262401	Specified display adapter child device does not support descriptor exposure.
0xC0262430	The display adapter is not linked to any other adapters.
0xC0262431	Lead adapter in a linked configuration was not enumerated yet.
0xC0262432	Some chain adapters in a linked configuration were not enumerated yet.
0xC0262433	The chain of linked adapters is not ready to start because of an unknown failure.
0xC0262434	An attempt was made to start a lead link display adapter when the chain links were not started yet.
0xC0262435	An attempt was made to power up a lead link display adapter when the chain links were powered down.
0xC0262436	The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state.
0xC0262438	The driver trying to start is not the same as the driver for the POSTed display adapter.
0xC026243B	An operation is being attempted that requires the display adapter to be in a quiescent state.
0xC0262500	The driver does not support OPM.
0xC0262501	The driver does not support COPP.
0xC0262502	The driver does not support UAB.
0xC0262503	The specified encrypted parameters are invalid.
0xC0262505	The GDI display device passed to this function does not have any active video outputs.
0xC026250B	An internal error caused this operation to fail.
0xC026250C	The function failed because the caller passed in an invalid OPM user mode handle.
0xC026250E	A certificate could not be returned because the certificate buffer passed to the function was too small.
0xC026250F	A video output could not be created because the frame buffer is in spanning mode.
0xC0262510	A video output could not be created because the frame buffer is in theater mode.
0xC0262511	The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.
0xC0262512	The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.
0xC0262513	The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.
0xC0262514	The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP.
0xC0262515	The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A.
0xC0262516	The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output.
0xC0262517	The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high.
0xC0262518	The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.
0xC026251A	The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop.
0xC026251B	The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote.
0xC026251C	Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only.
0xC026251D	The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
0xC026251E	The method failed because an unexpected error occurred inside of a display driver.
0xC026251F	Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only.
0xC0262520	The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.
0xC0262521	The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.
0xC0262580	The monitor connected to the specified video output does not have an I2C bus.
0xC0262581	No device on the I2C bus has the specified address.
0xC0262582	An error occurred while transmitting data to the device on the I2C bus.
0xC0262583	An error occurred while receiving data from the device on the I2C bus.
0xC0262584	The monitor does not support the specified VCP code.
0xC0262585	The data received from the monitor is invalid.
0xC0262586	The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor.
0xC0262587	The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.
0xC0262588	An internal Monitor Configuration API error occurred.
0xC0262589	An operation failed because a DDC/CI message had an invalid value in its command field.
0xC026258A	An error occurred because the field length of a DDC/CI message contained an invalid value.
0xC026258B	An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer.
0xC026258C	This function failed because an invalid monitor handle was passed to it.
0xC026258D	The operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications.
0xC02625D8	A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value.
0xC02625D9	The monitor's VCP Version (0xDF) VCP code returned an invalid version value.
0xC02625DA	The monitor does not comply with the MCCS specification it claims to support.
0xC02625DB	The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.
0xC02625DC	The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.
0xC02625DE	The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0xC02625DF	SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.
0xC02625E0	This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session.
0xC02625E1	This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.
0xC02625E2	The function failed because the specified GDI display device was not attached to the Windows desktop.
0xC02625E3	This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.
0xC02625E4	The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned.
0xC02625E5	The function failed because the specified GDI device did not have any monitors associated with it.
0xC02625E6	An array passed to the function cannot hold all of the data that the function must copy into the array.
0xC02625E7	An internal error caused an operation to fail.
0xC034100F	The TCP connection is not offloadable because of a local policy setting.
0xC0341012	The TCP connection is not offloadable by the Chimney Offload target.
0xC0341013	The IP Path object is not in an offloadable state.
0xC0350002	The hypervisor does not support the operation because the specified hypercall code is not supported.
0xC0350003	The hypervisor does not support the operation because the encoding for the hypercall input register is not supported.
0xC0350004	The hypervisor could not perform the operation because a parameter has an invalid alignment.
0xC0350005	The hypervisor could not perform the operation because an invalid parameter was specified.
0xC0350006	Access to the specified object was denied.
0xC0350007	The hypervisor could not perform the operation because the partition is entering or in an invalid state.
0xC0350008	The operation is not allowed in the current state.
0xC0350009	The hypervisor does not recognize the specified partition property.
0xC035000A	The specified value of a partition property is out of range or violates an invariant.
0xC035000B	There is not enough memory in the hypervisor pool to complete the operation.
0xC035000C	The maximum partition depth has been exceeded for the partition hierarchy.
0xC035000D	A partition with the specified partition Id does not exist.
0xC035000E	The hypervisor could not perform the operation because the specified VP index is invalid.
0xC0350011	The hypervisor could not perform the operation because the specified port identifier is invalid.
0xC0350012	The hypervisor could not perform the operation because the specified connection identifier is invalid.
0xC0350013	Not enough buffers were supplied to send a message.
0xC0350014	The previous virtual interrupt has not been acknowledged.
0xC0350015	A virtual processor is not in the correct state for the indicated operation.
0xC0350016	The previous virtual interrupt has already been acknowledged.
0xC0350017	The indicated partition is not in a valid state for saving or restoring.
0xC0350018	The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled.
0xC0350019	The hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation.
0xC035001A	The proximity domain information is invalid.
0xC035001B	An attempt to retrieve debugging data failed because none was available.
0xC035001C	The physical connection being used for debugging has not recorded any receive activity since the last operation.
0xC035001D	There are not enough resources to complete the operation.
0xC035001E	A hypervisor feature is not available to the user.
0xC0350033	The specified buffer was too small to contain all of the requested data.
0xC0350038	The maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition.
0xC035003C	Validation of CPUID data of the processor failed.
0xC035003D	Validation of XSAVE CPUID data of the processor failed.
0xC035003E	Processor did not respond within the timeout period.
0xC035003F	SMX has been enabled in the BIOS.
0xC0350041	The hypervisor could not perform the operation because the specified LP index is invalid.
0xC0350050	The supplied register value is invalid.
0xC0350051	The supplied virtual trust level is not in the correct state to perform the requested operation.
0xC0350055	No execute feature (NX) is not present or not enabled in the BIOS.
0xC0350057	The supplied device ID is invalid.
0xC0350058	The operation is not allowed in the current device state.
0xC0350060	The supplied page request specifies a memory access that the guest does not have permissions to perform.
0xC035006F	A CPU group with the specified CPU group Id does not exist.
0xC0350070	The hypervisor could not perform the operation because the CPU group is entering or in an invalid state.
0xC0350071	The requested operation failed.
0xC0350072	The hypervisor could not perform the operation because it is not allowed with nested virtualization active.
0xC0350073	There is not enough memory in the root partition's pool to complete the operation.
0xC0350074	The provided event log buffer was already marked as freed.
0xC0350075	There is not enough contiguous memory in the partition's pool to complete the operation.
0xC0351000	No hypervisor is present on this system.
0xC0370001	The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370002	The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370003	The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370004	No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370005	The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370006	The partition name of the virtualization infrastructure driver exceeds the maximum.
0xC0370007	The message queue name of the virtualization infrastructure driver exceeds the maximum.
0xC0370008	Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.
0xC0370009	The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037000A	The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037000B	A message queue with the same name already exists for the virtualization infrastructure driver.
0xC037000C	The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037000D	The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.
0xC037000E	Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037000F	The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration.
0xC0370010	The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.
0xC0370011	The memory block for the virtualization infrastructure driver is already associated with a message queue.
0xC0370012	The handle is not a valid memory block handle for the virtualization infrastructure driver.
0xC0370013	The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370014	The handle is not a valid message queue handle for the virtualization infrastructure driver.
0xC0370015	The handle is not a valid page range handle for the virtualization infrastructure driver.
0xC0370016	Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.
0xC0370017	The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370018	The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.
0xC0370019	Notifications cannot be created on the memory block because it is use.
0xC037001A	The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037001B	Cannot add a virtual processor to the partition because the maximum has been reached.
0xC037001C	Cannot stop the virtual processor immediately because of a pending intercept.
0xC037001D	Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037001E	The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC037001F	This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370020	Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370021	The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370022	The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370023	Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370024	The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370025	Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370026	Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.
0xC0370027	Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine.
0xC0370028	Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine.
0xC0370029	Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.
0xC037002A	The specified VTL does not have the permission to access the resource.
0xC0370100	The virtual machine or container exited unexpectedly while starting.
0xC0370101	The container operating system does not match the host operating system.
0xC0370102	The virtual machine could not be started because a required feature is not installed.
0xC0370103	The call to start an asynchronous operation succeeded and the operation is performed in the background.
0xC0370104	The supported number of notification callbacks has been exceeded.
0xC0370105	The requested virtual machine or container operation is not valid in the current state.
0xC0370106	The virtual machine or container exited unexpectedly.
0xC0370107	The virtual machine or container was forcefully exited.
0xC0370108	A connection could not be established with the container or virtual machine.
0xC0370109	The operation timed out because a response was not received from the virtual machine or container.
0xC037010A	The connection with the virtual machine or container was closed.
0xC037010B	An unknown internal message was received by the virtual machine or container.
0xC037010C	The virtual machine or container does not support an available version of the communication protocol with the host.
0xC037010D	The virtual machine or container JSON document is invalid.
0xC037010E	A virtual machine or container with the specified identifier does not exist.
0xC037010F	A virtual machine or container with the specified identifier already exists.
0xC0370110	The virtual machine or container with the specified identifier is not running.
0xC0370111	A communication protocol error has occurred between the virtual machine or container and the host.
0xC0370112	The container image contains a layer with an unrecognized format.
0xC0370113	To use this container image, you must join the Windows Insider Program. Please see https://go.microsoft.com/fwlink/?linkid=850659 for more information.
0xC0370200	A virtual switch with the given name was not found.
0xC0370400	Cannot restore this virtual machine because a file read from the vSMB saved state data could not be found. Delete the saved state data and then try to start the virtual machine.
0xC0370401	Cannot restore this virtual machine because the vSMB saved state data cannot be read. Delete the saved state data and then try to start the virtual machine.
0xC0370500	Partition state blob not found. Make sure the virtual machine is saved for this content to be included in the saved state file(s).
0xC0370501	Guest memory not found. Make sure the virtual machine is saved for this content to be included in the saved state file(s).
0xC0370502	No virtual processor information found in the saved partition blob. Make sure the virtual machine is saved successfully for this content to be included in the partition state.
0xC0370503	A virtual processor has been detected to have nested virtualization enabled. Nested Virtualization is not supported yet by VmSavedStateDumpProvider.
0xC0370504	The Windows kernel image address could not be found in the virtual machine saved state.
0xC0370505	Failed to read Page Map Level 4 entry (pxe) for a virtual address.
0xC0370506	Failed to read Page Directory Page Table entry (pdpte) for a virtual address.
0xC0370507	Failed to read Page Directory entry (pde) for a virtual address.
0xC0370508	Failed to read Page Table entry (pte) for a virtual address.
0xC0380001	The configuration database is full.
0xC0380002	The configuration data on the disk is corrupted.
0xC0380003	The configuration on the disk is not insync with the in-memory configuration.
0xC0380004	A majority of disks failed to be updated with the new configuration.
0xC0380005	The disk contains non-simple volumes.
0xC0380006	The same disk was specified more than once in the migration list.
0xC0380007	The disk is already dynamic.
0xC0380008	The specified disk id is invalid. There are no disks with the specified disk id.
0xC0380009	The specified disk is an invalid disk. Operation cannot complete on an invalid disk.
0xC038000A	The specified disk(s) cannot be removed since it is the last remaining voter.
0xC038000B	The specified disk has an invalid disk layout.
0xC038000C	The disk layout contains non-basic partitions which appear after basic partitions. This is an invalid disk layout.
0xC038000D	The disk layout contains partitions which are not cylinder aligned.
0xC038000E	The disk layout contains partitions which are smaller than the minimum size.
0xC038000F	The disk layout contains primary partitions in between logical drives. This is an invalid disk layout.
0xC0380010	The disk layout contains more than the maximum number of supported partitions.
0xC0380011	The specified disk is missing. The operation cannot complete on a missing disk.
0xC0380012	The specified disk is not empty.
0xC0380013	There is not enough usable space for this operation.
0xC0380014	The force revectoring of bad sectors failed.
0xC0380015	The specified disk has an invalid sector size.
0xC0380016	The specified disk set contains volumes which exist on disks outside of the set.
0xC0380017	A disk in the volume layout provides extents to more than one member of a plex.
0xC0380018	A disk in the volume layout provides extents to more than one plex.
0xC0380019	Dynamic disks are not supported on this system.
0xC038001A	The specified extent is already used by other volumes.
0xC038001B	The specified volume is retained and can only be extended into a contiguous extent. The specified extent to grow the volume is not contiguous with the specified volume.
0xC038001C	The specified volume extent is not within the public region of the disk.
0xC038001D	The specified volume extent is not sector aligned.
0xC038001E	The specified partition overlaps an EBR (the first track of an extended partition on an MBR disk).
0xC038001F	The specified extent lengths cannot be used to construct a volume with specified length.
0xC0380020	The system does not support fault tolerant volumes.
0xC0380021	The specified interleave length is invalid.
0xC0380022	There is already a maximum number of registered users.
0xC0380023	The specified member is already in-sync with the other active members. It does not need to be regenerated.
0xC0380024	The same member index was specified more than once.
0xC0380025	The specified member index is greater or equal than the number of members in the volume plex.
0xC0380026	The specified member is missing. It cannot be regenerated.
0xC0380027	The specified member is not detached. Cannot replace a member which is not detached.
0xC0380028	The specified member is already regenerating.
0xC0380029	All disks belonging to the pack failed.
0xC038002A	There are currently no registered users for notifications. The task number is irrelevant unless there are registered users.
0xC038002B	The specified notification user does not exist. Failed to unregister user for notifications.
0xC038002C	The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications.
0xC038002D	The specified number of members is invalid.
0xC038002E	The specified number of plexes is invalid.
0xC038002F	The specified source and target packs are identical.
0xC0380030	The specified pack id is invalid. There are no packs with the specified pack id.
0xC0380031	The specified pack is the invalid pack. The operation cannot complete with the invalid pack.
0xC0380032	The specified pack name is invalid.
0xC0380033	The specified pack is offline.
0xC0380034	The specified pack already has a quorum of healthy disks.
0xC0380035	The pack does not have a quorum of healthy disks.
0xC0380036	The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported.
0xC0380037	Failed to update the disk's partition layout.
0xC0380038	The specified plex is already in-sync with the other active plexes. It does not need to be regenerated.
0xC0380039	The same plex index was specified more than once.
0xC038003A	The specified plex index is greater or equal than the number of plexes in the volume.
0xC038003B	The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline.
0xC038003C	The specified plex is missing.
0xC038003D	The specified plex is currently regenerating.
0xC038003E	The specified plex type is invalid.
0xC038003F	The operation is only supported on RAID-5 plexes.
0xC0380040	The operation is only supported on simple plexes.
0xC0380041	The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set.
0xC0380042	There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications.
0xC0380043	There is currently a transaction in process.
0xC0380044	An unexpected layout change occurred outside of the volume manager.
0xC0380045	The specified volume contains a missing disk.
0xC0380046	The specified volume id is invalid. There are no volumes with the specified volume id.
0xC0380047	The specified volume length is invalid.
0xC0380048	The specified size for the volume is not a multiple of the sector size.
0xC0380049	The operation is only supported on mirrored volumes.
0xC038004A	The specified volume does not have a retain partition.
0xC038004B	The specified volume is offline.
0xC038004C	The specified volume already has a retain partition.
0xC038004D	The specified number of extents is invalid.
0xC038004E	All disks participating to the volume must have the same sector size.
0xC038004F	The boot disk experienced failures.
0xC0380050	The configuration of the pack is offline.
0xC0380051	The configuration of the pack is online.
0xC0380052	The specified pack is not the primary pack.
0xC0380053	All disks failed to be updated with the new content of the log.
0xC0380054	The specified number of disks in a plex is invalid.
0xC0380055	The specified number of disks in a plex member is invalid.
0xC0380056	The operation is not supported on mirrored volumes.
0xC0380057	The operation is only supported on simple and spanned plexes.
0xC0380058	The pack has no valid log copies.
0xC0380059	A primary pack is already present.
0xC038005A	The specified number of disks is invalid.
0xC038005B	The system does not support mirrored volumes.
0xC038005C	The system does not support RAID-5 volumes.
0xC0390002	Entries enumerated have exceeded the allowed threshold.
0xC03A0001	The virtual hard disk is corrupted. The virtual hard disk drive footer is missing.
0xC03A0002	The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum.
0xC03A0003	The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted.
0xC03A0004	The system does not recognize the file format of this virtual hard disk.
0xC03A0005	The version does not support this version of the file format.
0xC03A0006	The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum.
0xC03A0007	The system does not support this version of the virtual hard disk.This version of the sparse header is not supported.
0xC03A0008	The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt.
0xC03A0009	Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk.
0xC03A000A	The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt.
0xC03A000B	The system does not support this version of the virtual hard disk. The block size is invalid.
0xC03A000C	The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk.
0xC03A000D	The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk.
0xC03A000E	The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk.
0xC03A000F	The chain of virtual hard disks is corrupted. The time stamp of the parent virtual hard disk does not match the time stamp of the differencing disk.
0xC03A0010	Failed to read the metadata of the virtual hard disk.
0xC03A0011	Failed to write to the metadata of the virtual hard disk.
0xC03A0012	The size of the virtual hard disk is not valid.
0xC03A0013	The file size of this virtual hard disk is not valid.
0xC03A0014	A virtual disk support provider for the specified file was not found.
0xC03A0015	The specified disk is not a virtual disk.
0xC03A0016	The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk.
0xC03A0017	The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk.
0xC03A0018	The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain.
0xC03A0019	The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain.
0xC03A001A	The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse.
0xC03A001B	The requested operation cannot be performed on a virtual disk of this type.
0xC03A001C	The requested operation cannot be performed on the virtual disk in its current state.
0xC03A001D	The sector size of the physical disk on which the virtual disk resides is not supported.
0xC03A001E	The disk is already owned by a different owner.
0xC03A001F	The disk must be offline or read-only.
0xC03A0020	Change Tracking is not initialized for this virtual disk.
0xC03A0021	Size of change tracking file exceeded the maximum size limit.
0xC03A0022	VHD file is changed due to compaction, expansion, or offline updates.
0xC03A0023	Change Tracking for the virtual disk is not in a valid state to perform this request. Change tracking could be discontinued or already in the requested state.
0xC03A0024	Change Tracking file for the virtual disk is not in a valid state.
0xC03A0025	The requested resize operation could not be completed because it might truncate user data residing on the virtual disk.
0xC03A0026	The requested operation could not be completed because the virtual disk's minimum safe size could not be determined. This may be due to a missing or corrupt partition table.
0xC03A0027	The requested operation could not be completed because the virtual disk's size cannot be safely reduced further.
0xC03A0028	There is not enough space in the virtual disk file for the provided metadata item.
0xC03A0029	The specified change tracking identifier is not valid.
0xC03A002A	Change tracking is disabled for the specified virtual hard disk, so no change tracking information is available.
0xC03A0030	There is no change tracking data available associated with the specified change tracking identifier.
0xC05C0000	The proper error code with sense data was stored on server side.
0xC05CFF00	The requested error data is not available on the server.
0xC05CFF01	Unit Attention data is available for the initiator to query.
0xC05CFF02	The data capacity of the device has changed, resulting in a Unit Attention condition.
0xC05CFF03	A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition.
0xC05CFF04	A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition.
0xC05CFF05	A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition.
0xC05CFF06	The data storage format of the device has changed, resulting in a Unit Attention condition.
0xC05CFF07	The current initiator is not allowed to perform the SCSI command because of a reservation conflict.
0xC05CFF08	Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks.
0xC05CFF09	The server version does not match the requested version.
0xC05CFF0A	The requested operation cannot be performed on the virtual disk as it is currently used in shared mode.
0xC05CFF0B	Invalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures.
0xC05CFF0C	The requested operation failed due to a missing backing storage file.
0xC05D0000	Failed to negotiate a preauthentication integrity hash function.
0xC05D0001	The current cluster functional level does not support this SMB dialect.
0xC0E80000	The command was not recognized by the security core
0xC0EA0001	No applicable app licenses found.
0xC0EA0002	CLiP license not found.
0xC0EA0003	CLiP device license not found.
0xC0EA0004	CLiP license has an invalid signature.
0xC0EA0005	CLiP keyholder license is invalid or missing.
0xC0EA0006	CLiP license has expired.
0xC0EA0007	CLiP license is signed by an unknown source.
0xC0EA0008	CLiP license is not signed.
0xC0EA0009	CLiP license hardware ID is out of tolerance.
0xC0EA000A	CLiP license device ID does not match the device ID in the bound device license.
6729 entries