Win32Exceptions

Here is a list of all default win32 exceptions.

Error NumberHexError Text
-214748364780000001Not implemented
-214748364680000002Ran out of memory
-214748364580000003One or more arguments are invalid
-214748364480000004No such interface supported
-214748364380000005Invalid pointer
-214748364280000006Invalid handle
-214748364180000007Operation aborted
-214748364080000008Unspecified error
-214748363980000009General access denied error
-21474836388000000AThe data necessary to complete this operation is not yet available
-21474836378000000BThe operation attempted to access data outside the valid range
-21474836368000000CA concurrent or interleaved operation changed the state of the object
-21474836358000000DAn illegal state change was requested
-21474836348000000EA method was called at an unexpected time
-21474836338000000FTypename or Namespace was not found in metadata file
-214748363280000010Name is an existing namespace rather than a typename
-214748363180000011Typename has an invalid format
-214748363080000012Metadata file is invalid or corrupted
-214748362980000013The object has been closed
-214748362880000014Only one thread may access the object during a write operation
-214748362780000015Operation is prohibited during change notification
-214748362680000016The text associated with this error code could not be found
-214748362580000017String not null terminated
-214748362480000018A delegate was assigned when not allowed
-214748362380000019An async operation was not properly started
-21474836228000001AThe application is exiting and cannot service this request
-21474836218000001BThe application view is exiting and cannot service this request
-21474836208000001CThe object must support the IAgileObject interface
-21474836198000001DActivating a single-threaded class from MTA is not supported
-21474836188000001EThe object has been committed
-21474836178000001FA COM call to an ASTA was blocked because the call chain originated in or passed through another ASTA. This call pattern is deadlock-prone and disallowed by apartment call control
-214748361680000020A universal application process cannot activate a packaged WinRT server that is declared to run full trust
-214748361580000021A full trust packaged application process cannot activate a packaged WinRT server unless it is also declared to run full trust
-214746726380004001Not implemented
-214746726280004002No such interface supported
-214746726180004003Invalid pointer
-214746726080004004Operation aborted
-214746725980004005Unspecified error
-214746725880004006Thread local storage failure
-214746725780004007Get shared memory allocator failure
-214746725680004008Get memory allocator failure
-214746725580004009Unable to initialize class cache
-21474672548000400AUnable to initialize RPC services
-21474672538000400BCannot set thread local storage channel control
-21474672528000400CCould not allocate thread local storage channel control
-21474672518000400DThe user supplied memory allocator is unacceptable
-21474672508000400EThe OLE service mutex already exists
-21474672498000400FThe OLE service file mapping already exists
-214746724880004010Unable to map view of file for OLE service
-214746724780004011Failure attempting to launch OLE service
-214746724680004012There was an attempt to call CoInitialize a second time while single threaded
-214746724580004013A Remote activation was necessary but was not allowed
-214746724480004014A Remote activation was necessary but the server name provided was invalid
-214746724380004015The class is configured to run as a security id different from the caller
-214746724280004016Use of Ole1 services requiring DDE windows is disabled
-214746724180004017A RunAs specification must be \ or simply
-214746724080004018The server process could not be started. The pathname may be incorrect
-214746723980004019The server process could not be started as the configured identity. The pathname may be incorrect or unavailable
-21474672388000401AThe server process could not be started because the configured identity is incorrect. Check the username and password
-21474672378000401BThe client is not allowed to launch this server
-21474672368000401CThe service providing this server could not be started
-21474672358000401DThis computer was unable to communicate with the computer providing the server
-21474672348000401EThe server did not respond after being launched
-21474672338000401FThe registration information for this server is inconsistent or incomplete
-214746723280004020The registration information for this interface is inconsistent or incomplete
-214746723180004021The operation attempted is not supported
-214746723080004022A dll must be loaded
-214746722980004023A Microsoft Software Installer error was encountered
-214746722880004024The specified activation could not occur in the client context as specified
-214746722780004025Activations on the server are paused
-214746722680004026Activations on the server are not paused
-214746722580004027The component or application containing the component has been disabled
-214746722480004028The common language runtime is not available
-214746722380004029The thread-pool rejected the submitted asynchronous work
-21474672228000402AThe server started
-21474672218000402BUnable to complete the call since there is no COM+ security context inside IObjectControl.Activate
-214746721680004030The provided tracker configuration is invalid
-214746721580004031The provided thread pool configuration is invalid
-214746721480004032The provided side-by-side configuration is invalid
-214746721380004033The server principal name (SPN) obtained during security negotiation is malformed
-214746721280004034The caller failed to revoke a per-apartment registration before apartment shutdown
-214746721180004035The object has been rundown by the stub manager while there are external clients
-21474181138000FFFFCatastrophic failure
-214741811180010001Call was rejected by callee
-214741811080010002Call was canceled by the message filter
-214741810980010003The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage
-214741810880010004The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call
-214741810780010005It is illegal to call out while inside message filter
-214741810680010006The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid
-214741810580010007The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed
-214741810480010008The caller (client) disappeared while the callee (server) was processing a call
-214741810380010009The data packet with the marshalled parameter data is incorrect
-21474181028001000AThe call was not transmitted properly; the message queue was full and was not emptied after yielding
-21474181018001000BThe client (caller) cannot marshall the parameter data - low memory
-21474181008001000CThe client (caller) cannot unmarshall the return data - low memory
-21474180998001000DThe server (callee) cannot marshall the return data - low memory
-21474180988001000EThe server (callee) cannot unmarshall the parameter data - low memory
-21474180978001000FReceived data is invalid; could be server or client data
-214741809680010010A particular parameter is invalid and cannot be (un)marshalled
-214741809580010011There is no second outgoing call on same channel in DDE conversation
-214741809480010012The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute
-214741785680010100System call failed
-214741785580010101Could not allocate some required resource (memory
-214741785480010102Attempted to make calls on more than one thread in single threaded mode
-214741785380010103The requested interface is not registered on the server object
-214741785280010104RPC could not call the server or could not return the results of calling the server
-214741785180010105The server threw an exception
-214741785080010106Cannot change thread mode after it is set
-214741784980010107The method called does not exist on the server
-214741784880010108The object invoked has disconnected from its clients
-214741784780010109The object invoked chose not to process the call now. Try again later
-21474178468001010AThe message filter indicated that the application is busy
-21474178458001010BThe message filter rejected the call
-21474178448001010CA call control interfaces was called with invalid data
-21474178438001010DAn outgoing call cannot be made since the application is dispatching an input-synchronous call
-21474178428001010EThe application called an interface that was marshalled for a different thread
-21474178418001010FCoInitialize has not been called on the current thread
-214741784080010110The version of OLE on the client and server machines does not match
-214741783980010111OLE received a packet with an invalid header
-214741783880010112OLE received a packet with an invalid extension
-214741783780010113The requested object or interface does not exist
-214741783680010114The requested object does not exist
-214741783580010115OLE has sent a request and is waiting for a reply
-214741783480010116OLE is waiting before retrying a request
-214741783380010117Call context cannot be accessed after call completed
-214741783280010118Impersonate on unsecure calls is not supported
-214741783180010119Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized
-21474178308001011ANo security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server
-21474178298001011BAccess is denied
-21474178288001011CRemote calls are not allowed for this process
-21474178278001011DThe marshaled interface data packet (OBJREF) has an invalid or unknown format
-21474178268001011ENo context is associated with this call. This happens for some custom marshalled calls and on the client side of the call
-21474178258001011FThis operation returned because the timeout period expired
-214741782480010120There are no synchronize objects to wait on
-214741782380010121Full subject issuer chain SSL principal name expected from the server
-214741782280010122Principal name is not a valid MSSTD name
-214741782180010123Unable to impersonate DCOM client
-214741782080010124Unable to obtain server's security context
-214741781980010125Unable to open the access token of the current thread
-214741781880010126Unable to obtain user info from an access token
-214741781780010127The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method
-214741781680010128Unable to obtain the client's security blanket
-214741781580010129Unable to set a discretionary ACL into a security descriptor
-21474178148001012AThe system function
-21474178138001012BEither NetAccessDel or NetAccessAdd returned an error code
-21474178128001012COne of the trustee strings provided by the user did not conform to the \ syntax and it was not the "*" string
-21474178118001012DOne of the security identifiers provided by the user was invalid
-21474178108001012EUnable to convert a wide character trustee string to a multibyte trustee string
-21474178098001012FUnable to find a security identifier that corresponds to a trustee string provided by the user
-214741780880010130The system function
-214741780780010131Unable to find a trustee name that corresponds to a security identifier provided by the user
-214741780680010132The system function
-214741780580010133Unable to set or reset a serialization handle
-214741780480010134Unable to obtain the Windows directory
-214741780380010135Path too long
-214741780280010136Unable to generate a uuid
-214741780180010137Unable to create file
-214741780080010138Unable to close a serialization handle or a file handle
-214741779980010139The number of ACEs in an ACL exceeds the system limit
-21474177988001013ANot all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream
-21474177978001013BThe version of ACL format in the stream is not supported by this implementation of IAccessControl
-21474177968001013CUnable to open the access token of the server process
-21474177958001013DUnable to decode the ACL in the stream provided by the user
-21474177938001013FThe COM IAccessControl object is not initialized
-214741779280010140Call Cancellation is disabled
-21473525778001FFFFAn internal error occurred
-214735257580020001Unknown interface
-214735257380020003Member not found
-214735257280020004Parameter not found
-214735257180020005Type mismatch
-214735257080020006Unknown name
-214735256980020007No named arguments
-214735256880020008Bad variable type
-214735256780020009Exception occurred
-21473525668002000AOut of present range
-21473525658002000BInvalid index
-21473525648002000CUnknown language
-21473525638002000DMemory is locked
-21473525628002000EInvalid number of parameters
-21473525618002000FParameter not optional
-214735256080020010Invalid callee
-214735255980020011Does not support a collection
-214735255880020012Division by zero
-214735255780020013Buffer too small
-214731978680028016Buffer too small
-214731978580028017Field name not defined in the record
-214731978480028018Old format or invalid type library
-214731978380028019Old format or invalid type library
-21473197808002801CError accessing the OLE registry
-21473197798002801DLibrary not registered
-214731976980028027Bound to unknown type
-214731976880028028Qualified name disallowed
-214731976780028029Invalid forward reference
-21473197668002802AType mismatch
-21473197658002802BElement not found
-21473197648002802CAmbiguous name
-21473197638002802DName already exists in the library
-21473197628002802EUnknown LCID
-21473197618002802FFunction not defined in specified DLL
-2147317571800288BDWrong module kind for the operation
-2147317563800288C5Size may not exceed 64K
-2147317562800288C6Duplicate ID in inheritance hierarchy
-2147317553800288CFIncorrect inheritance depth in standard OLE hmember
-214731657680028CA0Type mismatch
-214731657580028CA1Invalid number of arguments
-214731657480028CA2I/O Error
-214731657380028CA3Error creating unique tmp file
-214731256680029C4AError loading type library/DLL
-214731250980029C83Inconsistent property functions
-214731250880029C84Circular dependency between types/modules
-214728703980030001Unable to perform requested operation
-214728703880030002%1 could not be found
-214728703780030003The path %1 could not be found
-214728703680030004There are insufficient resources to open another file
-214728703580030005Access Denied
-214728703480030006Attempted an operation on an invalid object
-214728703280030008There is insufficient memory available to complete operation
-214728703180030009Invalid pointer error
-214728702280030012There are no more entries to return
-214728702180030013Disk is write-protected
-214728701580030019An error occurred during a seek operation
-21472870118003001DA disk error occurred during a write operation
-21472870108003001EA disk error occurred during a read operation
-214728700880030020A share violation has occurred
-214728700780030021A lock violation has occurred
-214728696080030050%1 already exists
-214728695380030057Invalid parameter error
-214728692880030070There is insufficient disk space to complete operation
-2147286800800300F0Illegal write of non-simple property to simple property set
-2147286790800300FAAn API call exited abnormally
-2147286789800300FBThe file %1 is not a valid compound file
-2147286788800300FCThe name %1 is not valid
-2147286787800300FDAn unexpected error occurred
-2147286786800300FEThat function is not implemented
-2147286785800300FFInvalid flag error
-214728678480030100Attempted to use an object that is busy
-214728678380030101The storage has been changed since the last commit
-214728678280030102Attempted to use an object that has ceased to exist
-214728678180030103Can't save
-214728678080030104The compound file %1 was produced with an incompatible version of storage
-214728677980030105The compound file %1 was produced with a newer version of storage
-214728677880030106Share.exe or equivalent is required for operation
-214728677780030107Illegal operation called on non-file based storage
-214728677680030108Illegal operation called on object with extant marshallings
-214728677580030109The docfile has been corrupted
-214728676880030110OLE32.DLL has been loaded at the wrong address
-214728676780030111The compound file is too large for the current implementation
-214728676680030112The compound file was not created with the STGM_SIMPLE flag
-214728652780030201The file download was aborted abnormally. The file is incomplete
-214728652680030202The file download has been terminated
-214728652080030208The specified firmware slot is invalid
-214728651980030209The specified firmware image is invalid
-21472865188003020AThe storage device is unresponsive
-214728626780030305Generic Copy Protection Error
-214728626680030306Copy Protection Error - DVD CSS Authentication failed
-214728626580030307Copy Protection Error - The given sector does not have a valid CSS key
-214728626480030308Copy Protection Error - DVD session key not established
-214728626380030309Copy Protection Error - The read failed because the sector is encrypted
-21472862628003030ACopy Protection Error - The current DVD's region does not correspond to the region setting of the drive
-21472862618003030BCopy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted
-214722150480040000Invalid OLEVERB structure
-214722150380040001Invalid advise flags
-214722150280040002Can't enumerate any more
-214722150180040003This implementation doesn't take advises
-214722150080040004There is no connection for this connection ID
-214722149980040005Need to run the object to perform this operation
-214722149880040006There is no cache to operate on
-214722149780040007Uninitialized object
-214722149680040008Linked object's source class has changed
-214722149580040009Not able to get the moniker of the object
-21472214948004000ANot able to bind to the source
-21472214938004000BObject is static; operation not allowed
-21472214928004000CUser canceled out of save dialog
-21472214918004000DInvalid rectangle
-21472214908004000Ecompobj.dll is too old for the ole2.dll initialized
-21472214898004000FInvalid window handle
-214722148880040010Object is not in any of the inplace active states
-214722148780040011Not able to convert object
-214722148680040012Not able to perform the operation because object is not given storage yet
-214722140480040064Invalid FORMATETC structure
-214722140380040065Invalid DVTARGETDEVICE structure
-214722140280040066Invalid STDGMEDIUM structure
-214722140180040067Invalid STATDATA structure
-214722140080040068Invalid lindex
-214722139980040069Invalid tymed
-21472213988004006AInvalid clipboard format
-21472213978004006BInvalid aspect(s)
-21472213968004006CtdSize parameter of the DVTARGETDEVICE structure is invalid
-21472213958004006DObject doesn't support IViewObject interface
-214722124880040100Trying to revoke a drop target that has not been registered
-214722124780040101This window has already been registered as a drop target
-214722124680040102Invalid window handle
-214722124580040103A drag operation is already in progress
-214722123280040110Class does not support aggregation (or class object is remote)
-214722123180040111ClassFactory cannot supply requested class
-214722123080040112Class is not licensed for use
-214722118480040140Error drawing view
-214722116880040150Could not read key from registry
-214722116780040151Could not write key to registry
-214722116680040152Could not find the key in the registry
-214722116580040153Invalid value for registry
-214722116480040154Class not registered
-214722116380040155Interface not registered
-214722116280040156Threading model entry is not valid
-214722116180040157A registration in a package violates package-specific policies
-214722115280040160CATID does not exist
-214722115180040161Description not found
-214722114880040164No package in the software installation data in the Active Directory meets this criteria
-214722114780040165Deleting this will break the referential integrity of the software installation data in the Active Directory
-214722114680040166The CLSID was not found in the software installation data in the Active Directory
-214722114580040167The software installation data in the Active Directory is corrupt
-214722114480040168There is no software installation data in the Active Directory
-214722114380040169There is no software installation data object in the Active Directory
-21472211428004016AThe software installation data object in the Active Directory already exists
-21472211418004016BThe path to the software installation data in the Active Directory is not correct
-21472211408004016CA network error interrupted the operation
-21472211398004016DThe size of this object exceeds the maximum size set by the Administrator
-21472211388004016EThe schema for the software installation data in the Active Directory does not match the required schema
-21472211378004016FAn error occurred in the software installation data in the Active Directory
-214722113680040170Cache not updated
-214722112080040180No verbs for OLE object
-214722111980040181Invalid verb for OLE object
-2147221088800401A0Undo is not available
-2147221087800401A1Space for tools is not available
-2147221056800401C0OLESTREAM Get method failed
-2147221055800401C1OLESTREAM Put method failed
-2147221054800401C2Contents of the OLESTREAM not in correct format
-2147221053800401C3There was an error in a Windows GDI call while converting the bitmap to a DIB
-2147221052800401C4Contents of the IStorage not in correct format
-2147221051800401C5Contents of IStorage is missing one of the standard streams
-2147221050800401C6There was an error in a Windows GDI call while converting the DIB to a bitmap
-2147221040800401D0OpenClipboard Failed
-2147221039800401D1EmptyClipboard Failed
-2147221038800401D2SetClipboard Failed
-2147221037800401D3Data on clipboard is invalid
-2147221036800401D4CloseClipboard Failed
-2147221024800401E0Moniker needs to be connected manually
-2147221023800401E1Operation exceeded deadline
-2147221022800401E2Moniker needs to be generic
-2147221021800401E3Operation unavailable
-2147221020800401E4Invalid syntax
-2147221019800401E5No object for moniker
-2147221018800401E6Bad extension for file
-2147221017800401E7Intermediate operation failed
-2147221016800401E8Moniker is not bindable
-2147221015800401E9Moniker is not bound
-2147221014800401EAMoniker cannot open file
-2147221013800401EBUser input required for operation to succeed
-2147221012800401ECMoniker class has no inverse
-2147221011800401EDMoniker does not refer to storage
-2147221010800401EENo common prefix
-2147221009800401EFMoniker could not be enumerated
-2147221008800401F0CoInitialize has not been called
-2147221007800401F1CoInitialize has already been called
-2147221006800401F2Class of object cannot be determined
-2147221005800401F3Invalid class string
-2147221004800401F4Invalid interface string
-2147221003800401F5Application not found
-2147221002800401F6Application cannot be run more than once
-2147221001800401F7Some error in application program
-2147221000800401F8DLL for class not found
-2147220999800401F9Error in the DLL
-2147220998800401FAWrong OS or OS version for application
-2147220997800401FBObject is not registered
-2147220996800401FCObject is already registered
-2147220995800401FDObject is not connected to server
-2147220994800401FEApplication was launched but it didn't register a class factory
-2147220993800401FFObject has been released
-214722099180040201An event was unable to invoke any of the subscribers
-214722098980040203A syntax error occurred trying to evaluate a query string
-214722098880040204An invalid field name was used in a query string
-214722098780040205An unexpected exception was raised
-214722098680040206An unexpected internal error was detected
-214722098580040207The owner SID on a per-user subscription doesn't exist
-214722098480040208A user-supplied component or subscriber raised an exception
-214722098380040209An interface has too many methods to fire events from
-21472209828004020AA subscription cannot be stored unless its event class already exists
-21472209818004020BNot all the objects requested could be removed
-21472209808004020CCOM+ is required for this operation
-21472209798004020DCannot modify or delete an object that was not added using the COM+ Admin SDK
-21472209788004020ECannot modify or delete an object that was added using the COM+ Admin SDK
-21472209778004020FThe event class for this subscription is in an invalid partition
-214722097680040210The owner of the PerUser subscription is not logged on to the system specified
-214722097480040212TabletPC inking error code. No default tablet
-214722096780040219TabletPC inking error code. An invalid input rectangle was specified
-21472209658004021BTabletPC inking error code. Unknown property specified
-214722095880040222TabletPC inking error code. The stroke object was deleted
-214722095780040223TabletPC inking error code. Initialization failure
-214722094280040232TabletPC inking error code. The data required for the operation was not supplied
-214722094180040233TabletPC inking error code. Invalid packet description
-214722093980040235TabletPC inking error code. There are no handwriting recognizers registered
-214722093880040236TabletPC inking error code. User does not have the necessary rights to read recognizer information
-214722093780040237TabletPC inking error code. API calls were made in an incorrect order
-214722093680040238TabletPC inking error code. Queue is full
-214722093580040239TabletPC inking error code. RtpEnabled called multiple times
-21472209348004023ATabletPC inking error code. A recognizer returned invalid data
-214722092780040241TabletPC inking error code. The property was not found
-214721663180041309Trigger not found
-21472166308004130AOne or more of the properties that are needed to run this task have not been set
-21472166298004130BThere is no running instance of the task
-21472166288004130CThe Task Scheduler Service is not installed on this computer
-21472166278004130DThe task object could not be opened
-21472166268004130EThe object is either an invalid task object or is not a task object
-21472166258004130FNo account information could be found in the Task Scheduler security database for the task indicated
-214721662480041310Unable to establish existence of the account specified
-214721662380041311Corruption was detected in the Task Scheduler security database; the database has been reset
-214721662280041312Task Scheduler security services are available only on Windows NT
-214721662180041313The task object version is either unsupported or invalid
-214721662080041314The task has been configured with an unsupported combination of account settings and run time options
-214721661980041315The Task Scheduler Service is not running
-214721661880041316The task XML contains an unexpected node
-214721661780041317The task XML contains an element or attribute from an unexpected namespace
-214721661680041318The task XML contains a value which is incorrectly formatted or out of range
-214721661580041319The task XML is missing a required element or attribute
-21472166148004131AThe task XML is malformed
-21472166118004131DThe task XML contains too many nodes of the same type
-21472166108004131EThe task cannot be started after the trigger's end boundary
-21472166098004131FAn instance of this task is already running
-214721660880041320The task will not run because the user is not logged on
-214721660780041321The task image is corrupt or has been tampered with
-214721660680041322The Task Scheduler service is not available
-214721660580041323The Task Scheduler service is too busy to handle your request. Please try again later
-214721660480041324The Task Scheduler service attempted to run the task
-214721660280041326The task is disabled
-214721660180041327The task has properties that are not compatible with previous versions of Windows
-214721660080041328The task settings do not allow the task to start on demand
-214721659980041329The combination of properties that task is using is not compatible with the scheduling engine
-214721659280041330The task definition uses a deprecated feature
-21471682568004D000Another single phase resource manager has already been enlisted in this transaction
-21471682558004D001A retaining commit or abort is not supported
-21471682548004D002The transaction failed to commit for an unknown reason. The transaction was aborted
-21471682538004D003Cannot call commit on this transaction object because the calling application did not initiate the transaction
-21471682528004D004Instead of committing
-21471682518004D005Instead of aborting
-21471682508004D006Some of the states of the resource were committed while others were aborted
-21471682498004D007Some of the states of the resource may have been committed while others may have been aborted
-21471682488004D008The requested isolation level is not valid or supported
-21471682478004D009The transaction manager doesn't support an asynchronous operation for this method
-21471682468004D00AUnable to enlist in the transaction
-21471682458004D00BThe requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation
-21471682448004D00CThere is no resource presently associated with this enlistment
-21471682438004D00DThe transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers
-21471682428004D00EThe transaction has already been implicitly or explicitly committed or aborted
-21471682418004D00FAn invalid combination of flags was specified
-21471682408004D010The resource manager id is not associated with this transaction or the transaction manager
-21471682398004D011This method was called in the wrong state
-21471682388004D012The indicated unit of work does not match the unit of work expected by the resource manager
-21471682378004D013An enlistment in a transaction already exists
-21471682368004D014An import object for the transaction could not be found
-21471682358004D015The transaction cookie is invalid
-21471682348004D016The transaction status is in doubt. A communication failure occurred
-21471682338004D017A time-out was specified
-21471682328004D018The requested operation is already in progress for the transaction
-21471682318004D019The transaction has already been aborted
-21471682308004D01AThe Transaction Manager returned a log full error
-21471682298004D01BThe Transaction Manager is not available
-21471682288004D01CA connection with the transaction manager was lost
-21471682278004D01DA request to establish a connection with the transaction manager was denied
-21471682268004D01EResource manager reenlistment to determine transaction status timed out
-21471682258004D01FThis transaction manager failed to establish a connection with another TIP transaction manager
-21471682248004D020This transaction manager encountered a protocol error with another TIP transaction manager
-21471682238004D021This transaction manager could not propagate a transaction from another TIP transaction manager
-21471682228004D022The Transaction Manager on the destination machine is not available
-21471682218004D023The Transaction Manager has disabled its support for TIP
-21471682208004D024The transaction manager has disabled its support for remote/network transactions
-21471682198004D025The partner transaction manager has disabled its support for remote/network transactions
-21471682188004D026The transaction manager has disabled its support for XA transactions
-21471682178004D027MSDTC was unable to read its configuration information
-21471682168004D028MSDTC was unable to load the dtc proxy dll
-21471682158004D029The local transaction has aborted
-21471682148004D02AThe MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process
-21471682138004D02BThe MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process
-21471682128004D02CThe MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions
-21471681288004D080XACT_E_CLERKNOTFOUND
-21471681278004D081XACT_E_CLERKEXISTS
-21471681268004D082XACT_E_RECOVERYINPROGRESS
-21471681258004D083XACT_E_TRANSACTIONCLOSED
-21471681248004D084XACT_E_INVALIDLSN
-21471681238004D085XACT_E_REPLAYREQUEST
-21471680008004D100The request to connect to the specified transaction coordinator was denied
-21471679998004D101The maximum number of enlistments for the specified transaction has been reached
-21471679988004D102A resource manager with the same identifier is already registered with the specified transaction coordinator
-21471679978004D103The prepare request given was not eligible for single phase optimizations
-21471679968004D104RecoveryComplete has already been called for the given resource manager
-21471679958004D105The interface call made was incorrect for the current state of the protocol
-21471679948004D106xa_open call failed for the XA resource
-21471679938004D107xa_recover call failed for the XA resource
-21471679928004D108The Logical Unit of Work specified cannot be found
-21471679918004D109The specified Logical Unit of Work already exists
-21471679908004D10ASubordinate creation failed. The specified Logical Unit of Work was not connected
-21471679898004D10BA transaction with the given identifier already exists
-21471679888004D10CThe resource is in use
-21471679878004D10DThe LU Recovery process is down
-21471679868004D10EThe remote session was lost
-21471679858004D10FThe resource is currently recovering
-21471679848004D110There was a mismatch in driving recovery
-21471679838004D111An error occurred with the XA resource
-21471641588004E002The root transaction wanted to commit
-21471641578004E003You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting
-21471641568004E004There is no MTS object context
-21471641558004E005The component is configured to use synchronization and this method call would cause a deadlock to occur
-21471641548004E006The component is configured to use synchronization and a thread has timed out waiting to enter the context
-21471641538004E007You made a method call on a COM+ component that has a transaction that has already committed or aborted
-21471641488004E00CThe specified role was not configured for the application
-21471641458004E00FCOM+ was unable to talk to the Microsoft Distributed Transaction Coordinator
-21471641278004E021An unexpected error occurred during COM+ Activation
-21471641268004E022COM+ Activation failed. Check the event log for more information
-21471641258004E023COM+ Activation failed due to a catalog or configuration error
-21471641248004E024COM+ activation failed because the activation could not be completed in the specified amount of time
-21471641238004E025COM+ Activation failed because an initialization function failed. Check the event log for more information
-21471641228004E026The requested operation requires that JIT be in the current context and it is not
-21471641218004E027The requested operation requires that the current context have a Transaction
-21471641208004E028The components threading model has changed after install into a COM+ Application. Please re-install component
-21471641198004E029IIS intrinsics not available. Start your work with IIS
-21471641188004E02AAn attempt to write a cookie failed
-21471641178004E02BAn attempt to use a database generated a database specific error
-21471641168004E02CThe COM+ component you created must use object pooling to work
-21471641158004E02DThe COM+ component you created must use object construction to work correctly
-21471641148004E02EThe COM+ component requires synchronization
-21471641138004E02FThe TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the "root" component for the transaction. The creation failed
-21471641128004E030The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope
-21471641118004E031The component made a call to EnterTransactionScope
-214702489680070000The operation completed successfully
-214702489580070001Incorrect function
-214702489480070002The system cannot find the file specified
-214702489380070003The system cannot find the path specified
-214702489280070004The system cannot open the file
-214702489180070005Access is denied
-214702489080070006The handle is invalid
-214702488980070007The storage control blocks were destroyed
-214702488880070008Not enough memory resources are available to process this command
-214702488780070009The storage control block address is invalid
-21470248868007000AThe environment is incorrect
-21470248858007000BAn attempt was made to load a program with an incorrect format
-21470248848007000CThe access code is invalid
-21470248838007000DThe data is invalid
-21470248828007000ENot enough memory resources are available to complete this operation
-21470248818007000FThe system cannot find the drive specified
-214702488080070010The directory cannot be removed
-214702487980070011The system cannot move the file to a different disk drive
-214702487880070012There are no more files
-214702487780070013The media is write protected
-214702487680070014The system cannot find the device specified
-214702487580070015The device is not ready
-214702487480070016The device does not recognize the command
-214702487380070017Data error (cyclic redundancy check)
-214702487280070018The program issued a command but the command length is incorrect
-214702487180070019The drive cannot locate a specific area or track on the disk
-21470248708007001AThe specified disk or diskette cannot be accessed
-21470248698007001BThe drive cannot find the sector requested
-21470248688007001CThe printer is out of paper
-21470248678007001DThe system cannot write to the specified device
-21470248668007001EThe system cannot read from the specified device
-21470248658007001FA device attached to the system is not functioning
-214702486480070020The process cannot access the file because it is being used by another process
-214702486380070021The process cannot access the file because another process has locked a portion of the file
-214702486280070022The wrong diskette is in the drive.Insert %2 (Volume Serial Number: %3) into drive %1
-214702486080070024Too many files opened for sharing
-214702485880070026Reached the end of the file
-214702485780070027The disk is full
-214702484680070032The request is not supported
-214702484580070033Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path
-214702484480070034You were not connected because a duplicate name exists on the network. If joining a domain
-214702484380070035The network path was not found
-214702484280070036The network is busy
-214702484180070037The specified network resource or device is no longer available
-214702484080070038The network BIOS command limit has been reached
-214702483980070039A network adapter hardware error occurred
-21470248388007003AThe specified server cannot perform the requested operation
-21470248378007003BAn unexpected network error occurred
-21470248368007003CThe remote adapter is not compatible
-21470248358007003DThe printer queue is full
-21470248348007003ESpace to store the file waiting to be printed is not available on the server
-21470248338007003FYour file waiting to be printed was deleted
-214702483280070040The specified network name is no longer available
-214702483180070041Network access is denied
-214702483080070042The network resource type is not correct
-214702482980070043The network name cannot be found
-214702482880070044The name limit for the local computer network adapter card was exceeded
-214702482780070045The network BIOS session limit was exceeded
-214702482680070046The remote server has been paused or is in the process of being started
-214702482580070047No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept
-214702482480070048The specified printer or disk device has been paused
-214702481680070050The file exists
-214702481480070052The directory or file cannot be created
-214702481380070053Fail on INT 24
-214702481280070054Storage to process this request is not available
-214702481180070055The local device name is already in use
-214702481080070056The specified network password is not correct
-214702480980070057The parameter is incorrect
-214702480880070058A write fault occurred on the network
-214702480780070059The system cannot start another process at this time
-214702479680070064Cannot create another system semaphore
-214702479580070065The exclusive semaphore is owned by another process
-214702479480070066The semaphore is set and cannot be closed
-214702479380070067The semaphore cannot be set again
-214702479280070068Cannot request exclusive semaphores at interrupt time
-214702479180070069The previous ownership of this semaphore has ended
-21470247908007006AInsert the diskette for drive %1
-21470247898007006BThe program stopped because an alternate diskette was not inserted
-21470247888007006CThe disk is in use or locked by another process
-21470247878007006DThe pipe has been ended
-21470247868007006EThe system cannot open the device or file specified
-21470247858007006FThe file name is too long
-214702478480070070There is not enough space on the disk
-214702478380070071No more internal file identifiers available
-214702478280070072The target internal file identifier is incorrect
-214702477980070075The IOCTL call made by the application program is not correct
-214702477880070076The verify-on-write switch parameter value is not correct
-214702477780070077The system does not support the command requested
-214702477680070078This function is not supported on this system
-214702477580070079The semaphore timeout period has expired
-21470247748007007AThe data area passed to a system call is too small
-21470247738007007BThe filename
-21470247728007007CThe system call level is not correct
-21470247718007007DThe disk has no volume label
-21470247708007007EThe specified module could not be found
-21470247698007007FThe specified procedure could not be found
-214702476880070080There are no child processes to wait for
-214702476780070081The %1 application cannot be run in Win32 mode
-214702476680070082Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O
-214702476580070083An attempt was made to move the file pointer before the beginning of the file
-214702476480070084The file pointer cannot be set on the specified device or file
-214702476380070085A JOIN or SUBST command cannot be used for a drive that contains previously joined drives
-214702476280070086An attempt was made to use a JOIN or SUBST command on a drive that has already been joined
-214702476180070087An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted
-214702476080070088The system tried to delete the JOIN of a drive that is not joined
-214702475980070089The system tried to delete the substitution of a drive that is not substituted
-21470247588007008AThe system tried to join a drive to a directory on a joined drive
-21470247578007008BThe system tried to substitute a drive to a directory on a substituted drive
-21470247568007008CThe system tried to join a drive to a directory on a substituted drive
-21470247558007008DThe system tried to SUBST a drive to a directory on a joined drive
-21470247548007008EThe system cannot perform a JOIN or SUBST at this time
-21470247538007008FThe system cannot join or substitute a drive to or for a directory on the same drive
-214702475280070090The directory is not a subdirectory of the root directory
-214702475180070091The directory is not empty
-214702475080070092The path specified is being used in a substitute
-214702474980070093Not enough resources are available to process this command
-214702474880070094The path specified cannot be used at this time
-214702474780070095An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute
-214702474680070096System trace information was not specified in your CONFIG.SYS file
-214702474580070097The number of specified semaphore events for DosMuxSemWait is not correct
-214702474480070098DosMuxSemWait did not execute; too many semaphores are already set
-214702474380070099The DosMuxSemWait list is not correct
-21470247428007009AThe volume label you entered exceeds the label character limit of the target file system
-21470247418007009BCannot create another thread
-21470247408007009CThe recipient process has refused the signal
-21470247398007009DThe segment is already discarded and cannot be locked
-21470247388007009EThe segment is already unlocked
-21470247378007009FThe address for the thread ID is not correct
-2147024736800700A0One or more arguments are not correct
-2147024735800700A1The specified path is invalid
-2147024734800700A2A signal is already pending
-2147024732800700A4No more threads can be created in the system
-2147024729800700A7Unable to lock a region of a file
-2147024726800700AAThe requested resource is in use
-2147024725800700ABDevice's command support detection is in progress
-2147024723800700ADA lock request was not outstanding for the supplied cancel region
-2147024722800700AEThe file system does not support atomic changes to the lock type
-2147024716800700B4The system detected a segment number that was not correct
-2147024714800700B6The operating system cannot run %1
-2147024713800700B7Cannot create a file when that file already exists
-2147024710800700BAThe flag passed is not correct
-2147024709800700BBThe specified system semaphore name was not found
-2147024708800700BCThe operating system cannot run %1
-2147024707800700BDThe operating system cannot run %1
-2147024706800700BEThe operating system cannot run %1
-2147024705800700BFCannot run %1 in Win32 mode
-2147024704800700C0The operating system cannot run %1
-2147024703800700C1%1 is not a valid Win32 application
-2147024702800700C2The operating system cannot run %1
-2147024701800700C3The operating system cannot run %1
-2147024700800700C4The operating system cannot run this application program
-2147024699800700C5The operating system is not presently configured to run this application
-2147024698800700C6The operating system cannot run %1
-2147024697800700C7The operating system cannot run this application program
-2147024696800700C8The code segment cannot be greater than or equal to 64K
-2147024695800700C9The operating system cannot run %1
-2147024694800700CAThe operating system cannot run %1
-2147024693800700CBThe system could not find the environment option that was entered
-2147024691800700CDNo process in the command subtree has a signal handler
-2147024690800700CEThe filename or extension is too long
-2147024689800700CFThe ring 2 stack is in use
-2147024688800700D0The global filename characters
-2147024687800700D1The signal being posted is not correct
-2147024686800700D2The signal handler cannot be set
-2147024684800700D4The segment is locked and cannot be reallocated
-2147024682800700D6Too many dynamic-link modules are attached to this program or dynamic-link module
-2147024681800700D7Cannot nest calls to LoadModule
-2147024680800700D8This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher
-2147024679800700D9The image file %1 is signed
-2147024678800700DAThe image file %1 is strong signed
-2147024676800700DCThis file is checked out or locked for editing by another user
-2147024675800700DDThe file must be checked out before saving changes
-2147024674800700DEThe file type being saved or retrieved has been blocked
-2147024673800700DFThe file size exceeds the limit allowed and cannot be saved
-2147024672800700E0Access Denied. Before opening files in this location
-2147024671800700E1Operation did not complete successfully because the file contains a virus or potentially unwanted software
-2147024670800700E2This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software
-2147024667800700E5The pipe is local
-2147024666800700E6The pipe state is invalid
-2147024665800700E7All pipe instances are busy
-2147024664800700E8The pipe is being closed
-2147024663800700E9No process is on the other end of the pipe
-2147024662800700EAMore data is available
-2147024661800700EBThe action requested resulted in no work being done. Error-style clean-up has been performed
-2147024656800700F0The session was canceled
-2147024642800700FEThe specified extended attribute name was invalid
-2147024641800700FFThe extended attributes are inconsistent
-214702463880070102The wait operation timed out
-214702463780070103No more data is available
-21470246308007010AThe copy functions cannot be used
-21470246298007010BThe directory name is invalid
-214702462180070113The extended attributes did not fit in the buffer
-214702462080070114The extended attribute file on the mounted file system is corrupt
-214702461980070115The extended attribute table file is full
-214702461880070116The specified extended attribute handle is invalid
-21470246148007011AThe mounted file system does not support extended attributes
-214702460880070120Attempt to release mutex not owned by caller
-21470245988007012AToo many posts were made to a semaphore
-21470245978007012BOnly part of a ReadProcessMemory or WriteProcessMemory request was completed
-21470245968007012CThe oplock request is denied
-21470245958007012DAn invalid oplock acknowledgment was received by the system
-21470245948007012EThe volume is too fragmented to complete this operation
-21470245938007012FThe file cannot be opened because it is in the process of being deleted
-214702459280070130Short name settings may not be changed on this volume due to the global registry setting
-214702459180070131Short names are not enabled on this volume
-214702459080070132The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume
-214702458980070133A requested file lock operation cannot be processed due to an invalid byte range
-214702458880070134The subsystem needed to support the image type is not present
-214702458780070135The specified file already has a notification GUID associated with it
-214702458680070136An invalid exception handler routine has been detected
-214702458580070137Duplicate privileges were specified for the token
-214702458480070138No ranges for the specified operation were able to be processed
-214702458380070139Operation is not allowed on a file system internal file
-21470245828007013AThe physical resources of this disk have been exhausted
-21470245818007013BThe token representing the data is invalid
-21470245808007013CThe device does not support the command feature
-21470245798007013DThe system cannot find message text for message number 0x%1 in the message file for %2
-21470245788007013EThe scope specified was not found
-21470245778007013FThe Central Access Policy specified is not defined on the target machine
-214702457680070140The Central Access Policy obtained from Active Directory is invalid
-214702457580070141The device is unreachable
-214702457480070142The target device has insufficient resources to complete the operation
-214702457380070143A data integrity checksum error occurred. Data in the file stream is corrupt
-214702457280070144An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation
-214702457080070146Device does not support file-level TRIM
-214702456980070147The command specified a data offset that does not align to the device's granularity/alignment
-214702456880070148The command specified an invalid field in its parameter list
-214702456780070149An operation is currently in progress with the device
-21470245668007014AAn attempt was made to send down the command via an invalid path to the target device
-21470245658007014BThe command specified a number of descriptors that exceeded the maximum supported by the device
-21470245648007014CScrub is disabled on the specified file
-21470245638007014DThe storage device does not provide redundancy
-21470245628007014EAn operation is not supported on a resident file
-21470245618007014FAn operation is not supported on a compressed file
-214702456080070150An operation is not supported on a directory
-214702455980070151The specified copy of the requested data could not be read
-214702455880070152The specified data could not be written to any of the copies
-214702455780070153One 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
-214702455680070154The supplied kernel information version is invalid
-214702455580070155The supplied PEP information version is invalid
-214702455480070156This object is not externally backed by any provider
-214702455380070157The external backing provider is not recognized
-214702455280070158Compressing this object would not save space
-214702455180070159The request failed due to a storage topology ID mismatch
-21470245508007015AThe operation was blocked by parental controls
-21470245498007015BA file system block being referenced has already reached the maximum reference count and can't be referenced any further
-21470245488007015CThe requested operation failed because the file stream is marked to disallow writes
-21470245478007015DThe requested operation failed with an architecture-specific failure code
-21470245468007015ENo action was taken as a system reboot is required
-21470245458007015FThe shutdown operation failed
-214702454480070160The restart operation failed
-214702454380070161The maximum number of sessions has been reached
-214702454280070162Windows Information Protection policy does not allow access to this network resource
-214702454180070163The device hint name buffer is too small to receive the remaining name
-214702454080070164The requested operation was blocked by Windows Information Protection policy. For more information
-214702453980070165The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please
-214702453880070166The cloud sync root metadata is corrupted
-214702453780070167The device is in maintenance mode
-214702453680070168This operation is not supported on a DAX volume
-214702453580070169The volume has active DAX mappings
-21470245348007016AThe cloud file provider is not running
-21470245338007016BThe cloud file metadata is corrupt and unreadable
-21470245328007016CThe cloud file metadata is too large
-21470245318007016DThe cloud file property is too large
-21470245308007016EThe cloud file property is possibly corrupt. The on-disk checksum does not match the computed checksum
-21470245298007016FThe process creation has been blocked
-214702452880070170The storage device has lost data or persistence
-214702452780070171The provider that supports file system virtualization is temporarily unavailable
-214702452680070172The metadata for file system virtualization is corrupt and unreadable
-214702452580070173The provider that supports file system virtualization is too busy to complete this operation
-214702452480070174The provider that supports file system virtualization is unknown
-214702452380070175GDI handles were potentially leaked by the application
-214702452280070176The maximum number of cloud file properties has been reached
-214702452180070177The version of the cloud file property store is not supported
-214702452080070178The file is not a cloud file
-214702451980070179The file is not in sync with the cloud
-21470245188007017AThe cloud sync root is already connected with another cloud sync provider
-21470245178007017BThe operation is not supported by the cloud sync provider
-21470245168007017CThe cloud operation is invalid
-21470245158007017DThe cloud operation is not supported on a read-only volume
-21470245148007017EThe operation is reserved for a connected cloud sync provider
-21470245138007017FThe cloud sync provider failed to validate the downloaded data
-214702451280070180You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol
-214702451180070181The virtualization operation is not allowed on the file in its current state
-214702451080070182The cloud sync provider failed user authentication
-214702450980070183The cloud sync provider failed to perform the operation due to low system resources
-214702450880070184The cloud sync provider failed to perform the operation due to network being unavailable
-214702450780070185The cloud operation was unsuccessful
-214702450680070186The operation is only supported on files under a cloud sync root
-214702450580070187The operation cannot be performed on cloud files in use
-214702450480070188The operation cannot be performed on pinned cloud files
-214702450380070189The cloud operation was aborted
-21470245028007018AThe cloud file's property store is corrupt
-21470245018007018BAccess to the cloud file is denied
-21470245008007018CThe cloud operation cannot be performed on a file with incompatible hardlinks
-21470244998007018DThe operation failed due to a conflicting cloud file property lock
-21470244988007018EThe cloud operation was canceled by user
-21470244978007018FAn externally encrypted syskey has been configured
-214702449680070190The thread is already in background processing mode
-214702449580070191The thread is not in background processing mode
-214702449480070192The process is already in background processing mode
-214702449380070193The process is not in background processing mode
-214702449280070194The cloud file provider exited unexpectedly
-214702449180070195The file is not a cloud sync root
-214702449080070196The read or write operation to an encrypted file could not be completed because the file can only be accessed when the device is unlocked
-214702448980070197The volume is not cluster aligned on the disk
-214702448880070198No physically aligned free space was found on the volume
-214702448780070199The APPX file can not be accessed because it is not encrypted as expected
-21470244868007019AA read or write of raw encrypted data cannot be performed because the file is not encrypted
-21470244858007019BAn invalid file offset in the encrypted data info block was passed for read or write operation of file's raw encrypted data
-21470244848007019CAn invalid offset and length combination in the encrypted data info block was passed for read or write operation of file's raw encrypted data
-21470244838007019DAn invalid parameter in the encrypted data info block was passed for read or write operation of file's raw encrypted data
-21470244828007019EThe Windows Subsystem for Linux has not been enabled
-21470244818007019FThe specified data could not be read from any of the copies
-2147024480800701A0The specified storage reserve ID is invalid
-2147024479800701A1The specified storage reserve does not exist
-2147024478800701A2The specified storage reserve already exists
-2147024477800701A3The specified storage reserve is not empty
-2147024476800701A4This operation requires a DAX volume
-2147024475800701A5This stream is not DAX mappable
-2147024474800701A6Operation cannot be performed on a time critical thread
-2147024473800701A7User data protection is not supported for the current or provided user
-2147024472800701A8This directory contains entries whose names differ only in case
-2147024471800701A9The file cannot be safely opened because it is not supported by this version of Windows
-2147024470800701AAThe cloud operation was not completed before the time-out period expired
-2147024469800701ABA task queue is required for this operation but none is available
-2147024468800701ACFailed loading a valid version of srcsrv.dll
-2147024467800701ADThis operation is not supported with BTT enabled
-2147024466800701AEThis operation cannot be performed because encryption is currently disabled
-2147024465800701AFThis encryption operation cannot be performed on filesystem metadata
-2147024464800701B0Encryption cannot be cleared on this file/directory because it still has an encrypted attribute
-2147024463800701B1A device which does not exist was specified
-2147024462800701B2Dehydration of the cloud file is disallowed by the cloud sync provider
-2147024461800701B3A file snapshot operation was attempted when one is already in progress
-2147024460800701B4A snapshot of the file cannot be taken because a user-mapped section is present
-2147024459800701B5The file snapshot operation was terminated because one of the files was modified in a way incompatible with a snapshot operation. Please try again
-2147024458800701B6An I/O request could not be coordinated with a file snapshot operation
-2147024457800701B7An unexpected error occurred while processing a file snapshot operation
-2147024456800701B8A file snapshot operation received an invalid parameter
-2147024455800701B9The operation could not be completed due to one or more unsatisfied dependencies
-2147024454800701BAThe file cannot be opened because the path has a case-sensitive directory
-2147024453800701BBThe filesystem couldn't handle one of the CacheManager's callback error codes
-2147024452800701BCWSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel
-2147024451800701BDThis action is blocked
-2147024450800701BEThis action is blocked. Please refer to the data loss prevention notification for further information
-2147024447800701C1This action is blocked. Please refer to the data loss prevention notification for further information
-2147024446800701C2Neither developer unlocked mode nor side loading mode is enabled on the device
-2147024445800701C3Can not change application type during upgrade or re-provision
-2147024444800701C4The application has not been provisioned
-2147024443800701C5The requested capability can not be authorized for this application
-2147024442800701C6There is no capability authorization policy on the device
-2147024441800701C7The capability authorization database has been corrupted
-2147024440800701C8The custom capability's SCCD has an invalid catalog
-2147024439800701C9None of the authorized entity elements in the SCCD matched the app being installed; either the PFNs don't match
-2147024438800701CAThe custom capability's SCCD failed to parse
-2147024437800701CBThe custom capability's SCCD requires developer mode
-2147024436800701CCThere not all declared custom capabilities are found in the SCCD
-2147024426800701D6The CimFS image is corrupt
-2147024416800701E0The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request
-2147024415800701E1The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation
-2147024414800701E2The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation
-2147024413800701E3The request failed due to a fatal device hardware error
-2147024409800701E7Attempt to access invalid address
-2147024408800701E8The volume contains paging
-2147024396800701F4User profile cannot be loaded
-2147024386800701FEThe file system encountered a metadata file with inconsistent data
-214702436280070216Arithmetic result exceeded 32 bits
-214702436180070217There is a process on other end of the pipe
-214702436080070218Waiting for a process to open the other end of the pipe
-214702435980070219Application verifier has found an error in the current process
-21470243588007021AAn error occurred in the ABIOS subsystem
-21470243578007021BA warning occurred in the WX86 subsystem
-21470243568007021CAn error occurred in the WX86 subsystem
-21470243558007021DAn 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
-21470243548007021EUnwind exception code
-21470243538007021FAn invalid or unaligned stack was encountered during an unwind operation
-214702435280070220An invalid unwind target was encountered during an unwind operation
-214702435180070221Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
-214702435080070222Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port
-214702434980070223An attempt was made to lower a quota limit below the current usage
-214702434880070224An attempt was made to attach to a device that was already attached to another device
-214702434780070225An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references
-214702434680070226Profiling not started
-214702434580070227Profiling not stopped
-214702434480070228The passed ACL did not contain the minimum required information
-214702434380070229The number of active profiling objects is at the maximum and no more may be started
-21470243428007022AUsed to indicate that an operation cannot continue without blocking for I/O
-21470243418007022BIndicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process
-21470243408007022CIf an MM error is returned which is not defined in the standard FsRtl filter
-21470243398007022DIf an MM error is returned which is not defined in the standard FsRtl filter
-21470243388007022EIf an MM error is returned which is not defined in the standard FsRtl filter
-21470243378007022FA malformed function table was encountered during an unwind operation
-214702433680070230Indicates 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
-214702433580070231Indicates that an attempt was made to grow an LDT by setting its size
-214702433380070233Indicates that the starting value for the LDT information was not an integral multiple of the selector size
-214702433280070234Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors
-214702433180070235Indicates a process has too many threads to perform the requested action. For example
-214702433080070236An attempt was made to operate on a thread within a specific process
-214702432980070237Page file quota was exceeded
-214702432880070238The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role
-214702432780070239The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required
-21470243268007023AThe NtCreateFile API failed. This error should never be returned to an application
-21470243258007023B{Privilege Failed}The I/O permissions for the process could not be changed
-21470243248007023C{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C
-21470243238007023D{Missing System File}The required system file %hs is bad or missing
-21470243228007023E{Application Error}The exception %s (0x
-21470243218007023F{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application
-214702432080070240{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld
-214702431980070241Windows 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
-214702431880070242{No Paging File Specified}No paging file was specified in the system configuration
-214702431780070243{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present
-214702431680070244An event pair synchronization operation was performed using the thread specific client/server event pair object
-214702431580070245A Windows Server has an incorrect configuration
-214702431480070246An 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
-214702431380070247The Unicode character is not defined in the Unicode character set installed on the system
-214702431280070248The paging file cannot be created on a floppy diskette
-214702431180070249The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected
-21470243108007024AThis operation is only allowed for the Primary Domain Controller of the domain
-21470243098007024BAn attempt was made to acquire a mutant such that its maximum count would have been exceeded
-21470243088007024CA volume has been accessed for which a file system driver is required that has not yet been loaded
-21470243078007024D{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt
-21470243068007024E{Unexpected Failure in DebugActiveProcess}An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process
-21470243058007024F{Fatal System Error}The %hs system process terminated unexpectedly with a status of 0x
-214702430480070250{Data Not Accepted}The TDI client could not handle the data received during an indication
-214702430380070251NTVDM encountered a hard error
-214702430280070252{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time
-214702430180070253{Reply Message Mismatch}An attempt was made to reply to an LPC message
-214702430080070254{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
-214702429980070255The 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
-214702429880070256The stream is not a tiny stream
-214702429780070257The request must be handled by the stack overflow code
-214702429680070258Internal 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
-214702429580070259The 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
-21470242948007025AThe bucket array must be grown. Retry transaction after doing so
-21470242938007025BThe user/kernel marshalling buffer has overflowed
-21470242928007025CThe supplied variant structure contains invalid data
-21470242918007025DThe specified buffer contains ill-formed data
-21470242908007025E{Audit Failed}An attempt to generate a security audit failed
-21470242898007025FThe timer resolution was not previously set by the current process
-214702428880070260There is insufficient account information to log you on
-214702428780070261{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
-214702428680070262{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
-214702428580070263There is an IP address conflict with another system on the network
-214702428480070264There is an IP address conflict with another system on the network
-214702428380070265{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
-214702428280070266A callback return system service cannot be executed when no callback is active
-214702428180070267The password provided is too short to meet the policy of your user account.Please choose a longer password
-214702428080070268The 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
-214702427980070269You 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
-21470242788007026AThe specified compression format is unsupported
-21470242778007026BThe specified hardware profile configuration is invalid
-21470242768007026CThe specified Plug and Play registry device path is invalid
-21470242758007026DThe specified quota list is internally inconsistent with its descriptor
-21470242748007026E{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
-21470242738007026F{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
-214702427280070270{DLL Initialization Failed}The application failed to initialize because the window station is shutting down
-214702427180070271The validation process needs to continue on to the next step
-214702427080070272There are no more matches for the current index enumeration
-214702426980070273The range could not be added to the range list because of a conflict
-214702426880070274The server process is running under a SID different than that required by client
-214702426780070275A group marked use for deny only cannot be enabled
-214702426680070276{EXCEPTION}Multiple floating point faults
-214702426580070277{EXCEPTION}Multiple floating point traps
-214702426480070278The requested interface is not supported
-214702426380070279{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode
-21470242628007027AThe system file %1 has become corrupt and has been replaced
-21470242618007027B{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
-21470242608007027CA device was removed so enumeration must be restarted
-21470242598007027D{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
-21470242588007027EDevice will not start without a reboot
-21470242578007027FThere is not enough power to complete the requested operation
-214702425680070280ERROR_MULTIPLE_FAULT_VIOLATION
-214702425580070281The system is in the process of shutting down
-214702425480070282An attempt to remove a processes DebugPort was made
-214702425380070283This version of Windows is not compatible with the behavior version of directory forest
-214702425280070284The specified range could not be found in the range list
-214702425080070286The driver was not loaded because the system is booting into safe mode
-214702424980070287The driver was not loaded because it failed its initialization call
-214702424880070288The "%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
-214702424780070289The 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
-21470242468007028AThe device object parameter is either not a valid device object or is not attached to the volume specified by the file name
-21470242458007028BA Machine Check Error has occurred. Please check the system eventlog for additional information
-21470242448007028CThere was error [%2] processing the driver database
-21470242438007028DSystem hive size has exceeded its limit
-21470242428007028EThe driver could not be loaded because a previous version of the driver is still in memory
-21470242418007028F{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation
-214702424080070290The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted
-214702423980070291The password provided is too long to meet the policy of your user account.Please choose a shorter password
-214702423180070299The requested operation could not be completed due to a file system limitation
-21470242288007029CAn assertion failure has occurred
-21470242278007029DAn error occurred in the ACPI subsystem
-21470242268007029EWOW Assertion Error
-21470242258007029FA device is missing in the system BIOS MPS table. This device will not be used.Please contact your system vendor for system BIOS update
-2147024224800702A0A translator failed to translate resources
-2147024223800702A1A IRQ translator failed to translate resources
-2147024222800702A2Driver %2 returned invalid ID for a child device (%3)
-2147024221800702A3{Kernel Debugger Awakened}the system debugger was awakened by an interrupt
-2147024220800702A4{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation
-2147024219800702A5{Too Much Information}The specified access control list (ACL) contained more information than was expected
-2147024218800702A6This warning level status indicates that the transaction state already exists for the registry sub-tree
-2147024217800702A7{Media Changed}The media may have changed
-2147024216800702A8{GUID Substitution}During the translation of a global identifier (GUID) to a Windows security ID (SID)
-2147024215800702A9The create operation stopped after reaching a symbolic link
-2147024214800702AAA long jump has been executed
-2147024213800702ABThe Plug and Play query operation was not successful
-2147024212800702ACA frame consolidation has been executed
-2147024211800702AD{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost
-2147024210800702AEThe application is attempting to run executable code from the module %hs. This may be insecure. An alternative
-2147024209800702AFThe application is loading executable code from the module %hs. This is secure
-2147024208800702B0Debugger did not handle the exception
-2147024207800702B1Debugger will reply later
-2147024206800702B2Debugger cannot provide handle
-2147024205800702B3Debugger terminated thread
-2147024204800702B4Debugger terminated process
-2147024203800702B5Debugger got control C
-2147024202800702B6Debugger printed exception on control C
-2147024201800702B7Debugger received RIP exception
-2147024200800702B8Debugger received control break
-2147024199800702B9Debugger command communication exception
-2147024198800702BA{Object Exists}An attempt was made to create an object and the object name already existed
-2147024197800702BB{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed
-2147024196800702BC{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
-2147024195800702BDThis informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created
-2147024194800702BE{Segment Load}A virtual DOS machine (VDM) is loading
-2147024193800702BF{Invalid Current Directory}The process cannot switch to the startup current directory %hs.Select OK to set current directory to %hs
-2147024192800702C0{Redundant Read}To satisfy a read request
-2147024191800702C1{Redundant Write}To satisfy a write request
-2147024190800702C2{Machine Type Mismatch}The image file %hs is valid
-2147024189800702C3{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later
-2147024188800702C4{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system
-2147024187800702C5{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
-2147024186800702C6{TDI Event Done}The TDI indication has completed successfully
-2147024185800702C7{TDI Event Pending}The TDI indication has entered the pending state
-2147024184800702C8Checking file system on %wZ
-2147024183800702C9{Fatal Application Exit}%hs
-2147024182800702CAThe specified registry key is referenced by a predefined handle
-2147024181800702CB{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
-2147024180800702CC%hs
-2147024179800702CD{Page Locked}One of the pages to lock was already locked
-2147024178800702CEApplication popup: %1 : %2
-2147024177800702CFERROR_ALREADY_WIN32
-2147024176800702D0{Machine Type Mismatch}The image file %hs is valid
-2147024175800702D1A yield execution was performed and no thread was available to run
-2147024174800702D2The resumable flag to a timer API was ignored
-2147024173800702D3The arbiter has deferred arbitration of these resources to its parent
-2147024172800702D4The inserted CardBus device cannot be started because of a configuration error on "%hs"
-2147024171800702D5The 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
-2147024170800702D6The system was put into hibernation
-2147024169800702D7The system was resumed from hibernation
-2147024168800702D8Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2
-2147024167800702D9A 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
-2147024166800702DAThe system has awoken
-2147024165800702DBERROR_WAIT_1
-2147024164800702DCERROR_WAIT_2
-2147024163800702DDERROR_WAIT_3
-2147024162800702DEERROR_WAIT_63
-2147024161800702DFERROR_ABANDONED_WAIT_0
-2147024160800702E0ERROR_ABANDONED_WAIT_63
-2147024159800702E1ERROR_USER_APC
-2147024158800702E2ERROR_KERNEL_APC
-2147024157800702E3ERROR_ALERTED
-2147024156800702E4The requested operation requires elevation
-2147024155800702E5A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
-2147024154800702E6An open/create operation completed while an oplock break is underway
-2147024153800702E7A new volume has been mounted by a file system
-2147024152800702E8This success level status indicates that the transaction state already exists for the registry sub-tree
-2147024151800702E9This indicates that a notify change request has been completed due to closing the handle which made the notify change request
-2147024150800702EA{Connect Failure on Primary Transport}An attempt was made to connect to the remote server %hs on the primary transport
-2147024149800702EBPage fault was a transition fault
-2147024148800702ECPage fault was a demand zero fault
-2147024147800702EDPage fault was a demand zero fault
-2147024146800702EEPage fault was a demand zero fault
-2147024145800702EFPage fault was satisfied by reading from a secondary storage device
-2147024144800702F0Cached page was locked during operation
-2147024143800702F1Crash dump exists in paging file
-2147024142800702F2Specified buffer contains all zeros
-2147024141800702F3A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
-2147024140800702F4The device has succeeded a query-stop and its resource requirements have changed
-2147024139800702F5The translator has translated these resources into the global space and no further translations should be performed
-2147024138800702F6A process being terminated has no threads to terminate
-2147024137800702F7The specified process is not part of a job
-2147024136800702F8The specified process is part of a job
-2147024135800702F9{Volume Shadow Copy Service}The system is now ready for hibernation
-2147024134800702FAA file system or file system filter driver has successfully completed an FsFilter operation
-2147024133800702FBThe specified interrupt vector was already connected
-2147024132800702FCThe specified interrupt vector is still connected
-2147024131800702FDAn operation is blocked waiting for an oplock
-2147024130800702FEDebugger handled exception
-2147024129800702FFDebugger continued
-214702412880070300An exception occurred in a user mode callback and the kernel callback frame should be removed
-214702412780070301Compression is disabled for this volume
-214702412680070302The data provider cannot fetch backwards through a result set
-214702412580070303The data provider cannot scroll backwards through a result set
-214702412480070304The data provider requires that previously fetched data is released before asking for more data
-214702412380070305The data provider was not able to interpret the flags set for a column binding in an accessor
-214702412280070306One or more errors occurred while processing the request
-214702412180070307The implementation is not capable of performing the request
-214702412080070308The client of a component requested an operation which is not valid given the state of the component instance
-214702411980070309A version number could not be parsed
-21470241188007030AThe iterator's start position is invalid
-21470241178007030BThe hardware has reported an uncorrectable memory error
-21470241168007030CThe attempted operation required self healing to be enabled
-21470241158007030DThe Desktop heap encountered an error while allocating session memory. There is more information in the system event log
-21470241148007030EThe system power state is transitioning from %2 to %3
-21470241138007030FThe system power state is transitioning from %2 to %3 but could enter %4
-214702411280070310A thread is getting dispatched with MCA EXCEPTION because of MCA
-214702411180070311Access to %1 is monitored by policy rule %2
-214702411080070312Access to %1 has been restricted by your Administrator by policy rule %2
-214702410980070313A valid hibernation file has been invalidated and should be abandoned
-214702410880070314{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
-214702410780070315{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
-214702410680070316{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
-214702410580070317The resources required for this device conflict with the MCFG table
-214702410480070318The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired
-214702410380070319The volume repair was not successful
-21470241028007031AOne of the volume corruption logs is full. Further corruptions that may be detected won't be logged
-21470241018007031BOne of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned
-21470241008007031COne of the volume corruption logs is unavailable for being operated on
-21470240998007031DOne of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned
-21470240988007031EOne of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions
-21470240978007031FOrphaned 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
-214702409680070320The oplock that was associated with this handle is now associated with a different handle
-214702409580070321An oplock of the requested level cannot be granted. An oplock of a lower level may be available
-214702409480070322The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken
-214702409380070323The handle with which this oplock was associated has been closed. The oplock is now broken
-214702409280070324The specified access control entry (ACE) does not contain a condition
-214702409180070325The specified access control entry (ACE) contains an invalid condition
-214702409080070326Access to the specified file handle has been revoked
-214702408980070327{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
-214702408880070328The read or write operation to an encrypted file could not be completed because the file has not been opened for data access
-214702408780070329File metadata optimization is already in progress
-21470240868007032AThe requested operation failed due to quota operation is still in progress
-21470240858007032BAccess to the specified handle has been revoked
-21470240848007032CThe callback function must be invoked inline
-21470240838007032DThe specified CPU Set IDs are invalid
-21470240828007032EThe specified enclave has not yet been terminated
-21470240818007032FAn attempt was made to access protected memory in violation of its secure access policy
-2147023902800703E2Access to the extended attribute was denied
-2147023901800703E3The I/O operation has been aborted because of either a thread exit or an application request
-2147023900800703E4Overlapped I/O event is not in a signaled state
-2147023899800703E5Overlapped I/O operation is in progress
-2147023898800703E6Invalid access to memory location
-2147023897800703E7Error performing inpage operation
-2147023895800703E9Recursion too deep; the stack overflowed
-2147023894800703EAThe window cannot act on the sent message
-2147023893800703EBCannot complete this function
-2147023892800703ECInvalid flags
-2147023891800703EDThe volume does not contain a recognized file system.Please make sure that all required file system drivers are loaded and that the volume is not corrupted
-2147023890800703EEThe volume for a file has been externally altered so that the opened file is no longer valid
-2147023889800703EFThe requested operation cannot be performed in full-screen mode
-2147023888800703F0An attempt was made to reference a token that does not exist
-2147023887800703F1The configuration registry database is corrupt
-2147023886800703F2The configuration registry key is invalid
-2147023885800703F3The configuration registry key could not be opened
-2147023884800703F4The configuration registry key could not be read
-2147023883800703F5The configuration registry key could not be written
-2147023882800703F6One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful
-2147023881800703F7The registry is corrupted. The structure of one of the files containing registry data is corrupted
-2147023880800703F8An I/O operation initiated by the registry failed unrecoverably. The registry could not read in
-2147023879800703F9The system has attempted to load or restore a file into the registry
-2147023878800703FAIllegal operation attempted on a registry key that has been marked for deletion
-2147023877800703FBSystem could not allocate the required space in a registry log
-2147023876800703FCCannot create a symbolic link in a registry key that already has subkeys or values
-2147023875800703FDCannot create a stable subkey under a volatile parent key
-2147023874800703FEA notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes
-21470238458007041BA stop control has been sent to a service that other running services are dependent on
-21470238448007041CThe requested control is not valid for this service
-21470238438007041DThe service did not respond to the start or control request in a timely fashion
-21470238428007041EA thread could not be created for the service
-21470238418007041FThe service database is locked
-214702384080070420An instance of the service is already running
-214702383980070421The account name is invalid or does not exist
-214702383880070422The service cannot be started
-214702383780070423Circular service dependency was specified
-214702383680070424The specified service does not exist as an installed service
-214702383580070425The service cannot accept control messages at this time
-214702383480070426The service has not been started
-214702383380070427The service process could not connect to the service controller
-214702383280070428An exception occurred in the service when handling the control request
-214702383180070429The database specified does not exist
-21470238308007042AThe service has returned a service-specific error code
-21470238298007042BThe process terminated unexpectedly
-21470238288007042CThe dependency service or group failed to start
-21470238278007042DThe service did not start due to a logon failure
-21470238268007042EAfter starting
-21470238258007042FThe specified service database lock is invalid
-214702382480070430The specified service has been marked for deletion
-214702382380070431The specified service already exists
-214702382280070432The system is currently running with the last-known-good configuration
-214702382180070433The dependency service does not exist or has been marked for deletion
-214702382080070434The current boot has already been accepted for use as the last-known-good control set
-214702381980070435No attempts to start the service have been made since the last boot
-214702381880070436The name is already in use as either a service name or a service display name
-214702381780070437The account specified for this service is different from the account specified for other services running in the same process
-214702381680070438Failure actions can only be set for Win32 services
-214702381580070439This service runs in the same process as the service control manager.Therefore
-21470238148007043ANo recovery program has been configured for this service
-21470238138007043BThe executable program that this service is configured to run in does not implement the service
-21470238128007043CThis service cannot be started in Safe Mode
-21470237968007044CThe physical end of the tape has been reached
-21470237958007044DA tape access reached a filemark
-21470237948007044EThe beginning of the tape or a partition was encountered
-21470237938007044FA tape access reached the end of a set of files
-214702379280070450No more data is on the tape
-214702379180070451Tape could not be partitioned
-214702379080070452When accessing a new tape of a multivolume partition
-214702378980070453Tape partition information could not be found when loading a tape
-214702378880070454Unable to lock the media eject mechanism
-214702378780070455Unable to unload the media
-214702378680070456The media in the drive may have changed
-214702378580070457The I/O bus was reset
-214702378480070458No media in drive
-214702378380070459No mapping for the Unicode character exists in the target multi-byte code page
-21470237828007045AA dynamic link library (DLL) initialization routine failed
-21470237818007045BA system shutdown is in progress
-21470237808007045CUnable to abort the system shutdown because no shutdown was in progress
-21470237798007045DThe request could not be performed because of an I/O device error
-21470237788007045ENo serial device was successfully initialized. The serial driver will unload
-21470237778007045FUnable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened
-214702377680070460A serial I/O operation was completed by another write to the serial port.(The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
-214702377580070461A serial I/O operation completed because the timeout period expired.(The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
-214702377480070462No ID address mark was found on the floppy disk
-214702377380070463Mismatch between the floppy disk sector ID field and the floppy disk controller track address
-214702377280070464The floppy disk controller reported an error that is not recognized by the floppy disk driver
-214702377180070465The floppy disk controller returned inconsistent results in its registers
-214702377080070466While accessing the hard disk
-214702376980070467While accessing the hard disk
-214702376880070468While accessing the hard disk
-214702376780070469Physical end of tape encountered
-21470237668007046ANot enough server memory resources are available to process this command
-21470237658007046BA potential deadlock condition has been detected
-21470237648007046CThe base address or the file offset specified does not have the proper alignment
-214702375680070474An attempt to change the system power state was vetoed by another application or driver
-214702375580070475The system BIOS failed an attempt to change the system power state
-214702375480070476An attempt was made to create more links on a file than the file system supports
-21470237468007047EThe specified program requires a newer version of Windows
-21470237458007047FThe specified program is not a Windows or MS-DOS program
-214702374480070480Cannot start more than one instance of the specified program
-214702374380070481The specified program was written for an earlier version of Windows
-214702374280070482One of the library files needed to run this application is damaged
-214702374180070483No application is associated with the specified file for this operation
-214702374080070484An error occurred in sending the command to the application
-214702373980070485One of the library files needed to run this application cannot be found
-214702373880070486The current process has used all of its system allowance of handles for Window Manager objects
-214702373780070487The message can be used only with synchronous operations
-214702373680070488The indicated source element has no media
-214702373580070489The indicated destination element already contains media
-21470237348007048AThe indicated element does not exist
-21470237338007048BThe indicated element is part of a magazine that is not present
-21470237328007048CThe indicated device requires reinitialization due to hardware errors
-21470237318007048DThe device has indicated that cleaning is required before further operations are attempted
-21470237308007048EThe device has indicated that its door is open
-21470237298007048FThe device is not connected
-214702372880070490Element not found
-214702372780070491There was no match for the specified key in the index
-214702372680070492The property set specified does not exist on the object
-214702372580070493The point passed to GetMouseMovePoints is not in the buffer
-214702372480070494The tracking (workstation) service is not running
-214702372380070495The Volume ID could not be found
-214702372180070497Unable to remove the file to be replaced
-214702372080070498Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name
-214702371980070499Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name
-21470237188007049AThe volume change journal is being deleted
-21470237178007049BThe volume change journal is not active
-21470237168007049CA file was found
-21470237158007049DThe journal entry has been deleted from the journal
-21470237138007049FDriver Verifier Volatile settings cannot be set when CFG and IO are enabled
-2147023712800704A0An attempt was made to access a partition that has begun termination
-2147023706800704A6A system shutdown has already been scheduled
-2147023705800704A7The system shutdown cannot be initiated because there are other users logged on to the computer
-2147023696800704B0The specified device name is invalid
-2147023695800704B1The device is not currently connected but it is a remembered connection
-2147023694800704B2The local device name has a remembered connection to another network resource
-2147023693800704B3The network path was either typed incorrectly
-2147023692800704B4The specified network provider name is invalid
-2147023691800704B5Unable to open the network connection profile
-2147023690800704B6The network connection profile is corrupted
-2147023689800704B7Cannot enumerate a noncontainer
-2147023688800704B8An extended error has occurred
-2147023687800704B9The format of the specified group name is invalid
-2147023686800704BAThe format of the specified computer name is invalid
-2147023685800704BBThe format of the specified event name is invalid
-2147023684800704BCThe format of the specified domain name is invalid
-2147023683800704BDThe format of the specified service name is invalid
-2147023682800704BEThe format of the specified network name is invalid
-2147023681800704BFThe format of the specified share name is invalid
-2147023680800704C0The format of the specified password is invalid
-2147023679800704C1The format of the specified message name is invalid
-2147023678800704C2The format of the specified message destination is invalid
-2147023677800704C3Multiple connections to a server or shared resource by the same user
-2147023676800704C4An attempt was made to establish a session to a network server
-2147023675800704C5The workgroup or domain name is already in use by another computer on the network
-2147023674800704C6The network is not present or not started
-2147023673800704C7The operation was canceled by the user
-2147023672800704C8The requested operation cannot be performed on a file with a user-mapped section open
-2147023671800704C9The remote computer refused the network connection
-2147023670800704CAThe network connection was gracefully closed
-2147023669800704CBThe network transport endpoint already has an address associated with it
-2147023668800704CCAn address has not yet been associated with the network endpoint
-2147023667800704CDAn operation was attempted on a nonexistent network connection
-2147023666800704CEAn invalid operation was attempted on an active network connection
-2147023665800704CFThe network location cannot be reached. For information about network troubleshooting
-2147023664800704D0The network location cannot be reached. For information about network troubleshooting
-2147023663800704D1The network location cannot be reached. For information about network troubleshooting
-2147023662800704D2No service is operating at the destination network endpoint on the remote system
-2147023661800704D3The request was aborted
-2147023660800704D4The network connection was aborted by the local system
-2147023659800704D5The operation could not be completed. A retry should be performed
-2147023658800704D6A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached
-2147023657800704D7Attempting to log in during an unauthorized time of day for this account
-2147023656800704D8The account is not authorized to log in from this station
-2147023655800704D9The network address could not be used for the operation requested
-2147023654800704DAThe service is already registered
-2147023653800704DBThe specified service does not exist
-2147023652800704DCThe operation being requested was not performed because the user has not been authenticated
-2147023651800704DDThe operation being requested was not performed because the user has not logged on to the network. The specified service does not exist
-2147023650800704DEContinue with work in progress
-2147023649800704DFAn attempt was made to perform an initialization operation when initialization has already been completed
-2147023648800704E0No more local devices
-2147023647800704E1The specified site does not exist
-2147023646800704E2A domain controller with the specified name already exists
-2147023645800704E3This operation is supported only when you are connected to the server
-2147023644800704E4The group policy framework should call the extension even if there are no changes
-2147023643800704E5The specified user does not have a valid profile
-2147023642800704E6This operation is not supported on a computer running Windows Server 2003 for Small Business Server
-2147023641800704E7The server machine is shutting down
-2147023640800704E8The remote system is not available. For information about network troubleshooting
-2147023639800704E9The security identifier provided is not from an account domain
-2147023638800704EAThe security identifier provided does not have a domain component
-2147023637800704EBAppHelp dialog canceled thus preventing the application from starting
-2147023636800704ECThis program is blocked by group policy. For more information
-2147023635800704EDA program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific
-2147023634800704EEThe share is currently offline or does not exist
-2147023633800704EFThe Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log
-2147023632800704F0The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem
-2147023631800704F1The system cannot contact a domain controller to service the authentication request. Please try again later
-2147023625800704F7The machine is locked and cannot be shut down without the force option
-2147023624800704F8You 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
-2147023623800704F9An application-defined callback gave invalid data when called
-2147023622800704FAThe group policy framework should call the extension in the synchronous foreground policy refresh
-2147023621800704FBThis driver has been blocked from loading
-2147023620800704FCA dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image
-2147023619800704FDWindows cannot open this program since it has been disabled
-2147023618800704FEWindows cannot open this program because the license enforcement system has been tampered with or become corrupted
-2147023617800704FFA transaction recover failed
-214702361680070500The current thread has already been converted to a fiber
-214702361580070501The current thread has already been converted from a fiber
-214702361480070502The 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
-214702361380070503Data present in one of the parameters is more than the function can operate on
-214702361280070504An attempt to do an operation on a debug object failed because the object is in the process of being deleted
-214702361180070505An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed
-214702361080070506%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator
-214702360980070507Insufficient information exists to identify the cause of failure
-214702360880070508The parameter passed to a C runtime function is incorrect
-214702360780070509The operation occurred beyond the valid data length of the file
-21470236068007050AThe service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured
-21470236058007050BThe process hosting the driver for this device has been terminated
-21470236048007050CAn operation attempted to exceed an implementation-defined limit
-21470236038007050DEither the target process
-21470236028007050EThe service notification client is lagging too far behind the current state of services in the machine
-21470236018007050FThe requested file operation failed because the storage quota was exceeded.To free up disk space
-214702360080070510The requested file operation failed because the storage policy blocks that type of file. For more information
-214702359980070511A privilege that the service requires to function properly does not exist in the service account configuration.You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration
-214702359880070512A thread involved in this operation appears to be unresponsive
-214702359780070513Indicates a particular Security ID may not be assigned as the label of an object
-214702359680070514Not all privileges or groups referenced are assigned to the caller
-214702359580070515Some mapping between account names and security IDs was not done
-214702359480070516No system quota limits are specifically set for this account
-214702359380070517No encryption key is available. A well-known encryption key was returned
-214702359280070518The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string
-214702359180070519The revision level is unknown
-21470235908007051AIndicates two revision levels are incompatible
-21470235898007051BThis security ID may not be assigned as the owner of this object
-21470235888007051CThis security ID may not be assigned as the primary group of an object
-21470235878007051DAn attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client
-21470235868007051EThe group may not be disabled
-21470235858007051FWe 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
-214702358480070520A specified logon session does not exist. It may already have been terminated
-214702358380070521A specified privilege does not exist
-214702358280070522A required privilege is not held by the client
-214702358180070523The name provided is not a properly formed account name
-214702358080070524The specified account already exists
-214702357980070525The specified account does not exist
-214702357880070526The specified group already exists
-214702357780070527The specified group does not exist
-214702357680070528Either the specified user account is already a member of the specified group
-214702357580070529The specified user account is not a member of the specified group account
-21470235748007052AThis operation is disallowed as it could result in an administration account being disabled
-21470235738007052BUnable to update the password. The value provided as the current password is incorrect
-21470235728007052CUnable to update the password. The value provided for the new password contains values that are not allowed in passwords
-21470235718007052DUnable to update the password. The value provided for the new password does not meet the length
-21470235708007052EThe user name or password is incorrect
-21470235698007052FAccount restrictions are preventing this user from signing in. For example: blank passwords aren't allowed
-214702356880070530Your account has time restrictions that keep you from signing in right now
-214702356780070531This user isn't allowed to sign in to this computer
-214702356680070532The password for this account has expired
-214702356580070533This user can't sign in because this account is currently disabled
-214702356480070534No mapping between account names and security IDs was done
-214702356380070535Too many local user identifiers (LUIDs) were requested at one time
-214702356280070536No more local user identifiers (LUIDs) are available
-214702356180070537The subauthority part of a security ID is invalid for this particular use
-214702356080070538The access control list (ACL) structure is invalid
-214702355980070539The security ID structure is invalid
-21470235588007053AThe security descriptor structure is invalid
-21470235568007053CThe inherited access control list (ACL) or access control entry (ACE) could not be built
-21470235558007053DThe server is currently disabled
-21470235548007053EThe server is currently enabled
-21470235538007053FThe value provided was an invalid value for an identifier authority
-214702355280070540No more memory is available for security information updates
-214702355180070541The specified attributes are invalid
-214702355080070542Either a required impersonation level was not provided
-214702354980070543Cannot open an anonymous level security token
-214702354880070544The validation information class requested was invalid
-214702354780070545The type of the token is inappropriate for its attempted use
-214702354680070546Unable to perform a security operation on an object that has no associated security
-214702354580070547Configuration information could not be read from the domain controller
-214702354480070548The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation
-214702354380070549The domain was in the wrong state to perform the security operation
-21470235428007054AThis operation is only allowed for the Primary Domain Controller of the domain
-21470235418007054BThe specified domain either does not exist or could not be contacted
-21470235408007054CThe specified domain already exists
-21470235398007054DAn attempt was made to exceed the limit on the number of domains per server
-21470235388007054EUnable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk
-21470235378007054FAn internal error occurred
-214702353680070550Generic access types were contained in an access mask which should already be mapped to nongeneric types
-214702353580070551A security descriptor is not in the right format (absolute or self-relative)
-214702353480070552The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process
-214702353380070553Cannot start a new logon session with an ID that is already in use
-214702353280070554A specified authentication package is unknown
-214702353180070555The logon session is not in a state that is consistent with the requested operation
-214702353080070556The logon session ID is already in use
-214702352980070557A logon request contained an invalid logon type value
-214702352880070558Unable to impersonate using a named pipe until data has been read from that pipe
-214702352780070559The transaction state of a registry subtree is incompatible with the requested operation
-21470235268007055AAn internal security database corruption has been encountered
-21470235258007055BCannot perform this operation on built-in accounts
-21470235248007055CCannot perform this operation on this built-in special group
-21470235238007055DCannot perform this operation on this built-in special user
-21470235228007055EThe user cannot be removed from a group because the group is currently the user's primary group
-21470235218007055FThe token is already in use as a primary token
-214702352080070560The specified local group does not exist
-214702351980070561The specified account name is not a member of the group
-214702351880070562The specified account name is already a member of the group
-214702351780070563The specified local group already exists
-214702351680070564Logon failure: the user has not been granted the requested logon type at this computer
-214702351580070565The maximum number of secrets that may be stored in a single system has been exceeded
-214702351480070566The length of a secret exceeds the maximum length allowed
-214702351380070567The local security authority database contains an internal inconsistency
-214702351280070568During a logon attempt
-214702351180070569Logon failure: the user has not been granted the requested logon type at this computer
-21470235108007056AA cross-encrypted password is necessary to change a user password
-21470235098007056BA member could not be added to or removed from the local group because the member does not exist
-21470235088007056CA new member could not be added to a local group because the member has the wrong account type
-21470235078007056DToo many security IDs have been specified
-21470235068007056EA cross-encrypted password is necessary to change this user password
-21470235058007056FIndicates an ACL contains no inheritable components
-214702350480070570The file or directory is corrupted and unreadable
-214702350380070571The disk structure is corrupted and unreadable
-214702350280070572There is no user session key for the specified logon session
-214702350180070573The 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
-214702350080070574The target account name is incorrect
-214702349980070575Mutual Authentication failed. The server's password is out of date at the domain controller
-214702349880070576There is a time and/or date difference between the client and server
-214702349780070577This operation cannot be performed on the current domain
-214702349680070578Invalid window handle
-214702349580070579Invalid menu handle
-21470234948007057AInvalid cursor handle
-21470234938007057BInvalid accelerator table handle
-21470234928007057CInvalid hook handle
-21470234918007057DInvalid handle to a multiple-window position structure
-21470234908007057ECannot create a top-level child window
-21470234898007057FCannot find window class
-214702348880070580Invalid window; it belongs to other thread
-214702348780070581Hot key is already registered
-214702348680070582Class already exists
-214702348580070583Class does not exist
-214702348480070584Class still has open windows
-214702348380070585Invalid index
-214702348280070586Invalid icon handle
-214702348180070587Using private DIALOG window words
-214702348080070588The list box identifier was not found
-214702347980070589No wildcards were found
-21470234788007058AThread does not have a clipboard open
-21470234778007058BHot key is not registered
-21470234768007058CThe window is not a valid dialog window
-21470234758007058DControl ID not found
-21470234748007058EInvalid message for a combo box because it does not have an edit control
-21470234738007058FThe window is not a combo box
-214702347280070590Height must be less than 256
-214702347180070591Invalid device context (DC) handle
-214702347080070592Invalid hook procedure type
-214702346980070593Invalid hook procedure
-214702346880070594Cannot set nonlocal hook without a module handle
-214702346780070595This hook procedure can only be set globally
-214702346680070596The journal hook procedure is already installed
-214702346580070597The hook procedure is not installed
-214702346480070598Invalid message for single-selection list box
-214702346380070599LB_SETCOUNT sent to non-lazy list box
-21470234628007059AThis list box does not support tab stops
-21470234618007059BCannot destroy object created by another thread
-21470234608007059CChild windows cannot have menus
-21470234598007059DThe window does not have a system menu
-21470234588007059EInvalid message box style
-21470234578007059FInvalid system-wide (SPI_*) parameter
-2147023456800705A0Screen already locked
-2147023455800705A1All handles to windows in a multiple-window position structure must have the same parent
-2147023454800705A2The window is not a child window
-2147023453800705A3Invalid GW_* command
-2147023452800705A4Invalid thread identifier
-2147023451800705A5Cannot process a message from a window that is not a multiple document interface (MDI) window
-2147023450800705A6Popup menu already active
-2147023449800705A7The window does not have scroll bars
-2147023448800705A8Scroll bar range cannot be greater than MAXLONG
-2147023447800705A9Cannot show or remove the window in the way specified
-2147023446800705AAInsufficient system resources exist to complete the requested service
-2147023445800705ABInsufficient system resources exist to complete the requested service
-2147023444800705ACInsufficient system resources exist to complete the requested service
-2147023443800705ADInsufficient quota to complete the requested service
-2147023442800705AEInsufficient quota to complete the requested service
-2147023441800705AFThe paging file is too small for this operation to complete
-2147023440800705B0A menu item was not found
-2147023439800705B1Invalid keyboard layout handle
-2147023438800705B2Hook type not allowed
-2147023437800705B3This operation requires an interactive window station
-2147023436800705B4This operation returned because the timeout period expired
-2147023435800705B5Invalid monitor handle
-2147023434800705B6Incorrect size argument
-2147023433800705B7The symbolic link cannot be followed because its type is disabled
-2147023432800705B8This application does not support the current operation on symbolic links
-2147023431800705B9Windows was unable to parse the requested XML data
-2147023430800705BAAn error was encountered while processing an XML digital signature
-2147023429800705BBThis application must be restarted
-2147023428800705BCThe caller made the connection request in the wrong routing compartment
-2147023427800705BDThere was an AuthIP failure when attempting to connect to the remote host
-2147023426800705BEInsufficient NVRAM resources exist to complete the requested service. A reboot might be required
-2147023425800705BFUnable to finish the requested operation because the specified process is not a GUI process
-2147023396800705DCThe event log file is corrupted
-2147023395800705DDNo event log file could be opened
-2147023394800705DEThe event log file is full
-2147023393800705DFThe event log file has changed between read operations
-2147023392800705E0The specified Job already has a container assigned to it
-2147023391800705E1The specified Job does not have a container assigned to it
-21470233468007060EThe specified task name is invalid
-21470233458007060FThe specified task index is invalid
-214702334480070610The specified thread is already joining a task
-214702329580070641The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance
-214702329480070642User cancelled installation
-214702329380070643Fatal error during installation
-214702329280070644Installation suspended
-214702329180070645This action is only valid for products that are currently installed
-214702329080070646Feature ID not registered
-214702328980070647Component ID not registered
-214702328880070648Unknown property
-214702328780070649Handle is in an invalid state
-21470232868007064AThe configuration data for this product is corrupt. Contact your support personnel
-21470232858007064BComponent qualifier not present
-21470232848007064CThe installation source for this product is not available. Verify that the source exists and that you can access it
-21470232838007064DThis installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service
-21470232828007064EProduct is uninstalled
-21470232818007064FSQL query syntax invalid or unsupported
-214702328080070650Record field does not exist
-214702327980070651The device has been removed
-214702327880070652Another installation is already in progress. Complete that installation before proceeding with this install
-214702327780070653This installation package could not be opened. Verify that the package exists and that you can access it
-214702327680070654This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package
-214702327580070655There was an error starting the Windows Installer service user interface. Contact your support personnel
-214702327480070656Error opening installation log file. Verify that the specified log file location exists and that you can write to it
-214702327380070657The language of this installation package is not supported by your system
-214702327280070658Error applying transforms. Verify that the specified transform paths are valid
-214702327180070659This installation is forbidden by system policy. Contact your system administrator
-21470232708007065AFunction could not be executed
-21470232698007065BFunction failed during execution
-21470232688007065CInvalid or unknown table specified
-21470232678007065DData supplied is of wrong type
-21470232668007065EData of this type is not supported
-21470232658007065FThe Windows Installer service failed to start. Contact your support personnel
-214702326480070660The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder
-214702326380070661This installation package is not supported by this processor type. Contact your product vendor
-214702326280070662Component not used on this computer
-214702326180070663This update package could not be opened. Verify that the update package exists and that you can access it
-214702326080070664This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package
-214702325980070665This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service
-214702325880070666Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product
-214702325780070667Invalid command line argument. Consult the Windows Installer SDK for detailed command line help
-214702325680070668Only administrators have permission to add
-214702325580070669The requested operation completed successfully. The system will be restarted so the changes can take effect
-21470232548007066AThe upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing
-21470232538007066BThe update package is not permitted by software restriction policy
-21470232528007066COne or more customizations are not permitted by software restriction policy
-21470232518007066DThe Windows Installer does not permit installation from a Remote Desktop Connection
-21470232508007066EUninstallation of the update package is not supported
-21470232498007066FThe update is not applied to this product
-214702324880070670No valid sequence could be found for the set of updates
-214702324780070671Update removal was disallowed by policy
-214702324680070672The XML update data is invalid
-214702324580070673Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update
-214702324480070674The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state
-214702324380070675A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately
-214702324280070676The app that you are trying to run is not supported on this version of Windows
-214702324180070677The operation was blocked as the process prohibits dynamic code generation
-214702324080070678The objects are not identical
-214702323980070679The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard
-21470232368007067CThe thread context could not be updated because this has been restricted for the process
-21470232358007067DAn invalid cross-partition private file/section access was attempted
-21470232348007067EA return address hijack is being attempted. This is supported by the operating system when user-mode shadow stacks are enabled
-2147023196800706A4The string binding is invalid
-2147023195800706A5The binding handle is not the correct type
-2147023194800706A6The binding handle is invalid
-2147023193800706A7The RPC protocol sequence is not supported
-2147023192800706A8The RPC protocol sequence is invalid
-2147023191800706A9The string universal unique identifier (UUID) is invalid
-2147023190800706AAThe endpoint format is invalid
-2147023189800706ABThe network address is invalid
-2147023188800706ACNo endpoint was found
-2147023187800706ADThe timeout value is invalid
-2147023186800706AEThe object universal unique identifier (UUID) was not found
-2147023185800706AFThe object universal unique identifier (UUID) has already been registered
-2147023184800706B0The type universal unique identifier (UUID) has already been registered
-2147023183800706B1The RPC server is already listening
-2147023182800706B2No protocol sequences have been registered
-2147023181800706B3The RPC server is not listening
-2147023180800706B4The manager type is unknown
-2147023179800706B5The interface is unknown
-2147023178800706B6There are no bindings
-2147023177800706B7There are no protocol sequences
-2147023176800706B8The endpoint cannot be created
-2147023175800706B9Not enough resources are available to complete this operation
-2147023174800706BAThe RPC server is unavailable
-2147023173800706BBThe RPC server is too busy to complete this operation
-2147023172800706BCThe network options are invalid
-2147023171800706BDThere are no remote procedure calls active on this thread
-2147023170800706BEThe remote procedure call failed
-2147023169800706BFThe remote procedure call failed and did not execute
-2147023168800706C0A remote procedure call (RPC) protocol error occurred
-2147023167800706C1Access to the HTTP proxy is denied
-2147023166800706C2The transfer syntax is not supported by the RPC server
-2147023164800706C4The universal unique identifier (UUID) type is not supported
-2147023163800706C5The tag is invalid
-2147023162800706C6The array bounds are invalid
-2147023161800706C7The binding does not contain an entry name
-2147023160800706C8The name syntax is invalid
-2147023159800706C9The name syntax is not supported
-2147023157800706CBNo network address is available to use to construct a universal unique identifier (UUID)
-2147023156800706CCThe endpoint is a duplicate
-2147023155800706CDThe authentication type is unknown
-2147023154800706CEThe maximum number of calls is too small
-2147023153800706CFThe string is too long
-2147023152800706D0The RPC protocol sequence was not found
-2147023151800706D1The procedure number is out of range
-2147023150800706D2The binding does not contain any authentication information
-2147023149800706D3The authentication service is unknown
-2147023148800706D4The authentication level is unknown
-2147023147800706D5The security context is invalid
-2147023146800706D6The authorization service is unknown
-2147023145800706D7The entry is invalid
-2147023144800706D8The server endpoint cannot perform the operation
-2147023143800706D9There are no more endpoints available from the endpoint mapper
-2147023142800706DANo interfaces have been exported
-2147023141800706DBThe entry name is incomplete
-2147023140800706DCThe version option is invalid
-2147023139800706DDThere are no more members
-2147023138800706DEThere is nothing to unexport
-2147023137800706DFThe interface was not found
-2147023136800706E0The entry already exists
-2147023135800706E1The entry is not found
-2147023134800706E2The name service is unavailable
-2147023133800706E3The network address family is invalid
-2147023132800706E4The requested operation is not supported
-2147023131800706E5No security context is available to allow impersonation
-2147023130800706E6An internal error occurred in a remote procedure call (RPC)
-2147023129800706E7The RPC server attempted an integer division by zero
-2147023128800706E8An addressing error occurred in the RPC server
-2147023127800706E9A floating-point operation at the RPC server caused a division by zero
-2147023126800706EAA floating-point underflow occurred at the RPC server
-2147023125800706EBA floating-point overflow occurred at the RPC server
-2147023124800706ECThe list of RPC servers available for the binding of auto handles has been exhausted
-2147023123800706EDUnable to open the character translation table file
-2147023122800706EEThe file containing the character translation table has fewer than 512 bytes
-2147023121800706EFA null context handle was passed from the client to the host during a remote procedure call
-2147023119800706F1The context handle changed during a remote procedure call
-2147023118800706F2The binding handles passed to a remote procedure call do not match
-2147023117800706F3The stub is unable to get the remote procedure call handle
-2147023116800706F4A null reference pointer was passed to the stub
-2147023115800706F5The enumeration value is out of range
-2147023114800706F6The byte count is too small
-2147023113800706F7The stub received bad data
-2147023112800706F8The supplied user buffer is not valid for the requested operation
-2147023111800706F9The disk media is not recognized. It may not be formatted
-2147023110800706FAThe workstation does not have a trust secret
-2147023109800706FBThe security database on the server does not have a computer account for this workstation trust relationship
-2147023108800706FCThe trust relationship between the primary domain and the trusted domain failed
-2147023107800706FDThe trust relationship between this workstation and the primary domain failed
-2147023106800706FEThe network logon failed
-2147023105800706FFA remote procedure call is already in progress for this thread
-214702310480070700An attempt was made to logon
-214702310380070701The user's account has expired
-214702310280070702The redirector is in use and cannot be unloaded
-214702310180070703The specified printer driver is already installed
-214702310080070704The specified port is unknown
-214702309980070705The printer driver is unknown
-214702309880070706The print processor is unknown
-214702309780070707The specified separator file is invalid
-214702309680070708The specified priority is invalid
-214702309580070709The printer name is invalid
-21470230948007070AThe printer already exists
-21470230938007070BThe printer command is invalid
-21470230928007070CThe specified datatype is invalid
-21470230918007070DThe environment specified is invalid
-21470230908007070EThere are no more bindings
-21470230898007070FThe account used is an interdomain trust account. Use your global user account or local user account to access this server
-214702308880070710The account used is a computer account. Use your global user account or local user account to access this server
-214702308780070711The account used is a server trust account. Use your global user account or local user account to access this server
-214702308680070712The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain
-214702308580070713The server is in use and cannot be unloaded
-214702308480070714The specified image file did not contain a resource section
-214702308380070715The specified resource type cannot be found in the image file
-214702308280070716The specified resource name cannot be found in the image file
-214702308180070717The specified resource language ID cannot be found in the image file
-214702308080070718Not enough quota is available to process this command
-214702307980070719No interfaces have been registered
-21470230788007071AThe remote procedure call was cancelled
-21470230778007071BThe binding handle does not contain all required information
-21470230768007071CA communications failure occurred during a remote procedure call
-21470230758007071DThe requested authentication level is not supported
-21470230748007071ENo principal name registered
-21470230738007071FThe error specified is not a valid Windows RPC error code
-214702307280070720A UUID that is valid only on this computer has been allocated
-214702307180070721A security package specific error occurred
-214702307080070722Thread is not canceled
-214702306980070723Invalid operation on the encoding/decoding handle
-214702306880070724Incompatible version of the serializing package
-214702306780070725Incompatible version of the RPC stub
-214702306680070726The RPC pipe object is invalid or corrupted
-214702306580070727An invalid operation was attempted on an RPC pipe object
-214702306480070728Unsupported RPC pipe version
-214702306380070729HTTP proxy server rejected the connection because the cookie authentication failed
-21470230628007072AThe RPC server is suspended
-21470230618007072BThe RPC call contains too many handles to be transmitted in a single request
-21470230608007072CThe RPC call contains a handle that differs from the declared handle type
-21470229988007076AThe group member was not found
-21470229978007076BThe endpoint mapper database entry could not be created
-21470229968007076CThe object universal unique identifier (UUID) is the nil UUID
-21470229958007076DThe specified time is invalid
-21470229948007076EThe specified form name is invalid
-21470229938007076FThe specified form size is invalid
-214702299280070770The specified printer handle is already being waited on
-214702299180070771The specified printer has been deleted
-214702299080070772The state of the printer is invalid
-214702298980070773The user's password must be changed before signing in
-214702298880070774Could not find the domain controller for this domain
-214702298780070775The referenced account is currently locked out and may not be logged on to
-214702298680070776The object exporter specified was not found
-214702298580070777The object specified was not found
-214702298480070778The object resolver set specified was not found
-214702298380070779Some data remains to be sent in the request buffer
-21470229828007077AInvalid asynchronous remote procedure call handle
-21470229818007077BInvalid asynchronous RPC call handle for this operation
-21470229808007077CThe RPC pipe object has already been closed
-21470229798007077DThe RPC call completed before all pipes were processed
-21470229788007077ENo more data is available from the RPC pipe
-21470229778007077FNo site name is available for this machine
-214702297680070780The file cannot be accessed by the system
-214702297580070781The name of the file cannot be resolved by the system
-214702297480070782The entry is not of the expected type
-214702297380070783Not all object UUIDs could be exported to the specified entry
-214702297280070784Interface could not be exported to the specified entry
-214702297180070785The specified profile entry could not be added
-214702297080070786The specified profile element could not be added
-214702296980070787The specified profile element could not be removed
-214702296880070788The group element could not be added
-214702296780070789The group element could not be removed
-21470229668007078AThe printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers
-21470229658007078BThe context has expired and can no longer be used
-21470229648007078CThe current user's delegated trust creation quota has been exceeded
-21470229638007078DThe total delegated trust creation quota has been exceeded
-21470229628007078EThe current user's delegated trust deletion quota has been exceeded
-21470229618007078FThe computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer
-214702296080070790Remote connections to the Print Spooler are blocked by a policy set on your machine
-214702295980070791Authentication failed because NTLM authentication has been disabled
-214702295880070792Logon Failure: EAS policy requires that the user change their password before this operation can be performed
-214702295780070793An administrator has restricted sign in. To sign in
-2147022896800707D0The pixel format is invalid
-2147022895800707D1The specified driver is invalid
-2147022894800707D2The window style or class attribute is invalid for this operation
-2147022893800707D3The requested metafile operation is not supported
-2147022892800707D4The requested transformation operation is not supported
-2147022891800707D5The requested clipping operation is not supported
-2147022886800707DAThe specified color management module is invalid
-2147022885800707DBThe specified color profile is invalid
-2147022884800707DCThe specified tag was not found
-2147022883800707DDA required tag is not present
-2147022882800707DEThe specified tag is already present
-2147022881800707DFThe specified color profile is not associated with the specified device
-2147022880800707E0The specified color profile was not found
-2147022879800707E1The specified color space is invalid
-2147022878800707E2Image Color Management is not enabled
-2147022877800707E3There was an error while deleting the color transform
-2147022876800707E4The specified color transform is invalid
-2147022875800707E5The specified transform does not match the bitmap's color space
-2147022874800707E6The specified named color index is not present in the profile
-2147022873800707E7The specified profile is intended for a device of a different type than the specified device
-214702279480070836The workstation driver is not installed
-214702279380070837The server could not be located
-214702279280070838An internal error occurred. The network cannot access a shared memory segment
-214702279180070839A network resource shortage occurred
-21470227908007083AThis operation is not supported on workstations
-21470227898007083BThe device is not connected
-21470227888007083CThe network connection was made successfully
-21470227878007083DThe network connection was made successfully using default credentials
-214702278280070842The Server service is not started
-214702278180070843The queue is empty
-214702278080070844The device or directory does not exist
-214702277980070845The operation is invalid on a redirected resource
-214702277880070846The name has already been shared
-214702277780070847The server is currently out of the requested resource
-214702277580070849Requested addition of items exceeds the maximum allowed
-21470227748007084AThe Peer service supports only two simultaneous users
-21470227738007084BThe API return buffer is too small
-21470227698007084FA remote API error occurred
-214702276580070853An error occurred when opening or reading the configuration file
-214702276080070858A general network error occurred
-214702275980070859The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service
-21470227588007085AThe Workstation service has not been started
-21470227578007085BThe requested information is not available
-21470227568007085CAn internal Windows error occurred
-21470227558007085DThe server is not configured for transactions
-21470227548007085EThe requested API is not supported on the remote server
-21470227538007085FThe event name is invalid
-214702275280070860The computer name already exists on the network. Change it and restart the computer
-214702275080070862The specified component could not be found in the configuration information
-214702274980070863The specified parameter could not be found in the configuration information
-214702274780070865A line in the configuration file is too long
-214702274680070866The printer does not exist
-214702274580070867The print job does not exist
-214702274480070868The printer destination cannot be found
-214702274380070869The printer destination already exists
-21470227428007086AThe printer queue already exists
-21470227418007086BNo more printers can be added
-21470227408007086CNo more print jobs can be added
-21470227398007086DNo more printer destinations can be added
-21470227388007086EThis printer destination is idle and cannot accept control operations
-21470227378007086FThis printer destination request contains an invalid control function
-214702273680070870The print processor is not responding
-214702273580070871The spooler is not running
-214702273480070872This operation cannot be performed on the print destination in its current state
-214702273380070873This operation cannot be performed on the printer queue in its current state
-214702273280070874This operation cannot be performed on the print job in its current state
-214702273180070875A spooler memory allocation failure occurred
-214702273080070876The device driver does not exist
-214702272980070877The data type is not supported by the print processor
-214702272880070878The print processor is not installed
-214702271680070884The service database is locked
-214702271580070885The service table is full
-214702271480070886The requested service has already been started
-214702271380070887The service does not respond to control actions
-214702271280070888The service has not been started
-214702271180070889The service name is invalid
-21470227108007088AThe service is not responding to the control function
-21470227098007088BThe service control is busy
-21470227088007088CThe configuration file contains an invalid service program name
-21470227078007088DThe service could not be controlled in its present state
-21470227068007088EThe service ended abnormally
-21470227058007088FThe requested pause
-214702270480070890The service control dispatcher could not find the service name in the dispatch table
-214702270380070891The service control dispatcher pipe read failed
-214702270280070892A thread for the new service could not be created
-214702269680070898This workstation is already logged on to the local-area network
-214702269580070899The workstation is not logged on to the local-area network
-21470226948007089AThe specified username is invalid
-21470226938007089BThe password parameter is invalid
-21470226928007089CThe logon processor did not add the message alias
-21470226918007089DThe logon processor did not add the message alias
-21470226908007089EThe logoff processor did not delete the message alias
-21470226898007089FThe logoff processor did not delete the message alias
-2147022687800708A1Network logons are paused
-2147022686800708A2A centralized logon-server conflict occurred
-2147022685800708A3The server is configured without a valid user path
-2147022684800708A4An error occurred while loading or running the logon script
-2147022682800708A6The logon server was not specified. Your computer will be logged on as STANDALONE
-2147022681800708A7The logon server could not be found
-2147022680800708A8There is already a logon domain for this computer
-2147022679800708A9The logon server could not validate the logon
-2147022677800708ABThe security database could not be found
-2147022676800708ACThe group name could not be found
-2147022675800708ADThe user name could not be found
-2147022674800708AEThe resource name could not be found
-2147022673800708AFThe group already exists
-2147022672800708B0The account already exists
-2147022671800708B1The resource permission list already exists
-2147022670800708B2This operation is only allowed on the primary domain controller of the domain
-2147022669800708B3The security database has not been started
-2147022668800708B4There are too many names in the user accounts database
-2147022667800708B5A disk I/O failure occurred
-2147022666800708B6The limit of 64 entries per resource was exceeded
-2147022665800708B7Deleting a user with a session is not allowed
-2147022664800708B8The parent directory could not be located
-2147022663800708B9Unable to add to the security database session cache segment
-2147022662800708BAThis operation is not allowed on this special group
-2147022661800708BBThis user is not cached in user accounts database session cache
-2147022660800708BCThe user already belongs to this group
-2147022659800708BDThe user does not belong to this group
-2147022658800708BEThis user account is undefined
-2147022657800708BFThis user account has expired
-2147022656800708C0The user is not allowed to log on from this workstation
-2147022655800708C1The user is not allowed to log on at this time
-2147022654800708C2The password of this user has expired
-2147022653800708C3The password of this user cannot change
-2147022652800708C4This password cannot be used now
-2147022651800708C5The password does not meet the password policy requirements. Check the minimum password length
-2147022650800708C6The password of this user is too recent to change
-2147022649800708C7The security database is corrupted
-2147022648800708C8No updates are necessary to this replicant network/local security database
-2147022647800708C9This replicant database is outdated; synchronization is required
-2147022646800708CAThis network connection does not exist
-2147022645800708CBThis asg_type is invalid
-2147022644800708CCThis device is currently being shared
-2147022643800708CDThe user name may not be same as computer name
-2147022626800708DEThe computer name could not be added as a message alias. The name may already exist on the network
-2147022625800708DFThe Messenger service is already started
-2147022624800708E0The Messenger service failed to start
-2147022623800708E1The message alias could not be found on the network
-2147022622800708E2This message alias has already been forwarded
-2147022621800708E3This message alias has been added but is still forwarded
-2147022620800708E4This message alias already exists locally
-2147022619800708E5The maximum number of added message aliases has been exceeded
-2147022618800708E6The computer name could not be deleted
-2147022617800708E7Messages cannot be forwarded back to the same workstation
-2147022616800708E8An error occurred in the domain message processor
-2147022615800708E9The message was sent
-2147022614800708EAThe message was sent but not received
-2147022613800708EBThe message alias is currently in use. Try again later
-2147022612800708ECThe Messenger service has not been started
-2147022611800708EDThe name is not on the local computer
-2147022610800708EEThe forwarded message alias could not be found on the network
-2147022609800708EFThe message alias table on the remote station is full
-2147022608800708F0Messages for this alias are not currently being forwarded
-2147022607800708F1The broadcast message was truncated
-2147022602800708F6This is an invalid device name
-2147022601800708F7A write fault occurred
-2147022599800708F9A duplicate message alias exists on the network
-2147022598800708FAThis message alias will be deleted later
-2147022597800708FBThe message alias was not successfully deleted from all networks
-2147022596800708FCThis operation is not supported on computers with multiple networks
-214702258680070906This shared resource does not exist
-214702258580070907This device is not shared
-214702258480070908A session does not exist with that computer name
-21470225828007090AThere is not an open file with that identification number
-21470225818007090BA failure occurred when executing a remote administration command
-21470225808007090CA failure occurred when opening a remote temporary file
-21470225798007090DThe data returned from a remote administration command has been truncated to 64K
-21470225788007090EThis device cannot be shared as both a spooled and a non-spooled resource
-21470225778007090FThe information in the list of servers may be incorrect
-214702257680070910The computer is not active in this domain
-214702257580070911The share must be removed from the Distributed File System before it can be deleted
-21470225658007091BThe operation is invalid for this device
-21470225648007091CThis device cannot be shared
-21470225638007091DThis device was not open
-21470225628007091EThis device name list is invalid
-21470225618007091FThe queue priority is invalid
-214702255980070921There are no shared communication devices
-214702255880070922The queue you specified does not exist
-214702255680070924This list of devices is invalid
-214702255580070925The requested device is invalid
-214702255480070926This device is already in use by the spooler
-214702255380070927This device is already in use as a communication device
-21470225458007092FThis computer name is invalid
-214702254280070932The string and prefix specified are too long
-214702254080070934This path component is invalid
-214702253980070935Could not determine the type of input
-21470225348007093AThe buffer for types is not big enough
-214702252680070942Profile files cannot exceed 64K
-214702252580070943The start offset is out of range
-214702252480070944The system cannot delete current connections to network resources
-214702252380070945The system was unable to parse the command line in this file
-214702252280070946An error occurred while loading the profile file
-214702252180070947Errors occurred while saving the profile file. The profile was partially saved
-214702251980070949Log file %1 is full
-21470225188007094AThis log file has changed between reads
-21470225178007094BLog file %1 is corrupt
-21470225168007094CThe source path cannot be a directory
-21470225158007094DThe source path is illegal
-21470225148007094EThe destination path is illegal
-21470225138007094FThe source and destination paths are on different servers
-214702251180070951The Run server you requested is paused
-214702250780070955An error occurred when communicating with a Run server
-214702250580070957An error occurred when starting a background process
-214702250480070958The shared resource you are connected to could not be found
-214702249680070960The LAN adapter number is invalid
-214702249580070961This network connection has files open or requests pending
-214702249480070962Active connections still exist
-214702249380070963This share name or password is invalid
-214702249280070964The device is in use by an active process and cannot be disconnected
-214702249180070965The drive letter is in use locally
-21470224668007097EThe specified client is already registered for the specified event
-21470224658007097FThe alert table is full
-214702246480070980An invalid or nonexistent alert name was raised
-214702246380070981The alert recipient is invalid
-214702246280070982A user's session with this server has been deletedbecause the user's logon hours are no longer valid
-214702245680070988The log file does not contain the requested record number
-214702244680070992The user accounts database is not configured correctly
-214702244580070993This operation is not permitted when the Netlogon service is running
-214702244480070994This operation is not allowed on the last administrative account
-214702244380070995Could not find domain controller for this domain
-214702244280070996Could not set logon information for this user
-214702244180070997The Netlogon service has not been started
-214702244080070998Unable to add to the user accounts database
-214702243980070999This server's clock is not synchronized with the primary domain controller's clock
-21470224388007099AA password mismatch has been detected
-21470224368007099CThe server identification does not specify a valid server
-21470224358007099DThe session identification does not specify a valid session
-21470224348007099EThe connection identification does not specify a valid connection
-21470224338007099FThere is no space for another entry in the table of available servers
-2147022432800709A0The server has reached the maximum number of sessions it supports
-2147022431800709A1The server has reached the maximum number of connections it supports
-2147022430800709A2The server cannot open more files because it has reached its maximum number
-2147022429800709A3There are no alternate servers registered on this server
-2147022426800709A6Try down-level (remote admin protocol) version of API instead
-2147022416800709B0The UPS driver could not be accessed by the UPS service
-2147022415800709B1The UPS service is not configured correctly
-2147022414800709B2The UPS service could not access the specified Comm Port
-2147022413800709B3The UPS indicated a line fail or low battery situation. Service not started
-2147022412800709B4The UPS service failed to perform a system shut down
-2147022396800709C4The program below returned an MS-DOS error code:
-2147022395800709C5The program below needs more memory:
-2147022394800709C6The program below called an unsupported MS-DOS function:
-2147022393800709C7The workstation failed to boot
-2147022392800709C8The file below is corrupt
-2147022391800709C9No loader is specified in the boot-block definition file
-2147022390800709CANetBIOS returned an error: The NCB and SMB are dumped above
-2147022389800709CBA disk I/O error occurred
-2147022388800709CCImage parameter substitution failed
-2147022387800709CDToo many image parameters cross disk sector boundaries
-2147022386800709CEThe image was not generated from an MS-DOS diskette formatted with /S
-2147022385800709CFRemote boot will be restarted later
-2147022384800709D0The call to the Remoteboot server failed
-2147022383800709D1Cannot connect to the Remoteboot server
-2147022382800709D2Cannot open image file on the Remoteboot server
-2147022381800709D3Connecting to the Remoteboot server
-2147022380800709D4Connecting to the Remoteboot server
-2147022379800709D5Remote boot service was stopped; check the error log for the cause of the problem
-2147022378800709D6Remote boot startup failed; check the error log for the cause of the problem
-2147022377800709D7A second connection to a Remoteboot resource is not allowed
-2147022346800709F6The browser service was configured with MaintainServerList=No
-214702228680070A32Service failed to start since none of the network adapters started with this service
-214702228580070A33Service failed to start due to bad startup information in the registry
-214702228480070A34Service failed to start because its database is absent or corrupt
-214702228380070A35Service failed to start because RPLFILES share is absent
-214702228280070A36Service failed to start because RPLUSER group is absent
-214702228180070A37Cannot enumerate service records
-214702228080070A38Workstation record information has been corrupted
-214702227980070A39Workstation record was not found
-214702227880070A3AWorkstation name is in use by some other workstation
-214702227780070A3BProfile record information has been corrupted
-214702227680070A3CProfile record was not found
-214702227580070A3DProfile name is in use by some other profile
-214702227480070A3EThere are workstations using this profile
-214702227380070A3FConfiguration record information has been corrupted
-214702227280070A40Configuration record was not found
-214702227180070A41Adapter id record information has been corrupted
-214702227080070A42An internal service error has occurred
-214702226980070A43Vendor id record information has been corrupted
-214702226880070A44Boot block record information has been corrupted
-214702226780070A45The user account for this workstation record is missing
-214702226680070A46The RPLUSER local group could not be found
-214702226580070A47Boot block record was not found
-214702226480070A48Chosen profile is incompatible with this workstation
-214702226380070A49Chosen network adapter id is in use by some other workstation
-214702226280070A4AThere are profiles using this configuration
-214702226180070A4BThere are workstations
-214702226080070A4CService failed to backup Remoteboot database
-214702225980070A4DAdapter record was not found
-214702225880070A4EVendor record was not found
-214702225780070A4FVendor name is in use by some other vendor record
-214702225680070A50(boot name
-214702225580070A51Configuration name is in use by some other configuration
-214702223680070A64The internal database maintained by the DFS service is corrupt
-214702223580070A65One of the records in the internal DFS database is corrupt
-214702223480070A66There is no DFS name whose entry path matches the input Entry Path
-214702223380070A67A root or link with the given name already exists
-214702223280070A68The server share specified is already shared in the DFS
-214702223180070A69The indicated server share does not support the indicated DFS namespace
-214702223080070A6AThe operation is not valid on this portion of the namespace
-214702222980070A6BThe operation is not valid on this portion of the namespace
-214702222880070A6CThe operation is ambiguous because the link has multiple servers
-214702222780070A6DUnable to create a link
-214702222680070A6EThe server is not DFS Aware
-214702222580070A6FThe specified rename target path is invalid
-214702222480070A70The specified DFS link is offline
-214702222380070A71The specified server is not a server for this link
-214702222280070A72A cycle in the DFS name was detected
-214702222180070A73The operation is not supported on a server-based DFS
-214702222080070A74This link is already supported by the specified server-share
-214702221980070A75Can't remove the last server-share supporting this root or link
-214702221880070A76The operation is not supported for an Inter-DFS link
-214702221780070A77The internal state of the DFS Service has become inconsistent
-214702221680070A78The DFS Service has been installed on the specified server
-214702221580070A79The DFS data being reconciled is identical
-214702221480070A7AThe DFS root cannot be deleted - Uninstall DFS if required
-214702221380070A7BA child or parent directory of the share is already in a DFS
-214702220680070A82DFS internal error
-214702220580070A83This machine is already joined to a domain
-214702220480070A84This machine is not currently joined to a domain
-214702220380070A85This machine is a domain controller and cannot be unjoined from a domain
-214702220280070A86The destination domain controller does not support creating machine accounts in OUs
-214702220180070A87The specified workgroup name is invalid
-214702220080070A88The specified computer name is incompatible with the default language used on the domain controller
-214702219980070A89The specified computer account could not be found. Contact an administrator to verify the account is in the domain. If the account has been deleted unjoin
-214702219880070A8AThis version of Windows cannot be joined to a domain
-214702219780070A8BAn attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting
-214702219680070A8CThis device is joined to Azure AD. To join an Active Directory domain
-214702219580070A8DPassword must change at next logon
-214702219480070A8EAccount is locked out
-214702219380070A8FPassword is too long
-214702219280070A90Password doesn't meet the complexity policy
-214702219180070A91Password doesn't meet the requirements of the filter dll's
-214702218780070A95Offline join completion information was not found
-214702218680070A96The offline join completion information was bad
-214702218580070A97Unable to create offline join information. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required
-214702218480070A98The domain join info being saved was incomplete or bad
-214702218380070A99Offline join operation successfully completed but a restart is needed
-214702218280070A9AThere was no offline join operation pending
-214702218180070A9BUnable to set one or more requested machine or domain name values on the local computer
-214702218080070A9CCould not verify the current machine's hostname against the saved value in the join completion information
-214702217980070A9DUnable to load the specified offline registry hive. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required
-214702217880070A9EThe minimum session security requirements for this operation were not met
-214702217780070A9FComputer account provisioning blob version is not supported
-214702217680070AA0The specified domain controller does not meet the version requirement for this operation. Please select a domain controller capable of issuing claims
-214702217580070AA1This operation requires a domain controller which supports LDAP. Please select an LDAP-capable domain controller
-214702217480070AA2A domain controller which meets the version requirement for this operation could not be located. Please ensure that a domain controller capable of issuing claims is available
-214702217380070AA3The Windows version of the specified image does not support provisioning
-214702217280070AA4The machine name is blocked from joining the domain
-214702217180070AA5The domain controller does not meet the version requirement for this operation. See http://go.microsoft.com/fwlink/?LinkId=294288 for more information
-214702217080070AA6The local machine does not allow querying of LSA secrets in plain-text
-214702216980070AA7Unable to leave the Azure AD domain that this machine is joined to. Check the event log for detailed error information
-214702189780070BB7This is the last error in NERR range
-214702189680070BB8The specified print monitor is unknown
-214702189580070BB9The specified printer driver is currently in use
-214702189480070BBAThe spool file was not found
-214702189380070BBBA StartDocPrinter call was not issued
-214702189280070BBCAn AddJob call was not issued
-214702189180070BBDThe specified print processor has already been installed
-214702189080070BBEThe specified print monitor has already been installed
-214702188980070BBFThe specified print monitor does not have the required functions
-214702188880070BC0The specified print monitor is currently in use
-214702188780070BC1The requested operation is not allowed when there are jobs queued to the printer
-214702188680070BC2The requested operation is successful. Changes will not be effective until the system is rebooted
-214702188580070BC3The requested operation is successful. Changes will not be effective until the service is restarted
-214702188480070BC4No printers were found
-214702188380070BC5The printer driver is known to be unreliable
-214702188280070BC6The printer driver is known to harm the system
-214702188180070BC7The specified printer driver package is currently in use
-214702188080070BC8Unable to find a core driver package that is required by the printer driver package
-214702187980070BC9The requested operation failed. A system reboot is required to roll back changes made
-214702187880070BCAThe requested operation failed. A system reboot has been initiated to roll back changes made
-214702187780070BCBThe specified printer driver was not found on the system and needs to be downloaded
-214702187680070BCCThe requested print job has failed to print. A print system update requires the job to be resubmitted
-214702187580070BCDThe printer driver does not contain a valid manifest
-214702187480070BCEThe specified printer cannot be shared
-214702187380070BCFThere is a problem with a configuration of user specifiedshut down command file. The UPS service started anyway
-214702187180070BD1A defective sector on drive %1 has been replaced (hotfixed).No data was lost. You should run CHKDSK soon to restore fullperformance and replenish the volume's spare sector pool.The hotfix occurred while processing a remote request
-214702187080070BD2A disk error occurred on the HPFS volume in drive %1.The error occurred while processing a remote request
-214702186980070BD3The user accounts database (NET.ACC) is corrupted. The local securitysystem is replacing the corrupted NET.ACC with the backupmade on %1 at %2.Any updates made to the database after this time are lost
-214702186880070BD4The user accounts database (NET.ACC) is missing. The localsecurity system is restoring the backup databasemade on %1 at %2.Any updates made to the database after this time are lost
-214702186780070BD5Local security could not be started because the user accounts database(NET.ACC) was missing or corrupted
-214702186680070BD6The server cannot export directory %1
-214702186580070BD7The replication server could not update directory %2 from the sourceon %3 due to error %1
-214702186480070BD8Master %1 did not send an update notice for directory %2 at the expectedtime
-214702186380070BD9User %1 has exceeded account limitation %2 on server %3
-214702186280070BDAThe primary domain controller for domain %1 failed
-214702186180070BDBFailed to authenticate with %2
-214702186080070BDCThe replicator attempted to log on at %2 as %1 and failed
-214702185980070BDD@I *LOGON HOURS
-214702185880070BDEReplicator could not access %2on %3 due to system error %1
-214702185780070BDFReplicator limit for files in a directory has been exceeded
-214702185680070BE0Replicator limit for tree depth has been exceeded
-214702185580070BE1The replicator cannot update directory %1. It has tree integrityand is the current directory for some process
-214702185480070BE2Network error %1 occurred
-214702185180070BE5System error %1 occurred
-214702185080070BE6Cannot log on. User is currently logged on and argument TRYUSERis set to NO
-214702184980070BE7IMPORT path %1 cannot be found
-214702184880070BE8EXPORT path %1 cannot be found
-214702184780070BE9Replicated data has changed in directory %1
-214702184680070BEAThe operation was paused
-214702184580070BEBThe Registry or the information you just typed includes an illegalvalue for "%1"
-214702184480070BECThe required parameter was not provided on the commandline or in the configuration file
-214702184380070BEDLAN Manager does not recognize "%1" as a valid option
-214702184280070BEEA request for resource could not be satisfied
-214702184180070BEFA problem exists with the system configuration
-214702184080070BF0A system error has occurred
-214702183980070BF1An internal consistency error has occurred
-214702183880070BF2The configuration file or the command line has an ambiguous option
-214702183780070BF3The configuration file or the command line has a duplicate parameter
-214702183680070BF4The condition supplied for the app execution request was not satisfied
-214702183580070BF5The supplied handle has been invalidated and may not be used for the requested operation
-214702183480070BF6The supplied host generation has been invalidated and may not be used for the requested operation
-214702183380070BF7An attempt to register a process failed because the target host was not in a valid state to receive process registrations
-214702183280070BF8The host is not in a valid state to support the execution request
-214702183180070BF9The operation was not completed because a required resource donor was not found for the host
-214702183080070BFAThe operation was not completed because an unexpected host ID was encountered
-214702182980070BFBThe operation was not completed because the specified user was not known to the service
-214702182680070BFEmemory
-214702182580070BFFdisk space
-214702182480070C00thread
-214702182380070C01process
-214702182280070C02Security Failure
-214702182180070C03Bad or missing LAN Manager root directory
-214702182080070C04The network software is not installed
-214702181980070C05The server is not started
-214702181880070C06The server cannot access the user accounts database (NET.ACC)
-214702181780070C07Incompatible files are installed in the LANMAN tree
-214702181680070C08The LANMAN\LOGS directory is invalid
-214702181580070C09The domain specified could not be used
-214702181480070C0AThe computer name is being used as a message alias on another computer
-214702181380070C0BThe announcement of the server name failed
-214702181280070C0CThe user accounts database is not configured correctly
-214702181180070C0DThe server is not running with user-level security
-214702180980070C0FThe workstation is not configured properly
-214702180880070C10View your error log for details
-214702180780070C11Unable to write to this file
-214702180680070C12ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SERand reapply all ADDPAKs
-214702180580070C13The LM386 server cannot be started because CACHE.EXE is not running
-214702180480070C14There is no account for this computer in the security database
-214702180380070C15This computer is not a member of the group SERVERS
-214702180280070C16The group SERVERS is not present in the local security database
-214702180180070C17This computer is configured as a member of a workgroup
-214702180080070C18The primary Domain Controller for this domain could not be located
-214702179980070C19This computer is configured to be the primary domain controller of its domain.However
-214702179880070C1AThe service failed to authenticate with the primary domain controller
-214702179780070C1BThere is a problem with the security database creation date or serial number
-214702179680070C1CThe operation failed because a network software error occurred
-214702179580070C1DThe system ran out of a resource controlled by the %1 option
-214702179480070C1EThe service failed to obtain a long-term lock on thesegment for network control blocks (NCBs). The error code is the data
-214702179380070C1FThe service failed to release the long-term lock on thesegment for network control blocks (NCBs). The error code is the data
-214702179280070C20There was an error stopping service %1.The error code from NetServiceControl is the data
-214702179180070C21Initialization failed because of a system execution failure onpath %1. The system error code is the data
-214702179080070C22An unexpected network control block (NCB) was received. The NCB is the data
-214702178980070C23The network is not started
-214702178880070C24A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed.The data shown is in this format:DWORD approx CS:IP of call to ioctl or fsctlWORD error codeWORD ioctl or fsctl number
-214702178780070C25Unable to create or open system semaphore %1.The error code is the data
-214702178680070C26Initialization failed because of an open/create error on thefile %1. The system error code is the data
-214702178580070C27An unexpected NetBIOS error occurred.The error code is the data
-214702178480070C28An illegal server message block (SMB) was received.The SMB is the data
-214702178380070C29Initialization failed because the requested service %1could not be started
-214702178280070C2ASome entries in the error log were lost because of a bufferoverflow
-214702177680070C30Initialization parameters controlling resource usage otherthan net buffers are sized so that too much memory is needed
-214702177580070C31The server cannot increase the size of a memory segment
-214702177480070C32Initialization failed because account file %1 is either incorrector not present
-214702177380070C33Initialization failed because network %1 was not started
-214702177280070C34The server failed to start. Either all three chdevparameters must be zero or all three must be nonzero
-214702177180070C35A remote API request was halted due to the followinginvalid description string: %1
-214702177080070C36The network %1 ran out of network control blocks (NCBs). You may need to increase NCBsfor this network. The following information includes thenumber of NCBs submitted by the server when this error occurred:
-214702176980070C37The server cannot create the %1 mailslot needed to sendthe ReleaseMemory alert message. The error received is:
-214702176880070C38The server failed to register for the ReleaseMemory alert
-214702176780070C39The server cannot update the AT schedule file. The fileis corrupted
-214702176680070C3AThe server encountered an error when callingNetIMakeLMFileName. The error code is the data
-214702176580070C3BInitialization failed because of a system execution failure onpath %1. There is not enough memory to start the process.The system error code is the data
-214702176480070C3CLongterm lock of the server buffers failed.Check swap disk's free space and restart the system to start the server
-214702175680070C44The service has stopped due to repeated consecutiveoccurrences of a network control block (NCB) error. The last bad NCB followsin raw data
-214702175580070C45The Message server has stopped due to a lock on theMessage server shared data segment
-214702174680070C4EA file system error occurred while opening or writing to thesystem message log file %1. Message logging has beenswitched off due to the error. The error code is the data
-214702174580070C4FUnable to display message POPUP due to system VIO call error.The error code is the data
-214702174480070C50An illegal server message block (SMB) was received. The SMB is the data
-214702173680070C58The workstation information segment is bigger than 64K.The size follows
-214702173580070C59The workstation was unable to get the name-number of the computer
-214702173480070C5AThe workstation could not initialize the Async NetBIOS Thread.The error code is the data
-214702173380070C5BThe workstation could not open the initial shared segment.The error code is the data
-214702173280070C5CThe workstation host table is full
-214702173180070C5DA bad mailslot server message block (SMB) was received. The SMB is the data
-214702173080070C5EThe workstation encountered an error while trying to start the user accounts database.The error code is the data
-214702172980070C5FThe workstation encountered an error while responding to an SSI revalidation request.The function code and the error codes are the data
-214702172680070C62The Alerter service had a problem creating the list ofalert recipients. The error code is %1
-214702172580070C63There was an error expanding %1 as a group name. Trysplitting the group into two or more smaller groups
-214702172480070C64There was an error sending %2 the alert message -(%3 )The error code is %1
-214702172380070C65There was an error in creating or reading the alerter mailslot.The error code is %1
-214702172280070C66The server could not read the AT schedule file
-214702172180070C67The server found an invalid AT schedule record
-214702172080070C68The server could not find an AT schedule file so it created one
-214702171980070C69The server could not access the %1 network with NetBiosOpen
-214702171880070C6AThe AT command processor could not run %1
-214702171680070C6CWARNING: Because of a lazy-write error
-214702171580070C6DA defective sector on drive %1 has been replaced (hotfixed).No data was lost. You should run CHKDSK soon to restore fullperformance and replenish the volume's spare sector pool.The hotfix occurred while processing a remote request
-214702171480070C6EA disk error occurred on the HPFS volume in drive %1.The error occurred while processing a remote request
-214702171380070C6FThe user accounts database (NET.ACC) is corrupted. The local securitysystem is replacing the corrupted NET.ACC with the backupmade at %1.Any updates made to the database after this time are lost
-214702171280070C70The user accounts database (NET.ACC) is missing. The localsecurity system is restoring the backup databasemade at %1.Any updates made to the database made after this time are lost
-214702171180070C71Local security could not be started because the user accounts database(NET.ACC) was missing or corrupted
-214702171080070C72Local security could not be started because an erroroccurred during initialization. The error code returned is %1.THE SYSTEM IS NOT SECURE
-214702170680070C76A NetWksta internal error has occurred:%1
-214702170580070C77The redirector is out of a resource: %1
-214702170480070C78A server message block (SMB) error occurred on the connection to %1.The SMB header is the data
-214702170380070C79A virtual circuit error occurred on the session to %1.The network control block (NCB) command and return code is the data
-214702170280070C7AHanging up a stuck session to %1
-214702170180070C7BA network control block (NCB) error occurred (%1).The NCB is the data
-214702170080070C7CA write operation to %1 failed.Data may have been lost
-214702169980070C7DReset of driver %1 failed to complete the network control block (NCB).The NCB is the data
-214702169880070C7EThe amount of resource %1 requested was morethan the maximum. The maximum amount was allocated
-214702169280070C84The server could not create a thread.The THREADS parameter in the CONFIG.SYS file should be increased
-214702169180070C85The server could not close %1.The file is probably corrupted
-214702169080070C86The replicator cannot update directory %1. It has tree integrityand is the current directory for some process
-214702168980070C87The server cannot export directory %1 to client %2.It is exported from another server
-214702168880070C88The replication server could not update directory %2 from the sourceon %3 due to error %1
-214702168780070C89Master %1 did not send an update notice for directory %2 at the expectedtime
-214702168680070C8AThis computer could not authenticate with %2
-214702168580070C8BThe replicator attempted to log on at %2 as %1 and failed
-214702168480070C8CNetwork error %1 occurred
-214702168380070C8DReplicator limit for files in a directory has been exceeded
-214702168280070C8EReplicator limit for tree depth has been exceeded
-214702168180070C8FUnrecognized message received in mailslot
-214702168080070C90System error %1 occurred
-214702167980070C91Cannot log on. User is currently logged on and argument TRYUSERis set to NO
-214702167880070C92IMPORT path %1 cannot be found
-214702167780070C93EXPORT path %1 cannot be found
-214702167680070C94Replicator failed to update signal file in directory %2 due to%1 system error
-214702167580070C95Disk Fault Tolerance Error%1
-214702167480070C96Replicator could not access %2on %3 due to system error %1
-214702167380070C97The primary domain controller for domain %1 has apparently failed
-214702167280070C98Changing machine account password for account %1 failed withthe following error: %2
-214702167180070C99An error occurred while updating the logon or logoff information for %1
-214702167080070C9AAn error occurred while synchronizing with primary domain controller %1
-214702166980070C9BThe session setup to the Windows Domain Controller %1 for the domain %2failed because %1 does not support signing or sealing the Netlogonsession.Either upgrade the Domain controller or set the RequireSignOrSealregistry entry on this machine to 0
-214702166680070C9EA power failure was detected at the server
-214702166580070C9FThe UPS service performed server shut down
-214702166480070CA0The UPS service did not complete execution of theuser specified shut down command file
-214702166380070CA1The UPS driver could not be opened. The error code isthe data
-214702166280070CA2Power has been restored
-214702166180070CA3There is a problem with a configuration of user specifiedshut down command file
-214702166080070CA4The UPS service failed to execute a user specified shutdowncommand file %1. The error code is the data
-214702164680070CB2Initialization failed because of an invalid or missingparameter in the configuration file %1
-214702164580070CB3Initialization failed because of an invalid line in theconfiguration file %1. The invalid line is the data
-214702164480070CB4Initialization failed because of an error in the configurationfile %1
-214702164380070CB5The file %1 has been changed after initialization.The boot-block loading was temporarily terminated
-214702164280070CB6The files do not fit to the boot-block configurationfile %1. Change the BASE and ORG definitions or the orderof the files
-214702164180070CB7Initialization failed because the dynamic-linklibrary %1 returned an incorrect version number
-214702164080070CB8There was an unrecoverable error in the dynamic-link library of the service
-214702163980070CB9The system returned an unexpected error code.The error code is the data
-214702163880070CBAThe fault-tolerance error log file
-214702163780070CBBThe fault-tolerance error-log file
-214702163680070CBCThis computer has been successfully joined to domain '%1'
-214702163580070CBDThis computer has been successfully joined to workgroup '%1'
-214702159780070CE3%1 %2 %3 %4 %5 %6 %7 %8 %9
-214702159580070CE5Remote IPC
-214702159480070CE6Remote Admin
-214702159380070CE7Logon server share
-214702159280070CE8A network error occurred
-214702149680070D48There is not enough memory to start the Workstation service
-214702149580070D49An error occurred when reading the NETWORKS entry in the LANMAN.INI file
-214702149480070D4AThis is an invalid argument: %1
-214702149380070D4BThe %1 NETWORKS entry in the LANMAN.INI file has asyntax error and will be ignored
-214702149280070D4CThere are too many NETWORKS entries in the LANMAN.INI file
-214702149080070D4EAn error occurred when opening networkdevice driver %1 = %2
-214702148980070D4FDevice driver %1 sent a bad BiosLinkage response
-214702148880070D50The program cannot be used with this operating system
-214702148780070D51The redirector is already installed
-214702148680070D52Installing NETWKSTA.SYS Version %1.%2.%3 (%4)
-214702148580070D53There was an error installing NETWKSTA.SYS.Press ENTER to continue
-214702148480070D54Resolver linkage problem
-214702148380070D55Your logon time at %1 ends at %2.Please clean up and log off
-214702148280070D56You will be automatically disconnected at %1
-214702148180070D57Your logon time at %1 has ended
-214702148080070D58Your logon time at %1 ended at %2
-214702147980070D59WARNING: You have until %1 to logoff. If youhave not logged off at this time
-214702147880070D5AWARNING: You must log off at %1 now. You havetwo minutes to log off
-214702147780070D5BYou have open files or devices
-214702147680070D5CDefault Share for Internal Use
-214702147580070D5DMessenger Service
-214702139680070DACThe command completed successfully
-214702139580070DADYou used an invalid option
-214702139480070DAESystem error %1 has occurred
-214702139380070DAFThe command contains an invalid number of arguments
-214702139280070DB0The command completed with one or more errors
-214702139180070DB1You used an option with an invalid value
-214702139080070DB2The option %1 is unknown
-214702138980070DB3Option %1 is ambiguous
-214702138680070DB6A command was used with conflicting switches
-214702138580070DB7Could not find subprogram %1
-214702138480070DB8The software requires a newer version of the operatingsystem
-214702138380070DB9More data is available than can be returned by Windows
-214702138280070DBAMore help is available by typing NET HELPMSG %1
-214702138180070DBBThis command can be used only on a Windows Domain Controller
-214702138080070DBCThis command cannot be used on a Windows Domain Controller
-214702137680070DC0These Windows services are started:
-214702137580070DC1The %1 service is not started
-214702137480070DC2The %1 service is starting
-214702137380070DC3The %1 service could not be started
-214702137280070DC4The %1 service was started successfully
-214702137180070DC5Stopping the Workstation service also stops the Server service
-214702137080070DC6The workstation has open files
-214702136980070DC7The %1 service is stopping
-214702136880070DC8The %1 service could not be stopped
-214702136780070DC9The %1 service was stopped successfully
-214702136680070DCAThe following services are dependent on the %1 service.Stopping the %1 service will also stop these services
-214702136380070DCDThe service is starting or stopping. Please try again later
-214702136280070DCEThe service did not report an error
-214702136180070DCFAn error occurred controlling the device
-214702136080070DD0The %1 service was continued successfully
-214702135980070DD1The %1 service was paused successfully
-214702135880070DD2The %1 service failed to resume
-214702135780070DD3The %1 service failed to pause
-214702135680070DD4The %1 service continue is pending
-214702135580070DD5The %1 service pause is pending
-214702135480070DD6%1 was continued successfully
-214702135380070DD7%1 was paused successfully
-214702135280070DD8The %1 service has been started by another process and is pending
-214702134980070DDBA service specific error occurred: %1
-214702123680070E4CThese workstations have sessions on this server:
-214702123580070E4DThese workstations have sessions with open files on this server:
-214702123080070E52The message alias is forwarded
-214702122680070E56You have these remote connections:
-214702122580070E57Continuing will cancel the connections
-214702122180070E5BThe session from %1 has open files
-214702122080070E5CNew connections will be remembered
-214702121980070E5DNew connections will not be remembered
-214702121880070E5EAn error occurred while saving your profile : Access Denied. The state of your remembered connections has not changed
-214702121780070E5FAn error occurred while reading your profile
-214702121680070E60An error occurred while restoring the connection to %1
-214702121480070E62No network services are started
-214702121380070E63There are no entries in the list
-214702120880070E68Users have open files on %1. Continuing the operation will force the files closed
-214702120780070E69The Workstation service is already running. Windows will ignore command options for the workstation
-214702120580070E6BThere are open files and/or incomplete directory searches pending on the connection to %1
-214702120380070E6DThe request will be processed at a domain controller for domain %1
-214702120280070E6EThe shared queue cannot be deleted while a print job is being spooled to the queue
-214702120180070E6F%1 has a remembered connection to %2
-214702118680070E7EAn error occurred while opening the Help file
-214702118580070E7FThe Help file is empty
-214702118480070E80The Help file is corrupted
-214702118380070E81Could not find a domain controller for domain %1
-214702118280070E82This operation is privileged on systems with earlierversions of the software
-214702118080070E84The device type is unknown
-214702117980070E85The log file has been corrupted
-214702117880070E86Program filenames must end with .EXE
-214702117780070E87A matching share could not be found so nothing was deleted
-214702117680070E88A bad value is in the units-per-week field of the user record
-214702117580070E89The password is invalid for %1
-214702117480070E8AAn error occurred while sending a message to %1
-214702117380070E8BThe password or user name is invalid for %1
-214702117180070E8DAn error occurred when the share was deleted
-214702117080070E8EThe user name is invalid
-214702116980070E8FThe password is invalid
-214702116880070E90The passwords do not match
-214702116780070E91Your persistent connections were not all restored
-214702116680070E92This is not a valid computer name or domain name
-214702116480070E94Default permissions cannot be set for that resource
-214702116280070E96A valid password was not entered
-214702116180070E97A valid name was not entered
-214702116080070E98The resource named cannot be shared
-214702115980070E99The permissions string contains invalid permissions
-214702115880070E9AYou can only perform this operation on printers and communication devices
-214702115480070E9E%1 is an invalid user or group name
-214702115380070E9FThe server is not configured for remote administration
-214702114480070EA8No users have sessions with this server
-214702114380070EA9User %1 is not a member of group %2
-214702114280070EAAUser %1 is already a member of group %2
-214702114180070EABThere is no such user: %1
-214702114080070EACThis is an invalid response
-214702113980070EADNo valid response was provided
-214702113880070EAEThe destination list provided does not match the destination list of the printer queue
-214702113780070EAFYour password cannot be changed until %1
-214702113680070EB0%1 is not a recognized day of the week
-214702113580070EB1The time range specified ends before it starts
-214702113480070EB2%1 is not a recognized hour
-214702113380070EB3%1 is not a valid specification for minutes
-214702113280070EB4Time supplied is not exactly on the hour
-214702113180070EB512 and 24 hour time formats may not be mixed
-214702113080070EB6%1 is not a valid 12-hour suffix
-214702112980070EB7An illegal date format has been supplied
-214702112880070EB8An illegal day range has been supplied
-214702112780070EB9An illegal time range has been supplied
-214702112680070EBAArguments to NET USER are invalid. Check the minimum passwordlength and/or arguments supplied
-214702112580070EBBThe value for ENABLESCRIPT must be YES
-214702112380070EBDAn illegal country/region code has been supplied
-214702112280070EBEThe user was successfully created but could not be addedto the USERS local group
-214702112180070EBFThe user context supplied is invalid
-214702112080070EC0The dynamic-link library %1 could not be loaded
-214702111980070EC1Sending files is no longer supported
-214702111880070EC2You may not specify paths for ADMIN$ and IPC$ shares
-214702111780070EC3User or group %1 is already a member of local group %2
-214702111680070EC4There is no such user or group: %1
-214702111580070EC5There is no such computer: %1
-214702111480070EC6The computer %1 already exists
-214702111380070EC7There is no such global user or group: %1
-214702111280070EC8Only disk shares can be marked as cacheable
-214702110680070ECEThe system could not find message: %1
-214702109480070EDAThis schedule date is invalid
-214702109380070EDBThe LANMAN root directory is unavailable
-214702109280070EDCThe SCHED.LOG file could not be opened
-214702109180070EDDThe Server service has not been started
-214702109080070EDEThe AT job ID does not exist
-214702108980070EDFThe AT schedule file is corrupted
-214702108880070EE0The delete failed due to a problem with the AT schedule file
-214702108780070EE1The command line cannot exceed 259 characters
-214702108680070EE2The AT schedule file could not be updated because the disk is full
-214702108480070EE4The AT schedule file is invalid. Please delete the file and create a new one
-214702108380070EE5The AT schedule file was deleted
-214702108280070EE6The syntax of this command is:AT [id] [/DELETE]AT time [/EVERY:date | /NEXT:date] commandThe AT command schedules a program command to run at alater date and time on a server. It also displays thelist of programs and commands scheduled to be run.You can specify the date as M
-214702108180070EE7The AT command has timed-out.Please try again later
-214702108080070EE8The minimum password age for user accounts cannot be greaterthan the maximum password age
-214702107980070EE9You have specified a value that is incompatiblewith servers with down-level software. Please specify a lower value
-214702102680070F1E%1 is not a valid computer name
-214702102580070F1F%1 is not a valid Windows network message number
-214702099680070F3CMessage from %1 to %2 on %3
-214702099580070F3D****
-214702099480070F3E**** unexpected end of message ****
-214702099180070F41Press ESC to exit
-214702099080070F42
-214702098680070F46Current time at %1 is %2
-214702098580070F47The current local clock is %1Do you want to set the local computer's time to match thetime at %2? %3:
-214702098480070F48Could not locate a time-server
-214702098380070F49Could not find the domain controller for domain %1
-214702098280070F4ALocal time (GMT%3) at %1 is %2
-214702098180070F4BThe user's home directory could not be determined
-214702098080070F4CThe user's home directory has not been specified
-214702097980070F4DThe name specified for the user's home directory (%1) is not a universal naming convention (UNC) name
-214702097880070F4EDrive %1 is now connected to %2. Your home directory is %3\%4
-214702097780070F4FDrive %1 is now connected to %2
-214702097680070F50There are no available drive letters left
-214702096480070F5C%1 is not a valid domain or workgroup name
-214702096180070F5FThe current SNTP value is: %1
-214702096080070F60This computer is not currently configured to use a specific SNTP server
-214702095980070F61This current autoconfigured SNTP value is: %1
-214702094680070F6EReissue the given operation as a cached IO operation
-214702094580070F6FYou specified too many values for the %1 option
-214702094480070F70You entered an invalid value for the %1 option
-214702094380070F71The syntax is incorrect
-214702093680070F78You specified an invalid file number
-214702093580070F79You specified an invalid print job number
-214702093380070F7BThe user or group account specified cannot be found
-214702093180070F7DThe user was added but could not be enabled for File and PrintServices for NetWare
-214702093080070F7EFile and Print Services for NetWare is not installed
-214702092980070F7FCannot set user properties for File and Print Services for NetWare
-214702092880070F80Password for %1 is: %2
-214702092780070F81NetWare compatible logon
-214702089680070FA0WINS encountered an error while processing the command
-214702089580070FA1The local WINS cannot be deleted
-214702089480070FA2The importation from the file failed
-214702089380070FA3The backup failed. Was a full backup done before?
-214702089280070FA4The backup failed. Check the directory to which you are backing the database
-214702089180070FA5The name does not exist in the WINS database
-214702089080070FA6Replication with a nonconfigured partner is not allowed
-214702084680070FD2The version of the supplied content information is not supported
-214702084580070FD3The supplied content information is malformed
-214702084480070FD4The requested data cannot be found in local or peer caches
-214702084380070FD5No more data is available or required
-214702084280070FD6The supplied object has not been initialized
-214702084180070FD7The supplied object has already been initialized
-214702084080070FD8A shutdown operation is already in progress
-214702083980070FD9The supplied object has already been invalidated
-214702083880070FDAAn element already exists and was not replaced
-214702083780070FDBCan not cancel the requested operation as it has already been completed
-214702083680070FDCCan not perform the requested operation because it has already been carried out
-214702083580070FDDAn operation accessed data beyond the bounds of valid data
-214702083480070FDEThe requested version is not supported
-214702083380070FDFA configuration value is invalid
-214702083280070FE0The SKU is not licensed
-214702083180070FE1PeerDist Service is still initializing and will be available shortly
-214702083080070FE2Communication with one or more computers will be temporarily blocked due to recent errors
-214702079680071004The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address
-214702069680071068The GUID passed was not recognized as valid by a WMI data provider
-214702069580071069The instance name passed was not recognized as valid by a WMI data provider
-21470206948007106AThe data item ID passed was not recognized as valid by a WMI data provider
-21470206938007106BThe WMI request could not be completed and should be retried
-21470206928007106CThe WMI data provider could not be located
-21470206918007106DThe WMI data provider references an instance set that has not been registered
-21470206908007106EThe WMI data block or event notification has already been enabled
-21470206898007106FThe WMI data block is no longer available
-214702068880071070The WMI data service is not available
-214702068780071071The WMI data provider failed to carry out the request
-214702068680071072The WMI MOF information is not valid
-214702068580071073The WMI registration information is not valid
-214702068480071074The WMI data block or event notification has already been disabled
-214702068380071075The WMI data item or data block is read only
-214702068280071076The WMI data item or data block could not be changed
-21470206468007109AThis operation is only valid in the context of an app container
-21470206458007109BThis application can only run in the context of an app container
-21470206448007109CThis functionality is not supported in the context of an app container
-21470206438007109DThe length of the SID supplied is not a valid length for app container SIDs
-2147020596800710CCThe media identifier does not represent a valid medium
-2147020595800710CDThe library identifier does not represent a valid library
-2147020594800710CEThe media pool identifier does not represent a valid media pool
-2147020593800710CFThe drive and medium are not compatible or exist in different libraries
-2147020592800710D0The medium currently exists in an offline library and must be online to perform this operation
-2147020591800710D1The operation cannot be performed on an offline library
-2147020590800710D2The library
-2147020589800710D3The library
-2147020588800710D4No media is currently available in this media pool or library
-2147020587800710D5A resource required for this operation is disabled
-2147020586800710D6The media identifier does not represent a valid cleaner
-2147020585800710D7The drive cannot be cleaned or does not support cleaning
-2147020584800710D8The object identifier does not represent a valid object
-2147020583800710D9Unable to read from or write to the database
-2147020582800710DAThe database is full
-2147020581800710DBThe medium is not compatible with the device or media pool
-2147020580800710DCThe resource required for this operation does not exist
-2147020579800710DDThe operation identifier is not valid
-2147020578800710DEThe media is not mounted or ready for use
-2147020577800710DFThe device is not ready for use
-2147020576800710E0The operator or administrator has refused the request
-2147020575800710E1The drive identifier does not represent a valid drive
-2147020574800710E2Library is full. No slot is available for use
-2147020573800710E3The transport cannot access the medium
-2147020572800710E4Unable to load the medium into the drive
-2147020571800710E5Unable to retrieve the drive status
-2147020570800710E6Unable to retrieve the slot status
-2147020569800710E7Unable to retrieve status about the transport
-2147020568800710E8Cannot use the transport because it is already in use
-2147020567800710E9Unable to open or close the inject/eject port
-2147020566800710EAUnable to eject the medium because it is in a drive
-2147020565800710EBA cleaner slot is already reserved
-2147020564800710ECA cleaner slot is not reserved
-2147020563800710EDThe cleaner cartridge has performed the maximum number of drive cleanings
-2147020562800710EEUnexpected on-medium identifier
-2147020561800710EFThe last remaining item in this group or resource cannot be deleted
-2147020560800710F0The message provided exceeds the maximum size allowed for this parameter
-2147020559800710F1The volume contains system or paging files
-2147020558800710F2The media type cannot be removed from this library since at least one drive in the library reports it can support this media type
-2147020557800710F3This offline media cannot be mounted on this system since no enabled drives are present which can be used
-2147020556800710F4A cleaner cartridge is present in the tape library
-2147020555800710F5Cannot use the inject/eject port because it is not empty
-2147020554800710F6Error
-2147020553800710F7OK
-2147020552800710F8Y
-2147020551800710F9N
-2147020550800710FAAny
-2147020549800710FBA
-2147020548800710FCP
-2147020547800710FD(not found)
-2147020546800710FEThis file is currently not available for use on this computer
-2147020545800710FFThe remote storage service is not operational at this time
-214702054480071100The remote storage service encountered a media error
-214702054380071101Read
-214702054280071102Change
-214702054180071103Full
-214702054080071104Please type the password:
-214702053980071105Type the password for %1:
-214702053880071106Type a password for the user:
-214702053780071107Type the password for the shared resource:
-214702053680071108Type your password:
-214702053580071109Retype the password to confirm:
-21470205348007110AType the user's old password:
-21470205338007110BType the user's new password:
-21470205328007110CType your new password:
-21470205318007110DType the Replicator service password:
-21470205308007110EType your user name
-21470205298007110FType the domain or server where you want to change a password
-214702052880071110Type your user name:
-214702052780071111Network statistics for \\%1
-214702052680071112Printing options for %1
-214702052580071113Communication-device queues accessing %1
-214702052480071114Print job detail
-214702052380071115Communication-device queues at \\%1
-214702052280071116Printers at %1
-214702052180071117Printers accessing %1
-214702052080071118Print jobs at %1:
-214702051980071119Shared resources at %1
-21470205188007111AThe following running services can be controlled:
-21470205178007111BStatistics are available for the following running services:
-21470205168007111CUser accounts for \\%1
-21470205158007111DThe syntax of this command is:
-21470205148007111EThe options of this command are:
-21470205138007111FPlease enter the name of the Primary Domain Controller:
-214702051280071120The string you have entered is too long. The maximumis %1
-214702051180071121Sunday
-214702051080071122Monday
-214702050980071123Tuesday
-214702050880071124Wednesday
-214702050780071125Thursday
-214702050680071126The file or directory is not a reparse point
-214702050580071127The reparse point attribute cannot be set because it conflicts with an existing attribute
-214702050480071128The data present in the reparse point buffer is invalid
-214702050380071129The tag present in the reparse point buffer is invalid
-21470205028007112AThere is a mismatch between the tag specified in the request and the tag present in the reparse point
-21470205018007112BThe object manager encountered a reparse point while retrieving an object
-21470205008007112CTh
-21470204998007112DF
-21470204988007112ES
-21470204978007112FSa
-214702049680071130Fast Cache data not found
-214702049580071131Fast Cache data expired
-214702049480071132Fast Cache data corrupt
-214702049380071133Fast Cache data has exceeded its max size and cannot be updated
-214702049280071134Fast Cache has been ReArmed and requires a reboot until it can be updated
-214702049180071135Aliases for \\%1
-214702049080071136Alias name
-214702048980071137Comment
-214702048880071138Members
-21470204868007113AUser Accounts for \\%1
-21470204858007113BUser name
-21470204848007113CFull Name
-21470204838007113DComment
-21470204828007113EUser's comment
-21470204818007113FParameters
-214702048080071140Country/region code
-214702047980071141Privilege level
-214702047880071142Operator privileges
-214702047780071143Account active
-214702047680071144Secure Boot detected that rollback of protected data has been attempted
-214702047580071145The value is protected by Secure Boot policy and cannot be modified or deleted
-214702047480071146The Secure Boot policy is invalid
-214702047380071147A new Secure Boot policy did not contain the current publisher on its update list
-214702047280071148The Secure Boot policy is either not signed or is signed by a non-trusted signer
-214702047180071149Secure Boot is not enabled on this machine
-21470204708007114ASecure Boot requires that certain files and drivers are not replaced by other files or drivers
-21470204698007114BThe Secure Boot Supplemental Policy file was not authorized on this machine
-21470204688007114CThe Supplemental Policy is not recognized on this device
-21470204678007114DThe Antirollback version was not found in the Secure Boot Policy
-21470204668007114EThe Platform ID specified in the Secure Boot policy does not match the Platform ID on this device
-21470204658007114FThe Secure Boot policy file has an older Antirollback Version than this device
-214702046480071150The Secure Boot policy file does not match the upgraded legacy policy
-214702046380071151The Secure Boot policy file is required but could not be found
-214702046280071152Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy
-214702046180071153Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy
-214702046080071154Home directory
-214702045980071155Password required
-214702045880071156User may change password
-214702045780071157User profile
-214702045680071158The copy offload read operation is not supported by a filter
-214702045580071159The copy offload write operation is not supported by a filter
-21470204548007115AThe copy offload read operation is not supported for the file
-21470204538007115BThe copy offload write operation is not supported for the file
-21470204528007115CThis file is currently associated with a different stream id
-21470204518007115DThe volume must undergo garbage collection
-21470204508007115EThe WOF driver encountered a corruption in WIM image's Header
-21470204498007115FThe WOF driver encountered a corruption in WIM image's Resource Table
-214702044880071160The WOF driver encountered a corruption in the compressed file's Resource Table
-214702044680071162Computer name
-214702044580071163User name
-214702044480071164Software version
-214702044380071165Workstation active on
-214702044280071166Windows NT root directory
-214702044180071167Workstation domain
-214702044080071168Logon domain
-214702043980071169Other domain(s)
-21470204388007116ACOM Open Timeout (sec)
-21470204378007116BCOM Send Count (byte)
-21470204368007116CCOM Send Timeout (msec)
-21470204358007116DDOS session print time-out (sec)
-21470204348007116EMaximum error log size (K)
-21470204338007116FMaximum cache memory (K)
-214702043280071170Number of network buffers
-214702043180071171Number of character buffers
-214702043080071172Size of network buffers
-214702042980071173Size of character buffers
-214702042880071174Full Computer name
-214702042780071175Workstation Domain DNS Name
-214702042680071176Windows 2002
-214702041580071181Server Name
-214702041480071182Server Comment
-214702041380071183Send administrative alerts to
-214702041280071184Software version
-214702041180071185Peer Server
-214702041080071186Windows NT
-214702040980071187Server Level
-214702040880071188Windows NT Server
-214702040780071189Server is active on
-21470204048007118CServer hidden
-214702039680071194Single Instance Storage is not available on this volume
-21470203908007119AMaximum Logged On Users
-21470203898007119BMaximum concurrent administrators
-21470203888007119CMaximum resources shared
-21470203878007119DMaximum connections to resources
-21470203868007119EMaximum open files on server
-21470203858007119FMaximum open files per session
-2147020384800711A0Maximum file locks
-2147020376800711A8Idle session time (min)
-2147020370800711AEShare-level
-2147020369800711AFUser-level
-2147020366800711B2Unlimited Server
-2147020346800711C6System Integrity detected that policy rollback has been attempted
-2147020345800711C7Your organization used Device Guard to block this app. Contact your support person for more info
-2147020344800711C8The System Integrity policy is invalid
-2147020343800711C9The System Integrity policy is either not signed or is signed by a non-trusted signer
-2147020342800711CAThe number of System Integrity policies is out of limit
-2147020341800711CBThe Code Integrity supplemental policy is not authorized by a Code Integrity base policy
-2147020336800711D0Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled
-2147020335800711D1The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS
-2147020326800711DAThe Platform Manifest file was not authorized on this machine
-2147020325800711DBThe Platform Manifest file was not valid
-2147020324800711DCThe file is not authorized on this platform because an entry was not found in the Platform Manifest
-2147020323800711DDThe catalog is not authorized on this platform because an entry was not found in the Platform Manifest
-2147020322800711DEThe file is not authorized on this platform because a Binary ID was not found in the embedded signature
-2147020321800711DFNo active Platform Manifest exists on this system
-2147020320800711E0The Platform Manifest file was not properly signed
-2147020319800711E1Primary Domain controller for workstation domain:
-2147020318800711E2Lockout threshold:
-2147020317800711E3Lockout duration (minutes):
-2147020316800711E4Lockout observation window (minutes):
-2147020296800711F8Statistics since
-2147020295800711F9Sessions accepted
-2147020294800711FASessions timed-out
-2147020293800711FBSessions errored-out
-2147020292800711FCKilobytes sent
-2147020291800711FDKilobytes received
-2147020290800711FEMean response time (msec)
-2147020289800711FFNetwork errors
-214702028880071200Files accessed
-214702028780071201Print jobs spooled
-214702028680071202System errors
-214702028580071203Password violations
-214702028480071204Permission violations
-214702028380071205Communication devices accessed
-214702028280071206Sessions started
-214702028180071207Sessions reconnected
-214702028080071208Sessions starts failed
-214702027980071209Sessions disconnected
-21470202788007120ANetwork I/O's performed
-21470202778007120BFiles and pipes accessed
-21470202768007120CTimes buffers exhausted
-21470202758007120DBig buffers
-21470202748007120ERequest buffers
-21470202738007120FWorkstation Statistics for \\%1
-214702027280071210Server Statistics for \\%1
-214702027180071211Statistics since %1
-214702027080071212Connections made
-214702026980071213Connections failed
-214702026680071216Bytes received
-214702026580071217Server Message Blocks (SMBs) received
-214702026480071218Bytes transmitted
-214702026380071219Server Message Blocks (SMBs) transmitted
-21470202628007121ARead operations
-21470202618007121BWrite operations
-21470202608007121CRaw reads denied
-21470202598007121DRaw writes denied
-21470202588007121ENetwork errors
-21470202578007121FConnections made
-214702025680071220Reconnections made
-214702025580071221Server disconnects
-214702025480071222Sessions started
-214702025380071223Hung sessions
-214702025280071224Failed sessions
-214702025180071225Failed operations
-214702025080071226Use count
-214702024980071227Failed use count
-21470202468007122A%1 was deleted successfully
-21470202458007122B%1 was used successfully
-21470202448007122CThe message was successfully sent to %1
-21470202438007122DThe message name %1 was forwarded successfully
-21470202428007122EThe message name %1 was added successfully
-21470202418007122FThe message name forwarding was successfully canceled
-214702024080071230%1 was shared successfully
-214702023980071231The server %1 successfully logged you on as %2
-214702023880071232%1 was logged off successfully
-214702023780071233%1 was successfully removed from the list of shares the Server createson startup
-214702023580071235The password was changed successfully
-214702023480071236%1 file(s) copied
-214702023380071237%1 file(s) moved
-214702023280071238The message was successfully sent to all users of the network
-214702023180071239The message was successfully sent to domain %1
-21470202308007123AThe message was successfully sent to all users of this server
-21470202298007123BThe message was successfully sent to group *%1
-214702020180071257Microsoft LAN Manager Version %1
-214702020080071258Windows NT Server
-214702019980071259Windows NT Workstation
-21470201988007125AMS-DOS Enhanced Workstation
-21470201978007125BCreated at %1
-21470201968007125CServer Name Remark
-21470201958007125DCannot enumerate servers in non-default compartment
-21470201948007125E(UNC)
-21470201938007125F
-214702019280071260Domain
-214702019180071261Resources on %1
-214702019080071262Invalid network provider. Available networks are:
-214702018680071266Disk
-214702018580071267Print
-214702018480071268Comm
-214702018380071269IPC
-21470201828007126AStatus Local Remote Network
-21470201818007126BOK
-21470201808007126CDormant
-21470201798007126DPaused
-21470201788007126EDisconnected
-21470201778007126FError
-214702017680071270Connecting
-214702017580071271Reconnecting
-214702017480071272Status
-214702017380071273Local name
-214702017280071274Remote name
-214702017180071275Resource type
-214702017080071276# Opens
-214702016980071277# Connections
-214702016880071278Unavailable
-21470201668007127AShare name Resource Remark
-21470201658007127BShare name
-21470201648007127CResource
-21470201638007127DSpooled
-21470201628007127EPermission
-21470201618007127FMaximum users
-214702016080071280No limit
-214702015980071281Users
-214702015880071282The share name entered may not be accessible from some MS-DOS workstations.Are you sure you want to use this share name? %1:
-214702015780071283Caching
-214702015680071284ID Path User name # Locks
-214702015580071285File ID
-214702015480071286Locks
-214702015380071287Permissions
-214702015280071288Share name
-214702015180071289Type
-21470201508007128AUsed as
-21470201498007128BComment
-21470201468007128EComputer User name Client Type Opens Idle time
-21470201458007128FComputer
-214702014480071290Sess time
-214702014380071291Idle time
-214702014280071292Share name Type # Opens
-214702014180071293Client type
-214702014080071294Guest logon
-2147020126800712A2Manual caching of documents
-2147020125800712A3Automatic caching of documents
-2147020124800712A4Automatic caching of programs and documents
-2147020123800712A5Manual caching of documents with BranchCache enabled
-2147020122800712A6Caching disabled
-2147020121800712A7Automatic
-2147020120800712A8Manual
-2147020119800712A9Documents
-2147020118800712AAPrograms
-2147020117800712ABBranchCache
-2147020116800712ACNone
-2147020096800712C0Name
-2147020095800712C1Forwarded to
-2147020094800712C2Forwarded to you from
-2147020093800712C3Users of this server
-2147020092800712C4Net Send has been interrupted by a Ctrl+Break from the user
-2147020086800712CAName Job # Size Status
-2147020085800712CBjobs
-2147020084800712CCPrint
-2147020083800712CDName
-2147020082800712CEJob #
-2147020081800712CFSize
-2147020080800712D0Status
-2147020079800712D1Separator file
-2147020078800712D2Comment
-2147020077800712D3Priority
-2147020076800712D4Print after
-2147020075800712D5Print until
-2147020074800712D6Print processor
-2147020073800712D7Additional info
-2147020072800712D8Parameters
-2147020071800712D9Print Devices
-2147020070800712DAPrinter Active
-2147020069800712DBPrinter held
-2147020068800712DCPrinter error
-2147020067800712DDPrinter being deleted
-2147020066800712DEPrinter status unknown
-2147020056800712E8Held until %1
-2147020055800712E9Job #
-2147020054800712EASubmitting user
-2147020053800712EBNotify
-2147020052800712ECJob data type
-2147020051800712EDJob parameters
-2147020050800712EEWaiting
-2147020049800712EFHeld in queue
-2147020048800712F0Spooling
-2147020047800712F1Paused
-2147020046800712F2Offline
-2147020045800712F3Error
-2147020044800712F4Out of paper
-2147020043800712F5Intervention required
-2147020042800712F6Printing
-2147020041800712F7on
-2147020040800712F8Paused on %1
-2147020039800712F9Offline on %1
-2147020038800712FAError on%1
-2147020037800712FBOut of Paper on %1
-2147020036800712FCCheck printer on %1
-2147020035800712FDPrinting on %1
-2147020034800712FEDriver
-214701996680071342User name Type Date
-214701996580071343Lockout
-214701996480071344Service
-214701996380071345Server
-214701996280071346Server started
-214701996180071347Server paused
-214701996080071348Server continued
-214701995980071349Server stopped
-21470199588007134ASession
-21470199578007134BLogon Guest
-21470199568007134CLogon User
-21470199558007134DLogon Administrator
-21470199548007134ELogoff normal
-21470199538007134FLogon
-214701995280071350Logoff error
-214701995180071351Logoff auto-disconnect
-214701995080071352Logoff administrator-disconnect
-214701994980071353Logoff forced by logon restrictions
-214701994880071354Service
-214701994780071355%1 Installed
-214701994680071356%1 Install Pending
-214701994580071357%1 Paused
-214701994480071358%1 Pause Pending
-214701994380071359%1 Continued
-21470199428007135A%1 Continue Pending
-21470199418007135B%1 Stopped
-21470199408007135C%1 Stop Pending
-21470199398007135DAccount
-21470199388007135EUser account %1 was modified
-21470199378007135FGroup account %1 was modified
-214701993680071360User account %1 was deleted
-214701993580071361Group account %1 was deleted
-214701993480071362User account %1 was added
-214701993380071363Group account %1 was added
-214701993280071364Account system settings were modified
-214701993180071365Logon restriction
-214701993080071366Limit exceeded: UNKNOWN
-214701992980071367Limit exceeded: Logon hours
-214701992880071368Limit exceeded: Account expired
-214701992780071369Limit exceeded: Workstation ID invalid
-21470199268007136ALimit exceeded: Account disabled
-21470199258007136BLimit exceeded: Account deleted
-21470199248007136CShare
-21470199238007136DUse %1
-21470199228007136EUnuse %1
-21470199218007136FUser's session disconnected %1
-214701992080071370Administrator stopped sharing resource %1
-214701991980071371User reached limit for %1
-214701991880071372Bad password
-214701991780071373Administrator privilege required
-214701991680071374Access
-214701991580071375%1 permissions added
-214701991480071376%1 permissions modified
-214701991380071377%1 permissions deleted
-214701991280071378Access denied
-214701991180071379Unknown
-21470199108007137AOther
-21470199098007137BDuration:
-21470199088007137CDuration: Not available
-21470199078007137DDuration: Less than one second
-21470199068007137E(none)
-21470199058007137FClosed %1
-214701990480071380Closed %1 (disconnected)
-214701990380071381Administrator closed %1
-214701990280071382Access ended
-214701990180071383Log on to network
-214701990080071384Logon denied
-214701989980071385Program Message Time
-214701989880071386Account locked due to %1 bad passwords
-214701989780071387Account unlocked by administrator
-214701989680071388Log off network
-214701989580071389The operation cannot be completed because other resources are dependent on this resource
-21470198948007138AThe cluster resource dependency cannot be found
-21470198938007138BThe cluster resource cannot be made dependent on the specified resource because it is already dependent
-21470198928007138CThe cluster resource is not online
-21470198918007138DA cluster node is not available for this operation
-21470198908007138EThe cluster resource is not available
-21470198898007138FThe cluster resource could not be found
-214701988880071390The cluster is being shut down
-214701988780071391A cluster node cannot be evicted from the cluster unless the node is down or it is the last node
-214701988680071392The object already exists
-214701988580071393The object is already in the list
-214701988480071394The cluster group is not available for any new requests
-214701988380071395The cluster group could not be found
-214701988280071396The operation could not be completed because the cluster group is not online
-214701988180071397The operation failed because either the specified cluster node is not the owner of the resource
-214701988080071398The operation failed because either the specified cluster node is not the owner of the group
-214701987980071399The cluster resource could not be created in the specified resource monitor
-21470198788007139AThe cluster resource could not be brought online by the resource monitor
-21470198778007139BThe operation could not be completed because the cluster resource is online
-21470198768007139CThe cluster resource could not be deleted or brought offline because it is the quorum resource
-21470198758007139DThe cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource
-21470198748007139EThe cluster software is shutting down
-21470198738007139FThe group or resource is not in the correct state to perform the requested operation
-2147019872800713A0The properties were stored but not all changes will take effect until the next time the resource is brought online
-2147019871800713A1The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class
-2147019870800713A2The cluster resource could not be deleted since it is a core resource
-2147019869800713A3The quorum resource failed to come online
-2147019868800713A4The quorum log could not be created or mounted successfully
-2147019867800713A5The cluster log is corrupt
-2147019866800713A6The record could not be written to the cluster log since it exceeds the maximum size
-2147019865800713A7The cluster log exceeds its maximum size
-2147019864800713A8No checkpoint record was found in the cluster log
-2147019863800713A9The minimum required disk space needed for logging is not available
-2147019862800713AAThe cluster node failed to take control of the quorum resource because the resource is owned by another active node
-2147019861800713ABA cluster network is not available for this operation
-2147019860800713ACA cluster node is not available for this operation
-2147019859800713ADAll cluster nodes must be running to perform this operation
-2147019858800713AEA cluster resource failed
-2147019857800713AFThe cluster node is not valid
-2147019856800713B0The cluster node already exists
-2147019855800713B1A node is in the process of joining the cluster
-2147019854800713B2The cluster node was not found
-2147019853800713B3The cluster local node information was not found
-2147019852800713B4The cluster network already exists
-2147019851800713B5The cluster network was not found
-2147019850800713B6The cluster network interface already exists
-2147019849800713B7The cluster network interface was not found
-2147019848800713B8The cluster request is not valid for this object
-2147019847800713B9The cluster network provider is not valid
-2147019846800713BAThe cluster node is down
-2147019845800713BBThe cluster node is not reachable
-2147019844800713BCThe cluster node is not a member of the cluster
-2147019843800713BDA cluster join operation is not in progress
-2147019842800713BEThe cluster network is not valid
-2147019841800713BFMar
-2147019840800713C0The cluster node is up
-2147019839800713C1The cluster IP address is already in use
-2147019838800713C2The cluster node is not paused
-2147019837800713C3No cluster security context is available
-2147019836800713C4The cluster network is not configured for internal cluster communication
-2147019835800713C5The cluster node is already up
-2147019834800713C6The cluster node is already down
-2147019833800713C7The cluster network is already online
-2147019832800713C8The cluster network is already offline
-2147019831800713C9The cluster node is already a member of the cluster
-2147019830800713CAThe cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network
-2147019829800713CBOne or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network
-2147019828800713CCThis operation cannot currently be performed on the cluster group containing the quorum resource
-2147019827800713CDThe cluster quorum resource is not allowed to have any dependencies
-2147019826800713CEThe cluster node is paused
-2147019825800713CFThe cluster resource cannot be brought online. The owner node cannot run this resource
-2147019824800713D0The cluster node is not ready to perform the requested operation
-2147019823800713D1The cluster node is shutting down
-2147019822800713D2The cluster join operation was aborted
-2147019821800713D3The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster
-2147019820800713D4This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor
-2147019819800713D5The system configuration changed during the cluster join or form operation. The join or form operation was aborted
-2147019818800713D6The specified resource type was not found
-2147019817800713D7The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node
-2147019816800713D8The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL
-2147019815800713D9No authentication package could be registered with the RPC server
-2147019814800713DAYou cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group
-2147019813800713DBThe join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join
-2147019812800713DCThe resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state
-2147019811800713DDA non locker code got a request to reserve the lock for making global updates
-2147019810800713DEThe quorum disk could not be located by the cluster service
-2147019809800713DFThe backed up cluster database is possibly corrupt
-2147019808800713E0A DFS root already exists in this cluster node
-2147019807800713E1An attempt to modify a resource property failed because it conflicts with another existing property
-2147019806800713E2This operation is not supported on a cluster without an Administrator Access Point
-2147019805800713E3Denmark
-2147019804800713E4Sweden
-2147019803800713E5Norway
-2147019802800713E6Germany
-2147019801800713E7Australia
-2147019800800713E8Japan
-2147019799800713E9Korea
-2147019798800713EAChina (PRC)
-2147019797800713EBTaiwan
-2147019796800713ECAsia
-2147019795800713EDPortugal
-2147019794800713EEFinland
-2147019793800713EFArabic
-2147019792800713F0Hebrew
-21470197468007141EA power failure has occurred at %1. Please terminate all activity with this server
-21470197458007141FPower has been restored at %1. Normal operations have resumed
-214701974480071420The UPS service is starting shut down at %1
-214701974380071421The UPS service is about to perform final shut down
-214701972680071432The Workstation must be started with the NET START command
-214701972180071437Remote IPC
-214701972080071438Remote Admin
-214701971980071439Default share
-21470197188007143AUser Profiles
-2147019616800714A0The password entered is longer than 14 characters. Computerswith Windows prior to Windows 2000 will not be able to usethis account. Do you want to continue this operation? %1:
-2147019615800714A1%1 has a remembered connection to %2. Do youwant to overwrite the remembered connection? %3:
-2147019614800714A2Do you want to resume loading the profile? The command whichcaused the error will be ignored. %1:
-2147019612800714A4Do you want to continue this operation? %1:
-2147019611800714A5Do you want to add this? %1:
-2147019610800714A6Do you want to continue this operation? %1:
-2147019609800714A7Is it OK to start it? %1:
-2147019608800714A8Do you want to start the Workstation service? %1:
-2147019607800714A9Is it OK to continue disconnecting and force them closed? %1:
-2147019606800714AAThe printer does not exist. Do you want to create it? %1:
-2147019605800714ABNever
-2147019604800714ACNever
-2147019603800714ADNever
-2147019601800714AFNET.HLP
-2147019600800714B0NET.HLP
-2147019599800714B1Deny
-2147019596800714B4The network control block (NCB) request completed successfully.The NCB is the data
-2147019595800714B5Illegal network control block (NCB) buffer length on SEND DATAGRAM
-2147019594800714B6The data descriptor array specified in the network control block (NCB) isinvalid. The NCB is the data
-2147019593800714B7The command specified in the network control block (NCB) is illegal.The NCB is the data
-2147019592800714B8The message correlator specified in the network control block (NCB) isinvalid. The NCB is the data
-2147019591800714B9A network control block (NCB) command timed-out. The session may haveterminated abnormally. The NCB is the data
-2147019590800714BAAn incomplete network control block (NCB) message was received.The NCB is the data
-2147019589800714BBThe buffer address specified in the network control block (NCB) is illegal.The NCB is the data
-2147019588800714BCThe session number specified in the network control block (NCB) is not active.The NCB is the data
-2147019587800714BDNo resource was available in the network adapter.The network control block (NCB) request was refused. The NCB is the data
-2147019586800714BEThe session specified in the network control block (NCB) was closed.The NCB is the data
-2147019585800714BFThe network control block (NCB) command was canceled.The NCB is the data
-2147019584800714C0The message segment specified in the network control block (NCB) isillogical. The NCB is the data
-2147019583800714C1The name already exists in the local adapter name table.The network control block (NCB) request was refused. The NCB is the data
-2147019582800714C2The network adapter name table is full.The network control block (NCB) request was refused. The NCB is the data
-2147019581800714C3The network name has active sessions and is now de-registered.The network control block (NCB) command completed. The NCB is the data
-2147019580800714C4A previously issued Receive Lookahead command is activefor this session. The network control block (NCB) command was rejected.The NCB is the data
-2147019579800714C5The local session table is full. The network control block (NCB) request was refused.The NCB is the data
-2147019578800714C6A network control block (NCB) session open was rejected. No LISTEN is outstandingon the remote computer. The NCB is the data
-2147019577800714C7The name number specified in the network control block (NCB) is illegal.The NCB is the data
-2147019576800714C8The call name specified in the network control block (NCB) cannot be found ordid not answer. The NCB is the data
-2147019575800714C9The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data
-2147019574800714CAThe name specified in the network control block (NCB) is in use on a remote adapter.The NCB is the data
-2147019573800714CBThe name specified in the network control block (NCB) has been deleted.The NCB is the data
-2147019572800714CCThe session specified in the network control block (NCB) ended abnormally.The NCB is the data
-2147019571800714CDThe network protocol has detected two or more identicalnames on the network. The network control block (NCB) is the data
-2147019570800714CEAn unexpected protocol packet was received. There may be anincompatible remote device. The network control block (NCB) is the data
-2147019563800714D5The NetBIOS interface is busy.The network control block (NCB) request was refused. The NCB is the data
-2147019562800714D6There are too many network control block (NCB) commands outstanding.The NCB request was refused. The NCB is the data
-2147019561800714D7The adapter number specified in the network control block (NCB) is illegal.The NCB is the data
-2147019560800714D8The network control block (NCB) command completed while a cancel was occurring.The NCB is the data
-2147019559800714D9The name specified in the network control block (NCB) is reserved.The NCB is the data
-2147019558800714DAThe network control block (NCB) command is not valid to cancel.The NCB is the data
-2147019545800714E7There are multiple network control block (NCB) requests for the same session.The NCB request was refused. The NCB is the data
-2147019544800714E8There has been a network adapter error. The only NetBIOScommand that may be issued is an NCB RESET. The network control block (NCB) isthe data
-2147019542800714EAThe maximum number of applications was exceeded.The network control block (NCB) request was refused. The NCB is the data
-2147019540800714ECThe requested resources are not available.The network control block (NCB) request was refused. The NCB is the data
-2147019532800714F4A system error has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019531800714F5A ROM checksum failure has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019530800714F6A RAM test failure has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019529800714F7A digital loopback failure has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019528800714F8An analog loopback failure has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019527800714F9An interface failure has occurred.The network control block (NCB) request was refused. The NCB is the data
-2147019526800714FAAn unrecognized network control block (NCB) return code was received.The NCB is the data
-214701951680071504A network adapter malfunction has occurred.The network control block (NCB) request was refused. The NCB is the data
-214701951580071505The network control block (NCB) command is still pending.The NCB is the data
-21470193968007157CThe update log on %1 is over 80%% capacity. The primarydomain controller %2 is not retrieving the updates
-21470193958007157DThe update log on %1 is full
-21470193948007157EThe time difference with the primary domain controller %1exceeds the maximum allowed skew of %2 seconds
-21470193938007157FThe account of user %1 has been locked out on %2due to %3 bad password attempts
-214701939280071580The %1 log file cannot be opened
-214701939180071581The %1 log file is corrupted and will be cleared
-214701939080071582The Application log file could not be opened. %1 will be used as thedefault log file
-214701938980071583The %1 Log is full. If this is the first time you have seen thismessage
-214701938880071584The security database full synchronization has been initiated by the server %1
-214701938780071585Windows could not be started as configured.A previous working configuration was used instead
-214701938680071586The exception 0x%1 occurred in the application %2 at location 0x%3
-214701938580071587The servers %1 and %3 both claim to be an NT Domain Controller forthe %2 domain. One of the servers should be removed from thedomain because the servers have different security identifiers(SID)
-214701938480071588The server %1 and %2 both claim to be the primary domaincontroller for the %3 domain. One of the servers should bedemoted or removed from the domain
-214701938380071589The computer %1 tried to connect to the server %2 usingthe trust relationship established by the %3 domain. However
-21470193828007158AThe computer has rebooted from a bugcheck. The bugcheck was:%1.%2A full dump was not saved
-21470193818007158BThe computer has rebooted from a bugcheck. The bugcheck was:%1.%2A dump was saved in: %3
-21470193808007158CThe computer or domain %1 trusts domain %2. (This may be an indirecttrust.) However
-21470193798007158DThe computer or domain %1 trusts domain %2. (This may be an indirecttrust.) However
-2147019296800715E0Could not share the User or Script path
-2147019295800715E1The password for this computer is not found in the local securitydatabase
-2147019294800715E2An internal error occurred while accessing the computer'slocal or network security database
-214701919680071644The Netlogon service could not initialize the replication datastructures successfully. The service was terminated. The followingerror occurred: %1
-214701919580071645The Netlogon service failed to update the domain trust list. Thefollowing error occurred: %1
-214701919480071646The Netlogon service could not add the RPC interface. Theservice was terminated. The following error occurred: %1
-214701919380071647The Netlogon service could not read a mailslot message from %1 dueto the following error: %2
-214701919280071648The Netlogon service failed to register the service with theservice controller. The service was terminated. The followingerror occurred: %1
-214701919180071649The change log cache maintained by the Netlogon service for %1database changes is inconsistent. The Netlogon service is resettingthe change log
-21470191908007164AThe Netlogon service could not create server share %1. The followingerror occurred: %2
-21470191898007164BThe down-level logon request for the user %1 from %2 failed
-21470191888007164CThe down-level logoff request for the user %1 from %2 failed
-21470191878007164DThe Windows NT or Windows 2000 %1 logon request for the user %2\%3 from %4 (via %5)failed
-21470191868007164EThe Windows NT or Windows 2000 %1 logoff request for the user %2\%3 from %4failed
-21470191858007164FThe partial synchronization request from the server %1 completedsuccessfully. %2 changes(s) has(have) been returned to thecaller
-214701918480071650The partial synchronization request from the server %1 failed withthe following error: %2
-214701918380071651The full synchronization request from the server %1 completedsuccessfully. %2 object(s) has(have) been returned tothe caller
-214701918280071652The full synchronization request from the server %1 failed withthe following error: %2
-214701918180071653The partial synchronization replication of the %1 database from theprimary domain controller %2 completed successfully. %3 change(s) is(are)applied to the database
-214701918080071654The partial synchronization replication of the %1 database from theprimary domain controller %2 failed with the following error: %3
-214701917980071655The full synchronization replication of the %1 database from theprimary domain controller %2 completed successfully
-214701917880071656The full synchronization replication of the %1 database from theprimary domain controller %2 failed with the following error: %3
-214701917780071657This computer was not able to set up a secure session with a domaincontroller in domain %1 due to the following: %2This may lead to authentication problems. Make sure that thiscomputer is connected to the network. If the problem persists
-214701917680071658The session setup to the Windows Domain Controller %1 for the domain %2failed because the computer %3 does not have a local security database account
-214701917580071659The session setup to the Windows Domain Controller %1 for the domain %2failed because the Domain Controller did not have an account %4needed to set up the session by this computer %3.ADDITIONAL DATAIf this computer is a member of or a Domain Controller in the specified domain
-21470191748007165AThe session setup from the computer %1 failed to authenticate.The name(s) of the account(s) referenced in the security database is%2. The following error occurred: %3
-21470191738007165BThe session setup from computer '%1' failed because the security databasedoes not contain a trust account '%2' referenced by the specified computer.USER ACTIONIf this is the first occurrence of this event for the specified computerand account
-21470191728007165CCould not register control handler with service controller %1
-21470191718007165DCould not set service status with service controller %1
-21470191708007165ECould not find the computer name %1
-21470191698007165FCould not load %1 device driver
-214701916880071660Could not load any transport
-214701916780071661Replication of the %1 Domain Object "%2" from primary domain controller%3 failed with the following error: %4
-214701916680071662Replication of the %1 Global Group "%2" from primary domain controller%3 failed with the following error: %4
-214701916580071663Replication of the %1 Local Group "%2" from primary domain controller%3 failed with the following error: %4
-214701916480071664Replication of the %1 User "%2" from primary domain controller%3 failed with the following error: %4
-214701916380071665Replication of the %1 Policy Object "%2" from primary domain controller%3 failed with the following error: %4
-214701916280071666Replication of the %1 Trusted Domain Object "%2" from primary domain controller%3 failed with the following error: %4
-214701916180071667Replication of the %1 Account Object "%2" from primary domain controller%3 failed with the following error: %4
-214701916080071668Replication of the %1 Secret "%2" from primary domain controller%3 failed with the following error: %4
-214701915980071669The system returned the following unexpected error code: %1
-21470191588007166ANetlogon has detected two machine accounts for server "%1".The server can be either a Windows 2000 Server that is a member of thedomain or the server can be a LAN Manager server with an account in theSERVERS global group. It cannot be both
-21470191578007166BThis domain has more global groups than can be replicated to a LanManBDC. Either delete some of your global groups or remove the LanManBDCs from the domain
-21470191568007166CThe Browser driver returned the following error to Netlogon: %1
-21470191558007166DNetlogon could not register the %1<1B> name for the following reason: %2
-21470191548007166EService failed to retrieve messages needed to boot remote boot clients
-21470191538007166FService experienced a severe error and can no longer provide remote bootfor 3Com 3Start remote boot clients
-214701915280071670Service experienced a severe system error and will shut itself down
-214701915180071671Client with computer name %1 failed to acknowledge receipt of theboot data. Remote boot of this client was not completed
-214701915080071672Client with computer name %1 was not booted due to an error in openingfile %2
-214701914980071673Client with computer name %1 was not booted due to an error in readingfile %2
-214701914880071674Client with computer name %1 was not booted due to insufficient memoryat the remote boot server
-214701914780071675Client with computer name %1 will be booted without using checksumsbecause checksum for file %2 could not be calculated
-214701914680071676Client with computer name %1 was not booted due to too many lines infile %2
-214701914580071677Client with computer name %1 was not booted because the boot blockconfiguration file %2 for this client does not contain boot blockline and/or loader line
-214701914480071678Client with computer name %1 was not booted due to a bad size offile %2
-214701914380071679Client with computer name %1 was not booted due to remote bootservice internal error
-21470191428007167AClient with computer name %1 was not booted because file %2 has aninvalid boot header
-21470191418007167BClient with computer name %1 was not booted due to network error
-21470191408007167CClient with adapter id %1 was not booted due to lack of resources
-21470191398007167DService experienced error copying file or directory %1
-21470191388007167EService experienced error deleting file or directory %1
-21470191378007167FService experienced error setting permissions on file or directory %1
-214701913680071680Service experienced error evaluating RPL configurations
-214701913580071681Service experienced error creating RPL profiles for all configurations
-214701913480071682Service experienced error accessing registry
-214701913380071683Service experienced error replacing possibly outdated RPLDISK.SYS
-214701913280071684Service experienced error adding security accounts or settingfile permissions. These accounts are the RPLUSER local groupand the user accounts for the individual RPL workstations
-214701913180071685Service failed to back up its database
-214701913080071686Service failed to initialize from its database. The database may bemissing or corrupted. Service will attempt restoring the databasefrom the backup
-214701912980071687Service failed to restore its database from the backup. Servicewill not start
-214701912880071688Service successfully restored its database from the backup
-214701912780071689Service failed to initialize from its restored database. Servicewill not start
-21470191268007168AThe session setup to the Windows Domain Controller %1 from computer%2 using account %4 failed. %2 is declared to be a BDC in domain %3.However
-21470191258007168BThe Remoteboot database was in NT 3.5 / NT 3.51 format and NT isattempting to convert it to NT 4.0 format. The JETCONV converterwill write to the Application event log when it is finished
-21470191248007168CGlobal group SERVERS exists in domain %1 and has members.This group defines Lan Manager BDCs in the domain.Lan Manager BDCs are not permitted in NT domains
-21470191238007168DThe following DNS server that is authoritative for the DNS domain controllerlocator records of this domain controller does not support dynamic DNS updates:DNS server IP address: %1Returned Response Code (RCODE): %2Returned Status Code: %3USER ACTIONConfigure the DNS server to allow dynamic DNS updates or manually add the DNSrecords from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database
-21470191228007168EThe dynamic registration of the DNS record '%1' failed on the following DNS server:DNS server IP address: %3Returned Response Code (RCODE): %4Returned Status Code: %5For computers and users to locate this domain controller
-21470191218007168FThe dynamic deletion of the DNS record '%1' failed on the following DNS server:DNS server IP address: %3Returned Response Code (RCODE): %4Returned Status Code: %5USER ACTIONTo prevent remote computers from connecting unnecessarily to the domain controller
-214701912080071690Failed to create/open file %1 with the following error: %2
-214701911980071691Netlogon got the following error while trying to get the subnet to sitemapping information from the DS: %1
-214701911880071692'%1' tried to determine its site by looking up its IP address ('%2')in the Configuration\Sites\Subnets container in the DS. No subnet matchedthe IP address. Consider adding a subnet object for this IP address
-214701911780071693The site name for this computer is '%1'. That site name is not a validsite name. A site name must be a valid DNS label.Rename the site to be a valid name
-214701911680071694The subnet object '%1' appears in the Configuration\Sites\Subnetscontainer in the DS. The name is not syntactically valid. The validsyntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet numberand yy is the number of bits in the subnet mask.Correct the name of the subnet object
-214701911580071695Dynamic registration or deletion of one or more DNS records associated with DNSdomain '%1' failed. These records are used by other computers to locate thisserver as a domain controller (if the specified domain is an Active Directorydomain) or as an LDAP server (if the specified domain is an application partition).Possible causes of failure include: - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers - Specified preferred and alternate DNS servers are not running - DNS server(s) primary for the records to be registered is not running - Preferred or alternate DNS servers are configured with wrong root hints - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registrationUSER ACTIONFix possible misconfiguration(s) specified above and initiate registration or deletion ofthe DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domaincontroller or by restarting Net Logon service on the domain controller
-214701911480071696Dynamic registration or deregistration of one or more DNS records failed with the following error: %1
-214701911380071697The session setup to the Windows Domain Controller %1 for the domain %2is not responsive. The current RPC call from Netlogon on \\%3 to %1 has been cancelled
-214701911280071698Site '%2' does not have any Domain Controllers for domain '%3'.Domain Controllers in site '%1' have been automaticallyselected to cover site '%2' for domain '%3' based on configuredDirectory Server replication costs
-214701911180071699This Domain Controller no longer automatically covers site '%1' for domain '%2'
-21470191108007169ASite '%2' does not have any Global Catalog servers for forest '%3'.Global Catalog servers in site '%1' have been automaticallyselected to cover site '%2' for forest '%3' based on configuredDirectory Server replication costs
-21470191098007169BThis Global Catalog server no longer automatically covers site '%1' for forest '%2'
-21470191088007169CAttempt to update HOST Service Principal Names (SPNs) of the computerobject in Active Directory failed. The updated values were '%1' and '%2'.The following error occurred: %3
-21470191078007169DAttempt to update DNS Host Name of the computer objectin Active Directory failed. The updated value was '%1'.The following error occurred: %2
-21470191068007169ENo suitable Domain Controller is available for domain %1.An NT4 or older domain controller is available but it cannotbe used for authentication purposes in the Windows 2000 or newerdomain that this computer is a member of.The following error occurred:%2
-21470191058007169FThe domain of this computer
-2147019104800716A0Site '%2' does not have any LDAP servers for non-domain NC '%3'.LDAP servers in site '%1' have been automatically selected tocover site '%2' for non-domain NC '%3' based on configuredDirectory Server replication costs
-2147019103800716A1This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'
-2147019102800716A2Site '%2' is no longer manually configured in the registry ascovered by this Domain Controller for domain '%3'. As a result
-2147019101800716A3This Domain Controller no longer automatically covers site '%1' for domain '%2'.However
-2147019100800716A4Site '%2' is no longer manually configured in the registry ascovered by this Global Catalog server for forest '%3'. As a result
-2147019099800716A5This Global Catalog server no longer automatically covers site '%1' for forest '%2'.However
-2147019098800716A6Site '%2' is no longer manually configured in the registry ascovered by this LDAP server for non-domain NC '%3'. As a result
-2147019097800716A7This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'.However
-2147019096800716A8Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributesof the computer object in Active Directory failed because the Domain Controller'%1' had more than one account with the name '%2' corresponding to this computer.Not having SPNs registered may result in authentication failures for this computer.Contact your domain administrator who may need to manually resolve the account namecollision
-2147019095800716A9Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributesof the computer object in Active Directory failed because this computer accountname
-2147019094800716AANone of the IP addresses (%2) of this Domain Controller map to the configured site '%1'.While this may be a temporary situation due to IP address changes
-2147019093800716ABThe following error occurred while reading a parameter '%2' in theNetlogon %1 registry section:%3
-2147019092800716ACThe Netlogon %1 registry key contains an invalid value 0x%2 for parameter '%3'.The minimum and maximum values allowed for this parameter are 0x%4 and 0x%5
-2147019091800716ADThe session setup from the computer %1 failed to authenticate.The following error occurred: %2
-2147019090800716AEDynamic DNS updates have been manually disabled on this domain controller.USER ACTIONReconfigure this domain controller to use dynamic DNS updates or manually add the DNSrecords from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database
-2147019089800716AFDuring the past %1 hours there have been %2 connections to this DomainController from client machines whose IP addresses don't map to any ofthe existing sites in the enterprise. Those clients
-2147019088800716B0The deregistration of some DNS domain controller locator records was abortedat the time of this domain controller demotion because the DNS deregistrationstook too long.USER ACTIONManually delete the DNS records listed in the file'%SystemRoot%\System32\Config\Netlogon.dns' from the DNS database
-2147019087800716B1The NetLogon service on this domain controller has been configured to use port %1for incoming RPC connections over TCP/IP from remote machines. However
-2147019086800716B2During the past %1 hours
-2147019085800716B3The dynamic registration of the DNS record '%1' for the remote domain controller '%3'failed on the following DNS server:DNS server IP address: %4Returned Response Code (RCODE): %5Returned Status Code: %6For computers and users to locate the domain controller '%3'
-2147019084800716B4The dynamic deregistration of the DNS record '%1' for the remote domain controller'%3' failed on the following DNS server:DNS server IP address: %4Returned Response Code (RCODE): %5Returned Status Code: %6USER ACTIONTo prevent remote computers from attempting to connect to the domain controller '%3'using an invalid record
-2147019083800716B5The dynamic registration request for the DNS record '%1' has been rejected by theremote domain controller '%2'. Error: '%3'For computers and users to locate this domain controller
-2147019082800716B6The dynamic deregistration request of the DNS record '%1' has been rejected by theremote domain controller '%2'. Error: '%3'To prevent remote computers from connecting unnecessarily to this domain controller
-2147019081800716B7The remoting of the dynamic update request for the local domain controller's DNS recordsthrough a secure session has failed with error '%1'.For other computers and member servers to locate this domain controller
-2147019080800716B8Netlogon has failed an authentication request of account %1 in domain %2. The request timed out before it could be sent to domain controller %3 in domain %4. This is the first failure. If the problem continues
-2147019079800716B9Netlogon has failed an additional %1 authentication requests in the last %2 minutes.The requests timed out before they could be sent to domain controller %3 in domain %4.Please see http://support.microsoft.com/kb/2654097 for more information
-2147019078800716BANetlogon took more than %1 seconds for an authentication request of account %2 in domain %3
-2147019077800716BBNetlogon took more than %1 seconds for %2 authentication requests through domain controller %3 in domain %4 in the last %5 minutes.Please see http://support.microsoft.com/kb/2654097 for more information
-2147019076800716BCThe Netlogon service could not add the AuthZ RPC interface. Theservice was terminated. The following error occurred: '%1'
-2147019075800716BDThe Netlogon service failed to initialize the AuthZ resource manager.The service was terminated. The following error occurred: '%1'
-2147019074800716BEThe Netlogon service failed to initialize the security descriptor for the Netlogon RPC interface. The service was terminated. The following error occurred: '%1'
-2147019073800716BFThe system successfully changed its password on the domain controller %1.This event is logged when the password for the computer account ischanged by the system. It is logged on the computer that changed thepassword
-2147019072800716C0The system successfully changed the password for managed service account %1 on the domain controller %2.This event is logged when the password for a standalone managed serviceaccount is changed by the system. It is logged on the computer thatchanged the password
-2147019070800716C2The Netlogon service detected a non-windows account using secure RPC. Machine SamAccountName: %1 Domain: %2 Account Type: %3 Machine Os: %4 Machine Os Build Version: %5 Machine Os Service Pack: %6
-2147019069800716C3The Netlogon service denied a vulnerable Netlogon secure channel connection from a machine account. Machine SamAccountName: %1 Domain: %2 Account Type: %3 Machine Operating System: %4 Machine Operating System Build: %5 Machine Operating System Service Pack: %6For more information about why this was denied
-2147019068800716C4The Netlogon service denied a vulnerable Netlogon secure channel connection using a trust account. Account Type: %1 Trust Name: %2 Trust Target: %3 Client IP Address: %4For more information about why this was denied
-2147019067800716C5The Netlogon service allowed a vulnerable Netlogon secure channel connection.Warning: This connection will be denied once the enforcement phase is released. To better understand the enforcement phase
-2147019066800716C6The Netlogon service allowed a vulnerable Netlogon secure channel connection because the machine account is allowed in the "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy.Warning: Using vulnerable Netlogon secure channels will expose the domain-joined devices to attack. To protect your device from attack
-2147019065800716C7The Netlogon service allowed a vulnerable Netlogon secure channel connection because the trust account is allowed in the "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy.Warning: Using vulnerable Netlogon secure channels will expose Active Directory forests to attack. To protect your Active Directory forests from attack
-2147019064800716C8The Netlogon service allowed one or more unsecure pass-through NTLM authentication requests from trusted domains and/or forestsduring the most recent event throttling window. These unsecure requests would normally be blocked but were allowed to proceeddue to the current trust configuration.Warning: Allowing unsecure pass-through authentication requests will expose your Active Directory forest to attack.For more information about this issue please visit https://go.microsoft.com/fwlink/?linkid=276811&.Count of unsecure requests allowed due to administrative override: %1
-2147019063800716C9The Netlogon service blocked one or more unsecure pass-through NTLM authentication requests from trusted clients
-2147019062800716CAThe Netlogon service allowed an unsecure pass-through NTLM authentication request from a trusted client
-2147019061800716CBThe Netlogon service blocked an unsecure pass-through NTLM authentication requests from a trusted client
-214701900680071702An operation was attempted that is incompatible with the current membership state of the node
-214701900580071703The quorum resource does not contain the quorum log
-214701900480071704The membership engine requested shutdown of the cluster service on this node
-214701900380071705The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node
-214701900280071706A matching cluster network for the specified IP address could not be found
-214701900180071707The actual data type of the property did not match the expected data type of the property
-214701900080071708The cluster node was evicted from the cluster successfully
-214701899980071709Two or more parameter values specified for a resource's properties are in conflict
-21470189988007170AThis computer cannot be made a member of a cluster
-21470189978007170BThis computer cannot be made a member of a cluster because it does not have the correct version of Windows installed
-21470189968007170CA cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster
-21470189958007170DThe cluster configuration action has already been committed
-21470189948007170EThe cluster configuration action could not be rolled back
-21470189938007170FThe drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node
-214701899280071710One or more nodes in the cluster are running a version of Windows that does not support this operation
-214701899180071711The name of the corresponding computer account doesn't match the Network Name for this resource
-214701899080071712No network adapters are available
-214701898980071713The cluster node has been poisoned
-214701898880071714The group is unable to accept the request since it is moving to another node
-214701898780071715The resource type cannot accept the request since is too busy performing another operation
-214701898680071716The call to the cluster resource DLL timed out
-214701898580071717The address is not valid for an IPv6 Address resource. A global IPv6 address is required
-214701898480071718An internal cluster error occurred. A call to an invalid function was attempted
-214701898380071719A parameter value is out of acceptable range
-21470189828007171AA network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required
-21470189818007171BAn invalid cluster registry operation was attempted
-21470189808007171CAn input string of characters is not properly terminated
-21470189798007171DAn input string of characters is not in a valid format for the data it represents
-21470189788007171EAn internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress
-21470189778007171FAn internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress
-214701897680071720An internal cluster error occurred. Data was not properly initialized
-214701897580071721An error occurred while reading from a stream of data. An unexpected number of bytes was returned
-214701897480071722An error occurred while writing to a stream of data. The required number of bytes could not be written
-214701897380071723An error occurred while deserializing a stream of cluster data
-214701897280071724One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s)
-214701897180071725A quorum of cluster nodes was not present to form a cluster
-214701897080071726The cluster network is not valid for an IPv6 Address resource
-214701896980071727The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends
-214701896880071728Quorum resource cannot reside in the Available Storage group
-214701896780071729The dependencies for this resource are nested too deeply
-21470189668007172AThe call into the resource DLL raised an unhandled exception
-21470189658007172BThe RHS process failed to initialize
-21470189648007172CThe Failover Clustering feature is not installed on this node
-21470189638007172DThe resources must be online on the same node for this operation
-21470189628007172EA new node can not be added since this cluster is already at its maximum number of nodes
-21470189618007172FThis cluster can not be created since the specified number of nodes exceeds the maximum allowed limit
-214701896080071730An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain
-214701895980071731This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed
-214701895880071732File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes
-214701895780071733Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown.If it is the last node in the cluster
-214701895680071734Only one instance of this resource type is allowed in the cluster
-214701895580071735Only one instance of this resource type is allowed per resource group
-214701895480071736The resource failed to come online due to the failure of one or more provider resources
-214701895380071737The resource has indicated that it cannot come online on any node
-214701895280071738The current operation cannot be performed on this group at this time
-214701895180071739The directory or file is not located on a cluster shared volume
-21470189508007173AThe Security Descriptor does not meet the requirements for a cluster
-21470189498007173BThere is one or more shared volumes resources configured in the cluster.Those resources must be moved to available storage in order for operation to succeed
-21470189488007173CThis group or resource cannot be directly manipulated.Use shared volume APIs to perform desired operation
-21470189478007173DBack up is in progress. Please wait for backup completion before trying this operation again
-21470189468007173EThe path does not belong to a cluster shared volume
-21470189458007173FThe cluster shared volume is not locally mounted on this node
-214701894480071740The cluster watchdog is terminating
-214701894380071741A resource vetoed a move between two nodes because they are incompatible
-214701894280071742The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode
-214701894180071743The resource vetoed the call
-214701894080071744Resource could not start or run because it could not reserve sufficient system resources
-214701893980071745A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation
-214701893880071746A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation
-214701893780071747The requested operation can not be completed because the group is queued for an operation
-214701893680071748The requested operation can not be completed because a resource has locked status
-214701893580071749The resource cannot move to another node because a cluster shared volume vetoed the operation
-21470189348007174AA node drain is already in progress
-21470189338007174BClustered storage is not connected to the node
-21470189328007174CThe disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS
-21470189318007174DThe resource must be part of the Available Storage group to complete this action
-21470189308007174ECSVFS failed operation as volume is in redirected mode
-21470189298007174FCSVFS failed operation as volume is not in redirected mode
-214701892880071750Cluster properties cannot be returned at this time
-214701892780071751The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes
-214701892680071752The operation cannot be completed because the resource is in maintenance mode
-214701892580071753The operation cannot be completed because of cluster affinity conflicts
-214701892480071754The operation cannot be completed because the resource is a replica virtual machine
-214701892380071755The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version
-214701892280071756Updating the cluster functional level failed because the cluster is running in fix quorum mode.Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automaticallyswitch out of fix quorum mode
-214701892180071757The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster byusing the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features willbe available
-214701892080071758The cluster is currently performing a version upgrade
-214701891980071759The cluster did not successfully complete the version upgrade
-21470189188007175AThe cluster node is in grace period
-21470189178007175BThe operation has failed because CSV volume was not able to recover in time specified on this file object
-21470189168007175CThe operation failed because the requested node is not currently part of active cluster membership
-21470189158007175DThe operation failed because the requested cluster resource is currently unmonitored
-21470189148007175EThe operation failed because a resource does not support running in an unmonitored state
-21470189138007175FThe operation cannot be completed because a resource participates in replication
-214701891280071760The operation failed because the requested cluster node has been isolated
-214701891180071761The operation failed because the requested cluster node has been quarantined
-214701891080071762The operation failed because the specified database update condition was not met
-214701890980071763A clustered space is in a degraded condition and the requested action cannot be completed at this time
-214701890880071764The operation failed because token delegation for this control is not supported
-214701890780071765The operation has failed because CSV has invalidated this file object
-214701890680071766This operation is supported only on the CSV coordinator node
-214701890580071767The cluster group set is not available for any further requests
-214701890480071768The cluster group set could not be found
-214701890380071769The action cannot be completed at this time because the cluster group set would fall below quorum and not be able to act as a provider
-21470189028007176AThe specified parent fault domain is not found
-21470189018007176BThe fault domain cannot be a child of the parent specified
-21470189008007176CStorage Spaces Direct has rejected the proposed fault domain changes because it impacts the fault tolerance of the storage
-21470188998007176DStorage Spaces Direct has rejected the proposed fault domain changes because it reduces the storage connected to the system
-21470188988007176ECluster infrastructure file server creation failed because a valid non-empty file server name was not provided
-21470188978007176FThe action cannot be completed because the cluster set management cluster is unreachable
-214701889680071770The specified file could not be encrypted
-214701889580071771The specified file could not be decrypted
-214701889480071772The specified file is encrypted and the user does not have the ability to decrypt it
-214701889380071773There is no valid encryption recovery policy configured for this system
-214701889280071774The required encryption driver is not loaded for this system
-214701889180071775The file was encrypted with a different encryption driver than is currently loaded
-214701889080071776There are no EFS keys defined for the user
-214701888980071777The specified file is not encrypted
-214701888880071778The specified file is not in the defined EFS export format
-214701888780071779The specified file is read only
-21470188868007177AThe directory has been disabled for encryption
-21470188858007177BThe server is not trusted for remote encryption operation
-21470188848007177CRecovery policy configured for this system contains invalid recovery certificate
-21470188838007177DThe encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file
-21470188828007177EThe disk partition does not support file encryption
-21470188818007177FThis machine is disabled for file encryption
-214701888080071780A newer system is required to decrypt this encrypted file
-214701887980071781The remote server sent an invalid response for a file being opened with Client Side Encryption
-214701887880071782Client Side Encryption is not supported by the remote server even though it claims to support it
-214701887780071783File is encrypted and should be opened in Client Side Encryption mode
-214701887680071784A new encrypted file is being created and a $EFS needs to be provided
-214701887580071785The SMB client requested a CSE FSCTL on a non-CSE file
-214701887480071786The requested operation was blocked by policy. For more information
-214701887380071787The specified file could not be encrypted with Windows Information Protection
-2147018778800717E6The list of servers for this workgroup is not currently available
-214701869680071838The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts
-21470186468007186AThe object cannot be deleted from the local cluster because it is registered with the cluster set
-2147018296800719C8Log service encountered an invalid log sector
-2147018295800719C9Log service encountered a log sector with invalid block parity
-2147018294800719CALog service encountered a remapped log sector
-2147018293800719CBLog service encountered a partial or incomplete log block
-2147018292800719CCLog service encountered an attempt access data outside the active log range
-2147018291800719CDLog service user marshalling buffers are exhausted
-2147018290800719CELog service encountered an attempt read from a marshalling area with an invalid read context
-2147018289800719CFLog service encountered an invalid log restart area
-2147018288800719D0Log service encountered an invalid log block version
-2147018287800719D1Log service encountered an invalid log block
-2147018286800719D2Log service encountered an attempt to read the log with an invalid read mode
-2147018285800719D3Log service encountered a log stream with no restart area
-2147018284800719D4Log service encountered a corrupted metadata file
-2147018283800719D5Log service encountered a metadata file that could not be created by the log file system
-2147018282800719D6Log service encountered a metadata file with inconsistent data
-2147018281800719D7Log service encountered an attempt to erroneous allocate or dispose reservation space
-2147018280800719D8Log service cannot delete log file or file system container
-2147018279800719D9Log service has reached the maximum allowable containers allocated to a log file
-2147018278800719DALog service has attempted to read or write backward past the start of the log
-2147018277800719DBLog policy could not be installed because a policy of the same type is already present
-2147018276800719DCLog policy in question was not installed at the time of the request
-2147018275800719DDThe installed set of policies on the log is invalid
-2147018274800719DEA policy on the log in question prevented the operation from completing
-2147018273800719DFLog space cannot be reclaimed because the log is pinned by the archive tail
-2147018272800719E0Log record is not a record in the log file
-2147018271800719E1Number of reserved log records or the adjustment of the number of reserved log records is invalid
-2147018270800719E2Reserved log space or the adjustment of the log space is invalid
-2147018269800719E3An new or existing archive tail or base of the active log is invalid
-2147018268800719E4Log space is exhausted
-2147018267800719E5The log could not be set to the requested size
-2147018266800719E6Log is multiplexed
-2147018265800719E7The operation failed because the log is a dedicated log
-2147018264800719E8The operation requires an archive context
-2147018263800719E9Log archival is in progress
-2147018262800719EAThe operation requires a non-ephemeral log
-2147018261800719EBThe log must have at least two containers before it can be read from or written to
-2147018260800719ECA log client has already registered on the stream
-2147018259800719EDA log client has not been registered on the stream
-2147018258800719EEA request has already been made to handle the log full condition
-2147018257800719EFLog service encountered an error when attempting to read from a log container
-2147018256800719F0Log service encountered an error when attempting to write to a log container
-2147018255800719F1Log service encountered an error when attempting open a log container
-2147018254800719F2Log service encountered an invalid container state when attempting a requested action
-2147018253800719F3Log service is not in the correct state to perform a requested action
-2147018252800719F4Log space cannot be reclaimed because the log is pinned
-2147018251800719F5Log metadata flush failed
-2147018250800719F6Security on the log and its containers is inconsistent
-2147018249800719F7Records were appended to the log or reservation changes were made
-2147018248800719F8The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available
-214701819680071A2CThe transaction handle associated with this operation is not valid
-214701819580071A2DThe requested operation was made in the context of a transaction that is no longer active
-214701819480071A2EThe requested operation is not valid on the Transaction object in its current state
-214701819380071A2FThe caller has called a response API
-214701819280071A30It is too late to perform the requested operation
-214701819180071A31It is too late to perform the requested operation
-214701819080071A32The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported
-214701818980071A33The specified ResourceManager made no changes or updates to the resource under this transaction
-214701818880071A34The resource manager has attempted to prepare a transaction that it has not successfully joined
-214701818780071A35The Transaction object already has a superior enlistment
-214701818680071A36The RM tried to register a protocol that already exists
-214701818580071A37The attempt to propagate the Transaction failed
-214701818480071A38The requested propagation protocol was not registered as a CRM
-214701818380071A39The buffer passed in to PushTransaction or PullTransaction is not in a valid format
-214701818280071A3AThe current transaction context associated with the thread is not a valid handle to a transaction object
-214701818180071A3BThe specified Transaction object could not be opened
-214701818080071A3CThe specified ResourceManager object could not be opened
-214701817980071A3DThe specified Enlistment object could not be opened
-214701817880071A3EThe specified TransactionManager object could not be opened
-214701817780071A3FThe object specified could not be created or opened
-214701817680071A40The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore
-214701817580071A41The call to create a superior Enlistment on this Transaction object could not be completed
-214701817480071A42Because the associated transaction manager or resource manager has been closed
-214701817380071A43The specified operation could not be performed on this Superior enlistment
-214701817280071A44The specified operation could not be performed
-214701817180071A45Implicit transaction are not supported
-214701817080071A46The kernel transaction manager had to abort or forget the transaction because it blocked forward progress
-214701816980071A47The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file
-214701816880071A48This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again
-214701816780071A49The transaction cannot be enlisted on with the specified EnlistmentMask
-214701816680071A4AThe transaction does not have a superior enlistment
-214701816580071A4BThe attempt to commit the Transaction completed
-214701809680071A90The function attempted to use a name that is reserved for use by another transaction
-214701809580071A91Transaction support within the specified resource manager is not started or was shut down due to an error
-214701809480071A92The metadata of the RM has been corrupted. The RM will not function
-214701809380071A93The specified directory does not contain a resource manager
-214701809180071A95The remote server or share does not support transacted file operations
-214701809080071A96The requested log size is invalid
-214701808980071A97The object (file
-214701808880071A98The specified file miniversion was not found for this transacted file open
-214701808780071A99The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback
-214701808680071A9AA miniversion may only be opened in the context of the transaction that created it
-214701808580071A9BIt is not possible to open a miniversion with modify access
-214701808480071A9CIt is not possible to create any more miniversions for this stream
-214701808280071A9EThe remote server sent mismatching version number or Fid for a file opened with transactions
-214701808180071A9FThe 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
-214701808080071AA0There is no transaction metadata on the file
-214701807980071AA1The log data is corrupt
-214701807880071AA2The file can't be recovered because there is a handle still open on it
-214701807780071AA3The transaction outcome is unavailable because the resource manager responsible for it has disconnected
-214701807680071AA4The request was rejected because the enlistment in question is not a superior enlistment
-214701807580071AA5The transactional resource manager is already consistent. Recovery is not needed
-214701807480071AA6The transactional resource manager has already been started
-214701807380071AA7The file cannot be opened transactionally
-214701807280071AA8The operation cannot be performed because another transaction is depending on the fact that this property will not change
-214701807180071AA9The operation would involve a single file with two transactional resource managers and is therefore not allowed
-214701807080071AAAThe $Txf directory must be empty for this operation to succeed
-214701806980071AABThe operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed
-214701806880071AACThe operation could not be completed because the transaction manager does not have a log
-214701806780071AADA rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution
-214701806680071AAEThe transactional metadata attribute on the file or directory is corrupt and unreadable
-214701806580071AAFThe encryption operation could not be completed because a transaction is active
-214701806480071AB0This object is not allowed to be opened in a transaction
-214701806380071AB1An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log
-214701806280071AB2Memory mapping (creating a mapped section) a remote file under a transaction is not supported
-214701806180071AB3Transaction metadata is already present on this file and cannot be superseded
-214701806080071AB4A transaction scope could not be entered because the scope handler has not been initialized
-214701805980071AB5Promotion was required in order to allow the resource manager to enlist
-214701805880071AB6This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader
-214701805780071AB7The request to thaw frozen transactions was ignored because transactions had not previously been frozen
-214701805680071AB8Transactions cannot be frozen because a freeze is already in progress
-214701805580071AB9The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot
-214701805480071ABAThe savepoint operation failed because files are open on the transaction. This is not permitted
-214701805380071ABBWindows has discovered corruption in a file
-214701805280071ABCThe sparse operation could not be completed because a transaction is active on the file
-214701805180071ABDThe 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
-214701805080071ABEI/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data
-214701804980071ABFThe transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources
-214701804880071AC0The transactional resource manager had too many transactions outstanding that could not be aborted. The transactional resource manger has been shut down
-214701804780071AC1The operation could not be completed due to bad clusters on disk
-214701804680071AC2The compression operation could not be completed because a transaction is active on the file
-214701804580071AC3The operation could not be completed because the volume is dirty. Please run chkdsk and try again
-214701804480071AC4The link tracking operation could not be completed because a transaction is active
-214701804380071AC5This operation cannot be performed in a transaction
-214701804280071AC6The 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
-214701804180071AC7The specified operation could not be performed because the resource manager is not enlisted in the transaction
-214701789580071B59The specified session name is invalid
-214701789480071B5AThe specified protocol driver is invalid
-214701789380071B5BThe specified protocol driver was not found in the system path
-214701789280071B5CThe specified terminal connection driver was not found in the system path
-214701789180071B5DA registry key for event logging could not be created for this session
-214701789080071B5EA service with the same name already exists on the system
-214701788980071B5FA close operation is pending on the session
-214701788880071B60There are no free output buffers available
-214701788780071B61The MODEM.INF file was not found
-214701788680071B62The modem name was not found in MODEM.INF
-214701788580071B63The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem
-214701788480071B64The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on
-214701788380071B65Carrier detect has failed or carrier has been dropped due to disconnect
-214701788280071B66Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional
-214701788180071B67Busy signal detected at remote site on callback
-214701788080071B68Voice detected at remote site on callback
-214701787980071B69Transport driver error
-214701787480071B6EThe specified session cannot be found
-214701787380071B6FThe specified session name is already in use
-214701787280071B70The 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
-214701787180071B71An attempt has been made to connect to a session whose video mode is not supported by the current client
-214701786180071B7BThe application attempted to enable DOS graphics mode. DOS graphics mode is not supported
-214701785980071B7DYour interactive logon privilege has been disabled. Please contact your administrator
-214701785880071B7EThe 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
-214701785680071B80The client failed to respond to the server connect message
-214701785580071B81Disconnecting the console session is not supported
-214701785480071B82Reconnecting a disconnected session to the console is not supported
-214701785280071B84The request to control another session remotely was denied
-214701785180071B85The requested session access is denied
-214701784780071B89The specified terminal connection driver is invalid
-214701784680071B8AThe requested session cannot be controlled remotely.This may be because the session is disconnected or does not currently have a user logged on
-214701784580071B8BThe requested session is not configured to allow remote control
-214701784480071B8CYour request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number
-214701784380071B8DYour request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator
-214701784280071B8EThe number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator
-214701784180071B8FThe client you are using is not licensed to use this system. Your logon request is denied
-214701784080071B90The system license has expired. Your logon request is denied
-214701783980071B91Remote control could not be terminated because the specified session is not currently being remotely controlled
-214701783880071B92The 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
-214701783780071B93Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared
-214701783680071B94Remote logins are currently disabled
-214701783580071B95You do not have the proper encryption level to access this Session
-214701783480071B96The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer
-214701783380071B97The user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue
-214701783280071B98Unable to log you on because of an account restriction
-214701783180071B99The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client
-214701783080071B9AThe Client Drive Mapping Service Has Connected on Terminal Connection
-214701782980071B9BThe Client Drive Mapping Service Has Disconnected on Terminal Connection
-214701782880071B9CThe Terminal Server security layer detected an error in the protocol stream and has disconnected the client
-214701782780071B9DThe target session is incompatible with the current session
-214701782680071B9EWindows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later
-214701689580071F41The file replication service API was called incorrectly
-214701689480071F42The file replication service cannot be started
-214701689380071F43The file replication service cannot be stopped
-214701689280071F44The file replication service API terminated the request. The event log may have more information
-214701689180071F45The file replication service terminated the request. The event log may have more information
-214701689080071F46The file replication service cannot be contacted. The event log may have more information
-214701688980071F47The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information
-214701688880071F48The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information
-214701688780071F49The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information
-214701688680071F4AThe file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information
-214701688580071F4BThe file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information
-214701688480071F4CThe file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information
-214701688380071F4DThe file replication service cannot populate the system volume because of an internal error. The event log may have more information
-214701688280071F4EThe file replication service cannot populate the system volume because of an internal timeout. The event log may have more information
-214701688180071F4FThe file replication service cannot process the request. The system volume is busy with a previous request
-214701688080071F50The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information
-214701687980071F51The file replication service detected an invalid parameter
-214701669680072008An error occurred while installing the directory service. For more information
-214701669580072009The directory service evaluated group memberships locally
-21470166948007200AThe specified directory service attribute or value does not exist
-21470166938007200BThe attribute syntax specified to the directory service is invalid
-21470166928007200CThe attribute type specified to the directory service is not defined
-21470166918007200DThe specified directory service attribute or value already exists
-21470166908007200EThe directory service is busy
-21470166898007200FThe directory service is unavailable
-214701668880072010The directory service was unable to allocate a relative identifier
-214701668780072011The directory service has exhausted the pool of relative identifiers
-214701668680072012The requested operation could not be performed because the directory service is not the master for that type of operation
-214701668580072013The directory service was unable to initialize the subsystem that allocates relative identifiers
-214701668480072014The requested operation did not satisfy one or more constraints associated with the class of the object
-214701668380072015The directory service can perform the requested operation only on a leaf object
-214701668280072016The directory service cannot perform the requested operation on the RDN attribute of an object
-214701668180072017The directory service detected an attempt to modify the object class of an object
-214701668080072018The requested cross-domain move operation could not be performed
-214701667980072019Unable to contact the global catalog server
-21470166788007201AThe policy object is shared and can only be modified at the root
-21470166778007201BThe policy object does not exist
-21470166768007201CThe requested policy information is only in the directory service
-21470166758007201DA domain controller promotion is currently active
-21470166748007201EA domain controller promotion is not currently active
-214701667280072020An operations error occurred
-214701667180072021A protocol error occurred
-214701667080072022The time limit for this request was exceeded
-214701666980072023The size limit for this request was exceeded
-214701666880072024The administrative limit for this request was exceeded
-214701666780072025The compare response was false
-214701666680072026The compare response was true
-214701666580072027The requested authentication method is not supported by the server
-214701666480072028A more secure authentication method is required for this server
-214701666380072029Inappropriate authentication
-21470166628007202AThe authentication mechanism is unknown
-21470166618007202BA referral was returned from the server
-21470166608007202CThe server does not support the requested critical extension
-21470166598007202DThis request requires a secure connection
-21470166588007202EInappropriate matching
-21470166578007202FA constraint violation occurred
-214701665680072030There is no such object on the server
-214701665580072031There is an alias problem
-214701665480072032An invalid dn syntax has been specified
-214701665380072033The object is a leaf object
-214701665280072034There is an alias dereferencing problem
-214701665180072035The server is unwilling to process the request
-214701665080072036A loop has been detected
-214701664980072037There is a naming violation
-214701664880072038The result set is too large
-214701664780072039The operation affects multiple DSAs
-21470166468007203AThe server is not operational
-21470166458007203BA local error has occurred
-21470166448007203CAn encoding error has occurred
-21470166438007203DA decoding error has occurred
-21470166428007203EThe search filter cannot be recognized
-21470166418007203FOne or more parameters are illegal
-214701664080072040The specified method is not supported
-214701663980072041No results were returned
-214701663880072042The specified control is not supported by the server
-214701663780072043A referral loop was detected by the client
-214701663680072044The preset referral limit was exceeded
-214701663580072045The search requires a SORT control
-214701663480072046The search results exceed the offset range specified
-214701663380072047The 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
-21470165958007206DThe root object must be the head of a naming context. The root object cannot have an instantiated parent
-21470165948007206EThe add replica operation cannot be performed. The naming context must be writeable in order to create the replica
-21470165938007206FA reference to an attribute that is not defined in the schema occurred
-214701659280072070The maximum size of an object has been exceeded
-214701659180072071An attempt was made to add an object to the directory with a name that is already in use
-214701659080072072An attempt was made to add an object of a class that does not have an RDN defined in the schema
-214701658980072073An attempt was made to add an object using an RDN that is not the RDN defined in the schema
-214701658880072074None of the requested attributes were found on the objects
-214701658780072075The user buffer is too small
-214701658680072076The attribute specified in the operation is not present on the object
-214701658580072077Illegal modify operation. Some aspect of the modification is not permitted
-214701658480072078The specified object is too large
-214701658380072079The specified instance type is not valid
-21470165828007207AThe operation must be performed at a master DSA
-21470165818007207BThe object class attribute must be specified
-21470165808007207CA required attribute is missing
-21470165798007207DAn attempt was made to modify an object to include an attribute that is not legal for its class
-21470165788007207EThe specified attribute is already present on the object
-214701657680072080The specified attribute is not present
-214701657580072081Multiple values were specified for an attribute that can have only one value
-214701657480072082A value for the attribute was not in the acceptable range of values
-214701657380072083The specified value already exists
-214701657280072084The attribute cannot be removed because it is not present on the object
-214701657180072085The attribute value cannot be removed because it is not present on the object
-214701657080072086The specified root object cannot be a subref
-214701656980072087Chaining is not permitted
-214701656880072088Chained evaluation is not permitted
-214701656780072089The operation could not be performed because the object's parent is either uninstantiated or deleted
-21470165668007208AHaving a parent that is an alias is not permitted. Aliases are leaf objects
-21470165658007208BThe object and parent must be of the same type
-21470165648007208CThe operation cannot be performed because child objects exist. This operation can only be performed on a leaf object
-21470165638007208DDirectory object not found
-21470165628007208EThe aliased object is missing
-21470165618007208FThe object name has bad syntax
-214701656080072090It is not permitted for an alias to refer to another alias
-214701655980072091The alias cannot be dereferenced
-214701655880072092The operation is out of scope
-214701655780072093The operation cannot continue because the object is in the process of being removed
-214701655680072094The DSA object cannot be deleted
-214701655580072095A directory service error has occurred
-214701655480072096The operation can only be performed on an internal master DSA object
-214701655380072097The object must be of class DSA
-214701655280072098Insufficient access rights to perform the operation
-214701655180072099The object cannot be added because the parent is not on the list of possible superiors
-21470165508007209AAccess to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM)
-21470165498007209BThe name has too many parts
-21470165488007209CThe name is too long
-21470165478007209DThe name value is too long
-21470165468007209EThe directory service encountered an error parsing a name
-21470165458007209FThe directory service cannot get the attribute type for a name
-2147016544800720A0The name does not identify an object; the name identifies a phantom
-2147016543800720A1The security descriptor is too short
-2147016542800720A2The security descriptor is invalid
-2147016541800720A3Failed to create name for deleted object
-2147016540800720A4The parent of a new subref must exist
-2147016539800720A5The object must be a naming context
-2147016538800720A6It is not permitted to add an attribute which is owned by the system
-2147016537800720A7The class of the object must be structural; you cannot instantiate an abstract class
-2147016536800720A8The schema object could not be found
-2147016535800720A9A local object with this GUID (dead or alive) already exists
-2147016534800720AAThe operation cannot be performed on a back link
-2147016533800720ABThe cross reference for the specified naming context could not be found
-2147016532800720ACThe operation could not be performed because the directory service is shutting down
-2147016531800720ADThe directory service request is invalid
-2147016530800720AEThe role owner attribute could not be read
-2147016529800720AFThe requested FSMO operation failed. The current FSMO holder could not be contacted
-2147016528800720B0Modification of a DN across a naming context is not permitted
-2147016527800720B1The attribute cannot be modified because it is owned by the system
-2147016526800720B2Only the replicator can perform this function
-2147016525800720B3The specified class is not defined
-2147016524800720B4The specified class is not a subclass
-2147016523800720B5The name reference is invalid
-2147016522800720B6A cross reference already exists
-2147016521800720B7It is not permitted to delete a master cross reference
-2147016520800720B8Subtree notifications are only supported on NC heads
-2147016519800720B9Notification filter is too complex
-2147016518800720BASchema update failed: duplicate RDN
-2147016517800720BBSchema update failed: duplicate OID
-2147016516800720BCSchema update failed: duplicate MAPI identifier
-2147016515800720BDSchema update failed: duplicate schema-id GUID
-2147016514800720BESchema update failed: duplicate LDAP display name
-2147016513800720BFSchema update failed: range-lower less than range upper
-2147016512800720C0Schema update failed: syntax mismatch
-2147016511800720C1Schema deletion failed: attribute is used in must-contain
-2147016510800720C2Schema deletion failed: attribute is used in may-contain
-2147016509800720C3Schema update failed: attribute in may-contain does not exist
-2147016508800720C4Schema update failed: attribute in must-contain does not exist
-2147016507800720C5Schema update failed: class in aux-class list does not exist or is not an auxiliary class
-2147016506800720C6Schema update failed: class in poss-superiors does not exist
-2147016505800720C7Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules
-2147016504800720C8Schema update failed: Rdn-Att-Id has wrong syntax
-2147016503800720C9Schema deletion failed: class is used as auxiliary class
-2147016502800720CASchema deletion failed: class is used as sub class
-2147016501800720CBSchema deletion failed: class is used as poss superior
-2147016500800720CCSchema update failed in recalculating validation cache
-2147016499800720CDThe tree deletion is not finished. The request must be made again to continue deleting the tree
-2147016498800720CEThe requested delete operation could not be performed
-2147016497800720CFCannot read the governs class identifier for the schema record
-2147016496800720D0The attribute schema has bad syntax
-2147016495800720D1The attribute could not be cached
-2147016494800720D2The class could not be cached
-2147016493800720D3The attribute could not be removed from the cache
-2147016492800720D4The class could not be removed from the cache
-2147016491800720D5The distinguished name attribute could not be read
-2147016490800720D6No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest
-2147016489800720D7The instance type attribute could not be retrieved
-2147016488800720D8An internal error has occurred
-2147016487800720D9A database error has occurred
-2147016486800720DAThe attribute GOVERNSID is missing
-2147016485800720DBAn expected attribute is missing
-2147016484800720DCThe specified naming context is missing a cross reference
-2147016483800720DDA security checking error has occurred
-2147016482800720DEThe schema is not loaded
-2147016481800720DFSchema allocation failed. Please check if the machine is running low on memory
-2147016480800720E0Failed to obtain the required syntax for the attribute schema
-2147016479800720E1The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available
-2147016478800720E2The replication operation failed because of a schema mismatch between the servers involved
-2147016477800720E3The DSA object could not be found
-2147016476800720E4The naming context could not be found
-2147016475800720E5The naming context could not be found in the cache
-2147016474800720E6The child object could not be retrieved
-2147016473800720E7The modification was not permitted for security reasons
-2147016472800720E8The operation cannot replace the hidden record
-2147016471800720E9The hierarchy file is invalid
-2147016470800720EAThe attempt to build the hierarchy table failed
-2147016469800720EBThe directory configuration parameter is missing from the registry
-2147016468800720ECThe attempt to count the address book indices failed
-2147016467800720EDThe allocation of the hierarchy table failed
-2147016466800720EEThe directory service encountered an internal failure
-2147016465800720EFThe directory service encountered an unknown failure
-2147016464800720F0A root object requires a class of 'top'
-2147016463800720F1This directory server is shutting down
-2147016462800720F2The directory service is missing mandatory configuration information
-2147016461800720F3The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers
-2147016460800720F4The replication operation failed
-2147016459800720F5An invalid parameter was specified for this replication operation
-2147016458800720F6The directory service is too busy to complete the replication operation at this time
-2147016457800720F7The distinguished name specified for this replication operation is invalid
-2147016456800720F8The naming context specified for this replication operation is invalid
-2147016455800720F9The distinguished name specified for this replication operation already exists
-2147016454800720FAThe replication system encountered an internal error
-2147016453800720FBThe replication operation encountered a database inconsistency
-2147016452800720FCThe server specified for this replication operation could not be contacted
-2147016451800720FDThe replication operation encountered an object with an invalid instance type
-2147016450800720FEThe replication operation failed to allocate memory
-2147016449800720FFThe replication operation encountered an error with the mail system
-214701644880072100The replication reference information for the target server already exists
-214701644780072101The replication reference information for the target server does not exist
-214701644680072102The naming context cannot be removed because it is replicated to another server
-214701644580072103The replication operation encountered a database error
-214701644480072104The naming context is in the process of being removed or is not replicated from the specified server
-214701644380072105Replication access was denied
-214701644280072106The requested operation is not supported by this version of the directory service
-214701644180072107The replication remote procedure call was cancelled
-214701644080072108The source server is currently rejecting replication requests
-214701643980072109The destination server is currently rejecting replication requests
-21470164388007210AThe replication operation failed due to a collision of object names
-21470164378007210BThe replication source has been reinstalled
-21470164368007210CThe replication operation failed because a required parent object is missing
-21470164358007210DThe replication operation was preempted
-21470164348007210EThe replication synchronization attempt was abandoned because of a lack of updates
-21470164338007210FThe replication operation was terminated because the system is shutting down
-214701643280072110Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set
-214701643180072111The replication synchronization attempt failed because a master replica attempted to sync from a partial replica
-214701643080072112The server specified for this replication operation was contacted
-214701642980072113The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer
-214701642880072114Schema update failed: An attribute with the same link identifier already exists
-214701642780072115Name translation: Generic processing error
-214701642680072116Name translation: Could not find the name or insufficient right to see name
-214701642580072117Name translation: Input name mapped to more than one output name
-214701642480072118Name translation: Input name found
-214701642380072119Name translation: Unable to resolve completely
-21470164228007211AName translation: Unable to perform purely syntactical mapping at the client without going out to the wire
-21470164218007211BModification of a constructed attribute is not allowed
-21470164208007211CThe OM-Object-Class specified is incorrect for an attribute with the specified syntax
-21470164198007211DThe replication request has been posted; waiting for reply
-21470164188007211EThe requested operation requires a directory service
-21470164178007211FThe LDAP display name of the class or attribute contains non-ASCII characters
-214701641680072120The requested search operation is only supported for base searches
-214701641580072121The search failed to retrieve attributes from the database
-214701641480072122The schema update operation tried to add a backward link attribute that has no corresponding forward link
-214701641380072123Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object
-214701641280072124Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object
-214701641180072125Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation
-214701641080072126Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container
-214701640980072127Destination of a cross-domain move is not authoritative for the destination naming context
-214701640880072128Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object
-214701640780072129Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object
-21470164068007212AAnother operation which requires exclusive access to the PDC FSMO is already in progress
-21470164058007212BA cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state
-21470164048007212CThis object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed
-21470164038007212DCan't move objects with memberships across domain boundaries as once moved
-21470164028007212EA naming context head must be the immediate child of another naming context head
-21470164018007212FThe directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server
-214701640080072130Destination domain must be in native mode
-214701639980072131The operation cannot be performed because the server does not have an infrastructure container in the domain of interest
-214701639880072132Cross-domain move of non-empty account groups is not allowed
-214701639780072133Cross-domain move of non-empty resource groups is not allowed
-214701639680072134The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings
-214701639580072135Tree deletions starting at an object which has an NC head as a descendant are not allowed
-214701639480072136The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use
-214701639380072137The directory service failed to identify the list of objects to delete while attempting a tree deletion
-214701639280072138Security Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode
-214701639180072139Only an administrator can modify the membership list of an administrative group
-21470163908007213ACannot change the primary group ID of a domain controller account
-21470163898007213BAn attempt is made to modify the base schema
-21470163888007213CAdding a new mandatory attribute to an existing class
-21470163878007213DSchema update is not allowed on this DC because the DC is not the schema FSMO Role Owner
-21470163868007213EAn object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container
-21470163858007213FThe replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it
-214701638480072140The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory
-214701638380072141The specified group type is invalid
-214701638280072142You cannot nest global groups in a mixed domain if the group is security-enabled
-214701638180072143You cannot nest local groups in a mixed domain if the group is security-enabled
-214701638080072144A global group cannot have a local group as a member
-214701637980072145A global group cannot have a universal group as a member
-214701637880072146A universal group cannot have a local group as a member
-214701637780072147A global group cannot have a cross-domain member
-214701637680072148A local group cannot have another cross domain local group as a member
-214701637580072149A group with primary members cannot change to a security-disabled group
-21470163748007214AThe schema cache load failed to convert the string default SD on a class-schema object
-21470163738007214BOnly DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
-21470163728007214CThe DSA operation is unable to proceed because of a DNS lookup failure
-21470163718007214DWhile processing a change to the DNS Host Name for an object
-21470163708007214EThe Security Descriptor attribute could not be read
-21470163698007214FThe object requested was not found
-214701636880072150The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1
-214701636780072151Security Account Manager needs to get the boot password
-214701636680072152Security Account Manager needs to get the boot key from floppy disk
-214701636580072153Directory Service cannot start
-214701636480072154Directory Services could not start
-214701636380072155The connection between client and server requires packet privacy or better
-214701636280072156The source domain may not be in the same forest as destination
-214701636180072157The destination domain must be in the forest
-214701636080072158The operation requires that destination domain auditing be enabled
-214701635980072159The operation couldn't locate a DC for the source domain
-21470163588007215AThe source object must be a group or user
-21470163578007215BThe source object's SID already exists in destination forest
-21470163568007215CThe source and destination object must be of the same type
-21470163558007215DSecurity Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information
-21470163548007215ESchema information could not be included in the replication request
-21470163538007215FThe replication operation could not be completed due to a schema incompatibility
-214701635280072160The replication operation could not be completed due to a previous schema incompatibility
-214701635180072161The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation
-214701635080072162The requested domain could not be deleted because there exist domain controllers that still host this domain
-214701634980072163The requested operation can be performed only on a global catalog server
-214701634880072164A local group can only be a member of other local groups in the same domain
-214701634780072165Foreign security principals cannot be members of universal groups
-214701634680072166The attribute is not allowed to be replicated to the GC because of security reasons
-214701634580072167The checkpoint with the PDC could not be taken because there too many modifications being processed currently
-214701634480072168The operation requires that source domain auditing be enabled
-214701634380072169Security principal objects can only be created inside domain naming contexts
-21470163428007216AA Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format
-21470163418007216BA Filter was passed that uses constructed attributes
-21470163408007216CThe unicodePwd attribute value must be enclosed in double quotes
-21470163398007216DYour 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
-21470163388007216EFor security reasons
-21470163378007216FFor security reasons
-214701633680072170Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed
-214701633580072171Directory Services could not start because of the following error: %1.Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further
-214701633480072172Security Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further
-214701633380072173The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set
-214701633280072174The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain
-214701633180072175The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set
-214701633080072176The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain
-214701632980072177The version of the operating system installed on this server is incompatible with the functional level of the domain or forest
-214701632880072178The functional level of the domain (or forest) cannot be raised to the requested value
-214701632780072179The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode
-21470163268007217AThe sort order requested is not supported
-21470163258007217BThe requested name already exists as a unique identifier
-21470163248007217CThe machine account was created pre-NT4. The account needs to be recreated
-21470163238007217DThe database is out of version store
-21470163228007217EUnable to continue operation because multiple conflicting controls were used
-21470163218007217FUnable to find a valid security descriptor reference domain for this partition
-214701632080072180Schema update failed: The link identifier is reserved
-214701631980072181Schema update failed: There are no link identifiers available
-214701631880072182An account group cannot have a universal group as a member
-214701631780072183Rename or move operations on naming context heads or read-only objects are not allowed
-214701631680072184Move operations on objects in the schema naming context are not allowed
-214701631580072185A system flag has been set on the object and does not allow the object to be moved or renamed
-214701631480072186This object is not allowed to change its grandparent container. Moves are not forbidden on this object
-214701631380072187Unable to resolve completely
-214701631280072188The requested action is not supported on standard server
-214701631180072189Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question
-21470163108007218AThe directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS
-21470163098007218BThe thread limit for this request was exceeded
-21470163088007218CThe Global catalog server is not in the closest site
-21470163078007218DThe DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute
-21470163068007218EThe Directory Service failed to enter single user mode
-21470163058007218FThe Directory Service cannot parse the script because of a syntax error
-214701630480072190The Directory Service cannot process the script because of an error
-214701630380072191The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress)
-214701630280072192The directory service binding must be renegotiated due to a change in the server extensions information
-214701630180072193Operation not allowed on a disabled cross ref
-214701630080072194Schema update failed: No values for msDS-IntId are available
-214701629980072195Schema update failed: Duplicate msDS-INtId. Retry the operation
-214701629880072196Schema deletion failed: attribute is used in rDNAttID
-214701629780072197The directory service failed to authorize the request
-214701629680072198The Directory Service cannot process the script because it is invalid
-214701629580072199The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data
-21470162948007219AA cross reference is in use locally with the same name
-21470162938007219BThe DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest
-21470162928007219CWriteable NCs prevent this DC from demoting
-21470162918007219DThe requested object has a non-unique identifier and cannot be retrieved
-21470162908007219EInsufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected
-21470162898007219FThe group cannot be converted due to attribute restrictions on the requested group type
-2147016288800721A0Cross-domain move of non-empty basic application groups is not allowed
-2147016287800721A1Cross-domain move of non-empty query based application groups is not allowed
-2147016286800721A2The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner
-2147016285800721A3The target container for a redirection of a well known object container cannot already be a special container
-2147016284800721A4The Directory Service cannot perform the requested operation because a domain rename operation is in progress
-2147016283800721A5The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method
-2147016282800721A6The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime
-2147016281800721A7The requested operation is not allowed on an object under the system container
-2147016280800721A8The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected
-2147016279800721A9The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency
-2147016278800721AAAt this time
-2147016277800721ABThe site settings object for the specified site does not exist
-2147016276800721ACThe local account store does not contain secret material for the specified account
-2147016275800721ADCould not find a writable domain controller in the domain
-2147016274800721AEThe server object for the domain controller does not exist
-2147016273800721AFThe NTDS Settings object for the domain controller does not exist
-2147016272800721B0The requested search operation is not supported for ASQ searches
-2147016271800721B1A required audit event could not be generated for the operation
-2147016270800721B2The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes
-2147016269800721B3The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings
-2147016268800721B4The address books are nested too deeply. Failed to build the hierarchy table
-2147016267800721B5The specified up-to-date-ness vector is corrupt
-2147016266800721B6The request to replicate secrets is denied
-2147016265800721B7Schema update failed: The MAPI identifier is reserved
-2147016264800721B8Schema update failed: There are no MAPI identifiers available
-2147016263800721B9The replication operation failed because the required attributes of the local krbtgt object are missing
-2147016262800721BAThe domain name of the trusted domain already exists in the forest
-2147016261800721BBThe flat name of the trusted domain already exists in the forest
-2147016260800721BCThe User Principal Name (UPN) is invalid
-2147016259800721BDOID mapped groups cannot have members
-2147016258800721BEThe specified OID cannot be found
-2147016257800721BFThe replication operation failed because the target object referred by a link value is recycled
-2147016256800721C0The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller
-2147016255800721C1The functional level of the AD LDS configuration set cannot be lowered to the requested value
-2147016254800721C2The functional level of the domain (or forest) cannot be lowered to the requested value
-2147016253800721C3The functional level of the AD LDS configuration set cannot be raised to the requested value
-2147016252800721C4The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information
-2147016251800721C5The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object
-2147016250800721C6The 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
-2147016249800721C7The operation failed because SPN value provided for addition/modification is not unique forest-wide
-2147016248800721C8The operation failed because UPN value provided for addition/modification is not unique forest-wide
-2147016247800721C9The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present
-2147016246800721CAThe link value specified was not found
-2147016244800721CCThe add object operation failed because the caller was not authorized to add one or more attributes included in the request
-214701589580072329DNS server unable to interpret format
-21470158948007232ADNS server failure
-21470158938007232BDNS name does not exist
-21470158928007232CDNS request not supported by name server
-21470158918007232DDNS operation refused
-21470158908007232EDNS name that ought not exist
-21470158898007232FDNS RR set that ought not exist
-214701588880072330DNS RR set that ought to exist
-214701588780072331DNS server not authoritative for zone
-214701588680072332DNS name in update or prereq is not in zone
-214701588080072338DNS signature failed to verify
-214701587980072339DNS bad key
-21470158788007233ADNS signature validity expired
-21470157958007238DOnly the DNS server acting as the key master for the zone may perform this operation
-21470157948007238EThis operation is not allowed on a zone that is signed or has signing keys
-21470157938007238FNSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC
-214701579280072390The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK)
-214701579180072391The specified algorithm is not supported
-214701579080072392The specified key size is not supported
-214701578980072393One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved
-214701578880072394The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved
-214701578780072395An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved
-214701578680072396An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved
-214701578580072397The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved
-214701578480072398The specified key service provider cannot be opened by the DNS server
-214701578380072399The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone
-21470157828007239AThe specified rollover period is invalid
-21470157818007239BThe specified initial rollover offset is invalid
-21470157808007239CThe specified signing key is already in process of rolling over keys
-21470157798007239DThe specified signing key does not have a standby key to revoke
-21470157788007239EThis operation is not allowed on a zone signing key (ZSK)
-21470157778007239FThis operation is not allowed on an active signing key
-2147015776800723A0The specified signing key is already queued for rollover
-2147015775800723A1This operation is not allowed on an unsigned zone
-2147015774800723A2This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role
-2147015773800723A3The specified signature validity period is invalid
-2147015772800723A4The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone
-2147015771800723A5This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server
-2147015770800723A6This operation could not be completed because the XML stream received is empty or syntactically invalid
-2147015769800723A7This operation completed
-2147015768800723A8The specified signing key is not waiting for parental DS update
-2147015767800723A9Hash collision detected during NSEC3 signing. Specify a different user-provided salt
-2147015766800723AANSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3
-21470153958007251DNo records found for given DNS query
-21470153948007251EBad DNS packet
-21470153938007251FNo DNS packet
-214701539280072520DNS error
-214701539180072521Unsecured DNS packet
-214701539080072522DNS query request is pending
-21470153458007254FInvalid DNS type
-214701534480072550Invalid IP address
-214701534380072551Invalid property
-214701534280072552Try DNS operation again later
-214701534180072553Record for given name and type is not unique
-214701534080072554DNS name does not comply with RFC specifications
-214701533980072555DNS name is a fully-qualified DNS name
-214701533880072556DNS name is dotted (multi-label)
-214701533780072557DNS name is a single-part name
-214701533680072558DNS name contains an invalid character
-214701533580072559DNS name is entirely numeric
-21470153348007255AThe operation requested is not permitted on a DNS root server
-21470153338007255BThe record could not be created because this part of the DNS namespace has been delegated to another server
-21470153328007255CThe DNS server could not find a set of root hints
-21470153318007255DThe DNS server found root hints but they were not consistent across all adapters
-21470153308007255EThe specified value is too small for this parameter
-21470153298007255FThe specified value is too large for this parameter
-214701532880072560This operation is not allowed while the DNS server is loading zones in the background. Please try again later
-214701532780072561The operation requested is not permitted on against a DNS server running on a read-only DC
-214701532680072562No data is allowed to exist underneath a DNAME record
-214701532580072563This operation requires credentials delegation
-214701532480072564Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator
-214701532380072565Not allowed to remove all addresses
-214701529580072581DNS zone does not exist
-214701529480072582DNS zone information not available
-214701529380072583Invalid operation for DNS zone
-214701529280072584Invalid DNS zone configuration
-214701529180072585DNS zone has no start of authority (SOA) record
-214701529080072586DNS zone has no Name Server (NS) record
-214701528980072587DNS zone is locked
-214701528880072588DNS zone creation failed
-214701528780072589DNS zone already exists
-21470152868007258ADNS automatic zone already exists
-21470152858007258BInvalid DNS zone type
-21470152848007258CSecondary DNS zone requires master IP address
-21470152838007258DDNS zone not secondary
-21470152828007258ENeed secondary IP address
-21470152818007258FWINS initialization failed
-214701528080072590Need WINS servers
-214701527980072591NBTSTAT initialization call failed
-214701527880072592Invalid delete of start of authority (SOA)
-214701527780072593A conditional forwarding zone already exists for that name
-214701527680072594This zone must be configured with one or more master DNS server IP addresses
-214701527580072595The operation cannot be performed because this zone is shut down
-214701527480072596This operation cannot be performed because the zone is currently being signed. Please try again later
-2147015245800725B3Primary DNS zone requires datafile
-2147015244800725B4Invalid datafile name for DNS zone
-2147015243800725B5Failed to open datafile for DNS zone
-2147015242800725B6Failed to write datafile for DNS zone
-2147015241800725B7Failure while reading datafile for DNS zone
-2147015195800725E5DNS record does not exist
-2147015194800725E6DNS record format error
-2147015193800725E7Node creation failure in DNS
-2147015192800725E8Unknown DNS record type
-2147015191800725E9DNS record timed out
-2147015190800725EAName not in DNS zone
-2147015189800725EBCNAME loop detected
-2147015188800725ECNode is a CNAME DNS record
-2147015187800725EDA CNAME record already exists for given name
-2147015186800725EERecord only at DNS zone root
-2147015185800725EFDNS record already exists
-2147015184800725F0Secondary DNS zone data error
-2147015183800725F1Could not create DNS cache data
-2147015182800725F2DNS name does not exist
-2147015181800725F3Could not create pointer (PTR) record
-2147015180800725F4DNS domain was undeleted
-2147015179800725F5The directory service is unavailable
-2147015178800725F6DNS zone already exists in the directory service
-2147015177800725F7DNS server not creating or reading the boot file for the directory service integrated DNS zone
-2147015176800725F8Node is a DNAME DNS record
-2147015175800725F9A DNAME record already exists for given name
-2147015174800725FAAn alias loop has been detected with either CNAME or DNAME records
-214701514580072617DNS AXFR (zone transfer) complete
-214701514480072618DNS zone transfer failed
-214701514380072619Added local WINS server
-214701509580072649Secure update call needs to continue update request
-21470150458007267BTCP/IP network protocol not installed
-21470150448007267CNo DNS servers configured for local system
-2147014995800726ADThe specified directory partition does not exist
-2147014994800726AEThe specified directory partition already exists
-2147014993800726AFThis DNS server is not enlisted in the specified directory partition
-2147014992800726B0This DNS server is already enlisted in the specified directory partition
-2147014991800726B1The directory partition is not available at this time. Please wait a few minutes and try again
-2147014990800726B2The operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later
-2147014985800726B7The RRL is not enabled
-2147014984800726B8The window size parameter is invalid. It should be greater than or equal to 1
-2147014983800726B9The IPv4 prefix length parameter is invalid. It should be less than or equal to 32
-2147014982800726BAThe IPv6 prefix length parameter is invalid. It should be less than or equal to 128
-2147014981800726BBThe TC Rate parameter is invalid. It should be less than 10
-2147014980800726BCThe Leak Rate parameter is invalid. It should be either 0
-2147014979800726BDThe Leak Rate or TC Rate parameter is invalid. Leak Rate should be greater than TC Rate
-2147014975800726C1The virtualization instance already exists
-2147014974800726C2The virtualization instance does not exist
-2147014973800726C3The virtualization tree is locked
-2147014972800726C4Invalid virtualization instance name
-2147014971800726C5The default virtualization instance cannot be added
-2147014945800726DFThe scope already exists for the zone
-2147014944800726E0The scope does not exist for the zone
-2147014943800726E1The scope is the same as the default zone scope
-2147014942800726E2The scope name contains invalid characters
-2147014941800726E3Operation not allowed when the zone has scopes
-2147014940800726E4Failed to load zone scope
-2147014939800726E5Failed to write data file for DNS zone scope. Please verify the file exists and is writable
-2147014938800726E6The scope name contains invalid characters
-2147014937800726E7The scope does not exist
-2147014936800726E8The scope is the same as the default scope
-2147014935800726E9The operation is invalid on the scope
-2147014934800726EAThe scope is locked
-2147014933800726EBThe scope already exists
-2147014925800726F3A policy with the same name already exists on this level (server level or zone level) on the DNS server
-2147014924800726F4No policy with this name exists on this level (server level or zone level) on the DNS server
-2147014923800726F5The criteria provided in the policy are invalid
-2147014922800726F6At least one of the settings of this policy is invalid
-2147014921800726F7The client subnet cannot be deleted while it is being accessed by a policy
-2147014920800726F8The client subnet does not exist on the DNS server
-2147014919800726F9A client subnet with this name already exists on the DNS server
-2147014918800726FAThe IP subnet specified does not exist in the client subnet
-2147014917800726FBThe IP subnet that is being added
-2147014916800726FCThe policy is locked
-2147014915800726FDThe weight of the scope in the policy is invalid
-2147014914800726FEThe DNS policy name is invalid
-2147014913800726FFThe policy is missing criteria
-214701491280072700The name of the the client subnet record is invalid
-214701491180072701Invalid policy processing order
-214701491080072702The scope information has not been provided for a policy that requires it
-214701490980072703The scope information has been provided for a policy that does not require it
-214701490880072704The server scope cannot be deleted because it is referenced by a DNS Policy
-214701490780072705The zone scope cannot be deleted because it is referenced by a DNS Policy
-214701490680072706The criterion client subnet provided in the policy is invalid
-214701490580072707The criterion transport protocol provided in the policy is invalid
-214701490480072708The criterion network protocol provided in the policy is invalid
-214701490380072709The criterion interface provided in the policy is invalid
-21470149028007270AThe criterion FQDN provided in the policy is invalid
-21470149018007270BThe criterion query type provided in the policy is invalid
-21470149008007270CThe criterion time of day provided in the policy is invalid
-214701489280072714A blocking operation was interrupted by a call to WSACancelBlockingCall
-214701488780072719The file handle supplied is not valid
-21470148838007271DAn attempt was made to access a socket in a way forbidden by its access permissions
-21470148828007271EThe system detected an invalid pointer address in attempting to use a pointer argument in a call
-214701487480072726An invalid argument was supplied
-214701487280072728Too many open sockets
-214701486180072733A non-blocking socket operation could not be completed immediately
-214701486080072734A blocking operation is currently executing
-214701485980072735An operation was attempted on a non-blocking socket that already had an operation in progress
-214701485880072736An operation was attempted on something that is not a socket
-214701485780072737A required address was omitted from an operation on a socket
-214701485680072738A message sent on a datagram socket was larger than the internal message buffer or some other network limit
-214701485580072739A protocol was specified in the socket function call that does not support the semantics of the socket type requested
-21470148548007273AAn unknown
-21470148538007273BThe requested protocol has not been configured into the system
-21470148528007273CThe support for the specified socket type does not exist in this address family
-21470148518007273DThe attempted operation is not supported for the type of object referenced
-21470148508007273EThe protocol family has not been configured into the system or no implementation for it exists
-21470148498007273FAn address incompatible with the requested protocol was used
-214701484880072740Only one usage of each socket address (protocol/network address/port) is normally permitted
-214701484780072741The requested address is not valid in its context
-214701484680072742A socket operation encountered a dead network
-214701484580072743A socket operation was attempted to an unreachable network
-214701484480072744The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress
-214701484380072745An established connection was aborted by the software in your host machine
-214701484280072746An existing connection was forcibly closed by the remote host
-214701484180072747An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
-214701484080072748A connect request was made on an already connected socket
-214701483980072749A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied
-21470148388007274AA request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call
-21470148378007274BToo many references to some kernel object
-21470148368007274CA connection attempt failed because the connected party did not properly respond after a period of time
-21470148358007274DNo connection could be made because the target machine actively refused it
-21470148348007274ECannot translate name
-21470148338007274FName component or name was too long
-214701483280072750A socket operation failed because the destination host was down
-214701483180072751A socket operation was attempted to an unreachable host
-214701483080072752Cannot remove a directory that is not empty
-214701482980072753A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously
-214701482880072754Ran out of quota
-214701482780072755Ran out of disk quota
-214701482680072756File handle reference is no longer available
-214701482580072757Item is not available locally
-21470148058007276BWSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable
-21470148048007276CThe Windows Sockets version requested is not supported
-21470148038007276DEither the application has not called WSAStartup
-214701479580072775Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence
-214701479480072776No more results can be returned by WSALookupServiceNext
-214701479380072777A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled
-214701479280072778The procedure call table is invalid
-214701479180072779The requested service provider is invalid
-21470147908007277AThe requested service provider could not be loaded or initialized
-21470147898007277BA system call has failed
-21470147888007277CNo such service is known. The service cannot be found in the specified name space
-21470147878007277DThe specified class was not found
-21470147868007277ENo more results can be returned by WSALookupServiceNext
-21470147858007277FA call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled
-214701478480072780A database query failed because it was actively refused
-214701389580072AF9No such host is known
-214701389480072AFAThis is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
-214701389380072AFBA non-recoverable error occurred during a database lookup
-214701389280072AFCThe requested name is valid
-214701389180072AFDAt least one reserve has arrived
-214701389080072AFEAt least one path has arrived
-214701388980072AFFThere are no senders
-214701388880072B00There are no receivers
-214701388780072B01Reserve has been confirmed
-214701388680072B02Error due to lack of resources
-214701388580072B03Rejected for administrative reasons - bad credentials
-214701388480072B04Unknown or conflicting style
-214701388380072B05Problem with some part of the filterspec or providerspecific buffer in general
-214701388280072B06Problem with some part of the flowspec
-214701388180072B07General QOS error
-214701388080072B08An invalid or unrecognized service type was found in the flowspec
-214701387980072B09An invalid or inconsistent flowspec was found in the QOS structure
-214701387880072B0AInvalid QOS provider-specific buffer
-214701387780072B0BAn invalid QOS filter style was used
-214701387680072B0CAn invalid QOS filter type was used
-214701387580072B0DAn incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR
-214701387480072B0EAn object with an invalid ObjectLength field was specified in the QOS provider-specific buffer
-214701387380072B0FAn incorrect number of flow descriptors was specified in the QOS structure
-214701387280072B10An unrecognized object was found in the QOS provider-specific buffer
-214701387180072B11An invalid policy object was found in the QOS provider-specific buffer
-214701387080072B12An invalid QOS flow descriptor was found in the flow descriptor list
-214701386980072B13An invalid or inconsistent flowspec was found in the QOS provider specific buffer
-214701386880072B14An invalid FILTERSPEC was found in the QOS provider-specific buffer
-214701386780072B15An invalid shape discard mode object was found in the QOS provider specific buffer
-214701386680072B16An invalid shaping rate object was found in the QOS provider-specific buffer
-214701386580072B17A reserved policy element was found in the QOS provider-specific buffer
-214701386480072B18No such host is known securely
-214701386380072B19Name based IPSEC policy could not be added
-2147011896800732C8The specified quick mode policy already exists
-2147011895800732C9The specified quick mode policy was not found
-2147011894800732CAThe specified quick mode policy is being used
-2147011893800732CBThe specified main mode policy already exists
-2147011892800732CCThe specified main mode policy was not found
-2147011891800732CDThe specified main mode policy is being used
-2147011890800732CEThe specified main mode filter already exists
-2147011889800732CFThe specified main mode filter was not found
-2147011888800732D0The specified transport mode filter already exists
-2147011887800732D1The specified transport mode filter does not exist
-2147011886800732D2The specified main mode authentication list exists
-2147011885800732D3The specified main mode authentication list was not found
-2147011884800732D4The specified main mode authentication list is being used
-2147011883800732D5The specified default main mode policy was not found
-2147011882800732D6The specified default main mode authentication list was not found
-2147011881800732D7The specified default quick mode policy was not found
-2147011880800732D8The specified tunnel mode filter exists
-2147011879800732D9The specified tunnel mode filter was not found
-2147011878800732DAThe Main Mode filter is pending deletion
-2147011877800732DBThe transport filter is pending deletion
-2147011876800732DCThe tunnel filter is pending deletion
-2147011875800732DDThe Main Mode policy is pending deletion
-2147011874800732DEThe Main Mode authentication bundle is pending deletion
-2147011873800732DFThe Quick Mode policy is pending deletion
-2147011872800732E0The Main Mode policy was successfully added
-2147011871800732E1The Quick Mode policy was successfully added
-2147011096800735E8ERROR_IPSEC_IKE_NEG_STATUS_BEGIN
-2147011095800735E9IKE authentication credentials are unacceptable
-2147011094800735EAIKE security attributes are unacceptable
-2147011093800735EBIKE Negotiation in progress
-2147011092800735ECGeneral processing error
-2147011091800735EDNegotiation timed out
-2147011090800735EEIKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store
-2147011089800735EFIKE SA deleted by peer before establishment completed
-2147011088800735F0IKE SA deleted before establishment completed
-2147011087800735F1Negotiation request sat in Queue too long
-2147011086800735F2Negotiation request sat in Queue too long
-2147011085800735F3Negotiation request sat in Queue too long
-2147011084800735F4Negotiation request sat in Queue too long
-2147011083800735F5No response from peer
-2147011082800735F6Negotiation took too long
-2147011081800735F7Negotiation took too long
-2147011079800735F9Certificate Revocation Check failed
-2147011078800735FAInvalid certificate key usage
-2147011077800735FBInvalid certificate type
-2147011076800735FCIKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key
-2147011075800735FDSimultaneous rekeys were detected
-2147011074800735FEFailure in Diffie-Hellman computation
-2147011073800735FFDon't know how to process critical payload
-214701107280073600Invalid header
-214701107180073601No policy configured
-214701107080073602Failed to verify signature
-214701106980073603Failed to authenticate using Kerberos
-214701106880073604Peer's certificate did not have a public key
-214701106780073605Error processing error payload
-214701106680073606Error processing SA payload
-214701106580073607Error processing Proposal payload
-214701106480073608Error processing Transform payload
-214701106380073609Error processing KE payload
-21470110628007360AError processing ID payload
-21470110618007360BError processing Cert payload
-21470110608007360CError processing Certificate Request payload
-21470110598007360DError processing Hash payload
-21470110588007360EError processing Signature payload
-21470110578007360FError processing Nonce payload
-214701105680073610Error processing Notify payload
-214701105580073611Error processing Delete Payload
-214701105480073612Error processing VendorId payload
-214701105380073613Invalid payload received
-214701105280073614Soft SA loaded
-214701105180073615Soft SA torn down
-214701105080073616Invalid cookie received
-214701104980073617Peer failed to send valid machine certificate
-214701104880073618Certification Revocation check of peer's certificate failed
-214701104780073619New policy invalidated SAs formed with old policy
-21470110468007361AThere is no available Main Mode IKE policy
-21470110458007361BFailed to enabled TCB privilege
-21470110448007361CFailed to load SECURITY.DLL
-21470110438007361DFailed to obtain security function table dispatch address from SSPI
-21470110428007361EFailed to query Kerberos package to obtain max token size
-21470110418007361FFailed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup
-214701104080073620Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes)
-214701103980073621Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters
-214701103880073622Given filter is invalid
-214701103780073623Memory allocation failed
-214701103680073624Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists
-214701103580073625Invalid policy
-214701103480073626Invalid DOI
-214701103380073627Invalid situation
-214701103280073628Diffie-Hellman failure
-214701103180073629Invalid Diffie-Hellman group
-21470110308007362AError encrypting payload
-21470110298007362BError decrypting payload
-21470110288007362CPolicy match error
-21470110278007362DUnsupported ID
-21470110268007362EHash verification failed
-21470110258007362FInvalid hash algorithm
-214701102480073630Invalid hash size
-214701102380073631Invalid encryption algorithm
-214701102280073632Invalid authentication algorithm
-214701102180073633Invalid certificate signature
-214701102080073634Load failed
-214701101980073635Deleted via RPC call
-214701101880073636Temporary state created to perform reinitialization. This is not a real failure
-214701101780073637The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine
-214701101680073638The recipient cannot handle version of IKE specified in the header
-214701101580073639Key length in certificate is too small for configured security requirements
-21470110148007363AMax number of established MM SAs to peer exceeded
-21470110138007363BIKE received a policy that disables negotiation
-21470110128007363CReached maximum quick mode limit for the main mode. New main mode will be started
-21470110118007363DMain mode SA lifetime expired or peer sent a main mode delete
-21470110108007363EMain mode SA assumed to be invalid because peer stopped responding
-21470110098007363FCertificate doesn't chain to a trusted root in IPsec policy
-214701100880073640Received unexpected message ID
-214701100780073641Received invalid authentication offers
-214701100680073642Sent DoS cookie notify to initiator
-214701100580073643IKE service is shutting down
-214701100480073644Could not verify binding between CGA address and certificate
-214701100380073645Error processing NatOA payload
-214701100280073646Parameters of the main mode are invalid for this quick mode
-214701100180073647Quick mode SA was expired by IPsec driver
-214701100080073648Too many dynamically added IKEEXT filters were detected
-214701099980073649ERROR_IPSEC_IKE_NEG_STATUS_END
-21470109988007364ANAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel
-21470109978007364BError in assigning inner IP address to initiator in tunnel mode
-21470109968007364CRequire configuration payload missing
-21470109958007364DA negotiation running as the security principle who issued the connection is in progress
-21470109948007364ESA was deleted due to IKEv1/AuthIP co-existence suppress check
-21470109938007364FIncoming SA request was dropped due to peer IP address rate limiting
-214701099280073650Peer does not support MOBIKE
-214701099180073651SA establishment is not authorized
-214701099080073652SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential
-214701098980073653SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard
-214701098880073654SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA
-214701098780073655ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END
-214701098680073656The SPI in the packet does not match a valid IPsec SA
-214701098580073657Packet was received on an IPsec SA whose lifetime has expired
-214701098480073658Packet was received on an IPsec SA that does not match the packet characteristics
-214701098380073659Packet sequence number replay check failed
-21470109828007365AIPsec header and/or trailer in the packet is invalid
-21470109818007365BIPsec integrity check failed
-21470109808007365CIPsec dropped a clear text packet
-21470109798007365DIPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign
-21470109788007365EIPsec dropped a packet due to DoS throttling
-214701097180073665IPsec DoS Protection matched an explicit block rule
-214701097080073666IPsec DoS Protection received an IPsec specific multicast packet which is not allowed
-214701096980073667IPsec DoS Protection received an incorrectly formatted packet
-214701096880073668IPsec DoS Protection failed to look up state
-214701096780073669IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached
-21470109668007366AIPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy
-21470109658007366BIPsec DoS Protection has not been enabled
-21470109648007366CIPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached
-2147010896800736B0The requested section was not present in the activation context
-2147010895800736B1The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail
-2147010894800736B2The application binding data format is invalid
-2147010893800736B3The referenced assembly is not installed on your system
-2147010892800736B4The manifest file does not begin with the required tag and format information
-2147010891800736B5The manifest file contains one or more syntax errors
-2147010890800736B6The application attempted to activate a disabled activation context
-2147010889800736B7The requested lookup key was not found in any active activation context
-2147010888800736B8A component version required by the application conflicts with another component version already active
-2147010887800736B9The type requested activation context section does not match the query API used
-2147010886800736BALack of system resources has required isolated activation to be disabled for the current thread of execution
-2147010885800736BBAn attempt to set the process default activation context failed because the process default activation context was already set
-2147010884800736BCThe encoding group identifier specified is not recognized
-2147010883800736BDThe encoding requested is not recognized
-2147010882800736BEThe manifest contains a reference to an invalid URI
-2147010881800736BFThe application manifest contains a reference to a dependent assembly which is not installed
-2147010880800736C0The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed
-2147010879800736C1The manifest contains an attribute for the assembly identity which is not valid
-2147010878800736C2The manifest is missing the required default namespace specification on the assembly element
-2147010877800736C3The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1"
-2147010876800736C4The private manifest probed has crossed a path with an unsupported reparse point
-2147010875800736C5Two or more components referenced directly or indirectly by the application manifest have files by the same name
-2147010874800736C6Two or more components referenced directly or indirectly by the application manifest have window classes with the same name
-2147010873800736C7Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs
-2147010872800736C8Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs
-2147010871800736C9Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs
-2147010870800736CATwo or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs
-2147010869800736CBTwo or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted
-2147010868800736CCA component's file does not match the verification information present in the component manifest
-2147010867800736CDThe policy manifest contains one or more syntax errors
-2147010866800736CEManifest Parse Error : A string literal was expected
-2147010865800736CFManifest Parse Error : Incorrect syntax was used in a comment
-2147010864800736D0Manifest Parse Error : A name was started with an invalid character
-2147010863800736D1Manifest Parse Error : A name contained an invalid character
-2147010862800736D2Manifest Parse Error : A string literal contained an invalid character
-2147010861800736D3Manifest Parse Error : Invalid syntax for an xml declaration
-2147010860800736D4Manifest Parse Error : An Invalid character was found in text content
-2147010859800736D5Manifest Parse Error : Required white space was missing
-2147010858800736D6Manifest Parse Error : The character '>' was expected
-2147010857800736D7Manifest Parse Error : A semi colon character was expected
-2147010856800736D8Manifest Parse Error : Unbalanced parentheses
-2147010855800736D9Manifest Parse Error : Internal error
-2147010854800736DAManifest Parse Error : Whitespace is not allowed at this location
-2147010853800736DBManifest Parse Error : End of file reached in invalid state for current encoding
-2147010852800736DCManifest Parse Error : Missing parenthesis
-2147010851800736DDManifest Parse Error : A single or double closing quote character (\' or \") is missing
-2147010850800736DEManifest Parse Error : Multiple colons are not allowed in a name
-2147010849800736DFManifest Parse Error : Invalid character for decimal digit
-2147010848800736E0Manifest Parse Error : Invalid character for hexadecimal digit
-2147010847800736E1Manifest Parse Error : Invalid unicode character value for this platform
-2147010846800736E2Manifest Parse Error : Expecting whitespace or '?'
-2147010845800736E3Manifest Parse Error : End tag was not expected at this location
-2147010844800736E4Manifest Parse Error : The following tags were not closed: %1
-2147010843800736E5Manifest Parse Error : Duplicate attribute
-2147010842800736E6Manifest Parse Error : Only one top level element is allowed in an XML document
-2147010841800736E7Manifest Parse Error : Invalid at the top level of the document
-2147010840800736E8Manifest Parse Error : Invalid xml declaration
-2147010839800736E9Manifest Parse Error : XML document must have a top level element
-2147010838800736EAManifest Parse Error : Unexpected end of file
-2147010837800736EBManifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset
-2147010836800736ECManifest Parse Error : Element was not closed
-2147010835800736EDManifest Parse Error : End element was missing the character '>'
-2147010834800736EEManifest Parse Error : A string literal was not closed
-2147010833800736EFManifest Parse Error : A comment was not closed
-2147010832800736F0Manifest Parse Error : A declaration was not closed
-2147010831800736F1Manifest Parse Error : A CDATA section was not closed
-2147010830800736F2Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml"
-2147010829800736F3Manifest Parse Error : System does not support the specified encoding
-2147010828800736F4Manifest Parse Error : Switch from current encoding to specified encoding not supported
-2147010827800736F5Manifest Parse Error : The name 'xml' is reserved and must be lower case
-2147010826800736F6Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'
-2147010825800736F7Manifest Parse Error : The standalone attribute cannot be used in external entities
-2147010824800736F8Manifest Parse Error : Invalid version number
-2147010823800736F9Manifest Parse Error : Missing equals sign between attribute and attribute value
-2147010822800736FAAssembly Protection Error : Unable to recover the specified assembly
-2147010821800736FBAssembly Protection Error : The public key for an assembly was too short to be allowed
-2147010820800736FCAssembly Protection Error : The catalog for an assembly is not valid
-2147010819800736FDAn HRESULT could not be translated to a corresponding Win32 error code
-2147010818800736FEAssembly Protection Error : The catalog for an assembly is missing
-2147010817800736FFThe supplied assembly identity is missing one or more attributes which must be present in this context
-214701081680073700The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names
-214701081580073701The referenced assembly could not be found
-214701081480073702The activation context activation stack for the running thread of execution is corrupt
-214701081380073703The application isolation metadata for this process or thread has become corrupt
-214701081280073704The activation context being deactivated is not the most recently activated one
-214701081180073705The activation context being deactivated is not active for the current thread of execution
-214701081080073706The activation context being deactivated has already been deactivated
-214701080980073707A component used by the isolation facility has requested to terminate the process
-214701080880073708A kernel mode component is releasing a reference on an activation context
-214701080780073709The activation context of system default assembly could not be generated
-21470108068007370AThe value of an attribute in an identity is not within the legal range
-21470108058007370BThe name of an attribute in an identity is not within the legal range
-21470108048007370CAn identity contains two definitions for the same attribute
-21470108038007370DThe identity string is malformed. This may be due to a trailing comma
-21470108028007370EA string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found
-21470108018007370FThe public key token does not correspond to the public key specified
-214701080080073710A substitution string had no mapping
-214701079980073711The component must be locked before making the request
-214701079880073712The component store has been corrupted
-214701079780073713An advanced installer failed during setup or servicing
-214701079680073714The character encoding in the XML declaration did not match the encoding used in the document
-214701079580073715The identities of the manifests are identical but their contents are different
-214701079480073716The component identities are different
-214701079380073717The assembly is not a deployment
-214701079280073718The file is not a part of the assembly
-214701079180073719The size of the manifest exceeds the maximum allowed
-21470107908007371AThe setting is not registered
-21470107898007371BOne or more required members of the transaction are not present
-21470107888007371CThe SMI primitive installer failed during setup or servicing
-21470107878007371DA generic command executable returned a result that indicates failure
-21470107868007371EA component is missing file verification information in its manifest
-21470107858007371FTwo or more components referenced directly or indirectly by the application manifest have the same WinRT ActivatableClass IDs
-214700989680073A98The specified channel path is invalid
-214700989580073A99The specified query is invalid
-214700989480073A9AThe publisher metadata cannot be found in the resource
-214700989380073A9BThe template for an event definition cannot be found in the resource (error = %1)
-214700989280073A9CThe specified publisher name is invalid
-214700989180073A9DThe event data raised by the publisher is not compatible with the event template definition in the publisher's manifest
-214700988980073A9FThe specified channel could not be found
-214700988880073AA0The specified XML text was not well-formed. See Extended Error for more details
-214700988780073AA1The events for a direct channel go directly to a log file and cannot be subscribed to
-214700988680073AA2Configuration error
-214700988580073AA3The query result is stale or invalid and must be recreated. This may be due to the log being cleared or rolling over after the query result was created
-214700988480073AA4The query result is currently at an invalid position
-214700988380073AA5Registered MSXML doesn't support validation
-214700988280073AA6An expression can only be followed by a change-of-scope operation if the expression evaluates to a node set and is not already part of another change-of-scope operation
-214700988180073AA7Cannot perform a step operation from a term that does not represent an element set
-214700988080073AA8Left-hand side arguments to binary operators must be either attributes
-214700987980073AA9A step operation must involve a node test or
-214700987880073AAAThis data type is currently unsupported
-214700987780073AABA syntax error occurred at position %1!d!
-214700987680073AACThis operator is unsupported by this implementation of the filter
-214700987580073AADAn unexpected token was encountered
-214700987480073AAEThe requested operation cannot be performed over an enabled direct channel. The channel must first be disabled
-214700987380073AAFChannel property %1 contains an invalid value. The value has an invalid type
-214700987280073AB0Publisher property %1 contains an invalid value. The value has an invalid type
-214700987180073AB1The channel failed to activate
-214700987080073AB2The XPath expression exceeded the supported complexity. Simplify the expression or split it into multiple expressions
-214700986980073AB3The message resource is present but the message was not found in the message table
-214700986880073AB4The message ID for the desired message could not be found
-214700986780073AB5The substitution string for insert index (%1) could not be found
-214700986680073AB6The description string for parameter reference (%1) could not be found
-214700986580073AB7The maximum number of replacements has been reached
-214700986480073AB8The event definition could not be found for event ID (%1)
-214700986380073AB9The locale specific resource for the desired message is not present
-214700986280073ABAThe resource is too old and is not supported
-214700986180073ABBThe resource is too new and is not supported
-214700986080073ABCThe channel at index %1!d! of the query can't be opened
-214700985980073ABDThe publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded
-214700985880073ABEAttempted to create a numeric type that is outside of its valid range
-214700981680073AE8The subscription fails to activate
-214700981580073AE9The log of the subscription is in disabled state
-214700981480073AEAWhen forwarding events from local machine to itself
-214700981380073AEBThe credential store that is used to save credentials is full
-214700981280073AECThe credential used by this subscription can't be found in credential store
-214700981180073AEDNo active channel is found for the query
-214700979680073AFCThe resource loader failed to find MUI file
-214700979580073AFDThe resource loader failed to load MUI file because the file fail to pass validation
-214700979480073AFEThe RC Manifest is corrupted with garbage data or unsupported version or missing required item
-214700979380073AFFThe RC Manifest has invalid culture name
-214700979280073B00The RC Manifest has invalid ultimatefallback name
-214700979180073B01The resource loader cache doesn't have loaded MUI entry
-214700979080073B02User stopped resource enumeration
-214700978980073B03UI language installation failed
-214700978880073B04Locale installation failed
-214700978680073B06A resource does not have default or neutral value
-214700978580073B07Invalid PRI config file
-214700978480073B08Invalid file type
-214700978380073B09Unknown qualifier
-214700978280073B0AInvalid qualifier value
-214700978180073B0BNo Candidate found
-214700978080073B0CThe ResourceMap or NamedResource has an item that does not have default or neutral resource
-214700977980073B0DInvalid ResourceCandidate type
-214700977880073B0EDuplicate Resource Map
-214700977780073B0FDuplicate Entry
-214700977680073B10Invalid Resource Identifier
-214700977580073B11Filepath too long
-214700977480073B12Unsupported directory type
-214700977080073B16Invalid PRI File
-214700976980073B17NamedResource Not Found
-214700976180073B1FResourceMap Not Found
-214700976080073B20Unsupported MRT profile type
-214700975980073B21Invalid qualifier operator
-214700975880073B22Unable to determine qualifier value or qualifier value has not been set
-214700975780073B23Automerge is enabled in the PRI file
-214700975680073B24Too many resources defined for package
-214700975580073B25Resource File can not be used for merge operation
-214700975480073B26Load/UnloadPriFiles cannot be used with resource packages
-214700975380073B27Resource Contexts may not be created on threads that do not have a CoreWindow
-214700975280073B28The singleton Resource Manager with different profile is already created
-214700975180073B29The system component cannot operate given API operation
-214700975080073B2AThe resource is a direct reference to a non-default resource candidate
-214700974980073B2BResource Map has been re-generated and the query string is not valid anymore
-214700974880073B2CThe PRI files to be merged have incompatible versions
-214700974780073B2DThe primary PRI files to be merged does not contain a schema
-214700974680073B2EUnable to load one of the PRI files to be merged
-214700974580073B2FUnable to add one of the PRI files to the merged file
-214700974480073B30Unable to create the merged PRI file
-214700974380073B31Packages for a PRI file merge must all be from the same package family
-214700974280073B32Packages for a PRI file merge must not include multiple main packages
-214700974180073B33Packages for a PRI file merge must not include bundle packages
-214700974080073B34Packages for a PRI file merge must include one main package
-214700973980073B35Packages for a PRI file merge must include at least one resource package
-214700973880073B36Invalid name supplied for a canonical merged PRI file
-214700973780073B37Unable to find the specified package
-214700973680073B38No default value for language was specified
-214700969680073B60The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0
-214700969580073B61The monitor's VCP Version (0xDF) VCP code returned an invalid version value
-214700969480073B62The monitor does not comply with the MCCS specification it claims to support
-214700969380073B63The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used
-214700969280073B64The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification
-214700969180073B65An internal Monitor Configuration API error occurred
-214700969080073B66The monitor returned an invalid monitor technology type. CRT
-214700968980073B67The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification
-214700964680073B92The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria
-214700959780073BC3The requested system device cannot be found
-214700959680073BC4Hash generation for the specified hash version and hash type is not enabled on the server
-214700959580073BC5The hash requested from the server is not available or no longer valid
-214700957580073BD9The secondary interrupt controller instance that manages the specified interrupt is not registered
-214700957480073BDAThe information supplied by the GPIO client driver is invalid
-214700957380073BDBThe version specified by the GPIO client driver is not supported
-214700957280073BDCThe registration packet supplied by the GPIO client driver is not valid
-214700957180073BDDThe requested operation is not supported for the specified handle
-214700957080073BDEThe requested connect mode conflicts with an existing mode on one or more of the specified pins
-214700956980073BDFThe interrupt requested to be unmasked is not masked
-214700949680073C28The requested run level switch cannot be completed successfully
-214700949580073C29The service has an invalid run level setting. The run level for a servicemust not be higher than the run level of its dependent services
-214700949480073C2AThe requested run level switch cannot be completed successfully sinceone or more services will not stop or restart within the specified timeout
-214700949380073C2BA run level switch agent did not respond within the specified timeout
-214700949280073C2CA run level switch is currently in progress
-214700949180073C2DOne or more services failed to start during the service startup phase of a run level switch
-214700939580073C8DThe task stop request cannot be completed immediately sincetask needs more time to shutdown
-214700929680073CF0Package could not be opened
-214700929580073CF1Package was not found
-214700929480073CF2Package data is invalid
-214700929380073CF3Package failed updates
-214700929280073CF4There is not enough disk space on your computer. Please free up some space and try again
-214700929180073CF5There was a problem downloading your product
-214700929080073CF6Package could not be registered
-214700928980073CF7Package could not be unregistered
-214700928880073CF8User cancelled the install request
-214700928780073CF9Install failed. Please contact your software vendor
-214700928680073CFARemoval failed. Please contact your software vendor
-214700928580073CFBThe provided package is already installed
-214700928480073CFCThe application cannot be started. Try reinstalling the application to fix the problem
-214700928380073CFDA Prerequisite for an install could not be satisfied
-214700928280073CFEThe package repository is corrupted
-214700928180073CFFTo install this application you need either a Windows developer license or a sideloading-enabled system
-214700928080073D00The application cannot be started because it is currently updating
-214700927980073D01The package deployment operation is blocked by policy. Please contact your system administrator
-214700927880073D02The package could not be installed because resources it modifies are currently in use
-214700927780073D03The package could not be recovered because necessary data for recovery have been corrupted
-214700927680073D04The signature is invalid. To register in developer mode
-214700927580073D05An error occurred while deleting the package's previously existing application data
-214700927480073D06The package could not be installed because a higher version of this package is already installed
-214700927380073D07An error in a system binary was detected. Try refreshing the PC to fix the problem
-214700927280073D08A corrupted CLR NGEN binary was detected on the system
-214700927180073D09The operation could not be resumed because necessary data for recovery have been corrupted
-214700927080073D0AThe package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again
-214700926980073D0BPackage move failed
-214700926880073D0CThe deployment operation failed because the volume is not empty
-214700926780073D0DThe deployment operation failed because the volume is offline. For a package update
-214700926680073D0EThe deployment operation failed because the specified volume is corrupt
-214700926580073D0FThe deployment operation failed because the specified application needs to be registered first
-214700926480073D10The deployment operation failed because the package targets the wrong processor architecture
-214700926380073D11You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again
-214700926280073D12A main app package is required to install this optional package. Install the main package first and try again
-214700926180073D13This app package type is not supported on this filesystem
-214700926080073D14Package move operation is blocked until the application has finished streaming
-214700925980073D15A main or another optional app package has the same application ID as this optional package. Change the application ID for the optional package to avoid conflicts
-214700925880073D16This staging session has been held to allow another staging operation to be prioritized
-214700925780073D17A related set cannot be updated because the updated set is invalid. All packages in the related set must be updated at the same time
-214700925680073D18An optional package with a FullTrust entry point requires the main package to have the runFullTrust capability
-214700925580073D19An error occurred because a user was logged off
-214700925480073D1AAn optional package provision requires the dependency main package to also be provisioned
-214700925380073D1BThe packages failed the SmartScreen reputation check
-214700925280073D1CThe SmartScreen reputation check operation timed out
-214700925180073D1DThe current deployment option is not supported
-214700925080073D1EActivation is blocked due to the .appinstaller update settings for this app
-214700924980073D1FRemote drives are not supported; use \\server\share to register a remote package
-214700924880073D20Failed to process and write downloaded APPX package data to disk
-214700924780073D21The deployment operation was blocked due to a per-package-family policy restricting deployments on a non-system volume. Per policy
-214700924680073D22The deployment operation was blocked due to a machine-wide policy restricting deployments on a non-system volume. Per policy
-214700924580073D23The deployment operation was blocked because Special profile deployment is not allowed. Please try logging into an account that is not a Special profile. You can try logging out and logging back into the current account
-214700924480073D24The deployment operation failed due to a conflicting package's mutable package directory. To install this package remove the existing package with the conflicting mutable package directory
-214700924380073D25The package installation failed because a singleton resource was specified and another user with that package installed is logged in. Please make sure that all active users with the package installed are logged out and retry installation
-214700924280073D26The package installation failed because a different version of the service is installed. Try installing a newer version of the package
-214700924180073D27The package installation failed because a version of the service exists outside of APPX packaging. Please contact your software vendor
-214700924080073D28The package installation failed because administrator privileges are required. Please contact an administrator to install this package
-214700923980073D29The package deployment failed because the operation would have redirected to default account
-214700923880073D2AThe package deployment failed because the package requires a capability to natively target this host
-214700923780073D2BThe package deployment failed because its content is not valid for an unsigned package
-214700923680073D2CThe package deployment failed because its publisher is not in the unsigned namespace
-214700923580073D2DThe package deployment failed because its publisher is not in the signed namespace
-214700923480073D2EThe package deployment failed because its publisher is not in the signed namespace
-214700923380073D2FA host runtime dependency resolving to a package with full trust content requires the main package to have the runFullTrust capability
-214700919680073D54The process has no package identity
-214700919580073D55The package runtime information is corrupted
-214700919480073D56The package identity is corrupted
-214700919380073D57The process has no application identity
-214700919280073D58One or more AppModel Runtime group policy values could not be read. Please contact your system administrator with the contents of your AppModel Runtime event log
-214700919180073D59One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log
-214700919080073D5AThe package is currently not available
-214700918980073D5BThe package does not have a mutable directory
-214700909680073DB8Loading the state store failed
-214700909580073DB9Retrieving the state version for the application failed
-214700909480073DBASetting the state version for the application failed
-214700909380073DBBResetting the structured state of the application failed
-214700909280073DBCState Manager failed to open the container
-214700909180073DBDState Manager failed to create the container
-214700909080073DBEState Manager failed to delete the container
-214700908980073DBFState Manager failed to read the setting
-214700908880073DC0State Manager failed to write the setting
-214700908780073DC1State Manager failed to delete the setting
-214700908680073DC2State Manager failed to query the setting
-214700908580073DC3State Manager failed to read the composite setting
-214700908480073DC4State Manager failed to write the composite setting
-214700908380073DC5State Manager failed to enumerate the containers
-214700908280073DC6State Manager failed to enumerate the settings
-214700908180073DC7The size of the state manager composite setting value has exceeded the limit
-214700908080073DC8The size of the state manager setting value has exceeded the limit
-214700907980073DC9The length of the state manager setting name has exceeded the limit
-214700907880073DCAThe length of the state manager container name has exceeded the limit
-214700905580073DE1This API cannot be used in the context of the caller's application type
-214700903580073DF5This PC does not have a valid license for the application or product
-214700903480073DF6The authenticated user does not have a valid license for the application or product
-214700903380073DF7The commerce transaction associated with this license is still pending verification
-214700903280073DF8The license has been revoked for this user
-214695935980080001Attempt to create a class object failed
-214695935880080002OLE service could not bind object
-214695935780080003RPC communication failed with OLE service
-214695935680080004Bad path to object
-214695935580080005Server execution failed
-214695935480080006OLE service could not communicate with the object server
-214695935380080007Moniker path could not be normalized
-214695935280080008Object server is stopping when OLE service contacts it
-214695935180080009An invalid root block pointer was specified
-214695934480080010An allocation chain contained an invalid link pointer
-214695934380080011The requested allocation size was too large
-214695933980080015The activation requires a display name to be present under the CLSID key
-214695933880080016The activation requires that the RunAs value for the application is Activate As Activator
-214695933780080017The class is not configured to support Elevated activation
-214695884880080200Appx packaging API has encountered an internal error
-214695884780080201The file is not a valid Appx package because its contents are interleaved
-214695884680080202The file is not a valid Appx package because it contains OPC relationships
-214695884580080203The file is not a valid Appx package because it is missing a manifest or block map
-214695884480080204The Appx package's manifest is invalid
-214695884380080205The Appx package's block map is invalid
-214695884280080206The Appx package's content cannot be read because it is corrupt
-214695884180080207The computed hash value of the block does not match the one stored in the block map
-214695884080080208The requested byte range is over 4GB when translated to byte range of blocks
-214695883980080209The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data
-21469588388008020AThe APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data
-21469588378008020BThe Appx package's content group map is invalid
-21469588368008020CThe .appinstaller file is invalid
-21469588358008020DThe baseline package version in delta package does not match the version in the baseline package to be updated
-21469588348008020EThe delta package is missing a file from the updated package
-21469588338008020FThe delta package is invalid
-214695883280080210The delta appended package is not allowed for the current operation
-214695883180080211The packaging layout file is invalid
-214695883080080212The packageSignConfig file is invalid
-214695882980080213The resources.pri file is not allowed when there are no resource elements in the package manifest
-214695882880080214The compression state of file in baseline and updated package does not match
-214695882780080215Non appx extensions are not allowed for payload packages targeting older platforms
-214695882680080216The encryptionExclusionFileList file is invalid
-214695859280080300The background task activation is spurious
-214689382380090001Bad UID
-214689382280090002Bad Hash
-214689382180090003Bad Key
-214689382080090004Bad Length
-214689381980090005Bad Data
-214689381880090006Invalid Signature
-214689381780090007Bad Version of provider
-214689381680090008Invalid algorithm specified
-214689381580090009Invalid flags specified
-21468938148009000AInvalid type specified
-21468938138009000BKey not valid for use in specified state
-21468938128009000CHash not valid for use in specified state
-21468938118009000DKey does not exist
-21468938108009000EInsufficient memory available for the operation
-21468938098009000FObject already exists
-214689380880090010Access denied
-214689380780090011Object was not found
-214689380680090012Data already encrypted
-214689380580090013Invalid provider specified
-214689380480090014Invalid provider type specified
-214689380380090015Provider's public key is invalid
-214689380280090016Keyset does not exist
-214689380180090017Provider type not defined
-214689380080090018Provider type as registered is invalid
-214689379980090019The keyset is not defined
-21468937988009001AKeyset as registered is invalid
-21468937978009001BProvider type does not match registered value
-21468937968009001CThe digital signature file is corrupt
-21468937958009001DProvider DLL failed to initialize correctly
-21468937948009001EProvider DLL could not be found
-21468937938009001FThe Keyset parameter is invalid
-214689379280090020An internal error occurred
-214689379180090021A base error occurred
-214689379080090022Provider could not perform the action since the context was acquired as silent
-214689378980090023The security token does not have storage space available for an additional container
-214689378880090024The profile for the user is a temporary profile
-214689378780090025The key parameters could not be set because the CSP uses fixed parameters
-214689378680090026The supplied handle is invalid
-214689378580090027The parameter is incorrect
-214689378480090028The buffer supplied to a function was too small
-214689378380090029The requested operation is not supported
-21468937828009002ANo more data is available
-21468937818009002BThe supplied buffers overlap incorrectly
-21468937808009002CThe specified data could not be decrypted
-21468937798009002DAn internal consistency check failed
-21468937788009002EThis operation requires input from the user
-21468937778009002FThe cryptographic provider does not support HMAC
-214689377680090030The device that is required by this cryptographic provider is not ready for use
-214689377580090031The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider
-214689377480090032The validation of the provided data failed the integrity or signature validation
-214689377380090033Incorrect password
-214689377280090034Encryption failed
-214689377180090035The device that is required by this cryptographic provider is not found on this platform
-214689377080090036The action was cancelled by the user
-214689376980090037The password is no longer valid and must be changed
-214689376880090038The operation cannot be completed from Terminal Server client sessions
-214689305680090300Not enough memory is available to complete this request
-214689305580090301The handle specified is invalid
-214689305480090302The function requested is not supported
-214689305380090303The specified target is unknown or unreachable
-214689305280090304The Local Security Authority cannot be contacted
-214689305180090305The requested security package does not exist
-214689305080090306The caller is not the owner of the desired credentials
-214689304980090307The security package failed to initialize
-214689304880090308The token supplied to the function is invalid
-214689304780090309The security package is not able to marshall the logon buffer
-21468930468009030AThe per-message Quality of Protection is not supported by the security package
-21468930458009030BThe security context does not allow impersonation of the client
-21468930448009030CThe logon attempt failed
-21468930438009030DThe credentials supplied to the package were not recognized
-21468930428009030ENo credentials are available in the security package
-21468930418009030FThe message or signature supplied for verification has been altered
-214689304080090310The message supplied for verification is out of sequence
-214689303980090311No authority could be contacted for authentication
-214689303480090316The requested security package does not exist
-214689303380090317The context has expired and can no longer be used
-214689303280090318The supplied message is incomplete. The signature was not verified
-214689302480090320The credentials supplied were not complete
-214689302380090321The buffers supplied to a function was too small
-214689302280090322The target principal name is incorrect
-214689302080090324The clocks on the client and server machines are skewed
-214689301980090325The certificate chain was issued by an authority that is not trusted
-214689301880090326The message received was unexpected or badly formatted
-214689301780090327An unknown error occurred while processing the certificate
-214689301680090328The received certificate has expired
-214689301580090329The specified data could not be encrypted
-214689300880090330The specified data could not be decrypted
-214689300780090331The client and server cannot communicate
-214689300680090332The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation)
-214689300580090333A security context was deleted before the context was completed. This is considered a logon failure
-214689300480090334The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply
-214689300380090335Unable to accomplish the requested task because the local machine does not have any IP addresses
-214689300280090336The supplied credential handle does not match the credential associated with the security context
-214689300180090337The crypto system or checksum function is invalid because a required function is unavailable
-214689300080090338The number of maximum ticket referrals has been exceeded
-214689299980090339The local machine must be a Kerberos KDC (domain controller) and it is not
-21468929988009033AThe other end of the security negotiation is requires strong crypto but it is not supported on the local machine
-21468929978009033BThe KDC reply contained more than one principal name
-21468929968009033CExpected to find PA data for a hint of what etype to use
-21468929958009033DThe client certificate does not contain a valid UPN
-21468929948009033ESmartcard logon is required and was not used
-21468929938009033FA system shutdown is in progress
-214689299280090340An invalid request was sent to the KDC
-214689299180090341The KDC was unable to generate a referral for the service requested
-214689299080090342The encryption type requested is not supported by the KDC
-214689298980090343An unsupported preauthentication mechanism was presented to the Kerberos package
-214689298780090345The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation
-214689298680090346Client's supplied SSPI channel bindings were incorrect
-214689298580090347The received certificate was mapped to multiple accounts
-214689298480090348SEC_E_NO_KERB_KEY
-214689298380090349The certificate is not valid for the requested usage
-214689297680090350The system cannot contact a domain controller to service the authentication request. Please try again later
-214689297580090351The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log
-214689297480090352An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator
-214689297380090353The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator
-214689297280090354The smartcard certificate used for authentication was not trusted. Please contact your system administrator
-214689297180090355The smartcard certificate used for authentication has expired. Please contact your system administrator
-214689297080090356The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user
-214689296980090357An 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
-214689296880090358The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator
-214689296780090359An 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
-21468929668009035AThe domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log
-21468929658009035BThe domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log
-21468929638009035DOne or more of the parameters passed to the function was invalid
-21468929628009035EClient policy does not allow credential delegation to target server
-21468929618009035FClient policy does not allow credential delegation to target server with NLTM only authentication
-214689295980090361The required security context does not exist
-214689295880090362The PKU2U protocol encountered an error while attempting to utilize the associated certificates
-214689295780090363The identity of the server computer could not be verified
-214689295580090365Only https scheme is allowed
-214689295380090367No common application protocol exists between the client and the server. Application protocol negotiation failed
-214689295180090369You can't sign in with a user ID in this format. Try using your email address instead
-21468929508009036AThe buffer supplied by the SSPI caller to receive generic extensions is too small
-21468929498009036BNot enough secbuffers were supplied to generate a token
-214688972780091001An error occurred while performing an operation on a cryptographic message
-214688972680091002Unknown cryptographic algorithm
-214688972580091003The object identifier is poorly formatted
-214688972480091004Invalid cryptographic message type
-214688972380091005Unexpected cryptographic message encoding
-214688972280091006The cryptographic message does not contain an expected authenticated attribute
-214688972180091007The hash value is not correct
-214688972080091008The index value is not valid
-214688971980091009The content of the cryptographic message has already been decrypted
-21468897188009100AThe content of the cryptographic message has not been decrypted yet
-21468897178009100BThe enveloped-data message does not contain the specified recipient
-21468897168009100CInvalid control type
-21468897158009100DInvalid issuer and/or serial number
-21468897148009100ECannot find the original signer
-21468897138009100FThe cryptographic message does not contain all of the requested attributes
-214688971280091010The streamed cryptographic message is not ready to return data
-214688971180091011The streamed cryptographic message requires more data to complete the decode operation
-214688563180092001The length specified for the output data was insufficient
-214688563080092002An error occurred during encode or decode operation
-214688562980092003An error occurred while reading or writing to a file
-214688562880092004Cannot find object or property
-214688562780092005The object or property already exists
-214688562680092006No provider was specified for the store or object
-214688562580092007The specified certificate is self signed
-214688562480092008The previous certificate or CRL context was deleted
-214688562380092009Cannot find the requested object
-21468856228009200AThe certificate does not have a property that references a private key
-21468856218009200BCannot find the certificate and private key for decryption
-21468856208009200CCannot find the certificate and private key to use for decryption
-21468856198009200DNot a cryptographic message or the cryptographic message is not formatted correctly
-21468856188009200EThe signed cryptographic message does not have a signer for the specified signer index
-21468856178009200FFinal closure is pending until additional frees or closes
-214688561680092010The certificate is revoked
-214688561580092011No Dll or exported function was found to verify revocation
-214688561480092012The revocation function was unable to check revocation for the certificate
-214688561380092013The revocation function was unable to check revocation because the revocation server was offline
-214688561280092014The certificate is not in the revocation server's database
-214688560080092020The string contains a non-numeric character
-214688559980092021The string contains a non-printable character
-214688559880092022The string contains a character not in the 7 bit ASCII character set
-214688559780092023The string contains an invalid X500 name attribute key
-214688559680092024The dwValueType for the CERT_NAME_VALUE is not one of the character strings. Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_RDN_OCTET_STRING
-214688559580092025The Put operation cannot continue. The file needs to be resized. However
-214688559480092026The cryptographic operation failed due to a local security option setting
-214688559380092027No DLL or exported function was found to verify subject usage
-214688559280092028The called function was unable to do a usage check on the subject
-214688559180092029Since the server was offline
-21468855908009202AThe subject was not found in a Certificate Trust List (CTL)
-21468855898009202BNone of the signers of the cryptographic message or certificate trust list is trusted
-21468855888009202CThe public key's algorithm parameters are missing
-21468855878009202DAn object could not be located using the object locator infrastructure with the given name
-214688153680093000OSS Certificate encode/decode error code baseSee asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR
-214688153580093001OSS ASN.1 Error: Output Buffer is too small
-214688153480093002OSS ASN.1 Error: Signed integer is encoded as a unsigned integer
-214688153380093003OSS ASN.1 Error: Unknown ASN.1 data type
-214688153280093004OSS ASN.1 Error: Output buffer is too small
-214688153180093005OSS ASN.1 Error: Invalid data
-214688153080093006OSS ASN.1 Error: Invalid argument
-214688152980093007OSS ASN.1 Error: Encode/Decode version mismatch
-214688152880093008OSS ASN.1 Error: Out of memory
-214688152780093009OSS ASN.1 Error: Encode/Decode Error
-21468815268009300AOSS ASN.1 Error: Internal Error
-21468815258009300BOSS ASN.1 Error: Invalid data
-21468815248009300COSS ASN.1 Error: Invalid data
-21468815238009300DOSS ASN.1 Error: Unsupported BER indefinite-length encoding
-21468815228009300EOSS ASN.1 Error: Access violation
-21468815218009300FOSS ASN.1 Error: Invalid data
-214688152080093010OSS ASN.1 Error: Invalid data
-214688151980093011OSS ASN.1 Error: Invalid data
-214688151880093012OSS ASN.1 Error: Internal Error
-214688151780093013OSS ASN.1 Error: Multi-threading conflict
-214688151680093014OSS ASN.1 Error: Invalid data
-214688151580093015OSS ASN.1 Error: Invalid data
-214688151480093016OSS ASN.1 Error: Invalid data
-214688151380093017OSS ASN.1 Error: Encode/Decode function not implemented
-214688151280093018OSS ASN.1 Error: Trace file error
-214688151180093019OSS ASN.1 Error: Function not implemented
-21468815108009301AOSS ASN.1 Error: Program link error
-21468815098009301BOSS ASN.1 Error: Trace file error
-21468815088009301COSS ASN.1 Error: Trace file error
-21468815078009301DOSS ASN.1 Error: Invalid data
-21468815068009301EOSS ASN.1 Error: Invalid data
-21468815058009301FOSS ASN.1 Error: Program link error
-214688150480093020OSS ASN.1 Error: Program link error
-214688150380093021OSS ASN.1 Error: Program link error
-214688150280093022OSS ASN.1 Error: Program link error
-214688150180093023OSS ASN.1 Error: Program link error
-214688150080093024OSS ASN.1 Error: Program link error
-214688149980093025OSS ASN.1 Error: Program link error
-214688149880093026OSS ASN.1 Error: Program link error
-214688149780093027OSS ASN.1 Error: Program link error
-214688149680093028OSS ASN.1 Error: Program link error
-214688149580093029OSS ASN.1 Error: Program link error
-21468814948009302AOSS ASN.1 Error: Program link error
-21468814938009302BOSS ASN.1 Error: Program link error
-21468814928009302COSS ASN.1 Error: Program link error
-21468814918009302DOSS ASN.1 Error: System resource error
-21468814908009302EOSS ASN.1 Error: Trace file error
-214688128080093100ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR
-214688127980093101ASN1 internal encode or decode error
-214688127880093102ASN1 unexpected end of data
-214688127780093103ASN1 corrupted data
-214688127680093104ASN1 value too large
-214688127580093105ASN1 constraint violated
-214688127480093106ASN1 out of memory
-214688127380093107ASN1 buffer overflow
-214688127280093108ASN1 function not supported for this PDU
-214688127180093109ASN1 bad arguments to function call
-21468812708009310AASN1 bad real value
-21468812698009310BASN1 bad tag value met
-21468812688009310CASN1 bad choice value
-21468812678009310DASN1 bad encoding rule
-21468812668009310EASN1 bad unicode (UTF8)
-214688122980093133ASN1 bad PDU type
-214688122880093134ASN1 not yet implemented
-214688102380093201ASN1 skipped unknown extension(s)
-214688102280093202ASN1 end of data expected
-214687743980094001The request subject name is invalid or too long
-214687743880094002The request does not exist
-214687743780094003The request's current status does not allow this operation
-214687743680094004The requested property value is empty
-214687743580094005The certification authority's certificate contains invalid data
-214687743480094006Certificate service has been suspended for a database restore operation
-214687743380094007The certificate contains an encoded length that is potentially incompatible with older enrollment software
-214687743280094008The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation
-214687743180094009The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester
-21468774308009400ACannot archive private key. The certification authority is not configured for key archival
-21468774298009400BCannot archive private key. The certification authority could not verify one or more key recovery certificates
-21468774288009400CThe request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature
-21468774278009400DAt least one security principal must have the permission to manage this CA
-21468774268009400EThe request contains an invalid renewal certificate attribute
-21468774258009400FAn attempt was made to open a Certification Authority database session
-214687742480094010A memory reference caused a data alignment fault
-214687742380094011The permissions on this certification authority do not allow the current user to enroll for certificates
-214687742280094012The permissions on the certificate template do not allow the current user to enroll for this type of certificate
-214687742180094013The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access
-214687742080094014The request was denied by a certificate manager or CA administrator
-214687741980094015An enrollment policy server cannot be located
-214687741880094016A signature algorithm or public key length does not meet the system's minimum required strength
-214687741780094017Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation
-214687741680094018No encryption certificate was specified
-214687539280094800The requested certificate template is not supported by this CA
-214687539180094801The request contains no certificate template information
-214687539080094802The request contains conflicting template information
-214687538980094803The request is missing a required Subject Alternate name extension
-214687538880094804The request is missing a required private key for archival by the server
-214687538780094805The request is missing a required SMIME capabilities extension
-214687538680094806The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request
-214687538580094807The request template version is newer than the supported template version
-214687538480094808The template is missing a required signature policy attribute
-214687538380094809The request is missing required signature policy information
-21468753828009480AThe request is missing one or more required signatures
-21468753818009480BOne or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures
-21468753808009480CThe request is missing one or more required signature issuance policies
-21468753798009480DThe UPN is unavailable and cannot be added to the Subject Alternate name
-21468753788009480EThe Active Directory GUID is unavailable and cannot be added to the Subject Alternate name
-21468753778009480FThe DNS name is unavailable and cannot be added to the Subject Alternate name
-214687537680094810The request includes a private key for archival by the server
-214687537580094811The public key does not meet the minimum size required by the specified certificate template
-214687537480094812The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name
-214687537380094813One or more certificate templates to be enabled on this certification authority could not be found
-214687537280094814The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed
-214687537180094815The certificate template requires too many RA signatures. Only one RA signature is allowed
-214687537080094816The certificate template requires renewal with the same public key
-214687536980094817The certification authority cannot interpret or verify the endorsement key information supplied in the request
-214687536880094818The certification authority cannot validate the Attestation Identity Key Id Binding
-214687536780094819The certification authority cannot validate the private key attestation data
-21468753668009481AThe request does not support private key attestation as defined in the certificate template
-21468753658009481BThe request public key is not consistent with the private key attestation data
-21468753648009481CThe private key attestation challenge cannot be validated because the encryption certificate has expired
-21468753638009481DThe client's response could not be validated. It is either unexpected or incorrect
-21468753628009481EA valid Request ID was not detected in the request attributes
-21468753618009481FThe request is not consistent with the previously generated precertificate
-214687536080094820The request is locked against edits until a response is received from the client
-214687334480095000The key is not exportable
-214687334380095001You cannot add the root CA certificate into your local store
-214687334280095002The key archival hash attribute was not found in the response
-214687334180095003An unexpected key archival hash attribute was found in the response
-214687334080095004There is a key archival hash mismatch between the request and the response
-214687333980095005Signing certificate cannot include SMIME extension
-214686924780096001A system-level error occurred while verifying trust
-214686924680096002The certificate for the signer of the message is invalid or not found
-214686924580096003One of the counter signatures was invalid
-214686924480096004The signature of the certificate cannot be verified
-214686924380096005The timestamp signature and/or certificate could not be verified or is malformed
-214686923280096010The digital signature of the object did not verify
-214686923180096011The digital signature of the object is malformed. For technical detail
-214686922380096019A certificate's basic constraint extension has not been observed
-21468692188009601EThe certificate does not meet or contain the Authenticode(tm) financial extensions
-214686515180097001Tried to reference a part of the file outside the proper range
-214686515080097002Could not retrieve an object from the file
-214686514980097003Could not find the head table in the file
-214686514880097004The magic number in the head table is incorrect
-214686514780097005The offset table has incorrect values
-214686514680097006Duplicate table tags or tags out of alphabetical order
-214686514580097007A table does not start on a long word boundary
-214686514480097008First table does not appear after header information
-214686514380097009Two or more tables overlap
-21468651428009700AToo many pad bytes between tables or pad bytes are not 0
-21468651418009700BFile is too small to contain the last table
-21468651408009700CA table checksum is incorrect
-21468651398009700DThe file checksum is incorrect
-214686513680097010The signature does not have the correct attributes for the policy
-214686513580097011The file did not pass the hints check
-214686513480097012The file is not an OpenType file
-214686513380097013Failed on a file operation (open
-214686513280097014A call to a CryptoAPI function failed
-214686513180097015There is a bad version number in the file
-214686513080097016The structure of the DSIG table is incorrect
-214686512980097017A check failed in a partially constant table
-214686512880097018Some kind of structural error
-214686512780097019The requested credential requires confirmation
-2146762751800B0001Unknown trust provider
-2146762750800B0002The trust verification action specified is not supported by the specified trust provider
-2146762749800B0003The form specified for the subject is not one supported or known by the specified trust provider
-2146762748800B0004The subject is not trusted for the specified action
-2146762747800B0005Error due to problem in ASN.1 encoding process
-2146762746800B0006Error due to problem in ASN.1 decoding process
-2146762745800B0007Reading / writing Extensions where Attributes are appropriate
-2146762744800B0008Unspecified cryptographic failure
-2146762743800B0009The size of the data could not be determined
-2146762742800B000AThe size of the indefinite-sized data could not be determined
-2146762741800B000BThis object does not read and write self-sizing data
-2146762496800B0100No signature was present in the subject
-2146762495800B0101A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file
-2146762494800B0102The validity periods of the certification chain do not nest correctly
-2146762493800B0103A certificate that can only be used as an end-entity is being used as a CA or vice versa
-2146762492800B0104A path length constraint in the certification chain has been violated
-2146762491800B0105A certificate contains an unknown extension that is marked 'critical'
-2146762490800B0106A certificate being used for a purpose other than the ones specified by its CA
-2146762489800B0107A parent of a given certificate in fact did not issue that child certificate
-2146762488800B0108A certificate is missing or has an empty value for an important field
-2146762487800B0109A certificate chain processed
-2146762486800B010AA certificate chain could not be built to a trusted root authority
-2146762485800B010BGeneric trust failure
-2146762484800B010CA certificate was explicitly revoked by its issuer
-2146762483800B010DThe certification path terminates with the test root which is not trusted with the current policy settings
-2146762482800B010EThe revocation process could not continue - the certificate(s) could not be checked
-2146762481800B010FThe certificate's CN name does not match the passed value
-2146762480800B0110The certificate is not valid for the requested usage
-2146762479800B0111The certificate was explicitly marked as untrusted by the user
-2146762478800B0112A certification chain processed correctly
-2146762477800B0113The certificate has invalid policy
-2146762476800B0114The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded
-2146697214800C0002The URL is invalid
-2146697213800C0003No Internet session has been established
-2146697212800C0004Unable to connect to the target server
-2146697211800C0005The system cannot locate the resource specified
-2146697210800C0006The system cannot locate the object specified
-2146697209800C0007No data is available for the requested resource
-2146697208800C0008The download of the specified resource has failed
-2146697207800C0009Authentication is required to access this resource
-2146697206800C000AThe server could not recognize the provided mime type
-2146697205800C000BThe operation was timed out
-2146697204800C000CThe server did not understand the request
-2146697203800C000DThe specified protocol is unknown
-2146697202800C000EA security problem occurred
-2146697201800C000FThe system could not load the persisted data
-2146697200800C0010Unable to instantiate the object
-2146697196800C0014A redirection problem occurred
-2146697195800C0015The requested resource is a directory
-2146697191800C0019Security certificate required to access this resource is invalid
-2146500608800F0000A non-empty line was encountered in the INF before the start of a section
-2146500607800F0001A section name marker in the INF is not complete
-2146500606800F0002An INF section was encountered whose name exceeds the maximum section name length
-2146500605800F0003The syntax of the INF is invalid
-2146500352800F0100The style of the INF is different than what was requested
-2146500351800F0101The required section was not found in the INF
-2146500350800F0102The required line was not found in the INF
-2146500349800F0103The files affected by the installation of this file queue have not been backed up for uninstall
-2146500096800F0200The INF or the device information set or element does not have an associated install class
-2146500095800F0201The INF or the device information set or element does not match the specified install class
-2146500094800F0202An existing device was found that is a duplicate of the device being manually installed
-2146500093800F0203There is no driver selected for the device information set or element
-2146500092800F0204The requested device registry key does not exist
-2146500091800F0205The device instance name is invalid
-2146500090800F0206The install class is not present or is invalid
-2146500089800F0207The device instance cannot be created because it already exists
-2146500088800F0208The operation cannot be performed on a device information element that has not been registered
-2146500087800F0209The device property code is invalid
-2146500086800F020AThe INF from which a driver list is to be built does not exist
-2146500085800F020BThe device instance does not exist in the hardware tree
-2146500084800F020CThe icon representing this install class cannot be loaded
-2146500083800F020DThe class installer registry entry is invalid
-2146500082800F020EThe class installer has indicated that the default action should be performed for this installation request
-2146500081800F020FThe operation does not require any files to be copied
-2146500080800F0210The specified hardware profile does not exist
-2146500079800F0211There is no device information element currently selected for this device information set
-2146500078800F0212The operation cannot be performed because the device information set is locked
-2146500077800F0213The operation cannot be performed because the device information element is locked
-2146500076800F0214The specified path does not contain any applicable device INFs
-2146500075800F0215No class installer parameters have been set for the device information set or element
-2146500074800F0216The operation cannot be performed because the file queue is locked
-2146500073800F0217A service installation section in this INF is invalid
-2146500072800F0218There is no class driver list for the device information element
-2146500071800F0219The installation failed because a function driver was not specified for this device instance
-2146500070800F021AThere is presently no default device interface designated for this interface class
-2146500069800F021BThe operation cannot be performed because the device interface is currently active
-2146500068800F021CThe operation cannot be performed because the device interface has been removed from the system
-2146500067800F021DAn interface installation section in this INF is invalid
-2146500066800F021EThis interface class does not exist in the system
-2146500065800F021FThe reference string supplied for this interface device is invalid
-2146500064800F0220The specified machine name does not conform to UNC naming conventions
-2146500063800F0221A general remote communication error occurred
-2146500062800F0222The machine selected for remote communication is not available at this time
-2146500061800F0223The Plug and Play service is not available on the remote machine
-2146500060800F0224The property page provider registry entry is invalid
-2146500059800F0225The requested device interface is not present in the system
-2146500058800F0226The device's co-installer has additional work to perform after installation is complete
-2146500057800F0227The device's co-installer is invalid
-2146500056800F0228There are no compatible drivers for this device
-2146500055800F0229There is no icon that represents this device or device type
-2146500054800F022AA logical configuration specified in this INF is invalid
-2146500053800F022BThe class installer has denied the request to install or upgrade this device
-2146500052800F022COne of the filter drivers installed for this device is invalid
-2146500051800F022DThe driver selected for this device does not support this version of Windows
-2146500050800F022EThe driver selected for this device does not support Windows
-2146500049800F022FThe third-party INF does not contain digital signature information
-2146500048800F0230An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms
-2146500047800F0231The device cannot be disabled
-2146500046800F0232The device could not be dynamically removed
-2146500045800F0233Cannot copy to specified target
-2146500044800F0234Driver is not intended for this platform
-2146500043800F0235Operation not allowed in WOW64
-2146500042800F0236The operation involving unsigned file copying was rolled back
-2146500041800F0237An INF was copied into the Windows INF directory in an improper manner
-2146500040800F0238The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product
-2146500039800F0239An unknown exception was encountered
-2146500038800F023AA problem was encountered when accessing the Plug and Play registry database
-2146500037800F023BThe requested operation is not supported for a remote machine
-2146500036800F023CThe specified file is not an installed OEM INF
-2146500035800F023DOne or more devices are presently installed using the specified INF
-2146500034800F023EThe requested device install operation is obsolete
-2146500033800F023FA file could not be verified because it does not have an associated catalog signed via Authenticode(tm)
-2146500032800F0240Authenticode(tm) signature verification is not supported for the specified INF
-2146500031800F0241The INF was signed with an Authenticode(tm) catalog from a trusted publisher
-2146500030800F0242The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted
-2146500029800F0243The publisher of an Authenticode(tm) signed catalog was not established as trusted
-2146500028800F0244The software was tested for compliance with Windows Logo requirements on a different version of Windows
-2146500027800F0245The file may only be validated by a catalog signed via Authenticode(tm)
-2146500026800F0246One of the installers for this device cannot perform the installation at this time
-2146500025800F0247A problem was encountered while attempting to add the driver to the store
-2146500024800F0248The installation of this device is forbidden by system policy. Contact your system administrator
-2146500023800F0249The installation of this driver is forbidden by system policy. Contact your system administrator
-2146500022800F024AThe specified INF is the wrong type for this operation
-2146500021800F024BThe hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering
-2146500020800F024CA problem was encountered while attempting to delete the driver from the store
-2146499840800F0300An unrecoverable stack overflow was encountered
-2146496512800F1000No installed components were detected
-214643507180100001An internal consistency check failed
-214643507080100002The action was cancelled by an SCardCancel request
-214643506980100003The supplied handle was invalid
-214643506880100004One or more of the supplied parameters could not be properly interpreted
-214643506780100005Registry startup information is missing or invalid
-214643506680100006Not enough memory available to complete this command
-214643506580100007An internal consistency timer has expired
-214643506480100008The data buffer to receive returned data is too small for the returned data
-214643506380100009The specified reader name is not recognized
-21464350628010000AThe user-specified timeout value has expired
-21464350618010000BThe smart card cannot be accessed because of other connections outstanding
-21464350608010000CThe operation requires a smart card
-21464350598010000DThe specified smart card name is not recognized
-21464350588010000EThe system could not dispose of the media in the requested manner
-21464350578010000FThe requested protocols are incompatible with the protocol currently in use with the smart card
-214643505680100010The reader or smart card is not ready to accept commands
-214643505580100011One or more of the supplied parameters values could not be properly interpreted
-214643505480100012The action was cancelled by the system
-214643505380100013An internal communications error has been detected
-214643505280100014An internal error has been detected
-214643505180100015An ATR obtained from the registry is not a valid ATR string
-214643505080100016An attempt was made to end a non-existent transaction
-214643504980100017The specified reader is not currently available for use
-214643504880100018The operation has been aborted to allow the server application to exit
-214643504780100019The PCI Receive buffer was too small
-21464350468010001AThe reader driver does not meet minimal requirements for support
-21464350458010001BThe reader driver did not produce a unique reader name
-21464350448010001CThe smart card does not meet minimal requirements for support
-21464350438010001DThe Smart Card Resource Manager is not running
-21464350428010001EThe Smart Card Resource Manager has shut down
-21464350418010001FAn unexpected card error has occurred
-214643504080100020No Primary Provider can be found for the smart card
-214643503980100021The requested order of object creation is not supported
-214643503880100022This smart card does not support the requested feature
-214643503780100023The identified directory does not exist in the smart card
-214643503680100024The identified file does not exist in the smart card
-214643503580100025The supplied path does not represent a smart card directory
-214643503480100026The supplied path does not represent a smart card file
-214643503380100027Access is denied to this file
-214643503280100028The smart card does not have enough memory to store the information
-214643503180100029There was an error trying to set the smart card file object pointer
-21464350308010002AThe supplied PIN is incorrect
-21464350298010002BAn unrecognized error code was returned from a layered component
-21464350288010002CThe requested certificate does not exist
-21464350278010002DThe requested certificate could not be obtained
-21464350268010002ECannot find a smart card reader
-21464350258010002FA communications error with the smart card has been detected. Retry the operation
-214643502480100030The requested key container does not exist on the smart card
-214643502380100031The Smart Card Resource Manager is too busy to complete this operation
-214643502280100032The smart card PIN cache has expired
-214643502180100033The smart card PIN cannot be cached
-214643502080100034The smart card is read only and cannot be written to
-214643497180100065The reader cannot communicate with the smart card
-214643497080100066The smart card is not responding to a reset
-214643496980100067Power has been removed from the smart card
-214643496880100068The smart card has been reset
-214643496780100069The smart card has been removed
-21464349668010006AAccess was denied because of a security violation
-21464349658010006BThe card cannot be accessed because the wrong PIN was presented
-21464349648010006CThe card cannot be accessed because the maximum number of PIN entry attempts has been reached
-21464349638010006DThe end of the smart card file has been reached
-21464349628010006EThe action was cancelled by the user
-21464349618010006FNo PIN was presented to the smart card
-214643496080100070The requested item could not be found in the cache
-214643495980100071The requested cache item is too old and was deleted from the cache
-214643495880100072The new cache item exceeds the maximum per-item size defined for the cache
-214636851180110401Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail
-214636851080110402One or more of the object's properties are missing or invalid
-214636850980110403The object was not found in the catalog
-214636850880110404The object is already registered
-214636850580110407Error occurred writing to the application file
-214636850480110408Error occurred reading the application file
-214636850380110409Invalid version number in application file
-21463685028011040AThe file path is invalid
-21463685018011040BThe application is already installed
-21463685008011040CThe role already exists
-21463684998011040DAn error occurred copying the file
-21463684978011040FOne or more users are not valid
-214636849680110410One or more users in the application file are not valid
-214636849580110411The component's CLSID is missing or corrupt
-214636849480110412The component's progID is missing or corrupt
-214636849380110413Unable to set required authentication level for update request
-214636849280110414The identity or password set on the application is not valid
-214636848880110418Application file CLSIDs or IIDs do not match corresponding DLLs
-214636848780110419Interface information is either missing or changed
-21463684868011041ADllRegisterServer failed on component install
-21463684858011041BNo server file share available
-21463684838011041DDLL could not be loaded
-21463684828011041EThe registered TypeLib ID is not valid
-21463684818011041FApplication install directory not found
-214636847780110423Errors occurred while in the component registrar
-214636847680110424The file does not exist
-214636847580110425The DLL could not be loaded
-214636847480110426GetClassObject failed in the DLL
-214636847380110427The DLL does not support the components listed in the TypeLib
-214636847280110428The TypeLib could not be loaded
-214636847180110429The file does not contain components or component information
-21463684708011042AChanges to this object and its sub-objects have been disabled
-21463684698011042BThe delete function has been disabled for this object
-21463684688011042CThe server catalog version is not supported
-21463684678011042DThe component move was disallowed
-21463684668011042EThe component move failed because the destination application no longer exists
-214636846480110430The system was unable to register the TypeLib
-214636846180110433This operation cannot be performed on the system application
-214636846080110434The component registrar referenced in this file is not available
-214636845980110435A component in the same DLL is already installed
-214636845880110436The service is not installed
-214636845780110437One or more property settings are either invalid or in conflict with each other
-214636845680110438The object you are attempting to add or rename already exists
-214636845580110439The component already exists
-21463684538011043BThe registration file is corrupt
-21463684528011043CThe property value is too large
-21463684508011043EObject was not found in registry
-21463684498011043FThis object is not poolable
-214636844280110446A CLSID with the same GUID as the new application ID is already installed on this machine
-214636844180110447A role assigned to a component
-214636844080110448You must have components in an application in order to start the application
-214636843980110449This operation is not enabled on this platform
-21463684388011044AApplication Proxy is not exportable
-21463684378011044BFailed to start application because it is either a library application or an application proxy
-21463684368011044CSystem application is not exportable
-21463684358011044DCannot subscribe to this component (the component may have been imported)
-21463684348011044EAn event class cannot also be a subscriber component
-21463684338011044FLibrary applications and application proxies are incompatible
-214636843280110450This function is valid for the base partition only
-214636843180110451You cannot start an application that has been disabled
-214636842580110457The specified partition name is already in use on this computer
-214636842480110458The specified partition name is invalid. Check that the name contains at least one visible character
-214636842380110459The partition cannot be deleted because it is the default partition for one or more users
-21463684228011045AThe partition cannot be exported
-21463684218011045BApplications that contain one or more imported components cannot be installed into a non-base partition
-21463684208011045CThe application name is not unique and cannot be resolved to an application id
-21463684198011045DThe partition name is not unique and cannot be resolved to a partition id
-214636839880110472The COM+ registry database has not been initialized
-214636839780110473The COM+ registry database is not open
-214636839680110474The COM+ registry database detected a system error
-214636839580110475The COM+ registry database is already running
-214636838480110480This version of the COM+ registry database cannot be migrated
-214636838380110481The schema version to be migrated could not be found in the COM+ registry database
-214636838280110482There was a type mismatch between binaries
-214636838180110483A binary of unknown or invalid type was provided
-214636838080110484There was a type mismatch between a binary and an application
-214636837980110485The application cannot be paused or resumed
-214636837880110486The COM+ Catalog Server threw an exception during execution
-214636800080110600Only COM+ Applications marked "queued" can be invoked using the "queue" moniker
-214636799980110601At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker
-214636799880110602MSMQ is required for the requested operation and is not installed
-214636799780110603Unable to marshal an interface that does not support IPersistStream
-214636799680110604The message is improperly formatted or was damaged in transit
-214636799580110605An unauthenticated message was received by an application that accepts only authenticated messages
-214636799480110606The message was requeued or moved by a user not in the "QC Trusted User" role
-214636774380110701Cannot create a duplicate resource of type Distributed Transaction Coordinator
-214636748080110808One of the objects being inserted or updated does not belong to a valid parent collection
-214636747980110809One of the specified objects cannot be found
-21463674788011080AThe specified application is not currently running
-21463674778011080BThe partition(s) specified are not valid
-21463674758011080DCOM+ applications that run as NT service may not be pooled or recycled
-21463674748011080EOne or more users are already assigned to a local partition set
-21463674738011080FLibrary applications may not be recycled
-214636747180110811Applications running as NT services may not be recycled
-214636747080110812The process has already been recycled
-214636746980110813A paused process may not be recycled
-214636746880110814Library applications may not be NT services
-214636746780110815The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID
-214636746680110816The partition specified as default is not a member of the partition set
-214636746580110817A recycled process may not be paused
-214636746480110818Access to the specified partition is denied
-214636746380110819Only Application Files (*.MSI files) can be installed into partitions
-21463674628011081AApplications containing one or more legacy components may not be exported to 1.0 format
-21463674618011081BLegacy components may not exist in non-base partitions
-21463674608011081CA component cannot be moved (or copied) from the System Application
-21463674598011081DA component cannot be moved (or copied) to the System Application
-21463674588011081EA private component cannot be moved (or copied) to a library application or to the base partition
-21463674578011081FThe Base Application Partition exists in all partition sets and cannot be removed
-214636745680110820Alas
-214636745580110821Access is denied because the component is private
-214636745480110822The specified SAFER level is invalid
-214636745380110823The specified user cannot write to the system registry
-214636745280110824COM+ partitions are currently disabled
-214584524780190001Unexpected HTTP status code
-214584524580190003Unexpected redirection status code (3xx)
-214584524480190004Unexpected client error status code (4xx)
-214584524380190005Unexpected server error status code (5xx)
-21458449488019012CMultiple choices (300)
-21458449478019012DMoved permanently (301)
-21458449468019012EFound (302)
-21458449458019012FSee Other (303)
-214584494480190130Not modified (304)
-214584494380190131Use proxy (305)
-214584494180190133Temporary redirect (307)
-214584484880190190Bad request (400)
-214584484780190191Unauthorized (401)
-214584484680190192Payment required (402)
-214584484580190193Forbidden (403)
-214584484480190194Not found (404)
-214584484380190195Method not allowed (405)
-214584484280190196Not acceptable (406)
-214584484180190197Proxy authentication required (407)
-214584484080190198Request timeout (408)
-214584483980190199Conflict (409)
-21458448388019019AGone (410)
-21458448378019019BLength required (411)
-21458448368019019CPrecondition failed (412)
-21458448358019019DRequest entity too large (413)
-21458448348019019ERequest-URI too long (414)
-21458448338019019FUnsupported media type (415)
-2145844832801901A0Requested range not satisfiable (416)
-2145844831801901A1Expectation failed (417)
-2145844748801901F4Internal server error (500)
-2145844747801901F5Not implemented (501)
-2145844746801901F6Bad gateway (502)
-2145844745801901F7Service unavailable (503)
-2145844744801901F8Gateway timeout (504)
-2145844743801901F9Version not supported (505)
-2145681408801B8000Crash reporting failed
-2145681407801B8001Report aborted due to user cancellation
-2145681406801B8002Report aborted due to network failure
-2145681405801B8003Report not initialized
-2145681404801B8004Reporting is already in progress for the specified process
-2145681403801B8005Dump not generated due to a throttle
-2145681402801B8006Operation failed due to insufficient user consent
-2145681401801B8007Report aborted due to performance criteria
-2145452031801F0001A handler was not defined by the filter for this operation
-2145452030801F0002A context is already defined for this object
-2145452029801F0003Asynchronous requests are not valid for this operation
-2145452028801F0004Disallow the Fast IO path for this operation
-2145452027801F0005An invalid name request was made. The name requested cannot be retrieved at this time
-2145452026801F0006Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock
-2145452025801F0007The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver
-2145452024801F0008The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called)
-2145452023801F0009The 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
-2145452022801F000AThe Filter Manager had an internal error from which it cannot recover
-2145452021801F000BThe object specified for this action is in the process of being deleted
-2145452020801F000CNon-paged pool must be used for this type of context
-2145452019801F000DA duplicate handler definition has been provided for an operation
-2145452018801F000EThe callback data queue has been disabled
-2145452017801F000FDo not attach the filter to the volume at this time
-2145452016801F0010Do not detach the filter from the volume at this time
-2145452015801F0011An instance already exists at this altitude on the volume specified
-2145452014801F0012An instance already exists with this name on the volume specified
-2145452013801F0013The system could not find the filter specified
-2145452012801F0014The system could not find the volume specified
-2145452011801F0015The system could not find the instance specified
-2145452010801F0016No registered context allocation definition was found for the given request
-2145452009801F0017An invalid parameter was specified during context registration
-2145452008801F0018The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system
-2145452007801F0019The requested device object does not exist for the given volume
-2145452006801F001AThe specified volume is already mounted
-2145452005801F001BThe specified Transaction Context is already enlisted in a transaction
-2145452004801F001CThe specified context is already attached to another object
-2145452000801F0020No waiter is present for the filter's reply to this message
-2145451997801F0023The filesystem database resource is in use. Registration cannot complete at this time
-214499327980260001{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
-214498099180263001{Desktop composition is disabled}The operation could not be completed because desktop composition is disabled
-214498099080263002{Some desktop composition APIs are not supported while remoting}The operation is not supported while running in a remote session
-214498098980263003{No DWM redirection surface is available}The DWM was unable to provide a redirection surface to complete the DirectX present
-214498098880263004{DWM is not queuing presents for the specified window}The window specified is not currently using queued presents
-214498098780263005{The adapter specified by the LUID is not found}DWM can not find the adapter specified by the LUID
-214498098580263007{Redirection surface can not be created. The size of the surface is larger than what is supported on this machine}Redirection surface can not be created. The size of the surface is larger than what is supported on this machine
-214492774380270001The NAP SoH packet is invalid
-214492774280270002An SoH was missing from the NAP packet
-214492774180270003The entity ID conflicts with an already registered id
-214492774080270004No cached SoH is present
-214492773980270005The entity is still bound to the NAP system
-214492773880270006The entity is not registered with the NAP system
-214492773780270007The entity is not initialized with the NAP system
-214492773680270008The correlation id in the SoH-Request and SoH-Response do not match up
-214492773580270009Completion was indicated on a request that is not currently pending
-21449277348027000AThe NAP component's id was not found
-21449277338027000BThe maximum size of the connection is too small for an SoH packet
-21449277328027000CThe NapAgent service is not running
-21449277308027000EThe entity is disabled with the NapAgent service
-21449277298027000FGroup Policy is not configured
-214492772880270010Too many simultaneous calls
-214492772780270011SHV configuration already existed
-214492772680270012SHV configuration is not found
-214492772580270013SHV timed out on the request
-214492720080270220The maximum number of items for the access list has been reached. An item must be removed before another item is added
-214492719880270222Cannot access Homegroup. Homegroup may not be set up or may have encountered an error
-214492715280270250This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again
-214492715180270251This app can't be activated from an elevated context
-214492715080270252This app can't be activated when UAC is disabled
-214492714980270253This app can't be activated by the Built-in Administrator
-214492714880270254This app does not support the contract specified or is not installed
-214492714780270255This app has multiple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous
-214492714680270256This app's package family has more than one package installed. This is not supported
-214492714580270257The app manager is required to activate applications
-21449271428027025AThe app didn't start in the required time
-21449271418027025BThe app didn't start
-21449271408027025CThis app failed to launch because of an issue with its license. Please try again in a moment
-21449271398027025DThis app failed to launch because its trial license has expired
-214492713680270260Please choose a folder on a drive that's formatted with the NTFS file system
-214492713580270261This location is already being used. Please choose a different location
-214492713480270262This location cannot be indexed. Please choose a different location
-214492713380270263Sorry
-214492713280270264Sorry
-214492713180270265This content can only be moved to a folder. To move the content to this drive
-214486220880280000This is an error mask to convert TPM hardware errors to win errors
-214486220780280001TPM 1.2: Authentication failed
-214486220680280002TPM 1.2: The index to a PCR
-214486220580280003TPM 1.2: One or more parameter is bad
-214486220480280004TPM 1.2: An operation completed successfully but the auditing of that operation failed
-214486220380280005TPM 1.2: The clear disable flag is set and all clear operations now require physical access
-214486220280280006TPM 1.2: Activate the Trusted Platform Module (TPM)
-214486220180280007TPM 1.2: Enable the Trusted Platform Module (TPM)
-214486220080280008TPM 1.2: The target command has been disabled
-214486219980280009TPM 1.2: The operation failed
-21448621988028000ATPM 1.2: The ordinal was unknown or inconsistent
-21448621978028000BTPM 1.2: The ability to install an owner is disabled
-21448621968028000CTPM 1.2: The key handle cannot be interpreted
-21448621958028000DTPM 1.2: The key handle points to an invalid key
-21448621948028000ETPM 1.2: Unacceptable encryption scheme
-21448621938028000FTPM 1.2: Migration authorization failed
-214486219280280010TPM 1.2: PCR information could not be interpreted
-214486219180280011TPM 1.2: No room to load key
-214486219080280012TPM 1.2: There is no Storage Root Key (SRK) set
-214486218980280013TPM 1.2: An encrypted blob is invalid or was not created by this TPM
-214486218880280014TPM 1.2: The Trusted Platform Module (TPM) already has an owner
-214486218780280015TPM 1.2: The TPM has insufficient internal resources to perform the requested action
-214486218680280016TPM 1.2: A random string was too short
-214486218580280017TPM 1.2: The TPM does not have the space to perform the operation
-214486218480280018TPM 1.2: The named PCR value does not match the current PCR value
-214486218380280019TPM 1.2: The paramSize argument to the command has the incorrect value
-21448621828028001ATPM 1.2: There is no existing SHA-1 thread
-21448621818028001BTPM 1.2: The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error
-21448621808028001CTPM 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
-21448621798028001DTPM 1.2: The authorization for the second key in a 2 key function failed authorization
-21448621788028001ETPM 1.2: The tag value sent to for a command is invalid
-21448621778028001FTPM 1.2: An IO error occurred transmitting information to the TPM
-214486217680280020TPM 1.2: The encryption process had a problem
-214486217580280021TPM 1.2: The decryption process did not complete
-214486217480280022TPM 1.2: An invalid handle was used
-214486217380280023TPM 1.2: The TPM does not have an Endorsement Key (EK) installed
-214486217280280024TPM 1.2: The usage of a key is not allowed
-214486217180280025TPM 1.2: The submitted entity type is not allowed
-214486217080280026TPM 1.2: The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup
-214486216980280027TPM 1.2: Signed data cannot include additional DER information
-214486216880280028TPM 1.2: The key properties in TPM_KEY_PARMs are not supported by this TPM
-214486216780280029TPM 1.2: The migration properties of this key are incorrect
-21448621668028002ATPM 1.2: The signature or encryption scheme for this key is incorrect or not permitted in this situation
-21448621658028002BTPM 1.2: The size of the data (or blob) parameter is bad or inconsistent with the referenced key
-21448621648028002CTPM 1.2: A mode parameter is bad
-21448621638028002DTPM 1.2: Either the physicalPresence or physicalPresenceLock bits have the wrong value
-21448621628028002ETPM 1.2: The TPM cannot perform this version of the capability
-21448621618028002FTPM 1.2: The TPM does not allow for wrapped transport sessions
-214486216080280030TPM 1.2: TPM audit construction failed and the underlying command was returning a failure code also
-214486215980280031TPM 1.2: TPM audit construction failed and the underlying command was returning success
-214486215880280032TPM 1.2: Attempt to reset a PCR register that does not have the resettable attribute
-214486215780280033TPM 1.2: Attempt to reset a PCR register that requires locality and locality modifier not part of command transport
-214486215680280034TPM 1.2: Make identity blob not properly typed
-214486215580280035TPM 1.2: When saving context identified resource type does not match actual resource
-214486215480280036TPM 1.2: The TPM is attempting to execute a command only available when in FIPS mode
-214486215380280037TPM 1.2: The command is attempting to use an invalid family ID
-214486215280280038TPM 1.2: The permission to manipulate the NV storage is not available
-214486215180280039TPM 1.2: The operation requires a signed command
-21448621508028003ATPM 1.2: Wrong operation to load an NV key
-21448621498028003BTPM 1.2: NV_LoadKey blob requires both owner and blob authorization
-21448621488028003CTPM 1.2: The NV area is locked and not writable
-21448621478028003DTPM 1.2: The locality is incorrect for the attempted operation
-21448621468028003ETPM 1.2: The NV area is read only and can't be written to
-21448621458028003FTPM 1.2: There is no protection on the write to the NV area
-214486214480280040TPM 1.2: The family count value does not match
-214486214380280041TPM 1.2: The NV area has already been written to
-214486214280280042TPM 1.2: The NV area attributes conflict
-214486214180280043TPM 1.2: The structure tag and version are invalid or inconsistent
-214486214080280044TPM 1.2: The key is under control of the TPM Owner and can only be evicted by the TPM Owner
-214486213980280045TPM 1.2: The counter handle is incorrect
-214486213880280046TPM 1.2: The write is not a complete write of the area
-214486213780280047TPM 1.2: The gap between saved context counts is too large
-214486213680280048TPM 1.2: The maximum number of NV writes without an owner has been exceeded
-214486213580280049TPM 1.2: No operator AuthData value is set
-21448621348028004ATPM 1.2: The resource pointed to by context is not loaded
-21448621338028004BTPM 1.2: The delegate administration is locked
-21448621328028004CTPM 1.2: Attempt to manage a family other then the delegated family
-21448621318028004DTPM 1.2: Delegation table management not enabled
-21448621308028004ETPM 1.2: There was a command executed outside of an exclusive transport session
-21448621298028004FTPM 1.2: Attempt to context save a owner evict controlled key
-214486212880280050TPM 1.2: The DAA command has no resources available to execute the command
-214486212780280051TPM 1.2: The consistency check on DAA parameter inputData0 has failed
-214486212680280052TPM 1.2: The consistency check on DAA parameter inputData1 has failed
-214486212580280053TPM 1.2: The consistency check on DAA_issuerSettings has failed
-214486212480280054TPM 1.2: The consistency check on DAA_tpmSpecific has failed
-214486212380280055TPM 1.2: The atomic process indicated by the submitted DAA command is not the expected process
-214486212280280056TPM 1.2: The issuer's validity check has detected an inconsistency
-214486212180280057TPM 1.2: The consistency check on w has failed
-214486212080280058TPM 1.2: The handle is incorrect
-214486211980280059TPM 1.2: Delegation is not correct
-21448621188028005ATPM 1.2: The context blob is invalid
-21448621178028005BTPM 1.2: Too many contexts held by the TPM
-21448621168028005CTPM 1.2: Migration authority signature validation failure
-21448621158028005DTPM 1.2: Migration destination not authenticated
-21448621148028005ETPM 1.2: Migration source incorrect
-21448621138028005FTPM 1.2: Incorrect migration authority
-214486211180280061TPM 1.2: Attempt to revoke the EK and the EK is not revocable
-214486211080280062TPM 1.2: Bad signature of CMK ticket
-214486210980280063TPM 1.2: There is no room in the context list for additional contexts
-214486207980280081TPM 2.0: Asymmetric algorithm not supported or not correct
-214486207880280082TPM 2.0: Inconsistent attributes
-214486207780280083TPM 2.0: Hash algorithm not supported or not appropriate
-214486207680280084TPM 2.0: Value is out of range or is not correct for the context
-214486207580280085TPM 2.0: Hierarchy is not enabled or is not correct for the use
-214486207380280087TPM 2.0: Key size is not supported
-214486207280280088TPM 2.0: Mask generation function not supported
-214486207180280089TPM 2.0: Mode of operation not supported
-21448620708028008ATPM 2.0: The type of the value is not appropriate for the use
-21448620698028008BTPM 2.0: The Handle is not correct for the use
-21448620688028008CTPM 2.0: Unsupported key derivation function or function not appropriate for use
-21448620678028008DTPM 2.0: Value was out of allowed range
-21448620668028008ETPM 2.0: The authorization HMAC check failed and DA counter incremented
-21448620658028008FTPM 2.0: Invalid nonce size
-214486206480280090TPM 2.0: Authorization requires assertion of PP
-214486206280280092TPM 2.0: Unsupported or incompatible scheme
-214486205980280095TPM 2.0: Structure is wrong size
-214486205880280096TPM 2.0: Unsupported symmetric algorithm or key size
-214486205780280097TPM 2.0: Incorrect structure tag
-214486205680280098TPM 2.0: Union selector is incorrect
-21448620548028009ATPM 2.0: The TPM was unable to unmarshal a value because there were not enough octets in the input buffer
-21448620538028009BTPM 2.0: The signature is not valid
-21448620528028009CTPM 2.0: Key fields are not compatible with the selected use
-21448620518028009DTPM 2.0: A policy check failed
-21448620498028009FTPM 2.0: Integrity check failed
-2144862048802800A0TPM 2.0: Invalid ticket
-2144862047802800A1TPM 2.0: Reserved bits not set to zero as required
-2144862046802800A2TPM 2.0: Authorization failure without DA implications
-2144862045802800A3TPM 2.0: The policy has expired
-2144862044802800A4TPM 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
-2144862043802800A5TPM 2.0: Public and sensitive portions of an object are not cryptographically bound
-2144862042802800A6TPM 2.0: Curve not supported
-2144862041802800A7TPM 2.0: Point is not on the required curve
-214486195280280100TPM 2.0: TPM not initialized
-214486195180280101TPM 2.0: Commands not being accepted because of a TPM failure
-214486194980280103TPM 2.0: Improper use of a sequence handle
-21448619418028010BTPM 2.0: TPM_RC_PRIVATE error
-214486192780280119TPM 2.0: TPM_RC_HMAC
-214486192080280120TPM 2.0: TPM_RC_DISABLED
-214486191980280121TPM 2.0: Command failed because audit sequence required exclusivity
-214486191780280123TPM 2.0: Unsupported ECC curve
-214486191680280124TPM 2.0: Authorization handle is not correct for command
-214486191580280125TPM 2.0: Command requires an authorization session for handle and is not present
-214486191480280126TPM 2.0: Policy failure in Math Operation or an invalid authPolicy value
-214486191380280127TPM 2.0: PCR check fail
-214486191280280128TPM 2.0: PCR have changed since checked
-21448619078028012DTPM 2.0: The TPM is not in the right mode for upgrade
-21448619068028012ETPM 2.0: Context ID counter is at maximum
-21448619058028012FTPM 2.0: authValue or authPolicy is not available for selected entity
-214486190480280130TPM 2.0: A _TPM_Init and Startup(CLEAR) is required before the TPM can resume operation
-214486190380280131TPM 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
-214486188680280142TPM 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
-214486188580280143TPM 2.0: Command code not supported
-214486188480280144TPM 2.0: The value of authorizationSize is out of range or the number of octets in the authorization Area is greater than required
-214486188380280145TPM 2.0: Use of an authorization session with a context command or another command that cannot have an authorization session
-214486188280280146TPM 2.0: NV offset+size is out of range
-214486188180280147TPM 2.0: Requested allocation size is larger than allowed
-214486188080280148TPM 2.0: NV access locked
-214486187980280149TPM 2.0: NV access authorization fails in command actions
-21448618788028014ATPM 2.0: An NV index is used before being initialized or the state saved by TPM2_Shutdown(STATE) could not be restored
-21448618778028014BTPM 2.0: Insufficient space for NV allocation
-21448618768028014CTPM 2.0: NV index or persistent object already defined
-214486187280280150TPM 2.0: Context in TPM2_ContextLoad() is not valid
-214486187180280151TPM 2.0: chHash value already set or not correct for use
-214486187080280152TPM 2.0: Handle for parent is not a valid parent
-214486186980280153TPM 2.0: Some function needs testing
-214486186880280154TPM 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
-214486186780280155TPM 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
-214486118480280400The command was blocked
-214486118380280401The specified handle was not found
-214486118280280402The TPM returned a duplicate handle and the command needs to be resubmitted
-214486118180280403The command within the transport was blocked
-214486118080280404The command within the transport is not supported
-214486016080280800The TPM is too busy to respond to the command immediately
-214486015980280801SelfTestFull has not been run
-214486015880280802The TPM is currently executing a full selftest
-214486015780280803The TPM is defending against dictionary attacks and is in a time-out period
-214485990380280901TPM 2.0: Gap for context ID is too large
-214485990280280902TPM 2.0: Out of memory for object contexts
-214485990180280903TPM 2.0: Out of memory for session contexts
-214485990080280904TPM 2.0: Out of shared object/session memory or need space for internal operations
-214485989980280905TPM 2.0: Out of session handles - a session must be flushed before a nes session may be created
-214485989880280906TPM 2.0: Out of object handles - the handle space for objects is depleted and a reboot is required
-214485989780280907TPM 2.0: Bad locality
-214485989680280908TPM 2.0: The TPM has suspended operation on the command; forward progress was made and the command may be retried
-214485989580280909TPM 2.0: The command was canceled
-21448598948028090ATPM 2.0: TPM is performing self-tests
-214485987280280920TPM 2.0: The TPM is rate-limiting accesses to prevent wearout of NV
-214485987180280921TPM 2.0: Authorization for objects subject to DA protection are not allowed at this time because the TPM is in DA lockout mode
-214485987080280922TPM 2.0: The TPM was not able to start the command
-214485986980280923TPM 2.0: the command may require writing of NV and NV is not current accessible
-214484582380284001An internal error has occurred within the Trusted Platform Module support program
-214484582280284002One or more input parameters is bad
-214484582180284003A specified output pointer is bad
-214484582080284004The specified context handle does not refer to a valid context
-214484581980284005A specified output buffer is too small
-214484581880284006An error occurred while communicating with the TPM
-214484581780284007One or more context parameters is invalid
-214484581680284008The TBS service is not running and could not be started
-214484581580284009A new context could not be created because there are too many open contexts
-21448458148028400AA new virtual resource could not be created because there are too many open virtual resources
-21448458138028400BThe TBS service has been started but is not yet running
-21448458128028400CThe physical presence interface is not supported
-21448458118028400DThe command was canceled
-21448458108028400EThe input or output buffer is too large
-21448458098028400FA compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer
-214484580880284010The TBS service has been disabled
-214484580780284011No TCG event log is available
-214484580680284012The caller does not have the appropriate rights to perform the requested operation
-214484580580284013The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful
-214484580480284014The Physical Presence Interface of this firmware does not support the requested method
-214484580380284015The requested TPM OwnerAuth value was not found
-214484580280284016The TPM provisioning did not complete. For more information on completing the provisioning
-214479641680290100The command buffer is not in the correct state
-214479641580290101The command buffer does not contain enough data to satisfy the request
-214479641480290102The command buffer cannot contain any more data
-214479641380290103One or more output parameters was NULL or invalid
-214479641280290104One or more input parameters is invalid
-214479641180290105Not enough memory was available to satisfy the request
-214479641080290106The specified buffer was too small
-214479640980290107An internal error was detected
-214479640880290108The caller does not have the appropriate rights to perform the requested operation
-214479640780290109The specified authorization information was invalid
-21447964068029010AThe specified context handle was not valid
-21447964058029010BAn error occurred while communicating with the TBS
-21447964048029010CThe TPM returned an unexpected result
-21447964038029010DThe message was too large for the encoding scheme
-21447964028029010EThe encoding in the blob was not recognized
-21447964018029010FThe key size is not valid
-214479640080290110The encryption operation failed
-214479639980290111The key parameters structure was not valid
-214479639880290112The requested supplied data does not appear to be a valid migration authorization blob
-214479639780290113The specified PCR index was invalid
-214479639680290114The data given does not appear to be a valid delegate blob
-214479639580290115One or more of the specified context parameters was not valid
-214479639480290116The data given does not appear to be a valid key blob
-214479639380290117The specified PCR data was invalid
-214479639280290118The format of the owner auth data was invalid
-214479639180290119The random number generated did not pass FIPS RNG check
-21447963908029011AThe TCG Event Log does not contain any data
-21447963898029011BAn entry in the TCG Event Log was invalid
-21447963888029011CA TCG Separator was not found
-21447963878029011DA digest value in a TCG Log entry did not match hashed data
-21447963868029011EThe requested operation was blocked by current TPM policy. Please contact your system administrator for assistance
-21447963858029011FThe Windows TPM NV Bits index is not defined
-214479638480290120The Windows TPM NV Bits index is not ready for use
-214479638380290121The TPM key that was used to seal the data is no longer available
-214479638280290122An authorization chain could not be found that authorizes the PolicyAuthorize unseal
-214479638180290123The SVN counter to which the authorization was bound is not available
-214479638080290124The TPM Storage hierarchy (Owner) auth value is required to be NULL for this operation
-214479637980290125The TPM Endorsement hierarchy auth value is required to be NULL for this operation
-214479637880290126The authorization to perform this operation has been revoked
-214479637780290127The authorization public key is malformed
-214479637680290128The authorization public key is not supported
-214479637580290129The authorization signature is invalid
-21447963748029012AThe authorization policy is malformed
-21447963738029012BThe authorization data is malformed
-21447963728029012CThe key used to unseal this data has changed since sealing the data. This may be the result of a TPM clear
-21447963718029012DThe TPM version is invalid
-21447963708029012EThe policy authorization blob type is invalid
-214479616080290200The specified buffer was too small
-214479615980290201The context could not be cleaned up
-214479615880290202The specified context handle is invalid
-214479615780290203An invalid context parameter was specified
-214479615680290204An error occurred while communicating with the TPM
-214479615580290205No entry with the specified key was found
-214479615480290206The specified virtual handle matches a virtual handle already in use
-214479615380290207The pointer to the returned handle location was NULL or invalid
-214479615280290208One or more parameters is invalid
-214479615180290209The RPC subsystem could not be initialized
-21447961508029020AThe TBS scheduler is not running
-21447961498029020BThe command was canceled
-21447961488029020CThere was not enough memory to fulfill the request
-21447961478029020DThe specified list is empty
-21447961468029020EThe specified item was not found in the list
-21447961458029020FThe TPM does not have enough space to load the requested resource
-214479614480290210There are too many TPM contexts in use
-214479614380290211The TPM command failed
-214479614280290212The TBS does not recognize the specified ordinal
-214479614180290213The requested resource is no longer available
-214479614080290214The resource type did not match
-214479613980290215No resources can be unloaded
-214479613880290216No new entries can be added to the hash table
-214479613780290217A new TBS context could not be created because there are too many open contexts
-214479613680290218A new virtual resource could not be created because there are too many open virtual resources
-214479613580290219The physical presence interface is not supported
-21447961348029021ATBS is not compatible with the version of TPM found on the system
-21447961338029021BNo TCG event log is available
-214479590480290300A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command
-214479590380290301The user failed to confirm the TPM operation request
-214479590280290302The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request
-214479590180290303The BIOS does not support the physical presence interface
-214479590080290304The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command
-214479564880290400This is an error mask to convert Platform Crypto Provider errors to win errors
-214479564780290401The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational
-214479564680290402The handle provided to the Platform Crypto Provider is invalid
-214479564580290403A parameter provided to the Platform Crypto Provider is invalid
-214479564480290404A provided flag to the Platform Crypto Provider is not supported
-214479564380290405The requested operation is not supported by this Platform Crypto Provider
-214479564280290406The buffer is too small to contain all data. No information has been written to the buffer
-214479564180290407An unexpected internal error has occurred in the Platform Crypto Provider
-214479564080290408The authorization to use a provider object has failed
-214479563980290409The Platform Crypto Device has ignored the authorization for the provider object
-21447956388029040AThe referenced policy was not found
-21447956378029040BThe referenced profile was not found
-21447956368029040CThe validation was not succesful
-21447956348029040EAn attempt was made to import or load a key under an incorrect storage parent
-21447956338029040FThe TPM key is not loaded
-214479563280290410The TPM key certification has not been generated
-214479563180290411The TPM key is not yet finalized
-214479563080290412The TPM attestation challenge is not set
-214479562980290413The TPM PCR info is not available
-214479562880290414The TPM key is already finalized
-214479562780290415The TPM key usage policy is not supported
-214479562680290416The TPM key usage policy is invalid
-214479562580290417There was a problem with the software key being imported into the TPM
-214479562480290418The TPM key is not authenticated
-214479562380290419The TPM key is not an AIK
-21447956228029041AThe TPM key is not a signing key
-21447956218029041BThe TPM is locked out
-21447956208029041CThe claim type requested is not supported
-21447956198029041DTPM version is not supported
-21447956188029041EThe buffer lengths do not match
-21447956178029041FThe RSA key creation is blocked on this TPM due to known security vulnerabilities
-214479561680290420A ticket required to use a key was not provided
-214479561580290421This key has a raw policy so the KSP can't authenticate against it
-214479561480290422The TPM key's handle was unexpectedly invalidated due to a hardware or firmware issue
-214479539280290500TPM related network operations are blocked as Zero Exhaust mode is enabled on client
-214479513680290600TPM provisioning did not run to completion
-214479513580290601An invalid owner authorization value was specified
-214479513480290602TPM command returned too much data
-2144731135802A0001The object could not be created
-2144731134802A0002Shutdown was already called on this object or the object that owns it
-2144731133802A0003This method cannot be called during this type of callback
-2144731132802A0004This object has been sealed
-2144731131802A0005The requested value was never set
-2144731130802A0006The requested value cannot be determined
-2144731129802A0007A callback returned an invalid output parameter
-2144731128802A0008A callback returned a success code other than S_OK or S_FALSE
-2144731127802A0009A parameter that should be owned by this object is owned by a different object
-2144731126802A000AMore than one item matched the search criteria
-2144731125802A000BA floating-point overflow occurred
-2144731124802A000CThis method can only be called from the thread that created the object
-2144730879802A0101The storyboard is currently in the schedule
-2144730878802A0102The storyboard is not playing
-2144730877802A0103The start keyframe might occur after the end keyframe
-2144730876802A0104It might not be possible to determine the end keyframe time when the start keyframe is reached
-2144730875802A0105Two repeated portions of a storyboard might overlap
-2144730874802A0106The transition has already been added to a storyboard
-2144730873802A0107The transition has not been added to a storyboard
-2144730872802A0108The transition might eclipse the beginning of another transition in the storyboard
-2144730871802A0109The given time is earlier than the time passed to the last update
-2144730870802A010AThis client is already connected to a timer
-2144730869802A010BThe passed dimension is invalid or does not match the object's dimension
-2144730868802A010CThe added primitive begins at or beyond the duration of the interpolator
-2144730623802A0201The operation cannot be completed because the window is being closed
-214433791880300002Data Collector Set was not found
-214433785180300045Unable to start Data Collector Set because there are too many folders
-214433780880300070Not enough free disk space to start Data Collector Set
-2144337750803000AAThe Data Collector Set or one of its dependencies is already in use
-2144337737803000B7Data Collector Set already exists
-214433766380300101Property value conflict
-214433766280300102The current configuration for this Data Collector Set requires that it contain exactly one Data Collector
-214433766180300103A user account is required in order to commit the current Data Collector Set properties
-214433766080300104Data Collector Set is not running
-214433765980300105A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list
-214433765880300106The executable path you have specified refers to a network share or UNC path
-214433765780300107The executable path you have specified is already configured for API tracing
-214433765680300108The executable path you have specified does not exist. Verify that the specified path is correct
-214433765580300109Data Collector already exists
-21443376548030010AThe wait for the Data Collector Set start notification has timed out
-21443376538030010BThe wait for the Data Collector to start has timed out
-21443376528030010CThe wait for the report generation tool to finish has timed out
-21443376518030010DDuplicate items are not allowed
-21443376508030010EWhen specifying the executable that you want to trace
-21443376498030010FThe session name provided is invalid
-214433764880300110The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation
-214433764780300111The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation
-214433764680300112The execution of the Rules Manager failed
-214433764580300113An error occurred while attempting to compress or extract the data
-214427238480310000This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel
-214427238380310001This drive is not encrypted
-214427238280310002The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions
-214427238180310003The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions
-214427238080310004A required TPM measurement is missing. If there is a bootable CD or DVD in your computer
-214427237980310005The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR)
-214427237880310006The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR)
-214427237780310007At least one secure key protector is required for this operation to be performed
-214427237680310008BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker
-214427237580310009BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again
-21442723748031000AThe Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed
-21442723738031000BThe type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted
-21442723728031000CThe size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted
-21442723718031000DThe attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted
-21442723708031000EThe attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects
-21442723698031000FThe specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed
-214427236880310010The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access
-214427236780310011The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again
-214427236680310012The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive
-214427236580310013The drive cannot be encrypted because the file system is not supported
-214427236480310014The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker
-214427236380310015This drive cannot be encrypted
-214427236280310016The data is not valid
-214427236180310017The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically
-214427236080310018You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption
-214427235980310019The operation attempted cannot be performed on an operating system drive
-21442723588031001AThe buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again
-21442723578031001BA read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker
-21442723568031001CA write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker
-21442723558031001DOne or more BitLocker key protectors are required. You cannot delete the last key on this drive
-21442723548031001ECluster configurations are not supported by BitLocker Drive Encryption
-21442723538031001FThe drive specified is already configured to be automatically unlocked on the current computer
-214427235280310020The operating system drive is not protected by BitLocker Drive Encryption
-214427235180310021BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled
-214427235080310022The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive
-214427234980310023BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive
-214427234880310024The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again
-214427234780310025The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker
-214427234680310026The drive encryption algorithm cannot be used on this sector size
-214427234580310027The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again
-214427234480310028The drive specified is not the operating system drive
-214427234380310029BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer
-21442723428031002AThe system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector
-21442723418031002BBitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS
-21442723408031002CGroup Policy settings require that a recovery password be specified before encrypting the drive
-21442723398031002DThe drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption
-21442723388031002EBitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive
-214427233680310030BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker
-214427233580310031This key protector cannot be added. Only one key protector of this type is allowed for this drive
-214427233480310032The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path
-214427233380310033The specified key protector was not found on the drive. Try another key protector
-214427233280310034The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method
-214427233180310035The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again
-214427233080310036The random number generator check test failed
-214427232980310037The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode
-214427232880310038The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode
-214427232780310039The drive must be fully decrypted to complete this operation
-21442723268031003AThe key protector specified cannot be used for this operation
-21442723258031003BNo key protectors exist on the drive to perform the hardware test
-21442723248031003CThe BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device
-21442723238031003DThe BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again
-21442723228031003EThe BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again
-21442723218031003FThe Trusted Platform Module (TPM) is disabled. The TPM must be enabled
-214427232080310040The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode
-214427231980310041The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries
-214427231880310042The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM)
-214427231780310043The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN
-214427231680310044A boot application has changed since BitLocker Drive Encryption was enabled
-214427231580310045The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled
-214427231480310046The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys
-214427231380310047This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again
-214427231280310048BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions
-214427231180310049This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption
-21442723108031004ABitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer
-21442723098031004BThe drive cannot be locked when the drive is in use
-21442723088031004CThe access token associated with the current thread is not an impersonated token
-21442723078031004DThe BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM
-21442723068031004EYou must restart your computer before continuing with BitLocker Drive Encryption
-21442723058031004FDrive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging
-214427230480310050No action was taken as BitLocker Drive Encryption is in raw access mode
-214427230380310051BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use
-214427230280310052The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again
-214427230180310053BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments
-214427230080310054The auto-unlock master key was not available from the operating system drive
-214427229980310055The system firmware failed to enable clearing of system memory when the computer was restarted
-214427229880310056The hidden drive cannot be encrypted
-214427229780310057BitLocker encryption keys were ignored because the drive was in a transient state
-214427229680310058Public key based protectors are not allowed on this drive
-214427229580310059BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing
-21442722948031005AThis version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature
-21442722938031005BThe Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information
-21442722928031005CGroup Policy settings do not permit the creation of a recovery password
-21442722918031005DGroup Policy settings require the creation of a recovery password
-21442722908031005EGroup Policy settings do not permit the creation of a recovery key
-21442722898031005FGroup Policy settings require the creation of a recovery key
-214427228880310060Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option
-214427228780310061Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option
-214427228680310062Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option
-214427228580310063Group Policy settings require the use of a startup key. Please choose this BitLocker startup option
-214427228480310064Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option
-214427228380310065Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option
-214427228280310066Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option
-214427228180310067Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option
-214427228080310068The PIN provided does not meet minimum or maximum length requirements
-214427227980310069The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector
-21442722788031006AGroup Policy settings do not permit the creation of a password
-21442722778031006BGroup Policy settings require the creation of a password
-21442722768031006CThe Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information
-21442722758031006DA password cannot be added to the operating system drive
-21442722748031006EThe BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive
-21442722738031006FThe drive is too small to be protected using BitLocker Drive Encryption
-214427227280310070The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives
-214427227180310071The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go
-214427227080310072Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption
-214427226980310073Group Policy settings require that you have a valid user certificate
-214427226880310074Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption
-214427226780310075Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked
-214427226680310076Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked
-214427226580310077Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives
-214427226480310078Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker
-214427226380310079Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker
-214427225680310080Your password does not meet minimum password length requirements. By default
-214427225580310081Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters
-214427225480310082This drive cannot be encrypted because it is reserved for Windows System Recovery Options
-214427225380310083BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred
-214427225280310084BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred
-214427225180310085The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute
-214427225080310086BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker
-214427224980310087BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied
-214427224880310088BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected
-214427224780310089The requested virtualization size is too big
-214427224080310090BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker
-214427223980310091BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker
-214427223880310092BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker
-214427223780310093The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute
-214427223680310094The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid
-214427223580310095Removal of the data recovery agent certificate must be done using the Certificates snap-in
-214427223480310096This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command
-214427223380310097The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive
-214427223280310098The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments
-214427223180310099The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals
-21442722308031009AThe requested TPM PIN contains invalid characters
-21442722298031009BThe management information stored on the drive contained an unknown type. If you are using an old version of Windows
-21442722288031009CThe feature is only supported on EFI systems
-21442722278031009DMore than one Network Key Protector certificate has been found on the system
-21442722268031009ERemoval of the Network Key Protector certificate must be done using the Certificates snap-in
-21442722258031009FAn invalid certificate has been found in the Network Key Protector certificate store
-2144272224803100A0This drive isn't protected with a PIN
-2144272223803100A1Please enter the correct current PIN
-2144272222803100A2You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator
-2144272221803100A3BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator
-2144272220803100A4Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z
-2144272219803100A5BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage
-2144272218803100A6BitLocker Drive Encryption does not support wiping free space on thin provisioned storage
-2144272217803100A7The required authentication key length is not supported by the drive
-2144272216803100A8This drive isn't protected with a password
-2144272215803100A9Please enter the correct current password
-2144272214803100AAThe password cannot exceed 256 characters
-2144272213803100ABA password key protector cannot be added because a TPM protector exists on the drive
-2144272212803100ACA TPM key protector cannot be added because a password protector exists on the drive
-2144272211803100ADThis command can only be performed from the coordinator node for the specified CSV volume
-2144272210803100AEThis command cannot be performed on a volume when it is part of a cluster
-2144272209803100AFBitLocker did not revert to using BitLocker software encryption due to group policy configuration
-2144272208803100B0The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use
-2144272207803100B1Group Policy settings do not allow the use of hardware-based encryption
-2144272206803100B2The drive specified does not support hardware-based encryption
-2144272205803100B3BitLocker cannot be upgraded during disk encryption or decryption
-2144272204803100B4Discovery Volumes are not supported for volumes using hardware encryption
-2144272203803100B5No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume
-2144272202803100B6No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume
-2144272201803100B7Group Policy settings require the creation of a startup PIN
-2144272200803100B8Group Policy settings require the creation of a recovery password
-2144272199803100B9Wipe of free space is not currently taking place
-2144272198803100BABitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled
-2144272197803100BBBitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker
-2144272196803100BCYour computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates
-2144272195803100BDBitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume
-2144272194803100BEBitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker
-2144272193803100BFThis PC's firmware is not capable of supporting hardware encryption
-2144272192803100C0BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator
-2144272191803100C1You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator
-2144272190803100C2BitLocker cannot save the recovery password because the specified Microsoft account is Suspended
-2144272189803100C3BitLocker cannot save the recovery password because the specified Microsoft account is Blocked
-2144272188803100C4This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy
-2144272187803100C5This PC cannot support device encryption because unencrypted fixed data volumes are present
-2144272186803100C6This PC does not meet the hardware requirements to support device encryption
-2144272185803100C7This PC cannot support device encryption because WinRE is not properly configured
-2144272184803100C8Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot
-2144272183803100C9This PC is not provisioned to support device encryption
-2144272182803100CADevice Lock has been triggered due to too many incorrect password attempts
-2144272181803100CBProtection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error
-2144272180803100CCYour PIN can only contain numbers from 0 to 9
-2144272179803100CDBitLocker cannot use hardware replay protection because no counter is available on your PC
-2144272178803100CEDevice Lockout state validation failed due to counter mismatch
-2144272177803100CFThe input buffer is too large
-2144272176803100D0The target of an invocation does not support requested capability
-2144272175803100D1Device encryption is currently blocked by this PC's configuration
-2144272174803100D2This drive has been opted out of device encryption
-2144272173803100D3Device encryption isn't available for this drive
-2144272172803100D4The encrypt on write mode for BitLocker is not supported in this version of Windows. You can turn on BitLocker without using the encrypt on write mode
-2144272171803100D5Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info
-2144272170803100D6Device encryption can't be turned off while this drive is being encrypted. Please try again later
-2144272169803100D7This action isn't supported because this drive isn't automatically managed with device encryption
-2144272168803100D8BitLocker can't be suspended on this drive until the next restart
-2144272167803100D9BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume
-2144272166803100DABitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for the OS drive
-2144272165803100DBBitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for fixed data drives
-2144272164803100DCBitLocker recovery password rotation cannot be performed because backup policy for BitLocker recovery information is not set to required for removable data drives
-2144272163803100DDBitLocker recovery password rotation not supported
-2144272162803100DEA server issued BitLocker recovery password rotation was denied because requests must be 15 minutes apart
-2144272161803100DFBitLocker recovery password key rotation policy is not enabled
-2144272160803100E0BitLocker recovery password key rotation could not be performed because the device is neither Azure AD joined nor Hybrid Azure AD joined
-2144272159803100E1BitLocker recovery key backup endpoint is busy and cannot perform requested operation. Please retry after sometime
-2144272155803100E5Adding BitLocker predicted TPM based protector is not supported
-2144272154803100E6Registeration for TPM callback is not supported
-2144272153803100E7Creating new TPM context is not supported
-2144272152803100E8The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration
-214420684780320001The callout does not exist
-214420684680320002The filter condition does not exist
-214420684580320003The filter does not exist
-214420684480320004The layer does not exist
-214420684380320005The provider does not exist
-214420684280320006The provider context does not exist
-214420684180320007The sublayer does not exist
-214420684080320008The object does not exist
-214420683980320009An object with that GUID or LUID already exists
-21442068388032000AThe object is referenced by other objects so cannot be deleted
-21442068378032000BThe call is not allowed from within a dynamic session
-21442068368032000CThe call was made from the wrong session so cannot be completed
-21442068358032000DThe call must be made from within an explicit transaction
-21442068348032000EThe call is not allowed from within an explicit transaction
-21442068338032000FThe explicit transaction has been forcibly cancelled
-214420683280320010The session has been cancelled
-214420683180320011The call is not allowed from within a read-only transaction
-214420683080320012The call timed out while waiting to acquire the transaction lock
-214420682980320013Collection of network diagnostic events is disabled
-214420682880320014The operation is not supported by the specified layer
-214420682780320015The call is allowed for kernel-mode callers only
-214420682680320016The call tried to associate two objects with incompatible lifetimes
-214420682580320017The object is built in so cannot be deleted
-214420682480320018The maximum number of callouts has been reached
-214420682380320019A notification could not be delivered because a message queue is at its maximum capacity
-21442068228032001AThe traffic parameters do not match those for the security association context
-21442068218032001BThe call is not allowed for the current security association state
-21442068208032001CA required pointer is null
-21442068198032001DAn enumerator is not valid
-21442068188032001EThe flags field contains an invalid value
-21442068178032001FA network mask is not valid
-214420681680320020An FWP_RANGE is not valid
-214420681580320021The time interval is not valid
-214420681480320022An array that must contain at least one element is zero length
-214420681380320023The displayData.name field cannot be null
-214420681280320024The action type is not one of the allowed action types for a filter
-214420681180320025The filter weight is not valid
-214420681080320026A filter condition contains a match type that is not compatible with the operands
-214420680980320027An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type
-214420680880320028An integer value is outside the allowed range
-214420680780320029A reserved field is non-zero
-21442068068032002AA filter cannot contain multiple conditions operating on a single field
-21442068058032002BA policy cannot contain the same keying module more than once
-21442068048032002CThe action type is not compatible with the layer
-21442068038032002DThe action type is not compatible with the sublayer
-21442068028032002EThe raw context or the provider context is not compatible with the layer
-21442068018032002FThe raw context or the provider context is not compatible with the callout
-214420680080320030The authentication method is not compatible with the policy type
-214420679980320031The Diffie-Hellman group is not compatible with the policy type
-214420679880320032An IKE policy cannot contain an Extended Mode policy
-214420679780320033The enumeration template or subscription will never match any objects
-214420679680320034The provider context is of the wrong type
-214420679580320035The parameter is incorrect
-214420679480320036The maximum number of sublayers has been reached
-214420679380320037The notification function for a callout returned an error
-214420679280320038The IPsec authentication transform is not valid
-214420679180320039The IPsec cipher transform is not valid
-21442067908032003AThe IPsec cipher transform is not compatible with the policy
-21442067898032003BThe combination of IPsec transform types is not valid
-21442067888032003CA policy cannot contain the same auth method more than once
-21442067878032003DA tunnel endpoint configuration is invalid
-21442067868032003EThe WFP MAC Layers are not ready
-21442067858032003FA key manager capable of key dictation is already registered
-214420678480320040A key manager dictated invalid keys
-214420678380320041The BFE IPsec Connection Tracking is disabled
-214420678280320042The DNS name is invalid
-214420678180320043The engine option is still enabled due to other configuration settings
-214420678080320044The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine
-214420658880320104The packet should be dropped
-214407577480340002The binding to the network interface is being closed
-214407577280340004An invalid version was specified
-214407577180340005An invalid characteristics table was used
-214407577080340006Failed to find the network interface or network interface is not ready
-214407576980340007Failed to open the network interface
-214407576880340008Network interface has encountered an internal unrecoverable failure
-214407576780340009The multicast list on the network interface is full
-21440757668034000AAn attempt was made to add a duplicate multicast address to the list
-21440757658034000BAt attempt was made to remove a multicast address that was never added
-21440757648034000CNetowork interface aborted the request
-21440757638034000DNetwork interface can not process the request because it is being reset
-21440757618034000FAn attempt was made to send an invalid packet on a network interface
-214407576080340010The specified request is not a valid operation for the target device
-214407575980340011Network interface is not ready to complete this operation
-214407575680340014The length of the buffer submitted for this operation is not valid
-214407575580340015The data used for this operation is not valid
-214407575480340016The length of buffer submitted for this operation is too small
-214407575380340017Network interface does not support this OID (Object Identifier)
-214407575280340018The network interface has been removed
-214407575180340019Network interface does not support this media type
-21440757508034001AAn attempt was made to remove a token ring group address that is in use by other components
-21440757498034001BAn attempt was made to map a file that can not be found
-21440757488034001CAn error occurred while NDIS tried to map the file
-21440757478034001DAn attempt was made to map a file that is alreay mapped
-21440757468034001EAn attempt to allocate a hardware resource failed because the resource is used by another component
-21440757458034001FThe I/O operation failed because network media is disconnected or wireless access point is out of range
-214407574280340022The network address used in the request is invalid
-21440757348034002AThe offload operation on the network interface has been paused
-21440757338034002BNetwork interface was not found
-21440757328034002CThe revision number specified in the structure is not supported
-21440757318034002DThe specified port does not exist on this network interface
-21440757308034002EThe current state of the specified port on this network interface does not support the requested operation
-21440757298034002FThe miniport adapter is in low power state
-214407572880340030This operation requires the miniport adapter to be reinitialized
-214407572780340031There are not enough queues to complete the operation
-2144075589803400BBNetword interface does not support this request
-214406758480342000The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation
-214406758380342001The wireless local area network interface is busy and can not perform the requested operation
-214406758280342002The wireless local area network interface is powered down and doesn't support the requested operation
-214406758180342003The list of wake on LAN patterns is full
-214406758080342004The list of low power protocol offloads is full
-214406757980342005The wireless local area network interface cannot start an AP on the specified channel right now
-214406757880342006The wireless local area network interface cannot start an AP on the specified band right now
-214406757780342007The wireless local area network interface cannot start an AP on this channel due to regulatory reasons
-214406757680342008The wireless local area network interface cannot start an AP on this band due to regulatory reasons
-214387916780370001A 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
-214387891280370100The virtual machine or container exited unexpectedly while starting
-214387891180370101The container operating system does not match the host operating system
-214387891080370102The virtual machine could not be started because a required feature is not installed
-214387890780370105The requested virtual machine or container operation is not valid in the current state
-214387890680370106The virtual machine or container exited unexpectedly
-214387890580370107The virtual machine or container was forcefully exited
-214387890480370108A connection could not be established with the container or virtual machine
-214387890380370109The operation timed out because a response was not received from the virtual machine or container
-21438789028037010AThe connection with the virtual machine or container was closed
-21438789018037010BAn unknown internal message was received by the virtual machine or container
-21438789008037010CThe virtual machine or container does not support an available version of the communication protocol with the host
-21438788998037010DThe virtual machine or container JSON document is invalid
-21438788988037010EA virtual machine or container with the specified identifier does not exist
-21438788978037010FA virtual machine or container with the specified identifier already exists
-214387889680370110The virtual machine or container with the specified identifier is not running
-214387889580370111A communication protocol error has occurred between the virtual machine or container and the host
-214387889480370112The container image contains a layer with an unrecognized format
-214387889380370113To use this container image
-214387889280370114The operation could not be started because a required feature is not installed
-214387889180370115The operation has not started
-214387889080370116The operation is already running
-214387888980370117The operation is still running
-214387888880370118The operation did not complete in time
-214387888780370119An event callback has already been registered on this handle
-21438788868037011ANot enough memory available to return the result of the operation
-21438788858037011BInsufficient privileges. Only administrators or users that are members of the Hyper-V Administrators user group are permitted to access virtual machines or containers. To add yourself to the Hyper-V Administrators user group
-21438788848037011CThe virtual machine or container reported a critical error and was stopped or restarted
-21438788838037011DThe process information is not available
-21438788828037011EThe host compute system service has disconnected unexpectedly
-21438788818037011FThe process has already exited
-214387840080370300The specified capability does not exist
-214387839980370301The specified buffer is too small for the requested data
-214387839880370302The specified property does not exist
-214387839780370303The configuration of the hypervisor on this system is not supported
-214387839680370304The configuration of the partition is not valid
-214387839580370305The specified GPA range was not found
-214387839480370306A virtual processor with the specified index already exists
-214387839380370307A virtual processor with the specified index does not exist
-214387839280370308The virtual processor is not in the correct state to perform the requested operation
-214387839180370309A virtual processor register with the specified name does not exist
-214387838480370310The Windows Hypervisor Platform is not supported due to a processor limitation
-214381363180380001The regeneration operation was not able to copy all data from the active plexes due to bad sectors
-214381363080380002One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems
-214374809580390001Some BCD entries were not imported correctly from the BCD store
-214374809380390003Some BCD entries were not synchronized correctly with the firmware
-2143682559803A0001The virtualization storage subsystem has generated an error
-2143617023803B0001The network was not found
-2143617022803B0002The endpoint was not found
-2143617021803B0003The network's underlying layer was not found
-2143617020803B0004The virtual switch was not found
-2143617019803B0005The network does not have a subnet for this endpoint
-2143617018803B0006An adapter was not found
-2143617017803B0007The switch-port was not found
-2143617016803B0008An expected policy was not found
-2143617015803B0009A required VFP port setting was not found
-2143617014803B000AThe provided network configuration is invalid or missing parameters
-2143617013803B000BInvalid network type
-2143617012803B000CThe provided endpoint configuration is invalid or missing parameters
-2143617011803B000DThe provided policy configuration is invalid or missing parameters
-2143617010803B000EInvalid policy type
-2143617009803B000FThis requested operation is invalid for a remote endpoint
-2143617008803B0010A network with this name already exists
-2143617007803B0011A network with this name already exists
-2143617006803B0012Policy information already exists on this object
-2143617005803B0013The specified port already exists
-2143617004803B0014This endpoint is already attached to the switch
-2143617003803B0015The specified request is unsupported
-2143617002803B0016Port mapping is not supported on the given network
-2143617001803B0017There was an operation attempted on a degraded object
-2143617000803B0018Cannot modify a switch shared by multiple networks
-2143616999803B0019Failed to interpret a parameter as a GUID
-2143616998803B001AFailed to process registry key
-2143616997803B001BInvalid JSON document string
-2143616996803B001CThe reference is invalid in the JSON document
-2143616995803B001DEndpoint sharing is disabled
-2143616994803B001EIP address is either invalid or not part of any configured subnet(s)
-2143616993803B001FThe specified switch extension does not exist on this switch
-2143616992803B0020Operation cannot be performed while service is stopping
-2143616991803B0021Operation cannot be performed while service module not found
-2143616990803B0022Request Handlers not present to handle the JSON request
-2143616989803B0023The specified request is unsupported
-2143616988803B0024Add runtime keys to container failed
-2143616987803B0025Timeout while waiting for network adapter with the given instance id
-2143616986803B0026Network adapter not found for the given instance id
-2143616985803B0027Network compartment not found for the given id
-2143616984803B0028Network interface not found for the given id
-2143616983803B0029Default Namespace already exists
-2143616982803B002AInternet Connection Sharing service (SharedAccess) is disabled and cannot be started
-2143616981803B002BThis requested operation is invalid as endpoint is already part of a network namespace
-2143616980803B002CThe specified entity cannot be removed while it still has references
-2143616979803B002DThe internal port must exist and cannot be zero
-2143616978803B002EThe requested operation for attach namespace failed
-2143616977803B002FAn address provided is invalid or reserved
-2143616976803B0030The prefix provided is invalid
-2143616975803B0031A call was performed against an object that was torn down
-2143616974803B0032The provided subnet configuration is invalid or missing parameters
-2143616973803B0033The provided IP subnet configuration is invalid or missing parameters
-2143616972803B0034The endpoint must be attached to complete the operation
-2143616971803B0035The endpoint must be local to complete the operation
-2143616970803B0036Cannot apply more than one InterfaceParameters policy
-2143551232803C0100The operation was cancelled
-2143551231803C0101An error occurred when running a PowerShell script
-2143551230803C0102An error occurred when interacting with PowerShell runtime
-2143551229803C0103An error occurred in the Scripted Diagnostic Managed Host
-2143551228803C0104The troubleshooting pack does not contain a required verifier to complete the verification
-2143551226803C0106Scripted diagnostics is disabled by group policy
-2143551225803C0107Trust validation of the troubleshooting pack failed
-2143551224803C0108The troubleshooting pack cannot be executed on this system
-2143551223803C0109This version of the troubleshooting pack is not supported
-2143551222803C010AA required resource cannot be loaded
-2143551221803C010BThe troubleshooting pack reported information for a root cause without adding the root cause
-2143485952803D0000The input data was not in the expected format or did not have the expected value
-2143485951803D0001The operation could not be completed because the object is in a faulted state due to a previous error
-2143485950803D0002The operation could not be completed because it would lead to numeric overflow
-2143485949803D0003The operation is not allowed due to the current state of the object
-2143485948803D0004The operation was aborted
-2143485947803D0005Access was denied by the remote endpoint
-2143485946803D0006The operation did not complete within the time allotted
-2143485945803D0007The operation was abandoned
-2143485944803D0008A quota was exceeded
-2143485943803D0009The information was not available in the specified language
-2143485942803D000ASecurity verification was not successful for the received data
-2143485941803D000BThe address is already being used
-2143485940803D000CThe address is not valid for this context
-2143485939803D000DThe remote endpoint does not exist or could not be located
-2143485938803D000EThe remote endpoint is not currently in service at this location
-2143485937803D000FThe remote endpoint could not process the request
-2143485936803D0010The remote endpoint was not reachable
-2143485935803D0011The operation was not supported by the remote endpoint
-2143485934803D0012The remote endpoint is unable to process the request due to being overloaded
-2143485933803D0013A message containing a fault was received from the remote endpoint
-2143485932803D0014The connection with the remote endpoint was terminated
-2143485931803D0015The HTTP proxy server could not process the request
-2143485930803D0016Access was denied by the HTTP proxy server
-2143485929803D0017The requested feature is not available on this platform
-2143485928803D0018The HTTP proxy server requires HTTP authentication scheme 'basic'
-2143485927803D0019The HTTP proxy server requires HTTP authentication scheme 'digest'
-2143485926803D001AThe HTTP proxy server requires HTTP authentication scheme 'NTLM'
-2143485925803D001BThe HTTP proxy server requires HTTP authentication scheme 'negotiate'
-2143485924803D001CThe remote endpoint requires HTTP authentication scheme 'basic'
-2143485923803D001DThe remote endpoint requires HTTP authentication scheme 'digest'
-2143485922803D001EThe remote endpoint requires HTTP authentication scheme 'NTLM'
-2143485921803D001FThe remote endpoint requires HTTP authentication scheme 'negotiate'
-2143485920803D0020The endpoint address URL is invalid
-2143485919803D0021Unrecognized error occurred in the Windows Web Services framework
-2143485918803D0022A security token was rejected by the server because it has expired
-2143485917803D0023A security operation failed in the Windows Web Services framework
-2143420160803E0100The notification channel has already been closed
-2143420159803E0101The notification channel request did not complete successfully
-2143420158803E0102The application identifier provided is invalid
-2143420157803E0103A notification channel request for the provided application identifier is in progress
-2143420156803E0104The channel identifier is already tied to another application endpoint
-2143420155803E0105The notification platform is unavailable
-2143420154803E0106The notification has already been posted
-2143420153803E0107The notification has already been hidden
-2143420152803E0108The notification cannot be hidden until it has been shown
-2143420151803E0109Cloud notifications have been turned off
-2143420144803E0110The application does not have the cloud notification capability
-2143420143803E0111Settings prevent the notification from being delivered
-2143420142803E0112Application capabilities prevent the notification from being delivered
-2143420141803E0113The application does not have the internet access capability
-2143420140803E0114Settings prevent the notification type from being delivered
-2143420139803E0115The size of the notification content is too large
-2143420138803E0116The size of the notification tag is too large
-2143420137803E0117The notification platform doesn't have appropriate privilege on resources
-2143420136803E0118The notification platform found application is already registered
-2143420135803E0119The application background task does not have the push notification capability
-2143420134803E011AThe notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service
-2143420133803E011BThe notification platform is unable to connect to the cloud notification service
-2143420132803E011CThe notification platform is unable to initialize a callback for lock screen updates
-2143420128803E0120The size of the developer id for scheduled notification is too large
-2143420118803E012AThe notification tag is not alphanumeric
-2143420117803E012BThe notification platform has received invalid HTTP status code other than 2xx for polling
-2143419904803E0200The notification platform has run out of presentation layer sessions
-2143419903803E0201The notification platform rejects image download request due to system in power save mode
-2143419902803E0202The notification platform doesn't have the requested image in its cache
-2143419901803E0203The notification platform cannot complete all of requested image
-2143419900803E0204A cloud image downloaded from the notification platform is invalid
-2143419899803E0205Notification Id provided as filter is matched with what the notification platform maintains
-2143419898803E0206Notification callback interface is already registered
-2143419897803E0207Toast Notification was dropped without being displayed to the user
-2143419896803E0208The notification platform does not have the proper privileges to complete the request
-2143419895803E0209The size of the notification group is too large
-2143419894803E020AThe notification group is not alphanumeric
-2143419893803E020BCloud notifications have been disabled for the application due to a policy setting
-214328934480400000Input data cannot be processed in the non-chronological order
-214328934380400001Requested operation cannot be performed inside the callback or event handler
-214328934280400002Input cannot be processed because there is ongoing interaction with another pointer type
-214328934180400003One or more fields in the input packet are invalid
-214328934080400004Packets in the frame are inconsistent. Either pointer ids are not unique or there is a discrepancy in timestamps
-214328933980400005The history of frames is inconsistent. Pointer ids
-214328933880400006Failed to retrieve information about the input device
-214328933780400007Coordinate system transformation failed to transform the data
-214328933680400008The property is not supported or not reported correctly by the input device
-214322380880410000The QUIC connection handshake failed
-214322380780410001The QUIC connection failed to negotiate a compatible protocol version
-214194534380548201Context is not activated
-214194534280548202Bad SIM is inserted
-214194534180548203Requested data class is not available
-214194534080548204Access point name (APN) or Access string is incorrect
-214194533980548205Max activated contexts have reached
-214194533880548206Device is in packet detach state
-214194533780548207Provider is not visible
-214194533680548208Radio is powered off
-214194533580548209MBN subscription is not activated
-21419453348054820ASIM is not inserted
-21419453338054820BVoice call in progress
-21419453328054820CVisible provider cache is invalid
-21419453318054820DDevice is not registered
-21419453308054820EProviders not found
-21419453298054820FPin is not supported
-214194532880548210Pin is required
-214194532780548211PIN is disabled
-214194532680548212Generic Failure
-214194532080548218Profile is invalid
-214194531980548219Default profile exist
-214194531280548220SMS encoding is not supported
-214194531180548221SMS filter is not supported
-214194531080548222Invalid SMS memory index is used
-214194530980548223SMS language is not supported
-214194530880548224SMS memory failure occurred
-214194530780548225SMS network timeout happened
-214194530680548226Unknown SMSC address is used
-214194530580548227SMS format is not supported
-214194530480548228SMS operation is not allowed
-214194530380548229Device SMS memory is full
-214191308780550001Windows cannot evaluate this EAS policy since this is not managed by the operating system
-214191308680550002The system can be made compliant to this EAS policy if certain actions are performed by the user
-214191308580550003The EAS policy being evaluated cannot be enforced by the system
-214191308480550004EAS password policies for the user cannot be evaluated as the user has a blank password
-214191308380550005EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system
-214191308280550006The user is not allowed to change her password
-214191308180550007EAS password policies cannot be evaluated as one or more admins have blank passwords
-214191308080550008One or more admins are not allowed to change their password
-214191307980550009There are other standard users present who are not allowed to change their password
-21419130788055000AThe EAS password policy cannot be enforced by the connected account provider of at least one administrator
-21419130778055000BThere is at least one administrator whose connected account password needs to be changed for EAS password policy compliance
-21419130768055000CThe EAS password policy cannot be enforced by the connected account provider of the current user
-21419130758055000DThe connected account password of the current user needs to be changed for EAS password policy compliance
-214099558380630001The IPv6 protocol is not installed
-214099558280630002The component has not been initialized
-214099558180630003The required service cannot be started
-214099558080630004The P2P protocol is not licensed to run on this OS
-214099556880630010The graph handle is invalid
-214099556780630011The graph database name has changed
-214099556680630012A graph with the same ID already exists
-214099556580630013The graph is not ready
-214099556480630014The graph is shutting down
-214099556380630015The graph is still in use
-214099556280630016The graph database is corrupt
-214099556180630017Too many attributes have been used
-214099532580630103The connection can not be found
-214099532280630106The peer attempted to connect to itself
-214099532180630107The peer is already listening for connections
-214099532080630108The node was not found
-214099531980630109The Connection attempt failed
-21409953188063010AThe peer connection could not be authenticated
-21409953178063010BThe connection was refused
-214099507180630201The peer name classifier is too long
-214099507080630202The maximum number of identities have been created
-214099506980630203Unable to access a key
-214099506880630204The group already exists
-214099481580630301The requested record could not be found
-214099481480630302Access to the database was denied
-214099481380630303The Database could not be initialized
-214099481280630304The record is too big
-214099481180630305The database already exists
-214099481080630306The database could not be found
-214099455980630401The identity could not be found
-214099430380630501The event handle could not be found
-214099404780630601Invalid search
-214099404680630602The search attributes are invalid
-214099379180630701The invitation is not trusted
-214099378980630703The certchain is too long
-214099378780630705The time period is invalid
-214099378680630706A circular cert chain was detected
-214099353580630801The certstore is corrupted
-214099148780631001The specified PNRP cloud does not exist
-214099148380631005The cloud name is ambiguous
-214098737680632010The record is invalid
-214098736080632020Not authorized
-214098735980632021The password does not meet policy requirements
-214098734480632030The record validation has been deferred
-214098732880632040The group properties are invalid
-214098731280632050The peername is invalid
-214098729680632060The classifier is invalid
-214098728080632070The friendly name is invalid
-214098727980632071Invalid role property
-214098727880632072Invalid classifier property
-214098726480632080Invalid record expiration
-214098726380632081Invalid credential info
-214098726280632082Invalid credential
-214098726180632083Invalid record size
-214098724880632090Unsupported version
-214098724780632091The group is not ready
-214098724680632092The group is still in use
-214098724580632093The group is invalid
-214098724480632094No members were found
-214098724380632095There are no member connections
-214098724280632096Unable to listen
-2140987232806320A0The identity does not exist
-2140987231806320A1The service is not available
-214097919980634001The peername could not be converted to a DNS pnrp name
-214097919880634002Invalid peer host name
-214097919780634003No more data could be found
-214097919580634005The existing peer name is already registered
-214097100780636001THe contact could not be found
-214096691280637000The app invite request was cancelled by the user
-214096691180637001No response of the invite was received
-214096690980637003User is not signed into serverless presence
-214096690880637004The user declined the privacy policy prompt
-214096690780637005A timeout occurred
-214096690580637007The address is invalid
-214096690480637008A required firewall exception is disabled
-214096690380637009The service is blocked by a firewall policy
-21409669028063700AFirewall exceptions are disabled
-21409669018063700BThe user declined to enable the firewall exceptions
-214086451180650001The attribute handle given was not valid on this server
-214086451080650002The attribute cannot be read
-214086450980650003The attribute cannot be written
-214086450880650004The attribute PDU was invalid
-214086450780650005The attribute requires authentication before it can be read or written
-214086450680650006Attribute server does not support the request received from the client
-214086450580650007Offset specified was past the end of the attribute
-214086450480650008The attribute requires authorization before it can be read or written
-214086450380650009Too many prepare writes have been queued
-21408645028065000ANo attribute found within the given attribute handle range
-21408645018065000BThe attribute cannot be read or written using the Read Blob Request
-21408645008065000CThe Encryption Key Size used for encrypting this link is insufficient
-21408644998065000DThe attribute value length is invalid for the operation
-21408644988065000EThe attribute request that was requested has encountered an error that was unlikely
-21408644978065000FThe attribute requires encryption before it can be read or written
-214086449680650010The attribute type is not a supported grouping attribute as defined by a higher layer specification
-214086449580650011Insufficient Resources to complete the request
-214086041680651000An error that lies in the reserved range has been received
-214079897580660001PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode
-214079897480660002HD Audio widget encountered an unexpected empty connection list
-214079897380660003HD Audio widget does not support the connection list parameter
-214079897280660004No HD Audio subdevices were successfully created
-214079897180660005An unexpected NULL pointer was encountered in a linked list
-214073343980670001Optimistic locking failure. Data cannot be updated if it has changed since it was read
-214073343880670002A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits
-214073343780670003The StateRepository configuration is not valid
-214073343680670004The StateRepository schema version is not known
-214073343580670005A StateRepository dictionary is not valid
-214073343480670006The request failed because the StateRepository is actively blocking requests
-214073343380670007The database file is locked. The request will be retried
-214073343280670008The database file is locked because another process is busy recovering the database. The request will be retried
-214073343180670009A table in the database is locked. The request will be retried
-21407334308067000AThe shared cache for the database is locked by another connection. The request will be retried
-21407334298067000BA transaction is required to perform the request operation
-21407334288067000CThe database file is locked. The request has exceeded the allowed threshold
-21407334278067000DThe database file is locked because another process is busy recovering the database. The request has exceeded the allowed threshold
-21407334268067000EA table in the database is locked. The request has exceeded the allowed threshold
-21407334258067000FThe shared cache for the database is locked by another connection. The request has exceeded the allowed threshold
-214073342480670010The StateRepository service Stop event is in progress
-214073342380670011Nested transactions are not supported
-214073342280670012The StateRepository cache is not valid
-213896396780820001The bootfile is too small to support persistent snapshots
-213896396680820002Activation of persistent snapshots on this volume took longer than was allowed
-213889843180830001The specified volume does not support storage tiers
-213889843080830002The Storage Tiers Management service detected that the specified volume is in the process of being dismounted
-213889842980830003The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid
-213889842880830004The file identifier specified is not valid on the volume
-213889842780830005Storage tier operations must be called on the clustering node that owns the metadata volume
-213889842680830006The Storage Tiers Management service is already optimizing the storage tiers on the specified volume
-213889842580830007The requested object type cannot be assigned to a storage tier
-213889842480830008The requested file is not pinned to a tier
-213889842380830009The volume is not a tiered volume
-21388984228083000AThe requested attribute is not present on the specified file or directory
-213870182380860001Authentication target is invalid or not configured correctly
-213870182280860002Your application cannot get the Online Id properties due to the Terms of Use accepted by the user
-213870182180860003The application requesting authentication tokens is either disabled or incorrectly configured
-213870182080860004Online Id password must be updated before signin
-213870181980860005Online Id account properties must be updated before signin
-213870181880860006To help protect your Online Id account you must signin again
-213870181780860007Online Id account was locked because there have been too many attempts to sign in
-213870181680860008Online Id account requires parental consent before proceeding
-213870181580860009Online Id signin name is not yet verified. Email verification is required before signin
-21387018148086000AWe have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account
-21387018138086000BWe detected some suspicious activity with your Online Id account. To help protect you
-21387018128086000CUser interaction is required for authentication
-21387018118086000DUser has reached the maximum device associations per user limit
-21387018108086000ECannot sign out from the application since the user account is connected
-21387018098086000FUser authentication is required for this operation
-213870180880860010We want to make sure this is you. User interaction is required for authentication
-213594931180B00001Could not create new process from ARM architecture device
-213594931080B00002Could not attach to the application process from ARM architecture device
-213594930980B00003Could not connect to dbgsrv server from ARM architecture device
-213594930880B00004Could not start dbgsrv server from ARM architecture device
-213234483180E70001The specified fault domain type or combination of minimum / maximum fault domain type is not valid
-213234483080E70002A Storage Spaces internal error occurred
-213234482980E70003The specified resiliency type is not valid
-213234482880E70004The physical disk's sector size is not supported by the storage pool
-213234482680E70006The requested redundancy is outside of the supported range of values
-213234482580E70007The number of data copies requested is outside of the supported range of values
-213234482480E70008The value for ParityLayout is outside of the supported range of values
-213234482380E70009The value for interleave length is outside of the supported range of values or is not a power of 2
-213234482280E7000AThe number of columns specified is outside of the supported range of values
-213234482180E7000BThere were not enough physical disks to complete the requested operation
-213234482080E7000CExtended error information is available
-213234481980E7000DThe specified provisioning type is not valid
-213234481880E7000EThe allocation size is outside of the supported range of values
-213234481780E7000FEnclosure awareness is not supported for this virtual disk
-213234481680E70010The write cache size is outside of the supported range of values
-213234481580E70011The value for number of groups is outside of the supported range of values
-213234481480E70012The OperationalState of the physical disk is invalid for this operation
-213234481380E70013The specified log entry is not complete
-213234481280E70014The specified log entry is not valid
-208948428783750001Unsupported format
-208948428683750002Invalid XML
-208948428583750003Missing required element
-208948428483750004Missing required attribute
-208948428383750005Unexpected content
-208948428283750006Resource too large
-208948428183750007Invalid JSON string
-208948428083750008Invalid JSON number
-208948427983750009JSON value not found
-208941875183760001Invalid operation performed by the protocol
-208941875083760002Invalid data format for the specific protocol operation
-208941874983760003Protocol extensions are not supported
-208941874883760004Subprotocol is not supported
-208941874783760005Incorrect protocol version
-201857433587AF0001SQL error or missing database
-201857433487AF0002Internal logic error in SQLite
-201857433387AF0003Access permission denied
-201857433287AF0004Callback routine requested an abort
-201857433187AF0005The database file is locked
-201857433087AF0006A table in the database is locked
-201857432987AF0007A malloc() failed
-201857432887AF0008Attempt to write a readonly database
-201857432787AF0009Operation terminated by sqlite3_interrupt()
-201857432687AF000ASome kind of disk I/O error occurred
-201857432587AF000BThe database disk image is malformed
-201857432487AF000CUnknown opcode in sqlite3_file_control()
-201857432387AF000DInsertion failed because database is full
-201857432287AF000EUnable to open the database file
-201857432187AF000FDatabase lock protocol error
-201857432087AF0010Database is empty
-201857431987AF0011The database schema changed
-201857431887AF0012String or BLOB exceeds size limit
-201857431787AF0013Abort due to constraint violation
-201857431687AF0014Data type mismatch
-201857431587AF0015Library used incorrectly
-201857431487AF0016Uses OS features not supported on host
-201857431387AF0017Authorization denied
-201857431287AF0018Auxiliary database format error
-201857431187AF00192nd parameter to sqlite3_bind out of range
-201857431087AF001AFile opened that is not a database file
-201857430987AF001BNotifications from sqlite3_log()
-201857430887AF001CWarnings from sqlite3_log()
-201857423687AF0064sqlite3_step() has another row ready
-201857423587AF0065sqlite3_step() has finished executing
-201857407587AF0105SQLITE_BUSY_RECOVERY
-201857407487AF0106SQLITE_LOCKED_SHAREDCACHE
-201857407287AF0108SQLITE_READONLY_RECOVERY
-201857407087AF010ASQLITE_IOERR_READ
-201857406987AF010BSQLITE_CORRUPT_VTAB
-201857406687AF010ESQLITE_CANTOPEN_NOTEMPDIR
-201857406187AF0113SQLITE_CONSTRAINT_CHECK
-201857405387AF011BSQLITE_NOTICE_RECOVER_WAL
-201857405287AF011CSQLITE_WARNING_AUTOINDEX
-201857382087AF0204SQLITE_ABORT_ROLLBACK
-201857381987AF0205SQLITE_BUSY_SNAPSHOT
-201857381687AF0208SQLITE_READONLY_CANTLOCK
-201857381487AF020ASQLITE_IOERR_SHORT_READ
-201857381087AF020ESQLITE_CANTOPEN_ISDIR
-201857380587AF0213SQLITE_CONSTRAINT_COMMITHOOK
-201857379787AF021BSQLITE_NOTICE_RECOVER_ROLLBACK
-201857356087AF0308SQLITE_READONLY_ROLLBACK
-201857355887AF030ASQLITE_IOERR_WRITE
-201857355487AF030ESQLITE_CANTOPEN_FULLPATH
-201857354987AF0313SQLITE_CONSTRAINT_FOREIGNKEY
-201857330487AF0408SQLITE_READONLY_DBMOVED
-201857330287AF040ASQLITE_IOERR_FSYNC
-201857329887AF040ESQLITE_CANTOPEN_CONVPATH
-201857329387AF0413SQLITE_CONSTRAINT_FUNCTION
-201857304687AF050ASQLITE_IOERR_DIR_FSYNC
-201857303787AF0513SQLITE_CONSTRAINT_NOTNULL
-201857279087AF060ASQLITE_IOERR_TRUNCATE
-201857278187AF0613SQLITE_CONSTRAINT_PRIMARYKEY
-201857253487AF070ASQLITE_IOERR_FSTAT
-201857252587AF0713SQLITE_CONSTRAINT_TRIGGER
-201857227887AF080ASQLITE_IOERR_UNLOCK
-201857226987AF0813SQLITE_CONSTRAINT_UNIQUE
-201857202287AF090ASQLITE_IOERR_RDLOCK
-201857201387AF0913SQLITE_CONSTRAINT_VTAB
-201857176687AF0A0ASQLITE_IOERR_DELETE
-201857175787AF0A13SQLITE_CONSTRAINT_ROWID
-201857151087AF0B0ASQLITE_IOERR_BLOCKED
-201857125487AF0C0ASQLITE_IOERR_NOMEM
-201857099887AF0D0ASQLITE_IOERR_ACCESS
-201857074287AF0E0ASQLITE_IOERR_CHECKRESERVEDLOCK
-201857048687AF0F0ASQLITE_IOERR_LOCK
-201857023087AF100ASQLITE_IOERR_CLOSE
-201856997487AF110ASQLITE_IOERR_DIR_CLOSE
-201856971887AF120ASQLITE_IOERR_SHMOPEN
-201856946287AF130ASQLITE_IOERR_SHMSIZE
-201856920687AF140ASQLITE_IOERR_SHMLOCK
-201856895087AF150ASQLITE_IOERR_SHMMAP
-201856869487AF160ASQLITE_IOERR_SEEK
-201856843887AF170ASQLITE_IOERR_DELETE_NOENT
-201856818287AF180ASQLITE_IOERR_MMAP
-201856792687AF190ASQLITE_IOERR_GETTEMPPATH
-201856767887AF1A02SQLITE_IOERR_VNODE
-201856767787AF1A03SQLITE_IOERR_AUTH
-201856767087AF1A0ASQLITE_IOERR_CONVPATH
-201712844787C51001Toggle (alternative) trace started
-201712844687C51002Cannot pre-empt running trace: The current trace has a higher priority
-201712844587C51003The always-on-trace is not running
-201712844487C51004RunScriptAction contains an invalid script type
-201712844387C51005Requested scenario definition cannot be found
-201712844287C51006Requested trace profile cannot be found
-201712844187C51007Trigger forwarder is already enabled
-201712844087C51008Trigger forwarder is already disabled
-201712843987C51009Cannot parse EventLog XML: The entry is malformed
-201712843887C5100A node contains a schemaversion which is not compatible with this client
-201712843787C5100BRunScriptAction was forced to terminate a script
-201712843687C5100CToggleTraceWithCustomFilterAction contains an invalid custom filter
-201712843587C5100DThe trace is not running
-201712843487C5100EA scenario failed to escalate: This scenario has escalated too recently
-201712843387C5100FA scenario failed to escalate: This scenario is already running an escalation
-201712843287C51010Cannot start tracing: PerfTrack component is already tracing
-201712843187C51011A scenario failed to escalate: This scenario has reached max escalations for this escalation type
-201712843087C51012Cannot update forwarder: The forwarder passed to the function is of a different type
-201712842987C51013RunScriptAction failed intentionally to force this escalation to terminate
-201712842887C51014Failed to initialize SQM logger
-201712842787C51015Failed to initialize WER logger: This system does not support WER for UTC
-201712842687C51016The TraceManager has attempted to take a tracing action without initializing tracers
-201712842587C51017WinRT initialization failed
-201712842487C51018 node contains a schemaversion that is not compatible with this client
-201712842387C51019Scenario contains an invalid filter that can never be satisfied
-201712842287C5101ARunExeWithArgsAction was forced to terminate a running executable
-201712842187C5101BEscalation for scenario failed due to insufficient permissions
-201712842087C5101CSetup for scenario failed due to insufficient permissions
-201712841987C5101DA process launched by UTC failed with a non-zero exit code
-201712841887C5101EA RunExeWithArgs action contains an unauthorized command line
-201712841787C5101FUTC cannot load Scenario Editor XML. Convert the scenario file to a DiagTrack XML using the editor
-201712841687C51020Escalation for scenario has timed out
-201712841587C51021Setup for scenario has timed out
-201712841487C51022The given trigger does not match the expected trigger type
-201712841387C51023Requested trigger cannot be found
-201712841287C51024SIF is not supported on the machine
-201712841187C51025The delay action was terminated
-201712841087C51026The device ticket was not obtained
-201712840987C51027The trace profile needs more memory than is available for tracing
-201712840887C51028The API was not completed successfully so the result is unavailable
-201712840787C51029The requested API encountered a timeout in the API manager
-201712840687C5102AThe synchronous API encountered a wait failure
-201712840587C5102BThe UTC API is busy with another request
-201712840487C5102CThe running trace profile does not have a sufficient runtime to fulfill the escalation request
-201712840387C5102DThe trace profile could not be started because it requires exclusivity and another higher priority trace is already running
-201712840287C5102EThe file path is not approved for the GetFile escalation action
-201712840187C5102FThe escalation working directory for the requested escalation could not be created because it already exists
-201712840087C51030Time triggers cannot be used on a transition originating from the "_start" state
-201712839987C51031Time triggers can only be attached to a single transition
-201712839887C51032Time trigger duration must fall within an inclusive range of one second and 15 minutes
-201712839787C51033Only one Time Trigger is allowed per state
-201712839687C51034A RunExeWithArgs action contains a binary which is not present on the targeted device
-201712839487C51036UTC failed to identify the container id to use for a scenario escalation action
-201712839387C51037Failed to resolve session ID during API invocation
-201712839287C51038UTC has throttled the event for firing too often
-201712839187C51039The script is not approved to run as part of DiagTrack scenario
-201712839087C5103AThe script referenced in DiagTrack scenario is not present on the system
-201712838987C5103BA trigger in this scenario is throttled
-201712838887C5103CThe requested UTC API call is not supported on this device
-201712838787C5103DThe file path is not approved for collection on external rings for the GetFile escalation action
-201712838687C5103EQuerying a scenario definition exceeded the specified maximum timeout
-201712838587C5103FCertification revocation checking has been enabled
-201712838487C51040Failed to start NDISCAP service for network packet capture trace
-201712838387C51041UTC can perform no more than one KernelDump action on a device every 24 hours
-201712838287C51042The event contained an aggregation or differential privacy structure
-201712838187C51043The event contained an invalid aggregation or differential privacy structure
-201712838087C51044The action cannot be completed in the specified destination
-201712837987C51045Filter command is missing a required attribute
-201712837887C51046Filter command contains an unsupported type
-201712837787C51047Filter variable does not exist at point of evaluation
-201712837687C51048Filter command is not allowed in the current context
-201712837587C51049Requested filter version is incompatible with available version
-201712836887C51050Filter does not support this function
-201712836787C51051Filter function does not accept the provided parameter types and/or count
-201712836687C51052Filter command does not exist or is incorrectly formatted
-201712836587C51053Filter types can not be compared to each other
-201712836487C51054TTTracer executable returned a code other than ERROR_SUCCESS
-201712836387C51055The total size of the compressed escalation data payload exceeded the allowable limit
-201712836287C51056Escalation data was not completely transferred from agent to host
-201712836187C51057An escalation was requested for a scenario which has no actions for the passed type
-201712836087C51058UTC allocated space for TTTracer escalations is full
-201712835987C51059Disk needs minimum of 15GB to start TTD recording session
-201712835887C5105AEscalation was cancelled due to component shutdown
-201712835787C5105BThe file for the GetFileInfo action must be under the \Windows
-201712835687C5105CThe registry value type for SetRegKey action must be REG_SZ
-201320038388010001One or more fixed volumes are not provisioned with the 3rd party encryption providers to support device encryption. Enable encryption with the 3rd party provider to comply with policy
-201320038288010002This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption
-201320038188010003This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider
-201320038088010004This computer cannot support device encryption because the requisites for the device lock feature are not configured
-201320037988010005Protection is enabled on this volume but is not in the active state
-201320037888010006The 3rd party provider has been installed
-201320037788010007The operating system drive is not protected by 3rd party drive encryption
-201320037688010008Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin
-201320037588010009The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large
-20130897918802B001The file size is larger than supported by the sync engine
-20130897908802B002The file cannot be uploaded because it doesn't fit in the user's available service provided storage space
-20130897898802B003The file name contains invalid characters
-20130897888802B004The maximum file count has been reached for this folder in the sync engine
-20130897878802B005The file sync has been delegated to another program and has run into an issue
-20130897868802B006Sync has been delayed due to a throttling request from the service
-20130856948802C002We can't seem to find that file. Please try again later
-20130856938802C003The account you're signed in with doesn't have permission to open this file
-20130856928802C004There was a problem connecting to the service. Please try again later
-20130856918802C005Sorry
-20130856908802C006We're having trouble downloading the file right now. Please try again later
-20130856898802C007We're having trouble downloading the file right now. Please try again later
-20130815998802D001The sync engine does not have permissions to access a local folder under the sync root
-20130815988802D002The folder name contains invalid characters
-20130815978802D003The sync engine is not allowed to run in your current market
-20130815968802D004All files and folders can't be uploaded because a path of a file or folder is too long
-20130815958802D005All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit
-20130815948802D006Updates are needed in order to use the sync engine
-20130815938802D007The sync engine needs to authenticate with a proxy server
-20130815928802D008There was a problem setting up the storage services for the account
-20130815918802D009Files can't be uploaded because there's an unsupported reparse point
-20130815908802D00AThe service has blocked your account from accessing the storage service
-20130815898802D00BThe action can't be performed right now because this folder is being moved. Please try again later
-200533606388790001The application has exceeded the maximum number of unique state objects per Direct3D device.The limit is 4096 for feature levels up to 11.1
-200533606288790002The specified file was not found
-2005270527887A0001The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect.Enable the D3D debug layer in order to see details via debug messages
-2005270526887A0002The object was not found. If calling IDXGIFactory::EnumAdaptes
-2005270525887A0003The caller did not supply a sufficiently large buffer
-2005270524887A0004The specified device interface or feature level is not supported on this system
-2005270523887A0005The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action
-2005270522887A0006The GPU will not respond to more commands
-2005270521887A0007The GPU will not respond to more commands
-2005270518887A000AThe GPU was busy at the moment when the call was made
-2005270517887A000BAn event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should beconsidered invalid
-2005270516887A000CFullscreen mode could not be achieved because the specified output was already in use
-2005270496887A0020An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect
-2005270495887A0021A global counter resource was in use
-2005270494887A0022A resource is not available at the time of the call
-2005270493887A0023The application's remote device has been removed due to session disconnect or network disconnect.The application should call IDXGIFactory1::IsCurrent to find out when the remote device becomes available again
-2005270492887A0024The device has been removed during a remote session because the remote computer ran out of memory
-2005270491887A0025An on-going mode change prevented completion of the call. The call may succeed if attempted later
-2005270490887A0026The keyed mutex was abandoned
-2005270489887A0027The timeout value has elapsed and the resource is not yet available
-2005270488887A0028The output duplication has been turned off because the Windows session ended or was disconnected.This happens when a remote user disconnects
-2005270487887A0029The DXGI output (monitor) to which the swapchain content was restricted
-2005270486887A002ADXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver
-2005270485887A002BThe application is trying to use a resource to which it does not have the required access privileges.This is most commonly caused by writing to a shared resource with read-only access
-2005270484887A002CThe application is trying to create a shared handle using a name that is already associated with some other resource
-2005270483887A002DThe application requested an operation that depends on an SDK component that is missing or mismatched
-2005270482887A002EThe DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed
-2005270480887A0030Insufficient HW protected memory exits for proper function
-2005270479887A0031Creating this device would violate the process's dynamic code policy
-2005270478887A0032The operation failed because the compositor is not in control of the output
-2005270477887A0033The cache is corrupt and either could not be opened or could not be reset
-2005270476887A0034This entry would cause the cache to exceed its quota. On a load operation
-2005270475887A0035A cache entry was found
-2005270474887A0036The desired element already exists
-2005204991887B0001The GPU was busy when the operation was requested
-2005204990887B0002The driver has rejected the creation of this resource
-2005204989887B0003The GPU counter was in use by another process or d3d device when application requested access to it
-2005139455887C0001The application has exceeded the maximum number of unique state objects per Direct3D device.The limit is 4096 for feature levels up to 11.1
-2005139454887C0002The specified file was not found
-2005139453887C0003The application has exceeded the maximum number of unique view objects per Direct3D device.The limit is 2^20 for feature levels up to 11.1
-2005139452887C0004The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD
-2005008383887E0001The blob provided does not match the adapter that the device was created on
-2005008382887E0002The blob provided was created for a different version of the driver
-2005008381887E0003The D3D12 SDK version configuration of the host exe is invalid
-200487731188800001The application failed to unregister from an event it registered for
-200382873588900001The device is invalid or does not support machine learning
-200382873488900002The binding is incomplete or does not match the input/output description
-200382873388900003An attempt was made to bind an unknown input or output
-200382873288900004The size of the buffer provided for a bound variable is invalid
-200330444788980001MILERR_OBJECTBUSY
-200330444688980002MILERR_INSUFFICIENTBUFFER
-200330444588980003MILERR_WIN32ERROR
-200330444488980004MILERR_SCANNER_FAILED
-200330444388980005MILERR_SCREENACCESSDENIED
-200330444288980006MILERR_DISPLAYSTATEINVALID
-200330444188980007MILERR_NONINVERTIBLEMATRIX
-200330444088980008MILERR_ZEROVECTOR
-200330443988980009MILERR_TERMINATED
-20033044388898000AMILERR_BADNUMBER
-200330432088980080An internal error (MIL bug) occurred. On checked builds
-200330431688980084The display format we need to render is not supported by the hardware device
-200330431588980085A call to this method is invalid
-200330431488980086Lock attempted on an already locked object
-200330431388980087Unlock attempted on an unlocked object
-200330431288980088No algorithm available to render text with this device
-200330431188980089Some glyph bitmaps
-20033043108898008ASome glyph bitmaps in glyph cache are unexpectedly big
-20033043098898008BMarker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred
-20033043088898008CGuideline coordinates are not sorted properly or contain NaNs
-20033043078898008DNo HW rendering device is available for this operation
-20033043068898008EThere has been a presentation error that may be recoverable. The caller needs to recreate
-20033043058898008FThe object has already been initialized
-200330430488980090The size of the object does not match the expected size
-200330430388980091No Redirection surface available
-200330430288980092Remoting of this content is not supported
-200330430188980093Queued Presents are not supported
-200330430088980094Queued Presents are not being used
-200330429988980095No redirection surface was available. Caller should retry the call
-200330429888980096Shader construction failed because it was too complex
-200330429788980097MROW attempt to get a read lock failed
-200330429688980098MROW attempt to update the data failed because another update was outstanding
-200330429588980099Shader compilation failed
-20033042948898009ARequested DX redirection surface size exceeded maximum texture size
-20033042938898009BQueryPerformanceCounter returned a time in the past
-20033042918898009DPrimary Display device returned an invalid refresh rate
-20033042908898009EDWM can not find the adapter specified by the LUID
-20033042898898009FThe requested bitmap color space is not supported
-2003304288889800A0The requested bitmap pre-filtering state is not supported
-2003304287889800A1Access is denied to the requested bitmap for the specified display id
-200330342488980400UCEERR_INVALIDPACKETHEADER
-200330342388980401UCEERR_UNKNOWNPACKET
-200330342288980402UCEERR_ILLEGALPACKET
-200330342188980403UCEERR_MALFORMEDPACKET
-200330342088980404UCEERR_ILLEGALHANDLE
-200330341988980405UCEERR_HANDLELOOKUPFAILED
-200330341888980406UCEERR_RENDERTHREADFAILURE
-200330341788980407UCEERR_CTXSTACKFRSTTARGETNULL
-200330341688980408UCEERR_CONNECTIONIDLOOKUPFAILED
-200330341588980409UCEERR_BLOCKSFULL
-20033034148898040AUCEERR_MEMORYFAILURE
-20033034138898040BUCEERR_PACKETRECORDOUTOFRANGE
-20033034128898040CUCEERR_ILLEGALRECORDTYPE
-20033034118898040DUCEERR_OUTOFHANDLES
-20033034108898040EUCEERR_UNCHANGABLE_UPDATE_ATTEMPTED
-20033034098898040FUCEERR_NO_MULTIPLE_WORKER_THREADS
-200330340888980410UCEERR_REMOTINGNOTSUPPORTED
-200330340788980411UCEERR_MISSINGENDCOMMAND
-200330340688980412UCEERR_MISSINGBEGINCOMMAND
-200330340588980413UCEERR_CHANNELSYNCTIMEDOUT
-200330340488980414UCEERR_CHANNELSYNCABANDONED
-200330340388980415UCEERR_UNSUPPORTEDTRANSPORTVERSION
-200330340288980416UCEERR_TRANSPORTUNAVAILABLE
-200330340188980417UCEERR_FEEDBACK_UNSUPPORTED
-200330340088980418UCEERR_COMMANDTRANSPORTDENIED
-200330339988980419UCEERR_GRAPHICSSTREAMUNAVAILABLE
-200330339288980420UCEERR_GRAPHICSSTREAMALREADYOPEN
-200330339188980421UCEERR_TRANSPORTDISCONNECTED
-200330339088980422UCEERR_TRANSPORTOVERLOADED
-200330338988980423UCEERR_PARTITION_ZOMBIED
-200330316888980500MILAVERR_NOCLOCK
-200330316788980501MILAVERR_NOMEDIATYPE
-200330316688980502MILAVERR_NOVIDEOMIXER
-200330316588980503MILAVERR_NOVIDEOPRESENTER
-200330316488980504MILAVERR_NOREADYFRAMES
-200330316388980505MILAVERR_MODULENOTLOADED
-200330316288980506MILAVERR_WMPFACTORYNOTREGISTERED
-200330316188980507MILAVERR_INVALIDWMPVERSION
-200330316088980508MILAVERR_INSUFFICIENTVIDEORESOURCES
-200330315988980509MILAVERR_VIDEOACCELERATIONNOTAVAILABLE
-20033031588898050AMILAVERR_REQUESTEDTEXTURETOOBIG
-20033031578898050BMILAVERR_SEEKFAILED
-20033031568898050CMILAVERR_UNEXPECTEDWMPFAILURE
-20033031558898050DMILAVERR_MEDIAPLAYERCLOSED
-20033031548898050EMILAVERR_UNKNOWNHARDWAREERROR
-20033028988898060EMILEFFECTSERR_UNKNOWNPROPERTY
-20033028978898060FMILEFFECTSERR_EFFECTNOTPARTOFGROUP
-200330289688980610MILEFFECTSERR_NOINPUTSOURCEATTACHED
-200330289588980611MILEFFECTSERR_CONNECTORNOTCONNECTED
-200330289488980612MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT
-200330289388980613MILEFFECTSERR_RESERVED
-200330289288980614MILEFFECTSERR_CYCLEDETECTED
-200330289188980615MILEFFECTSERR_EFFECTINMORETHANONEGRAPH
-200330289088980616MILEFFECTSERR_EFFECTALREADYINAGRAPH
-200330288988980617MILEFFECTSERR_EFFECTHASNOCHILDREN
-200330288888980618MILEFFECTSERR_ALREADYATTACHEDTOLISTENER
-200330288788980619MILEFFECTSERR_NOTAFFINETRANSFORM
-20033028868898061AMILEFFECTSERR_EMPTYBOUNDS
-20033028858898061BMILEFFECTSERR_OUTPUTSIZETOOLARGE
-200330265688980700DWMERR_STATE_TRANSITION_FAILED
-200330265588980701DWMERR_THEME_FAILED
-200330265488980702DWMERR_CATASTROPHIC_FAILURE
-200330240088980800DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED
-200330239988980801DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED
-200330239888980802DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED
-200329241288982F04The codec is in the wrong state
-200329241188982F05The value is out of range
-200329240988982F07The image format is unknown
-200329240588982F0BThe SDK version is unsupported
-200329240488982F0CThe component is not initialized
-200329240388982F0DThere is already an outstanding read or write lock
-200329235288982F40The specified bitmap property cannot be found
-200329235188982F41The bitmap codec does not support the bitmap property
-200329235088982F42The bitmap property size is invalid
-200329234988982F43An unknown error has occurred
-200329234888982F44The bitmap codec does not support a thumbnail
-200329234788982F45The bitmap palette is unavailable
-200329234688982F46Too many scanlines were requested
-200329234488982F48An internal error occurred
-200329234388982F49The bitmap bounds do not match the bitmap dimensions
-200329233688982F50The component cannot be found
-200329233588982F51The bitmap size is outside the valid range
-200329233488982F52There is too much metadata to be written to the bitmap
-200329232088982F60The image is unrecognized
-200329231988982F61The image header is unrecognized
-200329231888982F62The bitmap frame is missing
-200329231788982F63The image metadata header is unrecognized
-200329230488982F70The stream data is unrecognized
-200329230388982F71Failed to write to the stream
-200329230288982F72Failed to read from the stream
-200329230188982F73The stream is not available
-200329228888982F80The bitmap pixel format is unsupported
-200329228788982F81The operation is unsupported
-200329227888982F8AThe component registration is invalid
-200329227788982F8BThe component initialization has failed
-200329227688982F8CThe buffer allocated is insufficient
-200329227588982F8DDuplicate metadata is present
-200329227488982F8EThe bitmap property type is unexpected
-200329227388982F8FThe size is unexpected
-200329227288982F90The property query is invalid
-200329227188982F91The metadata type is unexpected
-200329227088982F92The specified bitmap property is only valid at root level
-200329226988982F93The query string contains an invalid character
-200329226888982F94Windows Codecs received an error from the Win32 system
-200329226788982F95The requested level of detail is not present
-200329226688982F96The scan index is invalid
-200328396888985000Indicates an error in an input file such as a font file
-200328396788985001Indicates an error originating in DirectWrite code
-200328396688985002Indicates the specified font does not exist
-200328396588985003A font file could not be opened because the file
-200328396488985004A font file exists but could not be opened due to access denied
-200328396388985005A font collection is obsolete due to changes in the system
-200328396288985006The given interface is already registered
-200328396188985007The font cache contains invalid data
-200328396088985008A font cache file corresponds to a different version of DirectWrite
-200328395988985009The operation is not supported for this type of font
-20032839588898500AThe version of the text renderer interface is not compatible
-20032839578898500BThe flow direction conflicts with the reading direction. They must be perpendicular to each other
-20032839568898500CThe font or glyph run does not contain any colored glyphs
-20032839558898500DA font resource could not be accessed because it is remote
-20032839548898500EA font download was canceled
-20032839538898500FA font download failed
-200328395288985010A font download request was not added or a download failed because there are too many active downloads
-200323891188990001The object was not in the correct state to process the method
-200323891088990002The object has not yet been initialized
-200323890988990003The requested operation is not supported
-200323890888990004The geometry scanner failed to process the data
-200323890788990005Direct2D could not access the screen
-200323890688990006A valid display state could not be determined
-200323890588990007The supplied vector is zero
-200323890488990008An internal error (Direct2D bug) occurred. On checked builds
-200323890388990009The display format Direct2D needs to render is not supported by the hardware device
-20032389028899000AA call to this method is invalid
-20032389018899000BNo hardware rendering device is available for this operation
-20032389008899000CThere has been a presentation error that may be recoverable. The caller needs to recreate
-20032388998899000DShader construction failed because it was too complex
-20032388988899000EShader compilation failed
-20032388978899000FRequested DirectX surface size exceeded maximum texture size
-200323889688990010The requested Direct2D version is not supported
-200323889588990011Invalid number
-200323889488990012Objects used together must be created from the same factory instance
-200323889388990013A layer resource can only be in use once at any point in time
-200323889288990014The pop call did not match the corresponding push call
-200323889188990015The resource was realized on the wrong render target
-200323889088990016The push and pop calls were unbalanced
-200323888988990017Attempt to copy from a render target while a layer or clip rect is applied
-200323888888990018The brush types are incompatible for the call
-200323888788990019An unknown win32 failure occurred
-20032388868899001AThe render target is not compatible with GDI
-20032388858899001BA text client drawing effect object is of the wrong type
-20032388848899001CThe application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid
-20032388838899001DThe requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level
-20032388828899001EThere was a configuration error in the graph
-20032388818899001FThere was a internal configuration error in the graph
-200323888088990020There was a cycle in the graph
-200323887988990021Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option
-200323887888990022The operation cannot complete while there are outstanding references to the target bitmap
-200323887788990023The operation failed because the original target is not currently bound as a target
-200323887688990024Cannot set the image as a target because it is either an effect or is a bitmap that does not have the D2D1_BITMAP_OPTIONS_TARGET flag set
-200323887588990025Cannot draw with a bitmap that is currently bound as the target bitmap
-200323887488990026D3D Device does not have sufficient capabilities to perform the requested action
-200323887388990027The graph could not be rendered with the context's current tiling settings
-200323887288990028The CLSID provided to Unregister did not correspond to a registered effect
-200323887188990029The specified property does not exist
-20032388708899002AThe specified sub-property does not exist
-20032388698899002BAddPage or Close called after print job is already closed
-20032388688899002CError during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control
-20032388678899002DAn effect attempted to use a transform with too many inputs
-20032388668899002EAn error was encountered while decoding or parsing the requested glyph image
-199642316789010001The operation was preempted by a higher priority operation. It must be resumed later
-199635763189020001Function could not execute because it was deleted or garbage collected
-1073151999C0090001The specified event is currently not being audited
-1073151998C0090002The SID filtering operation removed all SIDs
-1073151997C0090003Business rule scripts are disabled for the calling application
-1072875856C00D36B0Platform not initialized. Please call MFStartup()
-1072875855C00D36B1The buffer was too small to carry out the requested action
-1072875854C00D36B2The request is invalid in the current state
-1072875853C00D36B3The stream number provided was invalid
-1072875852C00D36B4The data specified for the media type is invalid
-1072875851C00D36B5The callee is currently not accepting further input
-1072875850C00D36B6This object needs to be initialized before the requested operation can be carried out
-1072875849C00D36B7The requested representation is not supported by this object
-1072875847C00D36B9An object ran out of media types to suggest therefore the requested chain of streaming objects cannot be completed
-1072875846C00D36BAThe object does not support the specified service
-1072875845C00D36BBAn unexpected error has occurred in the operation requested
-1072875844C00D36BCInvalid name
-1072875843C00D36BDInvalid type
-1072875842C00D36BEThe file does not conform to the relevant file format specification
-1072875841C00D36BFInvalid index
-1072875840C00D36C0An invalid timestamp was given
-1072875837C00D36C3The scheme of the given URL is unsupported
-1072875836C00D36C4The byte stream type of the given URL is unsupported
-1072875835C00D36C5The given time format is unsupported
-1072875832C00D36C8The Media Sample does not have a timestamp
-1072875831C00D36C9The Media Sample does not have a duration
-1072875829C00D36CBThe request failed because the data in the stream is corrupt
-1072875825C00D36CFReal time services are not available
-1072875824C00D36D0The specified rate is not supported
-1072875823C00D36D1This component does not support stream-thinning
-1072875822C00D36D2The call failed because no reverse playback rates are available
-1072875821C00D36D3The requested rate transition cannot occur in the current state
-1072875820C00D36D4The requested rate change has been pre-empted and will not occur
-1072875819C00D36D5The specified object or value does not exist
-1072875818C00D36D6The requested value is not available
-1072875817C00D36D7The specified operation requires a clock and no clock is available
-1072875815C00D36D9This callback has already been passed in to this event generator
-1072875814C00D36DASome component is already listening to events on this event generator
-1072875813C00D36DBThis timer was orphaned before its callback time arrived
-1072875812C00D36DCA state transition is already pending
-1072875811C00D36DDThe requested state transition is unsupported
-1072875810C00D36DEAn unrecoverable error has occurred
-1072875809C00D36DFThe provided sample has too many buffers
-1072875808C00D36E0The provided sample is not writable
-1072875806C00D36E2The specified key is not valid
-1072875805C00D36E3You are calling MFStartup with the wrong MF_VERSION. Mismatched bits?
-1072875804C00D36E4The caption of the given URL is unsupported
-1072875803C00D36E5The operation on the current offset is not permitted
-1072875802C00D36E6The requested attribute was not found
-1072875801C00D36E7The specified property type is not allowed in this context
-1072875800C00D36E8The specified property type is not supported
-1072875799C00D36E9The specified property is empty
-1072875798C00D36EAThe specified property is not empty
-1072875797C00D36EBThe vector property specified is not allowed in this context
-1072875796C00D36ECA vector property is required in this context
-1072875795C00D36EDThe operation is cancelled
-1072875794C00D36EEThe provided bytestream was expected to be seekable and it is not
-1072875793C00D36EFThe Media Foundation platform is disabled when the system is running in Safe Mode
-1072875792C00D36F0The Media Source could not parse the byte stream
-1072875791C00D36F1Mutually exclusive flags have been specified to source resolver. This flag combination is invalid
-1072875790C00D36F2MediaProc is in the wrong state
-1072875789C00D36F3Real time I/O service can not provide requested throughput
-1072875788C00D36F4The workqueue cannot be registered with more classes
-1072875787C00D36F5This operation cannot succeed because another thread owns this object
-1072875786C00D36F6Internal. Bitpump not found
-1072875785C00D36F7No more RT memory available
-1072875784C00D36F8An MMCSS class has not been set for this work queue
-1072875782C00D36FAActivate failed to create mediasink. Call OutputNode::GetUINT32(MF_TOPONODE_MAJORTYPE) for more information
-1072875781C00D36FBThe length of the provided bytestream is unknown
-1072875780C00D36FCThe media session cannot pause from a stopped state
-1072875778C00D36FEThe data specified for the media type is supported
-1072875777C00D36FFThe operation failed because an invalid combination of workqueue ID and flags was specified
-1072875776C00D3700No DRM support is available
-1072875775C00D3701This operation is not authorized
-1072875774C00D3702The value is not in the specified or valid range
-1072875773C00D3703The registered codec merit is not valid
-1072875772C00D3704Hardware MFT failed to start streaming due to lack of hardware resources
-1072875771C00D3705The operation is already in progress
-1072875770C00D3706No Hardware DRM support is available
-1072875769C00D3707The specified duration is too long
-1072875768C00D3708The attempted call or command is not supported with the DirectX version used by the component
-1072875767C00D3709The specified media type is not supported with the DirectX version used by the component
-1072874856C00D3A98Not enough data have been parsed to carry out the requested action
-1072874855C00D3A99There is a gap in the ASF data provided
-1072874854C00D3A9AThe data provided are not valid ASF
-1072874853C00D3A9BThe packet is opaque
-1072874852C00D3A9CThe requested operation failed since there is no appropriate ASF index
-1072874851C00D3A9DThe value supplied is out of range for this operation
-1072874850C00D3A9EThe index entry requested needs to be loaded before it can be available
-1072874849C00D3A9FThe packet has reached the maximum number of payloads
-1072874848C00D3AA0Stream type is not supported
-1072874847C00D3AA1One or more ASF packets were dropped
-1072873856C00D3E80There are no events available in the queue
-1072873854C00D3E82A media source cannot go from the stopped state to the paused state
-1072873852C00D3E84The media stream cannot process any more samples because there are no more samples in the stream
-1072873851C00D3E85The request is invalid because Shutdown() has been called
-1072873850C00D3E86The MP3 object was not found
-1072873849C00D3E87The MP3 parser ran out of data before finding the MP3 object
-1072873848C00D3E88The file is not really a MP3 file
-1072873847C00D3E89The MP3 file is not supported
-1072873846C00D3E8AThe Media stream has no duration
-1072873844C00D3E8CThe Media format is recognized but is invalid
-1072873843C00D3E8DThe property requested was not found
-1072873842C00D3E8EThe property is read only
-1072873841C00D3E8FThe specified property is not allowed in this context
-1072873839C00D3E91The media source is not started
-1072873832C00D3E98The Media format is recognized but not supported
-1072873831C00D3E99The MPEG frame has bad CRC
-1072873830C00D3E9AThe file is not protected
-1072873829C00D3E9BThe media source is in the wrong state
-1072873828C00D3E9CNo streams are selected in source presentation descriptor
-1072873827C00D3E9DNo key frame sample was found
-1072873826C00D3E9EThe characteristics of the media source are not supported
-1072873825C00D3E9FNo audio recording device was found
-1072873824C00D3EA0The requested audio recording device is currently in use
-1072873823C00D3EA1The audio recording device is no longer present
-1072873822C00D3EA2The video recording device is no longer present
-1072873821C00D3EA3The video recording device is preempted by another immersive application
-1072872856C00D4268An attempt to acquire a network resource failed
-1072872855C00D4269Error writing to the network
-1072872854C00D426AError reading from the network
-1072872853C00D426BInternal. Entry cannot complete operation without network
-1072872852C00D426CInternal. Async op is required
-1072872851C00D426DInternal. Bandwidth levels are not supported
-1072872850C00D426EInternal. Stream groups are not supported
-1072872849C00D426FManual stream selection is not supported
-1072872848C00D4270Invalid presentation descriptor
-1072872847C00D4271Cannot find cache stream
-1072872844C00D4274Internal. Entry cannot complete operation without input
-1072872843C00D4275The client redirected to another server
-1072872842C00D4276The client is redirected to a proxy server
-1072872841C00D4277The client reached maximum redirection limit
-1072872840C00D4278The server
-1072872839C00D4279The control socket is closed by the client
-1072872838C00D427AThe server received invalid data from the client on the control connection
-1072872837C00D427BThe server is not a compatible streaming media server
-1072872836C00D427CUrl
-1072872835C00D427DData is not available
-1072872834C00D427EEnd of line
-1072872833C00D427FThe request could not be understood by the server
-1072872832C00D4280The server encountered an unexpected condition which prevented it from fulfilling the request
-1072872831C00D4281Session not found
-1072872830C00D4282There is no connection established with the Windows Media server. The operation failed
-1072872829C00D4283The network connection has failed
-1072872828C00D4284The Server service that received the HTTP push request is not a compatible version of Windows Media Services (WMS). This error may indicate the push request was received by IIS instead of WMS. Ensure WMS is started and has the HTTP Server control protocol properly enabled and try again
-1072872827C00D4285The Windows Media server is denying access. The username and/or password might be incorrect
-1072872826C00D4286The proxy server is denying access. The username and/or password might be incorrect
-1072872825C00D4287Unable to establish a connection to the server
-1072872824C00D4288The specified push template is invalid
-1072872823C00D4289The specified push publishing point is invalid
-1072872822C00D428AThe requested resource is in use
-1072872821C00D428BThe Publishing Point or file on the Windows Media Server is no longer available
-1072872820C00D428CThe proxy experienced an error while attempting to contact the media server
-1072872819C00D428DThe proxy did not receive a timely response while attempting to contact the media server
-1072872818C00D428EThe server is currently unable to handle the request due to a temporary overloading or maintenance of the server
-1072872817C00D428FThe encoding process was unable to keep up with the amount of supplied data
-1072872816C00D4290Session not found
-1072872815C00D4291The requested URL is not available in offline mode
-1072872814C00D4292A device in the network is blocking UDP traffic
-1072872813C00D4293The specified configuration value is not supported
-1072872812C00D4294The networking protocol is disabled
-1072872811C00D4295The companion driver asked the OS to disconnect from the receiver
-1072871856C00D4650This object has already been initialized and cannot be re-initialized at this time
-1072871855C00D4651The amount of data passed in exceeds the given bitrate and buffer window
-1072871854C00D4652The sample was passed in too late to be correctly processed
-1072871853C00D4653The requested action cannot be carried out until the object is flushed and the queue is emptied
-1072871852C00D4654The profile is invalid
-1072871851C00D4655The index that is being generated needs to be committed before the requested action can be carried out
-1072871850C00D4656The index that is necessary for the requested action is not found
-1072871849C00D4657The requested index cannot be added in-place to the specified ASF content
-1072871848C00D4658The ASF leaky bucket parameters must be specified in order to carry out this request
-1072871847C00D4659The stream id is invalid. The valid range for ASF stream id is from 1 to 127
-1072870856C00D4A38The requested Stream Sink has been removed and cannot be used
-1072870854C00D4A3AThe various Stream Sinks in this Media Sink are too far out of sync for the requested action to take place
-1072870853C00D4A3BStream Sinks cannot be added to or removed from this Media Sink because its set of streams is fixed
-1072870852C00D4A3CThe given Stream Sink already exists
-1072870851C00D4A3DSample allocations have been canceled
-1072870850C00D4A3EThe sample allocator is currently empty
-1072870849C00D4A3FWhen we try to stop a stream sink
-1072870848C00D4A40The ASF file sink could not reserve AVIO because the bitrate is unknown
-1072870847C00D4A41No streams are selected in sink presentation descriptor
-1072870845C00D4A43A metadata item was too long to write to the output container
-1072870844C00D4A44The operation failed because no samples were processed by the sink
-1072870843C00D4A45Sink could not create valid output file because required headers were not provided to the sink
-1072869856C00D4E20There is no available procamp hardware with which to perform color correction
-1072869855C00D4E21There is no available deinterlacing hardware with which to deinterlace the video stream
-1072869854C00D4E22A video stream requires copy protection to be enabled
-1072869853C00D4E23A component is attempting to access a surface for sharing that is not shared
-1072869852C00D4E24A component is attempting to access a shared device that is already locked by another component
-1072869851C00D4E25The device is no longer available. The handle should be closed and a new one opened
-1072869850C00D4E26A video sample is not currently queued on a stream that is required for mixing
-1072869756C00D4E84No audio playback device was found
-1072869755C00D4E85The requested audio playback device is currently in use
-1072869754C00D4E86The audio playback device is no longer present
-1072869753C00D4E87The audio service is not running
-1072869752C00D4E88The audio renderer encountered an error trying to set the render buffer size
-1072869751C00D4E89The audio renderer encountered an error trying spoof the invalidated audio client
-1072868850C00D520EThe topology contains an invalid optional node. Possible reasons are incorrect number of outputs and inputs or optional node is at the beginning or end of a segment
-1072868847C00D5211No suitable transform was found to decrypt the content
-1072868846C00D5212No suitable transform was found to encode or decode the content
-1072868845C00D5213Unable to find a way to connect nodes
-1072868844C00D5214Unsupported operations in topoloader
-1072868843C00D5215The topology or its nodes contain incorrectly set time attributes
-1072868842C00D5216The topology contains loops
-1072868841C00D5217A source stream node in the topology does not have a presentation descriptor
-1072868840C00D5218A source stream node in the topology does not have a stream descriptor
-1072868839C00D5219A stream descriptor was set on a source stream node but it was not selected on the presentation descriptor
-1072868838C00D521AA source stream node in the topology does not have a source
-1072868837C00D521BThe topology loader does not support sink activates on output nodes
-1072864852C00D61ACThe sequencer cannot find a segment with the given ID
-1072864850C00D61AECannot find source in source cache
-1072861856C00D6D60A valid type has not been set for this stream or a stream that it depends on
-1072861855C00D6D61A stream change has occurred. Output cannot be produced until the streams have been renegotiated
-1072861854C00D6D62The transform cannot take the requested action until all of the input data it currently holds is processed or flushed
-1072861853C00D6D63The transform requires a profile but no profile was supplied or found
-1072861852C00D6D64The transform requires a profile but the supplied profile was invalid or corrupt
-1072861851C00D6D65The transform requires a profile but the supplied profile ended unexpectedly while parsing
-1072861850C00D6D66The property ID does not match any property supported by the transform
-1072861849C00D6D67The variant does not have the type expected for this property ID
-1072861848C00D6D68An attempt was made to set the value on a read-only property
-1072861847C00D6D69The array property value has an unexpected number of dimensions
-1072861846C00D6D6AThe array or blob property value has an unexpected size
-1072861845C00D6D6BThe property value is out of range for this transform
-1072861844C00D6D6CThe property value is incompatible with some other property or mediatype set on the transform
-1072861843C00D6D6DThe requested operation is not supported for the currently set output mediatype
-1072861842C00D6D6EThe requested operation is not supported for the currently set input mediatype
-1072861841C00D6D6FThe requested operation is not supported for the currently set combination of mediatypes
-1072861840C00D6D70The requested feature is not supported in combination with some other currently enabled feature
-1072861838C00D6D72The transform cannot produce output until it gets more input samples
-1072861837C00D6D73The requested operation is not supported for the current speaker configuration
-1072861836C00D6D74The transform cannot accept mediatype changes in the middle of processing
-1072861834C00D6D76The input type is not supported for D3D device
-1072861833C00D6D77The caller does not appear to support this transform's asynchronous capabilities
-1072861832C00D6D78An audio compression manager driver could not be initialized by the transform
-1072861831C00D6D79The input stream has invalid and illegal resolution. Output should stop on next ProcessOutput call after the invalid and illegal resolution is detected
-1072861830C00D6D7AThe transform cannot be asynchronous in current context
-1072861828C00D6D7CIt is not supported in the current context to have the transform copy attributes from an input sample to an output sample
-1072860856C00D7148You are not allowed to open this file. Contact the content provider for further assistance
-1072860855C00D7149The license for this media file has expired. Get a new license or contact the content provider for further assistance
-1072860854C00D714AYou need a license to perform the requested operation on this media file
-1072860853C00D714BThe licenses for your media files are corrupted. Contact Microsoft product support
-1072860852C00D714CThe APP needs to provide IMFContentProtectionManager callback to access the protected media file
-1072860851C00D714DClient does not have rights to restore licenses
-1072860850C00D714ELicenses are restricted and hence can not be backed up
-1072860849C00D714FLicense restore requires machine to be individualized
-1072860847C00D7151Component is revoked
-1072860846C00D7152Trusted functionality is currently disabled on this component
-1072860845C00D7153No Action is set on WMDRM Output Trust Authority
-1072860844C00D7154Action is already set on WMDRM Output Trust Authority
-1072860843C00D7155DRM Heaader is not available
-1072860842C00D7156Current encryption scheme is not supported
-1072860841C00D7157Action does not match with current configuration
-1072860840C00D7158Invalid policy for WMDRM Output Trust Authority
-1072860839C00D7159The policies that the Input Trust Authority requires to be enforced are unsupported by the outputs
-1072860838C00D715AThe OPL that the license requires to be enforced are not supported by the Input Trust Authority
-1072860837C00D715BThe topology could not be successfully verified
-1072860836C00D715CSignature verification could not be completed successfully for this component
-1072860835C00D715DRunning this process under a debugger while using protected content is not allowed
-1072860834C00D715EMF component has expired
-1072860833C00D715FThe current GRL on the machine does not meet the minimum version requirements
-1072860832C00D7160The current GRL on the machine does not contain any renewal entries for the specified revocation
-1072860831C00D7161The current GRL on the machine does not contain any extensible entries for the specified extension GUID
-1072860830C00D7162The kernel isn't secure for high security level content
-1072860829C00D7163The response from protected environment driver isn't valid
-1072860827C00D7165A non-PE process tried to talk to PEAuth
-1072860825C00D7167We need to reboot the machine
-1072860822C00D716AThe GRL file is not correctly formed
-1072860821C00D716BThe GRL file is in a format newer than those recognized by this GRL Reader
-1072860820C00D716CThe GRL was reloaded and required all processes that can run protected media to restart
-1072860819C00D716DThe GRL was reloaded and the current process needs to restart
-1072860818C00D716EThe user space is untrusted for protected content play
-1072860817C00D716FPEAuth communication session hasn't been started
-1072860816C00D7170Insufficient memory for response
-1072860815C00D7171PEAuth's public key is revoked
-1072860814C00D7172The GRL is absent
-1072860812C00D7174The Protected Environment is untrusted
-1072860811C00D7175The Protected Environment Authorization service (PEAUTH) has not been started
-1072860810C00D7176The sample protection algorithms supported by components are not compatible
-1072860809C00D7177No more protected environment sessions can be supported
-1072860808C00D7178WMDRM ITA does not allow protected content with high security level for this release
-1072860807C00D7179WMDRM ITA cannot allow the requested action for the content as one or more components is not properly signed
-1072860806C00D717AWMDRM ITA does not support the requested action
-1072860805C00D717BWMDRM ITA encountered an error in parsing the Secure Audio Path parameters
-1072860804C00D717CThe Policy Manager action passed in is invalid
-1072860803C00D717DThe structure specifying Output Protection Level is not the correct format
-1072860802C00D717EWMDRM ITA does not recognize the Explicite Analog Video Output Protection guid specified in the license
-1072860801C00D717FIMFPMPHost object not available
-1072860800C00D7180WMDRM ITA could not initialize the Output Protection Level data
-1072860799C00D7181WMDRM ITA does not recognize the Analog Video Output specified by the OTA
-1072860798C00D7182WMDRM ITA does not recognize the Digital Video Output specified by the OTA
-1072860797C00D7183The protected stream cannot be resolved without the callback PKEY_PMP_Creation_Callback in the configuration property store
-1072860796C00D7184A valid hostname and port number could not be found in the DTCP parameters
-1072860795C00D7185The content protection system was not enabled by the application
-1072860794C00D7186The content protection system is not supported
-1072860793C00D7187DRM migration is not supported for the content
-1072860792C00D7188Authentication of the HDCP link failed
-1072860791C00D7189The HDCP link failed after being established
-1072849856C00D9C40The continuity key supplied is not currently valid
-1072849855C00D9C41No Presentation Time Source has been specified
-1072849854C00D9C42The clock is already in the requested state
-1072849853C00D9C43The clock has too many advanced features to carry out the request
-1072848856C00DA028The component does not support any more drop modes
-1072848855C00DA029The component does not support any more quality levels
-1072848854C00DA02AThe component does not support drop time functionality
-1072848853C00DA02BQuality Manager needs to wait longer before bumping the Quality Level up
-1072848852C00DA02CQuality Manager is in an invalid state. Quality Management is off at this moment
-1072847856C00DA410No transcode output container type is specified
-1072847855C00DA411The profile does not have a media type configuration for any selected source streams
-1072847854C00DA412Cannot find an encoder MFT that accepts the user preferred output type
-1072847853C00DA413The profile is invalid
-1072846856C00DA7F8Memory allocator is not initialized
-1072846855C00DA7F9Memory allocator is not committed yet
-1072846854C00DA7FAMemory allocator has already been committed
-1072846853C00DA7FBAn error occurred in media stream
-1072846852C00DA7FCStream is not in a state to handle the request
-1072846851C00DA7FDHardware stream is not connected yet
-1072845856C00DABE0No capture devices are available
-1072845855C00DABE1No output was set for recording
-1072845854C00DABE2The current capture sink configuration does not support mirroring
-1072845853C00DABE3The current capture sink configuration does not support rotation
-1072845852C00DABE4The op is invalid
-1072845851C00DABE5The effects previously added were incompatible with the new topology which caused all effects to be removed
-1072845850C00DABE6The current capture source does not have an independent photo stream
-1072845849C00DABE7The current capture source does not have a video stream
-1072845848C00DABE8The current capture source does not have an audio stream
-1072845847C00DABE9The capture source device has an asynchronous extended property operation in progress
-1072845846C00DABEAA property cannot be set because a photo or photo sequence is in progress
-1072845845C00DABEBNo more samples in queue
-1072845844C00DABECHardware accelerated thumbnail generation is not supported for the currently selected mediatype on the mediacapture stream
-1072845843C00DABEDCapture device that is present on the system is not supported by Media Foundation
-1072844856C00DAFC8Media Source type is not supported in Media Timeline Controller scenarios
-1072844855C00DAFC9Operation is not allowed when Media Timeline Controller is attached
-1072844854C00DAFCAAttaching Media Timeline Controller is blocked because of the current state of the object
-1072843856C00DB3B0Connection to app service providing a media extension failed
-1072843855C00DB3B1App service providing a media extension failed to process the request
-1072843854C00DB3B2Package integrity check for app failed
-1072843853C00DB3B3License check for app failed
-1071249944C02605E8The 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
-1071247357C0261003Checksum of the obtained monitor descriptor is invalid
-1071247356C0261004Monitor descriptor contains an invalid standard timing block
-1071247355C0261005WMI data block registration failed for one of the MSMonitorClass WMI subclasses
-1071247354C0261006Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number
-1071247353C0261007Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name
-1071247352C0261008There is no monitor descriptor data at the specified (offset
-1071247351C0261009Monitor descriptor contains an invalid detailed timing block
-1071247350C026100AMonitor descriptor contains invalid manufacture date
-1071243264C0262000Exclusive mode ownership is needed to create unmanaged primary allocation
-1071243263C0262001The driver needs more DMA buffer space in order to complete the requested operation
-1071243262C0262002Specified display adapter handle is invalid
-1071243261C0262003Specified display adapter and all of its state has been reset
-1071243260C0262004The driver stack doesn't match the expected driver model
-1071243259C0262005Present happened but ended up into the changed desktop mode
-1071243258C0262006Nothing to present due to desktop occlusion
-1071243257C0262007Not able to present due to denial of desktop access
-1071243256C0262008Not able to present with color conversion
-1071243255C0262009The kernel driver detected a version mismatch between it and the user mode driver
-1071243253C026200BPresent redirection is disabled (desktop windowing management subsystem is off)
-1071243252C026200CPrevious exclusive VidPn source owner has released its ownership
-1071243251C026200DWindow DC is not available for presentation
-1071243250C026200EWindowless present is disabled (desktop windowing management subsystem is off)
-1071243249C026200FWindow handle is invalid
-1071243248C0262010No buffer is bound to composition surface
-1071243247C0262011Vail state has been changed
-1071243246C0262012Notifying indirect display UMDF class driver to abandon current swapchain
-1071243245C0262013Notifying indirect display UMDF class driver that indirect display device has been stopped
-1071243244C0262014Failed to send Create Vail Super Wet Ink message
-1071243243C0262015Failed to send Destroy Vail Super Wet Ink message
-1071243008C0262100Not enough video memory available to complete the operation
-1071243007C0262101Couldn't probe and lock the underlying memory of an allocation
-1071243006C0262102The allocation is currently busy
-1071243005C0262103An object being referenced has reach the maximum reference count already and can't be reference further
-1071243004C0262104A problem couldn't be solved due to some currently existing condition. The problem should be tried again later
-1071243003C0262105A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately
-1071243002C0262106The allocation is invalid
-1071243001C0262107No more unswizzling aperture are currently available
-1071243000C0262108The current allocation can't be unswizzled by an aperture
-1071242999C0262109The request failed because a pinned allocation can't be evicted
-1071242992C0262110The allocation can't be used from its current segment location for the specified operation
-1071242991C0262111A locked allocation can't be used in the current command buffer
-1071242990C0262112The allocation being referenced has been closed permanently
-1071242989C0262113An invalid allocation instance is being referenced
-1071242988C0262114An invalid allocation handle is being referenced
-1071242987C0262115The allocation being referenced doesn't belong to the current device
-1071242986C0262116The specified allocation lost its content
-1071242752C0262200GPU exception is detected on the given device. The device is not able to be scheduled
-1071242496C0262300Specified VidPN topology is invalid
-1071242495C0262301Specified VidPN topology is valid but is not supported by this model of the display adapter
-1071242494C0262302Specified VidPN topology is valid but is not supported by the display adapter at this time
-1071242493C0262303Specified VidPN handle is invalid
-1071242492C0262304Specified video present source is invalid
-1071242491C0262305Specified video present target is invalid
-1071242490C0262306Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional)
-1071242488C0262308Specified VidPN source mode set is invalid
-1071242487C0262309Specified VidPN target mode set is invalid
-1071242486C026230ASpecified video signal frequency is invalid
-1071242485C026230BSpecified video signal active region is invalid
-1071242484C026230CSpecified video signal total region is invalid
-1071242480C0262310Specified video present source mode is invalid
-1071242479C0262311Specified video present target mode is invalid
-1071242478C0262312Pinned mode must remain in the set on VidPN's cofunctional modality enumeration
-1071242477C0262313Specified video present path is already in VidPN's topology
-1071242476C0262314Specified mode is already in the mode set
-1071242475C0262315Specified video present source set is invalid
-1071242474C0262316Specified video present target set is invalid
-1071242473C0262317Specified video present source is already in the video present source set
-1071242472C0262318Specified video present target is already in the video present target set
-1071242471C0262319Specified VidPN present path is invalid
-1071242470C026231AMiniport has no recommendation for augmentation of the specified VidPN's topology
-1071242469C026231BSpecified monitor frequency range set is invalid
-1071242468C026231CSpecified monitor frequency range is invalid
-1071242467C026231DSpecified frequency range is not in the specified monitor frequency range set
-1071242465C026231FSpecified frequency range is already in the specified monitor frequency range set
-1071242464C0262320Specified mode set is stale. Please reacquire the new mode set
-1071242463C0262321Specified monitor source mode set is invalid
-1071242462C0262322Specified monitor source mode is invalid
-1071242461C0262323Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration
-1071242460C0262324ID of the specified mode is already used by another mode in the set
-1071242459C0262325System failed to determine a mode that is supported by both the display adapter and the monitor connected to it
-1071242458C0262326Number of video present targets must be greater than or equal to the number of video present sources
-1071242457C0262327Specified present path is not in VidPN's topology
-1071242456C0262328Display adapter must have at least one video present source
-1071242455C0262329Display adapter must have at least one video present target
-1071242454C026232ASpecified monitor descriptor set is invalid
-1071242453C026232BSpecified monitor descriptor is invalid
-1071242452C026232CSpecified descriptor is not in the specified monitor descriptor set
-1071242451C026232DSpecified descriptor is already in the specified monitor descriptor set
-1071242450C026232EID of the specified monitor descriptor is already used by another descriptor in the set
-1071242449C026232FSpecified video present target subset type is invalid
-1071242448C0262330Two or more of the specified resources are not related to each other
-1071242447C0262331ID of the specified video present source is already used by another source in the set
-1071242446C0262332ID of the specified video present target is already used by another target in the set
-1071242445C0262333Specified VidPN source cannot be used because there is no available VidPN target to connect it to
-1071242444C0262334Newly arrived monitor could not be associated with a display adapter
-1071242443C0262335Display adapter in question does not have an associated VidPN manager
-1071242442C0262336VidPN manager of the display adapter in question does not have an active VidPN
-1071242441C0262337Specified VidPN topology is stale. Please reacquire the new topology
-1071242440C0262338There is no monitor connected on the specified video present target
-1071242439C0262339Specified source is not part of the specified VidPN's topology
-1071242438C026233ASpecified primary surface size is invalid
-1071242437C026233BSpecified visible region size is invalid
-1071242436C026233CSpecified stride is invalid
-1071242435C026233DSpecified pixel format is invalid
-1071242434C026233ESpecified color basis is invalid
-1071242433C026233FSpecified pixel value access mode is invalid
-1071242432C0262340Specified target is not part of the specified VidPN's topology
-1071242431C0262341Failed to acquire display mode management interface
-1071242430C0262342Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it
-1071242429C0262343Specified VidPN is active and cannot be accessed
-1071242428C0262344Specified VidPN present path importance ordinal is invalid
-1071242427C0262345Specified VidPN present path content geometry transformation is invalid
-1071242426C0262346Specified content geometry transformation is not supported on the respective VidPN present path
-1071242425C0262347Specified gamma ramp is invalid
-1071242424C0262348Specified gamma ramp is not supported on the respective VidPN present path
-1071242423C0262349Multi-sampling is not supported on the respective VidPN present path
-1071242422C026234ASpecified mode is not in the specified mode set
-1071242419C026234DSpecified VidPN topology recommendation reason is invalid
-1071242418C026234ESpecified VidPN present path content type is invalid
-1071242417C026234FSpecified VidPN present path copy protection type is invalid
-1071242416C0262350No more than one unassigned mode set can exist at any given time for a given VidPN source/target
-1071242414C0262352Specified scanline ordering type is invalid
-1071242413C0262353Topology changes are not allowed for the specified VidPN
-1071242412C0262354All available importance ordinals are already used in specified topology
-1071242411C0262355Specified primary surface has a different private format attribute than the current primary surface
-1071242410C0262356Specified mode pruning algorithm is invalid
-1071242409C0262357Specified monitor capability origin is invalid
-1071242408C0262358Specified monitor frequency range constraint is invalid
-1071242407C0262359Maximum supported number of present paths has been reached
-1071242406C026235AMiniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology
-1071242405C026235BSpecified client type was not recognized
-1071242404C026235CClient VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet)
-1071242240C0262400Specified display adapter child device already has an external device connected to it
-1071242239C0262401Specified display adapter child device does not support descriptor exposure
-1071242192C0262430The display adapter is not linked to any other adapters
-1071242191C0262431Lead adapter in a linked configuration was not enumerated yet
-1071242190C0262432Some chain adapters in a linked configuration were not enumerated yet
-1071242189C0262433The chain of linked adapters is not ready to start because of an unknown failure
-1071242188C0262434An attempt was made to start a lead link display adapter when the chain links were not started yet
-1071242187C0262435An attempt was made to power up a lead link display adapter when the chain links were powered down
-1071242186C0262436The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state
-1071242184C0262438The driver trying to start is not the same as the driver for the POSTed display adapter
-1071242181C026243BAn operation is being attempted that requires the display adapter to be in a quiescent state
-1071241984C0262500The driver does not support OPM
-1071241983C0262501The driver does not support COPP
-1071241982C0262502The driver does not support UAB
-1071241981C0262503The specified encrypted parameters are invalid
-1071241979C0262505The GDI display device passed to this function does not have any active video outputs
-1071241973C026250BAn internal error caused this operation to fail
-1071241972C026250CThe function failed because the caller passed in an invalid OPM user mode handle
-1071241970C026250EA certificate could not be returned because the certificate buffer passed to the function was too small
-1071241969C026250FA video output could not be created because the frame buffer is in spanning mode
-1071241968C0262510A video output could not be created because the frame buffer is in theater mode
-1071241967C0262511The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware
-1071241966C0262512The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification
-1071241965C0262513The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP
-1071241964C0262514The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP
-1071241963C0262515The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A
-1071241962C0262516The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output
-1071241961C0262517The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high
-1071241960C0262518The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs
-1071241958C026251AThe operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed
-1071241957C026251BThe method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console
-1071241956C026251CEither the IOPMVideoOutput::COPPCompatibleGetInformation
-1071241955C026251DThe IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid
-1071241954C026251EThe method failed because an unexpected error occurred inside of a display driver
-1071241953C026251FEither the IOPMVideoOutput::COPPCompatibleGetInformation
-1071241952C0262520The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs
-1071241951C0262521The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid
-1071241856C0262580The monitor connected to the specified video output does not have an I2C bus
-1071241855C0262581No device on the I2C bus has the specified address
-1071241854C0262582An error occurred while transmitting data to the device on the I2C bus
-1071241853C0262583An error occurred while receiving data from the device on the I2C bus
-1071241852C0262584The monitor does not support the specified VCP code
-1071241851C0262585The data received from the monitor is invalid
-1071241850C0262586The 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
-1071241849C0262587The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0
-1071241848C0262588An internal Monitor Configuration API error occurred
-1071241847C0262589An operation failed because a DDC/CI message had an invalid value in its command field
-1071241846C026258AAn error occurred because the field length of a DDC/CI message contained an invalid value
-1071241845C026258BAn 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
-1071241844C026258CThis function failed because an invalid monitor handle was passed to it
-1071241843C026258DThe 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
-1071241768C02625D8A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value
-1071241767C02625D9The monitor's VCP Version (0xDF) VCP code returned an invalid version value
-1071241766C02625DAThe monitor does not comply with the MCCS specification it claims to support
-1071241765C02625DBThe MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used
-1071241764C02625DCThe Monitor Configuration API only works with monitors which support the MCCS 1.0 specification
-1071241762C02625DEThe monitor returned an invalid monitor technology type. CRT
-1071241761C02625DFSetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification
-1071241760C02625E0This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session
-1071241759C02625E1This function cannot find an actual GDI display device which corresponds to the specified GDI display device name
-1071241758C02625E2The function failed because the specified GDI display device was not attached to the Windows desktop
-1071241757C02625E3This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them
-1071241756C02625E4The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL
-1071241755C02625E5The function failed because the specified GDI device did not have any monitors associated with it
-1071241754C02625E6An array passed to the function cannot hold all of the data that the function must copy into the array
-1071241753C02625E7An internal error caused an operation to fail
-1070329841C034100FThe TCP connection is not offloadable because of a local policy setting
-1070329838C0341012The TCP connection is not offloadable by the Chimney Offload target
-1070329837C0341013The IP Path object is not in an offloadable state
-1070268414C0350002The hypervisor does not support the operation because the specified hypercall code is not supported
-1070268413C0350003The hypervisor does not support the operation because the encoding for the hypercall input register is not supported
-1070268412C0350004The hypervisor could not perform the operation because a parameter has an invalid alignment
-1070268411C0350005The hypervisor could not perform the operation because an invalid parameter was specified
-1070268410C0350006Access to the specified object was denied
-1070268409C0350007The hypervisor could not perform the operation because the partition is entering or in an invalid state
-1070268408C0350008The operation is not allowed in the current state
-1070268407C0350009The hypervisor does not recognize the specified partition property
-1070268406C035000AThe specified value of a partition property is out of range or violates an invariant
-1070268405C035000BThere is not enough memory in the hypervisor pool to complete the operation
-1070268404C035000CThe maximum partition depth has been exceeded for the partition hierarchy
-1070268403C035000DA partition with the specified partition Id does not exist
-1070268402C035000EThe hypervisor could not perform the operation because the specified VP index is invalid
-1070268399C0350011The hypervisor could not perform the operation because the specified port identifier is invalid
-1070268398C0350012The hypervisor could not perform the operation because the specified connection identifier is invalid
-1070268397C0350013Not enough buffers were supplied to send a message
-1070268396C0350014The previous virtual interrupt has not been acknowledged
-1070268395C0350015A virtual processor is not in the correct state for the indicated operation
-1070268394C0350016The previous virtual interrupt has already been acknowledged
-1070268393C0350017The indicated partition is not in a valid state for saving or restoring
-1070268392C0350018The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled
-1070268391C0350019The 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
-1070268390C035001AThe proximity domain information is invalid
-1070268389C035001BAn attempt to retrieve debugging data failed because none was available
-1070268388C035001CThe physical connection being used for debugging has not recorded any receive activity since the last operation
-1070268387C035001DThere are not enough resources to complete the operation
-1070268386C035001EA hypervisor feature is not available to the user
-1070268365C0350033The specified buffer was too small to contain all of the requested data
-1070268360C0350038The 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
-1070268356C035003CValidation of CPUID data of the processor failed
-1070268355C035003DValidation of XSAVE CPUID data of the processor failed
-1070268354C035003EProcessor did not respond within the timeout period
-1070268353C035003FSMX has been enabled in the BIOS
-1070268351C0350041The hypervisor could not perform the operation because the specified LP index is invalid
-1070268336C0350050The supplied register value is invalid
-1070268335C0350051The supplied virtual trust level is not in the correct state to perform the requested operation
-1070268331C0350055No execute feature (NX) is not present or not enabled in the BIOS
-1070268329C0350057The supplied device ID is invalid
-1070268328C0350058The operation is not allowed in the current device state
-1070268320C0350060The supplied page request specifies a memory access that the guest does not have permissions to perform
-1070268305C035006FA CPU group with the specified CPU group Id does not exist
-1070268304C0350070The hypervisor could not perform the operation because the CPU group is entering or in an invalid state
-1070268303C0350071The requested operation failed
-1070268302C0350072The hypervisor could not perform the operation because it is not allowed with nested virtualization active
-1070268301C0350073There is not enough memory in the root partition's pool to complete the operation
-1070268300C0350074The provided event log buffer was already marked as freed
-1070268299C0350075There is not enough contiguous memory in the partition's pool to complete the operation
-1070264320C0351000No hypervisor is present on this system
-1070137343C0370001The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists
-1070137342C0370002The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists
-1070137341C0370003The 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
-1070137340C0370004No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists
-1070137339C0370005The 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
-1070137338C0370006The partition name of the virtualization infrastructure driver exceeds the maximum
-1070137337C0370007The message queue name of the virtualization infrastructure driver exceeds the maximum
-1070137336C0370008Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists
-1070137335C0370009The 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
-1070137334C037000AThe 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
-1070137333C037000BA message queue with the same name already exists for the virtualization infrastructure driver
-1070137332C037000CThe 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
-1070137331C037000DThe memory block for the virtualization infrastructure driver is still being used and cannot be destroyed
-1070137330C037000ECannot 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
-1070137329C037000FThe non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine
-1070137328C0370010The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology
-1070137327C0370011The memory block for the virtualization infrastructure driver is already associated with a message queue
-1070137326C0370012The handle is not a valid memory block handle for the virtualization infrastructure driver
-1070137325C0370013The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists
-1070137324C0370014The handle is not a valid message queue handle for the virtualization infrastructure driver
-1070137323C0370015The handle is not a valid page range handle for the virtualization infrastructure driver
-1070137322C0370016Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block
-1070137321C0370017The 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
-1070137320C0370018The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver
-1070137319C0370019Notifications cannot be created on the memory block because it is use
-1070137318C037001AThe message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists
-1070137317C037001BCannot add a virtual processor to the partition because the maximum has been reached
-1070137316C037001CCannot stop the virtual processor immediately because of a pending intercept
-1070137315C037001DInvalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists
-1070137314C037001EThe 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
-1070137313C037001FThis kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists
-1070137312C0370020Cannot 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
-1070137311C0370021The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists
-1070137310C0370022The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists
-1070137309C0370023Cannot 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
-1070137308C0370024The 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
-1070137307C0370025Cannot 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
-1070137306C0370026Cannot 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
-1070137305C0370027Cannot 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
-1070137304C0370028Cannot 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
-1070137303C0370029Cannot 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
-1070137302C037002AThe specified VTL does not have the permission to access the resource
-1070137088C0370100The virtual machine or container exited unexpectedly while starting
-1070137087C0370101The container operating system does not match the host operating system
-1070137086C0370102The virtual machine could not be started because a required feature is not installed
-1070137085C0370103The call to start an asynchronous operation succeeded and the operation is performed in the background
-1070137084C0370104The supported number of notification callbacks has been exceeded
-1070137083C0370105The requested virtual machine or container operation is not valid in the current state
-1070137082C0370106The virtual machine or container exited unexpectedly
-1070137081C0370107The virtual machine or container was forcefully exited
-1070137080C0370108A connection could not be established with the container or virtual machine
-1070137079C0370109The operation timed out because a response was not received from the virtual machine or container
-1070137078C037010AThe connection with the virtual machine or container was closed
-1070137077C037010BAn unknown internal message was received by the virtual machine or container
-1070137076C037010CThe virtual machine or container does not support an available version of the communication protocol with the host
-1070137075C037010DThe virtual machine or container JSON document is invalid
-1070137074C037010EA virtual machine or container with the specified identifier does not exist
-1070137073C037010FA virtual machine or container with the specified identifier already exists
-1070137072C0370110The virtual machine or container with the specified identifier is not running
-1070137071C0370111A communication protocol error has occurred between the virtual machine or container and the host
-1070137070C0370112The container image contains a layer with an unrecognized format
-1070137069C0370113To use this container image
-1070136832C0370200A virtual switch with the given name was not found
-1070136320C0370400Cannot restore this virtual machine because a file read from the vSMB saved state data could not be found. Delete the saved state data and then try to start the virtual machine
-1070136319C0370401Cannot restore this virtual machine because the vSMB saved state data cannot be read. Delete the saved state data and then try to start the virtual machine
-1070136064C0370500Partition state blob not found. Make sure the virtual machine is saved for this content to be included in the saved state file(s)
-1070136063C0370501Guest memory not found. Make sure the virtual machine is saved for this content to be included in the saved state file(s)
-1070136062C0370502No virtual processor information found in the saved partition blob. Make sure the virtual machine is saved successfully for this content to be included in the partition state
-1070136061C0370503A virtual processor has been detected to have nested virtualization enabled. Nested Virtualization is not supported yet by VmSavedStateDumpProvider
-1070136060C0370504The Windows kernel image address could not be found in the virtual machine saved state
-1070136059C0370505Failed to read Page Map Level 4 entry (pxe) for a virtual address
-1070136058C0370506Failed to read Page Directory Page Table entry (pdpte) for a virtual address
-1070136057C0370507Failed to read Page Directory entry (pde) for a virtual address
-1070136056C0370508Failed to read Page Table entry (pte) for a virtual address
-1070071807C0380001The configuration database is full
-1070071806C0380002The configuration data on the disk is corrupted
-1070071805C0380003The configuration on the disk is not insync with the in-memory configuration
-1070071804C0380004A majority of disks failed to be updated with the new configuration
-1070071803C0380005The disk contains non-simple volumes
-1070071802C0380006The same disk was specified more than once in the migration list
-1070071801C0380007The disk is already dynamic
-1070071800C0380008The specified disk id is invalid. There are no disks with the specified disk id
-1070071799C0380009The specified disk is an invalid disk. Operation cannot complete on an invalid disk
-1070071798C038000AThe specified disk(s) cannot be removed since it is the last remaining voter
-1070071797C038000BThe specified disk has an invalid disk layout
-1070071796C038000CThe disk layout contains non-basic partitions which appear after basic partitions. This is an invalid disk layout
-1070071795C038000DThe disk layout contains partitions which are not cylinder aligned
-1070071794C038000EThe disk layout contains partitions which are smaller than the minimum size
-1070071793C038000FThe disk layout contains primary partitions in between logical drives. This is an invalid disk layout
-1070071792C0380010The disk layout contains more than the maximum number of supported partitions
-1070071791C0380011The specified disk is missing. The operation cannot complete on a missing disk
-1070071790C0380012The specified disk is not empty
-1070071789C0380013There is not enough usable space for this operation
-1070071788C0380014The force revectoring of bad sectors failed
-1070071787C0380015The specified disk has an invalid sector size
-1070071786C0380016The specified disk set contains volumes which exist on disks outside of the set
-1070071785C0380017A disk in the volume layout provides extents to more than one member of a plex
-1070071784C0380018A disk in the volume layout provides extents to more than one plex
-1070071783C0380019Dynamic disks are not supported on this system
-1070071782C038001AThe specified extent is already used by other volumes
-1070071781C038001BThe 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
-1070071780C038001CThe specified volume extent is not within the public region of the disk
-1070071779C038001DThe specified volume extent is not sector aligned
-1070071778C038001EThe specified partition overlaps an EBR (the first track of an extended partition on an MBR disk)
-1070071777C038001FThe specified extent lengths cannot be used to construct a volume with specified length
-1070071776C0380020The system does not support fault tolerant volumes
-1070071775C0380021The specified interleave length is invalid
-1070071774C0380022There is already a maximum number of registered users
-1070071773C0380023The specified member is already in-sync with the other active members. It does not need to be regenerated
-1070071772C0380024The same member index was specified more than once
-1070071771C0380025The specified member index is greater or equal than the number of members in the volume plex
-1070071770C0380026The specified member is missing. It cannot be regenerated
-1070071769C0380027The specified member is not detached. Cannot replace a member which is not detached
-1070071768C0380028The specified member is already regenerating
-1070071767C0380029All disks belonging to the pack failed
-1070071766C038002AThere are currently no registered users for notifications. The task number is irrelevant unless there are registered users
-1070071765C038002BThe specified notification user does not exist. Failed to unregister user for notifications
-1070071764C038002CThe notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications
-1070071763C038002DThe specified number of members is invalid
-1070071762C038002EThe specified number of plexes is invalid
-1070071761C038002FThe specified source and target packs are identical
-1070071760C0380030The specified pack id is invalid. There are no packs with the specified pack id
-1070071759C0380031The specified pack is the invalid pack. The operation cannot complete with the invalid pack
-1070071758C0380032The specified pack name is invalid
-1070071757C0380033The specified pack is offline
-1070071756C0380034The specified pack already has a quorum of healthy disks
-1070071755C0380035The pack does not have a quorum of healthy disks
-1070071754C0380036The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported
-1070071753C0380037Failed to update the disk's partition layout
-1070071752C0380038The specified plex is already in-sync with the other active plexes. It does not need to be regenerated
-1070071751C0380039The same plex index was specified more than once
-1070071750C038003AThe specified plex index is greater or equal than the number of plexes in the volume
-1070071749C038003BThe specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline
-1070071748C038003CThe specified plex is missing
-1070071747C038003DThe specified plex is currently regenerating
-1070071746C038003EThe specified plex type is invalid
-1070071745C038003FThe operation is only supported on RAID-5 plexes
-1070071744C0380040The operation is only supported on simple plexes
-1070071743C0380041The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set
-1070071742C0380042There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications
-1070071741C0380043There is currently a transaction in process
-1070071740C0380044An unexpected layout change occurred outside of the volume manager
-1070071739C0380045The specified volume contains a missing disk
-1070071738C0380046The specified volume id is invalid. There are no volumes with the specified volume id
-1070071737C0380047The specified volume length is invalid
-1070071736C0380048The specified size for the volume is not a multiple of the sector size
-1070071735C0380049The operation is only supported on mirrored volumes
-1070071734C038004AThe specified volume does not have a retain partition
-1070071733C038004BThe specified volume is offline
-1070071732C038004CThe specified volume already has a retain partition
-1070071731C038004DThe specified number of extents is invalid
-1070071730C038004EAll disks participating to the volume must have the same sector size
-1070071729C038004FThe boot disk experienced failures
-1070071728C0380050The configuration of the pack is offline
-1070071727C0380051The configuration of the pack is online
-1070071726C0380052The specified pack is not the primary pack
-1070071725C0380053All disks failed to be updated with the new content of the log
-1070071724C0380054The specified number of disks in a plex is invalid
-1070071723C0380055The specified number of disks in a plex member is invalid
-1070071722C0380056The operation is not supported on mirrored volumes
-1070071721C0380057The operation is only supported on simple and spanned plexes
-1070071720C0380058The pack has no valid log copies
-1070071719C0380059A primary pack is already present
-1070071718C038005AThe specified number of disks is invalid
-1070071717C038005BThe system does not support mirrored volumes
-1070071716C038005CThe system does not support RAID-5 volumes
-1070006270C0390002Entries enumerated have exceeded the allowed threshold
-1069940735C03A0001The virtual hard disk is corrupted. The virtual hard disk drive footer is missing
-1069940734C03A0002The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum
-1069940733C03A0003The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted
-1069940732C03A0004The system does not recognize the file format of this virtual hard disk
-1069940731C03A0005The version does not support this version of the file format
-1069940730C03A0006The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum
-1069940729C03A0007The system does not support this version of the virtual hard disk.This version of the sparse header is not supported
-1069940728C03A0008The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt
-1069940727C03A0009Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk
-1069940726C03A000AThe virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt
-1069940725C03A000BThe system does not support this version of the virtual hard disk. The block size is invalid
-1069940724C03A000CThe virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk
-1069940723C03A000DThe chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk
-1069940722C03A000EThe chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk
-1069940721C03A000FThe 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
-1069940720C03A0010Failed to read the metadata of the virtual hard disk
-1069940719C03A0011Failed to write to the metadata of the virtual hard disk
-1069940718C03A0012The size of the virtual hard disk is not valid
-1069940717C03A0013The file size of this virtual hard disk is not valid
-1069940716C03A0014A virtual disk support provider for the specified file was not found
-1069940715C03A0015The specified disk is not a virtual disk
-1069940714C03A0016The 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
-1069940713C03A0017The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk
-1069940712C03A0018The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain
-1069940711C03A0019The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain
-1069940710C03A001AThe 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
-1069940709C03A001BThe requested operation cannot be performed on a virtual disk of this type
-1069940708C03A001CThe requested operation cannot be performed on the virtual disk in its current state
-1069940707C03A001DThe sector size of the physical disk on which the virtual disk resides is not supported
-1069940706C03A001EThe disk is already owned by a different owner
-1069940705C03A001FThe disk must be offline or read-only
-1069940704C03A0020Change Tracking is not initialized for this virtual disk
-1069940703C03A0021Size of change tracking file exceeded the maximum size limit
-1069940702C03A0022VHD file is changed due to compaction
-1069940701C03A0023Change 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
-1069940700C03A0024Change Tracking file for the virtual disk is not in a valid state
-1069940699C03A0025The requested resize operation could not be completed because it might truncate user data residing on the virtual disk
-1069940698C03A0026The requested operation could not be completed because the virtual disk's minimum safe size could not be determined.This may be due to a missing or corrupt partition table
-1069940697C03A0027The requested operation could not be completed because the virtual disk's size cannot be safely reduced further
-1069940696C03A0028There is not enough space in the virtual disk file for the provided metadata item
-1069940695C03A0029The specified change tracking identifier is not valid
-1069940694C03A002AChange tracking is disabled for the specified virtual hard disk
-1069940688C03A0030There is no change tracking data available associated with the specified change tracking identifier
-1067712512C05C0000The proper error code with sense data was stored on server side
-1067647232C05CFF00The requested error data is not available on the server
-1067647231C05CFF01Unit Attention data is available for the initiator to query
-1067647230C05CFF02The data capacity of the device has changed
-1067647229C05CFF03A previous operation resulted in this initiator's reservations being preempted
-1067647228C05CFF04A previous operation resulted in this initiator's reservations being released
-1067647227C05CFF05A previous operation resulted in this initiator's registrations being preempted
-1067647226C05CFF06The data storage format of the device has changed
-1067647225C05CFF07The current initiator is not allowed to perform the SCSI command because of a reservation conflict
-1067647224C05CFF08Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks
-1067647223C05CFF09The server version does not match the requested version
-1067647222C05CFF0AThe requested operation cannot be performed on the virtual disk as it is currently used in shared mode
-1067647221C05CFF0BInvalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures
-1067647220C05CFF0CThe requested operation failed due to a missing backing storage file
-1067646976C05D0000Failed to negotiate a preauthentication integrity hash function
-1067646975C05D0001The current cluster functional level does not support this SMB dialect
-1058537472C0E80000The command was not recognized by the security core
-1058406399C0EA0001No applicable app licenses found
-1058406398C0EA0002CLiP license not found
-1058406397C0EA0003CLiP device license not found
-1058406396C0EA0004CLiP license has an invalid signature
-1058406395C0EA0005CLiP keyholder license is invalid or missing
-1058406394C0EA0006CLiP license has expired
-1058406393C0EA0007CLiP license is signed by an unknown source
-1058406392C0EA0008CLiP license is not signed
-1058406391C0EA0009CLiP license hardware ID is out of tolerance
-1058406390C0EA000ACLiP license device ID does not match the device ID in the bound device license
000000000The operation completed successfully
100000001Incorrect function
200000002The system cannot find the file specified
300000003The system cannot find the path specified
400000004The system cannot open the file
500000005Access is denied
600000006The handle is invalid
700000007The storage control blocks were destroyed
800000008Not enough memory resources are available to process this command
900000009The storage control block address is invalid
100000000AThe environment is incorrect
110000000BAn attempt was made to load a program with an incorrect format
120000000CThe access code is invalid
130000000DThe data is invalid
140000000ENot enough memory resources are available to complete this operation
150000000FThe system cannot find the drive specified
1600000010The directory cannot be removed
1700000011The system cannot move the file to a different disk drive
1800000012There are no more files
1900000013The media is write protected
2000000014The system cannot find the device specified
2100000015The device is not ready
2200000016The device does not recognize the command
2300000017Data error (cyclic redundancy check)
2400000018The program issued a command but the command length is incorrect
2500000019The drive cannot locate a specific area or track on the disk
260000001AThe specified disk or diskette cannot be accessed
270000001BThe drive cannot find the sector requested
280000001CThe printer is out of paper
290000001DThe system cannot write to the specified device
300000001EThe system cannot read from the specified device
310000001FA device attached to the system is not functioning
3200000020The process cannot access the file because it is being used by another process
3300000021The process cannot access the file because another process has locked a portion of the file
3400000022The wrong diskette is in the drive.Insert %2 (Volume Serial Number: %3) into drive %1
3600000024Too many files opened for sharing
3800000026Reached the end of the file
3900000027The disk is full
5000000032The request is not supported
5100000033Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path
5200000034You were not connected because a duplicate name exists on the network. If joining a domain
5300000035The network path was not found
5400000036The network is busy
5500000037The specified network resource or device is no longer available
5600000038The network BIOS command limit has been reached
5700000039A network adapter hardware error occurred
580000003AThe specified server cannot perform the requested operation
590000003BAn unexpected network error occurred
600000003CThe remote adapter is not compatible
610000003DThe printer queue is full
620000003ESpace to store the file waiting to be printed is not available on the server
630000003FYour file waiting to be printed was deleted
6400000040The specified network name is no longer available
6500000041Network access is denied
6600000042The network resource type is not correct
6700000043The network name cannot be found
6800000044The name limit for the local computer network adapter card was exceeded
6900000045The network BIOS session limit was exceeded
7000000046The remote server has been paused or is in the process of being started
7100000047No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept
7200000048The specified printer or disk device has been paused
8000000050The file exists
8200000052The directory or file cannot be created
8300000053Fail on INT 24
8400000054Storage to process this request is not available
8500000055The local device name is already in use
8600000056The specified network password is not correct
8700000057The parameter is incorrect
8800000058A write fault occurred on the network
8900000059The system cannot start another process at this time
10000000064Cannot create another system semaphore
10100000065The exclusive semaphore is owned by another process
10200000066The semaphore is set and cannot be closed
10300000067The semaphore cannot be set again
10400000068Cannot request exclusive semaphores at interrupt time
10500000069The previous ownership of this semaphore has ended
1060000006AInsert the diskette for drive %1
1070000006BThe program stopped because an alternate diskette was not inserted
1080000006CThe disk is in use or locked by another process
1090000006DThe pipe has been ended
1100000006EThe system cannot open the device or file specified
1110000006FThe file name is too long
11200000070There is not enough space on the disk
11300000071No more internal file identifiers available
11400000072The target internal file identifier is incorrect
11700000075The IOCTL call made by the application program is not correct
11800000076The verify-on-write switch parameter value is not correct
11900000077The system does not support the command requested
12000000078This function is not supported on this system
12100000079The semaphore timeout period has expired
1220000007AThe data area passed to a system call is too small
1230000007BThe filename
1240000007CThe system call level is not correct
1250000007DThe disk has no volume label
1260000007EThe specified module could not be found
1270000007FThe specified procedure could not be found
12800000080There are no child processes to wait for
12900000081The %1 application cannot be run in Win32 mode
13000000082Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O
13100000083An attempt was made to move the file pointer before the beginning of the file
13200000084The file pointer cannot be set on the specified device or file
13300000085A JOIN or SUBST command cannot be used for a drive that contains previously joined drives
13400000086An attempt was made to use a JOIN or SUBST command on a drive that has already been joined
13500000087An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted
13600000088The system tried to delete the JOIN of a drive that is not joined
13700000089The system tried to delete the substitution of a drive that is not substituted
1380000008AThe system tried to join a drive to a directory on a joined drive
1390000008BThe system tried to substitute a drive to a directory on a substituted drive
1400000008CThe system tried to join a drive to a directory on a substituted drive
1410000008DThe system tried to SUBST a drive to a directory on a joined drive
1420000008EThe system cannot perform a JOIN or SUBST at this time
1430000008FThe system cannot join or substitute a drive to or for a directory on the same drive
14400000090The directory is not a subdirectory of the root directory
14500000091The directory is not empty
14600000092The path specified is being used in a substitute
14700000093Not enough resources are available to process this command
14800000094The path specified cannot be used at this time
14900000095An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute
15000000096System trace information was not specified in your CONFIG.SYS file
15100000097The number of specified semaphore events for DosMuxSemWait is not correct
15200000098DosMuxSemWait did not execute; too many semaphores are already set
15300000099The DosMuxSemWait list is not correct
1540000009AThe volume label you entered exceeds the label character limit of the target file system
1550000009BCannot create another thread
1560000009CThe recipient process has refused the signal
1570000009DThe segment is already discarded and cannot be locked
1580000009EThe segment is already unlocked
1590000009FThe address for the thread ID is not correct
160000000A0One or more arguments are not correct
161000000A1The specified path is invalid
162000000A2A signal is already pending
164000000A4No more threads can be created in the system
167000000A7Unable to lock a region of a file
170000000AAThe requested resource is in use
171000000ABDevice's command support detection is in progress
173000000ADA lock request was not outstanding for the supplied cancel region
174000000AEThe file system does not support atomic changes to the lock type
180000000B4The system detected a segment number that was not correct
182000000B6The operating system cannot run %1
183000000B7Cannot create a file when that file already exists
186000000BAThe flag passed is not correct
187000000BBThe specified system semaphore name was not found
188000000BCThe operating system cannot run %1
189000000BDThe operating system cannot run %1
190000000BEThe operating system cannot run %1
191000000BFCannot run %1 in Win32 mode
192000000C0The operating system cannot run %1
193000000C1%1 is not a valid Win32 application
194000000C2The operating system cannot run %1
195000000C3The operating system cannot run %1
196000000C4The operating system cannot run this application program
197000000C5The operating system is not presently configured to run this application
198000000C6The operating system cannot run %1
199000000C7The operating system cannot run this application program
200000000C8The code segment cannot be greater than or equal to 64K
201000000C9The operating system cannot run %1
202000000CAThe operating system cannot run %1
203000000CBThe system could not find the environment option that was entered
205000000CDNo process in the command subtree has a signal handler
206000000CEThe filename or extension is too long
207000000CFThe ring 2 stack is in use
208000000D0The global filename characters
209000000D1The signal being posted is not correct
210000000D2The signal handler cannot be set
212000000D4The segment is locked and cannot be reallocated
214000000D6Too many dynamic-link modules are attached to this program or dynamic-link module
215000000D7Cannot nest calls to LoadModule
216000000D8This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher
217000000D9The image file %1 is signed
218000000DAThe image file %1 is strong signed
220000000DCThis file is checked out or locked for editing by another user
221000000DDThe file must be checked out before saving changes
222000000DEThe file type being saved or retrieved has been blocked
223000000DFThe file size exceeds the limit allowed and cannot be saved
224000000E0Access Denied. Before opening files in this location
225000000E1Operation did not complete successfully because the file contains a virus or potentially unwanted software
226000000E2This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software
229000000E5The pipe is local
230000000E6The pipe state is invalid
231000000E7All pipe instances are busy
232000000E8The pipe is being closed
233000000E9No process is on the other end of the pipe
234000000EAMore data is available
235000000EBThe action requested resulted in no work being done. Error-style clean-up has been performed
240000000F0The session was canceled
254000000FEThe specified extended attribute name was invalid
255000000FFThe extended attributes are inconsistent
25800000102The wait operation timed out
25900000103No more data is available
2660000010AThe copy functions cannot be used
2670000010BThe directory name is invalid
27500000113The extended attributes did not fit in the buffer
27600000114The extended attribute file on the mounted file system is corrupt
27700000115The extended attribute table file is full
27800000116The specified extended attribute handle is invalid
2820000011AThe mounted file system does not support extended attributes
28800000120Attempt to release mutex not owned by caller
2980000012AToo many posts were made to a semaphore
2990000012BOnly part of a ReadProcessMemory or WriteProcessMemory request was completed
3000000012CThe oplock request is denied
3010000012DAn invalid oplock acknowledgment was received by the system
3020000012EThe volume is too fragmented to complete this operation
3030000012FThe file cannot be opened because it is in the process of being deleted
30400000130Short name settings may not be changed on this volume due to the global registry setting
30500000131Short names are not enabled on this volume
30600000132The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume
30700000133A requested file lock operation cannot be processed due to an invalid byte range
30800000134The subsystem needed to support the image type is not present
30900000135The specified file already has a notification GUID associated with it
31000000136An invalid exception handler routine has been detected
31100000137Duplicate privileges were specified for the token
31200000138No ranges for the specified operation were able to be processed
31300000139Operation is not allowed on a file system internal file
3140000013AThe physical resources of this disk have been exhausted
3150000013BThe token representing the data is invalid
3160000013CThe device does not support the command feature
3170000013DThe system cannot find message text for message number 0x%1 in the message file for %2
3180000013EThe scope specified was not found
3190000013FThe Central Access Policy specified is not defined on the target machine
32000000140The Central Access Policy obtained from Active Directory is invalid
32100000141The device is unreachable
32200000142The target device has insufficient resources to complete the operation
32300000143A data integrity checksum error occurred. Data in the file stream is corrupt
32400000144An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation
32600000146Device does not support file-level TRIM
32700000147The command specified a data offset that does not align to the device's granularity/alignment
32800000148The command specified an invalid field in its parameter list
32900000149An operation is currently in progress with the device
3300000014AAn attempt was made to send down the command via an invalid path to the target device
3310000014BThe command specified a number of descriptors that exceeded the maximum supported by the device
3320000014CScrub is disabled on the specified file
3330000014DThe storage device does not provide redundancy
3340000014EAn operation is not supported on a resident file
3350000014FAn operation is not supported on a compressed file
33600000150An operation is not supported on a directory
33700000151The specified copy of the requested data could not be read
33800000152The specified data could not be written to any of the copies
33900000153One 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
34000000154The supplied kernel information version is invalid
34100000155The supplied PEP information version is invalid
34200000156This object is not externally backed by any provider
34300000157The external backing provider is not recognized
34400000158Compressing this object would not save space
34500000159The request failed due to a storage topology ID mismatch
3460000015AThe operation was blocked by parental controls
3470000015BA file system block being referenced has already reached the maximum reference count and can't be referenced any further
3480000015CThe requested operation failed because the file stream is marked to disallow writes
3490000015DThe requested operation failed with an architecture-specific failure code
3500000015ENo action was taken as a system reboot is required
3510000015FThe shutdown operation failed
35200000160The restart operation failed
35300000161The maximum number of sessions has been reached
35400000162Windows Information Protection policy does not allow access to this network resource
35500000163The device hint name buffer is too small to receive the remaining name
35600000164The requested operation was blocked by Windows Information Protection policy. For more information
35700000165The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please
35800000166The cloud sync root metadata is corrupted
35900000167The device is in maintenance mode
36000000168This operation is not supported on a DAX volume
36100000169The volume has active DAX mappings
3620000016AThe cloud file provider is not running
3630000016BThe cloud file metadata is corrupt and unreadable
3640000016CThe cloud file metadata is too large
3650000016DThe cloud file property is too large
3660000016EThe cloud file property is possibly corrupt. The on-disk checksum does not match the computed checksum
3670000016FThe process creation has been blocked
36800000170The storage device has lost data or persistence
36900000171The provider that supports file system virtualization is temporarily unavailable
37000000172The metadata for file system virtualization is corrupt and unreadable
37100000173The provider that supports file system virtualization is too busy to complete this operation
37200000174The provider that supports file system virtualization is unknown
37300000175GDI handles were potentially leaked by the application
37400000176The maximum number of cloud file properties has been reached
37500000177The version of the cloud file property store is not supported
37600000178The file is not a cloud file
37700000179The file is not in sync with the cloud
3780000017AThe cloud sync root is already connected with another cloud sync provider
3790000017BThe operation is not supported by the cloud sync provider
3800000017CThe cloud operation is invalid
3810000017DThe cloud operation is not supported on a read-only volume
3820000017EThe operation is reserved for a connected cloud sync provider
3830000017FThe cloud sync provider failed to validate the downloaded data
38400000180You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol
38500000181The virtualization operation is not allowed on the file in its current state
38600000182The cloud sync provider failed user authentication
38700000183The cloud sync provider failed to perform the operation due to low system resources
38800000184The cloud sync provider failed to perform the operation due to network being unavailable
38900000185The cloud operation was unsuccessful
39000000186The operation is only supported on files under a cloud sync root
39100000187The operation cannot be performed on cloud files in use
39200000188The operation cannot be performed on pinned cloud files
39300000189The cloud operation was aborted
3940000018AThe cloud file's property store is corrupt
3950000018BAccess to the cloud file is denied
3960000018CThe cloud operation cannot be performed on a file with incompatible hardlinks
3970000018DThe operation failed due to a conflicting cloud file property lock
3980000018EThe cloud operation was canceled by user
3990000018FAn externally encrypted syskey has been configured
40000000190The thread is already in background processing mode
40100000191The thread is not in background processing mode
40200000192The process is already in background processing mode
40300000193The process is not in background processing mode
40400000194The cloud file provider exited unexpectedly
40500000195The file is not a cloud sync root
40600000196The read or write operation to an encrypted file could not be completed because the file can only be accessed when the device is unlocked
40700000197The volume is not cluster aligned on the disk
40800000198No physically aligned free space was found on the volume
40900000199The APPX file can not be accessed because it is not encrypted as expected
4100000019AA read or write of raw encrypted data cannot be performed because the file is not encrypted
4110000019BAn invalid file offset in the encrypted data info block was passed for read or write operation of file's raw encrypted data
4120000019CAn invalid offset and length combination in the encrypted data info block was passed for read or write operation of file's raw encrypted data
4130000019DAn invalid parameter in the encrypted data info block was passed for read or write operation of file's raw encrypted data
4140000019EThe Windows Subsystem for Linux has not been enabled
4150000019FThe specified data could not be read from any of the copies
416000001A0The specified storage reserve ID is invalid
417000001A1The specified storage reserve does not exist
418000001A2The specified storage reserve already exists
419000001A3The specified storage reserve is not empty
420000001A4This operation requires a DAX volume
421000001A5This stream is not DAX mappable
422000001A6Operation cannot be performed on a time critical thread
423000001A7User data protection is not supported for the current or provided user
424000001A8This directory contains entries whose names differ only in case
425000001A9The file cannot be safely opened because it is not supported by this version of Windows
426000001AAThe cloud operation was not completed before the time-out period expired
427000001ABA task queue is required for this operation but none is available
428000001ACFailed loading a valid version of srcsrv.dll
429000001ADThis operation is not supported with BTT enabled
430000001AEThis operation cannot be performed because encryption is currently disabled
431000001AFThis encryption operation cannot be performed on filesystem metadata
432000001B0Encryption cannot be cleared on this file/directory because it still has an encrypted attribute
433000001B1A device which does not exist was specified
434000001B2Dehydration of the cloud file is disallowed by the cloud sync provider
435000001B3A file snapshot operation was attempted when one is already in progress
436000001B4A snapshot of the file cannot be taken because a user-mapped section is present
437000001B5The file snapshot operation was terminated because one of the files was modified in a way incompatible with a snapshot operation. Please try again
438000001B6An I/O request could not be coordinated with a file snapshot operation
439000001B7An unexpected error occurred while processing a file snapshot operation
440000001B8A file snapshot operation received an invalid parameter
441000001B9The operation could not be completed due to one or more unsatisfied dependencies
442000001BAThe file cannot be opened because the path has a case-sensitive directory
443000001BBThe filesystem couldn't handle one of the CacheManager's callback error codes
444000001BCWSL 2 requires an update to its kernel component. For information please visit https://aka.ms/wsl2kernel
445000001BDThis action is blocked
446000001BEThis action is blocked. Please refer to the data loss prevention notification for further information
449000001C1This action is blocked. Please refer to the data loss prevention notification for further information
450000001C2Neither developer unlocked mode nor side loading mode is enabled on the device
451000001C3Can not change application type during upgrade or re-provision
452000001C4The application has not been provisioned
453000001C5The requested capability can not be authorized for this application
454000001C6There is no capability authorization policy on the device
455000001C7The capability authorization database has been corrupted
456000001C8The custom capability's SCCD has an invalid catalog
457000001C9None of the authorized entity elements in the SCCD matched the app being installed; either the PFNs don't match
458000001CAThe custom capability's SCCD failed to parse
459000001CBThe custom capability's SCCD requires developer mode
460000001CCThere not all declared custom capabilities are found in the SCCD
470000001D6The CimFS image is corrupt
480000001E0The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request
481000001E1The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation
482000001E2The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation
483000001E3The request failed due to a fatal device hardware error
487000001E7Attempt to access invalid address
488000001E8The volume contains paging
500000001F4User profile cannot be loaded
510000001FEThe file system encountered a metadata file with inconsistent data
53400000216Arithmetic result exceeded 32 bits
53500000217There is a process on other end of the pipe
53600000218Waiting for a process to open the other end of the pipe
53700000219Application verifier has found an error in the current process
5380000021AAn error occurred in the ABIOS subsystem
5390000021BA warning occurred in the WX86 subsystem
5400000021CAn error occurred in the WX86 subsystem
5410000021DAn 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
5420000021EUnwind exception code
5430000021FAn invalid or unaligned stack was encountered during an unwind operation
54400000220An invalid unwind target was encountered during an unwind operation
54500000221Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
54600000222Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port
54700000223An attempt was made to lower a quota limit below the current usage
54800000224An attempt was made to attach to a device that was already attached to another device
54900000225An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references
55000000226Profiling not started
55100000227Profiling not stopped
55200000228The passed ACL did not contain the minimum required information
55300000229The number of active profiling objects is at the maximum and no more may be started
5540000022AUsed to indicate that an operation cannot continue without blocking for I/O
5550000022BIndicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process
5560000022CIf an MM error is returned which is not defined in the standard FsRtl filter
5570000022DIf an MM error is returned which is not defined in the standard FsRtl filter
5580000022EIf an MM error is returned which is not defined in the standard FsRtl filter
5590000022FA malformed function table was encountered during an unwind operation
56000000230Indicates 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
56100000231Indicates that an attempt was made to grow an LDT by setting its size
56300000233Indicates that the starting value for the LDT information was not an integral multiple of the selector size
56400000234Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors
56500000235Indicates a process has too many threads to perform the requested action. For example
56600000236An attempt was made to operate on a thread within a specific process
56700000237Page file quota was exceeded
56800000238The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role
56900000239The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required
5700000023AThe NtCreateFile API failed. This error should never be returned to an application
5710000023B{Privilege Failed}The I/O permissions for the process could not be changed
5720000023C{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C
5730000023D{Missing System File}The required system file %hs is bad or missing
5740000023E{Application Error}The exception %s (0x
5750000023F{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application
57600000240{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld
57700000241Windows 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
57800000242{No Paging File Specified}No paging file was specified in the system configuration
57900000243{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present
58000000244An event pair synchronization operation was performed using the thread specific client/server event pair object
58100000245A Windows Server has an incorrect configuration
58200000246An 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
58300000247The Unicode character is not defined in the Unicode character set installed on the system
58400000248The paging file cannot be created on a floppy diskette
58500000249The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected
5860000024AThis operation is only allowed for the Primary Domain Controller of the domain
5870000024BAn attempt was made to acquire a mutant such that its maximum count would have been exceeded
5880000024CA volume has been accessed for which a file system driver is required that has not yet been loaded
5890000024D{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt
5900000024E{Unexpected Failure in DebugActiveProcess}An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process
5910000024F{Fatal System Error}The %hs system process terminated unexpectedly with a status of 0x
59200000250{Data Not Accepted}The TDI client could not handle the data received during an indication
59300000251NTVDM encountered a hard error
59400000252{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time
59500000253{Reply Message Mismatch}An attempt was made to reply to an LPC message
59600000254{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
59700000255The 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
59800000256The stream is not a tiny stream
59900000257The request must be handled by the stack overflow code
60000000258Internal 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
60100000259The 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
6020000025AThe bucket array must be grown. Retry transaction after doing so
6030000025BThe user/kernel marshalling buffer has overflowed
6040000025CThe supplied variant structure contains invalid data
6050000025DThe specified buffer contains ill-formed data
6060000025E{Audit Failed}An attempt to generate a security audit failed
6070000025FThe timer resolution was not previously set by the current process
60800000260There is insufficient account information to log you on
60900000261{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
61000000262{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
61100000263There is an IP address conflict with another system on the network
61200000264There is an IP address conflict with another system on the network
61300000265{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
61400000266A callback return system service cannot be executed when no callback is active
61500000267The password provided is too short to meet the policy of your user account.Please choose a longer password
61600000268The 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
61700000269You 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
6180000026AThe specified compression format is unsupported
6190000026BThe specified hardware profile configuration is invalid
6200000026CThe specified Plug and Play registry device path is invalid
6210000026DThe specified quota list is internally inconsistent with its descriptor
6220000026E{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
6230000026F{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
62400000270{DLL Initialization Failed}The application failed to initialize because the window station is shutting down
62500000271The validation process needs to continue on to the next step
62600000272There are no more matches for the current index enumeration
62700000273The range could not be added to the range list because of a conflict
62800000274The server process is running under a SID different than that required by client
62900000275A group marked use for deny only cannot be enabled
63000000276{EXCEPTION}Multiple floating point faults
63100000277{EXCEPTION}Multiple floating point traps
63200000278The requested interface is not supported
63300000279{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode
6340000027AThe system file %1 has become corrupt and has been replaced
6350000027B{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
6360000027CA device was removed so enumeration must be restarted
6370000027D{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
6380000027EDevice will not start without a reboot
6390000027FThere is not enough power to complete the requested operation
64000000280ERROR_MULTIPLE_FAULT_VIOLATION
64100000281The system is in the process of shutting down
64200000282An attempt to remove a processes DebugPort was made
64300000283This version of Windows is not compatible with the behavior version of directory forest
64400000284The specified range could not be found in the range list
64600000286The driver was not loaded because the system is booting into safe mode
64700000287The driver was not loaded because it failed its initialization call
64800000288The "%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
64900000289The 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
6500000028AThe device object parameter is either not a valid device object or is not attached to the volume specified by the file name
6510000028BA Machine Check Error has occurred. Please check the system eventlog for additional information
6520000028CThere was error [%2] processing the driver database
6530000028DSystem hive size has exceeded its limit
6540000028EThe driver could not be loaded because a previous version of the driver is still in memory
6550000028F{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation
65600000290The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted
65700000291The password provided is too long to meet the policy of your user account.Please choose a shorter password
66500000299The requested operation could not be completed due to a file system limitation
6680000029CAn assertion failure has occurred
6690000029DAn error occurred in the ACPI subsystem
6700000029EWOW Assertion Error
6710000029FA device is missing in the system BIOS MPS table. This device will not be used.Please contact your system vendor for system BIOS update
672000002A0A translator failed to translate resources
673000002A1A IRQ translator failed to translate resources
674000002A2Driver %2 returned invalid ID for a child device (%3)
675000002A3{Kernel Debugger Awakened}the system debugger was awakened by an interrupt
676000002A4{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation
677000002A5{Too Much Information}The specified access control list (ACL) contained more information than was expected
678000002A6This warning level status indicates that the transaction state already exists for the registry sub-tree
679000002A7{Media Changed}The media may have changed
680000002A8{GUID Substitution}During the translation of a global identifier (GUID) to a Windows security ID (SID)
681000002A9The create operation stopped after reaching a symbolic link
682000002AAA long jump has been executed
683000002ABThe Plug and Play query operation was not successful
684000002ACA frame consolidation has been executed
685000002AD{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost
686000002AEThe application is attempting to run executable code from the module %hs. This may be insecure. An alternative
687000002AFThe application is loading executable code from the module %hs. This is secure
688000002B0Debugger did not handle the exception
689000002B1Debugger will reply later
690000002B2Debugger cannot provide handle
691000002B3Debugger terminated thread
692000002B4Debugger terminated process
693000002B5Debugger got control C
694000002B6Debugger printed exception on control C
695000002B7Debugger received RIP exception
696000002B8Debugger received control break
697000002B9Debugger command communication exception
698000002BA{Object Exists}An attempt was made to create an object and the object name already existed
699000002BB{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed
700000002BC{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
701000002BDThis informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created
702000002BE{Segment Load}A virtual DOS machine (VDM) is loading
703000002BF{Invalid Current Directory}The process cannot switch to the startup current directory %hs.Select OK to set current directory to %hs
704000002C0{Redundant Read}To satisfy a read request
705000002C1{Redundant Write}To satisfy a write request
706000002C2{Machine Type Mismatch}The image file %hs is valid
707000002C3{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later
708000002C4{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system
709000002C5{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
710000002C6{TDI Event Done}The TDI indication has completed successfully
711000002C7{TDI Event Pending}The TDI indication has entered the pending state
712000002C8Checking file system on %wZ
713000002C9{Fatal Application Exit}%hs
714000002CAThe specified registry key is referenced by a predefined handle
715000002CB{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
716000002CC%hs
717000002CD{Page Locked}One of the pages to lock was already locked
718000002CEApplication popup: %1 : %2
719000002CFERROR_ALREADY_WIN32
720000002D0{Machine Type Mismatch}The image file %hs is valid
721000002D1A yield execution was performed and no thread was available to run
722000002D2The resumable flag to a timer API was ignored
723000002D3The arbiter has deferred arbitration of these resources to its parent
724000002D4The inserted CardBus device cannot be started because of a configuration error on "%hs"
725000002D5The 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
726000002D6The system was put into hibernation
727000002D7The system was resumed from hibernation
728000002D8Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2
729000002D9A 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
730000002DAThe system has awoken
731000002DBERROR_WAIT_1
732000002DCERROR_WAIT_2
733000002DDERROR_WAIT_3
734000002DEERROR_WAIT_63
735000002DFERROR_ABANDONED_WAIT_0
736000002E0ERROR_ABANDONED_WAIT_63
737000002E1ERROR_USER_APC
738000002E2ERROR_KERNEL_APC
739000002E3ERROR_ALERTED
740000002E4The requested operation requires elevation
741000002E5A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
742000002E6An open/create operation completed while an oplock break is underway
743000002E7A new volume has been mounted by a file system
744000002E8This success level status indicates that the transaction state already exists for the registry sub-tree
745000002E9This indicates that a notify change request has been completed due to closing the handle which made the notify change request
746000002EA{Connect Failure on Primary Transport}An attempt was made to connect to the remote server %hs on the primary transport
747000002EBPage fault was a transition fault
748000002ECPage fault was a demand zero fault
749000002EDPage fault was a demand zero fault
750000002EEPage fault was a demand zero fault
751000002EFPage fault was satisfied by reading from a secondary storage device
752000002F0Cached page was locked during operation
753000002F1Crash dump exists in paging file
754000002F2Specified buffer contains all zeros
755000002F3A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
756000002F4The device has succeeded a query-stop and its resource requirements have changed
757000002F5The translator has translated these resources into the global space and no further translations should be performed
758000002F6A process being terminated has no threads to terminate
759000002F7The specified process is not part of a job
760000002F8The specified process is part of a job
761000002F9{Volume Shadow Copy Service}The system is now ready for hibernation
762000002FAA file system or file system filter driver has successfully completed an FsFilter operation
763000002FBThe specified interrupt vector was already connected
764000002FCThe specified interrupt vector is still connected
765000002FDAn operation is blocked waiting for an oplock
766000002FEDebugger handled exception
767000002FFDebugger continued
76800000300An exception occurred in a user mode callback and the kernel callback frame should be removed
76900000301Compression is disabled for this volume
77000000302The data provider cannot fetch backwards through a result set
77100000303The data provider cannot scroll backwards through a result set
77200000304The data provider requires that previously fetched data is released before asking for more data
77300000305The data provider was not able to interpret the flags set for a column binding in an accessor
77400000306One or more errors occurred while processing the request
77500000307The implementation is not capable of performing the request
77600000308The client of a component requested an operation which is not valid given the state of the component instance
77700000309A version number could not be parsed
7780000030AThe iterator's start position is invalid
7790000030BThe hardware has reported an uncorrectable memory error
7800000030CThe attempted operation required self healing to be enabled
7810000030DThe Desktop heap encountered an error while allocating session memory. There is more information in the system event log
7820000030EThe system power state is transitioning from %2 to %3
7830000030FThe system power state is transitioning from %2 to %3 but could enter %4
78400000310A thread is getting dispatched with MCA EXCEPTION because of MCA
78500000311Access to %1 is monitored by policy rule %2
78600000312Access to %1 has been restricted by your Administrator by policy rule %2
78700000313A valid hibernation file has been invalidated and should be abandoned
78800000314{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
78900000315{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
79000000316{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
79100000317The resources required for this device conflict with the MCFG table
79200000318The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired
79300000319The volume repair was not successful
7940000031AOne of the volume corruption logs is full. Further corruptions that may be detected won't be logged
7950000031BOne of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned
7960000031COne of the volume corruption logs is unavailable for being operated on
7970000031DOne of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned
7980000031EOne of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions
7990000031FOrphaned 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
80000000320The oplock that was associated with this handle is now associated with a different handle
80100000321An oplock of the requested level cannot be granted. An oplock of a lower level may be available
80200000322The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken
80300000323The handle with which this oplock was associated has been closed. The oplock is now broken
80400000324The specified access control entry (ACE) does not contain a condition
80500000325The specified access control entry (ACE) contains an invalid condition
80600000326Access to the specified file handle has been revoked
80700000327{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
80800000328The read or write operation to an encrypted file could not be completed because the file has not been opened for data access
80900000329File metadata optimization is already in progress
8100000032AThe requested operation failed due to quota operation is still in progress
8110000032BAccess to the specified handle has been revoked
8120000032CThe callback function must be invoked inline
8130000032DThe specified CPU Set IDs are invalid
8140000032EThe specified enclave has not yet been terminated
8150000032FAn attempt was made to access protected memory in violation of its secure access policy
994000003E2Access to the extended attribute was denied
995000003E3The I/O operation has been aborted because of either a thread exit or an application request
996000003E4Overlapped I/O event is not in a signaled state
997000003E5Overlapped I/O operation is in progress
998000003E6Invalid access to memory location
999000003E7Error performing inpage operation
1001000003E9Recursion too deep; the stack overflowed
1002000003EAThe window cannot act on the sent message
1003000003EBCannot complete this function
1004000003ECInvalid flags
1005000003EDThe volume does not contain a recognized file system.Please make sure that all required file system drivers are loaded and that the volume is not corrupted
1006000003EEThe volume for a file has been externally altered so that the opened file is no longer valid
1007000003EFThe requested operation cannot be performed in full-screen mode
1008000003F0An attempt was made to reference a token that does not exist
1009000003F1The configuration registry database is corrupt
1010000003F2The configuration registry key is invalid
1011000003F3The configuration registry key could not be opened
1012000003F4The configuration registry key could not be read
1013000003F5The configuration registry key could not be written
1014000003F6One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful
1015000003F7The registry is corrupted. The structure of one of the files containing registry data is corrupted
1016000003F8An I/O operation initiated by the registry failed unrecoverably. The registry could not read in
1017000003F9The system has attempted to load or restore a file into the registry
1018000003FAIllegal operation attempted on a registry key that has been marked for deletion
1019000003FBSystem could not allocate the required space in a registry log
1020000003FCCannot create a symbolic link in a registry key that already has subkeys or values
1021000003FDCannot create a stable subkey under a volatile parent key
1022000003FEA notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes
10510000041BA stop control has been sent to a service that other running services are dependent on
10520000041CThe requested control is not valid for this service
10530000041DThe service did not respond to the start or control request in a timely fashion
10540000041EA thread could not be created for the service