403WebShell

403Webshell

Server IP : 121.121.20.254 / Your IP : 216.73.216.41
Web Server : Microsoft-IIS/10.0
System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64
User : IUSR ( 0)
PHP Version : 8.3.28
Disable Function : NONE
MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF
Directory : C:/Windows/SysWOW64/en-US/

Upload File :

[ Back ]

Current File : C:/Windows/SysWOW64/en-US/ntdll.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!P

pF@ <M8.rdata�@@.rsrcP N@@��T
T88��T$��8.rdata8x.rdata$zzzdbg �.rsrc$01� PL.rsrc$02 1]3T�
���R���$�@��,W�����T��(�@�X�p����� � � �� ���!H��i��MUI������ٗ�:�Kg>*O��h�����%M��������MUIen-US<
??�
���
��0��< 0�d(0)gh�.�/P00)0)�0Y5Y5�1��X2@7@�3�@�@ep@p@Pe@@�eD�@D�@�f@
@�gV@V@pj�@�@�j
@
@hk
@
@�l@@<m4@5@p@@4q�@�@�q
@
@�s@@�u@@dv@@�vK@L@pwQ@Q@<y/@/@�y7@7@Xz9@:@�z<@<@|#@#@�|# )@# )@$}���}
��Ђ�4�`��������H�'��'�������������ܤ������� � �ħ)�)�,�1�1���A�B�(�����������!�!���7�7���8�8��9�9�ȱ9�9�T�:�:��?�?�h�C�C���n�@�r�x���z������I�t�P�\�%^�s�h5u�|�G����|K�����O�����T��
��k �"�t�P�_��a�f���h�o���q�t�,�����\��� � �!�@�#�-��/�/��2�5���@�F���P�Y��`�������������������.�����/��`0��`>
��C�&�dD���a��e���g � ��q � �Py���zw��������������������������� �����p�!��&��̜A��C����E��F��������������������������Э����������б����L���!��������@���l���0�����!�&��(�M���O�U���W�X���b�e�����t�Y�a���5�9�X�
�
�,�
�
�8�
�
���"
�"
��$
�$
���&
�(
��*
�+
�l�.
�:
�������� �)��0�1��!���" �!�@,��-�'��4��LD
��J��L!�&�U(�(�XY0�0��Z2�3�[6�@��\C�a�xe����
�0�D���������� � ���#�$���
���� �������� ������������D���\���T��J�H�M�P��R�\�\����0�6��8�8��;�;�� ��H
�����T��h
��\�!�$����&�����3!�*!��=0!�A!�`XC!�Z!��f\!�]!��wa!�a!�$z"�D"��z"�"���#�#�H�#�
#���#�#�|�#�#�$�"#�"#�Ч*#�1#�@��#��#�l�#�#�ج#�#�t� #� #�x�$� $�0�
$�
$�ȹ*$�1$�T�G$�G$���P$�P$�t�Z$�Z$���t$�t$�t�)�_)��a)�c)���)��)�|��)��)���)��)�8��)��)����)��)�@��)��)�@)�)��)�)�x)�)��)�)� )�!)�T#)�()�$-)�1)��
B)�L)�XP)�U)�)�)�,)�)�0)�)�p )�" )�#0)�0)��3@)�@)��65�5��75�5�<@35�35��I85�85��J<5�?5��KA5�A5��MP5�Q5�<NU5�U5�`OW5�X5��O`5�`5��Po5�w5��Qy5�y5��V�5��5�PW5�5��W6� 6�,X�6��6�d\7�*7��a8�\8���9�9���:�$:�p�(:�*:��0:�3:� �@�@�0�A�A�|�B�B�T�B�B�H�C�C��C�C���D�D�,E�E�( E�E��P�P�TQ�Q�|
\�\�0�\��\��]�]�� ]� ]������X��X �'���+�
�$,�
�2��5���9� �C(STATUS_SUCCESS

$STATUS_WAIT_1

$STATUS_WAIT_2

$STATUS_WAIT_3

(STATUS_WAIT_63

8STATUS_ABANDONED_WAIT_0

<STATUS_ABANDONED_WAIT_63

(STATUS_USER_APC

�The requested action was completed by an earlier operation.

,STATUS_KERNEL_APC

(STATUS_ALERTED

(STATUS_TIMEOUT

xThe operation that was requested is pending completion.

�A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.

�Returned by enumeration APIs to indicate more information is available to successive calls.

�Indicates not all privileges or groups referenced are assigned to the caller.

This allows, for example, all privileges to be disabled without having to know exactly which privileges are assigned.

�Some of the information to be translated has not been translated.

�An open/create operation completed while an oplock break is underway.

hA new volume has been mounted by a file system.

�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.

This indicates that a notify change request has been completed due to closing the handle which made the notify change request.

�This indicates that a notify change request is being completed and that the information is not being returned in the caller's buffer.

The caller now needs to enumerate the files to find the changes.

�{No Quotas}

No system quota limits are specifically set for this account.

�{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.

PPage fault was a transition fault.

PPage fault was a demand zero fault.

�Page fault was satisfied by reading from a secondary storage device.

\Cached page was locked during operation.

LCrash dump exists in paging file.

TSpecified buffer contains all zeros.

�A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link.

�The device has succeeded a query-stop and its resource requirements have changed.

�The translator has translated these resources into the global space and no further translations should be performed.

�The directory service evaluated group memberships locally, as it was unable to contact a global catalog server.

xA process being terminated has no threads to terminate.

`The specified process is not part of a job.

XThe specified process is part of a job.

�{Volume Shadow Copy Service}

The system is now ready for hibernation.

�A file system or file system filter driver has successfully completed an FsFilter operation.

tThe specified interrupt vector was already connected.

pThe specified interrupt vector is still connected.

\The current process is a cloned process.

�The file was locked and all users of the file can only read.

�The file was locked and at least one user of the file can write.

DThe file image hash is valid.

HThe file catalog hash is valid.

xThe file hash is valid and uses strong code integrity.

�At least a portion of IO range intersects with a ghosted file range.

|A completed operation may have overwritten previous data.

�The specified ResourceManager made no changes or updates to the resource under this transaction.

�The specified ring buffer was empty before the packet was successfully inserted.

�The specified ring buffer was full before the packet was successfully removed.

�The specified ring buffer has dropped below its quota of outstanding transactions.

�The specified ring buffer has, with the removal of the current packet, now become empty.

The specified ring buffer was either previously empty or previously full which implies that the caller should signal the opposite endpoint.

�The oplock that was associated with this handle is now associated with a different handle.

�The handle with which this oplock was associated has been closed. The oplock is now broken.

hAn operation is blocked waiting for an oplock.

�A reparse should be performed by the Object Manager from the global root to escape the container name space.

@Debugger handled exception

0Debugger continued

LThe IO was completed by a filter.

�The remote TPM context exchange is not complete. The context should be transported to the target and continued.

TThe remote TPM operation is complete.

�The device had pending page requests which were discarded.

@The repair was successful.

HThe operation has been paused.

@The operation is complete.

pThe operation should be redirected to another node.

�{Object Exists}

An attempt was made to create an object and the object name already existed.

{Thread Suspended}

A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded.

${Working Set Range Error}

An attempt was made to set the working set minimum or maximum to values which are outside of the allowable range.

({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.

This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created.

�{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.

L{Local Session Key}

A user session key was requested for a local RPC connection. The session key returned is a constant value and not unique to this connection.

P{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.

({Serial IOCTL Complete}

A serial I/O operation was completed by another write to a serial port.

(The IOCTL_SERIAL_XOFF_COUNTER reached zero.)

H{Registry Recovery}

One of the files containing the system's Registry data had to be recovered by use of a log or alternate copy. The recovery was successful.

d{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.

d{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.

0{Serial IOCTL Timeout}

A serial I/O operation completed because the time-out period expired. (The IOCTL_SERIAL_XOFF_COUNTER had not reached zero.)

@{Password Too Complex}

The Windows password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string.

X{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.

{Partial Data Received}

The network transport returned partial data to its client. The remaining data will be sent later.

{Expedited Data Received}

The network transport returned data to its client that was marked as expedited by the remote system.

�{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.

�{TDI Event Done}

The TDI indication has completed successfully.

�{TDI Event Pending}

The TDI indication has entered the pending state.

@Checking file system on %wZ

D{Fatal Application Exit}

%hs

�The specified registry key is referenced by a predefined handle.

${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.

%hs

�{Page Locked}

One of the pages to lock was already locked.

@Application popup: %1 : %2

4STATUS_ALREADY_WIN32

�Exception status code used by Win32 x86 emulation subsystem.

�{Machine Type Mismatch}

The image file %hs is valid, but is for a machine type other than the current machine.

�A yield execution was performed and no thread was available to run.

hThe resumable flag to a timer API was ignored.

�The arbiter has deferred arbitration of these resources to its parent

The device "%hs" has detected a CardBus card in its slot, but the firmware on this system is not configured to allow the CardBus controller to be run in CardBus mode.

The operating system will currently accept only 16-bit (R2) pc-cards on this controller.

�Exception status code used by Win32 x86 emulation subsystem.

|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.

TThe system was put into hibernation.

\The system was resumed from hibernation.

�Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3].

LA 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.

�The ALPC message being canceled has already been retrieved from the queue on the other side.

xThe system power state is transitioning from %2 to %3.

�The receive operation was successful. Check the ALPC completion list for the received message.

�The system power state is transitioning from %2 to %3 but could enter %4.

dAccess to %1 is monitored by policy rule %2.

�A valid hibernation file has been invalidated and should be abandoned.

�Business rule scripts are disabled for the calling application.

�The specified copy of the requested data was successfully read.

`{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.

�A system patch was successfully loaded but is not applicable to any currently loaded images.

4The system has awoken

XThe Directory Service is shutting down.

The volume repair could not be performed while it is online.

Please schedule to take the volume offline so that it can be repaired.

�One or more services failed to start during the service startup phase of a run level switch.

@Debugger will reply later.

HDebugger cannot provide handle.

@Debugger terminated thread.

DDebugger terminated process.

8Debugger got control C.

\Debugger printed exception on control C.

LDebugger received RIP exception.

LDebugger received control break.

\Debugger command communication exception.

\Debugger printed exception on control C.

�A UUID that is valid only on this computer has been allocated.

pSome data remains to be sent in the request buffer.

�The Client Drive Mapping Service Has Connected on Terminal Connection.

�The Client Drive Mapping Service Has Disconnected on Terminal Connection.

�A kernel mode component is releasing a reference on an activation context.

�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.

�The transactional resource manager is already consistent. Recovery is not needed.

�The transactional resource manager has already been started.

�Log service encountered a log stream with no restart area.

<{Display Driver Recovered From Failure}

The %hs display driver has detected and recovered from a failure. Some graphical operations may have failed. The next time you reboot the machine a dialog will be displayed giving you a chance to upload data about this failure to Microsoft.

�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).

�Skip preparation of allocations referenced by the DMA buffer.

xNo mode is pinned on the specified VidPN source/target.

�Specified mode set does not specify preference for one of its modes.

�Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty.

Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements.

�Specified content transformation is not pinned on the specified VidPN present path.

lChild device presence was not reliably detected.

�Starting the leadlink adapter has been deferred temporarily.

�The display adapter is being polled for children too frequently at the same polling level.

pStarting the adapter has been deferred temporarily.

�We can depend on the child device presence returned by the driver.

�The request will be completed later by NDIS status indication.

�The requested salt size for signing with RSAPSS does not match what the TPM uses.

{EXCEPTION}

Guard Page Exception

A page of memory that marks the end of a data structure, such as a stack or an array, has been accessed.

�{EXCEPTION}

Alignment Fault

A datatype misalignment was detected in a load or store instruction.

x{EXCEPTION}

Breakpoint

A breakpoint has been reached.

�{EXCEPTION}

Single Step

A single step or trace operation has just been completed.

�{Buffer Overflow}

The data was too large to fit into the specified buffer.

�{No More Files}

No more files were found which match the file specification.

�{Kernel Debugger Awakened}

the system debugger was awakened by an interrupt.

�{Handles Closed}

Handles to objects have been automatically closed as a result of the requested operation.

�{Non-Inheritable ACL}

An access control list (ACL) contains no components that can be inherited.

\{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.

�{Partial Copy}

Due to protection conflicts not all the requested bytes could be copied.

d{Out of Paper}

The printer is out of paper.

�{Device Power Is Off}

The printer power has been turned off.

t{Device Offline}

The printer has been taken offline.

d{Device Busy}

The device is currently busy.

�{No More EAs}

No more extended attributes (EAs) were found for the file.

�{Illegal EA}

The specified extended attribute (EA) name contains at least one illegal character.

�{Inconsistent EA List}

The extended attribute (EA) list is inconsistent.

�{Invalid EA Flag}

An invalid extended attribute (EA) flag was set.

h{Verifying Disk}

The media has changed and a verify operation is in progress so no reads or writes may be performed to the device, except those used in the verify operation.

�{Too Much Information}

The specified access control list (ACL) contained more information than was expected.

,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).

�{No More Entries}

No more entries are available from an enumeration operation.

`{Filemark Found}

A filemark was detected.

d{Media Changed}

The media may have changed.

h{I/O Bus Reset}

An I/O bus reset was detected.

t{End of Media}

The end of the media was encountered.

lBeginning of tape or partition has been detected.

d{Media Changed}

The media may have changed.

LA tape access reached a setmark.

�During a tape access, the end of the data written is reached.

lThe redirector is in use and cannot be unloaded.

dThe server is in use and cannot be unloaded.

xThe specified connection has already been disconnected.

HA long jump has been executed.

pA cleaner cartridge is present in the tape library.

tThe Plug and Play query operation was not successful.

\A frame consolidation has been executed.

{Registry Hive Recovered}

Registry hive (file):

%hs

was corrupted and it has been recovered. Some data might have been lost.

tThe 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?

�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?

�The create operation stopped after reaching a symbolic link.

�An oplock of the requested level cannot be granted. An oplock of a lower level may be available.

�{No ACE Condition}

The specified access control entry (ACE) does not contain a condition.

�{Support Being Determined}

Device's command support detection is in progress.

TThe device needs to be power cycled.

�The action requested resulted in no work being done. Error-style clean-up has been performed.

A return address hijack is being attempted. This is supported by the operating system when user-mode shadow stacks are enabled.

�{EXCEPTION}

Recoverable Bugcheck Exception

A bugcheck was re-raised as an exception.

tThe device has indicated that cleaning is necessary.

�The device has indicated that its door is open. Further operations require it closed and secured.

HWindows discovered a corruption in the file "%hs".

This file has now been repaired.

Please check if any data in the file was lost because of the corruption.

tThe interrupt requested to be unmasked is not masked.

�The cloud file property is possibly corrupt. The on-disk checksum does not match the computed checksum.

TThe cloud file property is too large.

�The maximum number of cloud file properties has been reached.

XDebugger did not handle the exception.

HThe cluster node is already up.

LThe cluster node is already down.

XThe cluster network is already online.

XThe cluster network is already offline.

tThe cluster node is already a member of the cluster.

hThe log could not be set to the requested size.

dThere is no transaction metadata on the file.

�The file can't be recovered because there is a handle still open on it.

�Transaction metadata is already present on this file and cannot be superseded.

�A transaction scope could not be entered because the scope handler has not been initialized.

{Display Driver Stopped Responding and recovered}

The %hs display driver has stopped working normally. The recovery had been performed.

�{Buffer too small}

The buffer is too small to contain the entry. No information has been written to the buffer.

dVolume Metadata read or write is incomplete.

�BitLocker encryption keys were ignored because the volume was in a transient state.

0A 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.

�The regeneration operation was not able to copy all data from the active plexes due to bad sectors.

One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems.

�Some BCD entries were not imported correctly from the BCD store.

�Some BCD entries were not synchronized correctly with the firmware.

�The virtualization storage subsystem has generated an error.

xGDI handles were potentially leaked by the application.

`Secure Boot is not enabled on this machine.

�{Operation Failed}

The requested operation was unsuccessful.

�{Not Implemented}

The requested operation is not implemented.

�{Invalid Parameter}

The specified information class is not a valid information class for the specified object.

�The specified information record length does not match the length required for the specified information class.

�The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

xThe pagefile quota for the process has been exhausted.

LAn invalid HANDLE was specified.

�An invalid initial stack was specified in a call to NtCreateThread.

�An invalid initial start address was specified in a call to NtCreateThread.

PAn invalid Client ID was specified.

hAn 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.

|An invalid parameter was passed to a service or function.

dA device which does not exist was specified.

h{File Not Found}

The file %hs does not exist.

�The specified request is not a valid operation for the target device.

�The end-of-file marker has been reached. There is no valid data in the file beyond this marker.

�{Wrong Volume}

The wrong volume is in the drive.

Please insert volume %hs into drive %hs.

�{No Disk}

There is no disk in the drive.

Please insert a disk into drive %hs.

{Unknown Disk Format}

The disk in drive %hs is not formatted properly.

Please check the disk, and reformat if necessary.

|{Sector Not Found}

The specified sector does not exist.

�{Still Busy}

The specified I/O request packet (IRP) cannot be disposed of because the I/O operation is not complete.

�{Not Enough Quota}

Not enough virtual memory or paging file quota is available to complete the specified operation.

�{Conflicting Address Range}

The specified address range conflicts with the address space.

dAddress range to unmap is not a mapped view.

HVirtual memory cannot be freed.

TSpecified section cannot be deleted.

�An invalid system service was specified in a system service call.

�{EXCEPTION}

Illegal Instruction

An attempt was made to execute an illegal instruction.

�{Invalid Lock Sequence}

An attempt was made to execute an invalid lock sequence.

�{Invalid Mapping}

An attempt was made to create a view for a section which is bigger than the section.

�{Bad File}

The attributes of the specified mapping file for a section of memory cannot be read.

�{Already Committed}

The specified address range is already committed.

�{Access Denied}

A process has requested access to an object, but has not been granted those access rights.

�{Buffer Too Small}

The buffer is too small to contain the entry. No information has been written to the buffer.

<{Wrong Type}

There is a mismatch between the type of object required by the requested operation and the type of object that is specified in the request.

�{EXCEPTION}

Cannot Continue

Windows cannot continue from this exception.

�An invalid exception disposition was returned by an exception handler.

8Unwind exception code.

�An invalid or unaligned stack was encountered during an unwind operation.

�An invalid unwind target was encountered during an unwind operation.

�An attempt was made to unlock a page of memory which was not locked.

TDevice parity error on I/O operation.

�An attempt was made to decommit uncommitted virtual memory.

�An attempt was made to change the attributes on memory that has not been committed.

�Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort

Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port.

pAn invalid combination of parameters was specified.

�An attempt was made to lower a quota limit below the current usage.

{Corrupt Disk}

The file system structure on the disk is corrupt and unusable.

Please run the Chkdsk utility on the volume %hs.

4Object Name invalid.

8Object Name not found.

@Object Name already exists.

XA port with the 'do not disturb' flag set attempted to send a message to a port in a suspended process.

The process was not woken, and the message was not delivered.

�Attempt to send a message to a disconnected communication port.

�An attempt was made to attach to a device that was already attached to another device.

lObject Path Component was not a directory object.

h{Path Not Found}

The path %hs does not exist.

lObject Path Component was not a directory object.

h{Data Overrun}

A data overrun error occurred.

\{Data Late}

A data late error occurred.

�{Data Error}

An error in reading or writing data occurred.

�{Bad CRC}

A cyclic redundancy check (CRC) checksum error occurred.

�{Section Too Large}

The specified section is too big to map the file.

TThe NtConnectPort request is refused.

�The type of port handle is invalid for the operation requested.

�A file cannot be opened because the share access flags are incompatible.

pInsufficient quota exists to complete the operation

dThe specified page protection was not valid.

�An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.

�An attempt was made to release a semaphore such that its maximum count would have been exceeded.

TAn attempt to set a process's DebugPort or ExceptionPort was made, but a port already exists in the process or an attempt to set a file's CompletionPort made, but a port was already set in the file or an attempt to set an ALPC port's associated completion port was made, but it is already set.

�An attempt was made to query image information on a section which does not map an image.

�An attempt was made to suspend a thread whose suspend count was at its maximum.

�An attempt was made to access a thread that has begun termination.

�An attempt was made to set the working set limit to an invalid value (minimum greater than maximum, etc).

�A section was created to map a file which is not compatible to an already existing section which maps the same file.

�A view to a section specifies a protection which is incompatible with the initial view's protection.

�An operation involving EAs failed because the file system does not support EAs.

pAn EA operation failed because EA set is too large.

�An EA operation failed because the name or EA index is invalid.

lThe file for which EAs were requested has no EAs.

PThe EA is corrupt and non-readable.

�A requested read/write cannot be granted due to a conflicting file lock.

�A requested file lock cannot be granted due to other existing locks.

�A non close operation has been requested of a file object with a delete pending.

�An attempt was made to set the control attribute on a file. This attribute is not supported in the target file system.

4Indicates a revision number encountered or specified is not one known by the service. It may be a more recent revision than the service is aware of.

hIndicates two revision levels are incompatible.

�Indicates a particular Security ID may not be assigned as the owner of an object.

�Indicates a particular Security ID may not be assigned as the primary group of an object.

�An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.

XA mandatory group may not be disabled.

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.

�A specified logon session does not exist. It may already have been terminated.

TA specified privilege does not exist.

hA required privilege is not held by the client.

|The name provided is not a properly formed account name.

TThe specified account already exists.

TThe specified account does not exist.

PThe specified group already exists.

PThe specified group does not exist.

0The specified user account is already in the specified group account. Also used to indicate a group cannot be deleted because it contains a member.

�The specified user account is not a member of the specified group account.

�Indicates the requested operation would disable, delete or could prevent logon for an administration account.

This is not allowed to prevent creating a situation in which the system cannot be administrated.

When trying to update a password, this return status indicates that the value provided as the current password is not correct.

HWhen trying to update a password, this return status indicates that the value provided for the new password contains values that are not allowed in passwords.

LWhen trying to update a password, this status indicates that some password update rule has been violated. For example, the password may not meet length criteria.

�The attempted logon is invalid. This is either due to a bad username or authentication information.

|Indicates a referenced user name and authentication information are valid, but some user account restriction has prevented successful authentication (such as time-of-day restrictions).

�The user account has time restrictions and may not be logged onto at this time.

�The user account is restricted such that it may not be used to log on from the source workstation.

\The user account's password has expired.

�The referenced account is currently disabled and may not be logged on to.

�None of the information to be translated has been translated.

�The number of LUIDs requested may not be allocated with a single allocation.

hIndicates there are no more LUIDs to allocate.

�Indicates the sub-authority value is invalid for the particular use.

\Indicates the ACL structure is not valid.

\Indicates the SID structure is not valid.

|Indicates the SECURITY_DESCRIPTOR structure is not valid.

�Indicates the specified procedure address cannot be found in the DLL.

�{Bad Image}

%hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x%08lx.

tAn attempt was made to reference a token that doesn't exist.

This is typically done by referencing the token associated with a thread when the thread is not impersonating a client.

�Indicates that an attempt to build either an inherited ACL or ACE was not successful.

This can be caused by a number of things. One of the more probable causes is the replacement of a CreatorId with an SID that didn't fit into the ACE or ACL.

pThe range specified in NtUnlockFile was not locked.

0An operation failed because the disk was full.

If this is a thinly provisioned volume the physical storage backing this volume has been exhausted.

�The GUID allocation server is [already] disabled at the moment.

�The GUID allocation server is [already] enabled at the moment.

�Too many GUIDs were requested from the allocation server at once.

�The GUIDs could not be allocated because the Authority Agent was exhausted.

�The value provided was an invalid value for an identifier authority.

�There are no more authority agent values available for the given identifier authority value.

`An invalid volume label has been specified.

XA mapped section could not be extended.

tSpecified section to flush does not map a data file.

�Indicates the specified image file did not contain a resource section.

�Indicates the specified resource type cannot be found in the image file.

�Indicates the specified resource name cannot be found in the image file.

P{EXCEPTION}

Array bounds exceeded.

d{EXCEPTION}

Floating-point denormal operand.

d{EXCEPTION}

Floating-point division by zero.

`{EXCEPTION}

Floating-point inexact result.

h{EXCEPTION}

Floating-point invalid operation.

T{EXCEPTION}

Floating-point overflow.

\{EXCEPTION}

Floating-point stack check.

X{EXCEPTION}

Floating-point underflow.

X{EXCEPTION}

Integer division by zero.

H{EXCEPTION}

Integer overflow.

T{EXCEPTION}

Privileged instruction.

�An attempt was made to install more paging files than the system supports.

�The volume for a file has been externally altered such that the opened file is no longer valid.

When a block of memory is allotted for future updates, such as the memory allocated to hold discretionary access control and primary group information, successive updates may exceed the amount of memory originally allotted.

Since quota may already have been charged to several processes which have handles to the object, it is not reasonable to alter the size of the allocated memory.

Instead, a request that requires more memory than has been allotted must fail and the STATUS_ALLOTED_SPACE_EXCEEDED error returned.

|Insufficient system resources exist to complete the API.

�An attempt has been made to open a DFS exit path control file.

<STATUS_DEVICE_DATA_ERROR

@STATUS_DEVICE_NOT_CONNECTED

@STATUS_DEVICE_POWER_FAILURE

�Virtual memory cannot be freed as base address is not the base of the region and a region size of zero was specified.

�An attempt was made to free virtual memory which is not allocated.

�The working set is not big enough to allow the requested pages to be locked.

<{Write Protect Error}

The disk cannot be written to because it is write protected. Please remove the write protection from the volume %hs in drive %hs.

\{Drive Not Ready}

The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed.

�The specified attributes are invalid, or incompatible with the attributes for the group as a whole.

�A specified impersonation level is invalid.

Also used to indicate a required impersonation level was not provided.

�An attempt was made to open an Anonymous level token.

Anonymous tokens may not be opened.

xThe validation information class requested was invalid.

�The type of a token object is inappropriate for its attempted use.

$An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references.

xThe maximum named pipe instance count has been reached.

�An instance of a named pipe cannot be found in the listening state.

|The named pipe is not in the connected or closing state.

The specified pipe is set to complete operations and there are current I/O operations queued so it cannot be changed to queue operations.

�The specified handle is not open to the server end of the named pipe.

xThe specified named pipe is in the disconnected state.

lThe specified named pipe is in the closing state.

pThe specified named pipe is in the connected state.

pThe specified named pipe is in the listening state.

lThe specified named pipe is not in message mode.

�{Device Timeout}

The specified I/O operation on %hs was not completed before the time-out period expired.

xThe specified file has been closed by another process.

8Profiling not started.

8Profiling not stopped.

�The passed ACL did not contain the minimum required information.

The file that was specified as a target is a directory and the caller specified that it could be anything but a directory.

DThe request is not supported.

XThis remote computer is not listening.

XA duplicate name exists on the network.

PThe network path cannot be located.

4The network is busy.

@This device does not exist.

lThe network BIOS command limit has been reached.

`An I/O adapter hardware error has occurred.

PThe network responded incorrectly.

TAn unexpected network error occurred.

TThe remote adapter is not compatible.

@The printer queue is full.

�Space to store the file waiting to be printed is not available on the server.

`The requested print file has been canceled.

DThe network name was deleted.

<Network access is denied.

${Incorrect Network Resource Type}

The specified device type (LPT, for example) conflicts with the actual device type on the remote resource.

�{Network Name Not Found}

The specified share name cannot be found on the remote server.

�The name limit for the local computer network adapter card was exceeded.

dThe network BIOS session limit was exceeded.

\File sharing has been temporarily paused.

(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.

lPrint or disk redirection is temporarily paused.

HA network data fault occurred.

�The number of active profiling objects is at the maximum and no more may be started.

{Incorrect Volume}

The target file of a rename request is located on a different device than the source of the rename request.

�The file specified has been renamed and thus cannot be modified.

{Network Request Timeout}

The session with a remote server has been disconnected because the time-out interval for a request has expired.

�Indicates an attempt was made to operate on the security of an object that does not have security associated with it.

�Used to indicate that an operation cannot continue without blocking for I/O.

�Used to indicate that a read operation was done on an empty pipe.

$Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.

<Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process.

�Indicates the Sam Server was in the wrong state to perform the desired operation.

�Indicates the Domain was in the wrong state to perform the desired operation.

�This operation is only allowed for the Primary Domain Controller of the domain.

PThe specified Domain did not exist.

TThe specified Domain already exists.

�An attempt was made to exceed the limit on the number of domains per server for this release.

tError status returned when oplock request is denied.

�Error status returned when an invalid oplock acknowledgment is received by a file system.

(This error indicates that the requested operation cannot be completed due to a catastrophic media failure or on-disk data structure corruption.

@An internal error occurred.

Indicates generic access types were contained in an access mask which should already be mapped to non-generic access types.

�Indicates a security descriptor is not in the necessary format (absolute or self-relative).

XAn access to a user buffer failed at an "expected" point in time. This code is defined since the caller does not want to accept STATUS_ACCESS_VIOLATION in its filter.

�If an I/O error is returned which is not defined in the standard FsRtl filter, it is converted to the following error which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception.

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.

The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process.

�An attempt has been made to start a new session manager or LSA logon session with an ID that is already in use.

�An invalid parameter was passed to a service or function as the first argument.

�An invalid parameter was passed to a service or function as the second argument.

�An invalid parameter was passed to a service or function as the third argument.

�An invalid parameter was passed to a service or function as the fourth argument.

�An invalid parameter was passed to a service or function as the fifth argument.

�An invalid parameter was passed to a service or function as the sixth argument.

�An invalid parameter was passed to a service or function as the seventh argument.

�An invalid parameter was passed to a service or function as the eighth argument.

�An invalid parameter was passed to a service or function as the ninth argument.

�An invalid parameter was passed to a service or function as the tenth argument.

�An invalid parameter was passed to a service or function as the eleventh argument.

�An invalid parameter was passed to a service or function as the twelfth argument.

�An attempt was made to access a network file, but the network software was not yet started.

�An attempt was made to start the redirector, but the redirector has already been started.

lA new guard page for the stack cannot be created.

hA specified authentication package is unknown.

�A malformed function table was encountered during an unwind operation.

�Indicates the specified environment variable name was not found in the specified environment block.

�Indicates that the directory trying to be deleted is not empty.

�{Corrupt File}

The file or directory %hs is corrupt and unreadable.

Please run the Chkdsk utility.

`A requested opened file is not a directory.

�The logon session is not in a state that is consistent with the requested operation.

hAn internal LSA error has occurred. An authentication package has requested the creation of a Logon Session but the ID of an already existing Logon Session has been specified.

|A specified name string is too long for its intended use.

XThe user attempted to force close the files on a redirected drive, but there were opened files on the drive, and the user did not specify a sufficient level of force.

dThe user attempted to force close the files on a redirected drive, but there were opened directories on the drive, and the user did not specify a sufficient level of force.

�RtlFindMessage could not locate the requested message ID in the message table resource.

lAn attempt was made to access an exiting process.

�Indicates an invalid value has been provided for the LogonType requested.

tIndicates 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.

�Indicates that an attempt has been made to impersonate via a named pipe that has not yet been read from.

tIndicates that the specified image is already loaded.

<STATUS_ABIOS_NOT_PRESENT

@STATUS_ABIOS_LID_NOT_EXIST

HSTATUS_ABIOS_LID_ALREADY_OWNED

@STATUS_ABIOS_NOT_LID_OWNER

DSTATUS_ABIOS_INVALID_COMMAND

<STATUS_ABIOS_INVALID_LID

PSTATUS_ABIOS_SELECTOR_NOT_AVAILABLE

DSTATUS_ABIOS_INVALID_SELECTOR

�Indicates that an attempt was made to change the size of the LDT for a process that has no LDT.

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.

�Indicates that the starting value for the LDT information was not an integral multiple of the selector size.

�Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors.

�The specified image file did not have the correct format. It appears to be NE format.

LIndicates that the transaction state of a registry sub-tree is incompatible with the requested operation. For example, a request has been made to start a new transaction with one already in progress, or a request has been made to apply a transaction when one is not currently in progress.

�Indicates an error has occurred during a registry transaction commit. The database has been left in an unknown, but probably inconsistent, state. The state of the registry transaction is left as COMMITTING.

�An attempt was made to map a file of size zero with the maximum size specified as zero.

Too many files are opened on a remote server.

This error should only be returned by the Windows redirector on a remote drive.

DThe I/O request was canceled.

�An attempt has been made to remove a file or directory that cannot be deleted.

�Indicates a name specified as a remote computer name is syntactically invalid.

�An I/O request other than close was performed on a file after it has been deleted, which can only happen to a request which did not complete before the last handle was closed via NtClose.

dIndicates an operation has been attempted on a built-in (special) SAM account which is incompatible with built-in accounts. For example, built-in accounts cannot be deleted.

�The operation requested may not be performed on the specified group because it is a built-in special group.

�The operation requested may not be performed on the specified user because it is a built-in special user.

�Indicates a member cannot be removed from a group because the group is currently the member's primary group.

An I/O request other than close and several other special case operations was attempted using a file object that had already been closed.

pIndicates 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.

An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified.

TAn attempt was made to establish a token for use as a primary token but the token is already in use. A token can only be the primary token of one process at a time.

DPage file quota was exceeded.

�{Out of Virtual Memory}

Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

�The specified image file did not have the correct format, it appears to be LE format.

�The specified image file did not have the correct format, it did not have an initial MZ.

�The specified image file did not have the correct format, it did not have a proper e_lfarlc in the MZ header.

�The specified image file did not have the correct format, it appears to be a 16-bit Windows image.

The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role.

$The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount.

DThe SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required.

�The code execution cannot proceed because %hs was not found. Reinstalling the program may fix this problem.

�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.

�{Privilege Failed}

The I/O permissions for the process could not be changed.

�{Ordinal Not Found}

The ordinal %ld could not be located in the dynamic link library %hs.

�{Entry Point Not Found}

The procedure entry point %hs could not be located in the dynamic link library %hs.

�{Application Exit by CTRL+C}

The application terminated as a result of a CTRL+C.

0{Virtual Circuit Closed}

The network transport on your computer has closed a network connection. There may or may not be I/O requests outstanding.

8{Virtual Circuit Closed}

The network transport on a remote computer has closed a network connection. There may or may not be I/O requests outstanding.

�{Insufficient Resources on Remote Computer}

The remote computer has insufficient resources to complete the network request. For instance, there may not be enough memory available on the remote computer to carry out the request at this time.

�{Virtual Circuit Closed}

An existing connection (virtual circuit) has been broken at the remote computer. There is probably something wrong with the network software protocol or the network hardware on the remote computer.

\{Virtual Circuit Closed}

The network transport on your computer has closed a network connection because it had to wait too long for a response from the remote computer.

|The connection handle given to the transport was invalid.

xThe address handle given to the transport was invalid.

{DLL Initialization Failed}

Initialization of the dynamic link library %hs failed. The process is terminating abnormally.

�{Missing System File}

The required system file %hs is bad or missing.

�{Application Error}

The exception %s (0x%08lx) occurred in the application at location 0x%p.

�{Application Error}

The application was unable to start correctly (0x%lx). Click OK to close the application.

�{Unable to Create Paging File}

The creation of the paging file %hs failed (%lx). The requested size was %ld.

�{No Paging File Specified}

No paging file was specified in the system configuration.

�{Incorrect System Call Level}

An invalid level was passed into the specified system call.

�{Incorrect Password to LAN Manager Server}

You specified an incorrect password to a LAN Manager 2.x or MS-NET server.

�{EXCEPTION}

A real-mode application issued a floating-point instruction and floating-point hardware is not present.

�The pipe operation has failed because the other end of the pipe has been closed.

�{The Registry Is Corrupt}

The structure of one of the files that contains Registry data is corrupt, or the image of the file in memory is corrupt, or the file could not be recovered because the alternate copy or log was absent or corrupt.

�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.

\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.

@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 corrupt.

�No serial device was successfully initialized. The serial driver will unload.

\The specified local group does not exist.

|The specified account name is not a member of the group.

�The specified account name is already a member of the group.

\The specified local group already exists.

�A requested type of logon (e.g., Interactive, Network, Service) is not granted by the target system's local security policy.

Please ask the system administrator to grant the necessary form of logon.

�The maximum number of secrets that may be stored in a single system has been exceeded. The length and number of secrets is limited to satisfy United States State Department export restrictions.

TThe length of a secret exceeds the maximum length allowed. The length and number of secrets is limited to satisfy United States State Department export restrictions.

�The Local Security Authority (LSA) database contains an internal inconsistency.

�The requested operation cannot be performed in fullscreen mode.

�During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security ids to incorporate into the security context.

tA user has requested a type of logon (e.g., interactive or network) that has not been granted. An administrator has control over who may logon interactively and through the network.

The system has attempted to load or restore a file into the registry, and the specified file is not in the format of a registry file.

(An attempt was made to change a user password in the security account manager without providing the necessary Windows cross-encrypted password.

lA Windows Server has an incorrect configuration.

pAn attempt was made to explicitly access the secondary copy of information via a device control to the Fault Tolerance driver and the secondary copy is not present in the system.

A configuration registry node representing a driver service entry was ill-formed and did not contain required value entries.

�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.

�No mapping for the Unicode character exists in the target multi-byte code page.

�The Unicode character is not defined in the Unicode character set installed on the system.

xThe paging file cannot be created on a floppy diskette.

�{Floppy Disk Error}

While accessing a floppy disk, an ID address mark was not found.

d{Floppy Disk Error}

While accessing a floppy disk, the track address from the sector ID field was found to be different than the track address maintained by the controller.

�{Floppy Disk Error}

The floppy disk controller reported an error that is not recognized by the floppy disk driver.

�{Floppy Disk Error}

While accessing a floppy-disk, the controller returned inconsistent results via its registers.

�{Hard Disk Error}

While accessing the hard disk, a recalibrate operation failed, even after retries.

�{Hard Disk Error}

While accessing the hard disk, a disk operation failed even after retries.

�{Hard Disk Error}

While accessing the hard disk, a disk controller reset was needed, but even that failed.

TAn attempt was made to open a device that was sharing an IRQ with other devices.

At least one other device that uses that IRQ was already opened.

Two concurrent opens of devices that share an IRQ and only work via interrupts is not supported for the particular bus type that the devices use.

�{FT Orphaning}

A disk that is part of a fault-tolerant volume can no longer be accessed.

�The system bios failed to connect a system interrupt to the device or bus for which the device is connected.

HTape could not be partitioned.

�When accessing a new tape of a multivolume partition, the current blocksize is incorrect.

�Tape partition information could not be found when loading a tape.

lAttempt to lock the eject media mechanism fails.

0Unload media fails.

PPhysical end of tape was detected.

�{No Media}

There is no media in the drive. Please insert media into drive %hs.

�A member could not be added to or removed from the local group because the member does not exist.

�A new member could not be added to a local group because the member has the wrong account type.

�Illegal operation attempted on a registry key which has been marked for deletion.

�System could not allocate required space in a registry log.

PToo many Sids have been specified.

An attempt was made to change a user password in the security account manager without providing the necessary LM cross-encrypted password.

�An attempt was made to create a symbolic link in a registry key that already has subkeys or values.

�An attempt was made to create a Stable subkey under a Volatile parent key.

�The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect.

�An error was detected between two drivers or within an I/O driver.

�The device is not in a valid state to perform this request.

TThe I/O device reported an I/O error.

�A protocol error was detected between the driver and the device.

�This operation is only allowed for the Primary Domain Controller of the domain.

|Log file space is insufficient to support this operation.

�A write operation was attempted to a volume after it was dismounted.

�The workstation does not have a trust secret for the primary domain in the local LSA database.

�The SAM database on the Windows Server does not have a computer account for this workstation trust relationship.

�The logon request failed because the trust relationship between the primary domain and the trusted domain failed.

�The logon request failed because the trust relationship between this workstation and the primary domain failed.

LThe Eventlog log file is corrupt.

�No Eventlog log file could be opened. The Eventlog service did not start.

�The network logon failed. This may be because the validation authority can't be reached.

�An attempt was made to acquire a mutant such that its maximum count would have been exceeded.

�An attempt was made to logon, but the netlogon service was not started.

HThe user's account has expired.

\{EXCEPTION}

Possible deadlock condition.

�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.

An attempt was made to establish a session to a network server, but there are already too many sessions established to that server.

XThe log file has changed between reads.

The account used is an Interdomain Trust account. Use your global user account or local user account to access this server.

�The account used is a Computer Account. Use your global user account or local user account to access this server.

�The account used is an Server Trust account. Use your global user account or local user account to access this server.

�The name or SID of the domain specified is inconsistent with the trust information for that domain.

�A volume has been accessed for which a file system driver is required that has not yet been loaded.

�Indicates that the specified image is already loaded as a DLL.

�Short name settings may not be changed on this volume due to the global registry setting.

`Short names are not enabled on this volume.

�The security stream for the given volume is in an inconsistent state.

Please run CHKDSK on the volume.

�A requested file lock operation cannot be processed due to an invalid byte range.

�{Invalid ACE Condition}

The specified access control entry (ACE) contains an invalid condition.

�The subsystem needed to support the image type is not present.

�{Invalid ACE Condition}

The specified file already has a notification GUID associated with it.

xAn invalid exception handler routine has been detected.

pDuplicate privileges were specified for the token.

�Requested action not allowed on a file system internal file.

dA portion of the file system requires repair.

`Quota support is not enabled on the system.

�The operation failed because the application is not part of an application package.

pFile metadata optimization is already in progress.

HThe objects are not identical.

�The process has terminated because it could not allocate additional memory.

LThe process is not part of a job.

XThe specified CPU Set IDs are invalid.

`The device reported an invalid data error.

dThe device reported an unaligned write error.

xAn invalid address was found on the control flow stack.

�The Security Account Manager blocked the use of a weak Windows Hello for Business key.

XMultiple mappings to shared resource(s) on a server, using more than one transport, are not allowed. Use a single transport for all mappings to a server and try again.

�Multiple mappings to shared resource(s) on a server, using different certificate validation preferences, are not allowed. Use the same preference for all mappings to a server and try again.

�A remote open failed because the network open restrictions were not satisfied.

�There is no user session key for the specified logon session.

\The remote user session has been deleted.

�Indicates the specified resource language ID cannot be found in the

image file.

�Insufficient server resources exist to complete the request.

�The size of the buffer is invalid for the specified operation.

�The transport rejected the network address specified as invalid.

�The transport rejected the network address specified due to an invalid use of a wildcard.

�The transport address could not be opened because all the available addresses are in use.

�The transport address could not be opened because it already exists.

TThe transport address is now closed.

dThe transport connection is now disconnected.

\The transport connection has been reset.

|The transport cannot dynamically acquire any more nodes.

dThe transport aborted a pending transaction.

|The transport timed out a request waiting for a response.

�The transport did not receive a release for a pending response.

�The transport did not find a transaction matching the specific token.

�The transport had previously responded to a transaction request.

�The transport does not recognized the transaction request identifier specified.

�The transport does not recognize the transaction request type specified.

�The transport can only process the specified request on the server side of a session.

�The transport can only process the specified request on the client side of a session.

{Registry File Failure}

The registry cannot load the hive (file):

%hs

or its log or alternate.

It is corrupt, absent, or not writable.

�{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.

${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.

�{Data Not Accepted}

The TDI client could not handle the data received during an indication.

�{Unable to Retrieve Browser Server List}

The list of servers for this workgroup is not currently available.

HNTVDM encountered a hard error.

�{Cancel Timeout}

The driver %hs failed to complete a cancelled I/O request in the allotted time.

P{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.

�{Mapped View Alignment Incorrect}

An attempt was made to map a view of a file, but either the specified base address or the offset into the file were not aligned on the proper allocation granularity.

�{Bad Image Checksum}

The image %hs is possibly corrupt. The header checksum does not match the computed checksum.

�{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.

@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.

xThe user's password must be changed before signing in.

<The object was not found.

LThe stream is not a tiny stream.

DA transaction recover failed.

xThe request must be handled by the stack overflow code.

@A consistency check failed.

�The attempt to insert the ID in the index failed because the ID is already in the index.

�The attempt to set the object's ID failed because the object already has an ID.

�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.

LThe request needs to be retried.

$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.

�The bucket array must be grown. Retry transaction after doing so.

|The property set specified does not exist on the object.

pThe user/kernel marshalling buffer has overflowed.

tThe supplied variant structure contains invalid data.

pCould not find a domain controller for this domain.

The user account has been automatically locked because too many invalid logon attempts or password change attempts have been requested.

�NtClose was called on a handle that was protected from close via NtSetInformationObject.

�The transport connection attempt was refused by the remote system.

hThe transport connection was gracefully closed.

�The transport endpoint already has an address associated with it.

�An address has not yet been associated with the transport endpoint.

�An operation was attempted on a nonexistent transport connection.

�An invalid operation was attempted on an active transport connection.

tThe remote network is not reachable by the transport.

tThe remote system is not reachable by the transport.

�The remote system does not support the transport protocol.

�No service is operating at the destination port of the transport on the remote system.

<The request was aborted.

|The transport connection was aborted by the local system.

hThe specified buffer contains ill-formed data.

�The requested operation cannot be performed on a file with a user mapped section open.

�{Audit Failed}

An attempt to generate a security audit failed.

�The timer resolution was not previously set by the current process.

A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached.

�Attempting to login during an unauthorized time of day for this account.

|The account is not authorized to login from this station.

h{UP/MP Image Mismatch}

The image %hs has been modified for use on a uniprocessor system, but you are running it on a multiprocessor machine.

Please reinstall the image file.

|There is insufficient account information to log you on.

�{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.

�{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.

�The server received the messages but did not send a reply.

�There is an IP address conflict with another system on the network

@{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.

�The contacted server does not support the indicated part of the DFS namespace.

�A callback return system service cannot be executed when no callback is active.

�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.

�The password provided is too short to meet the policy of your user account. Please choose a longer password.

�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.

�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.

�You have attempted to load a legacy device driver while its device instance had been disabled.

lThe specified compression format is unsupported.

|The specified hardware profile configuration is invalid.

�The specified Plug and Play registry device path is invalid.

�{Driver Entry Point Not Found}

The %hs device driver could not locate the ordinal %ld in driver %hs.

�{Driver Entry Point Not Found}

The %hs device driver could not locate the entry point %hs in driver %hs.

{Application Error}

The application attempted to release a resource it did not own. Click OK to terminate the application.

�An attempt was made to create more links on a file than the file system supports.

�The specified quota list is internally inconsistent with its descriptor.

|The specified file has been relocated to offline storage.

({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.

@{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.

t{License Violation}

The system has detected tampering with your registered product type. This is a violation of your software license. Tampering with product type is not permitted.

�{DLL Initialization Failed}

The application failed to initialize because the window station is shutting down.

�{Unable to Load Device Driver}

%hs device driver could not be loaded.

Error Status was 0x%x

`DFS is unavailable on the contacted server.

�An operation was attempted to a volume after it was dismounted.

�An internal error occurred in the Win32 x86 emulation subsystem.

|Win32 x86 emulation subsystem Floating-point stack check.

�The validation process needs to continue on to the next step.

xThere was no match for the specified key in the index.

�There are no more matches for the current index enumeration.

dThe file or directory is not a reparse point.

�The Windows I/O reparse tag passed for the reparse point is invalid.

�The Windows I/O reparse tag does not match the one present in the reparse point.

xThe user data passed for the reparse point is invalid.

�The layered file system driver for this IO tag did not handle it when needed.

�The password provided is too long to meet the policy of your user account. Please choose a shorter password.

hAn application-internal exception has occurred.

�The symbolic link could not be resolved even though the initial file name is valid.

LThe directory is a reparse point.

�The range could not be added to the range list because of a conflict.

�The specified medium changer source element contains no media.

�The specified medium changer destination element already contains media.

tThe specified medium changer element does not exist.

�The specified element is contained within a magazine that is no longer present.

�The device requires reinitialization due to hardware errors.

PThe file encryption attempt failed.

PThe file decryption attempt failed.

|The specified range could not be found in the range list.

�There is no encryption recovery policy configured for this system.

�The required encryption driver is not loaded for this system.

�The file was encrypted with a different encryption driver than is currently loaded.

`There are no EFS keys defined for the user.

TThe specified file is not encrypted.

�The specified file is not in the defined EFS export format.

�The specified file is encrypted and the user does not have the ability to decrypt it.

�The guid passed was not recognized as valid by a WMI data provider.

�The instance name passed was not recognized as valid by a WMI data provider.

�The data item id passed was not recognized as valid by a WMI data provider.

�The WMI request could not be completed and should be retried.

�The policy object is shared and can only be modified at the root

hThe policy object does not exist when it should

tThe requested policy information only lives in the Ds

pThe volume must be upgraded to enable this feature

�The remote storage service is not operational at this time.

tThe remote storage service encountered a media error.

pThe tracking (workstation) service is not running.

�The server process is running under a SID different than that required by client.

�The specified directory service attribute or value does not exist.

�The attribute syntax specified to the directory service is invalid.

�The attribute type specified to the directory service is not defined.

�The specified directory service attribute or value already exists.

HThe directory service is busy.

XThe directory service is not available.

�The directory service was unable to allocate a relative identifier.

�The directory service has exhausted the pool of relative identifiers.

The requested operation could not be performed because the directory service is not the master for that type of operation.

�The directory service was unable to initialize the subsystem that allocates relative identifiers.

�The requested operation did not satisfy one or more constraints associated with the class of the object.

�The directory service can perform the requested operation only on a leaf object.

�The directory service cannot perform the requested operation on the Relatively Defined Name (RDN) attribute of an object.

�The directory service detected an attempt to modify the object class of an object.

�An error occurred while performing a cross domain move operation.

dUnable to Contact the Global Catalog Server.

�The requested operation requires a directory service, and none was available.

�The reparse attribute cannot be set as it is incompatible with an existing attribute.

pA group marked use for deny only cannot be enabled.

d{EXCEPTION}

Multiple floating point faults.

`{EXCEPTION}

Multiple floating point traps.

DThe device has been removed.

`The volume change journal is being deleted.

\The volume change journal is not active.

\The requested interface is not supported.

�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.

tA directory service resource limit has been exceeded.

{System Standby Failed}

The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode.

�Mutual Authentication failed. The server's password is out of date at the domain controller.

�The system file %1 has become corrupt and has been replaced.

�{EXCEPTION}

Alignment Error

A datatype misalignment error was detected in a load or store instruction.

dThe WMI data item or data block is read only.

tThe WMI data item or data block could not be changed.

�{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.

�{EXCEPTION}

A NaT value is consumed on a non speculative instruction.

�The medium changer's transport element contains media, which is causing the operation to fail.

�Security Accounts Manager initialization failed because of the following error:

%hs

Error Status: 0x%x.

Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.

�This operation is supported only when you are connected to the server.

�Only an administrator can modify the membership list of an administrative group.

xA device was removed so enumeration must be restarted.

tThe journal entry has been deleted from the journal.

�Cannot change the primary group ID of a domain controller account.

,{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.

XDevice will not start without a reboot.

xCurrent device power state cannot support this request.

TThe specified group type is invalid.

�In mixed domain no nesting of global group if group is security enabled.

�In mixed domain, cannot nest local groups with other local groups, if the group is security enabled.

tA global group cannot have a local group as a member.

|A global group cannot have a universal group as a member.

|A universal group cannot have a local group as a member.

lA global group cannot have a cross domain member.

�A local group cannot have another cross domain local group as a member.

�Cannot change to security disabled group because of having primary members in this group.

�The WMI operation is not supported by the data block or method.

�There is not enough power to complete the requested operation.

|Security Account Manager needs to get the boot password.

�Security Account Manager needs to get the boot key from floppy disk.

HDirectory Service cannot start.

�Directory Services could not start because of the following error:

%hs

Error Status: 0x%x.

Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.

�Security Accounts Manager initialization failed because of the following error:

%hs

Error Status: 0x%x.

Please click OK to shutdown this system and reboot into Safe Mode, check the event log for more detailed information.

�The requested operation can be performed only on a global catalog server.

�A local group can only be a member of other local groups in the same domain.

�Foreign security principals cannot be members of universal groups.

�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.

HSTATUS_MULTIPLE_FAULT_VIOLATION

|This operation cannot be performed on the current domain.

\The directory or file cannot be created.

hThe system is in the process of shutting down.

�Directory Services could not start because of the following error:

%hs

Error Status: 0x%x.

Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.

�Security Accounts Manager initialization failed because of the following error:

%hs

Error Status: 0x%x.

Please click OK to shutdown the system. You can use the recovery console to diagnose the system further.

�A security context was deleted before the context was completed. This is considered a logon failure.

�The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply.

XAn object ID was not found in the file.

�Unable to accomplish the requested task because the local machine does not have any IP addresses.

�The supplied credential handle does not match the credential associated with the security context.

�The crypto system or checksum function is invalid because a required function is unavailable.

|The number of maximum ticket referrals has been exceeded.

�The local machine must be a Kerberos KDC (domain controller) and it is not.

�The other end of the security negotiation is requires strong crypto but it is not supported on the local machine.

tThe KDC reply contained more than one principal name.

�Expected to find PA data for a hint of what etype to use, but it was not found.

(The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator.

dSmartcard logon is required and was not used.

XAn invalid request was sent to the KDC.

�The KDC was unable to generate a referral for the service requested.

�The encryption type requested is not supported by the KDC.

LA system shutdown is in progress.

TThe server machine is shutting down.

�This operation is not supported on a computer running Windows Server 2003 for Small Business Server

PThe WMI GUID is no longer available

�Collection or events for the WMI GUID is already disabled.

|Collection or events for the WMI GUID is already enabled.

�The Master File Table on the volume is too fragmented to complete this operation.

<Copy protection failure.

xCopy protection error - DVD CSS Authentication failed.

�Copy protection error - The given sector does not contain a valid key.

|Copy protection error - DVD session key not established.

�Copy protection error - The read failed because the sector is encrypted.

�Copy protection error - The given DVD's region does not correspond to the

region setting of the drive.

�Copy protection error - The drive's region setting may be permanent.

�EAS policy requires that the user change their password before this operation can be performed.

0An administrator has restricted sign in. To sign in, make sure your device is connected to the Internet, and have your administrator sign in first.

,The Kerberos protocol encountered an error while validating the KDC certificate during logon. There is more information in the system event log.

�The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem.

�The target server does not have acceptable Kerberos credentials.

|The transport determined that the remote system is down.

�An unsupported preauthentication mechanism was presented to the Kerberos package.

�The encryption algorithm used on the source file needs a bigger key buffer than the one used on the destination file.

�An attempt to remove a process's DebugPort was made, but a port was not already associated with the process.

�Debugger Inactive: Windows may have been started without kernel debugging enabled.

�This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller.

pThe specified event is currently not being audited.

�The machine account was created pre-NT4. The account needs to be recreated.

�A account group cannot have a universal group as a member.

�The specified image file did not have the correct format, it appears to be a 32-bit Windows image.

�The specified image file did not have the correct format, it appears to be a 64-bit Windows image.

xClient's supplied SSPI channel bindings were incorrect.

�The client's session has expired, so the client must reauthenticate to continue accessing the remote resources.

�AppHelp dialog canceled thus preventing the application from starting.

dThe SID filtering operation removed all SIDs.

�The driver was not loaded because the system is booting into safe mode.

�Access to %1 has been restricted by your Administrator by the default software restriction policy level.

�Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3

�Access to %1 has been restricted by your Administrator by software publisher policy.

�Access to %1 has been restricted by your Administrator by policy rule %2.

�The driver was not loaded because it failed its initialization call.

PThe "%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.

LThe 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.

The device object parameter is either not a valid device object or is not attached to the volume specified by the file name.

�A Machine Check Error has occurred. Please check the system eventlog for additional information.

\Driver %2 has been blocked from loading.

tThere was error [%2] processing the driver database.

\System hive size has exceeded its limit.

�A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image.

�The local account store does not contain secret material for the specified account.

�Access to %1 has been restricted by your Administrator by policy rule %2.

�The system was not able to allocate enough memory to perform a stack switch.

@A heap has been corrupted.

lAn incorrect PIN was presented to the smart card

<The smart card is blocked

XNo PIN was presented to the smart card

8No smart card available

�The requested key container does not exist on the smart card

�The requested certificate does not exist on the smart card

PThe requested keyset does not exist

�A communication error with the smart card has been detected.

�The system cannot contact a domain controller to service the authentication request. Please try again later.

PThe smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log.

�An untrusted certificate authority was detected while processing the certificate used for authentication.

�The revocation status of the certificate used for authentication could not be determined.

�The client certificate used for authentication was not trusted.

�The smartcard certificate used for authentication has expired. Please

contact your system administrator.

�The driver could not be loaded because a previous version of the driver is still in memory.

�The smartcard provider could not perform the action since the context was acquired as silent.

�The current user's delegated trust creation quota has been exceeded.

�The total delegated trust creation quota has been exceeded.

�The current user's delegated trust deletion quota has been exceeded.

|The requested name already exists as a unique identifier.

�The requested object has a non-unique identifier and cannot be retrieved.

�The group cannot be converted due to attribute restrictions on the requested group type.

�{Volume Shadow Copy Service}

Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation.

dKerberos sub-protocol User2User is required.

XThe 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.

HThe Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user.

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.

TThe revocation status of the domain controller certificate used for authentication could not be determined. There is additional information in the system event log.

�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.

�The domain controller certificate used for logon has expired. There is additional information in the system event log.

The domain controller certificate used for logon has been revoked. There is additional information in the system event log.

�Data present in one of the parameters is more than the function can operate on.

�The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted.

�An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed.

LLogon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine.

(%hs is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator.

H{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.

�The Desktop heap encountered an error while allocating session memory. There is more information in the system event log.

|An invalid parameter was passed to a C runtime function.

lThe authentication failed since NTLM was blocked.

�The source object's SID already exists in destination forest.

�The domain name of the trusted domain already exists in the forest.

�The flat name of the trusted domain already exists in the forest.

\The User Principal Name (UPN) is invalid.

�An unhandled exception was encountered during a user callback.

PAn assertion failure has occurred.

�Application verifier has found an error in the current process.

�An exception has occurred in a user mode callback and the kernel callback frame should be removed.

4%2 has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

�Illegal operation attempted on a registry key which has already been unloaded.

\Compression is disabled for this volume.

�The requested operation could not be completed due to a file system limitation

�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.

�The implementation is not capable of performing the request.

�The requested operation is out of order with respect to other operations.

�An operation attempted to exceed an implementation-defined limit.

`The requested operation requires elevation.

dThe required security context does not exist.

�The PKU2U protocol encountered an error while attempting to utilize the associated certificates.

�The operation was attempted beyond the valid data length of the file.

�The attempted write operation encountered a write already in progress for some portion of the range.

�The page fault mappings changed in the middle of processing a fault so the operation must be retried.

�The attempt to purge this file from memory failed to purge some or all the data from memory.

hThe requested credential requires confirmation.

�The remote server sent an invalid response for a file being opened with Client Side Encryption.

�Client Side Encryption is not supported by the remote server even though it claims to support it.

�File is encrypted and should be opened in Client Side Encryption mode.

�A new encrypted file is being created and a $EFS needs to be provided.

xThe SMB client requested a CSE FSCTL on a non-CSE file.

�Indicates a particular Security ID may not be assigned as the label of an object.

�The process hosting the driver for this device has terminated.

$The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria.

dThe requested system device cannot be found.

\This boot application must be restarted.

�Insufficient NVRAM resources exist to complete the API. A reboot might be required.

LThe specified session is invalid.

dThe specified thread is already in a session.

\The specified thread is not in a session.

LThe specified weight is invalid.

<The operation was paused.

�No ranges for the specified operation were able to be processed.

|The physical resources of this disk have been exhausted.

�The application cannot be started. Try reinstalling the application to fix the problem.

�{Device Feature Not Supported}

The device does not support the command feature.

�{Source/Destination device unreachable}

The device is unreachable.

�{Invalid Proxy Data Token}

The token representing the data is invalid.

`The file server is temporarily unavailable.

TThe file is temporarily unavailable.

�{Device Insufficient Resources}

The target device has insufficient resources to complete the operation.

�The application cannot be started because it is currently updating.

�The specified copy of the requested data could not be read.

�The specified data could not be written to any of the copies.

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.

tThis object is not externally backed by any provider.

lThe external backing provider is not recognized.

dCompressing this object would not save space.

�A data integrity checksum error occurred. Data in the file stream is corrupt.

�An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation.

{LogicalBlockProvisioningReadZero Not Supported}

The target device does not support read returning zeros from trimmed/unmapped blocks.

{Maximum Segment Descriptors Exceeded}

The command specified a number of descriptors that exceeded the maximum supported by the device.

�{Alignment Violation}

The command specified a data offset that does not align to the device's granularity/alignment.

�{Invalid Field In Parameter List}

The command specified an invalid field in its parameter list.

�{Operation In Progress}

An operation is currently in progress with the device.

�{Invalid I_T Nexus}

An attempt was made to send down the command via an invalid path to the target device.

\Scrub is disabled on the specified file.

hThe storage device does not provide redundancy.

lAn operation is not supported on a resident file.

pAn operation is not supported on a compressed file.

dAn operation is not supported on a directory.

�{IO Operation Timeout}

The specified I/O operation failed to complete within the expected time period.

�An error in a system binary was detected. Try refreshing the PC to fix the problem.

xA corrupted CLR NGEN binary was detected on the system.

TThe share is temporarily unavailable.

�The target dll was not found because the apiset %hs is not hosted.

�The API set extension contains a host for a non-existent API set.

|The request failed due to a fatal device hardware error.

XThe specified firmware slot is invalid.

\The specified firmware image is invalid.

|The request failed due to a storage topology ID mismatch.

�The specified Windows Image (WIM) is not marked as bootable.

hThe operation was blocked by parental controls.

�The deployment operation failed because the specified application needs to be registered first.

�The requested operation failed due to quota operation is still in progress.

dThe callback function must be invoked inline.

�A file system block being referenced has already reached the maximum reference count and can't be referenced any further.

�The requested operation failed because the file stream is marked to disallow writes.

�Windows Information Protection policy does not allow access to this network resource.

�The requested operation failed with an architecture-specific failure code.

�There are no compatible drivers available for this device.

�The specified driver package cannot be found on the system.

�The driver package cannot find a required driver configuration.

�The driver configuration is incomplete for use with this device.

�The device requires a driver configuration with a function driver.

dThe device is pending further configuration.

�The device hint name buffer is too small to receive the remaining name.

XThe package is currently not available.

PThe device is in maintenance mode.

lThis operation is not supported on a DAX volume.

�The free space on the volume is too fragmented to complete this operation.

PThe volume has active DAX mappings.

XThe process creation has been blocked.

lThe storage device has lost data or persistence.

�An attempt was made to access a partition that has begun termination.

tAn 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.

�An attempt was made to access protected memory in violation of its secure access policy.

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.

hThe volume is not cluster aligned on the disk.

|No physically aligned free space was found on the volume.

�The APPX file can not be accessed because it is not encrypted as expected.

�A read or write of raw encrypted data cannot be performed because the file is not encrypted.

An invalid file offset in the encrypted data info block was passed for read or write operation of file's raw encrypted data.

An invalid offset and length combination in the encrypted data info was passed for read or write operation of file's raw encrypted data.

�An invalid parameter in the encrypted data info was passed for read or write operation of file's raw encrypted data.

�The specified data could not be read from any of the copies.

�A system patch could not be applied due to conflicting accesses to the system image.

dThe specified storage reserve ID is invalid.

dThe specified storage reserve does not exist.

dThe specified storage reserve already exists.

`The specified storage reserve is not empty.

TThis operation requires a DAX volume.

LThis stream is not DAX mappable.

�This directory contains entries whose names differ only in case.

�The file cannot be safely opened because it is not supported by this version of Windows.

lThis operation is not supported with BTT enabled.

�This operation cannot be performed because encryption is currently disabled.

�This encryption operation cannot be performed on filesystem metadata.

�Encryption cannot be cleared on this file/directory because it still has an encrypted attribute.

�The operation could not be completed due to one or more unsatisfied dependencies.

�The file cannot be opened because the path has a case-sensitive directory.

�The currently selected address translation mode is not supported.

�The path cannot be traversed because it contains an untrusted mount point.

�The volume contains paging, crash dump or other system critical files.

�The request cannot be completed as it requires modifying an immutable object.

�The specified copy of the requested data could not be read.

�This image cannot be loaded because it has already been loaded as a hot patch image.

�The storage stack returned STATUS_ACCESS_DENEID for the current operation.

�Insufficient Virtual Address resources to complete the operation.

�The specified operation is not supported while virtualization is enabled on the target object.

|The specified index is beyond the bounds of valid range.

�The patch is not currently registered for the corresponding base image.

PThe specified task name is invalid.

TThe specified task index is invalid.

hThe specified thread is already joining a task.

hA callback has requested to bypass native code.

�The Central Access Policy specified is not defined on the target machine.

�The Central Access Policy obtained from Active Directory is invalid.

�Unable to finish the requested operation because the specified process is not a GUI process.

�The device is not responding and cannot be safely removed.

|The specified Job already has a container assigned to it.

�The specified Job does not have a container assigned to it.

@The device is unresponsive.

�The object manager encountered a reparse point while retrieving an object.

�The requested attribute is not present on the specified file or directory.

PThis volume is not a tiered volume.

�This file is currently associated with a different stream id.

�The requested operation could not be completed because the specified job has children.

pThe specified object has already been initialized.

pThe specified enclave has not yet been terminated.

�An attempt was made to access an enclave that has begun termination.

TYou 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

`The volume must undergo garbage collection.

\Execution of the thread was interrupted.

`The target thread is not currently running.

�The negotiated session key does not meet the minimum length requirement.

�The file system encountered a metadata file with inconsistent data.

${Fail Fast Exception}

A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately.

�Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked.

�The operation was blocked as the process prohibits dynamic code generation.

�Windows cannot verify the digital signature for this file. The signing certificate for this file has expired.

The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard.

�The thread context could not be updated because this has been restricted for the process.

�An attempt to access another partition's private file/section was rejected.

<The ALPC port is closed.

pThe ALPC message requested is no longer available.

TThe ALPC message supplied is invalid.

PThe ALPC message has been canceled.

PInvalid recursive dispatch attempt.

�No receive buffer has been supplied in a synchronous request.

pThe connection port is used in an invalid context.

pThe ALPC port does not accept new request messages.

\The resource requested is already in use.

|The hardware has reported an uncorrectable memory error.

�Status 0x%08x was returned, waiting on handle 0x%x for wait 0x%p, in waiter 0x%p.

�After a callback to 0x%p(0x%p), a completion call to SetEvent(0x%p) failed with status 0x%08x.

�After a callback to 0x%p(0x%p), a completion call to ReleaseSemaphore(0x%p, %d) failed with status 0x%08x.

�After a callback to 0x%p(0x%p), a completion call to ReleaseMutex(%p) failed with status 0x%08x.

�After a callback to 0x%p(0x%p), an completion call to FreeLibrary(%p) failed with status 0x%08x.

�The threadpool 0x%p was released while a thread was posting a callback to 0x%p(0x%p) to it.

xA threadpool worker thread is impersonating a client, after a callback to 0x%p(0x%p).

This is unexpected, indicating that the callback is missing a call to revert the impersonation.

\A threadpool worker thread is impersonating a client, after executing an APC.

This is unexpected, indicating that the APC is missing a call to revert the impersonation.

�Either the target process, or the target thread's containing process, is a protected process.

�A Thread is getting dispatched with MCA EXCEPTION because of MCA.

tThe client certificate account mapping is not unique.

�The symbolic link cannot be followed because its type is disabled.

�Indicates that the specified string is not valid for IDN normalization.

�No mapping for the Unicode character exists in the target multi-byte code page.

dThe provided callback is already registered.

hThe provided context did not match the target.

lThe specified port already has a completion list.

xA threadpool worker thread enter a callback at thread base priority 0x%x and exited at priority 0x%x.

This is unexpected, indicating that the callback missed restoring the priority.

�An invalid thread, handle %p, is specified for this operation. Possibly, a threadpool worker thread was specified.

DA threadpool worker thread enter a callback, which left transaction state.

This is unexpected, indicating that the callback missed clearing the transaction.

@A threadpool worker thread enter a callback, which left the loader lock held.

This is unexpected, indicating that the callback missed releasing the lock.

DA threadpool worker thread enter a callback, which left with preferred languages set.

This is unexpected, indicating that the callback missed clearing them.

pA threadpool worker thread enter a callback, which left with background priorities set.

This is unexpected, indicating that the callback missed restoring the original priorities.

dA threadpool worker thread enter a callback at thread affinity %p and exited at affinity %p.

This is unexpected, indicating that the callback missed restoring the priority.

�The caller has exceeded the maximum number of handles that may be transmitted in

a single local procedure call.

�A write to executable memory occurred for a process that is managing such operations.

�A write to executable memory occurred from kernel mode for a process that is managing such operations.

�A write to executable memory occurred from kernel mode while attached to a process that is managing such operations.

�A write to executable memory was triggered cross-process to a process that is managing such operations.

�The attempted operation required self healing to be enabled.

�The Directory Service cannot perform the requested operation because a domain rename operation is in progress.

�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.

,The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator.

�The operation could not be completed due to bad clusters on disk.

�The operation could not be completed because the volume is dirty. Please run chkdsk and try again.

TThe volume repair was not successful.

�One of the volume corruption logs is full. Further corruptions that may be detected won't be logged.

8One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned.

�One of the volume corruption logs is unavailable for being operated on.

@One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned.

�One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions.

tOrphaned 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.

�The operation could not be completed because an instance of Proactive Scanner is currently running.

The read or write operation to an encrypted file could not be completed because the file has not been opened for data access.

�One of the volume corruption logs comes from a newer version of Windows and contains corruption records. The log will be emptied and reset to the current version, and the volume health state will be updated accordingly.

�This file is checked out or locked for editing by another user.

pThe file must be checked out before saving changes.

|The file type being saved or retrieved has been blocked.

�The file size exceeds the limit allowed and cannot be saved.

Access Denied. Before opening files in this location, you must first browse to the web site and select the option to login automatically.

�Operation did not complete successfully because the file contains a virus or potentially unwanted software.

�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.

�The resources required for this device conflict with the MCFG table.

<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.

Bad key.

Bad data.

0Key does not exist.

tAccess to the specified file handle has been revoked.

�The specified section is supported by direct map technology but the caller specifically does not want that.

�Enabling driver verification from volatile command is currently not supported when both CFG and IO are enabled.

�Removal of current driver verification is not supported from volatile command.

�Enabling driver verification is not supported in safe mode.

�Enabling driver verification is not supported from volatile mode in current system.

�The specified rule class (a.k.a. flag) is not supported from volatile mode.

�The specified driver is protected and volatile verification is currently not supported.

�Enabling driver verification is not supported for a driver with NMI callback(s) registered.

Volatile verification settings cannot be changed when verification is enabled from boot or DIF volatile verification is enabled.

�Verifier's internal data size exceeds the limit of live dump secondary data.

�Verification cannot start because an attempt to lock code or data section failed.

�DIF volatile verification is not supported for hotpatched driver.

dThe passed system DIF information is invalid.

dDIF volatile only supports on loaded drivers.

HCurrently no plugin is running.

�Currently running plugin must be removed before applying a new plugin.

pThe plugin is not allowed to run in volatile mode.

dOne or more DDI is not yet supported by DIF.

4WOW Assertion Error.

XThe cryptographic signature is invalid.

lThe cryptographic provider does not support HMAC.

�The computed authentication tag did not match the input authentication tag.

�The requested state transition is invalid and cannot be performed.

pThe supplied kernel information version is invalid.

lThe supplied PEP information version is invalid.

lAccess to the specified handle has been revoked.

�The file operation will result in the end of file being on a ghosted range.

Filesystem needs to release all the file resources and callback into Cc to drain pending section deletions, before retrying the operation.

@The IPSEC queue overflowed.

\The neighbor discovery queue overflowed.

hAn ICMP hop limit exceeded error was received.

pThe protocol is not installed on the local machine.

�An operation or data has been rejected while on the network fast path.

�{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.

�{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.

�{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.

pWindows was unable to parse the requested XML data.

�An error was encountered while processing an XML digital signature.

�Indicates that the caller made the connection request in the wrong routing compartment.

�Indicates that there was an AuthIP failure when attempting to connect to the remote host.

XOID mapped groups cannot have members.

PThe specified OID cannot be found.

�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.

�The local account policy modification request was rejected because the policy is controlled by a regional authority.

�The account is controlled by external policy and cannot be modified.

,The Local Administrator Password Solution password update operation failed because the legacy LAPS schema needs to be added to Active Directory.

,The Local Administrator Password Solution password update operation failed because the Windows LAPS schema needs to be added to Active Directory.

|The Local Administrator Password Solution encrypted password update operation failed because Active Directory is not yet running at the minimum required domain functional level (2016).

�Hash generation for the specified version and hash type is not enabled on server.

�The hash requests is not present or not up to date with the current file contents.

�The secondary interrupt controller instance that manages the specified interrupt is not registered.

�The information supplied by the GPIO client driver is invalid.

�The version specified by the GPIO client driver is not supported.

�The registration packet supplied by the GPIO client driver is not valid.

�The requested operation is not supported for the specified handle.

�The requested connect mode conflicts with an existing mode on one or more of the specified pins.

�The requested run level switch cannot be completed successfully since

one or more services refused to stop or restart.

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.

0The requested run level switch cannot be completed successfully since

one or more services will not stop or restart within the specified timeout.

�A run level switch agent did not respond within the specified timeout.

dA run level switch is currently in progress.

�This operation is only valid in the context of an app container.

�This functionality is not supported in the context of an app container.

�The length of the SID supplied is not a valid length for app container SIDs.

�Access to the specified resource has been denied for a less privileged app container.

�Access to the specified resource has been denied for an adminless system.

@Fast Cache data not found.

<Fast Cache data expired.

<Fast Cache data corrupt.

�Fast Cache data has exceeded its max size and cannot be updated.

�Fast Cache has been ReArmed and requires a reboot until it can be updated.

�The copy offload read operation is not supported by a filter.

�The copy offload write operation is not supported by a filter.

�The copy offload read operation is not supported for the file.

�The copy offload write operation is not supported for the file.

�The WOF driver encountered a corruption in WIM image's Header.

�The WOF driver encountered a corruption in WIM image's Resource Table.

�The WOF driver encountered a corruption in the compressed file's Resource Table.

DThe CimFS image is corrupted.

�The system does not support this version of the CimFS image.

�The provider that supports file system virtualization is temporarily unavailable.

�The metadata for file system virtualization is corrupt and unreadable.

�The provider that supports file system virtualization is too busy to complete this operation.

�The provider that supports file system virtualization is unknown.

�The virtualization operation is not allowed on the file in its current state.

`The cloud sync root metadata is corrupted.

XThe cloud file provider is not running.

pThe cloud file metadata is corrupt and unreadable.

TThe cloud file metadata is too large.

�The version of the cloud file property store is not supported.

DThe file is not a cloud file.

XThe file is not in sync with the cloud.

�The cloud sync root is already connected with another cloud sync provider.

�The operation is not supported by the cloud sync provider.

HThe cloud operation is invalid.

�The cloud operation is not supported on a read-only volume.

�The operation is reserved for a connected cloud sync provider.

�The cloud sync provider failed to validate the downloaded data.

pThe cloud sync provider failed user authentication.

�The cloud sync provider failed to perform the operation due to low system resources.

�The cloud sync provider failed to perform the operation due to network being unavailable.

TThe cloud operation was unsuccessful.

�The operation is only supported on files under a cloud sync root.

|The operation cannot be performed on cloud files in use.

|The operation cannot be performed on pinned cloud files.

LThe cloud operation was aborted.

`The cloud file's property store is corrupt.

PAccess to the cloud file is denied.

�The cloud operation cannot be performed on a file with incompatible hardlinks.

�The operation failed due to a conflicting cloud file property lock.

\The cloud operation was canceled by user.

dThe cloud file provider exited unexpectedly.

PThe file is not a cloud sync root.

�The cloud operation was not completed before the time-out period expired.

�Dehydration of the cloud file is disallowed by the cloud sync provider.

�The cloud provider failed to acknowledge a message before the time-out expired.

�A file snapshot operation was attempted when one is already in progress.

�A snapshot of the file cannot be taken because a user-mapped section is present.

4The file snapshot operation was terminated because one of the files was modified in a way incompatible with a snapshot operation. Please try again.

�An I/O request could not be coordinated with a file snapshot operation.

�An unexpected error occurred while processing a file snapshot operation.

|A file snapshot operation received an invalid parameter.

\Debugger did not perform a state change.

hDebugger has found the application is not idle.

HThe string binding is invalid.

`The binding handle is not the correct type.

HThe binding handle is invalid.

`The RPC protocol sequence is not supported.

TThe RPC protocol sequence is invalid.

@The string UUID is invalid.

HThe endpoint format is invalid.

HThe network address is invalid.

8No endpoint was found.

DThe timeout value is invalid.

HThe object UUID was not found.

dThe object UUID has already been registered.

`The type UUID has already been registered.

TThe RPC server is already listening.

`No protocol sequences have been registered.

LThe RPC server is not listening.

DThe manager type is unknown.

<The interface is unknown.

8There are no bindings.

LThere are no protocol sequences.

HThe endpoint cannot be created.

�Not enough resources are available to complete this operation.

HThe RPC server is unavailable.

xThe RPC server is too busy to complete this operation.

LThe network options are invalid.

�There are no remote procedure calls active on this thread.

LThe remote procedure call failed.

tThe remote procedure call failed and did not execute.

HAn RPC protocol error occurred.

xThe transfer syntax is not supported by the RPC server.

HThe type UUID is not supported.

0The tag is invalid.

DThe array bounds are invalid.

`The binding does not contain an entry name.

@The name syntax is invalid.

LThe name syntax is not supported.

�No network address is available to use to construct a UUID.

DThe endpoint is a duplicate.

PThe authentication type is unknown.

\The maximum number of calls is too small.

8The string is too long.

\The RPC protocol sequence was not found.

TThe procedure number is out of range.

�The binding does not contain any authentication information.

XThe authentication service is unknown.

TThe authentication level is unknown.

LThe security context is invalid.

TThe authorization service is unknown.

4The entry is invalid.

PThe operation cannot be performed.

�There are no more endpoints available from the endpoint mapper.

LNo interfaces have been exported.

DThe entry name is incomplete.

HThe version option is invalid.

@There are no more members.

DThere is nothing to unexport.

DThe interface was not found.

<The entry already exists.

8The entry is not found.

LThe name service is unavailable.

XThe network address family is invalid.

\The requested operation is not supported.

|No security context is available to allow impersonation.

PAn internal error occurred in RPC.

pThe RPC server attempted an integer divide by zero.

hAn addressing error occurred in the RPC server.

�A floating point operation at the RPC server caused a divide by zero.

xA floating point underflow occurred at the RPC server.

tA floating point overflow occurred at the RPC server.

�A remote procedure call is already in progress for this thread.

@There are no more bindings.

HThe group member was not found.

|The endpoint mapper database entry could not be created.

LThe object UUID is the nil UUID.

PNo interfaces have been registered.

\The remote procedure call was cancelled.

�The binding handle does not contain all required information.

�A communications failure occurred during a remote procedure call.

tThe requested authentication level is not supported.

DNo principal name registered.

�The error specified is not a valid Windows RPC error code.

`A security package specific error occurred.

<Thread is not cancelled.

pInvalid asynchronous remote procedure call handle.

|Invalid asynchronous RPC call handle for this operation.

PAccess to the HTTP proxy is denied.

�HTTP proxy server rejected the connection because the cookie authentication failed.

�The list of RPC servers available for auto-handle binding has been exhausted.

|The file designated by DCERPCCHARTRANS cannot be opened.

�The file containing the character translation table has fewer than 512 bytes.

tA null context handle is passed as an [in] parameter.

�The context handle does not match any known context handles.

\The context handle changed during a call.

�The binding handles passed to a remote procedure call do not match.

`The stub is unable to get the call handle.

lA null reference pointer was passed to the stub.

XThe enumeration value is out of range.

DThe byte count is too small.

@The stub received bad data.

pInvalid operation on the encoding/decoding handle.

lIncompatible version of the serializing package.

TIncompatible version of the RPC stub.

dThe RPC pipe object is invalid or corrupted.

|An invalid operation was attempted on an RPC pipe object.

DUnsupported RPC pipe version.

dThe RPC pipe object has already been closed.

xThe RPC call completed before all pipes were processed.

dNo more data is available from the RPC pipe.

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.

`A translator failed to translate resources.

hA IRQ translator failed to translate resources.

xDriver %2 returned invalid ID for a child device (%3).

tReissue the given operation as a cached IO operation

@Session name %1 is invalid.

PThe protocol driver %1 is invalid.

|The protocol driver %1 was not found in the system path.

|A close operation is pending on the Terminal Connection.

`There are no free output buffers available.

LThe MODEM.INF file was not found.

`The modem (%1) was not found in MODEM.INF.

�The modem did not accept the command sent to it.

Verify the configured modem name matches the attached modem.

�The modem did not respond to the command sent to it.

Verify the modem is properly cabled and powered on.

�Carrier detect has failed or carrier has been dropped due to disconnect.

�Dial tone not detected within required time.

Verify phone cable is properly attached and functional.

lBusy signal detected at remote site on callback.

`Voice detected at remote site on callback.

8Transport driver error

�The client you are using is not licensed to use this system. Your logon request is denied.

�The system has reached its licensed logon limit.

Please try again later.

�The system license has expired. Your logon request is denied.

XThe specified session cannot be found.

dThe specified session name is already in use.

pThe 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.

�An attempt has been made to connect to a session whose video mode is not supported by the current client.

�The application attempted to enable DOS graphics mode.

DOS graphics mode is not supported.

HThe 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.

�The client failed to respond to the server connect message.

pDisconnecting the console session is not supported.

�Reconnecting a disconnected session to the console is not supported.

�The request to control another session remotely was denied.

�A process has requested access to a session, but has not been granted those access rights.

dThe Terminal Connection driver %1 is invalid.

�The Terminal Connection driver %1 was not found in the system path.

�The requested session cannot be controlled remotely.

You cannot control your own session, a session that is trying to control your session,

a session that has no user logged on, nor control other sessions from the console.

�The requested session is not configured to allow remote control.

�The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client.

�Your request to connect to this Terminal server has been rejected.

Your Terminal Server Client license number has not been entered for this copy of the Terminal Client.

Please call your system administrator for help in entering a valid, unique license number for this Terminal Server Client.

Click OK to continue.

dYour 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 new copy of the Terminal Server Client with a valid, unique license number.

Click OK to continue.

HThe 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.

�Remote control could not be terminated because the specified session is not currently being remotely controlled.

�Your interactive logon privilege has been disabled.

Please contact your system administrator.

The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.

Client IP: %2.

�The target session is incompatible with the current session.

lWindows 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.

dThe resource loader failed to find MUI file.

�The resource loader failed to load MUI file because the file fail to pass validation.

�The RC Manifest is corrupted with garbage data or unsupported version or missing required item.

\The RC Manifest has invalid culture name.

pThe RC Manifest has invalid ultimatefallback name.

|The resource loader cache doesn't have loaded MUI entry.

PUser stopped resource enumeration.

HThe cluster node is not valid.

LThe cluster node already exists.

lA node is in the process of joining the cluster.

HThe cluster node was not found.

lThe cluster local node information was not found.

PThe cluster network already exists.

PThe cluster network was not found.

dThe cluster network interface already exists.

dThe cluster network interface was not found.

lThe cluster request is not valid for this object.

`The cluster network provider is not valid.

<The cluster node is down.

PThe cluster node is not reachable.

lThe cluster node is not a member of the cluster.

dA cluster join operation is not in progress.

LThe cluster network is not valid.

PNo network adapters are available.

8The cluster node is up.

@The cluster node is paused.

HThe cluster node is not paused.

\No cluster security context is available.

�The cluster network is not configured for internal cluster communication.

PThe cluster node has been poisoned.

tThe path does not belong to a cluster shared volume.

lThe cluster shared volume is not locally mounted.

�The operation has failed because read oplock break is in progress.

�The operation has failed. CSVFS has to pause and refresh information.

�The operation has failed. CSVFS does not allow block i/o in redirected mode.

�The operation has failed. CSVFS is not in redirected mode.

�CSVFS is failing operation because it is in draining state.

�The operation has failed because snapshot creation is in progress.

�The operation has succeeded on the down level file system, but CSV is failing it because it is in draining state.

�Volsnap on the coordinating node returned an error indicating that there is no snapshots on this volume.

�The operation has failed because CSV volume was not able to recover in time specified on this file object.

�The operation has failed because CSV has invalidated this file object.

�This operation is supported only on the CSV coordinator node.

�Cluster CAM has detected that someone is trying to replay ticket.

lAn attempt was made to run an invalid AML opcode

\The AML Interpreter Stack has overflowed

PAn inconsistent state has occurred

�An attempt was made to access an array outside of its bounds

TA required argument was not specified

@A fatal error has occurred

PAn invalid SuperName was specified

lAn argument with an incorrect type was specified

hAn object with an incorrect type was specified

dA target with an incorrect type was specified

hAn incorrect number of arguments were specified

HAn address failed to translate

TAn incorrect event type was specified

XA handler for the target already exists

\Invalid data for the target was specified

hAn invalid region for the target was specified

�An attempt was made to access a field outside of the defined range

dThe Global system lock could not be acquired

xAn attempt was made to reinitialize the ACPI subsystem

`The ACPI subsystem has not been initialized

LAn incorrect mutex was specified

LThe mutex is not currently owned

�An attempt was made to access the mutex by a process that was not the owner

pAn error occurred during an access to Region Space

dAn attempt was made to use an incorrect table

\The registration of an ACPI event failed

hAn ACPI Power Object failed to transition state

�The requested section is not present in the activation context.

Windows was not able to process the application binding information.

Please refer to your System Event Log for further information.

hThe application binding data format is invalid.

|The referenced assembly is not installed on your system.

�The manifest file does not begin with the required tag and format information.

tThe manifest file contains one or more syntax errors.

�The application attempted to activate a disabled activation context.

�The requested lookup key was not found in any active activation context.

�A component version required by the application conflicts with another component version already active.

�The type requested activation context section does not match the query API used.

�Lack of system resources has required isolated activation to be disabled for the current thread of execution.

`The referenced assembly could not be found.

An attempt to set the process default activation context failed because the process default activation context was already set.

�The activation context being deactivated is not the most recently activated one.

�The activation context being deactivated is not active for the current thread of execution.

�The activation context being deactivated has already been deactivated.

�The activation context of system default assembly could not be generated.

�A component used by the isolation facility has requested to terminate the process.

�The activation context activation stack for the running thread of execution is corrupt.

�The application isolation metadata for this process or thread has become corrupt.

�The value of an attribute in an identity is not within the legal range.

�The name of an attribute in an identity is not within the legal range.

�An identity contains two definitions for the same attribute.

@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.

XThe component store has been corrupted.

�A component's file does not match the verification information present in the component manifest.

�The identities of the manifests are identical but their contents are different.

XThe component identities are different.

LThe assembly is not a deployment.

XThe file is not a part of the assembly.

xAn advanced installer failed during setup or servicing.

�The character encoding in the XML declaration did not match the encoding used in the document.

tThe size of the manifest exceeds the maximum allowed.

HThe setting is not registered.

�One or more required members of the transaction are not present.

�The SMI primitive installer failed during setup or servicing.

�A generic command executable returned a result that indicates failure.

�A component is missing file verification information in its manifest.

�The function attempted to use a name that is reserved for use by another transaction.

�The transaction handle associated with this operation is not valid.

�The requested operation was made in the context of a transaction that is no longer active.

�The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported.

�Transaction support within the specified resource manager is not started or was shut down due to an error.

�The metadata of the RM has been corrupted. The RM will not function.

�The resource manager has attempted to prepare a transaction that it has not successfully joined.

�The specified directory does not contain a file system resource manager.

�The remote server or share does not support transacted file operations.

�The requested log size for the file system resource manager is invalid.

�The remote server sent mismatching version number or Fid for a file opened with transactions.

|The RM tried to register a protocol that already exists.

lThe attempt to propagate the Transaction failed.

�The requested propagation protocol was not registered as a CRM.

tThe Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allowed.

�The requested operation is not valid on the Transaction object in its current state.

$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.

�It is too late to perform the requested operation, since the Transaction has already been aborted.

�It is too late to perform the requested operation, since the Transaction has already been committed.

�The buffer passed in to NtPushTransaction or NtPullTransaction is not in a valid format.

�The current transaction context associated with the thread is not a valid handle to a transaction object.

An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.

�The object (file, stream, link) corresponding to the handle has been deleted by a transaction savepoint rollback.

�The specified file miniversion was not found for this transacted file open.

�The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback.

�A miniversion may only be opened in the context of the transaction that created it.

�It is not possible to open a miniversion with modify access.

�It is not possible to create any more miniversions for this stream.

�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.

<The log data is corrupt.

�The transaction outcome is unavailable because the resource manager responsible for it has disconnected.

�The request was rejected because the enlistment in question is not a superior enlistment.

�The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction.

The operation cannot be performed because another transaction is depending on the fact that this property will not change.

�The operation would involve a single file with two transactional resource managers and is therefore not allowed.

�The $Txf directory must be empty for this operation to succeed.

�The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed.

�The operation could not be completed because the transaction manager does not have a log.

A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution.

�The transactional metadata attribute on the file or directory %hs is corrupt and unreadable.

�The encryption operation could not be completed because a transaction is active.

|This object is not allowed to be opened in a transaction.

�Memory mapping (creating a mapped section) a remote file under a transaction is not supported.

�Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it.

This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader.

�The request to thaw frozen transactions was ignored because transactions had not previously been frozen.

�Transactions cannot be frozen because a freeze is already in progress.

�The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot.

�The savepoint operation failed because files are open on the transaction. This is not permitted.

�The sparse operation could not be completed because a transaction is active on the file.

TThe 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.

�I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data.

The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources.

<The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manger has been shut down.

�The specified Transaction was unable to be opened, because it was not found.

�The specified ResourceManager was unable to be opened, because it was not found.

�The specified Enlistment was unable to be opened, because it was not found.

�The specified TransactionManager was unable to be opened, because it was not found.

LThe 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.

\The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover.

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.

�Because the associated transaction manager or resource manager has been closed, the handle is no longer valid.

�The compression operation could not be completed because a transaction is active on the file.

xThe specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask.

\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.

�The link tracking operation could not be completed because a transaction is active.

tThis operation cannot be performed in a transaction.

�The kernel transaction manager had to abort or forget the transaction because it blocked forward progress.

�The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file.

This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again.

�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.

tThe transaction does not have a superior enlistment.

�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.

�The specified operation could not be performed because the resource manager is not enlisted in the transaction.

\Log service found an invalid log sector.

�Log service encountered a log sector with invalid block parity.

hLog service encountered a remapped log sector.

�Log service encountered a partial or incomplete log block.

�Log service encountered an attempt access data outside the active log range.

xLog service user log marshalling buffers are exhausted.

�Log service encountered an attempt read from a marshalling area with an invalid read context.

tLog service encountered an invalid log restart area.

tLog service encountered an invalid log block version.

dLog service encountered an invalid log block.

�Log service encountered an attempt to read the log with an invalid read mode.

pLog service encountered a corrupted metadata file.

�Log service encountered a metadata file that could not be created by the log file system.

�Log service encountered a metadata file with inconsistent data.

�Log service encountered an attempt to erroneously allocate or dispose reservation space.

�Log service cannot delete log file or file system container.

�Log service has reached the maximum allowable containers allocated to a log file.

�Log service has attempted to read or write backwards past the start of the log.

�Log policy could not be installed because a policy of the same type is already present.

�Log policy in question was not installed at the time of the request.

tThe installed set of policies on the log is invalid.

�A policy on the log in question prevented the operation from completing.

�Log space cannot be reclaimed because the log is pinned by the archive tail.

`Log record is not a record in the log file.

�Number of reserved log records or the adjustment of the number of reserved log records is invalid.

�Reserved log space or the adjustment of the log space is invalid.

�A new or existing archive tail or base of the active log is invalid.

8Log space is exhausted.

�Log is multiplexed, no direct writes to the physical log is allowed.

|The operation failed because the log is a dedicated log.

`The operation requires an archive context.

DLog archival is in progress.

�The operation requires a non-ephemeral log, but the log is ephemeral.

�The log must have at least two containers before it can be read from or written to.

pA log client has already registered on the stream.

pA log client has not been registered on the stream.

�A request has already been made to handle the log full condition.

�Log service encountered an error when attempting to read from a log container.

�Log service encountered an error when attempting to write to a log container.

�Log service encountered an error when attempting open a log container.

�Log service encountered an invalid container state when attempting a requested action.

�Log service is not in the correct state to perform a requested action.

|Log space cannot be reclaimed because the log is pinned.

@Log metadata flush failed.

xSecurity on the log and its containers is inconsistent.

�Records were appended to the log or reservation changes were made, but the log could not be flushed.

�The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available.

\{Display Driver Stopped Responding}

�A handler was not defined by the filter for this operation.

dA context is already defined for this object.

xAsynchronous requests are not valid for this operation.

PInternal error code used by the filter manager to determine if a fastio operation should be forced down the IRP path. Mini-filters should never return this value.

�An invalid name request was made. The name requested cannot be retrieved at this time.

Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock.

The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver.

The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called).

XThe 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.

�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.

The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time.

tNon-paged pool must be used for this type of context.

�A duplicate handler definition has been provided for an operation.

`The callback data queue has been disabled.

tDo not attach the filter to the volume at this time.

xDo not detach the filter from the volume at this time.

�An instance already exists at this altitude on the volume specified.

�An instance already exists with this name on the volume specified.

hThe system could not find the filter specified.

hThe system could not find the volume specified.

lThe system could not find the instance specified.

�No registered context allocation definition was found for the given request.

�An invalid parameter was specified during context registration.

�The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.

�The requested device object does not exist for the given volume.

\The specified volume is already mounted.

�The specified Transaction Context is already enlisted in a transaction

�The specified context is already attached to another object

�No waiter is present for the filter's reply to this message.

�The filesystem database resource is in use. Registration cannot complete at this time.

�The filter is not allowed to attach because it has not declared compability with WCOS.

\Monitor descriptor could not be obtained.

�Format of the obtained monitor descriptor is not supported by this release.

xChecksum of the obtained monitor descriptor is invalid.

�Monitor descriptor contains an invalid standard timing block.

�WMI data block registration failed for one of the MSMonitorClass WMI subclasses.

�Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.

�Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.

�There is no monitor descriptor data at the specified (offset, size) region.

�Monitor descriptor contains an invalid detailed timing block.

tMonitor descriptor contains invalid manufacture date.

�Exclusive mode ownership is needed to create unmanaged primary allocation.

�The driver needs more DMA buffer space in order to complete the requested operation.

dSpecified display adapter handle is invalid.

�Specified display adapter and all of its state has been reset.

|The driver stack doesn't match the expected driver model.

�Present happened but ended up into the changed desktop mode

`Nothing to present due to desktop occlusion

pNot able to present due to denial of desktop access

\Not able to present with color conversion

�The kernel driver detected a version mismatch between it and the user mode driver.

�Present redirection is disabled (desktop windowing management subsystem is off).

�Previous exclusive VidPn source owner has released its ownership

`Window DC is not available for presentation

�Windowless present is disabled (desktop windowing management subsystem is off).

<Window handle is invalid

\No buffer is bound to composition surface

@Vail state has been changed

�Notifying indirect display UMDF class driver to abandon current swapchain.

�Notifying indirect display UMDF class driver that indirect display device has been stopped.

�Not enough video memory available to complete the operation.

�Couldn't probe and lock the underlying memory of an allocation.

LThe allocation is currently busy.

�An object being referenced has already reached the maximum reference count and can't be referenced any further.

�A problem couldn't be solved due to some currently existing condition. The problem should be tried again later.

�A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately.

@The allocation is invalid.

tNo more unswizzling aperture are currently available.

�The current allocation can't be unswizzled by an aperture.

�The request failed because a pinned allocation can't be evicted.

�The allocation can't be used from its current segment location for the specified operation.

�A locked allocation can't be used in the current command buffer.

�The allocation being referenced has been closed permanently.

pAn invalid allocation instance is being referenced.

lAn invalid allocation handle is being referenced.

�The allocation being referenced doesn't belong to the current device.

`The specified allocation lost its content.

�GPU exception is detected on the given device. The device is not able to be scheduled.

TSpecified VidPN topology is invalid.

�Specified VidPN topology is valid but is not supported by this model of the display adapter.

Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources.

PSpecified VidPN handle is invalid.

`Specified video present source is invalid.

`Specified video present target is invalid.

�Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).

`Specified VidPN source mode set is invalid.

`Specified VidPN target mode set is invalid.

dSpecified video signal frequency is invalid.

lSpecified video signal active region is invalid.

hSpecified video signal total region is invalid.

hSpecified video present source mode is invalid.

hSpecified video present target mode is invalid.

�Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.

�Specified video present path is already in VidPN's topology.

`Specified mode is already in the mode set.

hSpecified video present source set is invalid.

hSpecified video present target set is invalid.

�Specified video present source is already in the video present source set.

�Specified video present target is already in the video present target set.

\Specified VidPN present path is invalid.

�Miniport has no recommendation for augmentation of the specified VidPN's topology.

lSpecified monitor frequency range set is invalid.

dSpecified monitor frequency range is invalid.

�Specified frequency range is not in the specified monitor frequency range set.

�Specified frequency range is already in the specified monitor frequency range set.

�Specified mode set is stale. Please reacquire the new mode set.

dSpecified monitor source mode set is invalid.

\Specified monitor source mode is invalid.

(Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.

�ID of the specified mode is already used by another mode in the set.

�System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.

�Number of video present targets must be greater than or equal to the number of video present sources.

pSpecified present path is not in VidPN's topology.

�Display adapter must have at least one video present source.

�Display adapter must have at least one video present target.

dSpecified monitor descriptor set is invalid.

\Specified monitor descriptor is invalid.

�Specified descriptor is not in the specified monitor descriptor set.

�Specified descriptor is already in the specified monitor descriptor set.

�ID of the specified monitor descriptor is already used by another descriptor in the set.

xSpecified video present target subset type is invalid.

�Two or more of the specified resources are not related to each other, as defined by the interface semantics.

�ID of the specified video present source is already used by another source in the set.

�ID of the specified video present target is already used by another target in the set.

�Specified VidPN source cannot be used because there is no available VidPN target to connect it to.

�Newly arrived monitor could not be associated with a display adapter.

�Display adapter in question does not have an associated VidPN manager.

�VidPN manager of the display adapter in question does not have an active VidPN.

�Specified VidPN topology is stale. Please reacquire the new topology.

�There is no monitor connected on the specified video present target.

�Specified source is not part of the specified VidPN's topology.

`Specified primary surface size is invalid.

\Specified visible region size is invalid.

DSpecified stride is invalid.

PSpecified pixel format is invalid.

LSpecified color basis is invalid.

dSpecified pixel value access mode is invalid.

�Specified target is not part of the specified VidPN's topology.

tFailed to acquire display mode management interface.

�Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it.

lSpecified VidPN is active and cannot be accessed.

�Specified VidPN present path importance ordinal is invalid.

�Specified VidPN present path content geometry transformation is invalid.

�Specified content geometry transformation is not supported on the respective VidPN present path.

LSpecified gamma ramp is invalid.

�Specified gamma ramp is not supported on the respective VidPN present path.

�Multi-sampling is not supported on the respective VidPN present path.

lSpecified mode is not in the specified mode set.

�Specified VidPN topology recommendation reason is invalid.

tSpecified VidPN present path content type is invalid.

�Specified VidPN present path copy protection type is invalid.

�No more than one unassigned mode set can exist at any given time for a given VidPN source/target.

dSpecified scanline ordering type is invalid.

|Topology changes are not allowed for the specified VidPN.

�All available importance ordinals are already used in specified topology.

�Specified primary surface has a different private format attribute than the current primary surface

`Specified mode pruning algorithm is invalid

hSpecified monitor capability origin is invalid.

|Specified monitor frequency range constraint is invalid.

�Maximum supported number of present paths has been reached.

�Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology.

\Specified client type was not recognized.

�Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).

�Specified display adapter child device already has an external device connected to it.

�Specified display adapter child device does not support descriptor exposure.

|The display adapter is not linked to any other adapters.

�Lead adapter in a linked configuration was not enumerated yet.

�Some chain adapters in a linked configuration were not enumerated yet.

�The chain of linked adapters is not ready to start because of an unknown failure.

�An attempt was made to start a lead link display adapter when the chain links were not started yet.

�An attempt was made to power up a lead link display adapter when the chain links were powered down.

�The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state.

�The driver trying to start is not the same as the driver for the POSTed display adapter.

�An operation is being attempted that requires the display adapter to be in a quiescent state.

LThe driver does not support OPM.

LThe driver does not support COPP.

LThe driver does not support UAB.

hThe specified encrypted parameters are invalid.

�The GDI display device passed to this function does not have any active protected outputs.

hAn internal error caused an operation to fail.

�The function failed because the caller passed in an invalid OPM user mode handle.

�A certificate could not be returned because the certificate buffer passed to the function was too small.

The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in spanning mode.

The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in theater mode.

�The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.

�The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.

The protected output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.

�The protected output cannot enable Analogue Copy Protection (ACP) because it does not support ACP.

8The protected output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A.

XThe DxgkDdiOPMGetInformation function cannot return the version of the SRM being used because the application never successfully passed an SRM to the protected output.

DThe DxgkDdiOPMConfigureProtectedOutput function cannot enable the specified output protection technology because the output's screen resolution is too high.

HThe DxgkDdiOPMConfigureProtectedOutput function cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.

�The operating system asynchronously destroyed this OPM protected output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this protected output was removed, the monitor PDO associated with this protected output was stopped, or the protected output's session became a non-console session.

Either the DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned when the caller tries to use a COPP specific command while the protected output has OPM semantics only.

�The DxgkDdiOPMGetInformation and DxgkDdiOPMGetCOPPCompatibleInformation functions return this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.

�The function failed because an unexpected error occurred inside of a display driver.

Either the DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned when the caller tries to use an OPM specific command while the protected output has COPP semantics only.

�The DxgkDdiOPMGetCOPPCompatibleInformation and DxgkDdiOPMConfigureProtectedOutput functions return this error if the display driver does not support the DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING and DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.

tThe DxgkDdiOPMConfigureProtectedOutput function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.

�The monitor connected to the specified video output does not have an I2C bus.

pNo device on the I2C bus has the specified address.

�An error occurred while transmitting data to the device on the I2C bus.

�An error occurred while receiving data from the device on the I2C bus.

tThe monitor does not support the specified VCP code.

hThe data received from the monitor is invalid.

�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.

$A 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.

hAn internal error caused an operation to fail.

�An operation failed because a DDC/CI message had an invalid value in its command field.

�An error occurred because the field length of a DDC/CI message contained an invalid value.

�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.

�This function failed because an invalid monitor handle was passed to it.

TThe 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.

�This function can only be used if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session.

�This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.

�The function failed because the specified GDI display device was not attached to the Windows desktop.

@This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.

�The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, it points to an invalid address, it points to a kernel mode address or it is not correctly aligned.

�This function failed because the GDI device passed to it did not have any monitors associated with it.

�An array passed to the function cannot hold all of the data that the function must copy into the array.

hAn internal error caused an operation to fail.

�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.

tThis volume is locked by BitLocker Drive Encryption.

lThe volume is not encrypted, no key is available.

|The control block for the encrypted volume is not valid.

�The volume cannot be encrypted because it does not have enough free space.

�The volume cannot be encrypted because the file system is not supported.

�The file system size is larger than the partition size in the partition table.

|The file system does not extend to the end of the volume.

�This operation cannot be performed while a file system is mounted on the volume.

�BitLocker Drive Encryption is not included with this version of Windows.

|Requested action not allowed in the current volume state.

@Data supplied is malformed.

XThe volume is not bound to the system.

LThat volume is not a data volume.

tA read operation failed while converting the volume.

tA write operation failed while converting the volume.

�The control block for the encrypted volume was updated by another thread. Try again.

�The encryption algorithm does not support the sector size of that volume.

\BitLocker recovery authentication failed.

LThat volume is not the OS volume.

�The BitLocker startup key or recovery password could not be read from external media.

�The BitLocker startup key or recovery password file is corrupt or invalid.

�The BitLocker encryption key could not be obtained from the startup key or recovery password.

hThe Trusted Platform Module (TPM) is disabled.

�The authorization data for the Storage Root Key (SRK) of the Trusted Platform Module (TPM) is not zero.

<The system boot information changed or the Trusted Platform Module (TPM) locked out access to BitLocker encryption keys until the computer is restarted.

�The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM).

�The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and PIN.

�A boot application hash does not match the hash computed when BitLocker was turned on.

�The Boot Configuration Data (BCD) settings are not supported or have changed since BitLocker was enabled.

xBoot debugging is enabled. Run bcdedit to turn it off.

pThe BitLocker encryption key could not be obtained.

hThe metadata disk region pointer is incorrect.

hThe backup copy of the metadata is out of date.

pNo action was taken as a system reboot is required.

�No action was taken as BitLocker Drive Encryption is in RAW access mode.

�BitLocker Drive Encryption cannot enter raw access mode for this volume.

The auto-unlock master key was not available from the operating system volume. Retry the operation using the BitLocker WMI interface.

�The system firmware failed to enable clearing of system memory on reboot.

�This feature of BitLocker Drive Encryption is not included with this version of Windows.

�Group policy does not permit turning off BitLocker Drive Encryption on roaming data volumes.

\Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.

dThe requested virtualization size is too big.

XThe 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.

�The drive is too small to be protected using BitLocker Drive Encryption.

4The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals.

�BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage.

�BitLocker Drive Encryption does not support wiping free space on thin provisioned storage.

�This command can only be performed from the coordinator node for the specified CSV volume.

�This command cannot be performed on a volume when it is part of a cluster.

�BitLocker cannot be upgraded during disk encryption or decryption.

lWipe of free space is not currently taking place.

Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates.

Secure Boot has been disabled. Either Secure Boot must be re-enabled, or BitLocker must be suspended for Windows to start normally.

dSecure Boot policy has unexpectedly changed.

�Device Lock has been triggered due to too many incorrect password attempts.

�Device encryption removal is blocked due to volume being extended beyond its original size.

�This action isn't supported because this drive isn't automatically managed with device encryption.

�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.

�BitLocker can't be suspended on this drive until the next restart.

�BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume.

BitLocker can't enable encryption on this hardware encrypting drive volume because the drive bands couldn't be enumerated.

�This operation cannot be completed because dataset is full.

<This operation cannot be completed because BitLocker Drive Encryption metadata area is full. Consider removing unnecessary key protectors for this drive.

�The operation failed because BitLocker Drive Encryption cannot suspend protection due to policy.

�The datum is invalid in its current state, but may be fixed so that it is valid.

xThe dataset contains TPM datums that are inconsistent.

�The TPM protector contains conflicting information about whether the binding is a Secure Boot binding.

�The dataset contains conflicting information about whether the TPM protector binding is a Secure Boot binding.

�The dataset contains a TPM binding without associated binding information. Try removing and re-adding the TPM protector.

�The dataset contains TPM binding information incorrectly associated to multiple TPM bindings. Try re-enabling BitLocker.

\The compared final TPM PCR values match.

�BitLocker failed to obtain the key from the TPM due to an unforseen TPM failure.

�BitLocker encountered a problem communicating with the TPM at boot.

hA TPM was not available for BitLocker at boot.

�BitLocker could not enforce the PCR 11 cap event boundary.

,BitLocker prevented an attempt to create a TPM binding for a PCR that contains events extended into the TPM after the BitLocker boot lock event.

The firmware update was not applied because BitLocker TPM bindings do not include the latest measurements. Restart your computer to retry.

pThe BitLocker TPM binding configuration is invalid.

�The BitLocker TPM protector cannot fit all the necessary TPM bindings.

tA BitLocker TPM protector binding is badly formatted.

�The dataset contains binding information without an associated TPM binding. Try re-enabling BitLocker.

�BitLocker is prevented from using hardware accelerated encryption.

�BitLocker failed to find a TPM binding that can be used to unlock the drive.

�BitLocker failed to unlock the drive using a V2 TPM protector.

�BitLocker failed to find any TPM bindings that can be used to unlock the drive.

The firmware update was not applied. To finish installation of the firmware, please suspend BitLocker and restart your device.

`The firmware update was not applied because TPM PCRs affected by the firmware installation were not excluded by BitLocker's TPM protector. Restart your computer to retry.

�The TPM PCR values did not match what was calculated from the TCG log.

@The callout does not exist.

TThe filter condition does not exist.

@The filter does not exist.

<The layer does not exist.

DThe provider does not exist.

TThe provider context does not exist.

DThe sublayer does not exist.

@The object does not exist.

lAn object with that GUID or LUID already exists.

�The object is referenced by other objects so cannot be deleted.

xThe call is not allowed from within a dynamic session.

�The call was made from the wrong session so cannot be completed.

�The call must be made from within an explicit transaction.

�The call is not allowed from within an explicit transaction.

tThe explicit transaction has been forcibly cancelled.

HThe session has been cancelled.

�The call is not allowed from within a read-only transaction.

�The call timed out while waiting to acquire the transaction lock.

tCollection of network diagnostic events is disabled.

xThe operation is not supported by the specified layer.

lThe call is allowed for kernel-mode callers only.

�The call tried to associate two objects with incompatible lifetimes.

dThe object is built in so cannot be deleted.

lThe maximum number of callouts has been reached.

�A notification could not be delivered because a message queue is at its maximum capacity.

�The traffic parameters do not match those for the security association context.

�The call is not allowed for the current security association state.

@A required pointer is null.

@An enumerator is not valid.

`The flags field contains an invalid value.

DA network mask is not valid.

@An FWP_RANGE is not valid.

HThe time interval is not valid.

�An array that must contain at least one element is zero length.

`The displayData.name field cannot be null.

�The action type is not one of the allowed action types for a filter.

HThe filter weight is not valid.

�A filter condition contains a match type that is not compatible with the operands.

�An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type.

hAn integer value is outside the allowed range.

DA reserved field is non-zero.

�A filter cannot contain multiple conditions operating on a single field.

�A policy cannot contain the same keying module more than once.

lThe action type is not compatible with the layer.

tThe action type is not compatible with the sublayer.

�The raw context or the provider context is not compatible with the layer.

�The raw context or the provider context is not compatible with the callout.

�The authentication method is not compatible with the policy type.

�The Diffie-Hellman group is not compatible with the policy type.

tAn IKE policy cannot contain an Extended Mode policy.

�The enumeration template or subscription will never match any objects.

`The provider context is of the wrong type.

@The parameter is incorrect.

lThe maximum number of sublayers has been reached.

�The notification function for a callout returned an error.

lThe IPsec authentication transform is not valid.

\The IPsec cipher transform is not valid.

�The IPsec cipher transform is not compatible with the policy.

xThe combination of IPsec transform types is not valid.

�A policy cannot contain the same auth method more than once.

`A tunnel endpoint configuration is invalid.

LThe WFP MAC Layers are not ready.

�A key manager capable of key dictation is already registered

PA key manager dictated invalid keys

hThe BFE IPsec Connection Tracking is disabled.

<The DNS name is invalid.

�The engine option is still enabled due to other configuration settings.

�The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine.

HThe TCP/IP stack is not ready.

xThe injection handle is being closed by another thread.

HThe injection handle is stale.

HThe classify cannot be pended.

tThe packet should be dropped, no ICMP should be sent.

tThe binding to the network interface is being closed.

LAn invalid version was specified.

`An invalid characteristics table was used.

�Failed to find the network interface or network interface is not ready.

TFailed to open the network interface.

�Network interface has encountered an internal unrecoverable failure.

tThe multicast list on the network interface is full.

�An attempt was made to add a duplicate multicast address to the list.

�At attempt was made to remove a multicast address that was never added.

XNetwork interface aborted the request.

�Network interface can not process the request because it is being reset.

�An attempt was made to send an invalid packet on a network interface.

�The specified request is not a valid operation for the target device.

�Network interface is not ready to complete this operation.

�The length of the buffer submitted for this operation is not valid.

hThe data used for this operation is not valid.

�The length of buffer submitted for this operation is too small.

�Network interface does not support this OID (Object Identifier)

XThe network interface has been removed.

pNetwork interface does not support this media type.

�An attempt was made to remove a token ring group address that is in use by other components.

|An attempt was made to map a file that can not be found.

pAn error occurred while NDIS tried to map the file.

|An attempt was made to map a file that is already mapped.

�An attempt to allocate a hardware resource failed because the resource is used by another component.

�The I/O operation failed because network media is disconnected or wireless access point is out of range.

pThe network address used in the request is invalid.

�The offload operation on the network interface has been paused.

LNetwork interface was not found.

�The revision number specified in the structure is not supported.

�The specified port does not exist on this network interface.

�The current state of the specified port on this network interface does not support the requested operation.

dThe miniport adapter is in lower power state.

�This operation requires the miniport adapter to be reinitialized.

xThere are not enough queues to complete the operation.

lNetwork interface does not support this request.

�The TCP connection is not offloadable because of a local policy setting.

�The TCP connection is not offloadable by the Chimney offload target.

pThe IP Path object is not in an offloadable state.

The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation.

�The wireless local area network interface is busy and can not perform the requested operation.

�The wireless local area network interface is powered down and doesn't support the requested operation.

\The list of wake on LAN patterns is full.

lThe list of low power protocol offloads is full.

�The wireless local area network interface cannot start an AP on the specified channel right now.

�The wireless local area network interface cannot start an AP on the specified band right now.

�The wireless local area network interface cannot start an AP on this channel due to regulatory reasons.

�The wireless local area network interface cannot start an AP on this band due to regulatory reasons.

TThe QUIC connection handshake failed.

�The QUIC connection failed to negotiate a compatible protocol version.

dThe QUIC connection was canceled by the user.

pThe QUIC connection encountered an internal error.

tThe QUIC connection encountered a protocol violation.

DThe QUIC connection was idle.

�The QUIC connection timed out while trying to contact the peer.

�The QUIC connection failed to negotiate a compatible ALPN.

�The QUIC connection failed because there are not enough streams available.

xThe QUIC connection failed because the ALPN is in use.

�The QUIC connection encountered an unexpected message during TLS.

�The QUIC connection encountered a bad certificate during TLS.

�The QUIC connection encountered an unsupported certificate during TLS.

�The QUIC connection encountered a revoked certificate during TLS.

�The QUIC connection encountered an expired certificate during TLS.

�The QUIC connection encountered an unknown certificate during TLS.

�The QUIC connection encountered an illegal parameter during TLS.

�The QUIC connection encountered a certificate with an unkown certificate authority during TLS.

�The QUIC connection attempt was denied by the peer during TLS.

|The QUIC connection security was insufficient during TLS.

�The QUIC connection encountered an internal error during TLS.

|The QUIC connection was canceled by the user during TLS.

xThe QUIC connection required a certificate during TLS.

�This is an error mask to convert TPM hardware errors to win errors.

HTPM 1.2: Authentication failed.

�TPM 1.2: The index to a PCR, DIR or other register is incorrect.

XTPM 1.2: One or more parameter is bad.

�TPM 1.2: An operation completed successfully but the auditing of that operation failed.

�TPM 1.2: The clear disable flag is set and all clear operations now require physical access.

tTPM 1.2: Activate the Trusted Platform Module (TPM).

pTPM 1.2: Enable the Trusted Platform Module (TPM).

hTPM 1.2: The target command has been disabled.

HTPM 1.2: The operation failed.

lTPM 1.2: The ordinal was unknown or inconsistent.

tTPM 1.2: The ability to install an owner is disabled.

hTPM 1.2: The key handle cannot be interpreted.

lTPM 1.2: The key handle points to an invalid key.

\TPM 1.2: Unacceptable encryption scheme.

\TPM 1.2: Migration authorization failed.

pTPM 1.2: PCR information could not be interpreted.

DTPM 1.2: No room to load key.

lTPM 1.2: There is no Storage Root Key (SRK) set.

�TPM 1.2: An encrypted blob is invalid or was not created by this TPM.

�TPM 1.2: The Trusted Platform Module (TPM) already has an owner.

�TPM 1.2: The TPM has insufficient internal resources to perform the requested action.

XTPM 1.2: A random string was too short.

�TPM 1.2: The TPM does not have the space to perform the operation.

�TPM 1.2: The named PCR value does not match the current PCR value.

�TPM 1.2: The paramSize argument to the command has the incorrect value .

`TPM 1.2: There is no existing SHA-1 thread.

�TPM 1.2: The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error.

�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, you might need to replace your TPM hardware or motherboard.

�TPM 1.2: The authorization for the second key in a 2 key function failed authorization.

|TPM 1.2: The tag value sent to for a command is invalid.

�TPM 1.2: An IO error occurred transmitting information to the TPM.

hTPM 1.2: The encryption process had a problem.

lTPM 1.2: The decryption process did not complete.

TTPM 1.2: An invalid handle was used.

�TPM 1.2: The TPM does not have an Endorsement Key (EK) installed.

`TPM 1.2: The usage of a key is not allowed.

pTPM 1.2: The submitted entity type is not allowed.

�TPM 1.2: The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup.

�TPM 1.2: Signed data cannot include additional DER information.

�TPM 1.2: The key properties in TPM_KEY_PARMs are not supported by this TPM.

�TPM 1.2: The migration properties of this key are incorrect.

�TPM 1.2: The signature or encryption scheme for this key is incorrect or not permitted in this situation.

�TPM 1.2: The size of the data (or blob) parameter is bad or inconsistent with the referenced key.

|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.

�TPM 1.2: Either the physicalPresence or physicalPresenceLock bits have the wrong value.

�TPM 1.2: The TPM cannot perform this version of the capability.

�TPM 1.2: The TPM does not allow for wrapped transport sessions.

�TPM 1.2: TPM audit construction failed and the underlying command was returning a failure code also.

�TPM 1.2: TPM audit construction failed and the underlying command was returning success.

�TPM 1.2: Attempt to reset a PCR register that does not have the resettable attribute.

�TPM 1.2: Attempt to reset a PCR register that requires locality and locality modifier not part of command transport.

hTPM 1.2: Make identity blob not properly typed.

�TPM 1.2: When saving context identified resource type does not match actual resource.

�TPM 1.2: The TPM is attempting to execute a command that is not allowed when in FIPS mode.

�TPM 1.2: The command is attempting to use an invalid family ID.

�TPM 1.2: The permission to manipulate the NV storage is not available.

lTPM 1.2: The operation requires a signed command.

`TPM 1.2: Wrong operation to load an NV key.

�TPM 1.2: NV_LoadKey blob requires both owner and blob authorization.

lTPM 1.2: The NV area is locked and not writable.

�TPM 1.2: The locality is incorrect for the attempted operation.

�TPM 1.2: The NV area is read only and can't be written to.

�TPM 1.2: There is no protection on the write to the NV area.

hTPM 1.2: The family count value does not match.

lTPM 1.2: The NV area has already been written to.

\TPM 1.2: The NV area attributes conflict.

�TPM 1.2: The structure tag and version are invalid or inconsistent.

�TPM 1.2: The key is under control of the TPM Owner and can only be evicted by the TPM Owner.

\TPM 1.2: The counter handle is incorrect.

xTPM 1.2: The write is not a complete write of the area.

�TPM 1.2: The gap between saved context counts is too large.

�TPM 1.2: The maximum number of NV writes without an owner has been exceeded.

`TPM 1.2: No operator AuthData value is set.

�TPM 1.2: The resource pointed to by context is not loaded.

hTPM 1.2: The delegate administration is locked.

�TPM 1.2: Attempt to manage a family other then the delegated family.

lTPM 1.2: Delegation table management not enabled.

�TPM 1.2: There was a command executed outside of an exclusive transport session.

�TPM 1.2: Attempt to context save a owner evict controlled key.

�TPM 1.2: The DAA command has no resources available to execute the command.

�TPM 1.2: The consistency check on DAA parameter inputData0 has failed.

�TPM 1.2: The consistency check on DAA parameter inputData1 has failed.

�TPM 1.2: The consistency check on DAA_issuerSettings has failed.

�TPM 1.2: The consistency check on DAA_tpmSpecific has failed.

�TPM 1.2: The atomic process indicated by the submitted DAA command is not the expected process.

�TPM 1.2: The issuer's validity check has detected an inconsistency.

hTPM 1.2: The consistency check on w has failed.

LTPM 1.2: The handle is incorrect.

PTPM 1.2: Delegation is not correct.

TTPM 1.2: The context blob is invalid.

`TPM 1.2: Too many contexts held by the TPM.

�TPM 1.2: Migration authority signature validation failure.

lTPM 1.2: Migration destination not authenticated.

TTPM 1.2: Migration source incorrect.

XTPM 1.2: Incorrect migration authority.

�TPM 1.2: Attempt to revoke the EK and the EK is not revocable.

TTPM 1.2: Bad signature of CMK ticket.

�TPM 1.2: There is no room in the context list for additional contexts.

�TPM 2.0: Asymmetric algorithm not supported or not correct.

LTPM 2.0: Inconsistent attributes.

|TPM 2.0: Hash algorithm not supported or not appropriate.

�TPM 2.0: Value is out of range or is not correct for the context.

�TPM 2.0: Hierarchy is not enabled or is not correct for the use.

PTPM 2.0: Key size is not supported.

lTPM 2.0: Mask generation function not supported.

\TPM 2.0: Mode of operation not supported.

�TPM 2.0: The type of the value is not appropriate for the use.

hTPM 2.0: The Handle is not correct for the use.

�TPM 2.0: Unsupported key derivation function or function not appropriate for use.

\TPM 2.0: Value was out of allowed range.

�TPM 2.0: The authorization HMAC check failed and DA counter incremented.

DTPM 2.0: Invalid nonce size.

lTPM 2.0: Authorization requires assertion of PP.

dTPM 2.0: Unsupported or incompatible scheme.

LTPM 2.0: Structure is wrong size.

�TPM 2.0: Unsupported symmetric algorithm or key size, or not appropriate for instance.

LTPM 2.0: Incorrect structure tag.

TTPM 2.0: Union selector is incorrect.

�TPM 2.0: The TPM was unable to unmarshal a value because there were not enough octets in the input buffer.

TTPM 2.0: The signature is not valid.

�TPM 2.0: Key fields are not compatible with the selected use.

HTPM 2.0: A policy check failed.

LTPM 2.0: Integrity check failed.

<TPM 2.0: Invalid ticket.

pTPM 2.0: Reserved bits not set to zero as required.

xTPM 2.0: Authorization failure without DA implications.

LTPM 2.0: The policy has expired.

TTPM 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.

�TPM 2.0: Public and sensitive portions of an object are not cryptographically bound.

DTPM 2.0: Curve not supported.

dTPM 2.0: Point is not on the required curve.

DTPM 2.0: TPM not initialized.

�TPM 2.0: Commands not being accepted because of a TPM failure.

`TPM 2.0: Improper use of a sequence handle.

HTPM 2.0: TPM_RC_PRIVATE error.

4TPM 2.0: TPM_RC_HMAC.

<TPM 2.0: TPM_RC_DISABLED.

�TPM 2.0: Command failed because audit sequence required exclusivity.

HTPM 2.0: Unsupported ECC curve.

|TPM 2.0: Authorization handle is not correct for command.

�TPM 2.0: Command requires an authorization session for handle and is not present.

�TPM 2.0: Policy failure in Math Operation or an invalid authPolicy value.

<TPM 2.0: PCR check fail.

\TPM 2.0: PCR have changed since checked.

xTPM 2.0: The TPM is not in the right mode for upgrade.

`TPM 2.0: Context ID counter is at maximum.

�TPM 2.0: authValue or authPolicy is not available for selected entity.

�TPM 2.0: A _TPM_Init and Startup(CLEAR) is required before the TPM can resume operation.

dTPM 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.

�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.

TTPM 2.0: Command code not supported.

TPM 2.0: The value of authorizationSize is out of range or the number of octets in the authorization Area is greater than required.

TPM 2.0: Use of an authorization session with a context command or another command that cannot have an authorization session.

\TPM 2.0: NV offset+size is out of range.

�TPM 2.0: Requested allocation size is larger than allowed.

@TPM 2.0: NV access locked.

|TPM 2.0: NV access authorization fails in command actions

�TPM 2.0: An NV index is used before being initialized or the state saved by TPM2_Shutdown(STATE) could not be restored.

hTPM 2.0: Insufficient space for NV allocation.

xTPM 2.0: NV index or persistent object already defined.

tTPM 2.0: Context in TPM2_ContextLoad() is not valid.

|TPM 2.0: chHash value already set or not correct for use.

lTPM 2.0: Handle for parent is not a valid parent.

TTPM 2.0: Some function needs testing.

�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.

�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.

<The command was blocked.

PThe specified handle was not found.

�The TPM returned a duplicate handle and the command needs to be resubmitted.

dThe command within the transport was blocked.

pThe command within the transport is not supported.

�The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time.

HSelfTestFull has not been run.

hThe TPM is currently executing a full selftest.

�The TPM is defending against dictionary attacks and is in a time-out period.

@The command was cancelled.

�A new TPM context could not be created because there are too many open contexts.

�TPM driver is not compatible with the version of TPM found on the system.

�The caller does not have the appropriate rights to perform the requested operation.

�The Physical Presence Interface of this firmware does not support the requested method.

�This is an error mask to convert Platform Crypto Provider errors to win errors.

�The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational.

�The handle provided to the Platform Crypto Provider is invalid.

�A parameter provided to the Platform Crypto Provider is invalid.

�A provided flag to the Platform Crypto Provider is not supported.

�The requested operation is not supported by this Platform Crypto Provider.

�The buffer is too small to contain all data. No information has been written to the buffer.

�An unexpected internal error has occurred in the Platform Crypto Provider.

xThe authorization to use a provider object has failed.

The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack.

TThe referenced policy was not found.

TThe referenced profile was not found.

PThe validation was not successful.

�A Platform Crypto Device was not found. Operations that require a Platform Crypto Device will not be submitted.

�An attempt was made to import or load a key under an incorrect storage parent.

@The TPM key is not loaded.

lThe TPM key certification has not been generated.

LThe TPM key is not yet finalized.

\The TPM attestation challenge is not set.

TThe TPM key is not bound to PCR info.

LThe TPM key is already finalized.

`The TPM key usage policy is not supported.

TThe TPM key usage policy is invalid.

�There was a problem with the software key being imported into the TPM.

LThe TPM key is not authenticated.

@The TPM key is not an AIK.

LThe TPM key is not a signing key.

8The TPM is locked out.

`The claim type requested is not supported.

\The current TPM version is not supported.

LThe buffer lengths do not match.

�The RSA key creation is blocked on this TPM due to known security vulnerabilities.

lA ticket required to use a key was not provided.

�This key has a raw policy so the KSP can't authenticate against it.

�The TPM key's handle was unexpectedly invalidated due to a hardware or firmware issue.

hNo result associated with this instance exists.

(The TPM returned incomplete PCR results. This maybe due to an unsupported selection set. Attempt the read again with a different selection set.

�The rTPM context has been corrupted. The rTPM operation must be restarted.

�The rTPM target does not support remote processing of the specified TPM command.

�TPM related network operations are blocked as Zero Exhaust mode is enabled on client.

�The hypervisor does not support the operation because the specified hypercall code is not supported.

�The hypervisor does not support the operation because the encoding for the hypercall input register is not supported.

�The hypervisor could not perform the operation because a parameter has an invalid alignment.

�The hypervisor could not perform the operation because an invalid parameter was specified.

`Access to the specified object was denied.

�The hypervisor could not perform the operation because the partition is entering or in an invalid state.

pThe operation is not allowed in the current state.

�The hypervisor does not recognize the specified partition property.

�The specified value of a partition property is out of range or violates an invariant.

�There is not enough memory in the hypervisor pool to complete the operation.

�The maximum partition depth has been exceeded for the partition hierarchy.

�A partition with the specified partition Id does not exist.

�The hypervisor could not perform the operation because the specified VP index is invalid.

�The hypervisor could not perform the operation because the specified port identifier is invalid.

�The hypervisor could not perform the operation because the specified connection identifier is invalid.

pNot enough buffers were supplied to send a message.

|The previous virtual interrupt has not been acknowledged.

�A virtual processor is not in the correct state for the indicated operation.

�The previous virtual interrupt has already been acknowledged.

�The indicated partition is not in a valid state for saving or restoring.

The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled.

lThe 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.

dThe proximity domain information is invalid.

�An attempt to retrieve debugging data failed because none was available.

�The physical connection being used for debugging has not recorded any receive activity since the last operation.

|There are not enough resources to complete the operation.

pA hypervisor feature is not available to the user.

�The specified buffer was too small to contain all of the requested data.

TThe 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.

lValidation of CPUID data of the processor failed.

xValidation of XSAVE CPUID data of the processor failed.

tProcessor did not respond within the timeout period.

LSMX has been enabled in the BIOS.

�The hypervisor could not perform the operation because the specified LP index is invalid.

XThe supplied register value is invalid.

�The supplied virtual trust level is not in the correct state to perform the requested operation.

�No execute feature (NX) is not present or not enabled in the BIOS.

PThe supplied device ID is invalid.

|The operation is not allowed in the current device state.

�The supplied page request specifies a memory access that the guest does not have permissions to perform.

�A CPU group with the specified CPU group Id does not exist.

�The hypervisor could not perform the operation because the CPU group is entering or in an invalid state.

HThe requested operation failed.

�The hypervisor could not perform the operation because it is not allowed with nested virtualization active.

�There is not enough memory in the root partition's pool to complete the operation.

�The provided event log buffer was already marked as freed.

�There is not enough contiguous memory in the partition's pool to complete the operation.

TThe device is not in a device domain.

|The requested operation would result in a nested vm-exit.

xThe operation that was requested is pending completion.

�The requested access to the model specific register failed.

\No hypervisor is present on this system.

xThe SPI in the packet does not match a valid IPsec SA.

�Packet was received on an IPsec SA whose lifetime has expired.

�Packet was received on an IPsec SA that does not match the packet characteristics.

`Packet sequence number replay check failed.

tIPsec header and/or trailer in the packet is invalid.

DIPsec integrity check failed.

PIPsec dropped a clear text packet.

�IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.

dIPsec dropped a packet due to DoS throttling.

tIPsec DoS Protection matched an explicit block rule.

�IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.

�IPsec DoS Protection received an incorrectly formatted packet.

dIPsec DoS Protection failed to look up state.

�IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.

�IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.

,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.

�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.

�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.

�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.

�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.

�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.

�The partition name of the virtualization infrastructure driver exceeds the maximum.

�The message queue name of the virtualization infrastructure driver exceeds the maximum.

Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.

�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.

�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.

�A message queue with the same name already exists for the virtualization infrastructure driver.

�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.

�The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.

�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.

lThe 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.

�The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.

�The memory block for the virtualization infrastructure driver is already associated with a message queue.

�The handle is not a valid memory block handle for the virtualization infrastructure driver.

�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.

�The handle is not a valid message queue handle for the virtualization infrastructure driver.

�The handle is not a valid page range handle for the virtualization infrastructure driver.

(Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.

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.

�The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.

�Notifications cannot be created on the memory block because it is use.

�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.

�Cannot add a virtual processor to the partition because the maximum has been reached.

�Cannot stop the virtual processor immediately because of a pending intercept.

@Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

�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.

�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.

�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.

hThe 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.

�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.

�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.

�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.

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.

�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.

8Cannot 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.

dCannot 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.

TCannot 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.

�The specified VTL does not have the permission to access the resource.

PThe configuration database is full.

lThe configuration data on the disk is corrupted.

�The configuration on the disk is not insync with the in-memory configuration.

�A majority of disks failed to be updated with the new configuration.

TThe disk contains non-simple volumes.

�The same disk was specified more than once in the migration list.

DThe disk is already dynamic.

�The specified disk id is invalid. There are no disks with the specified disk id.

�The specified disk is an invalid disk. Operation cannot complete on an invalid disk.

�The specified disk(s) cannot be removed since it is the last remaining voter.

hThe specified disk has an invalid disk layout.

�The disk layout contains non-basic partitions which appear after basic partitions. This is an invalid disk layout.

�The disk layout contains partitions which are not cylinder aligned.

�The disk layout contains partitions which are smaller than the minimum size.

�The disk layout contains primary partitions in between logical drives. This is an invalid disk layout.

�The disk layout contains more than the maximum number of supported partitions.

�The specified disk is missing. The operation cannot complete on a missing disk.

LThe specified disk is not empty.

tThere is not enough usable space for this operation.

dThe force revectoring of bad sectors failed.

hThe specified disk has an invalid sector size.

�The specified disk set contains volumes which exist on disks outside of the set.

�A disk in the volume layout provides extents to more than one member of a plex.

�A disk in the volume layout provides extents to more than one plex.

hDynamic disks are not supported on this system.

xThe specified extent is already used by other volumes.

\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.

�The specified volume extent is not within the public region of the disk.

pThe specified volume extent is not sector aligned.

�The specified partition overlaps an EBR (the first track of an extended partition on a MBR disks).

�The specified extent lengths cannot be used to construct a volume with specified length.

pThe system does not support fault tolerant volumes.

`The specified interleave length is invalid.

xThere is already a maximum number of registered users.

�The specified member is already in-sync with the other active members. It does not need to be regenerated.

pThe same member index was specified more than once.

�The specified member index is greater or equal than the number of members in the volume plex.

�The specified member is missing. It cannot be regenerated.

�The specified member is not detached. Cannot replace a member which is not detached.

dThe specified member is already regenerating.

XAll disks belonging to the pack failed.

There are currently no registered users for notifications. The task number is irrelevant unless there are registered users.

�The specified notification user does not exist. Failed to unregister user for notifications.

The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications.

`The specified number of members is invalid.

`The specified number of plexes is invalid.

tThe specified source and target packs are identical.

�The specified pack id is invalid. There are no packs with the specified pack id.

�The specified pack is the invalid pack. The operation cannot complete with the invalid pack.

PThe specified pack name is invalid.

HThe specified pack is offline.

|The specified pack already has a quorum of healthy disks.

lThe pack does not have a quorum of healthy disks.

�The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported.

dFailed to update the disk's partition layout.

�The specified plex is already in-sync with the other active plexes. It does not need to be regenerated.

lThe same plex index was specified more than once.

�The specified plex index is greater or equal than the number of plexes in the volume.

�The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline.

HThe specified plex is missing.

dThe specified plex is currently regenerating.

PThe specified plex type is invalid.

lThe operation is only supported on RAID-5 plexes.

lThe operation is only supported on simple plexes.

�The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set.

There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications.

dThere is currently a transaction in process.

�An unexpected layout change occurred outside of the volume manager.

dThe specified volume contains a missing disk.

�The specified volume id is invalid. There are no volumes with the specified volume id.

XThe specified volume length is invalid.

�The specified size for the volume is not a multiple of the sector size.

tThe operation is only supported on mirrored volumes.

xThe specified volume does not have a retain partition.

LThe specified volume is offline.

tThe specified volume already has a retain partition.

`The specified number of extents is invalid.

�All disks participating to the volume must have the same sector size.

PThe boot disk experienced failures.

\The configuration of the pack is offline.

\The configuration of the pack is online.

`The specified pack is not the primary pack.

�All disks failed to be updated with the new content of the log.

pThe specified number of disks in a plex is invalid.

�The specified number of disks in a plex member is invalid.

pThe operation is not supported on mirrored volumes.

�The operation is only supported on simple and spanned plexes.

LThe pack has no valid log copies.

PA primary pack is already present.

\The specified number of disks is invalid.

dThe system does not support mirrored volumes.

`The system does not support RAID-5 volumes.

xEntries enumerated have exceeded the allowed threshold.

�The virtual hard disk is corrupted. The virtual hard disk drive footer is missing.

�The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum.

�The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted.

�The system does not recognize the file format of this virtual hard disk.

�The version does not support this version of the file format.

�The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum.

�The system does not support this version of the virtual hard disk.This version of the sparse header is not supported.

�The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt.

Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk.

�The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt.

�The system does not support this version of the virtual hard disk. The block size is invalid.

�The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk.

The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk.

The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk.

4The 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.

tFailed to read the metadata of the virtual hard disk.

|Failed to write to the metadata of the virtual hard disk.

hThe size of the virtual hard disk is not valid.

tThe file size of this virtual hard disk is not valid.

�A virtual disk support provider for the specified file was not found.

\The specified disk is not a virtual disk.

@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.

$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.

�The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain.

�The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain.

dThe 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.

�The requested operation cannot be performed on a virtual disk of this type.

�The requested operation cannot be performed on the virtual disk in its current state.

�The sector size of the physical disk on which the virtual disk resides is not supported.

hThe disk is already owned by a different owner.

XThe disk must be offline or read-only.

|Change Tracking is not initialized for this virtual disk.

�Size of change tracking file exceeded the maximum size limit.

�VHD file is changed due to compaction, expansion, or offline updates.

HChange 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.

�Change Tracking file for the virtual disk is not in a valid state.

�There is not enough space in the virtual disk file for the provided metadata item.

xThe specified change tracking identifier is not valid.

�Change tracking is disabled for the specified virtual hard disk, so no change tracking information is available.

�There is no change tracking data available associated with the specified change tracking identifier.

�The requested resize operation might truncate user data residing on the virtual disk.

The minimum safe size of the virtual disk could not be determined. This may be due to a missing or corrupt partition table.

�The size of the virtual disk cannot be safely reduced further.

�The Resume Key Filter could not find the resume key supplied for the operation.

�The Resume Key Filter found an existing resume key that matches the one supplied for the handle.

�The Resume Key Filter data blob attached to the handle is full. No more space is available.

�The Resume Key Filter handle store is full. No more resume handles can be accepted.

The Resume Key Filter failed the operation because the file is temporarily blocked pending the resume of existing handles on the file.

PThe Resume Key Filter found an existing resume key that matches the one supplied on a handle that's active/open. The operation requires an inactive/closed handle.

\The operation must be restarted by RDBSS.

XThe operation must continue processing.

�The operation must be posted to a thread to be retried at passive IRQL.

�The caller must retry by looking up the object in the name table.

|The attribute handle given was not valid on this server.

DThe attribute cannot be read.

LThe attribute cannot be written.

HThe attribute PDU was invalid.

�The attribute requires authentication before it can be read or written.

�Attribute server does not support the request received from the client.

pOffset specified was past the end of the attribute.

�The attribute requires authorization before it can be read or written.

\Too many prepare writes have been queued.

�No attribute found within the given attribute handle range.

�The attribute cannot be read or written using the Read Blob Request.

�The Encryption Key Size used for encrypting this link is insufficient.

|The attribute value length is invalid for the operation.

The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested.

�The attribute requires encryption before it can be read or written.

�The attribute type is not a supported grouping attribute as defined by a higher layer specification.

hInsufficient Resources to complete the request.

�An error that lies in the reserved range has been received.

�Secure Boot detected that rollback of protected data has been attempted.

�The value is protected by Secure Boot policy and cannot be modified or deleted.

PThe Secure Boot policy is invalid.

�A new Secure Boot policy did not contain the current publisher on its update list.

�The Secure Boot policy is either not signed or is signed by a non-trusted signer.

�Secure Boot requires that certain files and drivers are not replaced by other files or drivers.

�The Secure Boot Supplemental Policy file was not authorized on this machine.

|The Supplemental Policy is not recognized on this device.

�The Antirollback version was not found in the Secure Boot Policy.

�The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device.

�The Secure Boot policy file has an older Antirollback Version than this device.

�The Secure Boot policy file does not match the upgraded legacy policy.

�The Secure Boot policy file is required but could not be found.

�Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy.

�Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy.

�PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode.

�HD Audio widget encountered an unexpected empty connection list.

�HD Audio widget does not support the connection list parameter.

lNo HD Audio subdevices were successfully created.

�An unexpected NULL pointer was encountered in a linked list.

�Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled.

�The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS.

�The VSM encryption key could not be released because the minimum Code Integrity policy version was not met.

�VSM failed to seal to measurements included in the firmware update driver package.

�The bootfile is too small to support persistent snapshots.

�Activation of persistent snapshots on this volume took longer than was allowed.

�The operation was preempted by a higher priority operation. It must be resumed later.

�The proper error code with sense data was stored on server side.

|The requested error data is not available on the server.

�Unit Attention data is available for the initiator to query.

�The data capacity of the device has changed, resulting in a Unit Attention condition.

�A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition.

�A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition.

�A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition.

�The data storage format of the device has changed, resulting in a Unit Attention condition.

�The current initiator is not allowed to perform the SCSI command because of a reservation conflict.

Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks.

|The server version does not match the requested version.

�The requested operation cannot be performed on the virtual disk as it is currently used in shared mode.

�Invalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures.

�The requested operation failed due to a missing backing storage file.

�Failed to negotiate a preauthentication integrity hash function.

�The current cluster functional level does not support this SMB dialect.

�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.

dFailed to negotiate a signing hash function.

�The SMB client was denied access to the SMB server during mutual authentication.

�The specified fault domain type or combination of minimum / maximum fault domain type is not valid.

`The specified resiliency type is not valid.

�The sector size of the physical disk is not supported by the storage pool.

�The value for fault tolerance is outside of the supported range of values.

�The number of data copies requested is outside of the supported range of values.

�The value for interleave length is outside of the supported range of values or is not a power of 2.

�The number of columns specified is outside of the supported range of values.

�There were not enough physical disks to complete the requested operation.

\Extended error information is available.

dThe specified provisioning type is not valid.

�The allocation size is outside of the supported range of values.

�Enclosure awareness is not supported for this virtual disk.

�The write cache size is outside of the supported range of values.

�The value for number of groups is outside of the supported range of values.

�The OperationalState of the physical disk is invalid for this operation.

TA column's state needs to be updated.

LAn extent needs to be allocated.

TThe metadata version is unsupported.

HThe metadata read was corrupt.

,The DRT is full.

@An inconsistency was found.

4The log is not ready.

PNo good copy of data was available.

8The drive is not ready.

LThe data on this drive is stale.

TThe data on this drive has been lost.

\The specified log entry is not complete.

TThe specified log entry is not valid.

LA slab needs to be marked dirty.

\A persisted memory buffer was not found.

XA persisted memory buffer is too small.

tA persisted memory buffer has an unsupported version.

lA persisted memory buffer contains invalid data.

pThe cache metadata needs to be written and flushed.

0The cache is full.

8Repair is in progress.

pThe command was not recognized by the security core

�System Integrity detected that policy rollback has been attempted.

`System Integrity policy has been violated.

XThe System Integrity policy is invalid.

�The System Integrity policy is either not signed or is signed by a non-trusted signer.

|The number of System Integrity policies is out of limit.

�The Code Integrity supplemental policy is not authorized by a Code Integrity base policy.

�System Integrity policy has been violated. Malicious binary reputation.

�System Integrity policy has been violated. Potentially unwanted application.

�System Integrity policy has been violated. Dangerous file extension from the web.

�System Integrity policy has been violated. Unable to contact reputation service for unknown file.

LNo applicable app licenses found.

8CLiP license not found.

HCLiP device license not found.

XCLiP license has an invalid signature.

dCLiP keyholder license is invalid or missing.

<CLiP license has expired.

dCLiP license is signed by an unknown source.

@CLiP license is not signed.

dCLiP license hardware ID is out of tolerance.

�CLiP license device ID does not match the device ID in the bound device license.

�The Platform Manifest file was not authorized on this machine.

\The Platform Manifest file was not valid.

�The file is not authorized on this platform because an entry was not found in the Platform Manifest.

�The catalog is not authorized on this platform because an entry was not found in the Platform Manifest.

�The file is not authorized on this platform because a Binary ID was not found in the embedded signature.

pNo active Platform Manifest exists on this system.

pThe Platform Manifest file was not properly signed.

�The condition supplied for the app execution request was not satisfied, so the request was not performed.

�The supplied handle has been invalidated and may not be used for the requested operation.

�The supplied host generation has been invalidated and may not be used for the requested operation.

An attempt to register a process failed because the target host was not in a valid state to receive process registrations.

�The host is not in a valid state to support the execution request.

�The operation was not completed because a required resource donor was not found for the host.

�The operation was not completed because an unexpected host ID was encountered.

�The operation was not completed because the specified user was not known to the service.

lThe application is blocked by app compat policy.

�The caller specified wait timed out before the operation completed.

�The caller specified wait timed out before the operation completed because a host termination is in queued.

�The caller specified wait timed out before the operation completed because a licensing operation is being performed.

�The caller specified wait timed out before the operation completed because resources are being acquired.

dThis operation is not allowed across unions.

�This operation is not allowed to have a destination outside of a union.

�This file has one or more hard links in the scratch layer.

�The tombstone cannot be created in or transitioned to the given state.

|This union has attached layers preventing this operation.

�A union layer root cannot be a descendant of another layer root.

`A union with this union ID already exists.

�The union this operation is being performed on is inactive.

pThere are too many layers to construct this union.

�4VS_VERSION_INFO��
�|O
�|O?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationB
FileDescriptionNT Layer DLLn'FileVersion10.0.20348.5020 (WinBuild.160101.0800)4
InternalNamentdll.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.DOriginalFilenamentdll.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.20348.5020DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD

Youez - 2016 - github.com/yon3zu
LinuXploit