Microsoft error codes

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

An assertion failure has occurred.

An error occurred in the ACPI subsystem.

WOW Assertion Error.

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.

A IRQ translator failed to translate resources.

Driver %2 returned invalid ID for a child device (%3).

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

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

{Media Changed} The media may have changed.

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

The create operation stopped after reaching a symbolic link.

A long jump has been executed.

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

The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?

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?

Debugger did not handle the exception.

Debugger will reply later.

Debugger cannot provide handle.

Debugger terminated thread.

Debugger terminated process.

Debugger got control C.

Debugger printed exception on control C.

Debugger received RIP exception.

Debugger received control break.

Debugger command communication exception.

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

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

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

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

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

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