Win32Exception List

ErrorCodeNativeErrorCodeMessage
-21407334390x80670001Optimistic locking failure. Data cannot be updated if it has changed since it was read
-21407334380x80670002A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits
-21407334370x80670003The StateRepository configuration is not valid
-21407334360x80670004The StateRepository schema version is not known
-21407334350x80670005A StateRepository dictionary is not valid
-21407334340x80670006The request failed because the StateRepository is actively blocking requests
-21407334330x80670007The database file is locked. The request will be retried
-21407334320x80670008The database file is locked because another process is busy recovering the database. The request will be retried
-21407334310x80670009A table in the database is locked. The request will be retried
-21407334300x8067000AThe shared cache for the database is locked by another connection. The request will be retried
-21389639670x80820001The bootfile is too small to support persistent snapshots
-21388984310x80830001The specified volume does not support storage tiers
-21388984300x80830002The Storage Tiers Management service detected that the specified volume is in the process of being dismounted
-21388984290x80830003The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid
-21388984280x80830004The file identifier specified is not valid on the volume
-21388984270x80830005Storage tier operations must be called on the clustering node that owns the metadata volume
-21388984260x80830006The Storage Tiers Management service is already optimizing the storage tiers on the specified volume
-21388984250x80830007The requested object type cannot be assigned to a storage tier
-21387018230x80860001Authentication target is invalid or not configured correctly
-21387018220x80860002Your application cannot get the Online Id properties due to the Terms of Use accepted by the user
-21387018210x80860003The application requesting authentication tokens is either disabled or incorrectly configured
-21387018200x80860004Online Id password must be updated before signin
-21387018190x80860005Online Id account properties must be updated before signin
-21387018180x80860006To help protect your Online Id account you must signin again
-21387018170x80860007Online Id account was locked because there have been too many attempts to sign in
-21387018160x80860008Online Id account requires parental consent before proceeding
-21387018150x80860009Online Id signin name is not yet verified. Email verification is required before signin
-21387018140x8086000AWe have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account
-21387018130x8086000BWe detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account
-21387018120x8086000CUser interaction is required for authentication
-21387018110x8086000DUser has reached the maximum device associations per user limit
-21387018100x8086000ECannot sign out from the application since the user account is connected
-21387018090x8086000FUser authentication is required for this operation
-21387018080x80860010We want to make sure this is you. User interaction is required for authentication
-21359493110x80B00001Could not create new process from ARM architecture device
-21359493100x80B00002Could not attach to the application process from ARM architecture device
-21359493090x80B00003Could not connect to dbgsrv server from ARM architecture device
-21359493080x80B00004Could not start dbgsrv server from ARM architecture device
-21323448310x80E70001The specified fault domain type or combination of minimum / maximum fault domain type is not valid
-21323448300x80E70002A Storage Spaces internal error occurred
-21323448290x80E70003The specified resiliency type is not valid
-21323448280x80E70004The physical disk's sector size is not supported by the storage pool
-21323448260x80E70006The requested redundancy is outside of the supported range of values
-21323448250x80E70007The number of data copies requested is outside of the supported range of values
-21323448240x80E70008The value for ParityLayout is outside of the supported range of values
-21323448230x80E70009The value for interleave length is outside of the supported range of values or is not a power of 2
-21323448220x80E7000AThe number of columns specified is outside of the supported range of values
-21323448210x80E7000BThere were not enough physical disks to complete the requested operation
-21323448200x80E7000CExtended error information is available
-21323448190x80E7000DThe specified provisioning type is not valid
-21323448180x80E7000EThe allocation size is outside of the supported range of values
-21323448170x80E7000FEnclosure awareness is not supported for this virtual disk
-21323448160x80E70010The write cache size is outside of the supported range of values
-21323448150x80E70011The value for number of groups is outside of the supported range of values
-21323448140x80E70012The OperationalState of the physical disk is invalid for this operation
-21474836470x80000001Not implemented
-21474836460x80000002Ran out of memory
-21474836450x80000003One or more arguments are invalid
-21474836440x80000004No such interface supported
-21474836430x80000005Invalid pointer
-21474836420x80000006Invalid handle
-21474836410x80000007Operation aborted
-21474836400x80000008Unspecified error
-21474836390x80000009General access denied error
-21474836380x8000000AThe data necessary to complete this operation is not yet available
-21474836370x8000000BThe operation attempted to access data outside the valid range
-21474836360x8000000CA concurrent or interleaved operation changed the state of the object, invalidating this operation
-21474836350x8000000DAn illegal state change was requested
-21474836340x8000000EA method was called at an unexpected time
-21474836330x8000000FTypename or Namespace was not found in metadata file
-21474836320x80000010Name is an existing namespace rather than a typename
-21474836310x80000011Typename has an invalid format
-21474836300x80000012Metadata file is invalid or corrupted
-21474836290x80000013The object has been closed
-21474836280x80000014Only one thread may access the object during a write operation
-21474836270x80000015Operation is prohibited during change notification
-21474836260x80000016The text associated with this error code could not be found
-21474836250x80000017String not null terminated
-21474836240x80000018A delegate was assigned when not allowed
-21474836230x80000019An async operation was not properly started
-21474836220x8000001AThe application is exiting and cannot service this request
-21474836210x8000001BThe application view is exiting and cannot service this request
-21474836200x8000001CThe object must support the IAgileObject interface
-21474836190x8000001DActivating a single-threaded class from MTA is not supported
-21474836180x8000001EThe object has been committed
-21474836170x8000001FA 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
-21474672630x80004001Not implemented
-21474672620x80004002No such interface supported
-21474672610x80004003Invalid pointer
-21474672600x80004004Operation aborted
-21474672590x80004005Unspecified error
-21474672580x80004006Thread local storage failure
-21474672570x80004007Get shared memory allocator failure
-21474672560x80004008Get memory allocator failure
-21474672550x80004009Unable to initialize class cache
-21474672540x8000400AUnable to initialize RPC services
-21474672530x8000400BCannot set thread local storage channel control
-21474672520x8000400CCould not allocate thread local storage channel control
-21474672510x8000400DThe user supplied memory allocator is unacceptable
-21474672500x8000400EThe OLE service mutex already exists
-21474672490x8000400FThe OLE service file mapping already exists
-21474672480x80004010Unable to map view of file for OLE service
-21474672470x80004011Failure attempting to launch OLE service
-21474672460x80004012There was an attempt to call CoInitialize a second time while single threaded
-21474672450x80004013A Remote activation was necessary but was not allowed
-21474672440x80004014A Remote activation was necessary but the server name provided was invalid
-21474672430x80004015The class is configured to run as a security id different from the caller
-21474672420x80004016Use of Ole1 services requiring DDE windows is disabled
-21474672410x80004017A RunAs specification must be \ or simply
-21474672400x80004018The server process could not be started. The pathname may be incorrect
-21474672390x80004019The server process could not be started as the configured identity. The pathname may be incorrect or unavailable
-21474672380x8000401AThe server process could not be started because the configured identity is incorrect. Check the username and password
-21474672370x8000401BThe client is not allowed to launch this server
-21474672360x8000401CThe service providing this server could not be started
-21474672350x8000401DThis computer was unable to communicate with the computer providing the server
-21474672340x8000401EThe server did not respond after being launched
-21474672330x8000401FThe registration information for this server is inconsistent or incomplete
-21474672320x80004020The registration information for this interface is inconsistent or incomplete
-21474672310x80004021The operation attempted is not supported
-21474672300x80004022A dll must be loaded
-21474672290x80004023A Microsoft Software Installer error was encountered
-21474672280x80004024The specified activation could not occur in the client context as specified
-21474672270x80004025Activations on the server are paused
-21474672260x80004026Activations on the server are not paused
-21474672250x80004027The component or application containing the component has been disabled
-21474672240x80004028The common language runtime is not available
-21474672230x80004029The thread-pool rejected the submitted asynchronous work
-21474672220x8000402AThe server started, but did not finish initializing in a timely fashion
-21474672210x8000402BUnable to complete the call since there is no COM+ security context inside IObjectControl.Activate
-21474672160x80004030The provided tracker configuration is invalid
-21474672150x80004031The provided thread pool configuration is invalid
-21474672140x80004032The provided side-by-side configuration is invalid
-21474672130x80004033The server principal name (SPN) obtained during security negotiation is malformed
-21474672120x80004034The caller failed to revoke a per-apartment registration before apartment shutdown
-21474672110x80004035The object has been rundown by the stub manager while there are external clients
-21474181130x8000FFFFCatastrophic failure
-21474181110x80010001Call was rejected by callee
-21474181100x80010002Call was canceled by the message filter
-21474181090x80010003The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage
-21474181080x80010004The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call
-21474181070x80010005It is illegal to call out while inside message filter
-21474181060x80010006The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid
-21474181050x80010007The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed
-21474181040x80010008The caller (client) disappeared while the callee (server) was processing a call
-21474181030x80010009The data packet with the marshalled parameter data is incorrect
-21474181020x8001000AThe call was not transmitted properly; the message queue was full and was not emptied after yielding
-21474181010x8001000BThe client (caller) cannot marshall the parameter data - low memory, etc
-21474181000x8001000CThe client (caller) cannot unmarshall the return data - low memory, etc
-21474180990x8001000DThe server (callee) cannot marshall the return data - low memory, etc
-21474180980x8001000EThe server (callee) cannot unmarshall the parameter data - low memory, etc
-21474180970x8001000FReceived data is invalid; could be server or client data
-21474180960x80010010A particular parameter is invalid and cannot be (un)marshalled
-21474180950x80010011There is no second outgoing call on same channel in DDE conversation
-21474180940x80010012The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute
-21474178560x80010100System call failed
-21474178550x80010101Could not allocate some required resource (memory, events, ...)
-21474178540x80010102Attempted to make calls on more than one thread in single threaded mode
-21474178530x80010103The requested interface is not registered on the server object
-21474178520x80010104RPC could not call the server or could not return the results of calling the server
-21474178510x80010105The server threw an exception
-21474178500x80010106Cannot change thread mode after it is set
-21474178490x80010107The method called does not exist on the server
-21474178480x80010108The object invoked has disconnected from its clients
-21474178470x80010109The object invoked chose not to process the call now. Try again later
-21474178460x8001010AThe message filter indicated that the application is busy
-21474178450x8001010BThe message filter rejected the call
-21474178440x8001010CA call control interfaces was called with invalid data
-21474178430x8001010DAn outgoing call cannot be made since the application is dispatching an input-synchronous call
-21474178420x8001010EThe application called an interface that was marshalled for a different thread
-21474178410x8001010FCoInitialize has not been called on the current thread
-21474178400x80010110The version of OLE on the client and server machines does not match
-21474178390x80010111OLE received a packet with an invalid header
-21474178380x80010112OLE received a packet with an invalid extension
-21474178370x80010113The requested object or interface does not exist
-21474178360x80010114The requested object does not exist
-21474178350x80010115OLE has sent a request and is waiting for a reply
-21474178340x80010116OLE is waiting before retrying a request
-21474178330x80010117Call context cannot be accessed after call completed
-21474178320x80010118Impersonate on unsecure calls is not supported
-21474178310x80010119Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized
-21474178300x8001011ANo 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
-21474178290x8001011BAccess is denied
-21474178280x8001011CRemote calls are not allowed for this process
-21474178270x8001011DThe marshaled interface data packet (OBJREF) has an invalid or unknown format
-21474178260x8001011ENo context is associated with this call. This happens for some custom marshalled calls and on the client side of the call
-21474178250x8001011FThis operation returned because the timeout period expired
-21474178240x80010120There are no synchronize objects to wait on
-21474178230x80010121Full subject issuer chain SSL principal name expected from the server
-21474178220x80010122Principal name is not a valid MSSTD name
-21474178210x80010123Unable to impersonate DCOM client
-21474178200x80010124Unable to obtain server's security context
-21474178190x80010125Unable to open the access token of the current thread
-21474178180x80010126Unable to obtain user info from an access token
-21474178170x80010127The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method
-21474178160x80010128Unable to obtain the client's security blanket
-21474178150x80010129Unable to set a discretionary ACL into a security descriptor
-21474178140x8001012AThe system function, AccessCheck, returned false
-21474178130x8001012BEither NetAccessDel or NetAccessAdd returned an error code
-21474178120x8001012COne of the trustee strings provided by the user did not conform to the \ syntax and it was not the *"" string""
-21474178110x8001012DOne of the security identifiers provided by the user was invalid
-21474178100x8001012EUnable to convert a wide character trustee string to a multibyte trustee string
-21474178090x8001012FUnable to find a security identifier that corresponds to a trustee string provided by the user
-21474178080x80010130The system function, LookupAccountSID, failed
-21474178070x80010131Unable to find a trustee name that corresponds to a security identifier provided by the user
-21474178060x80010132The system function, LookupAccountName, failed
-21474178050x80010133Unable to set or reset a serialization handle
-21474178040x80010134Unable to obtain the Windows directory
-21474178030x80010135Path too long
-21474178020x80010136Unable to generate a uuid
-21474178010x80010137Unable to create file
-21474178000x80010138Unable to close a serialization handle or a file handle
-21474177990x80010139The number of ACEs in an ACL exceeds the system limit
-21474177980x8001013ANot all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream
-21474177970x8001013BThe version of ACL format in the stream is not supported by this implementation of IAccessControl
-21474177960x8001013CUnable to open the access token of the server process
-21474177950x8001013DUnable to decode the ACL in the stream provided by the user
-21474177930x8001013FThe COM IAccessControl object is not initialized
-21474177920x80010140Call Cancellation is disabled
-21473525770x8001FFFFAn internal error occurred
-21473525750x80020001Unknown interface
-21473525730x80020003Member not found
-21473525720x80020004Parameter not found
-21473525710x80020005Type mismatch
-21473525700x80020006Unknown name
-21473525690x80020007No named arguments
-21473525680x80020008Bad variable type
-21473525670x80020009Exception occurred
-21473525660x8002000AOut of present range
-21473525650x8002000BInvalid index
-21473525640x8002000CUnknown language
-21473525630x8002000DMemory is locked
-21473525620x8002000EInvalid number of parameters
-21473525610x8002000FParameter not optional
-21473525600x80020010Invalid callee
-21473525590x80020011Does not support a collection
-21473525580x80020012Division by zero
-21473525570x80020013Buffer too small
-21473197860x80028016Buffer too small
-21473197850x80028017Field name not defined in the record
-21473197840x80028018Old format or invalid type library
-21473197830x80028019Old format or invalid type library
-21473197800x8002801CError accessing the OLE registry
-21473197790x8002801DLibrary not registered
-21473197690x80028027Bound to unknown type
-21473197680x80028028Qualified name disallowed
-21473197670x80028029Invalid forward reference, or reference to uncompiled type
-21473197660x8002802AType mismatch
-21473197650x8002802BElement not found
-21473197640x8002802CAmbiguous name
-21473197630x8002802DName already exists in the library
-21473197620x8002802EUnknown LCID
-21473197610x8002802FFunction not defined in specified DLL
-21473175710x800288BDWrong module kind for the operation
-21473175630x800288C5Size may not exceed 64K
-21473175620x800288C6Duplicate ID in inheritance hierarchy
-21473175530x800288CFIncorrect inheritance depth in standard OLE hmember
-21473165760x80028CA0Type mismatch
-21473165750x80028CA1Invalid number of arguments
-21473165740x80028CA2I/O Error
-21473165730x80028CA3Error creating unique tmp file
-21473125660x80029C4AError loading type library/DLL
-21473125090x80029C83Inconsistent property functions
-21473125080x80029C84Circular dependency between types/modules
-21472870390x80030001Unable to perform requested operation
-21472870380x80030002%1 could not be found
-21472870370x80030003The path %1 could not be found
-21472870360x80030004There are insufficient resources to open another file
-21472870350x80030005Access Denied
-21472870340x80030006Attempted an operation on an invalid object
-21472870320x80030008There is insufficient memory available to complete operation
-21472870310x80030009Invalid pointer error
-21472870220x80030012There are no more entries to return
-21472870210x80030013Disk is write-protected
-21472870150x80030019An error occurred during a seek operation
-21472870110x8003001DA disk error occurred during a write operation
-21472870100x8003001EA disk error occurred during a read operation
-21472870080x80030020A share violation has occurred
-21472870070x80030021A lock violation has occurred
-21472869600x80030050%1 already exists
-21472869530x80030057Invalid parameter error
-21472869280x80030070There is insufficient disk space to complete operation
-21472868000x800300F0Illegal write of non-simple property to simple property set
-21472867900x800300FAAn API call exited abnormally
-21472867890x800300FBThe file %1 is not a valid compound file
-21472867880x800300FCThe name %1 is not valid
-21472867870x800300FDAn unexpected error occurred
-21472867860x800300FEThat function is not implemented
-21472867850x800300FFInvalid flag error
-21472867840x80030100Attempted to use an object that is busy
-21472867830x80030101The storage has been changed since the last commit
-21472867820x80030102Attempted to use an object that has ceased to exist
-21472867810x80030103Can't save
-21472867800x80030104The compound file %1 was produced with an incompatible version of storage
-21472867790x80030105The compound file %1 was produced with a newer version of storage
-21472867780x80030106Share.exe or equivalent is required for operation
-21472867770x80030107Illegal operation called on non-file based storage
-21472867760x80030108Illegal operation called on object with extant marshallings
-21472867750x80030109The docfile has been corrupted
-21472867680x80030110OLE32.DLL has been loaded at the wrong address
-21472867670x80030111The compound file is too large for the current implementation
-21472867660x80030112The compound file was not created with the STGM_SIMPLE flag
-21472865270x80030201The file download was aborted abnormally. The file is incomplete
-21472865260x80030202The file download has been terminated
-21472865200x80030208The specified firmware slot is invalid
-21472865190x80030209The specified firmware image is invalid
-21472862670x80030305Generic Copy Protection Error
-21472862660x80030306Copy Protection Error - DVD CSS Authentication failed
-21472862650x80030307Copy Protection Error - The given sector does not have a valid CSS key
-21472862640x80030308Copy Protection Error - DVD session key not established
-21472862630x80030309Copy Protection Error - The read failed because the sector is encrypted
-21472862620x8003030ACopy Protection Error - The current DVD's region does not correspond to the region setting of the drive
-21472862610x8003030BCopy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted
-21472215040x80040000Invalid OLEVERB structure
-21472215030x80040001Invalid advise flags
-21472215020x80040002Can't enumerate any more, because the associated data is missing
-21472215010x80040003This implementation doesn't take advises
-21472215000x80040004There is no connection for this connection ID
-21472214990x80040005Need to run the object to perform this operation
-21472214980x80040006There is no cache to operate on
-21472214970x80040007Uninitialized object
-21472214960x80040008Linked object's source class has changed
-21472214950x80040009Not able to get the moniker of the object
-21472214940x8004000ANot able to bind to the source
-21472214930x8004000BObject is static; operation not allowed
-21472214920x8004000CUser canceled out of save dialog
-21472214910x8004000DInvalid rectangle
-21472214900x8004000Ecompobj.dll is too old for the ole2.dll initialized
-21472214890x8004000FInvalid window handle
-21472214880x80040010Object is not in any of the inplace active states
-21472214870x80040011Not able to convert object
-21472214860x80040012Not able to perform the operation because object is not given storage yet
-21472214040x80040064Invalid FORMATETC structure
-21472214030x80040065Invalid DVTARGETDEVICE structure
-21472214020x80040066Invalid STDGMEDIUM structure
-21472214010x80040067Invalid STATDATA structure
-21472214000x80040068Invalid lindex
-21472213990x80040069Invalid tymed
-21472213980x8004006AInvalid clipboard format
-21472213970x8004006BInvalid aspect(s)
-21472213960x8004006CtdSize parameter of the DVTARGETDEVICE structure is invalid
-21472213950x8004006DObject doesn't support IViewObject interface
-21472212480x80040100Trying to revoke a drop target that has not been registered
-21472212470x80040101This window has already been registered as a drop target
-21472212460x80040102Invalid window handle
-21472212450x80040103A drag operation is already in progress
-21472212320x80040110Class does not support aggregation (or class object is remote)
-21472212310x80040111ClassFactory cannot supply requested class
-21472212300x80040112Class is not licensed for use
-21472211840x80040140Error drawing view
-21472211680x80040150Could not read key from registry
-21472211670x80040151Could not write key to registry
-21472211660x80040152Could not find the key in the registry
-21472211650x80040153Invalid value for registry
-21472211640x80040154Class not registered
-21472211630x80040155Interface not registered
-21472211620x80040156Threading model entry is not valid
-21472211520x80040160CATID does not exist
-21472211510x80040161Description not found
-21472211480x80040164No package in the software installation data in the Active Directory meets this criteria
-21472211470x80040165Deleting this will break the referential integrity of the software installation data in the Active Directory
-21472211460x80040166The CLSID was not found in the software installation data in the Active Directory
-21472211450x80040167The software installation data in the Active Directory is corrupt
-21472211440x80040168There is no software installation data in the Active Directory
-21472211430x80040169There is no software installation data object in the Active Directory
-21472211420x8004016AThe software installation data object in the Active Directory already exists
-21472211410x8004016BThe path to the software installation data in the Active Directory is not correct
-21472211400x8004016CA network error interrupted the operation
-21472211390x8004016DThe size of this object exceeds the maximum size set by the Administrator
-21472211380x8004016EThe schema for the software installation data in the Active Directory does not match the required schema
-21472211370x8004016FAn error occurred in the software installation data in the Active Directory
-21472211360x80040170Cache not updated
-21472211200x80040180No verbs for OLE object
-21472211190x80040181Invalid verb for OLE object
-21472210880x800401A0Undo is not available
-21472210870x800401A1Space for tools is not available
-21472210560x800401C0OLESTREAM Get method failed
-21472210550x800401C1OLESTREAM Put method failed
-21472210540x800401C2Contents of the OLESTREAM not in correct format
-21472210530x800401C3There was an error in a Windows GDI call while converting the bitmap to a DIB
-21472210520x800401C4Contents of the IStorage not in correct format
-21472210510x800401C5Contents of IStorage is missing one of the standard streams
-21472210500x800401C6There was an error in a Windows GDI call while converting the DIB to a bitmap
-21472210400x800401D0OpenClipboard Failed
-21472210390x800401D1EmptyClipboard Failed
-21472210380x800401D2SetClipboard Failed
-21472210370x800401D3Data on clipboard is invalid
-21472210360x800401D4CloseClipboard Failed
-21472210240x800401E0Moniker needs to be connected manually
-21472210230x800401E1Operation exceeded deadline
-21472210220x800401E2Moniker needs to be generic
-21472210210x800401E3Operation unavailable
-21472210200x800401E4Invalid syntax
-21472210190x800401E5No object for moniker
-21472210180x800401E6Bad extension for file
-21472210170x800401E7Intermediate operation failed
-21472210160x800401E8Moniker is not bindable
-21472210150x800401E9Moniker is not bound
-21472210140x800401EAMoniker cannot open file
-21472210130x800401EBUser input required for operation to succeed
-21472210120x800401ECMoniker class has no inverse
-21472210110x800401EDMoniker does not refer to storage
-21472210100x800401EENo common prefix
-21472210090x800401EFMoniker could not be enumerated
-21472210080x800401F0CoInitialize has not been called
-21472210070x800401F1CoInitialize has already been called
-21472210060x800401F2Class of object cannot be determined
-21472210050x800401F3Invalid class string
-21472210040x800401F4Invalid interface string
-21472210030x800401F5Application not found
-21472210020x800401F6Application cannot be run more than once
-21472210010x800401F7Some error in application program
-21472210000x800401F8DLL for class not found
-21472209990x800401F9Error in the DLL
-21472209980x800401FAWrong OS or OS version for application
-21472209970x800401FBObject is not registered
-21472209960x800401FCObject is already registered
-21472209950x800401FDObject is not connected to server
-21472209940x800401FEApplication was launched but it didn't register a class factory
-21472209930x800401FFObject has been released
-21472209910x80040201An event was unable to invoke any of the subscribers
-21472209890x80040203A syntax error occurred trying to evaluate a query string
-21472209880x80040204An invalid field name was used in a query string
-21472209870x80040205An unexpected exception was raised
-21472209860x80040206An unexpected internal error was detected
-21472209850x80040207The owner SID on a per-user subscription doesn't exist
-21472209840x80040208A user-supplied component or subscriber raised an exception
-21472209830x80040209An interface has too many methods to fire events from
-21472209820x8004020AA subscription cannot be stored unless its event class already exists
-21472209810x8004020BNot all the objects requested could be removed
-21472209800x8004020CCOM+ is required for this operation, but is not installed
-21472209790x8004020DCannot modify or delete an object that was not added using the COM+ Admin SDK
-21472209780x8004020ECannot modify or delete an object that was added using the COM+ Admin SDK
-21472209770x8004020FThe event class for this subscription is in an invalid partition
-21472209760x80040210The owner of the PerUser subscription is not logged on to the system specified
-21472209740x80040212TabletPC inking error code. No default tablet
-21472209670x80040219TabletPC inking error code. An invalid input rectangle was specified
-21472209650x8004021BTabletPC inking error code. Unknown property specified
-21472209580x80040222TabletPC inking error code. The stroke object was deleted
-21472209570x80040223TabletPC inking error code. Initialization failure
-21472209420x80040232TabletPC inking error code. The data required for the operation was not supplied
-21472209410x80040233TabletPC inking error code. Invalid packet description
-21472209390x80040235TabletPC inking error code. There are no handwriting recognizers registered
-21472209380x80040236TabletPC inking error code. User does not have the necessary rights to read recognizer information
-21472209370x80040237TabletPC inking error code. API calls were made in an incorrect order
-21472209360x80040238TabletPC inking error code. Queue is full
-21472209350x80040239TabletPC inking error code. RtpEnabled called multiple times
-21472209340x8004023ATabletPC inking error code. A recognizer returned invalid data
-21472209270x80040241TabletPC inking error code. The property was not found, or supported by the recognizer
-21472166310x80041309Trigger not found
-21472166300x8004130AOne or more of the properties that are needed to run this task have not been set
-21472166290x8004130BThere is no running instance of the task
-21472166280x8004130CThe Task Scheduler Service is not installed on this computer
-21472166270x8004130DThe task object could not be opened
-21472166260x8004130EThe object is either an invalid task object or is not a task object
-21472166250x8004130FNo account information could be found in the Task Scheduler security database for the task indicated
-21472166240x80041310Unable to establish existence of the account specified
-21472166230x80041311Corruption was detected in the Task Scheduler security database; the database has been reset
-21472166220x80041312Task Scheduler security services are available only on Windows NT
-21472166210x80041313The task object version is either unsupported or invalid
-21472166200x80041314The task has been configured with an unsupported combination of account settings and run time options
-21472166190x80041315The Task Scheduler Service is not running
-21472166180x80041316The task XML contains an unexpected node
-21472166170x80041317The task XML contains an element or attribute from an unexpected namespace
-21472166160x80041318The task XML contains a value which is incorrectly formatted or out of range
-21472166150x80041319The task XML is missing a required element or attribute
-21472166140x8004131AThe task XML is malformed
-21472166110x8004131DThe task XML contains too many nodes of the same type
-21472166100x8004131EThe task cannot be started after the trigger's end boundary
-21472166090x8004131FAn instance of this task is already running
-21472166080x80041320The task will not run because the user is not logged on
-21472166070x80041321The task image is corrupt or has been tampered with
-21472166060x80041322The Task Scheduler service is not available
-21472166050x80041323The Task Scheduler service is too busy to handle your request. Please try again later
-21472166040x80041324The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition
-21472166020x80041326The task is disabled
-21472166010x80041327The task has properties that are not compatible with previous versions of Windows
-21472166000x80041328The task settings do not allow the task to start on demand
-21472165990x80041329The combination of properties that task is using is not compatible with the scheduling engine
-21472165920x80041330The task definition uses a deprecated feature
-21471682560x8004D000Another single phase resource manager has already been enlisted in this transaction
-21471682550x8004D001A retaining commit or abort is not supported
-21471682540x8004D002The transaction failed to commit for an unknown reason. The transaction was aborted
-21471682530x8004D003Cannot call commit on this transaction object because the calling application did not initiate the transaction
-21471682520x8004D004Instead of committing, the resource heuristically aborted
-21471682510x8004D005Instead of aborting, the resource heuristically committed
-21471682500x8004D006Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions
-21471682490x8004D007Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions
-21471682480x8004D008The requested isolation level is not valid or supported
-21471682470x8004D009The transaction manager doesn't support an asynchronous operation for this method
-21471682460x8004D00AUnable to enlist in the transaction
-21471682450x8004D00BThe requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero
-21471682440x8004D00CThere is no resource presently associated with this enlistment
-21471682430x8004D00DThe transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers
-21471682420x8004D00EThe transaction has already been implicitly or explicitly committed or aborted
-21471682410x8004D00FAn invalid combination of flags was specified
-21471682400x8004D010The resource manager id is not associated with this transaction or the transaction manager
-21471682390x8004D011This method was called in the wrong state
-21471682380x8004D012The indicated unit of work does not match the unit of work expected by the resource manager
-21471682370x8004D013An enlistment in a transaction already exists
-21471682360x8004D014An import object for the transaction could not be found
-21471682350x8004D015The transaction cookie is invalid
-21471682340x8004D016The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed
-21471682330x8004D017A time-out was specified, but time-outs are not supported
-21471682320x8004D018The requested operation is already in progress for the transaction
-21471682310x8004D019The transaction has already been aborted
-21471682300x8004D01AThe Transaction Manager returned a log full error
-21471682290x8004D01BThe Transaction Manager is not available
-21471682280x8004D01CA connection with the transaction manager was lost
-21471682270x8004D01DA request to establish a connection with the transaction manager was denied
-21471682260x8004D01EResource manager reenlistment to determine transaction status timed out
-21471682250x8004D01FThis transaction manager failed to establish a connection with another TIP transaction manager
-21471682240x8004D020This transaction manager encountered a protocol error with another TIP transaction manager
-21471682230x8004D021This transaction manager could not propagate a transaction from another TIP transaction manager
-21471682220x8004D022The Transaction Manager on the destination machine is not available
-21471682210x8004D023The Transaction Manager has disabled its support for TIP
-21471682200x8004D024The transaction manager has disabled its support for remote/network transactions
-21471682190x8004D025The partner transaction manager has disabled its support for remote/network transactions
-21471682180x8004D026The transaction manager has disabled its support for XA transactions
-21471682170x8004D027MSDTC was unable to read its configuration information
-21471682160x8004D028MSDTC was unable to load the dtc proxy dll
-21471682150x8004D029The local transaction has aborted
-21471682140x8004D02AThe MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers
-21471682130x8004D02BThe MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers
-21471682120x8004D02CThe MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions
-21471681280x8004D080XACT_E_CLERKNOTFOUND
-21471681270x8004D081XACT_E_CLERKEXISTS
-21471681260x8004D082XACT_E_RECOVERYINPROGRESS
-21471681250x8004D083XACT_E_TRANSACTIONCLOSED
-21471681240x8004D084XACT_E_INVALIDLSN
-21471681230x8004D085XACT_E_REPLAYREQUEST
-21471680000x8004D100The request to connect to the specified transaction coordinator was denied
-21471679990x8004D101The maximum number of enlistments for the specified transaction has been reached
-21471679980x8004D102A resource manager with the same identifier is already registered with the specified transaction coordinator
-21471679970x8004D103The prepare request given was not eligible for single phase optimizations
-21471679960x8004D104RecoveryComplete has already been called for the given resource manager
-21471679950x8004D105The interface call made was incorrect for the current state of the protocol
-21471679940x8004D106xa_open call failed for the XA resource
-21471679930x8004D107xa_recover call failed for the XA resource
-21471679920x8004D108The Logical Unit of Work specified cannot be found
-21471679910x8004D109The specified Logical Unit of Work already exists
-21471679900x8004D10ASubordinate creation failed. The specified Logical Unit of Work was not connected
-21471679890x8004D10BA transaction with the given identifier already exists
-21471679880x8004D10CThe resource is in use
-21471679870x8004D10DThe LU Recovery process is down
-21471679860x8004D10EThe remote session was lost
-21471679850x8004D10FThe resource is currently recovering
-21471679840x8004D110There was a mismatch in driving recovery
-21471679830x8004D111An error occurred with the XA resource
-21471641580x8004E002The root transaction wanted to commit, but transaction aborted
-21471641570x8004E003You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting
-21471641560x8004E004There is no MTS object context
-21471641550x8004E005The component is configured to use synchronization and this method call would cause a deadlock to occur
-21471641540x8004E006The component is configured to use synchronization and a thread has timed out waiting to enter the context
-21471641530x8004E007You made a method call on a COM+ component that has a transaction that has already committed or aborted
-21471641480x8004E00CThe specified role was not configured for the application
-21471641450x8004E00FCOM+ was unable to talk to the Microsoft Distributed Transaction Coordinator
-21471641270x8004E021An unexpected error occurred during COM+ Activation
-21471641260x8004E022COM+ Activation failed. Check the event log for more information
-21471641250x8004E023COM+ Activation failed due to a catalog or configuration error
-21471641240x8004E024COM+ activation failed because the activation could not be completed in the specified amount of time
-21471641230x8004E025COM+ Activation failed because an initialization function failed. Check the event log for more information
-21471641220x8004E026The requested operation requires that JIT be in the current context and it is not
-21471641210x8004E027The requested operation requires that the current context have a Transaction, and it does not
-21471641200x8004E028The components threading model has changed after install into a COM+ Application. Please re-install component
-21471641190x8004E029IIS intrinsics not available. Start your work with IIS
-21471641180x8004E02AAn attempt to write a cookie failed
-21471641170x8004E02BAn attempt to use a database generated a database specific error
-21471641160x8004E02CThe COM+ component you created must use object pooling to work
-21471641150x8004E02DThe COM+ component you created must use object construction to work correctly
-21471641140x8004E02EThe COM+ component requires synchronization, and it is not configured for it
-21471641130x8004E02FThe TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the root"" component for the transaction. The creation failed""
-21471641120x8004E030The 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
-21471641110x8004E031The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning
-21470248960x80070000The operation completed successfully
-21470248950x80070001Incorrect function
-21470248940x80070002The system cannot find the file specified
-21470248930x80070003The system cannot find the path specified
-21470248920x80070004The system cannot open the file
-21470248910x80070005Access is denied
-21470248900x80070006The handle is invalid
-21470248890x80070007The storage control blocks were destroyed
-21470248880x80070008Not enough storage is available to process this command
-21470248870x80070009The storage control block address is invalid
-21470248860x8007000AThe environment is incorrect
-21470248850x8007000BAn attempt was made to load a program with an incorrect format
-21470248840x8007000CThe access code is invalid
-21470248830x8007000DThe data is invalid
-21470248820x8007000ENot enough storage is available to complete this operation
-21470248810x8007000FThe system cannot find the drive specified
-21470248800x80070010The directory cannot be removed
-21470248790x80070011The system cannot move the file to a different disk drive
-21470248780x80070012There are no more files
-21470248770x80070013The media is write protected
-21470248760x80070014The system cannot find the device specified
-21470248750x80070015The device is not ready
-21470248740x80070016The device does not recognize the command
-21470248730x80070017Data error (cyclic redundancy check)
-21470248720x80070018The program issued a command but the command length is incorrect
-21470248710x80070019The drive cannot locate a specific area or track on the disk
-21470248700x8007001AThe specified disk or diskette cannot be accessed
-21470248690x8007001BThe drive cannot find the sector requested
-21470248680x8007001CThe printer is out of paper
-21470248670x8007001DThe system cannot write to the specified device
-21470248660x8007001EThe system cannot read from the specified device
-21470248650x8007001FA device attached to the system is not functioning
-21470248640x80070020The process cannot access the file because it is being used by another process
-21470248630x80070021The process cannot access the file because another process has locked a portion of the file
-21470248620x80070022The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1
-21470248600x80070024Too many files opened for sharing
-21470248580x80070026Reached the end of the file
-21470248570x80070027The disk is full
-21470248460x80070032The request is not supported
-21470248450x80070033Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator
-21470248440x80070034You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name
-21470248430x80070035The network path was not found
-21470248420x80070036The network is busy
-21470248410x80070037The specified network resource or device is no longer available
-21470248400x80070038The network BIOS command limit has been reached
-21470248390x80070039A network adapter hardware error occurred
-21470248380x8007003AThe specified server cannot perform the requested operation
-21470248370x8007003BAn unexpected network error occurred
-21470248360x8007003CThe remote adapter is not compatible
-21470248350x8007003DThe printer queue is full
-21470248340x8007003ESpace to store the file waiting to be printed is not available on the server
-21470248330x8007003FYour file waiting to be printed was deleted
-21470248320x80070040The specified network name is no longer available
-21470248310x80070041Network access is denied
-21470248300x80070042The network resource type is not correct
-21470248290x80070043The network name cannot be found
-21470248280x80070044The name limit for the local computer network adapter card was exceeded
-21470248270x80070045The network BIOS session limit was exceeded
-21470248260x80070046The remote server has been paused or is in the process of being started
-21470248250x80070047No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept
-21470248240x80070048The specified printer or disk device has been paused
-21470248160x80070050The file exists
-21470248140x80070052The directory or file cannot be created
-21470248130x80070053Fail on INT 24
-21470248120x80070054Storage to process this request is not available
-21470248110x80070055The local device name is already in use
-21470248100x80070056The specified network password is not correct
-21470248090x80070057The parameter is incorrect
-21470248080x80070058A write fault occurred on the network
-21470248070x80070059The system cannot start another process at this time
-21470247960x80070064Cannot create another system semaphore
-21470247950x80070065The exclusive semaphore is owned by another process
-21470247940x80070066The semaphore is set and cannot be closed
-21470247930x80070067The semaphore cannot be set again
-21470247920x80070068Cannot request exclusive semaphores at interrupt time
-21470247910x80070069The previous ownership of this semaphore has ended
-21470247900x8007006AInsert the diskette for drive %1
-21470247890x8007006BThe program stopped because an alternate diskette was not inserted
-21470247880x8007006CThe disk is in use or locked by another process
-21470247870x8007006DThe pipe has been ended
-21470247860x8007006EThe system cannot open the device or file specified
-21470247850x8007006FThe file name is too long
-21470247840x80070070There is not enough space on the disk
-21470247830x80070071No more internal file identifiers available
-21470247820x80070072The target internal file identifier is incorrect
-21470247790x80070075The IOCTL call made by the application program is not correct
-21470247780x80070076The verify-on-write switch parameter value is not correct
-21470247770x80070077The system does not support the command requested
-21470247760x80070078This function is not supported on this system
-21470247750x80070079The semaphore timeout period has expired
-21470247740x8007007AThe data area passed to a system call is too small
-21470247730x8007007BThe filename, directory name, or volume label syntax is incorrect
-21470247720x8007007CThe system call level is not correct
-21470247710x8007007DThe disk has no volume label
-21470247700x8007007EThe specified module could not be found
-21470247690x8007007FThe specified procedure could not be found
-21470247680x80070080There are no child processes to wait for
-21470247670x80070081The %1 application cannot be run in Win32 mode
-21470247660x80070082Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O
-21470247650x80070083An attempt was made to move the file pointer before the beginning of the file
-21470247640x80070084The file pointer cannot be set on the specified device or file
-21470247630x80070085A JOIN or SUBST command cannot be used for a drive that contains previously joined drives
-21470247620x80070086An attempt was made to use a JOIN or SUBST command on a drive that has already been joined
-21470247610x80070087An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted
-21470247600x80070088The system tried to delete the JOIN of a drive that is not joined
-21470247590x80070089The system tried to delete the substitution of a drive that is not substituted
-21470247580x8007008AThe system tried to join a drive to a directory on a joined drive
-21470247570x8007008BThe system tried to substitute a drive to a directory on a substituted drive
-21470247560x8007008CThe system tried to join a drive to a directory on a substituted drive
-21470247550x8007008DThe system tried to SUBST a drive to a directory on a joined drive
-21470247540x8007008EThe system cannot perform a JOIN or SUBST at this time
-21470247530x8007008FThe system cannot join or substitute a drive to or for a directory on the same drive
-21470247520x80070090The directory is not a subdirectory of the root directory
-21470247510x80070091The directory is not empty
-21470247500x80070092The path specified is being used in a substitute
-21470247490x80070093Not enough resources are available to process this command
-21470247480x80070094The path specified cannot be used at this time
-21470247470x80070095An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute
-21470247460x80070096System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed
-21470247450x80070097The number of specified semaphore events for DosMuxSemWait is not correct
-21470247440x80070098DosMuxSemWait did not execute; too many semaphores are already set
-21470247430x80070099The DosMuxSemWait list is not correct
-21470247420x8007009AThe volume label you entered exceeds the label character limit of the target file system
-21470247410x8007009BCannot create another thread
-21470247400x8007009CThe recipient process has refused the signal
-21470247390x8007009DThe segment is already discarded and cannot be locked
-21470247380x8007009EThe segment is already unlocked
-21470247370x8007009FThe address for the thread ID is not correct
-21470247360x800700A0One or more arguments are not correct
-21470247350x800700A1The specified path is invalid
-21470247340x800700A2A signal is already pending
-21470247320x800700A4No more threads can be created in the system
-21470247290x800700A7Unable to lock a region of a file
-21470247260x800700AAThe requested resource is in use
-21470247250x800700ABDevice's command support detection is in progress
-21470247230x800700ADA lock request was not outstanding for the supplied cancel region
-21470247220x800700AEThe file system does not support atomic changes to the lock type
-21470247160x800700B4The system detected a segment number that was not correct
-21470247140x800700B6The operating system cannot run %1
-21470247130x800700B7Cannot create a file when that file already exists
-21470247100x800700BAThe flag passed is not correct
-21470247090x800700BBThe specified system semaphore name was not found
-21470247080x800700BCThe operating system cannot run %1
-21470247070x800700BDThe operating system cannot run %1
-21470247060x800700BEThe operating system cannot run %1
-21470247050x800700BFCannot run %1 in Win32 mode
-21470247040x800700C0The operating system cannot run %1
-21470247030x800700C1%1 is not a valid Win32 application
-21470247020x800700C2The operating system cannot run %1
-21470247010x800700C3The operating system cannot run %1
-21470247000x800700C4The operating system cannot run this application program
-21470246990x800700C5The operating system is not presently configured to run this application
-21470246980x800700C6The operating system cannot run %1
-21470246970x800700C7The operating system cannot run this application program
-21470246960x800700C8The code segment cannot be greater than or equal to 64K
-21470246950x800700C9The operating system cannot run %1
-21470246940x800700CAThe operating system cannot run %1
-21470246930x800700CBThe system could not find the environment option that was entered
-21470246910x800700CDNo process in the command subtree has a signal handler
-21470246900x800700CEThe filename or extension is too long
-21470246890x800700CFThe ring 2 stack is in use
-21470246880x800700D0The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified
-21470246870x800700D1The signal being posted is not correct
-21470246860x800700D2The signal handler cannot be set
-21470246840x800700D4The segment is locked and cannot be reallocated
-21470246820x800700D6Too many dynamic-link modules are attached to this program or dynamic-link module
-21470246810x800700D7Cannot nest calls to LoadModule
-21470246800x800700D8This 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
-21470246790x800700D9The image file %1 is signed, unable to modify
-21470246780x800700DAThe image file %1 is strong signed, unable to modify
-21470246760x800700DCThis file is checked out or locked for editing by another user
-21470246750x800700DDThe file must be checked out before saving changes
-21470246740x800700DEThe file type being saved or retrieved has been blocked
-21470246730x800700DFThe file size exceeds the limit allowed and cannot be saved
-21470246720x800700E0Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically
-21470246710x800700E1Operation did not complete successfully because the file contains a virus or potentially unwanted software
-21470246700x800700E2This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location
-21470246670x800700E5The pipe is local
-21470246660x800700E6The pipe state is invalid
-21470246650x800700E7All pipe instances are busy
-21470246640x800700E8The pipe is being closed
-21470246630x800700E9No process is on the other end of the pipe
-21470246620x800700EAMore data is available
-21470246560x800700F0The session was canceled
-21470246420x800700FEThe specified extended attribute name was invalid
-21470246410x800700FFThe extended attributes are inconsistent
-21470246380x80070102The wait operation timed out
-21470246370x80070103No more data is available
-21470246300x8007010AThe copy functions cannot be used
-21470246290x8007010BThe directory name is invalid
-21470246210x80070113The extended attributes did not fit in the buffer
-21470246200x80070114The extended attribute file on the mounted file system is corrupt
-21470246190x80070115The extended attribute table file is full
-21470246180x80070116The specified extended attribute handle is invalid
-21470246140x8007011AThe mounted file system does not support extended attributes
-21470246080x80070120Attempt to release mutex not owned by caller
-21470245980x8007012AToo many posts were made to a semaphore
-21470245970x8007012BOnly part of a ReadProcessMemory or WriteProcessMemory request was completed
-21470245960x8007012CThe oplock request is denied
-21470245950x8007012DAn invalid oplock acknowledgment was received by the system
-21470245940x8007012EThe volume is too fragmented to complete this operation
-21470245930x8007012FThe file cannot be opened because it is in the process of being deleted
-21470245920x80070130Short name settings may not be changed on this volume due to the global registry setting
-21470245910x80070131Short names are not enabled on this volume
-21470245900x80070132The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume
-21470245890x80070133A requested file lock operation cannot be processed due to an invalid byte range
-21470245880x80070134The subsystem needed to support the image type is not present
-21470245870x80070135The specified file already has a notification GUID associated with it
-21470245860x80070136An invalid exception handler routine has been detected
-21470245850x80070137Duplicate privileges were specified for the token
-21470245840x80070138No ranges for the specified operation were able to be processed
-21470245830x80070139Operation is not allowed on a file system internal file
-21470245820x8007013AThe physical resources of this disk have been exhausted
-21470245810x8007013BThe token representing the data is invalid
-21470245800x8007013CThe device does not support the command feature
-21470245790x8007013DThe system cannot find message text for message number 0x%1 in the message file for %2
-21470245780x8007013EThe scope specified was not found
-21470245770x8007013FThe Central Access Policy specified is not defined on the target machine
-21470245760x80070140The Central Access Policy obtained from Active Directory is invalid
-21470245750x80070141The device is unreachable
-21470245740x80070142The target device has insufficient resources to complete the operation
-21470245730x80070143A data integrity checksum error occurred. Data in the file stream is corrupt
-21470245720x80070144An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation
-21470245700x80070146Device does not support file-level TRIM
-21470245690x80070147The command specified a data offset that does not align to the device's granularity/alignment
-21470245680x80070148The command specified an invalid field in its parameter list
-21470245670x80070149An operation is currently in progress with the device
-21470245660x8007014AAn attempt was made to send down the command via an invalid path to the target device
-21470245650x8007014BThe command specified a number of descriptors that exceeded the maximum supported by the device
-21470245640x8007014CScrub is disabled on the specified file
-21470245630x8007014DThe storage device does not provide redundancy
-21470245620x8007014EAn operation is not supported on a resident file
-21470245610x8007014FAn operation is not supported on a compressed file
-21470245600x80070150An operation is not supported on a directory
-21470245590x80070151The specified copy of the requested data could not be read
-21470245580x80070152The specified data could not be written to any of the copies
-21470245570x80070153One 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
-21470245560x80070154The supplied kernel information version is invalid
-21470245550x80070155The supplied PEP information version is invalid
-21470245540x80070156This object is not externally backed by any provider
-21470245530x80070157The external backing provider is not recognized
-21470245520x80070158Compressing this object would not save space
-21470245510x80070159The request failed due to a storage topology ID mismatch
-21470245500x8007015AThe operation was blocked by parental controls
-21470245490x8007015BA file system block being referenced has already reached the maximum reference count and can't be referenced any further
-21470245460x8007015ENo action was taken as a system reboot is required
-21470245450x8007015FThe shutdown operation failed
-21470245440x80070160The restart operation failed
-21470245430x80070161The maximum number of sessions has been reached
-21470244960x80070190The thread is already in background processing mode
-21470244950x80070191The thread is not in background processing mode
-21470244940x80070192The process is already in background processing mode
-21470244930x80070193The process is not in background processing mode
-21470244130x800701E3The request failed due to a fatal device hardware error
-21470244090x800701E7Attempt to access invalid address
-21470243960x800701F4User profile cannot be loaded
-21470243620x80070216Arithmetic result exceeded 32 bits
-21470243610x80070217There is a process on other end of the pipe
-21470243600x80070218Waiting for a process to open the other end of the pipe
-21470243590x80070219Application verifier has found an error in the current process
-21470243580x8007021AAn error occurred in the ABIOS subsystem
-21470243570x8007021BA warning occurred in the WX86 subsystem
-21470243560x8007021CAn error occurred in the WX86 subsystem
-21470243550x8007021DAn 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
-21470243540x8007021EUnwind exception code
-21470243530x8007021FAn invalid or unaligned stack was encountered during an unwind operation
-21470243520x80070220An invalid unwind target was encountered during an unwind operation
-21470243510x80070221Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
-21470243500x80070222Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port
-21470243490x80070223An attempt was made to lower a quota limit below the current usage
-21470243480x80070224An attempt was made to attach to a device that was already attached to another device
-21470243470x80070225An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references
-21470243460x80070226Profiling not started
-21470243450x80070227Profiling not stopped
-21470243440x80070228The passed ACL did not contain the minimum required information
-21470243430x80070229The number of active profiling objects is at the maximum and no more may be started
-21470243420x8007022AUsed to indicate that an operation cannot continue without blocking for I/O
-21470243410x8007022BIndicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process
-21470243400x8007022CIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
-21470243390x8007022DIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
-21470243380x8007022EIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
-21470243370x8007022FA malformed function table was encountered during an unwind operation
-21470243360x80070230Indicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system. This causes the protection attempt to fail, which may cause a file creation attempt to fail
-21470243350x80070231Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors
-21470243330x80070233Indicates that the starting value for the LDT information was not an integral multiple of the selector size
-21470243320x80070234Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors
-21470243310x80070235Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads
-21470243300x80070236An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified
-21470243290x80070237Page file quota was exceeded
-21470243280x80070238The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role
-21470243270x80070239The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required
-21470243260x8007023AThe NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines
-21470243250x8007023B{Privilege Failed} The I/O permissions for the process could not be changed
-21470243240x8007023C{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C
-21470243230x8007023D{Missing System File} The required system file %hs is bad or missing
-21470243220x8007023E{Application Error} The exception %s (0x
-21470243210x8007023F{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application
-21470243200x80070240{Unable to Create Paging File} The creation of the paging file %hs failed (%lx). The requested size was %ld
-21470243190x80070241Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source
-21470243180x80070242{No Paging File Specified} No paging file was specified in the system configuration
-21470243170x80070243{EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present
-21470243160x80070244An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread
-21470243150x80070245A Windows Server has an incorrect configuration
-21470243140x80070246An 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
-21470243130x80070247The Unicode character is not defined in the Unicode character set installed on the system
-21470243120x80070248The paging file cannot be created on a floppy diskette
-21470243110x80070249The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected
-21470243100x8007024AThis operation is only allowed for the Primary Domain Controller of the domain
-21470243090x8007024BAn attempt was made to acquire a mutant such that its maximum count would have been exceeded
-21470243080x8007024CA volume has been accessed for which a file system driver is required that has not yet been loaded
-21470243070x8007024D{Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable
-21470243060x8007024E{Unexpected Failure in DebugActiveProcess} An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error
-21470243050x8007024F{Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x
-21470243040x80070250{Data Not Accepted} The TDI client could not handle the data received during an indication
-21470243030x80070251NTVDM encountered a hard error
-21470243020x80070252{Cancel Timeout} The driver %hs failed to complete a cancelled I/O request in the allotted time
-21470243010x80070253{Reply Message Mismatch} An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message
-21470243000x80070254{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
-21470242990x80070255The 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
-21470242980x80070256The stream is not a tiny stream
-21470242970x80070257The request must be handled by the stack overflow code
-21470242960x80070258Internal 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
-21470242950x80070259The 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
-21470242940x8007025AThe bucket array must be grown. Retry transaction after doing so
-21470242930x8007025BThe user/kernel marshalling buffer has overflowed
-21470242920x8007025CThe supplied variant structure contains invalid data
-21470242910x8007025DThe specified buffer contains ill-formed data
-21470242900x8007025E{Audit Failed} An attempt to generate a security audit failed
-21470242890x8007025FThe timer resolution was not previously set by the current process
-21470242880x80070260There is insufficient account information to log you on
-21470242870x80070261{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
-21470242860x80070262{Invalid Service Callback Entrypoint} The %hs service is not written correctly. The stack pointer has been left in an inconsistent state. The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly
-21470242850x80070263There is an IP address conflict with another system on the network
-21470242840x80070264There is an IP address conflict with another system on the network
-21470242830x80070265{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
-21470242820x80070266A callback return system service cannot be executed when no callback is active
-21470242810x80070267The password provided is too short to meet the policy of your user account. Please choose a longer password
-21470242800x80070268The policy of your user account does not allow you to change passwords too frequently. This is done to prevent users from changing back to a familiar, but potentially discovered, password. If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned
-21470242790x80070269You 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
-21470242780x8007026AThe specified compression format is unsupported
-21470242770x8007026BThe specified hardware profile configuration is invalid
-21470242760x8007026CThe specified Plug and Play registry device path is invalid
-21470242750x8007026DThe specified quota list is internally inconsistent with its descriptor
-21470242740x8007026E{Windows Evaluation Notification} The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product
-21470242730x8007026F{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
-21470242720x80070270{DLL Initialization Failed} The application failed to initialize because the window station is shutting down
-21470242710x80070271The validation process needs to continue on to the next step
-21470242700x80070272There are no more matches for the current index enumeration
-21470242690x80070273The range could not be added to the range list because of a conflict
-21470242680x80070274The server process is running under a SID different than that required by client
-21470242670x80070275A group marked use for deny only cannot be enabled
-21470242660x80070276{EXCEPTION} Multiple floating point faults
-21470242650x80070277{EXCEPTION} Multiple floating point traps
-21470242640x80070278The requested interface is not supported
-21470242630x80070279{System Standby Failed} The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode
-21470242620x8007027AThe system file %1 has become corrupt and has been replaced
-21470242610x8007027B{Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help
-21470242600x8007027CA device was removed so enumeration must be restarted
-21470242590x8007027D{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
-21470242580x8007027EDevice will not start without a reboot
-21470242570x8007027FThere is not enough power to complete the requested operation
-21470242560x80070280ERROR_MULTIPLE_FAULT_VIOLATION
-21470242550x80070281The system is in the process of shutting down
-21470242540x80070282An attempt to remove a processes DebugPort was made, but a port was not already associated with the process
-21470242530x80070283This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller
-21470242520x80070284The specified range could not be found in the range list
-21470242500x80070286The driver was not loaded because the system is booting into safe mode
-21470242490x80070287The driver was not loaded because it failed its initialization call
-21470242480x80070288The %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""
-21470242470x80070289The 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
-21470242460x8007028AThe device object parameter is either not a valid device object or is not attached to the volume specified by the file name
-21470242450x8007028BA Machine Check Error has occurred. Please check the system eventlog for additional information
-21470242440x8007028CThere was error [%2] processing the driver database
-21470242430x8007028DSystem hive size has exceeded its limit
-21470242420x8007028EThe driver could not be loaded because a previous version of the driver is still in memory
-21470242410x8007028F{Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation
-21470242400x80070290The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted
-21470242390x80070291The password provided is too long to meet the policy of your user account. Please choose a shorter password
-21470242310x80070299The requested operation could not be completed due to a file system limitation
-21470242280x8007029CAn assertion failure has occurred
-21470242270x8007029DAn error occurred in the ACPI subsystem
-21470242260x8007029EWOW Assertion Error
-21470242250x8007029FA device is missing in the system BIOS MPS table. This device will not be used. Please contact your system vendor for system BIOS update
-21470242240x800702A0A translator failed to translate resources
-21470242230x800702A1A IRQ translator failed to translate resources
-21470242220x800702A2Driver %2 returned invalid ID for a child device (%3)
-21470242210x800702A3{Kernel Debugger Awakened} the system debugger was awakened by an interrupt
-21470242200x800702A4{Handles Closed} Handles to objects have been automatically closed as a result of the requested operation
-21470242190x800702A5{Too Much Information} The specified access control list (ACL) contained more information than was expected
-21470242180x800702A6This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired)
-21470242170x800702A7{Media Changed} The media may have changed
-21470242160x800702A8{GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended
-21470242150x800702A9The create operation stopped after reaching a symbolic link
-21470242140x800702AAA long jump has been executed
-21470242130x800702ABThe Plug and Play query operation was not successful
-21470242120x800702ACA frame consolidation has been executed
-21470242110x800702AD{Registry Hive Recovered} Registry hive (file): %hs was corrupted and it has been recovered. Some data might have been lost
-21470242100x800702AEThe application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?
-21470242090x800702AFThe application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?
-21470242080x800702B0Debugger did not handle the exception
-21470242070x800702B1Debugger will reply later
-21470242060x800702B2Debugger cannot provide handle
-21470242050x800702B3Debugger terminated thread
-21470242040x800702B4Debugger terminated process
-21470242030x800702B5Debugger got control C
-21470242020x800702B6Debugger printed exception on control C
-21470242010x800702B7Debugger received RIP exception
-21470242000x800702B8Debugger received control break
-21470241990x800702B9Debugger command communication exception
-21470241980x800702BA{Object Exists} An attempt was made to create an object and the object name already existed
-21470241970x800702BB{Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded
-21470241960x800702BC{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
-21470241950x800702BDThis informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created
-21470241940x800702BE{Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments
-21470241930x800702BF{Invalid Current Directory} The process cannot switch to the startup current directory %hs. Select OK to set current directory to %hs, or select CANCEL to exit
-21470241920x800702C0{Redundant Read} To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device
-21470241910x800702C1{Redundant Write} To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device
-21470241900x800702C2{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load
-21470241890x800702C3{Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later
-21470241880x800702C4{Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system
-21470241870x800702C5{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
-21470241860x800702C6{TDI Event Done} The TDI indication has completed successfully
-21470241850x800702C7{TDI Event Pending} The TDI indication has entered the pending state
-21470241840x800702C8Checking file system on %wZ
-21470241830x800702C9{Fatal Application Exit} %hs
-21470241820x800702CAThe specified registry key is referenced by a predefined handle
-21470241810x800702CB{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
-21470241800x800702CC%hs
-21470241790x800702CD{Page Locked} One of the pages to lock was already locked
-21470241780x800702CEApplication popup: %1 : %2
-21470241770x800702CFERROR_ALREADY_WIN32
-21470241760x800702D0{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine
-21470241750x800702D1A yield execution was performed and no thread was available to run
-21470241740x800702D2The resumable flag to a timer API was ignored
-21470241730x800702D3The arbiter has deferred arbitration of these resources to its parent
-21470241720x800702D4The inserted CardBus device cannot be started because of a configuration error on %hs""""
-21470241710x800702D5The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported
-21470241700x800702D6The system was put into hibernation
-21470241690x800702D7The system was resumed from hibernation
-21470241680x800702D8Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]
-21470241670x800702D9A 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
-21470241660x800702DAThe system has awoken
-21470241650x800702DBERROR_WAIT_1
-21470241640x800702DCERROR_WAIT_2
-21470241630x800702DDERROR_WAIT_3
-21470241620x800702DEERROR_WAIT_63
-21470241610x800702DFERROR_ABANDONED_WAIT_0
-21470241600x800702E0ERROR_ABANDONED_WAIT_63
-21470241590x800702E1ERROR_USER_APC
-21470241580x800702E2ERROR_KERNEL_APC
-21470241570x800702E3ERROR_ALERTED
-21470241560x800702E4The requested operation requires elevation
-21470241550x800702E5A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
-21470241540x800702E6An open/create operation completed while an oplock break is underway
-21470241530x800702E7A new volume has been mounted by a file system
-21470241520x800702E8This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed
-21470241510x800702E9This indicates that a notify change request has been completed due to closing the handle which made the notify change request
-21470241500x800702EA{Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport
-21470241490x800702EBPage fault was a transition fault
-21470241480x800702ECPage fault was a demand zero fault
-21470241470x800702EDPage fault was a demand zero fault
-21470241460x800702EEPage fault was a demand zero fault
-21470241450x800702EFPage fault was satisfied by reading from a secondary storage device
-21470241440x800702F0Cached page was locked during operation
-21470241430x800702F1Crash dump exists in paging file
-21470241420x800702F2Specified buffer contains all zeros
-21470241410x800702F3A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
-21470241400x800702F4The device has succeeded a query-stop and its resource requirements have changed
-21470241390x800702F5The translator has translated these resources into the global space and no further translations should be performed
-21470241380x800702F6A process being terminated has no threads to terminate
-21470241370x800702F7The specified process is not part of a job
-21470241360x800702F8The specified process is part of a job
-21470241350x800702F9{Volume Shadow Copy Service} The system is now ready for hibernation
-21470241340x800702FAA file system or file system filter driver has successfully completed an FsFilter operation
-21470241330x800702FBThe specified interrupt vector was already connected
-21470241320x800702FCThe specified interrupt vector is still connected
-21470241310x800702FDAn operation is blocked waiting for an oplock
-21470241300x800702FEDebugger handled exception
-21470241290x800702FFDebugger continued
-21470241280x80070300An exception occurred in a user mode callback and the kernel callback frame should be removed
-21470241270x80070301Compression is disabled for this volume
-21470241260x80070302The data provider cannot fetch backwards through a result set
-21470241250x80070303The data provider cannot scroll backwards through a result set
-21470241240x80070304The data provider requires that previously fetched data is released before asking for more data
-21470241230x80070305The data provider was not able to interpret the flags set for a column binding in an accessor
-21470241220x80070306One or more errors occurred while processing the request
-21470241210x80070307The implementation is not capable of performing the request
-21470241200x80070308The client of a component requested an operation which is not valid given the state of the component instance
-21470241190x80070309A version number could not be parsed
-21470241180x8007030AThe iterator's start position is invalid
-21470241170x8007030BThe hardware has reported an uncorrectable memory error
-21470241160x8007030CThe attempted operation required self healing to be enabled
-21470241150x8007030DThe Desktop heap encountered an error while allocating session memory. There is more information in the system event log
-21470241140x8007030EThe system power state is transitioning from %2 to %3
-21470241130x8007030FThe system power state is transitioning from %2 to %3 but could enter %4
-21470241120x80070310A thread is getting dispatched with MCA EXCEPTION because of MCA
-21470241110x80070311Access to %1 is monitored by policy rule %2
-21470241100x80070312Access to %1 has been restricted by your Administrator by policy rule %2
-21470241090x80070313A valid hibernation file has been invalidated and should be abandoned
-21470241080x80070314{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
-21470241070x80070315{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
-21470241060x80070316{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
-21470241050x80070317The resources required for this device conflict with the MCFG table
-21470241040x80070318The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired
-21470241030x80070319The volume repair was not successful
-21470241020x8007031AOne of the volume corruption logs is full. Further corruptions that may be detected won't be logged
-21470241010x8007031BOne of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned
-21470241000x8007031COne of the volume corruption logs is unavailable for being operated on
-21470240990x8007031DOne of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned
-21470240980x8007031EOne of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions
-21470240970x8007031FOrphaned 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
-21470240960x80070320The oplock that was associated with this handle is now associated with a different handle
-21470240950x80070321An oplock of the requested level cannot be granted. An oplock of a lower level may be available
-21470240940x80070322The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken
-21470240930x80070323The handle with which this oplock was associated has been closed. The oplock is now broken
-21470240920x80070324The specified access control entry (ACE) does not contain a condition
-21470240910x80070325The specified access control entry (ACE) contains an invalid condition
-21470240900x80070326Access to the specified file handle has been revoked
-21470240890x80070327{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
-21470240880x80070328The read or write operation to an encrypted file could not be completed because the file has not been opened for data access
-21470240870x80070329File metadata optimization is already in progress
-21470240860x8007032AThe requested operation failed due to quota operation is still in progress
-21470240850x8007032BAccess to the specified handle has been revoked
-21470240840x8007032CThe callback function must be invoked inline
-21470240830x8007032DThe specified CPU Set IDs are invalid
-21470239020x800703E2Access to the extended attribute was denied
-21470239010x800703E3The I/O operation has been aborted because of either a thread exit or an application request
-21470239000x800703E4Overlapped I/O event is not in a signaled state
-21470238990x800703E5Overlapped I/O operation is in progress
-21470238980x800703E6Invalid access to memory location
-21470238970x800703E7Error performing inpage operation
-21470238950x800703E9Recursion too deep; the stack overflowed
-21470238940x800703EAThe window cannot act on the sent message
-21470238930x800703EBCannot complete this function
-21470238920x800703ECInvalid flags
-21470238910x800703EDThe 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
-21470238900x800703EEThe volume for a file has been externally altered so that the opened file is no longer valid
-21470238890x800703EFThe requested operation cannot be performed in full-screen mode
-21470238880x800703F0An attempt was made to reference a token that does not exist
-21470238870x800703F1The configuration registry database is corrupt
-21470238860x800703F2The configuration registry key is invalid
-21470238850x800703F3The configuration registry key could not be opened
-21470238840x800703F4The configuration registry key could not be read
-21470238830x800703F5The configuration registry key could not be written
-21470238820x800703F6One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful
-21470238810x800703F7The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted
-21470238800x800703F8An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry
-21470238790x800703F9The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format
-21470238780x800703FAIllegal operation attempted on a registry key that has been marked for deletion
-21470238770x800703FBSystem could not allocate the required space in a registry log
-21470238760x800703FCCannot create a symbolic link in a registry key that already has subkeys or values
-21470238750x800703FDCannot create a stable subkey under a volatile parent key
-21470238740x800703FEA 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
-21470238450x8007041BA stop control has been sent to a service that other running services are dependent on
-21470238440x8007041CThe requested control is not valid for this service
-21470238430x8007041DThe service did not respond to the start or control request in a timely fashion
-21470238420x8007041EA thread could not be created for the service
-21470238410x8007041FThe service database is locked
-21470238400x80070420An instance of the service is already running
-21470238390x80070421The account name is invalid or does not exist, or the password is invalid for the account name specified
-21470238380x80070422The service cannot be started, either because it is disabled or because it has no enabled devices associated with it
-21470238370x80070423Circular service dependency was specified
-21470238360x80070424The specified service does not exist as an installed service
-21470238350x80070425The service cannot accept control messages at this time
-21470238340x80070426The service has not been started
-21470238330x80070427The service process could not connect to the service controller
-21470238320x80070428An exception occurred in the service when handling the control request
-21470238310x80070429The database specified does not exist
-21470238300x8007042AThe service has returned a service-specific error code
-21470238290x8007042BThe process terminated unexpectedly
-21470238280x8007042CThe dependency service or group failed to start
-21470238270x8007042DThe service did not start due to a logon failure
-21470238260x8007042EAfter starting, the service hung in a start-pending state
-21470238250x8007042FThe specified service database lock is invalid
-21470238240x80070430The specified service has been marked for deletion
-21470238230x80070431The specified service already exists
-21470238220x80070432The system is currently running with the last-known-good configuration
-21470238210x80070433The dependency service does not exist or has been marked for deletion
-21470238200x80070434The current boot has already been accepted for use as the last-known-good control set
-21470238190x80070435No attempts to start the service have been made since the last boot
-21470238180x80070436The name is already in use as either a service name or a service display name
-21470238170x80070437The account specified for this service is different from the account specified for other services running in the same process
-21470238160x80070438Failure actions can only be set for Win32 services, not for drivers
-21470238150x80070439This service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service's process terminates unexpectedly
-21470238140x8007043ANo recovery program has been configured for this service
-21470238130x8007043BThe executable program that this service is configured to run in does not implement the service
-21470238120x8007043CThis service cannot be started in Safe Mode
-21470237960x8007044CThe physical end of the tape has been reached
-21470237950x8007044DA tape access reached a filemark
-21470237940x8007044EThe beginning of the tape or a partition was encountered
-21470237930x8007044FA tape access reached the end of a set of files
-21470237920x80070450No more data is on the tape
-21470237910x80070451Tape could not be partitioned
-21470237900x80070452When accessing a new tape of a multivolume partition, the current block size is incorrect
-21470237890x80070453Tape partition information could not be found when loading a tape
-21470237880x80070454Unable to lock the media eject mechanism
-21470237870x80070455Unable to unload the media
-21470237860x80070456The media in the drive may have changed
-21470237850x80070457The I/O bus was reset
-21470237840x80070458No media in drive
-21470237830x80070459No mapping for the Unicode character exists in the target multi-byte code page
-21470237820x8007045AA dynamic link library (DLL) initialization routine failed
-21470237810x8007045BA system shutdown is in progress
-21470237800x8007045CUnable to abort the system shutdown because no shutdown was in progress
-21470237790x8007045DThe request could not be performed because of an I/O device error
-21470237780x8007045ENo serial device was successfully initialized. The serial driver will unload
-21470237770x8007045FUnable 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
-21470237760x80070460A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
-21470237750x80070461A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
-21470237740x80070462No ID address mark was found on the floppy disk
-21470237730x80070463Mismatch between the floppy disk sector ID field and the floppy disk controller track address
-21470237720x80070464The floppy disk controller reported an error that is not recognized by the floppy disk driver
-21470237710x80070465The floppy disk controller returned inconsistent results in its registers
-21470237700x80070466While accessing the hard disk, a recalibrate operation failed, even after retries
-21470237690x80070467While accessing the hard disk, a disk operation failed even after retries
-21470237680x80070468While accessing the hard disk, a disk controller reset was needed, but even that failed
-21470237670x80070469Physical end of tape encountered
-21470237660x8007046ANot enough server storage is available to process this command
-21470237650x8007046BA potential deadlock condition has been detected
-21470237640x8007046CThe base address or the file offset specified does not have the proper alignment
-21470237560x80070474An attempt to change the system power state was vetoed by another application or driver
-21470237550x80070475The system BIOS failed an attempt to change the system power state
-21470237540x80070476An attempt was made to create more links on a file than the file system supports
-21470237460x8007047EThe specified program requires a newer version of Windows
-21470237450x8007047FThe specified program is not a Windows or MS-DOS program
-21470237440x80070480Cannot start more than one instance of the specified program
-21470237430x80070481The specified program was written for an earlier version of Windows
-21470237420x80070482One of the library files needed to run this application is damaged
-21470237410x80070483No application is associated with the specified file for this operation
-21470237400x80070484An error occurred in sending the command to the application
-21470237390x80070485One of the library files needed to run this application cannot be found
-21470237380x80070486The current process has used all of its system allowance of handles for Window Manager objects
-21470237370x80070487The message can be used only with synchronous operations
-21470237360x80070488The indicated source element has no media
-21470237350x80070489The indicated destination element already contains media
-21470237340x8007048AThe indicated element does not exist
-21470237330x8007048BThe indicated element is part of a magazine that is not present
-21470237320x8007048CThe indicated device requires reinitialization due to hardware errors
-21470237310x8007048DThe device has indicated that cleaning is required before further operations are attempted
-21470237300x8007048EThe device has indicated that its door is open
-21470237290x8007048FThe device is not connected
-21470237280x80070490Element not found
-21470237270x80070491There was no match for the specified key in the index
-21470237260x80070492The property set specified does not exist on the object
-21470237250x80070493The point passed to GetMouseMovePoints is not in the buffer
-21470237240x80070494The tracking (workstation) service is not running
-21470237230x80070495The Volume ID could not be found
-21470237210x80070497Unable to remove the file to be replaced
-21470237200x80070498Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name
-21470237190x80070499Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name
-21470237180x8007049AThe volume change journal is being deleted
-21470237170x8007049BThe volume change journal is not active
-21470237160x8007049CA file was found, but it may not be the correct file
-21470237150x8007049DThe journal entry has been deleted from the journal
-21470237060x800704A6A system shutdown has already been scheduled
-21470237050x800704A7The system shutdown cannot be initiated because there are other users logged on to the computer
-21470236960x800704B0The specified device name is invalid
-21470236950x800704B1The device is not currently connected but it is a remembered connection
-21470236940x800704B2The local device name has a remembered connection to another network resource
-21470236930x800704B3The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator
-21470236920x800704B4The specified network provider name is invalid
-21470236910x800704B5Unable to open the network connection profile
-21470236900x800704B6The network connection profile is corrupted
-21470236890x800704B7Cannot enumerate a noncontainer
-21470236880x800704B8An extended error has occurred
-21470236870x800704B9The format of the specified group name is invalid
-21470236860x800704BAThe format of the specified computer name is invalid
-21470236850x800704BBThe format of the specified event name is invalid
-21470236840x800704BCThe format of the specified domain name is invalid
-21470236830x800704BDThe format of the specified service name is invalid
-21470236820x800704BEThe format of the specified network name is invalid
-21470236810x800704BFThe format of the specified share name is invalid
-21470236800x800704C0The format of the specified password is invalid
-21470236790x800704C1The format of the specified message name is invalid
-21470236780x800704C2The format of the specified message destination is invalid
-21470236770x800704C3Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again
-21470236760x800704C4An attempt was made to establish a session to a network server, but there are already too many sessions established to that server
-21470236750x800704C5The workgroup or domain name is already in use by another computer on the network
-21470236740x800704C6The network is not present or not started
-21470236730x800704C7The operation was canceled by the user
-21470236720x800704C8The requested operation cannot be performed on a file with a user-mapped section open
-21470236710x800704C9The remote computer refused the network connection
-21470236700x800704CAThe network connection was gracefully closed
-21470236690x800704CBThe network transport endpoint already has an address associated with it
-21470236680x800704CCAn address has not yet been associated with the network endpoint
-21470236670x800704CDAn operation was attempted on a nonexistent network connection
-21470236660x800704CEAn invalid operation was attempted on an active network connection
-21470236650x800704CFThe network location cannot be reached. For information about network troubleshooting, see Windows Help
-21470236640x800704D0The network location cannot be reached. For information about network troubleshooting, see Windows Help
-21470236630x800704D1The network location cannot be reached. For information about network troubleshooting, see Windows Help
-21470236620x800704D2No service is operating at the destination network endpoint on the remote system
-21470236610x800704D3The request was aborted
-21470236600x800704D4The network connection was aborted by the local system
-21470236590x800704D5The operation could not be completed. A retry should be performed
-21470236580x800704D6A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached
-21470236570x800704D7Attempting to log in during an unauthorized time of day for this account
-21470236560x800704D8The account is not authorized to log in from this station
-21470236550x800704D9The network address could not be used for the operation requested
-21470236540x800704DAThe service is already registered
-21470236530x800704DBThe specified service does not exist
-21470236520x800704DCThe operation being requested was not performed because the user has not been authenticated
-21470236510x800704DDThe operation being requested was not performed because the user has not logged on to the network. The specified service does not exist
-21470236500x800704DEContinue with work in progress
-21470236490x800704DFAn attempt was made to perform an initialization operation when initialization has already been completed
-21470236480x800704E0No more local devices
-21470236470x800704E1The specified site does not exist
-21470236460x800704E2A domain controller with the specified name already exists
-21470236450x800704E3This operation is supported only when you are connected to the server
-21470236440x800704E4The group policy framework should call the extension even if there are no changes
-21470236430x800704E5The specified user does not have a valid profile
-21470236420x800704E6This operation is not supported on a computer running Windows Server 2003 for Small Business Server
-21470236410x800704E7The server machine is shutting down
-21470236400x800704E8The remote system is not available. For information about network troubleshooting, see Windows Help
-21470236390x800704E9The security identifier provided is not from an account domain
-21470236380x800704EAThe security identifier provided does not have a domain component
-21470236370x800704EBAppHelp dialog canceled thus preventing the application from starting
-21470236360x800704ECThis program is blocked by group policy. For more information, contact your system administrator
-21470236350x800704EDA program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific
-21470236340x800704EEThe share is currently offline or does not exist
-21470236330x800704EFThe Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log
-21470236320x800704F0The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem
-21470236310x800704F1The system cannot contact a domain controller to service the authentication request. Please try again later
-21470236250x800704F7The machine is locked and cannot be shut down without the force option
-21470236230x800704F9An application-defined callback gave invalid data when called
-21470236220x800704FAThe group policy framework should call the extension in the synchronous foreground policy refresh
-21470236210x800704FBThis driver has been blocked from loading
-21470236200x800704FCA dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image
-21470236190x800704FDWindows cannot open this program since it has been disabled
-21470236180x800704FEWindows cannot open this program because the license enforcement system has been tampered with or become corrupted
-21470236170x800704FFA transaction recover failed
-21470236160x80070500The current thread has already been converted to a fiber
-21470236150x80070501The current thread has already been converted from a fiber
-21470236140x80070502The 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
-21470236130x80070503Data present in one of the parameters is more than the function can operate on
-21470236120x80070504An attempt to do an operation on a debug object failed because the object is in the process of being deleted
-21470236110x80070505An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed
-21470236100x80070506%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator
-21470236090x80070507Insufficient information exists to identify the cause of failure
-21470236080x80070508The parameter passed to a C runtime function is incorrect
-21470236070x80070509The operation occurred beyond the valid data length of the file
-21470236060x8007050AThe service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service
-21470236050x8007050BThe process hosting the driver for this device has been terminated
-21470236040x8007050CAn operation attempted to exceed an implementation-defined limit
-21470236030x8007050DEither the target process, or the target thread's containing process, is a protected process
-21470236020x8007050EThe service notification client is lagging too far behind the current state of services in the machine
-21470236010x8007050FThe requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator
-21470236000x80070510The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator
-21470235990x80070511A 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
-21470235980x80070512A thread involved in this operation appears to be unresponsive
-21470235970x80070513Indicates a particular Security ID may not be assigned as the label of an object
-21470235960x80070514Not all privileges or groups referenced are assigned to the caller
-21470235950x80070515Some mapping between account names and security IDs was not done
-21470235940x80070516No system quota limits are specifically set for this account
-21470235930x80070517No encryption key is available. A well-known encryption key was returned
-21470235920x80070518The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string
-21470235910x80070519The revision level is unknown
-21470235900x8007051AIndicates two revision levels are incompatible
-21470235890x8007051BThis security ID may not be assigned as the owner of this object
-21470235880x8007051CThis security ID may not be assigned as the primary group of an object
-21470235870x8007051DAn attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client
-21470235860x8007051EThe group may not be disabled
-21470235850x8007051FThere are currently no logon servers available to service the logon request
-21470235840x80070520A specified logon session does not exist. It may already have been terminated
-21470235830x80070521A specified privilege does not exist
-21470235820x80070522A required privilege is not held by the client
-21470235810x80070523The name provided is not a properly formed account name
-21470235800x80070524The specified account already exists
-21470235790x80070525The specified account does not exist
-21470235780x80070526The specified group already exists
-21470235770x80070527The specified group does not exist
-21470235760x80070528Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member
-21470235750x80070529The specified user account is not a member of the specified group account
-21470235740x8007052AThis operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon
-21470235730x8007052BUnable to update the password. The value provided as the current password is incorrect
-21470235720x8007052CUnable to update the password. The value provided for the new password contains values that are not allowed in passwords
-21470235710x8007052DUnable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain
-21470235700x8007052EThe user name or password is incorrect
-21470235690x8007052FAccount restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced
-21470235680x80070530Your account has time restrictions that keep you from signing in right now
-21470235670x80070531This user isn't allowed to sign in to this computer
-21470235660x80070532The password for this account has expired
-21470235650x80070533This user can't sign in because this account is currently disabled
-21470235640x80070534No mapping between account names and security IDs was done
-21470235630x80070535Too many local user identifiers (LUIDs) were requested at one time
-21470235620x80070536No more local user identifiers (LUIDs) are available
-21470235610x80070537The subauthority part of a security ID is invalid for this particular use
-21470235600x80070538The access control list (ACL) structure is invalid
-21470235590x80070539The security ID structure is invalid
-21470235580x8007053AThe security descriptor structure is invalid
-21470235560x8007053CThe inherited access control list (ACL) or access control entry (ACE) could not be built
-21470235550x8007053DThe server is currently disabled
-21470235540x8007053EThe server is currently enabled
-21470235530x8007053FThe value provided was an invalid value for an identifier authority
-21470235520x80070540No more memory is available for security information updates
-21470235510x80070541The specified attributes are invalid, or incompatible with the attributes for the group as a whole
-21470235500x80070542Either a required impersonation level was not provided, or the provided impersonation level is invalid
-21470235490x80070543Cannot open an anonymous level security token
-21470235480x80070544The validation information class requested was invalid
-21470235470x80070545The type of the token is inappropriate for its attempted use
-21470235460x80070546Unable to perform a security operation on an object that has no associated security
-21470235450x80070547Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied
-21470235440x80070548The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation
-21470235430x80070549The domain was in the wrong state to perform the security operation
-21470235420x8007054AThis operation is only allowed for the Primary Domain Controller of the domain
-21470235410x8007054BThe specified domain either does not exist or could not be contacted
-21470235400x8007054CThe specified domain already exists
-21470235390x8007054DAn attempt was made to exceed the limit on the number of domains per server
-21470235380x8007054EUnable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk
-21470235370x8007054FAn internal error occurred
-21470235360x80070550Generic access types were contained in an access mask which should already be mapped to nongeneric types
-21470235350x80070551A security descriptor is not in the right format (absolute or self-relative)
-21470235340x80070552The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process
-21470235330x80070553Cannot start a new logon session with an ID that is already in use
-21470235320x80070554A specified authentication package is unknown
-21470235310x80070555The logon session is not in a state that is consistent with the requested operation
-21470235300x80070556The logon session ID is already in use
-21470235290x80070557A logon request contained an invalid logon type value
-21470235280x80070558Unable to impersonate using a named pipe until data has been read from that pipe
-21470235270x80070559The transaction state of a registry subtree is incompatible with the requested operation
-21470235260x8007055AAn internal security database corruption has been encountered
-21470235250x8007055BCannot perform this operation on built-in accounts
-21470235240x8007055CCannot perform this operation on this built-in special group
-21470235230x8007055DCannot perform this operation on this built-in special user
-21470235220x8007055EThe user cannot be removed from a group because the group is currently the user's primary group
-21470235210x8007055FThe token is already in use as a primary token
-21470235200x80070560The specified local group does not exist
-21470235190x80070561The specified account name is not a member of the group
-21470235180x80070562The specified account name is already a member of the group
-21470235170x80070563The specified local group already exists
-21470235160x80070564Logon failure: the user has not been granted the requested logon type at this computer
-21470235150x80070565The maximum number of secrets that may be stored in a single system has been exceeded
-21470235140x80070566The length of a secret exceeds the maximum length allowed
-21470235130x80070567The local security authority database contains an internal inconsistency
-21470235120x80070568During a logon attempt, the user's security context accumulated too many security IDs
-21470235110x80070569Logon failure: the user has not been granted the requested logon type at this computer
-21470235100x8007056AA cross-encrypted password is necessary to change a user password
-21470235090x8007056BA member could not be added to or removed from the local group because the member does not exist
-21470235080x8007056CA new member could not be added to a local group because the member has the wrong account type
-21470235070x8007056DToo many security IDs have been specified
-21470235060x8007056EA cross-encrypted password is necessary to change this user password
-21470235050x8007056FIndicates an ACL contains no inheritable components
-21470235040x80070570The file or directory is corrupted and unreadable
-21470235030x80070571The disk structure is corrupted and unreadable
-21470235020x80070572There is no user session key for the specified logon session
-21470235010x80070573The 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
-21470235000x80070574The target account name is incorrect
-21470234990x80070575Mutual Authentication failed. The server's password is out of date at the domain controller
-21470234980x80070576There is a time and/or date difference between the client and server
-21470234970x80070577This operation cannot be performed on the current domain
-21470234960x80070578Invalid window handle
-21470234950x80070579Invalid menu handle
-21470234940x8007057AInvalid cursor handle
-21470234930x8007057BInvalid accelerator table handle
-21470234920x8007057CInvalid hook handle
-21470234910x8007057DInvalid handle to a multiple-window position structure
-21470234900x8007057ECannot create a top-level child window
-21470234890x8007057FCannot find window class
-21470234880x80070580Invalid window; it belongs to other thread
-21470234870x80070581Hot key is already registered
-21470234860x80070582Class already exists
-21470234850x80070583Class does not exist
-21470234840x80070584Class still has open windows
-21470234830x80070585Invalid index
-21470234820x80070586Invalid icon handle
-21470234810x80070587Using private DIALOG window words
-21470234800x80070588The list box identifier was not found
-21470234790x80070589No wildcards were found
-21470234780x8007058AThread does not have a clipboard open
-21470234770x8007058BHot key is not registered
-21470234760x8007058CThe window is not a valid dialog window
-21470234750x8007058DControl ID not found
-21470234740x8007058EInvalid message for a combo box because it does not have an edit control
-21470234730x8007058FThe window is not a combo box
-21470234720x80070590Height must be less than 256
-21470234710x80070591Invalid device context (DC) handle
-21470234700x80070592Invalid hook procedure type
-21470234690x80070593Invalid hook procedure
-21470234680x80070594Cannot set nonlocal hook without a module handle
-21470234670x80070595This hook procedure can only be set globally
-21470234660x80070596The journal hook procedure is already installed
-21470234650x80070597The hook procedure is not installed
-21470234640x80070598Invalid message for single-selection list box
-21470234630x80070599LB_SETCOUNT sent to non-lazy list box
-21470234620x8007059AThis list box does not support tab stops
-21470234610x8007059BCannot destroy object created by another thread
-21470234600x8007059CChild windows cannot have menus
-21470234590x8007059DThe window does not have a system menu
-21470234580x8007059EInvalid message box style
-21470234570x8007059FInvalid system-wide (SPI_*) parameter
-21470234560x800705A0Screen already locked
-21470234550x800705A1All handles to windows in a multiple-window position structure must have the same parent
-21470234540x800705A2The window is not a child window
-21470234530x800705A3Invalid GW_* command
-21470234520x800705A4Invalid thread identifier
-21470234510x800705A5Cannot process a message from a window that is not a multiple document interface (MDI) window
-21470234500x800705A6Popup menu already active
-21470234490x800705A7The window does not have scroll bars
-21470234480x800705A8Scroll bar range cannot be greater than MAXLONG
-21470234470x800705A9Cannot show or remove the window in the way specified
-21470234460x800705AAInsufficient system resources exist to complete the requested service
-21470234450x800705ABInsufficient system resources exist to complete the requested service
-21470234440x800705ACInsufficient system resources exist to complete the requested service
-21470234430x800705ADInsufficient quota to complete the requested service
-21470234420x800705AEInsufficient quota to complete the requested service
-21470234410x800705AFThe paging file is too small for this operation to complete
-21470234400x800705B0A menu item was not found
-21470234390x800705B1Invalid keyboard layout handle
-21470234380x800705B2Hook type not allowed
-21470234370x800705B3This operation requires an interactive window station
-21470234360x800705B4This operation returned because the timeout period expired
-21470234350x800705B5Invalid monitor handle
-21470234340x800705B6Incorrect size argument
-21470234330x800705B7The symbolic link cannot be followed because its type is disabled
-21470234320x800705B8This application does not support the current operation on symbolic links
-21470234310x800705B9Windows was unable to parse the requested XML data
-21470234300x800705BAAn error was encountered while processing an XML digital signature
-21470234290x800705BBThis application must be restarted
-21470234280x800705BCThe caller made the connection request in the wrong routing compartment
-21470234270x800705BDThere was an AuthIP failure when attempting to connect to the remote host
-21470234260x800705BEInsufficient NVRAM resources exist to complete the requested service. A reboot might be required
-21470234250x800705BFUnable to finish the requested operation because the specified process is not a GUI process
-21470233960x800705DCThe event log file is corrupted
-21470233950x800705DDNo event log file could be opened, so the event logging service did not start
-21470233940x800705DEThe event log file is full
-21470233930x800705DFThe event log file has changed between read operations
-21470233920x800705E0The specified Job already has a container assigned to it
-21470233910x800705E1The specified Job does not have a container assigned to it
-21470233460x8007060EThe specified task name is invalid
-21470233450x8007060FThe specified task index is invalid
-21470233440x80070610The specified thread is already joining a task
-21470232950x80070641The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance
-21470232940x80070642User cancelled installation
-21470232930x80070643Fatal error during installation
-21470232920x80070644Installation suspended, incomplete
-21470232910x80070645This action is only valid for products that are currently installed
-21470232900x80070646Feature ID not registered
-21470232890x80070647Component ID not registered
-21470232880x80070648Unknown property
-21470232870x80070649Handle is in an invalid state
-21470232860x8007064AThe configuration data for this product is corrupt. Contact your support personnel
-21470232850x8007064BComponent qualifier not present
-21470232840x8007064CThe installation source for this product is not available. Verify that the source exists and that you can access it
-21470232830x8007064DThis 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
-21470232820x8007064EProduct is uninstalled
-21470232810x8007064FSQL query syntax invalid or unsupported
-21470232800x80070650Record field does not exist
-21470232790x80070651The device has been removed
-21470232780x80070652Another installation is already in progress. Complete that installation before proceeding with this install
-21470232770x80070653This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
-21470232760x80070654This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package
-21470232750x80070655There was an error starting the Windows Installer service user interface. Contact your support personnel
-21470232740x80070656Error opening installation log file. Verify that the specified log file location exists and that you can write to it
-21470232730x80070657The language of this installation package is not supported by your system
-21470232720x80070658Error applying transforms. Verify that the specified transform paths are valid
-21470232710x80070659This installation is forbidden by system policy. Contact your system administrator
-21470232700x8007065AFunction could not be executed
-21470232690x8007065BFunction failed during execution
-21470232680x8007065CInvalid or unknown table specified
-21470232670x8007065DData supplied is of wrong type
-21470232660x8007065EData of this type is not supported
-21470232650x8007065FThe Windows Installer service failed to start. Contact your support personnel
-21470232640x80070660The 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
-21470232630x80070661This installation package is not supported by this processor type. Contact your product vendor
-21470232620x80070662Component not used on this computer
-21470232610x80070663This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package
-21470232600x80070664This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package
-21470232590x80070665This 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
-21470232580x80070666Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel
-21470232570x80070667Invalid command line argument. Consult the Windows Installer SDK for detailed command line help
-21470232560x80070668Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator
-21470232550x80070669The requested operation completed successfully. The system will be restarted so the changes can take effect
-21470232540x8007066AThe upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade
-21470232530x8007066BThe update package is not permitted by software restriction policy
-21470232520x8007066COne or more customizations are not permitted by software restriction policy
-21470232510x8007066DThe Windows Installer does not permit installation from a Remote Desktop Connection
-21470232500x8007066EUninstallation of the update package is not supported
-21470232490x8007066FThe update is not applied to this product
-21470232480x80070670No valid sequence could be found for the set of updates
-21470232470x80070671Update removal was disallowed by policy
-21470232460x80070672The XML update data is invalid
-21470232450x80070673Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update
-21470232440x80070674The 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
-21470232430x80070675A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately
-21470232420x80070676The app that you are trying to run is not supported on this version of Windows
-21470232410x80070677The operation was blocked as the process prohibits dynamic code generation
-21470232400x80070678The objects are not identical
-21470231960x800706A4The string binding is invalid
-21470231950x800706A5The binding handle is not the correct type
-21470231940x800706A6The binding handle is invalid
-21470231930x800706A7The RPC protocol sequence is not supported
-21470231920x800706A8The RPC protocol sequence is invalid
-21470231910x800706A9The string universal unique identifier (UUID) is invalid
-21470231900x800706AAThe endpoint format is invalid
-21470231890x800706ABThe network address is invalid
-21470231880x800706ACNo endpoint was found
-21470231870x800706ADThe timeout value is invalid
-21470231860x800706AEThe object universal unique identifier (UUID) was not found
-21470231850x800706AFThe object universal unique identifier (UUID) has already been registered
-21470231840x800706B0The type universal unique identifier (UUID) has already been registered
-21470231830x800706B1The RPC server is already listening
-21470231820x800706B2No protocol sequences have been registered
-21470231810x800706B3The RPC server is not listening
-21470231800x800706B4The manager type is unknown
-21470231790x800706B5The interface is unknown
-21470231780x800706B6There are no bindings
-21470231770x800706B7There are no protocol sequences
-21470231760x800706B8The endpoint cannot be created
-21470231750x800706B9Not enough resources are available to complete this operation
-21470231740x800706BAThe RPC server is unavailable
-21470231730x800706BBThe RPC server is too busy to complete this operation
-21470231720x800706BCThe network options are invalid
-21470231710x800706BDThere are no remote procedure calls active on this thread
-21470231700x800706BEThe remote procedure call failed
-21470231690x800706BFThe remote procedure call failed and did not execute
-21470231680x800706C0A remote procedure call (RPC) protocol error occurred
-21470231670x800706C1Access to the HTTP proxy is denied
-21470231660x800706C2The transfer syntax is not supported by the RPC server
-21470231640x800706C4The universal unique identifier (UUID) type is not supported
-21470231630x800706C5The tag is invalid
-21470231620x800706C6The array bounds are invalid
-21470231610x800706C7The binding does not contain an entry name
-21470231600x800706C8The name syntax is invalid
-21470231590x800706C9The name syntax is not supported
-21470231570x800706CBNo network address is available to use to construct a universal unique identifier (UUID)
-21470231560x800706CCThe endpoint is a duplicate
-21470231550x800706CDThe authentication type is unknown
-21470231540x800706CEThe maximum number of calls is too small
-21470231530x800706CFThe string is too long
-21470231520x800706D0The RPC protocol sequence was not found
-21470231510x800706D1The procedure number is out of range
-21470231500x800706D2The binding does not contain any authentication information
-21470231490x800706D3The authentication service is unknown
-21470231480x800706D4The authentication level is unknown
-21470231470x800706D5The security context is invalid
-21470231460x800706D6The authorization service is unknown
-21470231450x800706D7The entry is invalid
-21470231440x800706D8The server endpoint cannot perform the operation
-21470231430x800706D9There are no more endpoints available from the endpoint mapper
-21470231420x800706DANo interfaces have been exported
-21470231410x800706DBThe entry name is incomplete
-21470231400x800706DCThe version option is invalid
-21470231390x800706DDThere are no more members
-21470231380x800706DEThere is nothing to unexport
-21470231370x800706DFThe interface was not found
-21470231360x800706E0The entry already exists
-21470231350x800706E1The entry is not found
-21470231340x800706E2The name service is unavailable
-21470231330x800706E3The network address family is invalid
-21470231320x800706E4The requested operation is not supported
-21470231310x800706E5No security context is available to allow impersonation
-21470231300x800706E6An internal error occurred in a remote procedure call (RPC)
-21470231290x800706E7The RPC server attempted an integer division by zero
-21470231280x800706E8An addressing error occurred in the RPC server
-21470231270x800706E9A floating-point operation at the RPC server caused a division by zero
-21470231260x800706EAA floating-point underflow occurred at the RPC server
-21470231250x800706EBA floating-point overflow occurred at the RPC server
-21470231240x800706ECThe list of RPC servers available for the binding of auto handles has been exhausted
-21470231230x800706EDUnable to open the character translation table file
-21470231220x800706EEThe file containing the character translation table has fewer than 512 bytes
-21470231210x800706EFA null context handle was passed from the client to the host during a remote procedure call
-21470231190x800706F1The context handle changed during a remote procedure call
-21470231180x800706F2The binding handles passed to a remote procedure call do not match
-21470231170x800706F3The stub is unable to get the remote procedure call handle
-21470231160x800706F4A null reference pointer was passed to the stub
-21470231150x800706F5The enumeration value is out of range
-21470231140x800706F6The byte count is too small
-21470231130x800706F7The stub received bad data
-21470231120x800706F8The supplied user buffer is not valid for the requested operation
-21470231110x800706F9The disk media is not recognized. It may not be formatted
-21470231100x800706FAThe workstation does not have a trust secret
-21470231090x800706FBThe security database on the server does not have a computer account for this workstation trust relationship
-21470231080x800706FCThe trust relationship between the primary domain and the trusted domain failed
-21470231070x800706FDThe trust relationship between this workstation and the primary domain failed
-21470231060x800706FEThe network logon failed
-21470231050x800706FFA remote procedure call is already in progress for this thread
-21470231040x80070700An attempt was made to logon, but the network logon service was not started
-21470231030x80070701The user's account has expired
-21470231020x80070702The redirector is in use and cannot be unloaded
-21470231010x80070703The specified printer driver is already installed
-21470231000x80070704The specified port is unknown
-21470230990x80070705The printer driver is unknown
-21470230980x80070706The print processor is unknown
-21470230970x80070707The specified separator file is invalid
-21470230960x80070708The specified priority is invalid
-21470230950x80070709The printer name is invalid
-21470230940x8007070AThe printer already exists
-21470230930x8007070BThe printer command is invalid
-21470230920x8007070CThe specified datatype is invalid
-21470230910x8007070DThe environment specified is invalid
-21470230900x8007070EThere are no more bindings
-21470230890x8007070FThe account used is an interdomain trust account. Use your global user account or local user account to access this server
-21470230880x80070710The account used is a computer account. Use your global user account or local user account to access this server
-21470230870x80070711The account used is a server trust account. Use your global user account or local user account to access this server
-21470230860x80070712The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain
-21470230850x80070713The server is in use and cannot be unloaded
-21470230840x80070714The specified image file did not contain a resource section
-21470230830x80070715The specified resource type cannot be found in the image file
-21470230820x80070716The specified resource name cannot be found in the image file
-21470230810x80070717The specified resource language ID cannot be found in the image file
-21470230800x80070718Not enough quota is available to process this command
-21470230790x80070719No interfaces have been registered
-21470230780x8007071AThe remote procedure call was cancelled
-21470230770x8007071BThe binding handle does not contain all required information
-21470230760x8007071CA communications failure occurred during a remote procedure call
-21470230750x8007071DThe requested authentication level is not supported
-21470230740x8007071ENo principal name registered
-21470230730x8007071FThe error specified is not a valid Windows RPC error code
-21470230720x80070720A UUID that is valid only on this computer has been allocated
-21470230710x80070721A security package specific error occurred
-21470230700x80070722Thread is not canceled
-21470230690x80070723Invalid operation on the encoding/decoding handle
-21470230680x80070724Incompatible version of the serializing package
-21470230670x80070725Incompatible version of the RPC stub
-21470230660x80070726The RPC pipe object is invalid or corrupted
-21470230650x80070727An invalid operation was attempted on an RPC pipe object
-21470230640x80070728Unsupported RPC pipe version
-21470230630x80070729HTTP proxy server rejected the connection because the cookie authentication failed
-21470230620x8007072AThe RPC server is suspended, and could not be resumed for this request. The call did not execute
-21470229980x8007076AThe group member was not found
-21470229970x8007076BThe endpoint mapper database entry could not be created
-21470229960x8007076CThe object universal unique identifier (UUID) is the nil UUID
-21470229950x8007076DThe specified time is invalid
-21470229940x8007076EThe specified form name is invalid
-21470229930x8007076FThe specified form size is invalid
-21470229920x80070770The specified printer handle is already being waited on
-21470229910x80070771The specified printer has been deleted
-21470229900x80070772The state of the printer is invalid
-21470229890x80070773The user's password must be changed before signing in
-21470229880x80070774Could not find the domain controller for this domain
-21470229870x80070775The referenced account is currently locked out and may not be logged on to
-21470229860x80070776The object exporter specified was not found
-21470229850x80070777The object specified was not found
-21470229840x80070778The object resolver set specified was not found
-21470229830x80070779Some data remains to be sent in the request buffer
-21470229820x8007077AInvalid asynchronous remote procedure call handle
-21470229810x8007077BInvalid asynchronous RPC call handle for this operation
-21470229800x8007077CThe RPC pipe object has already been closed
-21470229790x8007077DThe RPC call completed before all pipes were processed
-21470229780x8007077ENo more data is available from the RPC pipe
-21470229770x8007077FNo site name is available for this machine
-21470229760x80070780The file cannot be accessed by the system
-21470229750x80070781The name of the file cannot be resolved by the system
-21470229740x80070782The entry is not of the expected type
-21470229730x80070783Not all object UUIDs could be exported to the specified entry
-21470229720x80070784Interface could not be exported to the specified entry
-21470229710x80070785The specified profile entry could not be added
-21470229700x80070786The specified profile element could not be added
-21470229690x80070787The specified profile element could not be removed
-21470229680x80070788The group element could not be added
-21470229670x80070789The group element could not be removed
-21470229660x8007078AThe printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers
-21470229650x8007078BThe context has expired and can no longer be used
-21470229640x8007078CThe current user's delegated trust creation quota has been exceeded
-21470229630x8007078DThe total delegated trust creation quota has been exceeded
-21470229620x8007078EThe current user's delegated trust deletion quota has been exceeded
-21470229610x8007078FThe computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer
-21470229600x80070790Remote connections to the Print Spooler are blocked by a policy set on your machine
-21470229590x80070791Authentication failed because NTLM authentication has been disabled
-21470229580x80070792Logon Failure: EAS policy requires that the user change their password before this operation can be performed
-21470228960x800707D0The pixel format is invalid
-21470228950x800707D1The specified driver is invalid
-21470228940x800707D2The window style or class attribute is invalid for this operation
-21470228930x800707D3The requested metafile operation is not supported
-21470228920x800707D4The requested transformation operation is not supported
-21470228910x800707D5The requested clipping operation is not supported
-21470228860x800707DAThe specified color management module is invalid
-21470228850x800707DBThe specified color profile is invalid
-21470228840x800707DCThe specified tag was not found
-21470228830x800707DDA required tag is not present
-21470228820x800707DEThe specified tag is already present
-21470228810x800707DFThe specified color profile is not associated with the specified device
-21470228800x800707E0The specified color profile was not found
-21470228790x800707E1The specified color space is invalid
-21470228780x800707E2Image Color Management is not enabled
-21470228770x800707E3There was an error while deleting the color transform
-21470228760x800707E4The specified color transform is invalid
-21470228750x800707E5The specified transform does not match the bitmap's color space
-21470228740x800707E6The specified named color index is not present in the profile
-21470228730x800707E7The specified profile is intended for a device of a different type than the specified device
-21470227940x80070836The workstation driver is not installed
-21470227930x80070837The server could not be located
-21470227920x80070838An internal error occurred. The network cannot access a shared memory segment
-21470227910x80070839A network resource shortage occurred
-21470227900x8007083AThis operation is not supported on workstations
-21470227890x8007083BThe device is not connected
-21470227880x8007083CThe network connection was made successfully, but the user had to be prompted for a password other than the one originally specified
-21470227870x8007083DThe network connection was made successfully using default credentials
-21470227820x80070842The Server service is not started
-21470227810x80070843The queue is empty
-21470227800x80070844The device or directory does not exist
-21470227790x80070845The operation is invalid on a redirected resource
-21470227780x80070846The name has already been shared
-21470227770x80070847The server is currently out of the requested resource
-21470227750x80070849Requested addition of items exceeds the maximum allowed
-21470227740x8007084AThe Peer service supports only two simultaneous users
-21470227730x8007084BThe API return buffer is too small
-21470227690x8007084FA remote API error occurred
-21470227650x80070853An error occurred when opening or reading the configuration file
-21470227600x80070858A general network error occurred
-21470227590x80070859The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service
-21470227580x8007085AThe Workstation service has not been started
-21470227570x8007085BThe requested information is not available
-21470227560x8007085CAn internal Windows error occurred
-21470227550x8007085DThe server is not configured for transactions
-21470227540x8007085EThe requested API is not supported on the remote server
-21470227530x8007085FThe event name is invalid
-21470227520x80070860The computer name already exists on the network. Change it and restart the computer
-21470227500x80070862The specified component could not be found in the configuration information
-21470227490x80070863The specified parameter could not be found in the configuration information
-21470227470x80070865A line in the configuration file is too long
-21470227460x80070866The printer does not exist
-21470227450x80070867The print job does not exist
-21470227440x80070868The printer destination cannot be found
-21470227430x80070869The printer destination already exists
-21470227420x8007086AThe printer queue already exists
-21470227410x8007086BNo more printers can be added
-21470227400x8007086CNo more print jobs can be added
-21470227390x8007086DNo more printer destinations can be added
-21470227380x8007086EThis printer destination is idle and cannot accept control operations
-21470227370x8007086FThis printer destination request contains an invalid control function
-21470227360x80070870The print processor is not responding
-21470227350x80070871The spooler is not running
-21470227340x80070872This operation cannot be performed on the print destination in its current state
-21470227330x80070873This operation cannot be performed on the printer queue in its current state
-21470227320x80070874This operation cannot be performed on the print job in its current state
-21470227310x80070875A spooler memory allocation failure occurred
-21470227300x80070876The device driver does not exist
-21470227290x80070877The data type is not supported by the print processor
-21470227280x80070878The print processor is not installed
-21470227160x80070884The service database is locked
-21470227150x80070885The service table is full
-21470227140x80070886The requested service has already been started
-21470227130x80070887The service does not respond to control actions
-21470227120x80070888The service has not been started
-21470227110x80070889The service name is invalid
-21470227100x8007088AThe service is not responding to the control function
-21470227090x8007088BThe service control is busy
-21470227080x8007088CThe configuration file contains an invalid service program name
-21470227070x8007088DThe service could not be controlled in its present state
-21470227060x8007088EThe service ended abnormally
-21470227050x8007088FThe requested pause, continue, or stop is not valid for this service
-21470227040x80070890The service control dispatcher could not find the service name in the dispatch table
-21470227030x80070891The service control dispatcher pipe read failed
-21470227020x80070892A thread for the new service could not be created
-21470226960x80070898This workstation is already logged on to the local-area network
-21470226950x80070899The workstation is not logged on to the local-area network
-21470226940x8007089AThe specified username is invalid
-21470226930x8007089BThe password parameter is invalid
-21470226920x8007089CThe logon processor did not add the message alias
-21470226910x8007089DThe logon processor did not add the message alias
-21470226900x8007089EThe logoff processor did not delete the message alias
-21470226890x8007089FThe logoff processor did not delete the message alias
-21470226870x800708A1Network logons are paused
-21470226860x800708A2A centralized logon-server conflict occurred
-21470226850x800708A3The server is configured without a valid user path
-21470226840x800708A4An error occurred while loading or running the logon script
-21470226820x800708A6The logon server was not specified. Your computer will be logged on as STANDALONE
-21470226810x800708A7The logon server could not be found
-21470226800x800708A8There is already a logon domain for this computer
-21470226790x800708A9The logon server could not validate the logon
-21470226770x800708ABThe security database could not be found
-21470226760x800708ACThe group name could not be found
-21470226750x800708ADThe user name could not be found
-21470226740x800708AEThe resource name could not be found
-21470226730x800708AFThe group already exists
-21470226720x800708B0The account already exists
-21470226710x800708B1The resource permission list already exists
-21470226700x800708B2This operation is only allowed on the primary domain controller of the domain
-21470226690x800708B3The security database has not been started
-21470226680x800708B4There are too many names in the user accounts database
-21470226670x800708B5A disk I/O failure occurred
-21470226660x800708B6The limit of 64 entries per resource was exceeded
-21470226650x800708B7Deleting a user with a session is not allowed
-21470226640x800708B8The parent directory could not be located
-21470226630x800708B9Unable to add to the security database session cache segment
-21470226620x800708BAThis operation is not allowed on this special group
-21470226610x800708BBThis user is not cached in user accounts database session cache
-21470226600x800708BCThe user already belongs to this group
-21470226590x800708BDThe user does not belong to this group
-21470226580x800708BEThis user account is undefined
-21470226570x800708BFThis user account has expired
-21470226560x800708C0The user is not allowed to log on from this workstation
-21470226550x800708C1The user is not allowed to log on at this time
-21470226540x800708C2The password of this user has expired
-21470226530x800708C3The password of this user cannot change
-21470226520x800708C4This password cannot be used now
-21470226510x800708C5The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements
-21470226500x800708C6The password of this user is too recent to change
-21470226490x800708C7The security database is corrupted
-21470226480x800708C8No updates are necessary to this replicant network/local security database
-21470226470x800708C9This replicant database is outdated; synchronization is required
-21470226460x800708CAThis network connection does not exist
-21470226450x800708CBThis asg_type is invalid
-21470226440x800708CCThis device is currently being shared
-21470226430x800708CDThe user name may not be same as computer name
-21470226260x800708DEThe computer name could not be added as a message alias. The name may already exist on the network
-21470226250x800708DFThe Messenger service is already started
-21470226240x800708E0The Messenger service failed to start
-21470226230x800708E1The message alias could not be found on the network
-21470226220x800708E2This message alias has already been forwarded
-21470226210x800708E3This message alias has been added but is still forwarded
-21470226200x800708E4This message alias already exists locally
-21470226190x800708E5The maximum number of added message aliases has been exceeded
-21470226180x800708E6The computer name could not be deleted
-21470226170x800708E7Messages cannot be forwarded back to the same workstation
-21470226160x800708E8An error occurred in the domain message processor
-21470226150x800708E9The message was sent, but the recipient has paused the Messenger service
-21470226140x800708EAThe message was sent but not received
-21470226130x800708EBThe message alias is currently in use. Try again later
-21470226120x800708ECThe Messenger service has not been started
-21470226110x800708EDThe name is not on the local computer
-21470226100x800708EEThe forwarded message alias could not be found on the network
-21470226090x800708EFThe message alias table on the remote station is full
-21470226080x800708F0Messages for this alias are not currently being forwarded
-21470226070x800708F1The broadcast message was truncated
-21470226020x800708F6This is an invalid device name
-21470226010x800708F7A write fault occurred
-21470225990x800708F9A duplicate message alias exists on the network
-21470225980x800708FAThis message alias will be deleted later
-21470225970x800708FBThe message alias was not successfully deleted from all networks
-21470225960x800708FCThis operation is not supported on computers with multiple networks
-21470225860x80070906This shared resource does not exist
-21470225850x80070907This device is not shared
-21470225840x80070908A session does not exist with that computer name
-21470225820x8007090AThere is not an open file with that identification number
-21470225810x8007090BA failure occurred when executing a remote administration command
-21470225800x8007090CA failure occurred when opening a remote temporary file
-21470225790x8007090DThe data returned from a remote administration command has been truncated to 64K
-21470225780x8007090EThis device cannot be shared as both a spooled and a non-spooled resource
-21470225770x8007090FThe information in the list of servers may be incorrect
-21470225760x80070910The computer is not active in this domain
-21470225750x80070911The share must be removed from the Distributed File System before it can be deleted
-21470225650x8007091BThe operation is invalid for this device
-21470225640x8007091CThis device cannot be shared
-21470225630x8007091DThis device was not open
-21470225620x8007091EThis device name list is invalid
-21470225610x8007091FThe queue priority is invalid
-21470225590x80070921There are no shared communication devices
-21470225580x80070922The queue you specified does not exist
-21470225560x80070924This list of devices is invalid
-21470225550x80070925The requested device is invalid
-21470225540x80070926This device is already in use by the spooler
-21470225530x80070927This device is already in use as a communication device
-21470225450x8007092FThis computer name is invalid
-21470225420x80070932The string and prefix specified are too long
-21470225400x80070934This path component is invalid
-21470225390x80070935Could not determine the type of input
-21470225340x8007093AThe buffer for types is not big enough
-21470225260x80070942Profile files cannot exceed 64K
-21470225250x80070943The start offset is out of range
-21470225240x80070944The system cannot delete current connections to network resources
-21470225230x80070945The system was unable to parse the command line in this file
-21470225220x80070946An error occurred while loading the profile file
-21470225210x80070947Errors occurred while saving the profile file. The profile was partially saved
-21470225190x80070949Log file %1 is full
-21470225180x8007094AThis log file has changed between reads
-21470225170x8007094BLog file %1 is corrupt
-21470225160x8007094CThe source path cannot be a directory
-21470225150x8007094DThe source path is illegal
-21470225140x8007094EThe destination path is illegal
-21470225130x8007094FThe source and destination paths are on different servers
-21470225110x80070951The Run server you requested is paused
-21470225070x80070955An error occurred when communicating with a Run server
-21470225050x80070957An error occurred when starting a background process
-21470225040x80070958The shared resource you are connected to could not be found
-21470224960x80070960The LAN adapter number is invalid
-21470224950x80070961This network connection has files open or requests pending
-21470224940x80070962Active connections still exist
-21470224930x80070963This share name or password is invalid
-21470224920x80070964The device is in use by an active process and cannot be disconnected
-21470224910x80070965The drive letter is in use locally
-21470224660x8007097EThe specified client is already registered for the specified event
-21470224650x8007097FThe alert table is full
-21470224640x80070980An invalid or nonexistent alert name was raised
-21470224630x80070981The alert recipient is invalid
-21470224620x80070982A user's session with this server has been deleted because the user's logon hours are no longer valid
-21470224560x80070988The log file does not contain the requested record number
-21470224460x80070992The user accounts database is not configured correctly
-21470224450x80070993This operation is not permitted when the Netlogon service is running
-21470224440x80070994This operation is not allowed on the last administrative account
-21470224430x80070995Could not find domain controller for this domain
-21470224420x80070996Could not set logon information for this user
-21470224410x80070997The Netlogon service has not been started
-21470224400x80070998Unable to add to the user accounts database
-21470224390x80070999This server's clock is not synchronized with the primary domain controller's clock
-21470224380x8007099AA password mismatch has been detected
-21470224360x8007099CThe server identification does not specify a valid server
-21470224350x8007099DThe session identification does not specify a valid session
-21470224340x8007099EThe connection identification does not specify a valid connection
-21470224330x8007099FThere is no space for another entry in the table of available servers
-21470224320x800709A0The server has reached the maximum number of sessions it supports
-21470224310x800709A1The server has reached the maximum number of connections it supports
-21470224300x800709A2The server cannot open more files because it has reached its maximum number
-21470224290x800709A3There are no alternate servers registered on this server
-21470224260x800709A6Try down-level (remote admin protocol) version of API instead
-21470224160x800709B0The UPS driver could not be accessed by the UPS service
-21470224150x800709B1The UPS service is not configured correctly
-21470224140x800709B2The UPS service could not access the specified Comm Port
-21470224130x800709B3The UPS indicated a line fail or low battery situation. Service not started
-21470224120x800709B4The UPS service failed to perform a system shut down
-21470223960x800709C4The program below returned an MS-DOS error code:
-21470223950x800709C5The program below needs more memory:
-21470223940x800709C6The program below called an unsupported MS-DOS function:
-21470223930x800709C7The workstation failed to boot
-21470223920x800709C8The file below is corrupt
-21470223910x800709C9No loader is specified in the boot-block definition file
-21470223900x800709CANetBIOS returned an error: The NCB and SMB are dumped above
-21470223890x800709CBA disk I/O error occurred
-21470223880x800709CCImage parameter substitution failed
-21470223870x800709CDToo many image parameters cross disk sector boundaries
-21470223860x800709CEThe image was not generated from an MS-DOS diskette formatted with /S
-21470223850x800709CFRemote boot will be restarted later
-21470223840x800709D0The call to the Remoteboot server failed
-21470223830x800709D1Cannot connect to the Remoteboot server
-21470223820x800709D2Cannot open image file on the Remoteboot server
-21470223810x800709D3Connecting to the Remoteboot server
-21470223800x800709D4Connecting to the Remoteboot server
-21470223790x800709D5Remote boot service was stopped; check the error log for the cause of the problem
-21470223780x800709D6Remote boot startup failed; check the error log for the cause of the problem
-21470223770x800709D7A second connection to a Remoteboot resource is not allowed
-21470223460x800709F6The browser service was configured with MaintainServerList=No
-21470222860x80070A32Service failed to start since none of the network adapters started with this service
-21470222850x80070A33Service failed to start due to bad startup information in the registry
-21470222840x80070A34Service failed to start because its database is absent or corrupt
-21470222830x80070A35Service failed to start because RPLFILES share is absent
-21470222820x80070A36Service failed to start because RPLUSER group is absent
-21470222810x80070A37Cannot enumerate service records
-21470222800x80070A38Workstation record information has been corrupted
-21470222790x80070A39Workstation record was not found
-21470222780x80070A3AWorkstation name is in use by some other workstation
-21470222770x80070A3BProfile record information has been corrupted
-21470222760x80070A3CProfile record was not found
-21470222750x80070A3DProfile name is in use by some other profile
-21470222740x80070A3EThere are workstations using this profile
-21470222730x80070A3FConfiguration record information has been corrupted
-21470222720x80070A40Configuration record was not found
-21470222710x80070A41Adapter id record information has been corrupted
-21470222700x80070A42An internal service error has occurred
-21470222690x80070A43Vendor id record information has been corrupted
-21470222680x80070A44Boot block record information has been corrupted
-21470222670x80070A45The user account for this workstation record is missing
-21470222660x80070A46The RPLUSER local group could not be found
-21470222650x80070A47Boot block record was not found
-21470222640x80070A48Chosen profile is incompatible with this workstation
-21470222630x80070A49Chosen network adapter id is in use by some other workstation
-21470222620x80070A4AThere are profiles using this configuration
-21470222610x80070A4BThere are workstations, profiles or configurations using this boot block
-21470222600x80070A4CService failed to backup Remoteboot database
-21470222590x80070A4DAdapter record was not found
-21470222580x80070A4EVendor record was not found
-21470222570x80070A4FVendor name is in use by some other vendor record
-21470222560x80070A50(boot name, vendor id) is in use by some other boot block record
-21470222550x80070A51Configuration name is in use by some other configuration
-21470222360x80070A64The internal database maintained by the DFS service is corrupt
-21470222350x80070A65One of the records in the internal DFS database is corrupt
-21470222340x80070A66There is no DFS name whose entry path matches the input Entry Path
-21470222330x80070A67A root or link with the given name already exists
-21470222320x80070A68The server share specified is already shared in the DFS
-21470222310x80070A69The indicated server share does not support the indicated DFS namespace
-21470222300x80070A6AThe operation is not valid on this portion of the namespace
-21470222290x80070A6BThe operation is not valid on this portion of the namespace
-21470222280x80070A6CThe operation is ambiguous because the link has multiple servers
-21470222270x80070A6DUnable to create a link
-21470222260x80070A6EThe server is not DFS Aware
-21470222250x80070A6FThe specified rename target path is invalid
-21470222240x80070A70The specified DFS link is offline
-21470222230x80070A71The specified server is not a server for this link
-21470222220x80070A72A cycle in the DFS name was detected
-21470222210x80070A73The operation is not supported on a server-based DFS
-21470222200x80070A74This link is already supported by the specified server-share
-21470222190x80070A75Can't remove the last server-share supporting this root or link
-21470222180x80070A76The operation is not supported for an Inter-DFS link
-21470222170x80070A77The internal state of the DFS Service has become inconsistent
-21470222160x80070A78The DFS Service has been installed on the specified server
-21470222150x80070A79The DFS data being reconciled is identical
-21470222140x80070A7AThe DFS root cannot be deleted - Uninstall DFS if required
-21470222130x80070A7BA child or parent directory of the share is already in a DFS
-21470222060x80070A82DFS internal error
-21470222050x80070A83This machine is already joined to a domain
-21470222040x80070A84This machine is not currently joined to a domain
-21470222030x80070A85This machine is a domain controller and cannot be unjoined from a domain
-21470222020x80070A86The destination domain controller does not support creating machine accounts in OUs
-21470222010x80070A87The specified workgroup name is invalid
-21470222000x80070A88The specified computer name is incompatible with the default language used on the domain controller
-21470221990x80070A89The 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, reboot, and rejoin the domain
-21470221980x80070A8AThis version of Windows cannot be joined to a domain
-21470221970x80070A8BAn 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, see Windows Help
-21470221960x80070A8CThis machine is already joined to a cloud domain and cannot be subsequently joined to an Active Directory domain
-21470221950x80070A8DPassword must change at next logon
-21470221940x80070A8EAccount is locked out
-21470221930x80070A8FPassword is too long
-21470221920x80070A90Password doesn't meet the complexity policy
-21470221910x80070A91Password doesn't meet the requirements of the filter dll's
-21470221870x80070A95Offline join completion information was not found
-21470221860x80070A96The offline join completion information was bad
-21470221850x80070A97Unable 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
-21470221840x80070A98The domain join info being saved was incomplete or bad
-21470221830x80070A99Offline join operation successfully completed but a restart is needed
-21470221820x80070A9AThere was no offline join operation pending
-21470221810x80070A9BUnable to set one or more requested machine or domain name values on the local computer
-21470221800x80070A9CCould not verify the current machine's hostname against the saved value in the join completion information
-21470221790x80070A9DUnable 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
-21470221780x80070A9EThe minimum session security requirements for this operation were not met
-21470221770x80070A9FComputer account provisioning blob version is not supported
-21470221760x80070AA0The specified domain controller does not meet the version requirement for this operation. Please select a domain controller capable of issuing claims
-21470221750x80070AA1This operation requires a domain controller which supports LDAP. Please select an LDAP-capable domain controller
-21470221740x80070AA2A 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
-21470221730x80070AA3The Windows version of the specified image does not support provisioning
-21470221720x80070AA4The machine name is blocked from joining the domain
-21470221710x80070AA5The domain controller does not meet the version requirement for this operation. See http://go.microsoft.com/fwlink/?LinkId=294288 for more information
-21470221700x80070AA6The local machine does not allow querying of LSA secrets in plain-text
-21470218970x80070BB7This is the last error in NERR range
-21470218960x80070BB8The specified print monitor is unknown
-21470218950x80070BB9The specified printer driver is currently in use
-21470218940x80070BBAThe spool file was not found
-21470218930x80070BBBA StartDocPrinter call was not issued
-21470218920x80070BBCAn AddJob call was not issued
-21470218910x80070BBDThe specified print processor has already been installed
-21470218900x80070BBEThe specified print monitor has already been installed
-21470218890x80070BBFThe specified print monitor does not have the required functions
-21470218880x80070BC0The specified print monitor is currently in use
-21470218870x80070BC1The requested operation is not allowed when there are jobs queued to the printer
-21470218860x80070BC2The requested operation is successful. Changes will not be effective until the system is rebooted
-21470218850x80070BC3The requested operation is successful. Changes will not be effective until the service is restarted
-21470218840x80070BC4No printers were found
-21470218830x80070BC5The printer driver is known to be unreliable
-21470218820x80070BC6The printer driver is known to harm the system
-21470218810x80070BC7The specified printer driver package is currently in use
-21470218800x80070BC8Unable to find a core driver package that is required by the printer driver package
-21470218790x80070BC9The requested operation failed. A system reboot is required to roll back changes made
-21470218780x80070BCAThe requested operation failed. A system reboot has been initiated to roll back changes made
-21470218770x80070BCBThe specified printer driver was not found on the system and needs to be downloaded
-21470218760x80070BCCThe requested print job has failed to print. A print system update requires the job to be resubmitted
-21470218750x80070BCDThe printer driver does not contain a valid manifest, or contains too many manifests
-21470218740x80070BCEThe specified printer cannot be shared
-21470218730x80070BCFThere is a problem with a configuration of user specified shut down command file. The UPS service started anyway
-21470218710x80070BD1A defective sector on drive %1 has been replaced (hotfixed). No data was lost. You should run CHKDSK soon to restore full performance and replenish the volume's spare sector pool. The hotfix occurred while processing a remote request
-21470218700x80070BD2A disk error occurred on the HPFS volume in drive %1. The error occurred while processing a remote request
-21470218690x80070BD3The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made on %1 at %2. Any updates made to the database after this time are lost
-21470218680x80070BD4The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made on %1 at %2. Any updates made to the database after this time are lost
-21470218670x80070BD5Local security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE
-21470218660x80070BD6The server cannot export directory %1, to client %2. It is exported from another server
-21470218650x80070BD7The replication server could not update directory %2 from the source on %3 due to error %1
-21470218640x80070BD8Master %1 did not send an update notice for directory %2 at the expected time
-21470218630x80070BD9User %1 has exceeded account limitation %2 on server %3
-21470218620x80070BDAThe primary domain controller for domain %1 failed
-21470218610x80070BDBFailed to authenticate with %2, a Windows Domain Controller for domain %1
-21470218600x80070BDCThe replicator attempted to log on at %2 as %1 and failed
-21470218590x80070BDD@I *LOGON HOURS
-21470218580x80070BDEReplicator could not access %2 on %3 due to system error %1
-21470218570x80070BDFReplicator limit for files in a directory has been exceeded
-21470218560x80070BE0Replicator limit for tree depth has been exceeded
-21470218550x80070BE1The replicator cannot update directory %1. It has tree integrity and is the current directory for some process
-21470218540x80070BE2Network error %1 occurred
-21470218510x80070BE5System error %1 occurred
-21470218500x80070BE6Cannot log on. User is currently logged on and argument TRYUSER is set to NO
-21470218490x80070BE7IMPORT path %1 cannot be found
-21470218480x80070BE8EXPORT path %1 cannot be found
-21470218470x80070BE9Replicated data has changed in directory %1
-21470218460x80070BEAThe operation was paused
-21470218450x80070BEBThe Registry or the information you just typed includes an illegal value for %1""""
-21470218440x80070BECThe required parameter was not provided on the command line or in the configuration file
-21470218430x80070BEDLAN Manager does not recognize %1"" as a valid option""
-21470218420x80070BEEA request for resource could not be satisfied
-21470218410x80070BEFA problem exists with the system configuration
-21470218400x80070BF0A system error has occurred
-21470218390x80070BF1An internal consistency error has occurred
-21470218380x80070BF2The configuration file or the command line has an ambiguous option
-21470218370x80070BF3The configuration file or the command line has a duplicate parameter
-21470218360x80070BF4The service did not respond to control and was stopped with the DosKillProc function
-21470218350x80070BF5An error occurred when attempting to run the service program
-21470218340x80070BF6The sub-service failed to start
-21470218330x80070BF7There is a conflict in the value or use of these options: %1
-21470218320x80070BF8There is a problem with the file
-21470218260x80070BFEmemory
-21470218250x80070BFFdisk space
-21470218240x80070C00thread
-21470218230x80070C01process
-21470218220x80070C02Security Failure
-21470218210x80070C03Bad or missing LAN Manager root directory
-21470218200x80070C04The network software is not installed
-21470218190x80070C05The server is not started
-21470218180x80070C06The server cannot access the user accounts database (NET.ACC)
-21470218170x80070C07Incompatible files are installed in the LANMAN tree
-21470218160x80070C08The LANMAN\LOGS directory is invalid
-21470218150x80070C09The domain specified could not be used
-21470218140x80070C0AThe computer name is being used as a message alias on another computer
-21470218130x80070C0BThe announcement of the server name failed
-21470218120x80070C0CThe user accounts database is not configured correctly
-21470218110x80070C0DThe server is not running with user-level security
-21470218090x80070C0FThe workstation is not configured properly
-21470218080x80070C10View your error log for details
-21470218070x80070C11Unable to write to this file
-21470218060x80070C12ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs
-21470218050x80070C13The LM386 server cannot be started because CACHE.EXE is not running
-21470218040x80070C14There is no account for this computer in the security database
-21470218030x80070C15This computer is not a member of the group SERVERS
-21470218020x80070C16The group SERVERS is not present in the local security database
-21470218010x80070C17This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration
-21470218000x80070C18The primary Domain Controller for this domain could not be located
-21470217990x80070C19This computer is configured to be the primary domain controller of its domain. However, the computer %1 is currently claiming to be the primary domain controller of the domain
-21470217980x80070C1AThe service failed to authenticate with the primary domain controller
-21470217970x80070C1BThere is a problem with the security database creation date or serial number
-21470217960x80070C1CThe operation failed because a network software error occurred
-21470217950x80070C1DThe system ran out of a resource controlled by the %1 option
-21470217940x80070C1EThe service failed to obtain a long-term lock on the segment for network control blocks (NCBs). The error code is the data
-21470217930x80070C1FThe service failed to release the long-term lock on the segment for network control blocks (NCBs). The error code is the data
-21470217920x80070C20There was an error stopping service %1. The error code from NetServiceControl is the data
-21470217910x80070C21Initialization failed because of a system execution failure on path %1. The system error code is the data
-21470217900x80070C22An unexpected network control block (NCB) was received. The NCB is the data
-21470217890x80070C23The network is not started
-21470217880x80070C24A DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed. The data shown is in this format: DWORD approx CS:IP of call to ioctl or fsctl WORD error code WORD ioctl or fsctl number
-21470217870x80070C25Unable to create or open system semaphore %1. The error code is the data
-21470217860x80070C26Initialization failed because of an open/create error on the file %1. The system error code is the data
-21470217850x80070C27An unexpected NetBIOS error occurred. The error code is the data
-21470217840x80070C28An illegal server message block (SMB) was received. The SMB is the data
-21470217830x80070C29Initialization failed because the requested service %1 could not be started
-21470217820x80070C2ASome entries in the error log were lost because of a buffer overflow
-21470217760x80070C30Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed
-21470217750x80070C31The server cannot increase the size of a memory segment
-21470217740x80070C32Initialization failed because account file %1 is either incorrect or not present
-21470217730x80070C33Initialization failed because network %1 was not started
-21470217720x80070C34The server failed to start. Either all three chdev parameters must be zero or all three must be nonzero
-21470217710x80070C35A remote API request was halted due to the following invalid description string: %1
-21470217700x80070C36The network %1 ran out of network control blocks (NCBs). You may need to increase NCBs for this network. The following information includes the number of NCBs submitted by the server when this error occurred:
-21470217690x80070C37The server cannot create the %1 mailslot needed to send the ReleaseMemory alert message. The error received is:
-21470217680x80070C38The server failed to register for the ReleaseMemory alert, with recipient %1. The error code from NetAlertStart is the data
-21470217670x80070C39The server cannot update the AT schedule file. The file is corrupted
-21470217660x80070C3AThe server encountered an error when calling NetIMakeLMFileName. The error code is the data
-21470217650x80070C3BInitialization failed because of a system execution failure on path %1. There is not enough memory to start the process. The system error code is the data
-21470217640x80070C3CLongterm lock of the server buffers failed. Check swap disk's free space and restart the system to start the server
-21470217560x80070C44The service has stopped due to repeated consecutive occurrences of a network control block (NCB) error. The last bad NCB follows in raw data
-21470217550x80070C45The Message server has stopped due to a lock on the Message server shared data segment
-21470217460x80070C4EA file system error occurred while opening or writing to the system message log file %1. Message logging has been switched off due to the error. The error code is the data
-21470217450x80070C4FUnable to display message POPUP due to system VIO call error. The error code is the data
-21470217440x80070C50An illegal server message block (SMB) was received. The SMB is the data
-21470217360x80070C58The workstation information segment is bigger than 64K. The size follows, in DWORD format:
-21470217350x80070C59The workstation was unable to get the name-number of the computer
-21470217340x80070C5AThe workstation could not initialize the Async NetBIOS Thread. The error code is the data
-21470217330x80070C5BThe workstation could not open the initial shared segment. The error code is the data
-21470217320x80070C5CThe workstation host table is full
-21470217310x80070C5DA bad mailslot server message block (SMB) was received. The SMB is the data
-21470217300x80070C5EThe workstation encountered an error while trying to start the user accounts database. The error code is the data
-21470217290x80070C5FThe workstation encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data
-21470217260x80070C62The Alerter service had a problem creating the list of alert recipients. The error code is %1
-21470217250x80070C63There was an error expanding %1 as a group name. Try splitting the group into two or more smaller groups
-21470217240x80070C64There was an error sending %2 the alert message - ( %3 ) The error code is %1
-21470217230x80070C65There was an error in creating or reading the alerter mailslot. The error code is %1
-21470217220x80070C66The server could not read the AT schedule file
-21470217210x80070C67The server found an invalid AT schedule record
-21470217200x80070C68The server could not find an AT schedule file so it created one
-21470217190x80070C69The server could not access the %1 network with NetBiosOpen
-21470217180x80070C6AThe AT command processor could not run %1
-21470217160x80070C6CWARNING: Because of a lazy-write error, drive %1 now contains some corrupted data. The cache is stopped
-21470217150x80070C6DA defective sector on drive %1 has been replaced (hotfixed). No data was lost. You should run CHKDSK soon to restore full performance and replenish the volume's spare sector pool. The hotfix occurred while processing a remote request
-21470217140x80070C6EA disk error occurred on the HPFS volume in drive %1. The error occurred while processing a remote request
-21470217130x80070C6FThe user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made at %1. Any updates made to the database after this time are lost
-21470217120x80070C70The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at %1. Any updates made to the database made after this time are lost
-21470217110x80070C71Local security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE
-21470217100x80070C72Local security could not be started because an error occurred during initialization. The error code returned is %1. THE SYSTEM IS NOT SECURE
-21470217060x80070C76A NetWksta internal error has occurred: %1
-21470217050x80070C77The redirector is out of a resource: %1
-21470217040x80070C78A server message block (SMB) error occurred on the connection to %1. The SMB header is the data
-21470217030x80070C79A virtual circuit error occurred on the session to %1. The network control block (NCB) command and return code is the data
-21470217020x80070C7AHanging up a stuck session to %1
-21470217010x80070C7BA network control block (NCB) error occurred (%1). The NCB is the data
-21470217000x80070C7CA write operation to %1 failed. Data may have been lost
-21470216990x80070C7DReset of driver %1 failed to complete the network control block (NCB). The NCB is the data
-21470216980x80070C7EThe amount of resource %1 requested was more than the maximum. The maximum amount was allocated
-21470216920x80070C84The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should be increased
-21470216910x80070C85The server could not close %1. The file is probably corrupted
-21470216900x80070C86The replicator cannot update directory %1. It has tree integrity and is the current directory for some process
-21470216890x80070C87The server cannot export directory %1 to client %2. It is exported from another server
-21470216880x80070C88The replication server could not update directory %2 from the source on %3 due to error %1
-21470216870x80070C89Master %1 did not send an update notice for directory %2 at the expected time
-21470216860x80070C8AThis computer could not authenticate with %2, a Windows domain controller for domain %1, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator
-21470216850x80070C8BThe replicator attempted to log on at %2 as %1 and failed
-21470216840x80070C8CNetwork error %1 occurred
-21470216830x80070C8DReplicator limit for files in a directory has been exceeded
-21470216820x80070C8EReplicator limit for tree depth has been exceeded
-21470216810x80070C8FUnrecognized message received in mailslot
-21470216800x80070C90System error %1 occurred
-21470216790x80070C91Cannot log on. User is currently logged on and argument TRYUSER is set to NO
-21470216780x80070C92IMPORT path %1 cannot be found
-21470216770x80070C93EXPORT path %1 cannot be found
-21470216760x80070C94Replicator failed to update signal file in directory %2 due to %1 system error
-21470216750x80070C95Disk Fault Tolerance Error %1
-21470216740x80070C96Replicator could not access %2 on %3 due to system error %1
-21470216730x80070C97The primary domain controller for domain %1 has apparently failed
-21470216720x80070C98Changing machine account password for account %1 failed with the following error: %2
-21470216710x80070C99An error occurred while updating the logon or logoff information for %1
-21470216700x80070C9AAn error occurred while synchronizing with primary domain controller %1
-21470216690x80070C9BThe session setup to the Windows Domain Controller %1 for the domain %2 failed because %1 does not support signing or sealing the Netlogon session. Either upgrade the Domain controller or set the RequireSignOrSeal registry entry on this machine to 0
-21470216660x80070C9EA power failure was detected at the server
-21470216650x80070C9FThe UPS service performed server shut down
-21470216640x80070CA0The UPS service did not complete execution of the user specified shut down command file
-21470216630x80070CA1The UPS driver could not be opened. The error code is the data
-21470216620x80070CA2Power has been restored
-21470216610x80070CA3There is a problem with a configuration of user specified shut down command file
-21470216600x80070CA4The UPS service failed to execute a user specified shutdown command file %1. The error code is the data
-21470216460x80070CB2Initialization failed because of an invalid or missing parameter in the configuration file %1
-21470216450x80070CB3Initialization failed because of an invalid line in the configuration file %1. The invalid line is the data
-21470216440x80070CB4Initialization failed because of an error in the configuration file %1
-21470216430x80070CB5The file %1 has been changed after initialization. The boot-block loading was temporarily terminated
-21470216420x80070CB6The files do not fit to the boot-block configuration file %1. Change the BASE and ORG definitions or the order of the files
-21470216410x80070CB7Initialization failed because the dynamic-link library %1 returned an incorrect version number
-21470216400x80070CB8There was an unrecoverable error in the dynamic- link library of the service
-21470216390x80070CB9The system returned an unexpected error code. The error code is the data
-21470216380x80070CBAThe fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K
-21470216370x80070CBBThe fault-tolerance error-log file, LANROOT\LOGS\FT.LOG, had the update in progress bit set upon opening, which means that the system crashed while working on the error log
-21470216360x80070CBCThis computer has been successfully joined to domain '%1'
-21470216350x80070CBDThis computer has been successfully joined to workgroup '%1'
-21470215970x80070CE3%1 %2 %3 %4 %5 %6 %7 %8 %9
-21470215950x80070CE5Remote IPC
-21470215940x80070CE6Remote Admin
-21470215930x80070CE7Logon server share
-21470215920x80070CE8A network error occurred
-21470214960x80070D48There is not enough memory to start the Workstation service
-21470214950x80070D49An error occurred when reading the NETWORKS entry in the LANMAN.INI file
-21470214940x80070D4AThis is an invalid argument: %1
-21470214930x80070D4BThe %1 NETWORKS entry in the LANMAN.INI file has a syntax error and will be ignored
-21470214920x80070D4CThere are too many NETWORKS entries in the LANMAN.INI file
-21470214900x80070D4EAn error occurred when opening network device driver %1 = %2
-21470214890x80070D4FDevice driver %1 sent a bad BiosLinkage response
-21470214880x80070D50The program cannot be used with this operating system
-21470214870x80070D51The redirector is already installed
-21470214860x80070D52Installing NETWKSTA.SYS Version %1.%2.%3 (%4)
-21470214850x80070D53There was an error installing NETWKSTA.SYS. Press ENTER to continue
-21470214840x80070D54Resolver linkage problem
-21470214830x80070D55Your logon time at %1 ends at %2. Please clean up and log off
-21470214820x80070D56You will be automatically disconnected at %1
-21470214810x80070D57Your logon time at %1 has ended
-21470214800x80070D58Your logon time at %1 ended at %2
-21470214790x80070D59WARNING: You have until %1 to logoff. If you have not logged off at this time, your session will be disconnected, and any open files or devices you have open may lose data
-21470214780x80070D5AWARNING: You must log off at %1 now. You have two minutes to log off, or you will be disconnected
-21470214770x80070D5BYou have open files or devices, and a forced disconnection may cause you to lose data
-21470214760x80070D5CDefault Share for Internal Use
-21470214750x80070D5DMessenger Service
-21470213960x80070DACThe command completed successfully
-21470213950x80070DADYou used an invalid option
-21470213940x80070DAESystem error %1 has occurred
-21470213930x80070DAFThe command contains an invalid number of arguments
-21470213920x80070DB0The command completed with one or more errors
-21470213910x80070DB1You used an option with an invalid value
-21470213900x80070DB2The option %1 is unknown
-21470213890x80070DB3Option %1 is ambiguous
-21470213860x80070DB6A command was used with conflicting switches
-21470213850x80070DB7Could not find subprogram %1
-21470213840x80070DB8The software requires a newer version of the operating system
-21470213830x80070DB9More data is available than can be returned by Windows
-21470213820x80070DBAMore help is available by typing NET HELPMSG %1
-21470213810x80070DBBThis command can be used only on a Windows Domain Controller
-21470213800x80070DBCThis command cannot be used on a Windows Domain Controller
-21470213760x80070DC0These Windows services are started:
-21470213750x80070DC1The %1 service is not started
-21470213740x80070DC2The %1 service is starting
-21470213730x80070DC3The %1 service could not be started
-21470213720x80070DC4The %1 service was started successfully
-21470213710x80070DC5Stopping the Workstation service also stops the Server service
-21470213700x80070DC6The workstation has open files
-21470213690x80070DC7The %1 service is stopping
-21470213680x80070DC8The %1 service could not be stopped
-21470213670x80070DC9The %1 service was stopped successfully
-21470213660x80070DCAThe following services are dependent on the %1 service. Stopping the %1 service will also stop these services
-21470213630x80070DCDThe service is starting or stopping. Please try again later
-21470213620x80070DCEThe service did not report an error
-21470213610x80070DCFAn error occurred controlling the device
-21470213600x80070DD0The %1 service was continued successfully
-21470213590x80070DD1The %1 service was paused successfully
-21470213580x80070DD2The %1 service failed to resume
-21470213570x80070DD3The %1 service failed to pause
-21470213560x80070DD4The %1 service continue is pending
-21470213550x80070DD5The %1 service pause is pending
-21470213540x80070DD6%1 was continued successfully
-21470213530x80070DD7%1 was paused successfully
-21470213520x80070DD8The %1 service has been started by another process and is pending
-21470213490x80070DDBA service specific error occurred: %1
-21470212360x80070E4CThese workstations have sessions on this server:
-21470212350x80070E4DThese workstations have sessions with open files on this server:
-21470212300x80070E52The message alias is forwarded
-21470212260x80070E56You have these remote connections:
-21470212250x80070E57Continuing will cancel the connections
-21470212210x80070E5BThe session from %1 has open files
-21470212200x80070E5CNew connections will be remembered
-21470212190x80070E5DNew connections will not be remembered
-21470212180x80070E5EAn error occurred while saving your profile : Access Denied. The state of your remembered connections has not changed
-21470212170x80070E5FAn error occurred while reading your profile
-21470212160x80070E60An error occurred while restoring the connection to %1
-21470212140x80070E62No network services are started
-21470212130x80070E63There are no entries in the list
-21470212080x80070E68Users have open files on %1. Continuing the operation will force the files closed
-21470212070x80070E69The Workstation service is already running. Windows will ignore command options for the workstation
-21470212050x80070E6BThere are open files and/or incomplete directory searches pending on the connection to %1
-21470212030x80070E6DThe request will be processed at a domain controller for domain %1
-21470212020x80070E6EThe shared queue cannot be deleted while a print job is being spooled to the queue
-21470212010x80070E6F%1 has a remembered connection to %2
-21470211860x80070E7EAn error occurred while opening the Help file
-21470211850x80070E7FThe Help file is empty
-21470211840x80070E80The Help file is corrupted
-21470211830x80070E81Could not find a domain controller for domain %1
-21470211820x80070E82This operation is privileged on systems with earlier versions of the software
-21470211800x80070E84The device type is unknown
-21470211790x80070E85The log file has been corrupted
-21470211780x80070E86Program filenames must end with .EXE
-21470211770x80070E87A matching share could not be found so nothing was deleted
-21470211760x80070E88A bad value is in the units-per-week field of the user record
-21470211750x80070E89The password is invalid for %1
-21470211740x80070E8AAn error occurred while sending a message to %1
-21470211730x80070E8BThe password or user name is invalid for %1
-21470211710x80070E8DAn error occurred when the share was deleted
-21470211700x80070E8EThe user name is invalid
-21470211690x80070E8FThe password is invalid
-21470211680x80070E90The passwords do not match
-21470211670x80070E91Your persistent connections were not all restored
-21470211660x80070E92This is not a valid computer name or domain name
-21470211640x80070E94Default permissions cannot be set for that resource
-21470211620x80070E96A valid password was not entered
-21470211610x80070E97A valid name was not entered
-21470211600x80070E98The resource named cannot be shared
-21470211590x80070E99The permissions string contains invalid permissions
-21470211580x80070E9AYou can only perform this operation on printers and communication devices
-21470211540x80070E9E%1 is an invalid user or group name
-21470211530x80070E9FThe server is not configured for remote administration
-21470211440x80070EA8No users have sessions with this server
-21470211430x80070EA9User %1 is not a member of group %2
-21470211420x80070EAAUser %1 is already a member of group %2
-21470211410x80070EABThere is no such user: %1
-21470211400x80070EACThis is an invalid response
-21470211390x80070EADNo valid response was provided
-21470211380x80070EAEThe destination list provided does not match the destination list of the printer queue
-21470211370x80070EAFYour password cannot be changed until %1
-21470211360x80070EB0%1 is not a recognized day of the week
-21470211350x80070EB1The time range specified ends before it starts
-21470211340x80070EB2%1 is not a recognized hour
-21470211330x80070EB3%1 is not a valid specification for minutes
-21470211320x80070EB4Time supplied is not exactly on the hour
-21470211310x80070EB512 and 24 hour time formats may not be mixed
-21470211300x80070EB6%1 is not a valid 12-hour suffix
-21470211290x80070EB7An illegal date format has been supplied
-21470211280x80070EB8An illegal day range has been supplied
-21470211270x80070EB9An illegal time range has been supplied
-21470211260x80070EBAArguments to NET USER are invalid. Check the minimum password length and/or arguments supplied
-21470211250x80070EBBThe value for ENABLESCRIPT must be YES
-21470211230x80070EBDAn illegal country/region code has been supplied
-21470211220x80070EBEThe user was successfully created but could not be added to the USERS local group
-21470211210x80070EBFThe user context supplied is invalid
-21470211200x80070EC0The dynamic-link library %1 could not be loaded, or an error occurred while trying to use it
-21470211190x80070EC1Sending files is no longer supported
-21470211180x80070EC2You may not specify paths for ADMIN$ and IPC$ shares
-21470211170x80070EC3User or group %1 is already a member of local group %2
-21470211160x80070EC4There is no such user or group: %1
-21470211150x80070EC5There is no such computer: %1
-21470211140x80070EC6The computer %1 already exists
-21470211130x80070EC7There is no such global user or group: %1
-21470211120x80070EC8Only disk shares can be marked as cacheable
-21470211060x80070ECEThe system could not find message: %1
-21470210940x80070EDAThis schedule date is invalid
-21470210930x80070EDBThe LANMAN root directory is unavailable
-21470210920x80070EDCThe SCHED.LOG file could not be opened
-21470210910x80070EDDThe Server service has not been started
-21470210900x80070EDEThe AT job ID does not exist
-21470210890x80070EDFThe AT schedule file is corrupted
-21470210880x80070EE0The delete failed due to a problem with the AT schedule file
-21470210870x80070EE1The command line cannot exceed 259 characters
-21470210860x80070EE2The AT schedule file could not be updated because the disk is full
-21470210840x80070EE4The AT schedule file is invalid. Please delete the file and create a new one
-21470210830x80070EE5The AT schedule file was deleted
-21470210820x80070EE6The syntax of this command is: AT [id] [/DELETE] AT time [/EVERY:date | /NEXT:date] command The AT command schedules a program command to run at a later date and time on a server. It also displays the list of programs and commands scheduled to be run. You can specify the date as M,T,W,Th,F,Sa,Su or 1-31 for the day of the month. You can specify the time in the 24 hour HH:MM format
-21470210810x80070EE7The AT command has timed-out. Please try again later
-21470210800x80070EE8The minimum password age for user accounts cannot be greater than the maximum password age
-21470210790x80070EE9You have specified a value that is incompatible with servers with down-level software. Please specify a lower value
-21470210260x80070F1E%1 is not a valid computer name
-21470210250x80070F1F%1 is not a valid Windows network message number
-21470209960x80070F3CMessage from %1 to %2 on %3
-21470209950x80070F3D****
-21470209940x80070F3E**** unexpected end of message ****
-21470209910x80070F41Press ESC to exit
-21470209900x80070F42
-21470209860x80070F46Current time at %1 is %2
-21470209850x80070F47The current local clock is %1 Do you want to set the local computer's time to match the time at %2? %3:
-21470209840x80070F48Could not locate a time-server
-21470209830x80070F49Could not find the domain controller for domain %1
-21470209820x80070F4ALocal time (GMT%3) at %1 is %2
-21470209810x80070F4BThe user's home directory could not be determined
-21470209800x80070F4CThe user's home directory has not been specified
-21470209790x80070F4DThe name specified for the user's home directory (%1) is not a universal naming convention (UNC) name
-21470209780x80070F4EDrive %1 is now connected to %2. Your home directory is %3\%4
-21470209770x80070F4FDrive %1 is now connected to %2
-21470209760x80070F50There are no available drive letters left
-21470209640x80070F5C%1 is not a valid domain or workgroup name
-21470209610x80070F5FThe current SNTP value is: %1
-21470209600x80070F60This computer is not currently configured to use a specific SNTP server
-21470209590x80070F61This current autoconfigured SNTP value is: %1
-21470209460x80070F6EReissue the given operation as a cached IO operation
-21470209450x80070F6FYou specified too many values for the %1 option
-21470209440x80070F70You entered an invalid value for the %1 option
-21470209430x80070F71The syntax is incorrect
-21470209360x80070F78You specified an invalid file number
-21470209350x80070F79You specified an invalid print job number
-21470209330x80070F7BThe user or group account specified cannot be found
-21470209310x80070F7DThe user was added but could not be enabled for File and Print Services for NetWare
-21470209300x80070F7EFile and Print Services for NetWare is not installed
-21470209290x80070F7FCannot set user properties for File and Print Services for NetWare
-21470209280x80070F80Password for %1 is: %2
-21470209270x80070F81NetWare compatible logon
-21470208960x80070FA0WINS encountered an error while processing the command
-21470208950x80070FA1The local WINS cannot be deleted
-21470208940x80070FA2The importation from the file failed
-21470208930x80070FA3The backup failed. Was a full backup done before?
-21470208920x80070FA4The backup failed. Check the directory to which you are backing the database
-21470208910x80070FA5The name does not exist in the WINS database
-21470208900x80070FA6Replication with a nonconfigured partner is not allowed
-21470208460x80070FD2The version of the supplied content information is not supported
-21470208450x80070FD3The supplied content information is malformed
-21470208440x80070FD4The requested data cannot be found in local or peer caches
-21470208430x80070FD5No more data is available or required
-21470208420x80070FD6The supplied object has not been initialized
-21470208410x80070FD7The supplied object has already been initialized
-21470208400x80070FD8A shutdown operation is already in progress
-21470208390x80070FD9The supplied object has already been invalidated
-21470208380x80070FDAAn element already exists and was not replaced
-21470208370x80070FDBCan not cancel the requested operation as it has already been completed
-21470208360x80070FDCCan not perform the reqested operation because it has already been carried out
-21470208350x80070FDDAn operation accessed data beyond the bounds of valid data
-21470208340x80070FDEThe requested version is not supported
-21470208330x80070FDFA configuration value is invalid
-21470208320x80070FE0The SKU is not licensed
-21470208310x80070FE1PeerDist Service is still initializing and will be available shortly
-21470208300x80070FE2Communication with one or more computers will be temporarily blocked due to recent errors
-21470207960x80071004The 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
-21470206960x80071068The GUID passed was not recognized as valid by a WMI data provider
-21470206950x80071069The instance name passed was not recognized as valid by a WMI data provider
-21470206940x8007106AThe data item ID passed was not recognized as valid by a WMI data provider
-21470206930x8007106BThe WMI request could not be completed and should be retried
-21470206920x8007106CThe WMI data provider could not be located
-21470206910x8007106DThe WMI data provider references an instance set that has not been registered
-21470206900x8007106EThe WMI data block or event notification has already been enabled
-21470206890x8007106FThe WMI data block is no longer available
-21470206880x80071070The WMI data service is not available
-21470206870x80071071The WMI data provider failed to carry out the request
-21470206860x80071072The WMI MOF information is not valid
-21470206850x80071073The WMI registration information is not valid
-21470206840x80071074The WMI data block or event notification has already been disabled
-21470206830x80071075The WMI data item or data block is read only
-21470206820x80071076The WMI data item or data block could not be changed
-21470206460x8007109AThis operation is only valid in the context of an app container
-21470206450x8007109BThis application can only run in the context of an app container
-21470206440x8007109CThis functionality is not supported in the context of an app container
-21470206430x8007109DThe length of the SID supplied is not a valid length for app container SIDs
-21470205960x800710CCThe media identifier does not represent a valid medium
-21470205950x800710CDThe library identifier does not represent a valid library
-21470205940x800710CEThe media pool identifier does not represent a valid media pool
-21470205930x800710CFThe drive and medium are not compatible or exist in different libraries
-21470205920x800710D0The medium currently exists in an offline library and must be online to perform this operation
-21470205910x800710D1The operation cannot be performed on an offline library
-21470205900x800710D2The library, drive, or media pool is empty
-21470205890x800710D3The library, drive, or media pool must be empty to perform this operation
-21470205880x800710D4No media is currently available in this media pool or library
-21470205870x800710D5A resource required for this operation is disabled
-21470205860x800710D6The media identifier does not represent a valid cleaner
-21470205850x800710D7The drive cannot be cleaned or does not support cleaning
-21470205840x800710D8The object identifier does not represent a valid object
-21470205830x800710D9Unable to read from or write to the database
-21470205820x800710DAThe database is full
-21470205810x800710DBThe medium is not compatible with the device or media pool
-21470205800x800710DCThe resource required for this operation does not exist
-21470205790x800710DDThe operation identifier is not valid
-21470205780x800710DEThe media is not mounted or ready for use
-21470205770x800710DFThe device is not ready for use
-21470205760x800710E0The operator or administrator has refused the request
-21470205750x800710E1The drive identifier does not represent a valid drive
-21470205740x800710E2Library is full. No slot is available for use
-21470205730x800710E3The transport cannot access the medium
-21470205720x800710E4Unable to load the medium into the drive
-21470205710x800710E5Unable to retrieve the drive status
-21470205700x800710E6Unable to retrieve the slot status
-21470205690x800710E7Unable to retrieve status about the transport
-21470205680x800710E8Cannot use the transport because it is already in use
-21470205670x800710E9Unable to open or close the inject/eject port
-21470205660x800710EAUnable to eject the medium because it is in a drive
-21470205650x800710EBA cleaner slot is already reserved
-21470205640x800710ECA cleaner slot is not reserved
-21470205630x800710EDThe cleaner cartridge has performed the maximum number of drive cleanings
-21470205620x800710EEUnexpected on-medium identifier
-21470205610x800710EFThe last remaining item in this group or resource cannot be deleted
-21470205600x800710F0The message provided exceeds the maximum size allowed for this parameter
-21470205590x800710F1The volume contains system or paging files
-21470205580x800710F2The media type cannot be removed from this library since at least one drive in the library reports it can support this media type
-21470205570x800710F3This offline media cannot be mounted on this system since no enabled drives are present which can be used
-21470205560x800710F4A cleaner cartridge is present in the tape library
-21470205550x800710F5Cannot use the inject/eject port because it is not empty
-21470205540x800710F6Error
-21470205530x800710F7OK
-21470205520x800710F8Y
-21470205510x800710F9N
-21470205500x800710FAAny
-21470205490x800710FBA
-21470205480x800710FCP
-21470205470x800710FD(not found)
-21470205460x800710FEThis file is currently not available for use on this computer
-21470205450x800710FFThe remote storage service is not operational at this time
-21470205440x80071100The remote storage service encountered a media error
-21470205430x80071101Read
-21470205420x80071102Change
-21470205410x80071103Full
-21470205400x80071104Please type the password:
-21470205390x80071105Type the password for %1:
-21470205380x80071106Type a password for the user:
-21470205370x80071107Type the password for the shared resource:
-21470205360x80071108Type your password:
-21470205350x80071109Retype the password to confirm:
-21470205340x8007110AType the user's old password:
-21470205330x8007110BType the user's new password:
-21470205320x8007110CType your new password:
-21470205310x8007110DType the Replicator service password:
-21470205300x8007110EType your user name, or press ENTER if it is %1:
-21470205290x8007110FType the domain or server where you want to change a password, or press ENTER if it is for domain %1:
-21470205280x80071110Type your user name:
-21470205270x80071111Network statistics for \\%1
-21470205260x80071112Printing options for %1
-21470205250x80071113Communication-device queues accessing %1
-21470205240x80071114Print job detail
-21470205230x80071115Communication-device queues at \\%1
-21470205220x80071116Printers at %1
-21470205210x80071117Printers accessing %1
-21470205200x80071118Print jobs at %1:
-21470205190x80071119Shared resources at %1
-21470205180x8007111AThe following running services can be controlled:
-21470205170x8007111BStatistics are available for the following running services:
-21470205160x8007111CUser accounts for \\%1
-21470205150x8007111DThe syntax of this command is:
-21470205140x8007111EThe options of this command are:
-21470205130x8007111FPlease enter the name of the Primary Domain Controller:
-21470205120x80071120The string you have entered is too long. The maximum is %1, please reenter
-21470205110x80071121Sunday
-21470205100x80071122Monday
-21470205090x80071123Tuesday
-21470205080x80071124Wednesday
-21470205070x80071125Thursday
-21470205060x80071126The file or directory is not a reparse point
-21470205050x80071127The reparse point attribute cannot be set because it conflicts with an existing attribute
-21470205040x80071128The data present in the reparse point buffer is invalid
-21470205030x80071129The tag present in the reparse point buffer is invalid
-21470205020x8007112AThere is a mismatch between the tag specified in the request and the tag present in the reparse point
-21470205010x8007112BW
-21470205000x8007112CTh
-21470204990x8007112DF
-21470204980x8007112ES
-21470204970x8007112FSa
-21470204960x80071130Fast Cache data not found
-21470204950x80071131Fast Cache data expired
-21470204940x80071132Fast Cache data corrupt
-21470204930x80071133Fast Cache data has exceeded its max size and cannot be updated
-21470204920x80071134Fast Cache has been ReArmed and requires a reboot until it can be updated
-21470204910x80071135Aliases for \\%1
-21470204900x80071136Alias name
-21470204890x80071137Comment
-21470204880x80071138Members
-21470204860x8007113AUser Accounts for \\%1
-21470204850x8007113BUser name
-21470204840x8007113CFull Name
-21470204830x8007113DComment
-21470204820x8007113EUser's comment
-21470204810x8007113FParameters
-21470204800x80071140Country/region code
-21470204790x80071141Privilege level
-21470204780x80071142Operator privileges
-21470204770x80071143Account active
-21470204760x80071144Secure Boot detected that rollback of protected data has been attempted
-21470204750x80071145The value is protected by Secure Boot policy and cannot be modified or deleted
-21470204740x80071146The Secure Boot policy is invalid
-21470204730x80071147A new Secure Boot policy did not contain the current publisher on its update list
-21470204720x80071148The Secure Boot policy is either not signed or is signed by a non-trusted signer
-21470204710x80071149Secure Boot is not enabled on this machine
-21470204700x8007114ASecure Boot requires that certain files and drivers are not replaced by other files or drivers
-21470204690x8007114BLocal Group Memberships
-21470204680x8007114CDomain controller
-21470204670x8007114DLogon script
-21470204660x8007114ELast logon
-21470204650x8007114FGlobal Group memberships
-21470204640x80071150Logon hours allowed
-21470204630x80071151All
-21470204620x80071152None
-21470204610x80071153Daily %1 - %2
-21470204600x80071154Home directory
-21470204590x80071155Password required
-21470204580x80071156User may change password
-21470204570x80071157User profile
-21470204560x80071158The copy offload read operation is not supported by a filter
-21470204550x80071159The copy offload write operation is not supported by a filter
-21470204540x8007115AThe copy offload read operation is not supported for the file
-21470204530x8007115BThe copy offload write operation is not supported for the file
-21470204460x80071162Computer name
-21470204450x80071163User name
-21470204440x80071164Software version
-21470204430x80071165Workstation active on
-21470204420x80071166Windows NT root directory
-21470204410x80071167Workstation domain
-21470204400x80071168Logon domain
-21470204390x80071169Other domain(s)
-21470204380x8007116ACOM Open Timeout (sec)
-21470204370x8007116BCOM Send Count (byte)
-21470204360x8007116CCOM Send Timeout (msec)
-21470204350x8007116DDOS session print time-out (sec)
-21470204340x8007116EMaximum error log size (K)
-21470204330x8007116FMaximum cache memory (K)
-21470204320x80071170Number of network buffers
-21470204310x80071171Number of character buffers
-21470204300x80071172Size of network buffers
-21470204290x80071173Size of character buffers
-21470204280x80071174Full Computer name
-21470204270x80071175Workstation Domain DNS Name
-21470204260x80071176Windows 2002
-21470204150x80071181Server Name
-21470204140x80071182Server Comment
-21470204130x80071183Send administrative alerts to
-21470204120x80071184Software version
-21470204110x80071185Peer Server
-21470204100x80071186Windows NT
-21470204090x80071187Server Level
-21470204080x80071188Windows NT Server
-21470204070x80071189Server is active on
-21470204040x8007118CServer hidden
-21470203960x80071194Single Instance Storage is not available on this volume
-21470203900x8007119AMaximum Logged On Users
-21470203890x8007119BMaximum concurrent administrators
-21470203880x8007119CMaximum resources shared
-21470203870x8007119DMaximum connections to resources
-21470203860x8007119EMaximum open files on server
-21470203850x8007119FMaximum open files per session
-21470203840x800711A0Maximum file locks
-21470203760x800711A8Idle session time (min)
-21470203700x800711AEShare-level
-21470203690x800711AFUser-level
-21470203660x800711B2Unlimited Server
-21470203460x800711C6System Integrity detected that policy rollback has been attempted
-21470203450x800711C7This program was blocked by Device Guard because it violates the code integrity policy installed on this system
-21470203440x800711C8The System Integrity policy is invalid
-21470203430x800711C9The System Integrity policy is either not signed or is signed by a non-trusted signer
-21470203360x800711D0Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled
-21470203350x800711D1The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS
-21470203260x800711DAForce user logoff how long after time expires?:
-21470203250x800711DBLock out account after how many bad passwords?:
-21470203240x800711DCMinimum password age (days):
-21470203230x800711DDMaximum password age (days):
-21470203220x800711DEMinimum password length:
-21470203210x800711DFLength of password history maintained:
-21470203200x800711E0Computer role:
-21470203190x800711E1Primary Domain controller for workstation domain:
-21470203180x800711E2Lockout threshold:
-21470203170x800711E3Lockout duration (minutes):
-21470203160x800711E4Lockout observation window (minutes):
-21470202960x800711F8Statistics since
-21470202950x800711F9Sessions accepted
-21470202940x800711FASessions timed-out
-21470202930x800711FBSessions errored-out
-21470202920x800711FCKilobytes sent
-21470202910x800711FDKilobytes received
-21470202900x800711FEMean response time (msec)
-21470202890x800711FFNetwork errors
-21470202880x80071200Files accessed
-21470202870x80071201Print jobs spooled
-21470202860x80071202System errors
-21470202850x80071203Password violations
-21470202840x80071204Permission violations
-21470202830x80071205Communication devices accessed
-21470202820x80071206Sessions started
-21470202810x80071207Sessions reconnected
-21470202800x80071208Sessions starts failed
-21470202790x80071209Sessions disconnected
-21470202780x8007120ANetwork I/O's performed
-21470202770x8007120BFiles and pipes accessed
-21470202760x8007120CTimes buffers exhausted
-21470202750x8007120DBig buffers
-21470202740x8007120ERequest buffers
-21470202730x8007120FWorkstation Statistics for \\%1
-21470202720x80071210Server Statistics for \\%1
-21470202710x80071211Statistics since %1
-21470202700x80071212Connections made
-21470202690x80071213Connections failed
-21470202660x80071216Bytes received
-21470202650x80071217Server Message Blocks (SMBs) received
-21470202640x80071218Bytes transmitted
-21470202630x80071219Server Message Blocks (SMBs) transmitted
-21470202620x8007121ARead operations
-21470202610x8007121BWrite operations
-21470202600x8007121CRaw reads denied
-21470202590x8007121DRaw writes denied
-21470202580x8007121ENetwork errors
-21470202570x8007121FConnections made
-21470202560x80071220Reconnections made
-21470202550x80071221Server disconnects
-21470202540x80071222Sessions started
-21470202530x80071223Hung sessions
-21470202520x80071224Failed sessions
-21470202510x80071225Failed operations
-21470202500x80071226Use count
-21470202490x80071227Failed use count
-21470202460x8007122A%1 was deleted successfully
-21470202450x8007122B%1 was used successfully
-21470202440x8007122CThe message was successfully sent to %1
-21470202430x8007122DThe message name %1 was forwarded successfully
-21470202420x8007122EThe message name %1 was added successfully
-21470202410x8007122FThe message name forwarding was successfully canceled
-21470202400x80071230%1 was shared successfully
-21470202390x80071231The server %1 successfully logged you on as %2
-21470202380x80071232%1 was logged off successfully
-21470202370x80071233%1 was successfully removed from the list of shares the Server creates on startup
-21470202350x80071235The password was changed successfully
-21470202340x80071236%1 file(s) copied
-21470202330x80071237%1 file(s) moved
-21470202320x80071238The message was successfully sent to all users of the network
-21470202310x80071239The message was successfully sent to domain %1
-21470202300x8007123AThe message was successfully sent to all users of this server
-21470202290x8007123BThe message was successfully sent to group *%1
-21470202010x80071257Microsoft LAN Manager Version %1
-21470202000x80071258Windows NT Server
-21470201990x80071259Windows NT Workstation
-21470201980x8007125AMS-DOS Enhanced Workstation
-21470201970x8007125BCreated at %1
-21470201960x8007125CServer Name Remark
-21470201950x8007125DCannot enumerate servers in non-default compartment
-21470201940x8007125E(UNC)
-21470201930x8007125F
-21470201920x80071260Domain
-21470201910x80071261Resources on %1
-21470201900x80071262Invalid network provider. Available networks are:
-21470201860x80071266Disk
-21470201850x80071267Print
-21470201840x80071268Comm
-21470201830x80071269IPC
-21470201820x8007126AStatus Local Remote Network
-21470201810x8007126BOK
-21470201800x8007126CDormant
-21470201790x8007126DPaused
-21470201780x8007126EDisconnected
-21470201770x8007126FError
-21470201760x80071270Connecting
-21470201750x80071271Reconnecting
-21470201740x80071272Status
-21470201730x80071273Local name
-21470201720x80071274Remote name
-21470201710x80071275Resource type
-21470201700x80071276# Opens
-21470201690x80071277# Connections
-21470201680x80071278Unavailable
-21470201660x8007127AShare name Resource Remark
-21470201650x8007127BShare name
-21470201640x8007127CResource
-21470201630x8007127DSpooled
-21470201620x8007127EPermission
-21470201610x8007127FMaximum users
-21470201600x80071280No limit
-21470201590x80071281Users
-21470201580x80071282The share name entered may not be accessible from some MS-DOS workstations. Are you sure you want to use this share name? %1:
-21470201570x80071283Caching
-21470201560x80071284ID Path User name # Locks
-21470201550x80071285File ID
-21470201540x80071286Locks
-21470201530x80071287Permissions
-21470201520x80071288Share name
-21470201510x80071289Type
-21470201500x8007128AUsed as
-21470201490x8007128BComment
-21470201460x8007128EComputer User name Client Type Opens Idle time
-21470201450x8007128FComputer
-21470201440x80071290Sess time
-21470201430x80071291Idle time
-21470201420x80071292Share name Type # Opens
-21470201410x80071293Client type
-21470201400x80071294Guest logon
-21470201260x800712A2Manual caching of documents
-21470201250x800712A3Automatic caching of documents
-21470201240x800712A4Automatic caching of programs and documents
-21470201230x800712A5Manual caching of documents with BranchCache enabled
-21470201220x800712A6Caching disabled
-21470201210x800712A7Automatic
-21470201200x800712A8Manual
-21470201190x800712A9Documents
-21470201180x800712AAPrograms
-21470201170x800712ABBranchCache
-21470201160x800712ACNone
-21470200960x800712C0Name
-21470200950x800712C1Forwarded to
-21470200940x800712C2Forwarded to you from
-21470200930x800712C3Users of this server
-21470200920x800712C4Net Send has been interrupted by a Ctrl+Break from the user
-21470200860x800712CAName Job # Size Status
-21470200850x800712CBjobs
-21470200840x800712CCPrint
-21470200830x800712CDName
-21470200820x800712CEJob #
-21470200810x800712CFSize
-21470200800x800712D0Status
-21470200790x800712D1Separator file
-21470200780x800712D2Comment
-21470200770x800712D3Priority
-21470200760x800712D4Print after
-21470200750x800712D5Print until
-21470200740x800712D6Print processor
-21470200730x800712D7Additional info
-21470200720x800712D8Parameters
-21470200710x800712D9Print Devices
-21470200700x800712DAPrinter Active
-21470200690x800712DBPrinter held
-21470200680x800712DCPrinter error
-21470200670x800712DDPrinter being deleted
-21470200660x800712DEPrinter status unknown
-21470200560x800712E8Held until %1
-21470200550x800712E9Job #
-21470200540x800712EASubmitting user
-21470200530x800712EBNotify
-21470200520x800712ECJob data type
-21470200510x800712EDJob parameters
-21470200500x800712EEWaiting
-21470200490x800712EFHeld in queue
-21470200480x800712F0Spooling
-21470200470x800712F1Paused
-21470200460x800712F2Offline
-21470200450x800712F3Error
-21470200440x800712F4Out of paper
-21470200430x800712F5Intervention required
-21470200420x800712F6Printing
-21470200410x800712F7on
-21470200400x800712F8Paused on %1
-21470200390x800712F9Offline on %1
-21470200380x800712FAError on%1
-21470200370x800712FBOut of Paper on %1
-21470200360x800712FCCheck printer on %1
-21470200350x800712FDPrinting on %1
-21470200340x800712FEDriver
-21470199660x80071342User name Type Date
-21470199650x80071343Lockout
-21470199640x80071344Service
-21470199630x80071345Server
-21470199620x80071346Server started
-21470199610x80071347Server paused
-21470199600x80071348Server continued
-21470199590x80071349Server stopped
-21470199580x8007134ASession
-21470199570x8007134BLogon Guest
-21470199560x8007134CLogon User
-21470199550x8007134DLogon Administrator
-21470199540x8007134ELogoff normal
-21470199530x8007134FLogon
-21470199520x80071350Logoff error
-21470199510x80071351Logoff auto-disconnect
-21470199500x80071352Logoff administrator-disconnect
-21470199490x80071353Logoff forced by logon restrictions
-21470199480x80071354Service
-21470199470x80071355%1 Installed
-21470199460x80071356%1 Install Pending
-21470199450x80071357%1 Paused
-21470199440x80071358%1 Pause Pending
-21470199430x80071359%1 Continued
-21470199420x8007135A%1 Continue Pending
-21470199410x8007135B%1 Stopped
-21470199400x8007135C%1 Stop Pending
-21470199390x8007135DAccount
-21470199380x8007135EUser account %1 was modified
-21470199370x8007135FGroup account %1 was modified
-21470199360x80071360User account %1 was deleted
-21470199350x80071361Group account %1 was deleted
-21470199340x80071362User account %1 was added
-21470199330x80071363Group account %1 was added
-21470199320x80071364Account system settings were modified
-21470199310x80071365Logon restriction
-21470199300x80071366Limit exceeded: UNKNOWN
-21470199290x80071367Limit exceeded: Logon hours
-21470199280x80071368Limit exceeded: Account expired
-21470199270x80071369Limit exceeded: Workstation ID invalid
-21470199260x8007136ALimit exceeded: Account disabled
-21470199250x8007136BLimit exceeded: Account deleted
-21470199240x8007136CShare
-21470199230x8007136DUse %1
-21470199220x8007136EUnuse %1
-21470199210x8007136FUser's session disconnected %1
-21470199200x80071370Administrator stopped sharing resource %1
-21470199190x80071371User reached limit for %1
-21470199180x80071372Bad password
-21470199170x80071373Administrator privilege required
-21470199160x80071374Access
-21470199150x80071375%1 permissions added
-21470199140x80071376%1 permissions modified
-21470199130x80071377%1 permissions deleted
-21470199120x80071378Access denied
-21470199110x80071379Unknown
-21470199100x8007137AOther
-21470199090x8007137BDuration:
-21470199080x8007137CDuration: Not available
-21470199070x8007137DDuration: Less than one second
-21470199060x8007137E(none)
-21470199050x8007137FClosed %1
-21470199040x80071380Closed %1 (disconnected)
-21470199030x80071381Administrator closed %1
-21470199020x80071382Access ended
-21470199010x80071383Log on to network
-21470199000x80071384Logon denied
-21470198990x80071385Program Message Time
-21470198980x80071386Account locked due to %1 bad passwords
-21470198970x80071387Account unlocked by administrator
-21470198960x80071388Log off network
-21470198950x80071389The operation cannot be completed because other resources are dependent on this resource
-21470198940x8007138AThe cluster resource dependency cannot be found
-21470198930x8007138BThe cluster resource cannot be made dependent on the specified resource because it is already dependent
-21470198920x8007138CThe cluster resource is not online
-21470198910x8007138DA cluster node is not available for this operation
-21470198900x8007138EThe cluster resource is not available
-21470198890x8007138FThe cluster resource could not be found
-21470198880x80071390The cluster is being shut down
-21470198870x80071391A cluster node cannot be evicted from the cluster unless the node is down or it is the last node
-21470198860x80071392The object already exists
-21470198850x80071393The object is already in the list
-21470198840x80071394The cluster group is not available for any new requests
-21470198830x80071395The cluster group could not be found
-21470198820x80071396The operation could not be completed because the cluster group is not online
-21470198810x80071397The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource
-21470198800x80071398The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group
-21470198790x80071399The cluster resource could not be created in the specified resource monitor
-21470198780x8007139AThe cluster resource could not be brought online by the resource monitor
-21470198770x8007139BThe operation could not be completed because the cluster resource is online
-21470198760x8007139CThe cluster resource could not be deleted or brought offline because it is the quorum resource
-21470198750x8007139DThe cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource
-21470198740x8007139EThe cluster software is shutting down
-21470198730x8007139FThe group or resource is not in the correct state to perform the requested operation
-21470198720x800713A0The properties were stored but not all changes will take effect until the next time the resource is brought online
-21470198710x800713A1The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class
-21470198700x800713A2The cluster resource could not be deleted since it is a core resource
-21470198690x800713A3The quorum resource failed to come online
-21470198680x800713A4The quorum log could not be created or mounted successfully
-21470198670x800713A5The cluster log is corrupt
-21470198660x800713A6The record could not be written to the cluster log since it exceeds the maximum size
-21470198650x800713A7The cluster log exceeds its maximum size
-21470198640x800713A8No checkpoint record was found in the cluster log
-21470198630x800713A9The minimum required disk space needed for logging is not available
-21470198620x800713AAThe cluster node failed to take control of the quorum resource because the resource is owned by another active node
-21470198610x800713ABA cluster network is not available for this operation
-21470198600x800713ACA cluster node is not available for this operation
-21470198590x800713ADAll cluster nodes must be running to perform this operation
-21470198580x800713AEA cluster resource failed
-21470198570x800713AFThe cluster node is not valid
-21470198560x800713B0The cluster node already exists
-21470198550x800713B1A node is in the process of joining the cluster
-21470198540x800713B2The cluster node was not found
-21470198530x800713B3The cluster local node information was not found
-21470198520x800713B4The cluster network already exists
-21470198510x800713B5The cluster network was not found
-21470198500x800713B6The cluster network interface already exists
-21470198490x800713B7The cluster network interface was not found
-21470198480x800713B8The cluster request is not valid for this object
-21470198470x800713B9The cluster network provider is not valid
-21470198460x800713BAThe cluster node is down
-21470198450x800713BBThe cluster node is not reachable
-21470198440x800713BCThe cluster node is not a member of the cluster
-21470198430x800713BDA cluster join operation is not in progress
-21470198420x800713BEThe cluster network is not valid
-21470198410x800713BFMar
-21470198400x800713C0The cluster node is up
-21470198390x800713C1The cluster IP address is already in use
-21470198380x800713C2The cluster node is not paused
-21470198370x800713C3No cluster security context is available
-21470198360x800713C4The cluster network is not configured for internal cluster communication
-21470198350x800713C5The cluster node is already up
-21470198340x800713C6The cluster node is already down
-21470198330x800713C7The cluster network is already online
-21470198320x800713C8The cluster network is already offline
-21470198310x800713C9The cluster node is already a member of the cluster
-21470198300x800713CAThe 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
-21470198290x800713CBOne or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network
-21470198280x800713CCThis operation cannot currently be performed on the cluster group containing the quorum resource
-21470198270x800713CDThe cluster quorum resource is not allowed to have any dependencies
-21470198260x800713CEThe cluster node is paused
-21470198250x800713CFThe cluster resource cannot be brought online. The owner node cannot run this resource
-21470198240x800713D0The cluster node is not ready to perform the requested operation
-21470198230x800713D1The cluster node is shutting down
-21470198220x800713D2The cluster join operation was aborted
-21470198210x800713D3The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet
-21470198200x800713D4This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor
-21470198190x800713D5The system configuration changed during the cluster join or form operation. The join or form operation was aborted
-21470198180x800713D6The specified resource type was not found
-21470198170x800713D7The 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
-21470198160x800713D8The 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
-21470198150x800713D9No authentication package could be registered with the RPC server
-21470198140x800713DAYou cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group
-21470198130x800713DBThe 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
-21470198120x800713DCThe 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
-21470198110x800713DDA non locker code got a request to reserve the lock for making global updates
-21470198100x800713DEThe quorum disk could not be located by the cluster service
-21470198090x800713DFThe backed up cluster database is possibly corrupt
-21470198080x800713E0A DFS root already exists in this cluster node
-21470198070x800713E1An attempt to modify a resource property failed because it conflicts with another existing property
-21470198060x800713E2This operation is not supported on a cluster without an Administrator Access Point
-21470198050x800713E3Denmark
-21470198040x800713E4Sweden
-21470198030x800713E5Norway
-21470198020x800713E6Germany
-21470198010x800713E7Australia
-21470198000x800713E8Japan
-21470197990x800713E9Korea
-21470197980x800713EAChina (PRC)
-21470197970x800713EBTaiwan
-21470197960x800713ECAsia
-21470197950x800713EDPortugal
-21470197940x800713EEFinland
-21470197930x800713EFArabic
-21470197920x800713F0Hebrew
-21470197460x8007141EA power failure has occurred at %1. Please terminate all activity with this server
-21470197450x8007141FPower has been restored at %1. Normal operations have resumed
-21470197440x80071420The UPS service is starting shut down at %1
-21470197430x80071421The UPS service is about to perform final shut down
-21470197260x80071432The Workstation must be started with the NET START command
-21470197210x80071437Remote IPC
-21470197200x80071438Remote Admin
-21470197190x80071439Default share
-21470197180x8007143AUser Profiles
-21470196160x800714A0The password entered is longer than 14 characters. Computers with Windows prior to Windows 2000 will not be able to use this account. Do you want to continue this operation? %1:
-21470196150x800714A1%1 has a remembered connection to %2. Do you want to overwrite the remembered connection? %3:
-21470196140x800714A2Do you want to resume loading the profile? The command which caused the error will be ignored. %1:
-21470196120x800714A4Do you want to continue this operation? %1:
-21470196110x800714A5Do you want to add this? %1:
-21470196100x800714A6Do you want to continue this operation? %1:
-21470196090x800714A7Is it OK to start it? %1:
-21470196080x800714A8Do you want to start the Workstation service? %1:
-21470196070x800714A9Is it OK to continue disconnecting and force them closed? %1:
-21470196060x800714AAThe printer does not exist. Do you want to create it? %1:
-21470196050x800714ABNever
-21470196040x800714ACNever
-21470196030x800714ADNever
-21470196010x800714AFNET.HLP
-21470196000x800714B0NET.HLP
-21470195990x800714B1Deny
-21470195960x800714B4The network control block (NCB) request completed successfully. The NCB is the data
-21470195950x800714B5Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data
-21470195940x800714B6The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data
-21470195930x800714B7The command specified in the network control block (NCB) is illegal. The NCB is the data
-21470195920x800714B8The message correlator specified in the network control block (NCB) is invalid. The NCB is the data
-21470195910x800714B9A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data
-21470195900x800714BAAn incomplete network control block (NCB) message was received. The NCB is the data
-21470195890x800714BBThe buffer address specified in the network control block (NCB) is illegal. The NCB is the data
-21470195880x800714BCThe session number specified in the network control block (NCB) is not active. The NCB is the data
-21470195870x800714BDNo resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data
-21470195860x800714BEThe session specified in the network control block (NCB) was closed. The NCB is the data
-21470195850x800714BFThe network control block (NCB) command was canceled. The NCB is the data
-21470195840x800714C0The message segment specified in the network control block (NCB) is illogical. The NCB is the data
-21470195830x800714C1The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data
-21470195820x800714C2The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data
-21470195810x800714C3The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data
-21470195800x800714C4A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data
-21470195790x800714C5The local session table is full. The network control block (NCB) request was refused. The NCB is the data
-21470195780x800714C6A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data
-21470195770x800714C7The name number specified in the network control block (NCB) is illegal. The NCB is the data
-21470195760x800714C8The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data
-21470195750x800714C9The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data
-21470195740x800714CAThe name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data
-21470195730x800714CBThe name specified in the network control block (NCB) has been deleted. The NCB is the data
-21470195720x800714CCThe session specified in the network control block (NCB) ended abnormally. The NCB is the data
-21470195710x800714CDThe network protocol has detected two or more identical names on the network. The network control block (NCB) is the data
-21470195700x800714CEAn unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data
-21470195630x800714D5The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data
-21470195620x800714D6There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data
-21470195610x800714D7The adapter number specified in the network control block (NCB) is illegal. The NCB is the data
-21470195600x800714D8The network control block (NCB) command completed while a cancel was occurring. The NCB is the data
-21470195590x800714D9The name specified in the network control block (NCB) is reserved. The NCB is the data
-21470195580x800714DAThe network control block (NCB) command is not valid to cancel. The NCB is the data
-21470195450x800714E7There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data
-21470195440x800714E8There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data
-21470195420x800714EAThe maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data
-21470195400x800714ECThe requested resources are not available. The network control block (NCB) request was refused. The NCB is the data
-21470195320x800714F4A system error has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195310x800714F5A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195300x800714F6A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195290x800714F7A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195280x800714F8An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195270x800714F9An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195260x800714FAAn unrecognized network control block (NCB) return code was received. The NCB is the data
-21470195160x80071504A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data
-21470195150x80071505The network control block (NCB) command is still pending. The NCB is the data
-21470193960x8007157CThe update log on %1 is over 80%% capacity. The primary domain controller %2 is not retrieving the updates
-21470193950x8007157DThe update log on %1 is full, and no further updates can be added until the primary domain controller %2 retrieves the updates
-21470193940x8007157EThe time difference with the primary domain controller %1 exceeds the maximum allowed skew of %2 seconds
-21470193930x8007157FThe account of user %1 has been locked out on %2 due to %3 bad password attempts
-21470193920x80071580The %1 log file cannot be opened
-21470193910x80071581The %1 log file is corrupted and will be cleared
-21470193900x80071582The Application log file could not be opened. %1 will be used as the default log file
-21470193890x80071583The %1 Log is full. If this is the first time you have seen this message, take the following steps: 1. Click Start, click Run, type ""eventvwr"", and then click OK. 2. Click %1, click the Action menu, click Clear All Events, and then click No. If this dialog reappears, contact your helpdesk or system administrator
-21470193880x80071584The security database full synchronization has been initiated by the server %1
-21470193870x80071585Windows could not be started as configured. A previous working configuration was used instead
-21470193860x80071586The exception 0x%1 occurred in the application %2 at location 0x%3
-21470193850x80071587The servers %1 and %3 both claim to be an NT Domain Controller for the %2 domain. One of the servers should be removed from the domain because the servers have different security identifiers (SID)
-21470193840x80071588The server %1 and %2 both claim to be the primary domain controller for the %3 domain. One of the servers should be demoted or removed from the domain
-21470193830x80071589The computer %1 tried to connect to the server %2 using the trust relationship established by the %3 domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship
-21470193820x8007158AThe computer has rebooted from a bugcheck. The bugcheck was: %1. %2 A full dump was not saved
-21470193810x8007158BThe computer has rebooted from a bugcheck. The bugcheck was: %1. %2 A dump was saved in: %3
-21470193800x8007158CThe computer or domain %1 trusts domain %2. (This may be an indirect trust.) However, %1 and %2 have the same machine security identifier (SID). NT should be re-installed on either %1 or %2
-21470193790x8007158DThe computer or domain %1 trusts domain %2. (This may be an indirect trust.) However, %2 is not a valid name for a trusted domain. The name of the trusted domain should be changed to a valid name
-21470192960x800715E0Could not share the User or Script path
-21470192950x800715E1The password for this computer is not found in the local security database
-21470192940x800715E2An internal error occurred while accessing the computer's local or network security database
-21470191960x80071644The Netlogon service could not initialize the replication data structures successfully. The service was terminated. The following error occurred: %1
-21470191950x80071645The Netlogon service failed to update the domain trust list. The following error occurred: %1
-21470191940x80071646The Netlogon service could not add the RPC interface. The service was terminated. The following error occurred: %1
-21470191930x80071647The Netlogon service could not read a mailslot message from %1 due to the following error: %2
-21470191920x80071648The Netlogon service failed to register the service with the service controller. The service was terminated. The following error occurred: %1
-21470191910x80071649The change log cache maintained by the Netlogon service for %1 database changes is inconsistent. The Netlogon service is resetting the change log
-21470191900x8007164AThe Netlogon service could not create server share %1. The following error occurred: %2
-21470191890x8007164BThe down-level logon request for the user %1 from %2 failed
-21470191880x8007164CThe down-level logoff request for the user %1 from %2 failed
-21470191870x8007164DThe Windows NT or Windows 2000 %1 logon request for the user %2\%3 from %4 (via %5) failed
-21470191860x8007164EThe Windows NT or Windows 2000 %1 logoff request for the user %2\%3 from %4 failed
-21470191850x8007164FThe partial synchronization request from the server %1 completed successfully. %2 changes(s) has(have) been returned to the caller
-21470191840x80071650The partial synchronization request from the server %1 failed with the following error: %2
-21470191830x80071651The full synchronization request from the server %1 completed successfully. %2 object(s) has(have) been returned to the caller
-21470191820x80071652The full synchronization request from the server %1 failed with the following error: %2
-21470191810x80071653The partial synchronization replication of the %1 database from the primary domain controller %2 completed successfully. %3 change(s) is(are) applied to the database
-21470191800x80071654The partial synchronization replication of the %1 database from the primary domain controller %2 failed with the following error: %3
-21470191790x80071655The full synchronization replication of the %1 database from the primary domain controller %2 completed successfully
-21470191780x80071656The full synchronization replication of the %1 database from the primary domain controller %2 failed with the following error: %3
-21470191770x80071657This computer was not able to set up a secure session with a domain controller in domain %1 due to the following: %2 This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. ADDITIONAL INFO If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain
-21470191760x80071658The session setup to the Windows Domain Controller %1 for the domain %2 failed because the computer %3 does not have a local security database account
-21470191750x80071659The session setup to the Windows Domain Controller %1 for the domain %2 failed because the Domain Controller did not have an account %4 needed to set up the session by this computer %3. ADDITIONAL DATA If this computer is a member of or a Domain Controller in the specified domain, the aforementioned account is a computer account for this computer in the specified domain. Otherwise, the account is an interdomain trust account with the specified domain
-21470191740x8007165AThe 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
-21470191730x8007165BThe session setup from computer '%1' failed because the security database does not contain a trust account '%2' referenced by the specified computer. USER ACTION If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and '%2' is a legitimate machine account for the computer '%1' then '%1' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: If '%2' is a legitimate machine account for the computer '%1', then '%1' should be rejoined to the domain. If '%2' is a legitimate interdomain trust account, then the trust should be recreated. Otherwise, assuming that '%2' is not a legitimate account, the following action should be taken on '%1': If '%1' is a Domain Controller, then the trust associated with '%2' should be deleted. If '%1' is not a Domain Controller, it should be disjoined from the domain
-21470191720x8007165CCould not register control handler with service controller %1
-21470191710x8007165DCould not set service status with service controller %1
-21470191700x8007165ECould not find the computer name %1
-21470191690x8007165FCould not load %1 device driver
-21470191680x80071660Could not load any transport
-21470191670x80071661Replication of the %1 Domain Object %2"" from primary domain controller %3 failed with the following error: %4""
-21470191660x80071662Replication of the %1 Global Group %2"" from primary domain controller %3 failed with the following error: %4""
-21470191650x80071663Replication of the %1 Local Group %2"" from primary domain controller %3 failed with the following error: %4""
-21470191640x80071664Replication of the %1 User %2"" from primary domain controller %3 failed with the following error: %4""
-21470191630x80071665Replication of the %1 Policy Object %2"" from primary domain controller %3 failed with the following error: %4""
-21470191620x80071666Replication of the %1 Trusted Domain Object %2"" from primary domain controller %3 failed with the following error: %4""
-21470191610x80071667Replication of the %1 Account Object %2"" from primary domain controller %3 failed with the following error: %4""
-21470191600x80071668Replication of the %1 Secret %2"" from primary domain controller %3 failed with the following error: %4""
-21470191590x80071669The system returned the following unexpected error code: %1
-21470191580x8007166ANetlogon has detected two machine accounts for server %1"". The server can be either a Windows 2000 Server that is a member of the domain or the server can be a LAN Manager server with an account in the SERVERS global group. It cannot be both""
-21470191570x8007166BThis domain has more global groups than can be replicated to a LanMan BDC. Either delete some of your global groups or remove the LanMan BDCs from the domain
-21470191560x8007166CThe Browser driver returned the following error to Netlogon: %1
-21470191550x8007166DNetlogon could not register the %1<1B> name for the following reason: %2
-21470191540x8007166EService failed to retrieve messages needed to boot remote boot clients
-21470191530x8007166FService experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients
-21470191520x80071670Service experienced a severe system error and will shut itself down
-21470191510x80071671Client with computer name %1 failed to acknowledge receipt of the boot data. Remote boot of this client was not completed
-21470191500x80071672Client with computer name %1 was not booted due to an error in opening file %2
-21470191490x80071673Client with computer name %1 was not booted due to an error in reading file %2
-21470191480x80071674Client with computer name %1 was not booted due to insufficient memory at the remote boot server
-21470191470x80071675Client with computer name %1 will be booted without using checksums because checksum for file %2 could not be calculated
-21470191460x80071676Client with computer name %1 was not booted due to too many lines in file %2
-21470191450x80071677Client with computer name %1 was not booted because the boot block configuration file %2 for this client does not contain boot block line and/or loader line
-21470191440x80071678Client with computer name %1 was not booted due to a bad size of file %2
-21470191430x80071679Client with computer name %1 was not booted due to remote boot service internal error
-21470191420x8007167AClient with computer name %1 was not booted because file %2 has an invalid boot header
-21470191410x8007167BClient with computer name %1 was not booted due to network error
-21470191400x8007167CClient with adapter id %1 was not booted due to lack of resources
-21470191390x8007167DService experienced error copying file or directory %1
-21470191380x8007167EService experienced error deleting file or directory %1
-21470191370x8007167FService experienced error setting permissions on file or directory %1
-21470191360x80071680Service experienced error evaluating RPL configurations
-21470191350x80071681Service experienced error creating RPL profiles for all configurations
-21470191340x80071682Service experienced error accessing registry
-21470191330x80071683Service experienced error replacing possibly outdated RPLDISK.SYS
-21470191320x80071684Service experienced error adding security accounts or setting file permissions. These accounts are the RPLUSER local group and the user accounts for the individual RPL workstations
-21470191310x80071685Service failed to back up its database
-21470191300x80071686Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup
-21470191290x80071687Service failed to restore its database from the backup. Service will not start
-21470191280x80071688Service successfully restored its database from the backup
-21470191270x80071689Service failed to initialize from its restored database. Service will not start
-21470191260x8007168AThe 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, %2 tried to connect as either a DC in a trusted domain, a member workstation in domain %3, or as a server in domain %3. Use the Active Directory Users and Computers tool or Server Manager to remove the BDC account for %2
-21470191250x8007168BThe Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished
-21470191240x8007168CGlobal 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
-21470191230x8007168DThe following DNS server that is authoritative for the DNS domain controller locator records of this domain controller does not support dynamic DNS updates: DNS server IP address: %1 Returned Response Code (RCODE): %2 Returned Status Code: %3 USER ACTION Configure the DNS server to allow dynamic DNS updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database
-21470191220x8007168EThe dynamic registration of the DNS record '%1' failed on the following DNS server: DNS server IP address: %3 Returned Response Code (RCODE): %4 Returned Status Code: %5 For computers and users to locate this domain controller, this record must be registered in DNS. USER ACTION Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service. Or, you can manually add this record to DNS, but it is not recommended. ADDITIONAL DATA Error Value: %2
-21470191210x8007168FThe dynamic deletion of the DNS record '%1' failed on the following DNS server: DNS server IP address: %3 Returned Response Code (RCODE): %4 Returned Status Code: %5 USER ACTION To prevent remote computers from connecting unnecessarily to the domain controller, delete the record manually or troubleshoot the failure to dynamically delete the record. To learn more about debugging DNS, see Help and Support Center. ADDITIONAL DATA Error Value: %2
-21470191200x80071690Failed to create/open file %1 with the following error: %2
-21470191190x80071691Netlogon got the following error while trying to get the subnet to site mapping information from the DS: %1
-21470191180x80071692'%1' tried to determine its site by looking up its IP address ('%2') in the Configuration\Sites\Subnets container in the DS. No subnet matched the IP address. Consider adding a subnet object for this IP address
-21470191170x80071693The site name for this computer is '%1'. That site name is not a valid site name. A site name must be a valid DNS label. Rename the site to be a valid name
-21470191160x80071694The subnet object '%1' appears in the Configuration\Sites\Subnets container in the DS. The name is not syntactically valid. The valid syntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet number and yy is the number of bits in the subnet mask. Correct the name of the subnet object
-21470191150x80071695Dynamic registration or deletion of one or more DNS records associated with DNS domain '%1' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) 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 registration USER ACTION Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller
-21470191140x80071696Dynamic registration or deregistration of one or more DNS records failed with the following error: %1
-21470191130x80071697The session setup to the Windows Domain Controller %1 for the domain %2 is not responsive. The current RPC call from Netlogon on \\%3 to %1 has been cancelled
-21470191120x80071698Site '%2' does not have any Domain Controllers for domain '%3'. Domain Controllers in site '%1' have been automatically selected to cover site '%2' for domain '%3' based on configured Directory Server replication costs
-21470191110x80071699This Domain Controller no longer automatically covers site '%1' for domain '%2'
-21470191100x8007169ASite '%2' does not have any Global Catalog servers for forest '%3'. Global Catalog servers in site '%1' have been automatically selected to cover site '%2' for forest '%3' based on configured Directory Server replication costs
-21470191090x8007169BThis Global Catalog server no longer automatically covers site '%1' for forest '%2'
-21470191080x8007169CAttempt to update HOST Service Principal Names (SPNs) of the computer object in Active Directory failed. The updated values were '%1' and '%2'. The following error occurred: %3
-21470191070x8007169DAttempt to update DNS Host Name of the computer object in Active Directory failed. The updated value was '%1'. The following error occurred: %2
-21470191060x8007169ENo suitable Domain Controller is available for domain %1. An NT4 or older domain controller is available but it cannot be used for authentication purposes in the Windows 2000 or newer domain that this computer is a member of. The following error occurred: %2
-21470191050x8007169FThe domain of this computer, %1 has been downgraded from Windows 2000 or newer to Windows NT4 or older. The computer cannot function properly in this case for authentication purposes. This computer needs to rejoin the domain. The following error occurred: %2
-21470191040x800716A0Site '%2' does not have any LDAP servers for non-domain NC '%3'. LDAP servers in site '%1' have been automatically selected to cover site '%2' for non-domain NC '%3' based on configured Directory Server replication costs
-21470191030x800716A1This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'
-21470191020x800716A2Site '%2' is no longer manually configured in the registry as covered by this Domain Controller for domain '%3'. As a result, site '%2' does not have any Domain Controllers for domain '%3'. Domain Controllers in site '%1' have been automatically selected to cover site '%2' for domain '%3' based on configured Directory Server replication costs
-21470191010x800716A3This Domain Controller no longer automatically covers site '%1' for domain '%2'. However, site '%1' is still (manually) covered by this Domain Controller for domain '%2' since this site has been manually configured in the registry
-21470191000x800716A4Site '%2' is no longer manually configured in the registry as covered by this Global Catalog server for forest '%3'. As a result, site '%2' does not have any Global Catalog servers for forest '%3'. Global Catalog servers in site '%1' have been automatically selected to cover site '%2' for forest '%3' based on configured Directory Server replication costs
-21470190990x800716A5This Global Catalog server no longer automatically covers site '%1' for forest '%2'. However, site '%1' is still (manually) covered by this Global catalog for forest '%2' since this site has been manually configured in the registry
-21470190980x800716A6Site '%2' is no longer manually configured in the registry as covered by this LDAP server for non-domain NC '%3'. As a result, site '%2' does not have any LDAP servers for non-domain NC '%3'. LDAP servers in site '%1' have been automatically selected to cover site '%2' for non-domain NC '%3' based on configured Directory Server replication costs
-21470190970x800716A7This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'. However, site '%1' is still (manually) covered by this LDAP server for non-domain NC '%2' since this site has been manually configured in the registry
-21470190960x800716A8Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes of 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 name collision
-21470190950x800716A9Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes of the computer object in Active Directory failed because this computer account name, '%2' could not be mapped to the computer object on Domain Controller '%1'. Not having SPNs registered may result in authentication failures for this computer. Contact your domain administrator. The following technical information may be useful for the resolution of this failure: DsCrackNames status = 0x%3, crack error = 0x%4
-21470190940x800716AANone 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, it is generally recommended that the IP address of the Domain Controller (accessible to machines in its domain) maps to the Site which it services. If the above list of IP addresses is stable, consider moving this server to a site (or create one if it does not already exist) such that the above IP address maps to the selected site. This may require the creation of a new subnet object (whose range includes the above IP address) which maps to the selected site object
-21470190930x800716ABThe following error occurred while reading a parameter '%2' in the Netlogon %1 registry section: %3
-21470190920x800716ACThe 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, respectively. The value of 0x%6 has been assigned to this parameter
-21470190910x800716ADThe session setup from the computer %1 failed to authenticate. The following error occurred: %2
-21470190900x800716AEDynamic DNS updates have been manually disabled on this domain controller. USER ACTION Reconfigure this domain controller to use dynamic DNS updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database
-21470190890x800716AFDuring the past %1 hours there have been %2 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites. The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is %3 bytes. The current maximum size is %4 bytes. To set a different maximum size, create the above registry value and set the desired maximum size in bytes
-21470190880x800716B0The deregistration of some DNS domain controller locator records was aborted at the time of this domain controller demotion because the DNS deregistrations took too long. USER ACTION Manually delete the DNS records listed in the file '%SystemRoot%\System32\Config\Netlogon.dns' from the DNS database
-21470190870x800716B1The NetLogon service on this domain controller has been configured to use port %1 for incoming RPC connections over TCP/IP from remote machines. However, the following error occurred when Netlogon attempted to register this port with the RPC endpoint mapper service: %2 This will prevent the NetLogon service on remote machines from connecting to this domain controller over TCP/IP that may result in authentication problems. USER ACTION The specified port is configured via the Group Policy or via a registry value 'DcTcpipPort' under the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters' registry key; the value configured through the Group Policy takes precedence. If the port specified is in error, reset it to a correct value. You can also remove this configuration for the port in which case the port will be assigned dynamically by the endpoint mapper at the time the NetLogon service on remote machines makes RPC connections to this domain controller. After the misconfiguration is corrected, restart the NetLogon service on this machine and verify that this event log no longer appears
-21470190860x800716B2During the past %1 hours, this domain controller has received %2 connections from dual-stack IPv4/IPv6 clients with partial subnet-site mappings. A client has a partial subnet-site mapping if its IPv4 address is mapped to a site but its global IPv6 address is not mapped to a site, or vice versa. To ensure correct behavior for applications running on member computers and servers that rely on subnet-site mappings, dual-stack IPv4/IPv6 clients must have both IPv4 and global IPv6 addresses mapped to the same site. If a partially mapped client attempts to connect to this domain controller using its unmapped IP address, its mapped address is used for the client's site mapping. The log files %SystemRoot%\debug\netlogon.log or %SystemRoot%\debug\netlogon.bak contain the name, unmapped IP address and mapped IP address for each partially mapped client. The log files may also contain unrelated debugging information. To locate the information pertaining to partial-subnet mappings, search for lines that contain the text 'PARTIAL_CLIENT_SITE_MAPPING:'. The first word after this text is the client name. Following the client name is the client's unmapped IP address (the IP address that does not have a subnet-site mapping) and the client's mapped IP address, which was used to return site information. USER ACTION Use the Active Directory Sites and Services management console (MMC) snap-in to add the subnet mapping for the unmapped IP addresses to the same site being used by the mapped IP addresses. When adding site mappings for IPv6 addresses, you should use global IPv6 addresses and not for instance temporary, link-local or site-local IPv6 addresses. The default maximum size of the log files is %3 bytes. The current maximum size is %4 bytes. To set a different maximum size, create the following registry DWORD value to specify the maximum size in bytes: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize
-21470190850x800716B3The dynamic registration of the DNS record '%1' for the remote domain controller '%3' failed on the following DNS server: DNS server IP address: %4 Returned Response Code (RCODE): %5 Returned Status Code: %6 For computers and users to locate the domain controller '%3', this record must be registered in DNS. USER ACTION Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller '%3'. For help with determining and resolving the problem, see Help and Support for information about troubleshooting DNS. To initiate registration of the DNS records by the domain controller '%3', run 'nltest.exe /dsregdns' from the command prompt on the domain controller '%3' or restart the Net Logon service on the domain controller '%3'. Nltest.exe is a command line tool that is built into Windows Server. As a workaround, you can manually add this record to DNS, but it is not recommended because you then must manually update any changes it requires hereafter. ADDITIONAL DATA Error Value: %2
-21470190840x800716B4The dynamic deregistration of the DNS record '%1' for the remote domain controller '%3' failed on the following DNS server: DNS server IP address: %4 Returned Response Code (RCODE): %5 Returned Status Code: %6 USER ACTION To prevent remote computers from attempting to connect to the domain controller '%3' using an invalid record, delete the record '%1' manually or troubleshoot the root cause behind the dynamic deregistration failure. To learn more about troubleshooting DNS, see Help and Support. ADDITIONAL DATA Error Value: %2
-21470190830x800716B5The dynamic registration request for the DNS record '%1' has been rejected by the remote domain controller '%2'. Error: '%3' For computers and users to locate this domain controller, this record must be registered in DNS. If the problem persists, please contact your domain administrator
-21470190820x800716B6The dynamic deregistration request of the DNS record '%1' has been rejected by the remote domain controller '%2'. Error: '%3' To prevent remote computers from connecting unnecessarily to this domain controller, an administrator with sufficient privileges must manually delete the record on the DNS server that hosts it
-21470190810x800716B7The remoting of the dynamic update request for the local domain controller's DNS records through a secure session has failed with error '%1'. For other computers and member servers to locate this domain controller, the appropriate records must be registered in DNS. On this domain controller, look for events related to failure to set up a secure session to determine why the request is failing. If the problem persists, please contact your domain administrator
-21470190800x800716B8Netlogon 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, consolidated events will be logged about every %5 minutes. Please see http://support.microsoft.com/kb/2654097 for more information
-21470190790x800716B9Netlogon 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
-21470190780x800716BANetlogon took more than %1 seconds for an authentication request of account %2 in domain %3, through domain controller %4 in domain %5. This is the first warning. If the problem persists, a recurring event will be logged every %6 minutes. Please see http://support.microsoft.com/kb/2654097 for more information on this error
-21470190770x800716BBNetlogon 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
-21470190760x800716BCThe Netlogon service could not add the AuthZ RPC interface. The service was terminated. The following error occurred: '%1'
-21470190750x800716BDThe Netlogon service failed to initialize the AuthZ resource manager. The service was terminated. The following error occurred: '%1'
-21470190740x800716BEThe Netlogon service failed to initialize the security descriptor for the Netlogon RPC interface. The service was terminated. The following error occurred: '%1'
-21470190730x800716BFThe system successfully changed its password on the domain controller %1. This event is logged when the password for the computer account is changed by the system. It is logged on the computer that changed the password
-21470190720x800716C0The 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 service account is changed by the system. It is logged on the computer that changed the password
-21470190060x80071702An operation was attempted that is incompatible with the current membership state of the node
-21470190050x80071703The quorum resource does not contain the quorum log
-21470190040x80071704The membership engine requested shutdown of the cluster service on this node
-21470190030x80071705The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node
-21470190020x80071706A matching cluster network for the specified IP address could not be found
-21470190010x80071707The actual data type of the property did not match the expected data type of the property
-21470190000x80071708The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer
-21470189990x80071709Two or more parameter values specified for a resource's properties are in conflict
-21470189980x8007170AThis computer cannot be made a member of a cluster
-21470189970x8007170BThis computer cannot be made a member of a cluster because it does not have the correct version of Windows installed
-21470189960x8007170CA cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster
-21470189950x8007170DThe cluster configuration action has already been committed
-21470189940x8007170EThe cluster configuration action could not be rolled back
-21470189930x8007170FThe drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node
-21470189920x80071710One or more nodes in the cluster are running a version of Windows that does not support this operation
-21470189910x80071711The name of the corresponding computer account doesn't match the Network Name for this resource
-21470189900x80071712No network adapters are available
-21470189890x80071713The cluster node has been poisoned
-21470189880x80071714The group is unable to accept the request since it is moving to another node
-21470189870x80071715The resource type cannot accept the request since is too busy performing another operation
-21470189860x80071716The call to the cluster resource DLL timed out
-21470189850x80071717The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted
-21470189840x80071718An internal cluster error occurred. A call to an invalid function was attempted
-21470189830x80071719A parameter value is out of acceptable range
-21470189820x8007171AA network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required
-21470189810x8007171BAn invalid cluster registry operation was attempted
-21470189800x8007171CAn input string of characters is not properly terminated
-21470189790x8007171DAn input string of characters is not in a valid format for the data it represents
-21470189780x8007171EAn internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress
-21470189770x8007171FAn internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress
-21470189760x80071720An internal cluster error occurred. Data was not properly initialized
-21470189750x80071721An error occurred while reading from a stream of data. An unexpected number of bytes was returned
-21470189740x80071722An error occurred while writing to a stream of data. The required number of bytes could not be written
-21470189730x80071723An error occurred while deserializing a stream of cluster data
-21470189720x80071724One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s)
-21470189710x80071725A quorum of cluster nodes was not present to form a cluster
-21470189700x80071726The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address
-21470189690x80071727The 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
-21470189680x80071728Quorum resource cannot reside in the Available Storage group
-21470189670x80071729The dependencies for this resource are nested too deeply
-21470189660x8007172AThe call into the resource DLL raised an unhandled exception
-21470189650x8007172BThe RHS process failed to initialize
-21470189640x8007172CThe Failover Clustering feature is not installed on this node
-21470189630x8007172DThe resources must be online on the same node for this operation
-21470189620x8007172EA new node can not be added since this cluster is already at its maximum number of nodes
-21470189610x8007172FThis cluster can not be created since the specified number of nodes exceeds the maximum allowed limit
-21470189600x80071730An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain
-21470189590x80071731This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed
-21470189580x80071732File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes
-21470189570x80071733Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown. If it is the last node in the cluster, destroy cluster command should be used
-21470189560x80071734Only one instance of this resource type is allowed in the cluster
-21470189550x80071735Only one instance of this resource type is allowed per resource group
-21470189540x80071736The resource failed to come online due to the failure of one or more provider resources
-21470189530x80071737The resource has indicated that it cannot come online on any node
-21470189520x80071738The current operation cannot be performed on this group at this time
-21470189510x80071739The directory or file is not located on a cluster shared volume
-21470189500x8007173AThe Security Descriptor does not meet the requirements for a cluster
-21470189490x8007173BThere 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
-21470189480x8007173CThis group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation
-21470189470x8007173DBack up is in progress. Please wait for backup completion before trying this operation again
-21470189460x8007173EThe path does not belong to a cluster shared volume
-21470189450x8007173FThe cluster shared volume is not locally mounted on this node
-21470189440x80071740The cluster watchdog is terminating
-21470189430x80071741A resource vetoed a move between two nodes because they are incompatible
-21470189420x80071742The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements
-21470189410x80071743The resource vetoed the call
-21470189400x80071744Resource could not start or run because it could not reserve sufficient system resources
-21470189390x80071745A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation
-21470189380x80071746A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation
-21470189370x80071747The requested operation can not be completed because the group is queued for an operation
-21470189360x80071748The requested operation can not be completed because a resource has locked status
-21470189350x80071749The resource cannot move to another node because a cluster shared volume vetoed the operation
-21470189340x8007174AA node drain is already in progress
-21470189330x8007174BClustered storage is not connected to the node
-21470189320x8007174CThe 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
-21470189310x8007174DThe resource must be part of the Available Storage group to complete this action
-21470189300x8007174ECSVFS failed operation as volume is in redirected mode
-21470189290x8007174FCSVFS failed operation as volume is not in redirected mode
-21470189280x80071750Cluster properties cannot be returned at this time
-21470189270x80071751The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes
-21470189260x80071752The operation cannot be completed because the resource is in maintenance mode
-21470189250x80071753The operation cannot be completed because of cluster affinity conflicts
-21470189240x80071754The operation cannot be completed because the resource is a replica virtual machine
-21470189230x80071755The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version
-21470189220x80071756Updating the cluster functional level failed because the cluster is running in fix quorum mode. Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automatically switch out of fix quorum mode, or stop and restart the cluster without the FixQuorum switch. Once the cluster is out of fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level
-21470189210x80071757The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster by using the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features will be available
-21470189200x80071758The cluster is currently performing a version upgrade
-21470189190x80071759The cluster did not successfully complete the version upgrade
-21470189180x8007175AThe cluster node is in grace period
-21470189170x8007175BThe operation has failed because CSV volume was not able to recover in time specified on this file object
-21470189160x8007175CThe operation failed because the requested node is not currently part of active cluster membership
-21470189150x8007175DThe operation failed because the requested cluster resource is currently unmonitored
-21470189140x8007175EThe operation failed because a resource does not support running in an unmonitored state
-21470189130x8007175FThe operation cannot be completed because a resource participates in replication
-21470189120x80071760The operation failed because the requested cluster node has been isolated
-21470189110x80071761The operation failed because the requested cluster node has been quarantined
-21470189100x80071762The operation failed because the specified database update condition was not met
-21470189090x80071763A clustered space is in a degraded condition and the requested action cannot be completed at this time
-21470189080x80071764The operation failed because token delegation for this control is not supported
-21470188960x80071770The specified file could not be encrypted
-21470188950x80071771The specified file could not be decrypted
-21470188940x80071772The specified file is encrypted and the user does not have the ability to decrypt it
-21470188930x80071773There is no valid encryption recovery policy configured for this system
-21470188920x80071774The required encryption driver is not loaded for this system
-21470188910x80071775The file was encrypted with a different encryption driver than is currently loaded
-21470188900x80071776There are no EFS keys defined for the user
-21470188890x80071777The specified file is not encrypted
-21470188880x80071778The specified file is not in the defined EFS export format
-21470188870x80071779The specified file is read only
-21470188860x8007177AThe directory has been disabled for encryption
-21470188850x8007177BThe server is not trusted for remote encryption operation
-21470188840x8007177CRecovery policy configured for this system contains invalid recovery certificate
-21470188830x8007177DThe encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file
-21470188820x8007177EThe disk partition does not support file encryption
-21470188810x8007177FThis machine is disabled for file encryption
-21470188800x80071780A newer system is required to decrypt this encrypted file
-21470188790x80071781The remote server sent an invalid response for a file being opened with Client Side Encryption
-21470188780x80071782Client Side Encryption is not supported by the remote server even though it claims to support it
-21470188770x80071783File is encrypted and should be opened in Client Side Encryption mode
-21470188760x80071784A new encrypted file is being created and a $EFS needs to be provided
-21470188750x80071785The SMB client requested a CSE FSCTL on a non-CSE file
-21470188740x80071786The requested operation was blocked by policy. For more information, contact your system administrator
-21470187780x800717E6The list of servers for this workgroup is not currently available
-21470186960x80071838The 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
-21470182960x800719C8Log service encountered an invalid log sector
-21470182950x800719C9Log service encountered a log sector with invalid block parity
-21470182940x800719CALog service encountered a remapped log sector
-21470182930x800719CBLog service encountered a partial or incomplete log block
-21470182920x800719CCLog service encountered an attempt access data outside the active log range
-21470182910x800719CDLog service user marshalling buffers are exhausted
-21470182900x800719CELog service encountered an attempt read from a marshalling area with an invalid read context
-21470182890x800719CFLog service encountered an invalid log restart area
-21470182880x800719D0Log service encountered an invalid log block version
-21470182870x800719D1Log service encountered an invalid log block
-21470182860x800719D2Log service encountered an attempt to read the log with an invalid read mode
-21470182850x800719D3Log service encountered a log stream with no restart area
-21470182840x800719D4Log service encountered a corrupted metadata file
-21470182830x800719D5Log service encountered a metadata file that could not be created by the log file system
-21470182820x800719D6Log service encountered a metadata file with inconsistent data
-21470182810x800719D7Log service encountered an attempt to erroneous allocate or dispose reservation space
-21470182800x800719D8Log service cannot delete log file or file system container
-21470182790x800719D9Log service has reached the maximum allowable containers allocated to a log file
-21470182780x800719DALog service has attempted to read or write backward past the start of the log
-21470182770x800719DBLog policy could not be installed because a policy of the same type is already present
-21470182760x800719DCLog policy in question was not installed at the time of the request
-21470182750x800719DDThe installed set of policies on the log is invalid
-21470182740x800719DEA policy on the log in question prevented the operation from completing
-21470182730x800719DFLog space cannot be reclaimed because the log is pinned by the archive tail
-21470182720x800719E0Log record is not a record in the log file
-21470182710x800719E1Number of reserved log records or the adjustment of the number of reserved log records is invalid
-21470182700x800719E2Reserved log space or the adjustment of the log space is invalid
-21470182690x800719E3An new or existing archive tail or base of the active log is invalid
-21470182680x800719E4Log space is exhausted
-21470182670x800719E5The log could not be set to the requested size
-21470182660x800719E6Log is multiplexed, no direct writes to the physical log is allowed
-21470182650x800719E7The operation failed because the log is a dedicated log
-21470182640x800719E8The operation requires an archive context
-21470182630x800719E9Log archival is in progress
-21470182620x800719EAThe operation requires a non-ephemeral log, but the log is ephemeral
-21470182610x800719EBThe log must have at least two containers before it can be read from or written to
-21470182600x800719ECA log client has already registered on the stream
-21470182590x800719EDA log client has not been registered on the stream
-21470182580x800719EEA request has already been made to handle the log full condition
-21470182570x800719EFLog service encountered an error when attempting to read from a log container
-21470182560x800719F0Log service encountered an error when attempting to write to a log container
-21470182550x800719F1Log service encountered an error when attempting open a log container
-21470182540x800719F2Log service encountered an invalid container state when attempting a requested action
-21470182530x800719F3Log service is not in the correct state to perform a requested action
-21470182520x800719F4Log space cannot be reclaimed because the log is pinned
-21470182510x800719F5Log metadata flush failed
-21470182500x800719F6Security on the log and its containers is inconsistent
-21470182490x800719F7Records were appended to the log or reservation changes were made, but the log could not be flushed
-21470182480x800719F8The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available
-21470181960x80071A2CThe transaction handle associated with this operation is not valid
-21470181950x80071A2DThe requested operation was made in the context of a transaction that is no longer active
-21470181940x80071A2EThe requested operation is not valid on the Transaction object in its current state
-21470181930x80071A2FThe caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller
-21470181920x80071A30It is too late to perform the requested operation, since the Transaction has already been aborted
-21470181910x80071A31It is too late to perform the requested operation, since the Transaction has already been committed
-21470181900x80071A32The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported
-21470181890x80071A33The specified ResourceManager made no changes or updates to the resource under this transaction
-21470181880x80071A34The resource manager has attempted to prepare a transaction that it has not successfully joined
-21470181870x80071A35The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow
-21470181860x80071A36The RM tried to register a protocol that already exists
-21470181850x80071A37The attempt to propagate the Transaction failed
-21470181840x80071A38The requested propagation protocol was not registered as a CRM
-21470181830x80071A39The buffer passed in to PushTransaction or PullTransaction is not in a valid format
-21470181820x80071A3AThe current transaction context associated with the thread is not a valid handle to a transaction object
-21470181810x80071A3BThe specified Transaction object could not be opened, because it was not found
-21470181800x80071A3CThe specified ResourceManager object could not be opened, because it was not found
-21470181790x80071A3DThe specified Enlistment object could not be opened, because it was not found
-21470181780x80071A3EThe specified TransactionManager object could not be opened, because it was not found
-21470181770x80071A3FThe object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline
-21470181760x80071A40The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover
-21470181750x80071A41The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior
-21470181740x80071A42Because the associated transaction manager or resource manager has been closed, the handle is no longer valid
-21470181730x80071A43The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask
-21470181720x80071A44The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long
-21470181710x80071A45Implicit transaction are not supported
-21470181700x80071A46The kernel transaction manager had to abort or forget the transaction because it blocked forward progress
-21470181690x80071A47The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file
-21470181680x80071A48This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again
-21470181670x80071A49The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed
-21470181660x80071A4AThe transaction does not have a superior enlistment
-21470181650x80071A4BThe attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data
-21470180960x80071A90The function attempted to use a name that is reserved for use by another transaction
-21470180950x80071A91Transaction support within the specified resource manager is not started or was shut down due to an error
-21470180940x80071A92The metadata of the RM has been corrupted. The RM will not function
-21470180930x80071A93The specified directory does not contain a resource manager
-21470180910x80071A95The remote server or share does not support transacted file operations
-21470180900x80071A96The requested log size is invalid
-21470180890x80071A97The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback
-21470180880x80071A98The specified file miniversion was not found for this transacted file open
-21470180870x80071A99The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback
-21470180860x80071A9AA miniversion may only be opened in the context of the transaction that created it
-21470180850x80071A9BIt is not possible to open a miniversion with modify access
-21470180840x80071A9CIt is not possible to create any more miniversions for this stream
-21470180820x80071A9EThe remote server sent mismatching version number or Fid for a file opened with transactions
-21470180810x80071A9FThe 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
-21470180800x80071AA0There is no transaction metadata on the file
-21470180790x80071AA1The log data is corrupt
-21470180780x80071AA2The file can't be recovered because there is a handle still open on it
-21470180770x80071AA3The transaction outcome is unavailable because the resource manager responsible for it has disconnected
-21470180760x80071AA4The request was rejected because the enlistment in question is not a superior enlistment
-21470180750x80071AA5The transactional resource manager is already consistent. Recovery is not needed
-21470180740x80071AA6The transactional resource manager has already been started
-21470180730x80071AA7The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction
-21470180720x80071AA8The operation cannot be performed because another transaction is depending on the fact that this property will not change
-21470180710x80071AA9The operation would involve a single file with two transactional resource managers and is therefore not allowed
-21470180700x80071AAAThe $Txf directory must be empty for this operation to succeed
-21470180690x80071AABThe operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed
-21470180680x80071AACThe operation could not be completed because the transaction manager does not have a log
-21470180670x80071AADA rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution
-21470180660x80071AAEThe transactional metadata attribute on the file or directory is corrupt and unreadable
-21470180650x80071AAFThe encryption operation could not be completed because a transaction is active
-21470180640x80071AB0This object is not allowed to be opened in a transaction
-21470180630x80071AB1An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log
-21470180620x80071AB2Memory mapping (creating a mapped section) a remote file under a transaction is not supported
-21470180610x80071AB3Transaction metadata is already present on this file and cannot be superseded
-21470180600x80071AB4A transaction scope could not be entered because the scope handler has not been initialized
-21470180590x80071AB5Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it
-21470180580x80071AB6This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader
-21470180570x80071AB7The request to thaw frozen transactions was ignored because transactions had not previously been frozen
-21470180560x80071AB8Transactions cannot be frozen because a freeze is already in progress
-21470180550x80071AB9The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot
-21470180540x80071ABAThe savepoint operation failed because files are open on the transaction. This is not permitted
-21470180530x80071ABBWindows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred
-21470180520x80071ABCThe sparse operation could not be completed because a transaction is active on the file
-21470180510x80071ABDThe 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
-21470180500x80071ABEI/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data
-21470180490x80071ABFThe transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources
-21470180480x80071AC0The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down
-21470180470x80071AC1The operation could not be completed due to bad clusters on disk
-21470180460x80071AC2The compression operation could not be completed because a transaction is active on the file
-21470180450x80071AC3The operation could not be completed because the volume is dirty. Please run chkdsk and try again
-21470180440x80071AC4The link tracking operation could not be completed because a transaction is active
-21470180430x80071AC5This operation cannot be performed in a transaction
-21470180420x80071AC6The 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
-21470180410x80071AC7The specified operation could not be performed because the resource manager is not enlisted in the transaction
-21470178950x80071B59The specified session name is invalid
-21470178940x80071B5AThe specified protocol driver is invalid
-21470178930x80071B5BThe specified protocol driver was not found in the system path
-21470178920x80071B5CThe specified terminal connection driver was not found in the system path
-21470178910x80071B5DA registry key for event logging could not be created for this session
-21470178900x80071B5EA service with the same name already exists on the system
-21470178890x80071B5FA close operation is pending on the session
-21470178880x80071B60There are no free output buffers available
-21470178870x80071B61The MODEM.INF file was not found
-21470178860x80071B62The modem name was not found in MODEM.INF
-21470178850x80071B63The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem
-21470178840x80071B64The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on
-21470178830x80071B65Carrier detect has failed or carrier has been dropped due to disconnect
-21470178820x80071B66Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional
-21470178810x80071B67Busy signal detected at remote site on callback
-21470178800x80071B68Voice detected at remote site on callback
-21470178790x80071B69Transport driver error
-21470178740x80071B6EThe specified session cannot be found
-21470178730x80071B6FThe specified session name is already in use
-21470178720x80071B70The 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
-21470178710x80071B71An attempt has been made to connect to a session whose video mode is not supported by the current client
-21470178610x80071B7BThe application attempted to enable DOS graphics mode. DOS graphics mode is not supported
-21470178590x80071B7DYour interactive logon privilege has been disabled. Please contact your administrator
-21470178580x80071B7EThe 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
-21470178560x80071B80The client failed to respond to the server connect message
-21470178550x80071B81Disconnecting the console session is not supported
-21470178540x80071B82Reconnecting a disconnected session to the console is not supported
-21470178520x80071B84The request to control another session remotely was denied
-21470178510x80071B85The requested session access is denied
-21470178470x80071B89The specified terminal connection driver is invalid
-21470178460x80071B8AThe requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on
-21470178450x80071B8BThe requested session is not configured to allow remote control
-21470178440x80071B8CYour 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
-21470178430x80071B8DYour 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
-21470178420x80071B8EThe number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator
-21470178410x80071B8FThe client you are using is not licensed to use this system. Your logon request is denied
-21470178400x80071B90The system license has expired. Your logon request is denied
-21470178390x80071B91Remote control could not be terminated because the specified session is not currently being remotely controlled
-21470178380x80071B92The 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
-21470178370x80071B93Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared
-21470178360x80071B94Remote logins are currently disabled
-21470178350x80071B95You do not have the proper encryption level to access this Session
-21470178340x80071B96The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer
-21470178330x80071B97The user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\%s and have them log off
-21470178320x80071B98Unable to log you on because of an account restriction
-21470178310x80071B99The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client
-21470178300x80071B9AThe Client Drive Mapping Service Has Connected on Terminal Connection
-21470178290x80071B9BThe Client Drive Mapping Service Has Disconnected on Terminal Connection
-21470178280x80071B9CThe Terminal Server security layer detected an error in the protocol stream and has disconnected the client
-21470178270x80071B9DThe target session is incompatible with the current session
-21470178260x80071B9EWindows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance
-21470168950x80071F41The file replication service API was called incorrectly
-21470168940x80071F42The file replication service cannot be started
-21470168930x80071F43The file replication service cannot be stopped
-21470168920x80071F44The file replication service API terminated the request. The event log may have more information
-21470168910x80071F45The file replication service terminated the request. The event log may have more information
-21470168900x80071F46The file replication service cannot be contacted. The event log may have more information
-21470168890x80071F47The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information
-21470168880x80071F48The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information
-21470168870x80071F49The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information
-21470168860x80071F4AThe file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information
-21470168850x80071F4BThe file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information
-21470168840x80071F4CThe file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information
-21470168830x80071F4DThe file replication service cannot populate the system volume because of an internal error. The event log may have more information
-21470168820x80071F4EThe file replication service cannot populate the system volume because of an internal timeout. The event log may have more information
-21470168810x80071F4FThe file replication service cannot process the request. The system volume is busy with a previous request
-21470168800x80071F50The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information
-21470168790x80071F51The file replication service detected an invalid parameter
-21470166960x80072008An error occurred while installing the directory service. For more information, see the event log
-21470166950x80072009The directory service evaluated group memberships locally
-21470166940x8007200AThe specified directory service attribute or value does not exist
-21470166930x8007200BThe attribute syntax specified to the directory service is invalid
-21470166920x8007200CThe attribute type specified to the directory service is not defined
-21470166910x8007200DThe specified directory service attribute or value already exists
-21470166900x8007200EThe directory service is busy
-21470166890x8007200FThe directory service is unavailable
-21470166880x80072010The directory service was unable to allocate a relative identifier
-21470166870x80072011The directory service has exhausted the pool of relative identifiers
-21470166860x80072012The requested operation could not be performed because the directory service is not the master for that type of operation
-21470166850x80072013The directory service was unable to initialize the subsystem that allocates relative identifiers
-21470166840x80072014The requested operation did not satisfy one or more constraints associated with the class of the object
-21470166830x80072015The directory service can perform the requested operation only on a leaf object
-21470166820x80072016The directory service cannot perform the requested operation on the RDN attribute of an object
-21470166810x80072017The directory service detected an attempt to modify the object class of an object
-21470166800x80072018The requested cross-domain move operation could not be performed
-21470166790x80072019Unable to contact the global catalog server
-21470166780x8007201AThe policy object is shared and can only be modified at the root
-21470166770x8007201BThe policy object does not exist
-21470166760x8007201CThe requested policy information is only in the directory service
-21470166750x8007201DA domain controller promotion is currently active
-21470166740x8007201EA domain controller promotion is not currently active
-21470166720x80072020An operations error occurred
-21470166710x80072021A protocol error occurred
-21470166700x80072022The time limit for this request was exceeded
-21470166690x80072023The size limit for this request was exceeded
-21470166680x80072024The administrative limit for this request was exceeded
-21470166670x80072025The compare response was false
-21470166660x80072026The compare response was true
-21470166650x80072027The requested authentication method is not supported by the server
-21470166640x80072028A more secure authentication method is required for this server
-21470166630x80072029Inappropriate authentication
-21470166620x8007202AThe authentication mechanism is unknown
-21470166610x8007202BA referral was returned from the server
-21470166600x8007202CThe server does not support the requested critical extension
-21470166590x8007202DThis request requires a secure connection
-21470166580x8007202EInappropriate matching
-21470166570x8007202FA constraint violation occurred
-21470166560x80072030There is no such object on the server
-21470166550x80072031There is an alias problem
-21470166540x80072032An invalid dn syntax has been specified
-21470166530x80072033The object is a leaf object
-21470166520x80072034There is an alias dereferencing problem
-21470166510x80072035The server is unwilling to process the request
-21470166500x80072036A loop has been detected
-21470166490x80072037There is a naming violation
-21470166480x80072038The result set is too large
-21470166470x80072039The operation affects multiple DSAs
-21470166460x8007203AThe server is not operational
-21470166450x8007203BA local error has occurred
-21470166440x8007203CAn encoding error has occurred
-21470166430x8007203DA decoding error has occurred
-21470166420x8007203EThe search filter cannot be recognized
-21470166410x8007203FOne or more parameters are illegal
-21470166400x80072040The specified method is not supported
-21470166390x80072041No results were returned
-21470166380x80072042The specified control is not supported by the server
-21470166370x80072043A referral loop was detected by the client
-21470166360x80072044The preset referral limit was exceeded
-21470166350x80072045The search requires a SORT control
-21470166340x80072046The search results exceed the offset range specified
-21470166330x80072047The 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
-21470165950x8007206DThe root object must be the head of a naming context. The root object cannot have an instantiated parent
-21470165940x8007206EThe add replica operation cannot be performed. The naming context must be writeable in order to create the replica
-21470165930x8007206FA reference to an attribute that is not defined in the schema occurred
-21470165920x80072070The maximum size of an object has been exceeded
-21470165910x80072071An attempt was made to add an object to the directory with a name that is already in use
-21470165900x80072072An attempt was made to add an object of a class that does not have an RDN defined in the schema
-21470165890x80072073An attempt was made to add an object using an RDN that is not the RDN defined in the schema
-21470165880x80072074None of the requested attributes were found on the objects
-21470165870x80072075The user buffer is too small
-21470165860x80072076The attribute specified in the operation is not present on the object
-21470165850x80072077Illegal modify operation. Some aspect of the modification is not permitted
-21470165840x80072078The specified object is too large
-21470165830x80072079The specified instance type is not valid
-21470165820x8007207AThe operation must be performed at a master DSA
-21470165810x8007207BThe object class attribute must be specified
-21470165800x8007207CA required attribute is missing
-21470165790x8007207DAn attempt was made to modify an object to include an attribute that is not legal for its class
-21470165780x8007207EThe specified attribute is already present on the object
-21470165760x80072080The specified attribute is not present, or has no values
-21470165750x80072081Multiple values were specified for an attribute that can have only one value
-21470165740x80072082A value for the attribute was not in the acceptable range of values
-21470165730x80072083The specified value already exists
-21470165720x80072084The attribute cannot be removed because it is not present on the object
-21470165710x80072085The attribute value cannot be removed because it is not present on the object
-21470165700x80072086The specified root object cannot be a subref
-21470165690x80072087Chaining is not permitted
-21470165680x80072088Chained evaluation is not permitted
-21470165670x80072089The operation could not be performed because the object's parent is either uninstantiated or deleted
-21470165660x8007208AHaving a parent that is an alias is not permitted. Aliases are leaf objects
-21470165650x8007208BThe object and parent must be of the same type, either both masters or both replicas
-21470165640x8007208CThe operation cannot be performed because child objects exist. This operation can only be performed on a leaf object
-21470165630x8007208DDirectory object not found
-21470165620x8007208EThe aliased object is missing
-21470165610x8007208FThe object name has bad syntax
-21470165600x80072090It is not permitted for an alias to refer to another alias
-21470165590x80072091The alias cannot be dereferenced
-21470165580x80072092The operation is out of scope
-21470165570x80072093The operation cannot continue because the object is in the process of being removed
-21470165560x80072094The DSA object cannot be deleted
-21470165550x80072095A directory service error has occurred
-21470165540x80072096The operation can only be performed on an internal master DSA object
-21470165530x80072097The object must be of class DSA
-21470165520x80072098Insufficient access rights to perform the operation
-21470165510x80072099The object cannot be added because the parent is not on the list of possible superiors
-21470165500x8007209AAccess to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM)
-21470165490x8007209BThe name has too many parts
-21470165480x8007209CThe name is too long
-21470165470x8007209DThe name value is too long
-21470165460x8007209EThe directory service encountered an error parsing a name
-21470165450x8007209FThe directory service cannot get the attribute type for a name
-21470165440x800720A0The name does not identify an object; the name identifies a phantom
-21470165430x800720A1The security descriptor is too short
-21470165420x800720A2The security descriptor is invalid
-21470165410x800720A3Failed to create name for deleted object
-21470165400x800720A4The parent of a new subref must exist
-21470165390x800720A5The object must be a naming context
-21470165380x800720A6It is not permitted to add an attribute which is owned by the system
-21470165370x800720A7The class of the object must be structural; you cannot instantiate an abstract class
-21470165360x800720A8The schema object could not be found
-21470165350x800720A9A local object with this GUID (dead or alive) already exists
-21470165340x800720AAThe operation cannot be performed on a back link
-21470165330x800720ABThe cross reference for the specified naming context could not be found
-21470165320x800720ACThe operation could not be performed because the directory service is shutting down
-21470165310x800720ADThe directory service request is invalid
-21470165300x800720AEThe role owner attribute could not be read
-21470165290x800720AFThe requested FSMO operation failed. The current FSMO holder could not be contacted
-21470165280x800720B0Modification of a DN across a naming context is not permitted
-21470165270x800720B1The attribute cannot be modified because it is owned by the system
-21470165260x800720B2Only the replicator can perform this function
-21470165250x800720B3The specified class is not defined
-21470165240x800720B4The specified class is not a subclass
-21470165230x800720B5The name reference is invalid
-21470165220x800720B6A cross reference already exists
-21470165210x800720B7It is not permitted to delete a master cross reference
-21470165200x800720B8Subtree notifications are only supported on NC heads
-21470165190x800720B9Notification filter is too complex
-21470165180x800720BASchema update failed: duplicate RDN
-21470165170x800720BBSchema update failed: duplicate OID
-21470165160x800720BCSchema update failed: duplicate MAPI identifier
-21470165150x800720BDSchema update failed: duplicate schema-id GUID
-21470165140x800720BESchema update failed: duplicate LDAP display name
-21470165130x800720BFSchema update failed: range-lower less than range upper
-21470165120x800720C0Schema update failed: syntax mismatch
-21470165110x800720C1Schema deletion failed: attribute is used in must-contain
-21470165100x800720C2Schema deletion failed: attribute is used in may-contain
-21470165090x800720C3Schema update failed: attribute in may-contain does not exist
-21470165080x800720C4Schema update failed: attribute in must-contain does not exist
-21470165070x800720C5Schema update failed: class in aux-class list does not exist or is not an auxiliary class
-21470165060x800720C6Schema update failed: class in poss-superiors does not exist
-21470165050x800720C7Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules
-21470165040x800720C8Schema update failed: Rdn-Att-Id has wrong syntax
-21470165030x800720C9Schema deletion failed: class is used as auxiliary class
-21470165020x800720CASchema deletion failed: class is used as sub class
-21470165010x800720CBSchema deletion failed: class is used as poss superior
-21470165000x800720CCSchema update failed in recalculating validation cache
-21470164990x800720CDThe tree deletion is not finished. The request must be made again to continue deleting the tree
-21470164980x800720CEThe requested delete operation could not be performed
-21470164970x800720CFCannot read the governs class identifier for the schema record
-21470164960x800720D0The attribute schema has bad syntax
-21470164950x800720D1The attribute could not be cached
-21470164940x800720D2The class could not be cached
-21470164930x800720D3The attribute could not be removed from the cache
-21470164920x800720D4The class could not be removed from the cache
-21470164910x800720D5The distinguished name attribute could not be read
-21470164900x800720D6No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest
-21470164890x800720D7The instance type attribute could not be retrieved
-21470164880x800720D8An internal error has occurred
-21470164870x800720D9A database error has occurred
-21470164860x800720DAThe attribute GOVERNSID is missing
-21470164850x800720DBAn expected attribute is missing
-21470164840x800720DCThe specified naming context is missing a cross reference
-21470164830x800720DDA security checking error has occurred
-21470164820x800720DEThe schema is not loaded
-21470164810x800720DFSchema allocation failed. Please check if the machine is running low on memory
-21470164800x800720E0Failed to obtain the required syntax for the attribute schema
-21470164790x800720E1The 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
-21470164780x800720E2The replication operation failed because of a schema mismatch between the servers involved
-21470164770x800720E3The DSA object could not be found
-21470164760x800720E4The naming context could not be found
-21470164750x800720E5The naming context could not be found in the cache
-21470164740x800720E6The child object could not be retrieved
-21470164730x800720E7The modification was not permitted for security reasons
-21470164720x800720E8The operation cannot replace the hidden record
-21470164710x800720E9The hierarchy file is invalid
-21470164700x800720EAThe attempt to build the hierarchy table failed
-21470164690x800720EBThe directory configuration parameter is missing from the registry
-21470164680x800720ECThe attempt to count the address book indices failed
-21470164670x800720EDThe allocation of the hierarchy table failed
-21470164660x800720EEThe directory service encountered an internal failure
-21470164650x800720EFThe directory service encountered an unknown failure
-21470164640x800720F0A root object requires a class of 'top'
-21470164630x800720F1This directory server is shutting down, and cannot take ownership of new floating single-master operation roles
-21470164620x800720F2The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles
-21470164610x800720F3The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers
-21470164600x800720F4The replication operation failed
-21470164590x800720F5An invalid parameter was specified for this replication operation
-21470164580x800720F6The directory service is too busy to complete the replication operation at this time
-21470164570x800720F7The distinguished name specified for this replication operation is invalid
-21470164560x800720F8The naming context specified for this replication operation is invalid
-21470164550x800720F9The distinguished name specified for this replication operation already exists
-21470164540x800720FAThe replication system encountered an internal error
-21470164530x800720FBThe replication operation encountered a database inconsistency
-21470164520x800720FCThe server specified for this replication operation could not be contacted
-21470164510x800720FDThe replication operation encountered an object with an invalid instance type
-21470164500x800720FEThe replication operation failed to allocate memory
-21470164490x800720FFThe replication operation encountered an error with the mail system
-21470164480x80072100The replication reference information for the target server already exists
-21470164470x80072101The replication reference information for the target server does not exist
-21470164460x80072102The naming context cannot be removed because it is replicated to another server
-21470164450x80072103The replication operation encountered a database error
-21470164440x80072104The naming context is in the process of being removed or is not replicated from the specified server
-21470164430x80072105Replication access was denied
-21470164420x80072106The requested operation is not supported by this version of the directory service
-21470164410x80072107The replication remote procedure call was cancelled
-21470164400x80072108The source server is currently rejecting replication requests
-21470164390x80072109The destination server is currently rejecting replication requests
-21470164380x8007210AThe replication operation failed due to a collision of object names
-21470164370x8007210BThe replication source has been reinstalled
-21470164360x8007210CThe replication operation failed because a required parent object is missing
-21470164350x8007210DThe replication operation was preempted
-21470164340x8007210EThe replication synchronization attempt was abandoned because of a lack of updates
-21470164330x8007210FThe replication operation was terminated because the system is shutting down
-21470164320x80072110Synchronization 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
-21470164310x80072111The replication synchronization attempt failed because a master replica attempted to sync from a partial replica
-21470164300x80072112The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation
-21470164290x80072113The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer
-21470164280x80072114Schema update failed: An attribute with the same link identifier already exists
-21470164270x80072115Name translation: Generic processing error
-21470164260x80072116Name translation: Could not find the name or insufficient right to see name
-21470164250x80072117Name translation: Input name mapped to more than one output name
-21470164240x80072118Name translation: Input name found, but not the associated output format
-21470164230x80072119Name translation: Unable to resolve completely, only the domain was found
-21470164220x8007211AName translation: Unable to perform purely syntactical mapping at the client without going out to the wire
-21470164210x8007211BModification of a constructed attribute is not allowed
-21470164200x8007211CThe OM-Object-Class specified is incorrect for an attribute with the specified syntax
-21470164190x8007211DThe replication request has been posted; waiting for reply
-21470164180x8007211EThe requested operation requires a directory service, and none was available
-21470164170x8007211FThe LDAP display name of the class or attribute contains non-ASCII characters
-21470164160x80072120The requested search operation is only supported for base searches
-21470164150x80072121The search failed to retrieve attributes from the database
-21470164140x80072122The schema update operation tried to add a backward link attribute that has no corresponding forward link
-21470164130x80072123Source 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
-21470164120x80072124Source 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
-21470164110x80072125Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation
-21470164100x80072126Source 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
-21470164090x80072127Destination of a cross-domain move is not authoritative for the destination naming context
-21470164080x80072128Source 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
-21470164070x80072129Object 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
-21470164060x8007212AAnother operation which requires exclusive access to the PDC FSMO is already in progress
-21470164050x8007212BA 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
-21470164040x8007212CThis object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move
-21470164030x8007212DCan't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry
-21470164020x8007212EA naming context head must be the immediate child of another naming context head, not of an interior node
-21470164010x8007212FThe directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters)
-21470164000x80072130Destination domain must be in native mode
-21470163990x80072131The operation cannot be performed because the server does not have an infrastructure container in the domain of interest
-21470163980x80072132Cross-domain move of non-empty account groups is not allowed
-21470163970x80072133Cross-domain move of non-empty resource groups is not allowed
-21470163960x80072134The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings
-21470163950x80072135Tree deletions starting at an object which has an NC head as a descendant are not allowed
-21470163940x80072136The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use
-21470163930x80072137The directory service failed to identify the list of objects to delete while attempting a tree deletion
-21470163920x80072138Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information
-21470163910x80072139Only an administrator can modify the membership list of an administrative group
-21470163900x8007213ACannot change the primary group ID of a domain controller account
-21470163890x8007213BAn attempt is made to modify the base schema
-21470163880x8007213CAdding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed
-21470163870x8007213DSchema update is not allowed on this DC because the DC is not the schema FSMO Role Owner
-21470163860x8007213EAn 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
-21470163850x8007213FThe 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
-21470163840x80072140The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory
-21470163830x80072141The specified group type is invalid
-21470163820x80072142You cannot nest global groups in a mixed domain if the group is security-enabled
-21470163810x80072143You cannot nest local groups in a mixed domain if the group is security-enabled
-21470163800x80072144A global group cannot have a local group as a member
-21470163790x80072145A global group cannot have a universal group as a member
-21470163780x80072146A universal group cannot have a local group as a member
-21470163770x80072147A global group cannot have a cross-domain member
-21470163760x80072148A local group cannot have another cross domain local group as a member
-21470163750x80072149A group with primary members cannot change to a security-disabled group
-21470163740x8007214AThe schema cache load failed to convert the string default SD on a class-schema object
-21470163730x8007214BOnly DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers)
-21470163720x8007214CThe DSA operation is unable to proceed because of a DNS lookup failure
-21470163710x8007214DWhile processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync
-21470163700x8007214EThe Security Descriptor attribute could not be read
-21470163690x8007214FThe object requested was not found, but an object with that key was found
-21470163680x80072150The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1
-21470163670x80072151Security Account Manager needs to get the boot password
-21470163660x80072152Security Account Manager needs to get the boot key from floppy disk
-21470163650x80072153Directory Service cannot start
-21470163640x80072154Directory Services could not start
-21470163630x80072155The connection between client and server requires packet privacy or better
-21470163620x80072156The source domain may not be in the same forest as destination
-21470163610x80072157The destination domain must be in the forest
-21470163600x80072158The operation requires that destination domain auditing be enabled
-21470163590x80072159The operation couldn't locate a DC for the source domain
-21470163580x8007215AThe source object must be a group or user
-21470163570x8007215BThe source object's SID already exists in destination forest
-21470163560x8007215CThe source and destination object must be of the same type
-21470163550x8007215DSecurity 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
-21470163540x8007215ESchema information could not be included in the replication request
-21470163530x8007215FThe replication operation could not be completed due to a schema incompatibility
-21470163520x80072160The replication operation could not be completed due to a previous schema incompatibility
-21470163510x80072161The 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
-21470163500x80072162The requested domain could not be deleted because there exist domain controllers that still host this domain
-21470163490x80072163The requested operation can be performed only on a global catalog server
-21470163480x80072164A local group can only be a member of other local groups in the same domain
-21470163470x80072165Foreign security principals cannot be members of universal groups
-21470163460x80072166The attribute is not allowed to be replicated to the GC because of security reasons
-21470163450x80072167The checkpoint with the PDC could not be taken because there too many modifications being processed currently
-21470163440x80072168The operation requires that source domain auditing be enabled
-21470163430x80072169Security principal objects can only be created inside domain naming contexts
-21470163420x8007216AA Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format
-21470163410x8007216BA Filter was passed that uses constructed attributes
-21470163400x8007216CThe unicodePwd attribute value must be enclosed in double quotes
-21470163390x8007216DYour 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
-21470163380x8007216EFor security reasons, the operation must be run on the destination DC
-21470163370x8007216FFor security reasons, the source DC must be NT4SP4 or greater
-21470163360x80072170Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed
-21470163350x80072171Directory 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
-21470163340x80072172Security 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
-21470163330x80072173The 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
-21470163320x80072174The 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
-21470163310x80072175The 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
-21470163300x80072176The 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
-21470163290x80072177The version of the operating system installed on this server is incompatible with the functional level of the domain or forest
-21470163280x80072178The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level
-21470163270x80072179The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level
-21470163260x8007217AThe sort order requested is not supported
-21470163250x8007217BThe requested name already exists as a unique identifier
-21470163240x8007217CThe machine account was created pre-NT4. The account needs to be recreated
-21470163230x8007217DThe database is out of version store
-21470163220x8007217EUnable to continue operation because multiple conflicting controls were used
-21470163210x8007217FUnable to find a valid security descriptor reference domain for this partition
-21470163200x80072180Schema update failed: The link identifier is reserved
-21470163190x80072181Schema update failed: There are no link identifiers available
-21470163180x80072182An account group cannot have a universal group as a member
-21470163170x80072183Rename or move operations on naming context heads or read-only objects are not allowed
-21470163160x80072184Move operations on objects in the schema naming context are not allowed
-21470163150x80072185A system flag has been set on the object and does not allow the object to be moved or renamed
-21470163140x80072186This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers
-21470163130x80072187Unable to resolve completely, a referral to another forest is generated
-21470163120x80072188The requested action is not supported on standard server
-21470163110x80072189Could 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
-21470163100x8007218AThe directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master
-21470163090x8007218BThe thread limit for this request was exceeded
-21470163080x8007218CThe Global catalog server is not in the closest site
-21470163070x8007218DThe 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
-21470163060x8007218EThe Directory Service failed to enter single user mode
-21470163050x8007218FThe Directory Service cannot parse the script because of a syntax error
-21470163040x80072190The Directory Service cannot process the script because of an error
-21470163030x80072191The 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)
-21470163020x80072192The directory service binding must be renegotiated due to a change in the server extensions information
-21470163010x80072193Operation not allowed on a disabled cross ref
-21470163000x80072194Schema update failed: No values for msDS-IntId are available
-21470162990x80072195Schema update failed: Duplicate msDS-INtId. Retry the operation
-21470162980x80072196Schema deletion failed: attribute is used in rDNAttID
-21470162970x80072197The directory service failed to authorize the request
-21470162960x80072198The Directory Service cannot process the script because it is invalid
-21470162950x80072199The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data
-21470162940x8007219AA cross reference is in use locally with the same name
-21470162930x8007219BThe 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
-21470162920x8007219CWriteable NCs prevent this DC from demoting
-21470162910x8007219DThe requested object has a non-unique identifier and cannot be retrieved
-21470162900x8007219EInsufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected
-21470162890x8007219FThe group cannot be converted due to attribute restrictions on the requested group type
-21470162880x800721A0Cross-domain move of non-empty basic application groups is not allowed
-21470162870x800721A1Cross-domain move of non-empty query based application groups is not allowed
-21470162860x800721A2The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner
-21470162850x800721A3The target container for a redirection of a well known object container cannot already be a special container
-21470162840x800721A4The Directory Service cannot perform the requested operation because a domain rename operation is in progress
-21470162830x800721A5The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method
-21470162820x800721A6The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime
-21470162810x800721A7The requested operation is not allowed on an object under the system container
-21470162800x800721A8The 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
-21470162790x800721A9The 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
-21470162780x800721AAAt this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies
-21470162770x800721ABThe site settings object for the specified site does not exist
-21470162760x800721ACThe local account store does not contain secret material for the specified account
-21470162750x800721ADCould not find a writable domain controller in the domain
-21470162740x800721AEThe server object for the domain controller does not exist
-21470162730x800721AFThe NTDS Settings object for the domain controller does not exist
-21470162720x800721B0The requested search operation is not supported for ASQ searches
-21470162710x800721B1A required audit event could not be generated for the operation
-21470162700x800721B2The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes
-21470162690x800721B3The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings
-21470162680x800721B4The address books are nested too deeply. Failed to build the hierarchy table
-21470162670x800721B5The specified up-to-date-ness vector is corrupt
-21470162660x800721B6The request to replicate secrets is denied
-21470162650x800721B7Schema update failed: The MAPI identifier is reserved
-21470162640x800721B8Schema update failed: There are no MAPI identifiers available
-21470162630x800721B9The replication operation failed because the required attributes of the local krbtgt object are missing
-21470162620x800721BAThe domain name of the trusted domain already exists in the forest
-21470162610x800721BBThe flat name of the trusted domain already exists in the forest
-21470162600x800721BCThe User Principal Name (UPN) is invalid
-21470162590x800721BDOID mapped groups cannot have members
-21470162580x800721BEThe specified OID cannot be found
-21470162570x800721BFThe replication operation failed because the target object referred by a link value is recycled
-21470162560x800721C0The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller
-21470162550x800721C1The functional level of the AD LDS configuration set cannot be lowered to the requested value
-21470162540x800721C2The functional level of the domain (or forest) cannot be lowered to the requested value
-21470162530x800721C3The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level
-21470162520x800721C4The 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
-21470162510x800721C5The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object
-21470162500x800721C6The 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
-21470162490x800721C7The operation failed because SPN value provided for addition/modification is not unique forest-wide
-21470162480x800721C8The operation failed because UPN value provided for addition/modification is not unique forest-wide
-21470162470x800721C9The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present
-21470162460x800721CAThe link value specified was not found, but a link value with that key was found
-21470158950x80072329DNS server unable to interpret format
-21470158940x8007232ADNS server failure
-21470158930x8007232BDNS name does not exist
-21470158920x8007232CDNS request not supported by name server
-21470158910x8007232DDNS operation refused
-21470158900x8007232EDNS name that ought not exist, does exist
-21470158890x8007232FDNS RR set that ought not exist, does exist
-21470158880x80072330DNS RR set that ought to exist, does not exist
-21470158870x80072331DNS server not authoritative for zone
-21470158860x80072332DNS name in update or prereq is not in zone
-21470158800x80072338DNS signature failed to verify
-21470158790x80072339DNS bad key
-21470158780x8007233ADNS signature validity expired
-21470157950x8007238DOnly the DNS server acting as the key master for the zone may perform this operation
-21470157940x8007238EThis operation is not allowed on a zone that is signed or has signing keys
-21470157930x8007238FNSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC
-21470157920x80072390The 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)
-21470157910x80072391The specified algorithm is not supported
-21470157900x80072392The specified key size is not supported
-21470157890x80072393One 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
-21470157880x80072394The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved
-21470157870x80072395An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved
-21470157860x80072396An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved
-21470157850x80072397The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved
-21470157840x80072398The specified key service provider cannot be opened by the DNS server
-21470157830x80072399The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone
-21470157820x8007239AThe specified rollover period is invalid
-21470157810x8007239BThe specified initial rollover offset is invalid
-21470157800x8007239CThe specified signing key is already in process of rolling over keys
-21470157790x8007239DThe specified signing key does not have a standby key to revoke
-21470157780x8007239EThis operation is not allowed on a zone signing key (ZSK)
-21470157770x8007239FThis operation is not allowed on an active signing key
-21470157760x800723A0The specified signing key is already queued for rollover
-21470157750x800723A1This operation is not allowed on an unsigned zone
-21470157740x800723A2This 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
-21470157730x800723A3The specified signature validity period is invalid
-21470157720x800723A4The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone
-21470157710x800723A5This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server
-21470157700x800723A6This operation could not be completed because the XML stream received is empty or syntactically invalid
-21470157690x800723A7This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days
-21470157680x800723A8The specified signing key is not waiting for parental DS update
-21470157670x800723A9Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again
-21470157660x800723AANSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3
-21470153950x8007251DNo records found for given DNS query
-21470153940x8007251EBad DNS packet
-21470153930x8007251FNo DNS packet
-21470153920x80072520DNS error, check rcode
-21470153910x80072521Unsecured DNS packet
-21470153900x80072522DNS query request is pending
-21470153450x8007254FInvalid DNS type
-21470153440x80072550Invalid IP address
-21470153430x80072551Invalid property
-21470153420x80072552Try DNS operation again later
-21470153410x80072553Record for given name and type is not unique
-21470153400x80072554DNS name does not comply with RFC specifications
-21470153390x80072555DNS name is a fully-qualified DNS name
-21470153380x80072556DNS name is dotted (multi-label)
-21470153370x80072557DNS name is a single-part name
-21470153360x80072558DNS name contains an invalid character
-21470153350x80072559DNS name is entirely numeric
-21470153340x8007255AThe operation requested is not permitted on a DNS root server
-21470153330x8007255BThe record could not be created because this part of the DNS namespace has been delegated to another server
-21470153320x8007255CThe DNS server could not find a set of root hints
-21470153310x8007255DThe DNS server found root hints but they were not consistent across all adapters
-21470153300x8007255EThe specified value is too small for this parameter
-21470153290x8007255FThe specified value is too large for this parameter
-21470153280x80072560This operation is not allowed while the DNS server is loading zones in the background. Please try again later
-21470153270x80072561The operation requested is not permitted on against a DNS server running on a read-only DC
-21470153260x80072562No data is allowed to exist underneath a DNAME record
-21470153250x80072563This operation requires credentials delegation
-21470153240x80072564Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator
-21470153230x80072565Not allowed to remove all addresses
-21470152950x80072581DNS zone does not exist
-21470152940x80072582DNS zone information not available
-21470152930x80072583Invalid operation for DNS zone
-21470152920x80072584Invalid DNS zone configuration
-21470152910x80072585DNS zone has no start of authority (SOA) record
-21470152900x80072586DNS zone has no Name Server (NS) record
-21470152890x80072587DNS zone is locked
-21470152880x80072588DNS zone creation failed
-21470152870x80072589DNS zone already exists
-21470152860x8007258ADNS automatic zone already exists
-21470152850x8007258BInvalid DNS zone type
-21470152840x8007258CSecondary DNS zone requires master IP address
-21470152830x8007258DDNS zone not secondary
-21470152820x8007258ENeed secondary IP address
-21470152810x8007258FWINS initialization failed
-21470152800x80072590Need WINS servers
-21470152790x80072591NBTSTAT initialization call failed
-21470152780x80072592Invalid delete of start of authority (SOA)
-21470152770x80072593A conditional forwarding zone already exists for that name
-21470152760x80072594This zone must be configured with one or more master DNS server IP addresses
-21470152750x80072595The operation cannot be performed because this zone is shut down
-21470152740x80072596This operation cannot be performed because the zone is currently being signed. Please try again later
-21470152450x800725B3Primary DNS zone requires datafile
-21470152440x800725B4Invalid datafile name for DNS zone
-21470152430x800725B5Failed to open datafile for DNS zone
-21470152420x800725B6Failed to write datafile for DNS zone
-21470152410x800725B7Failure while reading datafile for DNS zone
-21470151950x800725E5DNS record does not exist
-21470151940x800725E6DNS record format error
-21470151930x800725E7Node creation failure in DNS
-21470151920x800725E8Unknown DNS record type
-21470151910x800725E9DNS record timed out
-21470151900x800725EAName not in DNS zone
-21470151890x800725EBCNAME loop detected
-21470151880x800725ECNode is a CNAME DNS record
-21470151870x800725EDA CNAME record already exists for given name
-21470151860x800725EERecord only at DNS zone root
-21470151850x800725EFDNS record already exists
-21470151840x800725F0Secondary DNS zone data error
-21470151830x800725F1Could not create DNS cache data
-21470151820x800725F2DNS name does not exist
-21470151810x800725F3Could not create pointer (PTR) record
-21470151800x800725F4DNS domain was undeleted
-21470151790x800725F5The directory service is unavailable
-21470151780x800725F6DNS zone already exists in the directory service
-21470151770x800725F7DNS server not creating or reading the boot file for the directory service integrated DNS zone
-21470151760x800725F8Node is a DNAME DNS record
-21470151750x800725F9A DNAME record already exists for given name
-21470151740x800725FAAn alias loop has been detected with either CNAME or DNAME records
-21470151450x80072617DNS AXFR (zone transfer) complete
-21470151440x80072618DNS zone transfer failed
-21470151430x80072619Added local WINS server
-21470150950x80072649Secure update call needs to continue update request
-21470150450x8007267BTCP/IP network protocol not installed
-21470150440x8007267CNo DNS servers configured for local system
-21470149950x800726ADThe specified directory partition does not exist
-21470149940x800726AEThe specified directory partition already exists
-21470149930x800726AFThis DNS server is not enlisted in the specified directory partition
-21470149920x800726B0This DNS server is already enlisted in the specified directory partition
-21470149910x800726B1The directory partition is not available at this time. Please wait a few minutes and try again
-21470149900x800726B2The 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
-21470149450x800726DFThe scope already exists for the zone
-21470149440x800726E0The scope does not exist for the zone
-21470149430x800726E1The scope is the same as the default zone scope
-21470149420x800726E2The scope name contains invalid characters
-21470149410x800726E3Operation not allowed when the zone has scopes
-21470149400x800726E4Failed to load zone scope
-21470149390x800726E5Failed to write data file for DNS zone scope. Please verify the file exists and is writable
-21470149380x800726E6The scope name contains invalid characters
-21470149370x800726E7The scope does not exist
-21470149360x800726E8The scope is the same as the default scope
-21470149350x800726E9The operation is invalid on the scope
-21470149340x800726EAThe scope is locked
-21470149330x800726EBThe scope already exists
-21470149250x800726F3A policy with the same name already exists on this level (server level or zone level) on the DNS server
-21470149240x800726F4No policy with this name exists on this level (server level or zone level) on the DNS server
-21470149230x800726F5The criteria provided in the policy are invalid
-21470149220x800726F6At least one of the settings of this policy is invalid
-21470149210x800726F7The client subnet cannot be deleted while it is being accessed by a policy
-21470149200x800726F8The client subnet does not exist on the DNS server
-21470149190x800726F9A client subnet with this name already exists on the DNS server
-21470149180x800726FAThe IP subnet specified does not exist in the client subnet
-21470149170x800726FBThe IP subnet that is being added, already exists in the client subnet
-21470149160x800726FCThe policy is locked
-21470149150x800726FDThe weight of the scope in the policy is invalid
-21470149140x800726FEThe DNS policy name is invalid
-21470149130x800726FFThe policy is missing criteria
-21470149120x80072700The name of the the client subnet record is invalid
-21470149110x80072701Invalid policy processing order
-21470149100x80072702The scope information has not been provided for a policy that requires it
-21470149090x80072703The scope information has been provided for a policy that does not require it
-21470149080x80072704The server scope cannot be deleted because it is referenced by a DNS Policy
-21470149070x80072705The zone scope cannot be deleted because it is referenced by a DNS Policy
-21470149060x80072706The criterion client subnet provided in the policy is invalid
-21470149050x80072707The criterion transport protocol provided in the policy is invalid
-21470149040x80072708The criterion network protocol provided in the policy is invalid
-21470149030x80072709The criterion interface provided in the policy is invalid
-21470149020x8007270AThe criterion FQDN provided in the policy is invalid
-21470149010x8007270BThe criterion query type provided in the policy is invalid
-21470149000x8007270CThe criterion time of day provided in the policy is invalid
-21470148920x80072714A blocking operation was interrupted by a call to WSACancelBlockingCall
-21470148870x80072719The file handle supplied is not valid
-21470148830x8007271DAn attempt was made to access a socket in a way forbidden by its access permissions
-21470148820x8007271EThe system detected an invalid pointer address in attempting to use a pointer argument in a call
-21470148740x80072726An invalid argument was supplied
-21470148720x80072728Too many open sockets
-21470148610x80072733A non-blocking socket operation could not be completed immediately
-21470148600x80072734A blocking operation is currently executing
-21470148590x80072735An operation was attempted on a non-blocking socket that already had an operation in progress
-21470148580x80072736An operation was attempted on something that is not a socket
-21470148570x80072737A required address was omitted from an operation on a socket
-21470148560x80072738A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself
-21470148550x80072739A protocol was specified in the socket function call that does not support the semantics of the socket type requested
-21470148540x8007273AAn unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call
-21470148530x8007273BThe requested protocol has not been configured into the system, or no implementation for it exists
-21470148520x8007273CThe support for the specified socket type does not exist in this address family
-21470148510x8007273DThe attempted operation is not supported for the type of object referenced
-21470148500x8007273EThe protocol family has not been configured into the system or no implementation for it exists
-21470148490x8007273FAn address incompatible with the requested protocol was used
-21470148480x80072740Only one usage of each socket address (protocol/network address/port) is normally permitted
-21470148470x80072741The requested address is not valid in its context
-21470148460x80072742A socket operation encountered a dead network
-21470148450x80072743A socket operation was attempted to an unreachable network
-21470148440x80072744The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress
-21470148430x80072745An established connection was aborted by the software in your host machine
-21470148420x80072746An existing connection was forcibly closed by the remote host
-21470148410x80072747An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full
-21470148400x80072748A connect request was made on an already connected socket
-21470148390x80072749A 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
-21470148380x8007274AA request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call
-21470148370x8007274BToo many references to some kernel object
-21470148360x8007274CA connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
-21470148350x8007274DNo connection could be made because the target machine actively refused it
-21470148340x8007274ECannot translate name
-21470148330x8007274FName component or name was too long
-21470148320x80072750A socket operation failed because the destination host was down
-21470148310x80072751A socket operation was attempted to an unreachable host
-21470148300x80072752Cannot remove a directory that is not empty
-21470148290x80072753A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously
-21470148280x80072754Ran out of quota
-21470148270x80072755Ran out of disk quota
-21470148260x80072756File handle reference is no longer available
-21470148250x80072757Item is not available locally
-21470148050x8007276BWSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable
-21470148040x8007276CThe Windows Sockets version requested is not supported
-21470148030x8007276DEither the application has not called WSAStartup, or WSAStartup failed
-21470147950x80072775Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence
-21470147940x80072776No more results can be returned by WSALookupServiceNext
-21470147930x80072777A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled
-21470147920x80072778The procedure call table is invalid
-21470147910x80072779The requested service provider is invalid
-21470147900x8007277AThe requested service provider could not be loaded or initialized
-21470147890x8007277BA system call has failed
-21470147880x8007277CNo such service is known. The service cannot be found in the specified name space
-21470147870x8007277DThe specified class was not found
-21470147860x8007277ENo more results can be returned by WSALookupServiceNext
-21470147850x8007277FA call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled
-21470147840x80072780A database query failed because it was actively refused
-21470138950x80072AF9No such host is known
-21470138940x80072AFAThis is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
-21470138930x80072AFBA non-recoverable error occurred during a database lookup
-21470138920x80072AFCThe requested name is valid, but no data of the requested type was found
-21470138910x80072AFDAt least one reserve has arrived
-21470138900x80072AFEAt least one path has arrived
-21470138890x80072AFFThere are no senders
-21470138880x80072B00There are no receivers
-21470138870x80072B01Reserve has been confirmed
-21470138860x80072B02Error due to lack of resources
-21470138850x80072B03Rejected for administrative reasons - bad credentials
-21470138840x80072B04Unknown or conflicting style
-21470138830x80072B05Problem with some part of the filterspec or providerspecific buffer in general
-21470138820x80072B06Problem with some part of the flowspec
-21470138810x80072B07General QOS error
-21470138800x80072B08An invalid or unrecognized service type was found in the flowspec
-21470138790x80072B09An invalid or inconsistent flowspec was found in the QOS structure
-21470138780x80072B0AInvalid QOS provider-specific buffer
-21470138770x80072B0BAn invalid QOS filter style was used
-21470138760x80072B0CAn invalid QOS filter type was used
-21470138750x80072B0DAn incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR
-21470138740x80072B0EAn object with an invalid ObjectLength field was specified in the QOS provider-specific buffer
-21470138730x80072B0FAn incorrect number of flow descriptors was specified in the QOS structure
-21470138720x80072B10An unrecognized object was found in the QOS provider-specific buffer
-21470138710x80072B11An invalid policy object was found in the QOS provider-specific buffer
-21470138700x80072B12An invalid QOS flow descriptor was found in the flow descriptor list
-21470138690x80072B13An invalid or inconsistent flowspec was found in the QOS provider specific buffer
-21470138680x80072B14An invalid FILTERSPEC was found in the QOS provider-specific buffer
-21470138670x80072B15An invalid shape discard mode object was found in the QOS provider specific buffer
-21470138660x80072B16An invalid shaping rate object was found in the QOS provider-specific buffer
-21470138650x80072B17A reserved policy element was found in the QOS provider-specific buffer
-21470138640x80072B18No such host is known securely
-21470138630x80072B19Name based IPSEC policy could not be added
-21470118960x800732C8The specified quick mode policy already exists
-21470118950x800732C9The specified quick mode policy was not found
-21470118940x800732CAThe specified quick mode policy is being used
-21470118930x800732CBThe specified main mode policy already exists
-21470118920x800732CCThe specified main mode policy was not found
-21470118910x800732CDThe specified main mode policy is being used
-21470118900x800732CEThe specified main mode filter already exists
-21470118890x800732CFThe specified main mode filter was not found
-21470118880x800732D0The specified transport mode filter already exists
-21470118870x800732D1The specified transport mode filter does not exist
-21470118860x800732D2The specified main mode authentication list exists
-21470118850x800732D3The specified main mode authentication list was not found
-21470118840x800732D4The specified main mode authentication list is being used
-21470118830x800732D5The specified default main mode policy was not found
-21470118820x800732D6The specified default main mode authentication list was not found
-21470118810x800732D7The specified default quick mode policy was not found
-21470118800x800732D8The specified tunnel mode filter exists
-21470118790x800732D9The specified tunnel mode filter was not found
-21470118780x800732DAThe Main Mode filter is pending deletion
-21470118770x800732DBThe transport filter is pending deletion
-21470118760x800732DCThe tunnel filter is pending deletion
-21470118750x800732DDThe Main Mode policy is pending deletion
-21470118740x800732DEThe Main Mode authentication bundle is pending deletion
-21470118730x800732DFThe Quick Mode policy is pending deletion
-21470118720x800732E0The Main Mode policy was successfully added, but some of the requested offers are not supported
-21470118710x800732E1The Quick Mode policy was successfully added, but some of the requested offers are not supported
-21470110960x800735E8ERROR_IPSEC_IKE_NEG_STATUS_BEGIN
-21470110950x800735E9IKE authentication credentials are unacceptable
-21470110940x800735EAIKE security attributes are unacceptable
-21470110930x800735EBIKE Negotiation in progress
-21470110920x800735ECGeneral processing error
-21470110910x800735EDNegotiation timed out
-21470110900x800735EEIKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store
-21470110890x800735EFIKE SA deleted by peer before establishment completed
-21470110880x800735F0IKE SA deleted before establishment completed
-21470110870x800735F1Negotiation request sat in Queue too long
-21470110860x800735F2Negotiation request sat in Queue too long
-21470110850x800735F3Negotiation request sat in Queue too long
-21470110840x800735F4Negotiation request sat in Queue too long
-21470110830x800735F5No response from peer
-21470110820x800735F6Negotiation took too long
-21470110810x800735F7Negotiation took too long
-21470110800x800735F8Unknown error occurred
-21470110790x800735F9Certificate Revocation Check failed
-21470110780x800735FAInvalid certificate key usage
-21470110770x800735FBInvalid certificate type
-21470110760x800735FCIKE 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
-21470110750x800735FDSimultaneous rekeys were detected
-21470110740x800735FEFailure in Diffie-Hellman computation
-21470110730x800735FFDon't know how to process critical payload
-21470110720x80073600Invalid header
-21470110710x80073601No policy configured
-21470110700x80073602Failed to verify signature
-21470110690x80073603Failed to authenticate using Kerberos
-21470110680x80073604Peer's certificate did not have a public key
-21470110670x80073605Error processing error payload
-21470110660x80073606Error processing SA payload
-21470110650x80073607Error processing Proposal payload
-21470110640x80073608Error processing Transform payload
-21470110630x80073609Error processing KE payload
-21470110620x8007360AError processing ID payload
-21470110610x8007360BError processing Cert payload
-21470110600x8007360CError processing Certificate Request payload
-21470110590x8007360DError processing Hash payload
-21470110580x8007360EError processing Signature payload
-21470110570x8007360FError processing Nonce payload
-21470110560x80073610Error processing Notify payload
-21470110550x80073611Error processing Delete Payload
-21470110540x80073612Error processing VendorId payload
-21470110530x80073613Invalid payload received
-21470110520x80073614Soft SA loaded
-21470110510x80073615Soft SA torn down
-21470110500x80073616Invalid cookie received
-21470110490x80073617Peer failed to send valid machine certificate
-21470110480x80073618Certification Revocation check of peer's certificate failed
-21470110470x80073619New policy invalidated SAs formed with old policy
-21470110460x8007361AThere is no available Main Mode IKE policy
-21470110450x8007361BFailed to enabled TCB privilege
-21470110440x8007361CFailed to load SECURITY.DLL
-21470110430x8007361DFailed to obtain security function table dispatch address from SSPI
-21470110420x8007361EFailed to query Kerberos package to obtain max token size
-21470110410x8007361FFailed 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
-21470110400x80073620Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes)
-21470110390x80073621Failed 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
-21470110380x80073622Given filter is invalid
-21470110370x80073623Memory allocation failed
-21470110360x80073624Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine
-21470110350x80073625Invalid policy
-21470110340x80073626Invalid DOI
-21470110330x80073627Invalid situation
-21470110320x80073628Diffie-Hellman failure
-21470110310x80073629Invalid Diffie-Hellman group
-21470110300x8007362AError encrypting payload
-21470110290x8007362BError decrypting payload
-21470110280x8007362CPolicy match error
-21470110270x8007362DUnsupported ID
-21470110260x8007362EHash verification failed
-21470110250x8007362FInvalid hash algorithm
-21470110240x80073630Invalid hash size
-21470110230x80073631Invalid encryption algorithm
-21470110220x80073632Invalid authentication algorithm
-21470110210x80073633Invalid certificate signature
-21470110200x80073634Load failed
-21470110190x80073635Deleted via RPC call
-21470110180x80073636Temporary state created to perform reinitialization. This is not a real failure
-21470110170x80073637The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine
-21470110160x80073638The recipient cannot handle version of IKE specified in the header
-21470110150x80073639Key length in certificate is too small for configured security requirements
-21470110140x8007363AMax number of established MM SAs to peer exceeded
-21470110130x8007363BIKE received a policy that disables negotiation
-21470110120x8007363CReached maximum quick mode limit for the main mode. New main mode will be started
-21470110110x8007363DMain mode SA lifetime expired or peer sent a main mode delete
-21470110100x8007363EMain mode SA assumed to be invalid because peer stopped responding
-21470110090x8007363FCertificate doesn't chain to a trusted root in IPsec policy
-21470110080x80073640Received unexpected message ID
-21470110070x80073641Received invalid authentication offers
-21470110060x80073642Sent DoS cookie notify to initiator
-21470110050x80073643IKE service is shutting down
-21470110040x80073644Could not verify binding between CGA address and certificate
-21470110030x80073645Error processing NatOA payload
-21470110020x80073646Parameters of the main mode are invalid for this quick mode
-21470110010x80073647Quick mode SA was expired by IPsec driver
-21470110000x80073648Too many dynamically added IKEEXT filters were detected
-21470109990x80073649ERROR_IPSEC_IKE_NEG_STATUS_END
-21470109980x8007364ANAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel
-21470109970x8007364BError in assigning inner IP address to initiator in tunnel mode
-21470109960x8007364CRequire configuration payload missing
-21470109950x8007364DA negotiation running as the security principle who issued the connection is in progress
-21470109940x8007364ESA was deleted due to IKEv1/AuthIP co-existence suppress check
-21470109930x8007364FIncoming SA request was dropped due to peer IP address rate limiting
-21470109920x80073650Peer does not support MOBIKE
-21470109910x80073651SA establishment is not authorized
-21470109900x80073652SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential
-21470109890x80073653SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard
-21470109880x80073654SA 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
-21470109870x80073655ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END
-21470109860x80073656The SPI in the packet does not match a valid IPsec SA
-21470109850x80073657Packet was received on an IPsec SA whose lifetime has expired
-21470109840x80073658Packet was received on an IPsec SA that does not match the packet characteristics
-21470109830x80073659Packet sequence number replay check failed
-21470109820x8007365AIPsec header and/or trailer in the packet is invalid
-21470109810x8007365BIPsec integrity check failed
-21470109800x8007365CIPsec dropped a clear text packet
-21470109790x8007365DIPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign
-21470109780x8007365EIPsec dropped a packet due to DoS throttling
-21470109710x80073665IPsec DoS Protection matched an explicit block rule
-21470109700x80073666IPsec DoS Protection received an IPsec specific multicast packet which is not allowed
-21470109690x80073667IPsec DoS Protection received an incorrectly formatted packet
-21470109680x80073668IPsec DoS Protection failed to look up state
-21470109670x80073669IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached
-21470109660x8007366AIPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy
-21470109650x8007366BIPsec DoS Protection has not been enabled
-21470109640x8007366CIPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached
-21470108960x800736B0The requested section was not present in the activation context
-21470108950x800736B1The 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
-21470108940x800736B2The application binding data format is invalid
-21470108930x800736B3The referenced assembly is not installed on your system
-21470108920x800736B4The manifest file does not begin with the required tag and format information
-21470108910x800736B5The manifest file contains one or more syntax errors
-21470108900x800736B6The application attempted to activate a disabled activation context
-21470108890x800736B7The requested lookup key was not found in any active activation context
-21470108880x800736B8A component version required by the application conflicts with another component version already active
-21470108870x800736B9The type requested activation context section does not match the query API used
-21470108860x800736BALack of system resources has required isolated activation to be disabled for the current thread of execution
-21470108850x800736BBAn attempt to set the process default activation context failed because the process default activation context was already set
-21470108840x800736BCThe encoding group identifier specified is not recognized
-21470108830x800736BDThe encoding requested is not recognized
-21470108820x800736BEThe manifest contains a reference to an invalid URI
-21470108810x800736BFThe application manifest contains a reference to a dependent assembly which is not installed
-21470108800x800736C0The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed
-21470108790x800736C1The manifest contains an attribute for the assembly identity which is not valid
-21470108780x800736C2The manifest is missing the required default namespace specification on the assembly element
-21470108770x800736C3The manifest has a default namespace specified on the assembly element but its value is not urn:schemas-microsoft-com:asm.v1""""
-21470108760x800736C4The private manifest probed has crossed a path with an unsupported reparse point
-21470108750x800736C5Two or more components referenced directly or indirectly by the application manifest have files by the same name
-21470108740x800736C6Two or more components referenced directly or indirectly by the application manifest have window classes with the same name
-21470108730x800736C7Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs
-21470108720x800736C8Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs
-21470108710x800736C9Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs
-21470108700x800736CATwo or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs
-21470108690x800736CBTwo or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted
-21470108680x800736CCA component's file does not match the verification information present in the component manifest
-21470108670x800736CDThe policy manifest contains one or more syntax errors
-21470108660x800736CEManifest Parse Error : A string literal was expected, but no opening quote character was found
-21470108650x800736CFManifest Parse Error : Incorrect syntax was used in a comment
-21470108640x800736D0Manifest Parse Error : A name was started with an invalid character
-21470108630x800736D1Manifest Parse Error : A name contained an invalid character
-21470108620x800736D2Manifest Parse Error : A string literal contained an invalid character
-21470108610x800736D3Manifest Parse Error : Invalid syntax for an xml declaration
-21470108600x800736D4Manifest Parse Error : An Invalid character was found in text content
-21470108590x800736D5Manifest Parse Error : Required white space was missing
-21470108580x800736D6Manifest Parse Error : The character '>' was expected
-21470108570x800736D7Manifest Parse Error : A semi colon character was expected
-21470108560x800736D8Manifest Parse Error : Unbalanced parentheses
-21470108550x800736D9Manifest Parse Error : Internal error
-21470108540x800736DAManifest Parse Error : Whitespace is not allowed at this location
-21470108530x800736DBManifest Parse Error : End of file reached in invalid state for current encoding
-21470108520x800736DCManifest Parse Error : Missing parenthesis
-21470108510x800736DDManifest Parse Error : A single or double closing quote character (\' or \) is missing""
-21470108500x800736DEManifest Parse Error : Multiple colons are not allowed in a name
-21470108490x800736DFManifest Parse Error : Invalid character for decimal digit
-21470108480x800736E0Manifest Parse Error : Invalid character for hexadecimal digit
-21470108470x800736E1Manifest Parse Error : Invalid unicode character value for this platform
-21470108460x800736E2Manifest Parse Error : Expecting whitespace or '?'
-21470108450x800736E3Manifest Parse Error : End tag was not expected at this location
-21470108440x800736E4Manifest Parse Error : The following tags were not closed: %1
-21470108430x800736E5Manifest Parse Error : Duplicate attribute
-21470108420x800736E6Manifest Parse Error : Only one top level element is allowed in an XML document
-21470108410x800736E7Manifest Parse Error : Invalid at the top level of the document
-21470108400x800736E8Manifest Parse Error : Invalid xml declaration
-21470108390x800736E9Manifest Parse Error : XML document must have a top level element
-21470108380x800736EAManifest Parse Error : Unexpected end of file
-21470108370x800736EBManifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset
-21470108360x800736ECManifest Parse Error : Element was not closed
-21470108350x800736EDManifest Parse Error : End element was missing the character '>'
-21470108340x800736EEManifest Parse Error : A string literal was not closed
-21470108330x800736EFManifest Parse Error : A comment was not closed
-21470108320x800736F0Manifest Parse Error : A declaration was not closed
-21470108310x800736F1Manifest Parse Error : A CDATA section was not closed
-21470108300x800736F2Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string xml""""
-21470108290x800736F3Manifest Parse Error : System does not support the specified encoding
-21470108280x800736F4Manifest Parse Error : Switch from current encoding to specified encoding not supported
-21470108270x800736F5Manifest Parse Error : The name 'xml' is reserved and must be lower case
-21470108260x800736F6Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'
-21470108250x800736F7Manifest Parse Error : The standalone attribute cannot be used in external entities
-21470108240x800736F8Manifest Parse Error : Invalid version number
-21470108230x800736F9Manifest Parse Error : Missing equals sign between attribute and attribute value
-21470108220x800736FAAssembly Protection Error : Unable to recover the specified assembly
-21470108210x800736FBAssembly Protection Error : The public key for an assembly was too short to be allowed
-21470108200x800736FCAssembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest
-21470108190x800736FDAn HRESULT could not be translated to a corresponding Win32 error code
-21470108180x800736FEAssembly Protection Error : The catalog for an assembly is missing
-21470108170x800736FFThe supplied assembly identity is missing one or more attributes which must be present in this context
-21470108160x80073700The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names
-21470108150x80073701The referenced assembly could not be found
-21470108140x80073702The activation context activation stack for the running thread of execution is corrupt
-21470108130x80073703The application isolation metadata for this process or thread has become corrupt
-21470108120x80073704The activation context being deactivated is not the most recently activated one
-21470108110x80073705The activation context being deactivated is not active for the current thread of execution
-21470108100x80073706The activation context being deactivated has already been deactivated
-21470108090x80073707A component used by the isolation facility has requested to terminate the process
-21470108080x80073708A kernel mode component is releasing a reference on an activation context
-21470108070x80073709The activation context of system default assembly could not be generated
-21470108060x8007370AThe value of an attribute in an identity is not within the legal range
-21470108050x8007370BThe name of an attribute in an identity is not within the legal range
-21470108040x8007370CAn identity contains two definitions for the same attribute
-21470108030x8007370DThe identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value
-21470108020x8007370EA 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
-21470108010x8007370FThe public key token does not correspond to the public key specified
-21470108000x80073710A substitution string had no mapping
-21470107990x80073711The component must be locked before making the request
-21470107980x80073712The component store has been corrupted
-21470107970x80073713An advanced installer failed during setup or servicing
-21470107960x80073714The character encoding in the XML declaration did not match the encoding used in the document
-21470107950x80073715The identities of the manifests are identical but their contents are different
-21470107940x80073716The component identities are different
-21470107930x80073717The assembly is not a deployment
-21470107920x80073718The file is not a part of the assembly
-21470107910x80073719The size of the manifest exceeds the maximum allowed
-21470107900x8007371AThe setting is not registered
-21470107890x8007371BOne or more required members of the transaction are not present
-21470107880x8007371CThe SMI primitive installer failed during setup or servicing
-21470107870x8007371DA generic command executable returned a result that indicates failure
-21470107860x8007371EA component is missing file verification information in its manifest
-21470098960x80073A98The specified channel path is invalid
-21470098950x80073A99The specified query is invalid
-21470098940x80073A9AThe publisher metadata cannot be found in the resource
-21470098930x80073A9BThe template for an event definition cannot be found in the resource (error = %1)
-21470098920x80073A9CThe specified publisher name is invalid
-21470098910x80073A9DThe event data raised by the publisher is not compatible with the event template definition in the publisher's manifest
-21470098890x80073A9FThe specified channel could not be found. Check channel configuration
-21470098880x80073AA0The specified xml text was not well-formed. See Extended Error for more details
-21470098870x80073AA1The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to
-21470098860x80073AA2Configuration error
-21470098850x80073AA3The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query
-21470098840x80073AA4Query result is currently at an invalid position
-21470098830x80073AA5Registered MSXML doesn't support validation
-21470098820x80073AA6An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation
-21470098810x80073AA7Can't perform a step operation from a term that does not represent an element set
-21470098800x80073AA8Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants
-21470098790x80073AA9A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceeding node set can be evaluated
-21470098780x80073AAAThis data type is currently unsupported
-21470098770x80073AABA syntax error occurred at position %1!d!
-21470098760x80073AACThis operator is unsupported by this implementation of the filter
-21470098750x80073AADThe token encountered was unexpected
-21470098740x80073AAEThe requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation
-21470098730x80073AAFChannel property %1 contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of channel
-21470098720x80073AB0Publisher property %1 contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of publisher
-21470098710x80073AB1The channel fails to activate
-21470098700x80073AB2The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions
-21470098690x80073AB3the message resource is present but the message is not found in the string/message table
-21470098680x80073AB4The message id for the desired message could not be found
-21470098670x80073AB5The substitution string for insert index (%1) could not be found
-21470098660x80073AB6The description string for parameter reference (%1) could not be found
-21470098650x80073AB7The maximum number of replacements has been reached
-21470098640x80073AB8The event definition could not be found for event id (%1)
-21470098630x80073AB9The locale specific resource for the desired message is not present
-21470098620x80073ABAThe resource is too old to be compatible
-21470098610x80073ABBThe resource is too new to be compatible
-21470098600x80073ABCThe channel at index %1!d! of the query can't be opened
-21470098590x80073ABDThe 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
-21470098580x80073ABEAttempted to create a numeric type that is outside of its valid range
-21470098160x80073AE8The subscription fails to activate
-21470098150x80073AE9The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated
-21470098140x80073AEAWhen forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription
-21470098130x80073AEBThe credential store that is used to save credentials is full
-21470098120x80073AECThe credential used by this subscription can't be found in credential store
-21470098110x80073AEDNo active channel is found for the query
-21470097960x80073AFCThe resource loader failed to find MUI file
-21470097950x80073AFDThe resource loader failed to load MUI file because the file fail to pass validation
-21470097940x80073AFEThe RC Manifest is corrupted with garbage data or unsupported version or missing required item
-21470097930x80073AFFThe RC Manifest has invalid culture name
-21470097920x80073B00The RC Manifest has invalid ultimatefallback name
-21470097910x80073B01The resource loader cache doesn't have loaded MUI entry
-21470097900x80073B02User stopped resource enumeration
-21470097890x80073B03UI language installation failed
-21470097880x80073B04Locale installation failed
-21470097860x80073B06A resource does not have default or neutral value
-21470097850x80073B07Invalid PRI config file
-21470097840x80073B08Invalid file type
-21470097830x80073B09Unknown qualifier
-21470097820x80073B0AInvalid qualifier value
-21470097810x80073B0BNo Candidate found
-21470097800x80073B0CThe ResourceMap or NamedResource has an item that does not have default or neutral resource
-21470097790x80073B0DInvalid ResourceCandidate type
-21470097780x80073B0EDuplicate Resource Map
-21470097770x80073B0FDuplicate Entry
-21470097760x80073B10Invalid Resource Identifier
-21470097750x80073B11Filepath too long
-21470097740x80073B12Unsupported directory type
-21470097700x80073B16Invalid PRI File
-21470097690x80073B17NamedResource Not Found
-21470097610x80073B1FResourceMap Not Found
-21470097600x80073B20Unsupported MRT profile type
-21470097590x80073B21Invalid qualifier operator
-21470097580x80073B22Unable to determine qualifier value or qualifier value has not been set
-21470097570x80073B23Automerge is enabled in the PRI file
-21470097560x80073B24Too many resources defined for package
-21470097550x80073B25Resource File can not be used for merge operation
-21470097540x80073B26Load/UnloadPriFiles cannot be used with resource packages
-21470097530x80073B27Resource Contexts may not be created on threads that do not have a CoreWindow
-21470097520x80073B28The singleton Resource Manager with different profile is already created
-21470097510x80073B29The system component cannot operate given API operation
-21470097500x80073B2AThe resource is a direct reference to a non-default resource candidate
-21470097490x80073B2BResource Map has been re-generated and the query string is not valid anymore
-21470096960x80073B60The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification
-21470096950x80073B61The monitor's VCP Version (0xDF) VCP code returned an invalid version value
-21470096940x80073B62The monitor does not comply with the MCCS specification it claims to support
-21470096930x80073B63The 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
-21470096920x80073B64The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification
-21470096910x80073B65An internal Monitor Configuration API error occurred
-21470096900x80073B66The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification
-21470096890x80073B67The 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
-21470096460x80073B92The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria
-21470095970x80073BC3The requested system device cannot be found
-21470095960x80073BC4Hash generation for the specified hash version and hash type is not enabled on the server
-21470095950x80073BC5The hash requested from the server is not available or no longer valid
-21470095750x80073BD9The secondary interrupt controller instance that manages the specified interrupt is not registered
-21470095740x80073BDAThe information supplied by the GPIO client driver is invalid
-21470095730x80073BDBThe version specified by the GPIO client driver is not supported
-21470095720x80073BDCThe registration packet supplied by the GPIO client driver is not valid
-21470095710x80073BDDThe requested operation is not suppported for the specified handle
-21470095700x80073BDEThe requested connect mode conflicts with an existing mode on one or more of the specified pins
-21470095690x80073BDFThe interrupt requested to be unmasked is not masked
-21470094960x80073C28The requested run level switch cannot be completed successfully
-21470094950x80073C29The service has an invalid run level setting. The run level for a service must not be higher than the run level of its dependent services
-21470094940x80073C2AThe requested run level switch cannot be completed successfully since one or more services will not stop or restart within the specified timeout
-21470094930x80073C2BA run level switch agent did not respond within the specified timeout
-21470094920x80073C2CA run level switch is currently in progress
-21470094910x80073C2DOne or more services failed to start during the service startup phase of a run level switch
-21470093950x80073C8DThe task stop request cannot be completed immediately since task needs more time to shutdown
-21470092960x80073CF0Package could not be opened
-21470092950x80073CF1Package was not found
-21470092940x80073CF2Package data is invalid
-21470092930x80073CF3Package failed updates, dependency or conflict validation
-21470092920x80073CF4There is not enough disk space on your computer. Please free up some space and try again
-21470092910x80073CF5There was a problem downloading your product
-21470092900x80073CF6Package could not be registered
-21470092890x80073CF7Package could not be unregistered
-21470092880x80073CF8User cancelled the install request
-21470092870x80073CF9Install failed. Please contact your software vendor
-21470092860x80073CFARemoval failed. Please contact your software vendor
-21470092850x80073CFBThe provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details
-21470092840x80073CFCThe application cannot be started. Try reinstalling the application to fix the problem
-21470092830x80073CFDA Prerequisite for an install could not be satisfied
-21470092820x80073CFEThe package repository is corrupted
-21470092810x80073CFFTo install this application you need either a Windows developer license or a sideloading-enabled system
-21470092800x80073D00The application cannot be started because it is currently updating
-21470092790x80073D01The package deployment operation is blocked by policy. Please contact your system administrator
-21470092780x80073D02The package could not be installed because resources it modifies are currently in use
-21470092770x80073D03The package could not be recovered because necessary data for recovery have been corrupted
-21470092760x80073D04The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present
-21470092750x80073D05An error occurred while deleting the package's previously existing application data
-21470092740x80073D06The package could not be installed because a higher version of this package is already installed
-21470092730x80073D07An error in a system binary was detected. Try refreshing the PC to fix the problem
-21470092720x80073D08A corrupted CLR NGEN binary was detected on the system
-21470092710x80073D09The operation could not be resumed because necessary data for recovery have been corrupted
-21470092700x80073D0AThe package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again
-21470092690x80073D0BPackage move failed
-21470092680x80073D0CThe deployment operation failed because the volume is not empty
-21470092670x80073D0DThe deployment operation failed because the volume is offline
-21470092660x80073D0EThe deployment operation failed because the specified volume is corrupt
-21470092650x80073D0FThe deployment operation failed because the specified application needs to be registered first
-21470092640x80073D10The deployment operation failed because the package targets the wrong processor architecture
-21470092630x80073D11You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again
-21470091960x80073D54The process has no package identity
-21470091950x80073D55The package runtime information is corrupted
-21470091940x80073D56The package identity is corrupted
-21470091930x80073D57The process has no application identity
-21470091920x80073D58One 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
-21470091910x80073D59One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log
-21470091900x80073D5AThe package is currently not available
-21470090960x80073DB8Loading the state store failed
-21470090950x80073DB9Retrieving the state version for the application failed
-21470090940x80073DBASetting the state version for the application failed
-21470090930x80073DBBResetting the structured state of the application failed
-21470090920x80073DBCState Manager failed to open the container
-21470090910x80073DBDState Manager failed to create the container
-21470090900x80073DBEState Manager failed to delete the container
-21470090890x80073DBFState Manager failed to read the setting
-21470090880x80073DC0State Manager failed to write the setting
-21470090870x80073DC1State Manager failed to delete the setting
-21470090860x80073DC2State Manager failed to query the setting
-21470090850x80073DC3State Manager failed to read the composite setting
-21470090840x80073DC4State Manager failed to write the composite setting
-21470090830x80073DC5State Manager failed to enumerate the containers
-21470090820x80073DC6State Manager failed to enumerate the settings
-21470090810x80073DC7The size of the state manager composite setting value has exceeded the limit
-21470090800x80073DC8The size of the state manager setting value has exceeded the limit
-21470090790x80073DC9The length of the state manager setting name has exceeded the limit
-21470090780x80073DCAThe length of the state manager container name has exceeded the limit
-21470090550x80073DE1This API cannot be used in the context of the caller's application type
-21470090350x80073DF5This PC does not have a valid license for the application or product
-21470090340x80073DF6The authenticated user does not have a valid license for the application or product
-21470090330x80073DF7The commerce transaction associated with this license is still pending verification
-21470090320x80073DF8The license has been revoked for this user
-21469593590x80080001Attempt to create a class object failed
-21469593580x80080002OLE service could not bind object
-21469593570x80080003RPC communication failed with OLE service
-21469593560x80080004Bad path to object
-21469593550x80080005Server execution failed
-21469593540x80080006OLE service could not communicate with the object server
-21469593530x80080007Moniker path could not be normalized
-21469593520x80080008Object server is stopping when OLE service contacts it
-21469593510x80080009An invalid root block pointer was specified
-21469593440x80080010An allocation chain contained an invalid link pointer
-21469593430x80080011The requested allocation size was too large
-21469593390x80080015The activation requires a display name to be present under the CLSID key
-21469593380x80080016The activation requires that the RunAs value for the application is Activate As Activator
-21469593370x80080017The class is not configured to support Elevated activation
-21469588480x80080200Appx packaging API has encountered an internal error
-21469588470x80080201The file is not a valid Appx package because its contents are interleaved
-21469588460x80080202The file is not a valid Appx package because it contains OPC relationships
-21469588450x80080203The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present
-21469588440x80080204The Appx package's manifest is invalid
-21469588430x80080205The Appx package's block map is invalid
-21469588420x80080206The Appx package's content cannot be read because it is corrupt
-21469588410x80080207The computed hash value of the block does not match the one stored in the block map
-21469588400x80080208The requested byte range is over 4GB when translated to byte range of blocks
-21469588390x80080209The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data
-21469588380x8008020AThe APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data
-21469585920x80080300The background task activation is spurious
-21468938230x80090001Bad UID
-21468938220x80090002Bad Hash
-21468938210x80090003Bad Key
-21468938200x80090004Bad Length
-21468938190x80090005Bad Data
-21468938180x80090006Invalid Signature
-21468938170x80090007Bad Version of provider
-21468938160x80090008Invalid algorithm specified
-21468938150x80090009Invalid flags specified
-21468938140x8009000AInvalid type specified
-21468938130x8009000BKey not valid for use in specified state
-21468938120x8009000CHash not valid for use in specified state
-21468938110x8009000DKey does not exist
-21468938100x8009000EInsufficient memory available for the operation
-21468938090x8009000FObject already exists
-21468938080x80090010Access denied
-21468938070x80090011Object was not found
-21468938060x80090012Data already encrypted
-21468938050x80090013Invalid provider specified
-21468938040x80090014Invalid provider type specified
-21468938030x80090015Provider's public key is invalid
-21468938020x80090016Keyset does not exist
-21468938010x80090017Provider type not defined
-21468938000x80090018Provider type as registered is invalid
-21468937990x80090019The keyset is not defined
-21468937980x8009001AKeyset as registered is invalid
-21468937970x8009001BProvider type does not match registered value
-21468937960x8009001CThe digital signature file is corrupt
-21468937950x8009001DProvider DLL failed to initialize correctly
-21468937940x8009001EProvider DLL could not be found
-21468937930x8009001FThe Keyset parameter is invalid
-21468937920x80090020An internal error occurred
-21468937910x80090021A base error occurred
-21468937900x80090022Provider could not perform the action since the context was acquired as silent
-21468937890x80090023The security token does not have storage space available for an additional container
-21468937880x80090024The profile for the user is a temporary profile
-21468937870x80090025The key parameters could not be set because the CSP uses fixed parameters
-21468937860x80090026The supplied handle is invalid
-21468937850x80090027The parameter is incorrect
-21468937840x80090028The buffer supplied to a function was too small
-21468937830x80090029The requested operation is not supported
-21468937820x8009002ANo more data is available
-21468937810x8009002BThe supplied buffers overlap incorrectly
-21468937800x8009002CThe specified data could not be decrypted
-21468937790x8009002DAn internal consistency check failed
-21468937780x8009002EThis operation requires input from the user
-21468937770x8009002FThe cryptographic provider does not support HMAC
-21468937760x80090030The device that is required by this cryptographic provider is not ready for use
-21468937750x80090031The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider
-21468937740x80090032The validation of the provided data failed the integrity or signature validation
-21468937730x80090033Incorrect password
-21468937720x80090034Encryption failed
-21468937710x80090035The device that is required by this cryptographic provider is not found on this platform
-21468937700x80090036The action was cancelled by the user
-21468937690x80090037The password is no longer valid and must be changed
-21468930560x80090300Not enough memory is available to complete this request
-21468930550x80090301The handle specified is invalid
-21468930540x80090302The function requested is not supported
-21468930530x80090303The specified target is unknown or unreachable
-21468930520x80090304The Local Security Authority cannot be contacted
-21468930510x80090305The requested security package does not exist
-21468930500x80090306The caller is not the owner of the desired credentials
-21468930490x80090307The security package failed to initialize, and cannot be installed
-21468930480x80090308The token supplied to the function is invalid
-21468930470x80090309The security package is not able to marshall the logon buffer, so the logon attempt has failed
-21468930460x8009030AThe per-message Quality of Protection is not supported by the security package
-21468930450x8009030BThe security context does not allow impersonation of the client
-21468930440x8009030CThe logon attempt failed
-21468930430x8009030DThe credentials supplied to the package were not recognized
-21468930420x8009030ENo credentials are available in the security package
-21468930410x8009030FThe message or signature supplied for verification has been altered
-21468930400x80090310The message supplied for verification is out of sequence
-21468930390x80090311No authority could be contacted for authentication
-21468930340x80090316The requested security package does not exist
-21468930330x80090317The context has expired and can no longer be used
-21468930320x80090318The supplied message is incomplete. The signature was not verified
-21468930240x80090320The credentials supplied were not complete, and could not be verified. The context could not be initialized
-21468930230x80090321The buffers supplied to a function was too small
-21468930220x80090322The target principal name is incorrect
-21468930200x80090324The clocks on the client and server machines are skewed
-21468930190x80090325The certificate chain was issued by an authority that is not trusted
-21468930180x80090326The message received was unexpected or badly formatted
-21468930170x80090327An unknown error occurred while processing the certificate
-21468930160x80090328The received certificate has expired
-21468930150x80090329The specified data could not be encrypted
-21468930080x80090330The specified data could not be decrypted
-21468930070x80090331The client and server cannot communicate, because they do not possess a common algorithm
-21468930060x80090332The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation)
-21468930050x80090333A security context was deleted before the context was completed. This is considered a logon failure
-21468930040x80090334The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply
-21468930030x80090335Unable to accomplish the requested task because the local machine does not have any IP addresses
-21468930020x80090336The supplied credential handle does not match the credential associated with the security context
-21468930010x80090337The crypto system or checksum function is invalid because a required function is unavailable
-21468930000x80090338The number of maximum ticket referrals has been exceeded
-21468929990x80090339The local machine must be a Kerberos KDC (domain controller) and it is not
-21468929980x8009033AThe other end of the security negotiation is requires strong crypto but it is not supported on the local machine
-21468929970x8009033BThe KDC reply contained more than one principal name
-21468929960x8009033CExpected to find PA data for a hint of what etype to use, but it was not found
-21468929950x8009033DThe client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator
-21468929940x8009033ESmartcard logon is required and was not used
-21468929930x8009033FA system shutdown is in progress
-21468929920x80090340An invalid request was sent to the KDC
-21468929910x80090341The KDC was unable to generate a referral for the service requested
-21468929900x80090342The encryption type requested is not supported by the KDC
-21468929890x80090343An unsupported preauthentication mechanism was presented to the Kerberos package
-21468929870x80090345The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation
-21468929860x80090346Client's supplied SSPI channel bindings were incorrect
-21468929850x80090347The received certificate was mapped to multiple accounts
-21468929840x80090348SEC_E_NO_KERB_KEY
-21468929830x80090349The certificate is not valid for the requested usage
-21468929760x80090350The system cannot contact a domain controller to service the authentication request. Please try again later
-21468929750x80090351The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log
-21468929740x80090352An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator
-21468929730x80090353The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator
-21468929720x80090354The smartcard certificate used for authentication was not trusted. Please contact your system administrator
-21468929710x80090355The smartcard certificate used for authentication has expired. Please contact your system administrator
-21468929700x80090356The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user
-21468929690x80090357An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator
-21468929680x80090358The 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
-21468929670x80090359An 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
-21468929660x8009035AThe domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log
-21468929650x8009035BThe domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log
-21468929630x8009035DOne or more of the parameters passed to the function was invalid
-21468929620x8009035EClient policy does not allow credential delegation to target server
-21468929610x8009035FClient policy does not allow credential delegation to target server with NLTM only authentication
-21468929590x80090361The required security context does not exist
-21468929580x80090362The PKU2U protocol encountered an error while attempting to utilize the associated certificates
-21468929570x80090363The identity of the server computer could not be verified
-21468929550x80090365Only https scheme is allowed
-21468929530x80090367No common application protocol exists between the client and the server. Application protocol negotiation failed
-21468897270x80091001An error occurred while performing an operation on a cryptographic message
-21468897260x80091002Unknown cryptographic algorithm
-21468897250x80091003The object identifier is poorly formatted
-21468897240x80091004Invalid cryptographic message type
-21468897230x80091005Unexpected cryptographic message encoding
-21468897220x80091006The cryptographic message does not contain an expected authenticated attribute
-21468897210x80091007The hash value is not correct
-21468897200x80091008The index value is not valid
-21468897190x80091009The content of the cryptographic message has already been decrypted
-21468897180x8009100AThe content of the cryptographic message has not been decrypted yet
-21468897170x8009100BThe enveloped-data message does not contain the specified recipient
-21468897160x8009100CInvalid control type
-21468897150x8009100DInvalid issuer and/or serial number
-21468897140x8009100ECannot find the original signer
-21468897130x8009100FThe cryptographic message does not contain all of the requested attributes
-21468897120x80091010The streamed cryptographic message is not ready to return data
-21468897110x80091011The streamed cryptographic message requires more data to complete the decode operation
-21468856310x80092001The length specified for the output data was insufficient
-21468856300x80092002An error occurred during encode or decode operation
-21468856290x80092003An error occurred while reading or writing to a file
-21468856280x80092004Cannot find object or property
-21468856270x80092005The object or property already exists
-21468856260x80092006No provider was specified for the store or object
-21468856250x80092007The specified certificate is self signed
-21468856240x80092008The previous certificate or CRL context was deleted
-21468856230x80092009Cannot find the requested object
-21468856220x8009200AThe certificate does not have a property that references a private key
-21468856210x8009200BCannot find the certificate and private key for decryption
-21468856200x8009200CCannot find the certificate and private key to use for decryption
-21468856190x8009200DNot a cryptographic message or the cryptographic message is not formatted correctly
-21468856180x8009200EThe signed cryptographic message does not have a signer for the specified signer index
-21468856170x8009200FFinal closure is pending until additional frees or closes
-21468856160x80092010The certificate is revoked
-21468856150x80092011No Dll or exported function was found to verify revocation
-21468856140x80092012The revocation function was unable to check revocation for the certificate
-21468856130x80092013The revocation function was unable to check revocation because the revocation server was offline
-21468856120x80092014The certificate is not in the revocation server's database
-21468856000x80092020The string contains a non-numeric character
-21468855990x80092021The string contains a non-printable character
-21468855980x80092022The string contains a character not in the 7 bit ASCII character set
-21468855970x80092023The string contains an invalid X500 name attribute key, oid, value or delimiter
-21468855960x80092024The 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
-21468855950x80092025The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done
-21468855940x80092026The cryptographic operation failed due to a local security option setting
-21468855930x80092027No DLL or exported function was found to verify subject usage
-21468855920x80092028The called function was unable to do a usage check on the subject
-21468855910x80092029Since the server was offline, the called function was unable to complete the usage check
-21468855900x8009202AThe subject was not found in a Certificate Trust List (CTL)
-21468855890x8009202BNone of the signers of the cryptographic message or certificate trust list is trusted
-21468855880x8009202CThe public key's algorithm parameters are missing
-21468855870x8009202DAn object could not be located using the object locator infrastructure with the given name
-21468815360x80093000OSS Certificate encode/decode error code base See asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR
-21468815350x80093001OSS ASN.1 Error: Output Buffer is too small
-21468815340x80093002OSS ASN.1 Error: Signed integer is encoded as a unsigned integer
-21468815330x80093003OSS ASN.1 Error: Unknown ASN.1 data type
-21468815320x80093004OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated
-21468815310x80093005OSS ASN.1 Error: Invalid data
-21468815300x80093006OSS ASN.1 Error: Invalid argument
-21468815290x80093007OSS ASN.1 Error: Encode/Decode version mismatch
-21468815280x80093008OSS ASN.1 Error: Out of memory
-21468815270x80093009OSS ASN.1 Error: Encode/Decode Error
-21468815260x8009300AOSS ASN.1 Error: Internal Error
-21468815250x8009300BOSS ASN.1 Error: Invalid data
-21468815240x8009300COSS ASN.1 Error: Invalid data
-21468815230x8009300DOSS ASN.1 Error: Unsupported BER indefinite-length encoding
-21468815220x8009300EOSS ASN.1 Error: Access violation
-21468815210x8009300FOSS ASN.1 Error: Invalid data
-21468815200x80093010OSS ASN.1 Error: Invalid data
-21468815190x80093011OSS ASN.1 Error: Invalid data
-21468815180x80093012OSS ASN.1 Error: Internal Error
-21468815170x80093013OSS ASN.1 Error: Multi-threading conflict
-21468815160x80093014OSS ASN.1 Error: Invalid data
-21468815150x80093015OSS ASN.1 Error: Invalid data
-21468815140x80093016OSS ASN.1 Error: Invalid data
-21468815130x80093017OSS ASN.1 Error: Encode/Decode function not implemented
-21468815120x80093018OSS ASN.1 Error: Trace file error
-21468815110x80093019OSS ASN.1 Error: Function not implemented
-21468815100x8009301AOSS ASN.1 Error: Program link error
-21468815090x8009301BOSS ASN.1 Error: Trace file error
-21468815080x8009301COSS ASN.1 Error: Trace file error
-21468815070x8009301DOSS ASN.1 Error: Invalid data
-21468815060x8009301EOSS ASN.1 Error: Invalid data
-21468815050x8009301FOSS ASN.1 Error: Program link error
-21468815040x80093020OSS ASN.1 Error: Program link error
-21468815030x80093021OSS ASN.1 Error: Program link error
-21468815020x80093022OSS ASN.1 Error: Program link error
-21468815010x80093023OSS ASN.1 Error: Program link error
-21468815000x80093024OSS ASN.1 Error: Program link error
-21468814990x80093025OSS ASN.1 Error: Program link error
-21468814980x80093026OSS ASN.1 Error: Program link error
-21468814970x80093027OSS ASN.1 Error: Program link error
-21468814960x80093028OSS ASN.1 Error: Program link error
-21468814950x80093029OSS ASN.1 Error: Program link error
-21468814940x8009302AOSS ASN.1 Error: Program link error
-21468814930x8009302BOSS ASN.1 Error: Program link error
-21468814920x8009302COSS ASN.1 Error: Program link error
-21468814910x8009302DOSS ASN.1 Error: System resource error
-21468814900x8009302EOSS ASN.1 Error: Trace file error
-21468812800x80093100ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR
-21468812790x80093101ASN1 internal encode or decode error
-21468812780x80093102ASN1 unexpected end of data
-21468812770x80093103ASN1 corrupted data
-21468812760x80093104ASN1 value too large
-21468812750x80093105ASN1 constraint violated
-21468812740x80093106ASN1 out of memory
-21468812730x80093107ASN1 buffer overflow
-21468812720x80093108ASN1 function not supported for this PDU
-21468812710x80093109ASN1 bad arguments to function call
-21468812700x8009310AASN1 bad real value
-21468812690x8009310BASN1 bad tag value met
-21468812680x8009310CASN1 bad choice value
-21468812670x8009310DASN1 bad encoding rule
-21468812660x8009310EASN1 bad unicode (UTF8)
-21468812290x80093133ASN1 bad PDU type
-21468812280x80093134ASN1 not yet implemented
-21468810230x80093201ASN1 skipped unknown extension(s)
-21468810220x80093202ASN1 end of data expected
-21468774390x80094001The request subject name is invalid or too long
-21468774380x80094002The request does not exist
-21468774370x80094003The request's current status does not allow this operation
-21468774360x80094004The requested property value is empty
-21468774350x80094005The certification authority's certificate contains invalid data
-21468774340x80094006Certificate service has been suspended for a database restore operation
-21468774330x80094007The certificate contains an encoded length that is potentially incompatible with older enrollment software
-21468774320x80094008The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation
-21468774310x80094009The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester
-21468774300x8009400ACannot archive private key. The certification authority is not configured for key archival
-21468774290x8009400BCannot archive private key. The certification authority could not verify one or more key recovery certificates
-21468774280x8009400CThe request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature
-21468774270x8009400DAt least one security principal must have the permission to manage this CA
-21468774260x8009400EThe request contains an invalid renewal certificate attribute
-21468774250x8009400FAn attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions
-21468774240x80094010A memory reference caused a data alignment fault
-21468774230x80094011The permissions on this certification authority do not allow the current user to enroll for certificates
-21468774220x80094012The permissions on the certificate template do not allow the current user to enroll for this type of certificate
-21468774210x80094013The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access
-21468774200x80094014The request was denied by a certificate manager or CA administrator
-21468774190x80094015An enrollment policy server cannot be located
-21468774180x80094016A signature algorithm or public key length does not meet the system's minimum required strength
-21468774170x80094017Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation
-21468774160x80094018No encryption certificate was specified
-21468753920x80094800The requested certificate template is not supported by this CA
-21468753910x80094801The request contains no certificate template information
-21468753900x80094802The request contains conflicting template information
-21468753890x80094803The request is missing a required Subject Alternate name extension
-21468753880x80094804The request is missing a required private key for archival by the server
-21468753870x80094805The request is missing a required SMIME capabilities extension
-21468753860x80094806The 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
-21468753850x80094807The request template version is newer than the supported template version
-21468753840x80094808The template is missing a required signature policy attribute
-21468753830x80094809The request is missing required signature policy information
-21468753820x8009480AThe request is missing one or more required signatures
-21468753810x8009480BOne or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures
-21468753800x8009480CThe request is missing one or more required signature issuance policies
-21468753790x8009480DThe UPN is unavailable and cannot be added to the Subject Alternate name
-21468753780x8009480EThe Active Directory GUID is unavailable and cannot be added to the Subject Alternate name
-21468753770x8009480FThe DNS name is unavailable and cannot be added to the Subject Alternate name
-21468753760x80094810The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template
-21468753750x80094811The public key does not meet the minimum size required by the specified certificate template
-21468753740x80094812The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name
-21468753730x80094813One or more certificate templates to be enabled on this certification authority could not be found
-21468753720x80094814The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed
-21468753710x80094815The certificate template requires too many RA signatures. Only one RA signature is allowed
-21468753700x80094816The certificate template requires renewal with the same public key, but the request uses a different public key
-21468753690x80094817The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent
-21468753680x80094818The certification authority cannot validate the Attestation Identity Key Id Binding
-21468753670x80094819The certification authority cannot validate the private key attestation data
-21468753660x8009481AThe request does not support private key attestation as defined in the certificate template
-21468753650x8009481BThe request public key is not consistent with the private key attestation data
-21468753640x8009481CThe private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable
-21468753630x8009481DThe attestation response could not be validated. It is either unexpected or incorrect
-21468753620x8009481EA valid Request ID was not detected in the request attributes, or an invalid one was submitted
-21468733440x80095000The key is not exportable
-21468733430x80095001You cannot add the root CA certificate into your local store
-21468733420x80095002The key archival hash attribute was not found in the response
-21468733410x80095003An unexpected key archival hash attribute was found in the response
-21468733400x80095004There is a key archival hash mismatch between the request and the response
-21468733390x80095005Signing certificate cannot include SMIME extension
-21468692470x80096001A system-level error occurred while verifying trust
-21468692460x80096002The certificate for the signer of the message is invalid or not found
-21468692450x80096003One of the counter signatures was invalid
-21468692440x80096004The signature of the certificate cannot be verified
-21468692430x80096005The timestamp signature and/or certificate could not be verified or is malformed
-21468692320x80096010The digital signature of the object did not verify
-21468692310x80096011The digital signature of the object is malformed. For technical detail, see security bulletin MS13-098
-21468692230x80096019A certificate's basic constraint extension has not been observed
-21468692180x8009601EThe certificate does not meet or contain the Authenticode(tm) financial extensions
-21468651510x80097001Tried to reference a part of the file outside the proper range
-21468651500x80097002Could not retrieve an object from the file
-21468651490x80097003Could not find the head table in the file
-21468651480x80097004The magic number in the head table is incorrect
-21468651470x80097005The offset table has incorrect values
-21468651460x80097006Duplicate table tags or tags out of alphabetical order
-21468651450x80097007A table does not start on a long word boundary
-21468651440x80097008First table does not appear after header information
-21468651430x80097009Two or more tables overlap
-21468651420x8009700AToo many pad bytes between tables or pad bytes are not 0
-21468651410x8009700BFile is too small to contain the last table
-21468651400x8009700CA table checksum is incorrect
-21468651390x8009700DThe file checksum is incorrect
-21468651360x80097010The signature does not have the correct attributes for the policy
-21468651350x80097011The file did not pass the hints check
-21468651340x80097012The file is not an OpenType file
-21468651330x80097013Failed on a file operation (open, map, read, write)
-21468651320x80097014A call to a CryptoAPI function failed
-21468651310x80097015There is a bad version number in the file
-21468651300x80097016The structure of the DSIG table is incorrect
-21468651290x80097017A check failed in a partially constant table
-21468651280x80097018Some kind of structural error
-21468651270x80097019The requested credential requires confirmation
-21467627510x800B0001Unknown trust provider
-21467627500x800B0002The trust verification action specified is not supported by the specified trust provider
-21467627490x800B0003The form specified for the subject is not one supported or known by the specified trust provider
-21467627480x800B0004The subject is not trusted for the specified action
-21467627470x800B0005Error due to problem in ASN.1 encoding process
-21467627460x800B0006Error due to problem in ASN.1 decoding process
-21467627450x800B0007Reading / writing Extensions where Attributes are appropriate, and vice versa
-21467627440x800B0008Unspecified cryptographic failure
-21467627430x800B0009The size of the data could not be determined
-21467627420x800B000AThe size of the indefinite-sized data could not be determined
-21467627410x800B000BThis object does not read and write self-sizing data
-21467624960x800B0100No signature was present in the subject
-21467624950x800B0101A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file
-21467624940x800B0102The validity periods of the certification chain do not nest correctly
-21467624930x800B0103A certificate that can only be used as an end-entity is being used as a CA or vice versa
-21467624920x800B0104A path length constraint in the certification chain has been violated
-21467624910x800B0105A certificate contains an unknown extension that is marked 'critical'
-21467624900x800B0106A certificate being used for a purpose other than the ones specified by its CA
-21467624890x800B0107A parent of a given certificate in fact did not issue that child certificate
-21467624880x800B0108A certificate is missing or has an empty value for an important field, such as a subject or issuer name
-21467624870x800B0109A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider
-21467624860x800B010AA certificate chain could not be built to a trusted root authority
-21467624850x800B010BGeneric trust failure
-21467624840x800B010CA certificate was explicitly revoked by its issuer
-21467624830x800B010DThe certification path terminates with the test root which is not trusted with the current policy settings
-21467624820x800B010EThe revocation process could not continue - the certificate(s) could not be checked
-21467624810x800B010FThe certificate's CN name does not match the passed value
-21467624800x800B0110The certificate is not valid for the requested usage
-21467624790x800B0111The certificate was explicitly marked as untrusted by the user
-21467624780x800B0112A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider
-21467624770x800B0113The certificate has invalid policy
-21467624760x800B0114The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded
-21466972140x800C0002The URL is invalid
-21466972130x800C0003No Internet session has been established
-21466972120x800C0004Unable to connect to the target server
-21466972110x800C0005The system cannot locate the resource specified
-21466972100x800C0006The system cannot locate the object specified
-21466972090x800C0007No data is available for the requested resource
-21466972080x800C0008The download of the specified resource has failed
-21466972070x800C0009Authentication is required to access this resource
-21466972060x800C000AThe server could not recognize the provided mime type
-21466972050x800C000BThe operation was timed out
-21466972040x800C000CThe server did not understand the request, or the request was invalid
-21466972030x800C000DThe specified protocol is unknown
-21466972020x800C000EA security problem occurred
-21466972010x800C000FThe system could not load the persisted data
-21466972000x800C0010Unable to instantiate the object
-21466971960x800C0014A redirection problem occurred
-21466971950x800C0015The requested resource is a directory, not a file
-21466971910x800C0019Security certificate required to access this resource is invalid
-21465006080x800F0000A non-empty line was encountered in the INF before the start of a section
-21465006070x800F0001A section name marker in the INF is not complete, or does not exist on a line by itself
-21465006060x800F0002An INF section was encountered whose name exceeds the maximum section name length
-21465006050x800F0003The syntax of the INF is invalid
-21465003520x800F0100The style of the INF is different than what was requested
-21465003510x800F0101The required section was not found in the INF
-21465003500x800F0102The required line was not found in the INF
-21465003490x800F0103The files affected by the installation of this file queue have not been backed up for uninstall
-21465000960x800F0200The INF or the device information set or element does not have an associated install class
-21465000950x800F0201The INF or the device information set or element does not match the specified install class
-21465000940x800F0202An existing device was found that is a duplicate of the device being manually installed
-21465000930x800F0203There is no driver selected for the device information set or element
-21465000920x800F0204The requested device registry key does not exist
-21465000910x800F0205The device instance name is invalid
-21465000900x800F0206The install class is not present or is invalid
-21465000890x800F0207The device instance cannot be created because it already exists
-21465000880x800F0208The operation cannot be performed on a device information element that has not been registered
-21465000870x800F0209The device property code is invalid
-21465000860x800F020AThe INF from which a driver list is to be built does not exist
-21465000850x800F020BThe device instance does not exist in the hardware tree
-21465000840x800F020CThe icon representing this install class cannot be loaded
-21465000830x800F020DThe class installer registry entry is invalid
-21465000820x800F020EThe class installer has indicated that the default action should be performed for this installation request
-21465000810x800F020FThe operation does not require any files to be copied
-21465000800x800F0210The specified hardware profile does not exist
-21465000790x800F0211There is no device information element currently selected for this device information set
-21465000780x800F0212The operation cannot be performed because the device information set is locked
-21465000770x800F0213The operation cannot be performed because the device information element is locked
-21465000760x800F0214The specified path does not contain any applicable device INFs
-21465000750x800F0215No class installer parameters have been set for the device information set or element
-21465000740x800F0216The operation cannot be performed because the file queue is locked
-21465000730x800F0217A service installation section in this INF is invalid
-21465000720x800F0218There is no class driver list for the device information element
-21465000710x800F0219The installation failed because a function driver was not specified for this device instance
-21465000700x800F021AThere is presently no default device interface designated for this interface class
-21465000690x800F021BThe operation cannot be performed because the device interface is currently active
-21465000680x800F021CThe operation cannot be performed because the device interface has been removed from the system
-21465000670x800F021DAn interface installation section in this INF is invalid
-21465000660x800F021EThis interface class does not exist in the system
-21465000650x800F021FThe reference string supplied for this interface device is invalid
-21465000640x800F0220The specified machine name does not conform to UNC naming conventions
-21465000630x800F0221A general remote communication error occurred
-21465000620x800F0222The machine selected for remote communication is not available at this time
-21465000610x800F0223The Plug and Play service is not available on the remote machine
-21465000600x800F0224The property page provider registry entry is invalid
-21465000590x800F0225The requested device interface is not present in the system
-21465000580x800F0226The device's co-installer has additional work to perform after installation is complete
-21465000570x800F0227The device's co-installer is invalid
-21465000560x800F0228There are no compatible drivers for this device
-21465000550x800F0229There is no icon that represents this device or device type
-21465000540x800F022AA logical configuration specified in this INF is invalid
-21465000530x800F022BThe class installer has denied the request to install or upgrade this device
-21465000520x800F022COne of the filter drivers installed for this device is invalid
-21465000510x800F022DThe driver selected for this device does not support this version of Windows
-21465000500x800F022EThe driver selected for this device does not support Windows
-21465000490x800F022FThe third-party INF does not contain digital signature information
-21465000480x800F0230An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms
-21465000470x800F0231The device cannot be disabled
-21465000460x800F0232The device could not be dynamically removed
-21465000450x800F0233Cannot copy to specified target
-21465000440x800F0234Driver is not intended for this platform
-21465000430x800F0235Operation not allowed in WOW64
-21465000420x800F0236The operation involving unsigned file copying was rolled back, so that a system restore point could be set
-21465000410x800F0237An INF was copied into the Windows INF directory in an improper manner
-21465000400x800F0238The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product
-21465000390x800F0239An unknown exception was encountered
-21465000380x800F023AA problem was encountered when accessing the Plug and Play registry database
-21465000370x800F023BThe requested operation is not supported for a remote machine
-21465000360x800F023CThe specified file is not an installed OEM INF
-21465000350x800F023DOne or more devices are presently installed using the specified INF
-21465000340x800F023EThe requested device install operation is obsolete
-21465000330x800F023FA file could not be verified because it does not have an associated catalog signed via Authenticode(tm)
-21465000320x800F0240Authenticode(tm) signature verification is not supported for the specified INF
-21465000310x800F0241The INF was signed with an Authenticode(tm) catalog from a trusted publisher
-21465000300x800F0242The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted
-21465000290x800F0243The publisher of an Authenticode(tm) signed catalog was not established as trusted
-21465000280x800F0244The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version
-21465000270x800F0245The file may only be validated by a catalog signed via Authenticode(tm)
-21465000260x800F0246One of the installers for this device cannot perform the installation at this time
-21465000250x800F0247A problem was encountered while attempting to add the driver to the store
-21465000240x800F0248The installation of this device is forbidden by system policy. Contact your system administrator
-21465000230x800F0249The installation of this driver is forbidden by system policy. Contact your system administrator
-21465000220x800F024AThe specified INF is the wrong type for this operation
-21465000210x800F024BThe hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering
-21465000200x800F024CA problem was encountered while attempting to delete the driver from the store
-21464998400x800F0300An unrecoverable stack overflow was encountered
-21464965120x800F1000No installed components were detected
-21464350710x80100001An internal consistency check failed
-21464350700x80100002The action was cancelled by an SCardCancel request
-21464350690x80100003The supplied handle was invalid
-21464350680x80100004One or more of the supplied parameters could not be properly interpreted
-21464350670x80100005Registry startup information is missing or invalid
-21464350660x80100006Not enough memory available to complete this command
-21464350650x80100007An internal consistency timer has expired
-21464350640x80100008The data buffer to receive returned data is too small for the returned data
-21464350630x80100009The specified reader name is not recognized
-21464350620x8010000AThe user-specified timeout value has expired
-21464350610x8010000BThe smart card cannot be accessed because of other connections outstanding
-21464350600x8010000CThe operation requires a smart card, but no smart card is currently in the device
-21464350590x8010000DThe specified smart card name is not recognized
-21464350580x8010000EThe system could not dispose of the media in the requested manner
-21464350570x8010000FThe requested protocols are incompatible with the protocol currently in use with the smart card
-21464350560x80100010The reader or smart card is not ready to accept commands
-21464350550x80100011One or more of the supplied parameters values could not be properly interpreted
-21464350540x80100012The action was cancelled by the system, presumably to log off or shut down
-21464350530x80100013An internal communications error has been detected
-21464350520x80100014An internal error has been detected, but the source is unknown
-21464350510x80100015An ATR obtained from the registry is not a valid ATR string
-21464350500x80100016An attempt was made to end a non-existent transaction
-21464350490x80100017The specified reader is not currently available for use
-21464350480x80100018The operation has been aborted to allow the server application to exit
-21464350470x80100019The PCI Receive buffer was too small
-21464350460x8010001AThe reader driver does not meet minimal requirements for support
-21464350450x8010001BThe reader driver did not produce a unique reader name
-21464350440x8010001CThe smart card does not meet minimal requirements for support
-21464350430x8010001DThe Smart Card Resource Manager is not running
-21464350420x8010001EThe Smart Card Resource Manager has shut down
-21464350410x8010001FAn unexpected card error has occurred
-21464350400x80100020No Primary Provider can be found for the smart card
-21464350390x80100021The requested order of object creation is not supported
-21464350380x80100022This smart card does not support the requested feature
-21464350370x80100023The identified directory does not exist in the smart card
-21464350360x80100024The identified file does not exist in the smart card
-21464350350x80100025The supplied path does not represent a smart card directory
-21464350340x80100026The supplied path does not represent a smart card file
-21464350330x80100027Access is denied to this file
-21464350320x80100028The smart card does not have enough memory to store the information
-21464350310x80100029There was an error trying to set the smart card file object pointer
-21464350300x8010002AThe supplied PIN is incorrect
-21464350290x8010002BAn unrecognized error code was returned from a layered component
-21464350280x8010002CThe requested certificate does not exist
-21464350270x8010002DThe requested certificate could not be obtained
-21464350260x8010002ECannot find a smart card reader
-21464350250x8010002FA communications error with the smart card has been detected. Retry the operation
-21464350240x80100030The requested key container does not exist on the smart card
-21464350230x80100031The Smart Card Resource Manager is too busy to complete this operation
-21464350220x80100032The smart card PIN cache has expired
-21464350210x80100033The smart card PIN cannot be cached
-21464350200x80100034The smart card is read only and cannot be written to
-21464349710x80100065The reader cannot communicate with the smart card, due to ATR configuration conflicts
-21464349700x80100066The smart card is not responding to a reset
-21464349690x80100067Power has been removed from the smart card, so that further communication is not possible
-21464349680x80100068The smart card has been reset, so any shared state information is invalid
-21464349670x80100069The smart card has been removed, so that further communication is not possible
-21464349660x8010006AAccess was denied because of a security violation
-21464349650x8010006BThe card cannot be accessed because the wrong PIN was presented
-21464349640x8010006CThe card cannot be accessed because the maximum number of PIN entry attempts has been reached
-21464349630x8010006DThe end of the smart card file has been reached
-21464349620x8010006EThe action was cancelled by the user
-21464349610x8010006FNo PIN was presented to the smart card
-21464349600x80100070The requested item could not be found in the cache
-21464349590x80100071The requested cache item is too old and was deleted from the cache
-21464349580x80100072The new cache item exceeds the maximum per-item size defined for the cache
-21463685110x80110401Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail
-21463685100x80110402One or more of the object's properties are missing or invalid
-21463685090x80110403The object was not found in the catalog
-21463685080x80110404The object is already registered
-21463685050x80110407Error occurred writing to the application file
-21463685040x80110408Error occurred reading the application file
-21463685030x80110409Invalid version number in application file
-21463685020x8011040AThe file path is invalid
-21463685010x8011040BThe application is already installed
-21463685000x8011040CThe role already exists
-21463684990x8011040DAn error occurred copying the file
-21463684970x8011040FOne or more users are not valid
-21463684960x80110410One or more users in the application file are not valid
-21463684950x80110411The component's CLSID is missing or corrupt
-21463684940x80110412The component's progID is missing or corrupt
-21463684930x80110413Unable to set required authentication level for update request
-21463684920x80110414The identity or password set on the application is not valid
-21463684880x80110418Application file CLSIDs or IIDs do not match corresponding DLLs
-21463684870x80110419Interface information is either missing or changed
-21463684860x8011041ADllRegisterServer failed on component install
-21463684850x8011041BNo server file share available
-21463684830x8011041DDLL could not be loaded
-21463684820x8011041EThe registered TypeLib ID is not valid
-21463684810x8011041FApplication install directory not found
-21463684770x80110423Errors occurred while in the component registrar
-21463684760x80110424The file does not exist
-21463684750x80110425The DLL could not be loaded
-21463684740x80110426GetClassObject failed in the DLL
-21463684730x80110427The DLL does not support the components listed in the TypeLib
-21463684720x80110428The TypeLib could not be loaded
-21463684710x80110429The file does not contain components or component information
-21463684700x8011042AChanges to this object and its sub-objects have been disabled
-21463684690x8011042BThe delete function has been disabled for this object
-21463684680x8011042CThe server catalog version is not supported
-21463684670x8011042DThe component move was disallowed, because the source or destination application is either a system application or currently locked against changes
-21463684660x8011042EThe component move failed because the destination application no longer exists
-21463684640x80110430The system was unable to register the TypeLib
-21463684610x80110433This operation cannot be performed on the system application
-21463684600x80110434The component registrar referenced in this file is not available
-21463684590x80110435A component in the same DLL is already installed
-21463684580x80110436The service is not installed
-21463684570x80110437One or more property settings are either invalid or in conflict with each other
-21463684560x80110438The object you are attempting to add or rename already exists
-21463684550x80110439The component already exists
-21463684530x8011043BThe registration file is corrupt
-21463684520x8011043CThe property value is too large
-21463684500x8011043EObject was not found in registry
-21463684490x8011043FThis object is not poolable
-21463684420x80110446A CLSID with the same GUID as the new application ID is already installed on this machine
-21463684410x80110447A role assigned to a component, interface, or method did not exist in the application
-21463684400x80110448You must have components in an application in order to start the application
-21463684390x80110449This operation is not enabled on this platform
-21463684380x8011044AApplication Proxy is not exportable
-21463684370x8011044BFailed to start application because it is either a library application or an application proxy
-21463684360x8011044CSystem application is not exportable
-21463684350x8011044DCannot subscribe to this component (the component may have been imported)
-21463684340x8011044EAn event class cannot also be a subscriber component
-21463684330x8011044FLibrary applications and application proxies are incompatible
-21463684320x80110450This function is valid for the base partition only
-21463684310x80110451You cannot start an application that has been disabled
-21463684250x80110457The specified partition name is already in use on this computer
-21463684240x80110458The specified partition name is invalid. Check that the name contains at least one visible character
-21463684230x80110459The partition cannot be deleted because it is the default partition for one or more users
-21463684220x8011045AThe partition cannot be exported, because one or more components in the partition have the same file name
-21463684210x8011045BApplications that contain one or more imported components cannot be installed into a non-base partition
-21463684200x8011045CThe application name is not unique and cannot be resolved to an application id
-21463684190x8011045DThe partition name is not unique and cannot be resolved to a partition id
-21463683980x80110472The COM+ registry database has not been initialized
-21463683970x80110473The COM+ registry database is not open
-21463683960x80110474The COM+ registry database detected a system error
-21463683950x80110475The COM+ registry database is already running
-21463683840x80110480This version of the COM+ registry database cannot be migrated
-21463683830x80110481The schema version to be migrated could not be found in the COM+ registry database
-21463683820x80110482There was a type mismatch between binaries
-21463683810x80110483A binary of unknown or invalid type was provided
-21463683800x80110484There was a type mismatch between a binary and an application
-21463683790x80110485The application cannot be paused or resumed
-21463683780x80110486The COM+ Catalog Server threw an exception during execution
-21463680000x80110600Only COM+ Applications marked queued"" can be invoked using the ""queue"" moniker""
-21463679990x80110601At least one interface must be marked queued"" in order to create a queued component instance with the ""queue"" moniker""
-21463679980x80110602MSMQ is required for the requested operation and is not installed
-21463679970x80110603Unable to marshal an interface that does not support IPersistStream
-21463679960x80110604The message is improperly formatted or was damaged in transit
-21463679950x80110605An unauthenticated message was received by an application that accepts only authenticated messages
-21463679940x80110606The message was requeued or moved by a user not in the QC Trusted User"" role""
-21463677430x80110701Cannot create a duplicate resource of type Distributed Transaction Coordinator
-21463674800x80110808One of the objects being inserted or updated does not belong to a valid parent collection
-21463674790x80110809One of the specified objects cannot be found
-21463674780x8011080AThe specified application is not currently running
-21463674770x8011080BThe partition(s) specified are not valid
-21463674750x8011080DCOM+ applications that run as NT service may not be pooled or recycled
-21463674740x8011080EOne or more users are already assigned to a local partition set
-21463674730x8011080FLibrary applications may not be recycled
-21463674710x80110811Applications running as NT services may not be recycled
-21463674700x80110812The process has already been recycled
-21463674690x80110813A paused process may not be recycled
-21463674680x80110814Library applications may not be NT services
-21463674670x80110815The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID
-21463674660x80110816The partition specified as default is not a member of the partition set
-21463674650x80110817A recycled process may not be paused
-21463674640x80110818Access to the specified partition is denied
-21463674630x80110819Only Application Files (*.MSI files) can be installed into partitions
-21463674620x8011081AApplications containing one or more legacy components may not be exported to 1.0 format
-21463674610x8011081BLegacy components may not exist in non-base partitions
-21463674600x8011081CA component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application
-21463674590x8011081DA component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application
-21463674580x8011081EA private component cannot be moved (or copied) to a library application or to the base partition
-21463674570x8011081FThe Base Application Partition exists in all partition sets and cannot be removed
-21463674560x80110820Alas, Event Class components cannot be aliased
-21463674550x80110821Access is denied because the component is private
-21463674540x80110822The specified SAFER level is invalid
-21463674530x80110823The specified user cannot write to the system registry
-21463674520x80110824COM+ partitions are currently disabled
-21458452470x80190001Unexpected HTTP status code
-21458452450x80190003Unexpected redirection status code (3xx)
-21458452440x80190004Unexpected client error status code (4xx)
-21458452430x80190005Unexpected server error status code (5xx)
-21458449480x8019012CMultiple choices (300)
-21458449470x8019012DMoved permanently (301)
-21458449460x8019012EFound (302)
-21458449450x8019012FSee Other (303)
-21458449440x80190130Not modified (304)
-21458449430x80190131Use proxy (305)
-21458449410x80190133Temporary redirect (307)
-21458448480x80190190Bad request (400)
-21458448470x80190191Unauthorized (401)
-21458448460x80190192Payment required (402)
-21458448450x80190193Forbidden (403)
-21458448440x80190194Not found (404)
-21458448430x80190195Method not allowed (405)
-21458448420x80190196Not acceptable (406)
-21458448410x80190197Proxy authentication required (407)
-21458448400x80190198Request timeout (408)
-21458448390x80190199Conflict (409)
-21458448380x8019019AGone (410)
-21458448370x8019019BLength required (411)
-21458448360x8019019CPrecondition failed (412)
-21458448350x8019019DRequest entity too large (413)
-21458448340x8019019ERequest-URI too long (414)
-21458448330x8019019FUnsupported media type (415)
-21458448320x801901A0Requested range not satisfiable (416)
-21458448310x801901A1Expectation failed (417)
-21458447480x801901F4Internal server error (500)
-21458447470x801901F5Not implemented (501)
-21458447460x801901F6Bad gateway (502)
-21458447450x801901F7Service unavailable (503)
-21458447440x801901F8Gateway timeout (504)
-21458447430x801901F9Version not supported (505)
-21456814080x801B8000Crash reporting failed
-21456814070x801B8001Report aborted due to user cancelation
-21456814060x801B8002Report aborted due to network failure
-21456814050x801B8003Report not initialized
-21456814040x801B8004Reporting is already in progress for the specified process
-21456814030x801B8005Dump not generated due to a throttle
-21454520310x801F0001A handler was not defined by the filter for this operation
-21454520300x801F0002A context is already defined for this object
-21454520290x801F0003Asynchronous requests are not valid for this operation
-21454520280x801F0004Disallow the Fast IO path for this operation
-21454520270x801F0005An invalid name request was made. The name requested cannot be retrieved at this time
-21454520260x801F0006Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock
-21454520250x801F0007The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver
-21454520240x801F0008The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called)
-21454520230x801F0009The 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
-21454520220x801F000AThe Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback
-21454520210x801F000BThe object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time
-21454520200x801F000CNon-paged pool must be used for this type of context
-21454520190x801F000DA duplicate handler definition has been provided for an operation
-21454520180x801F000EThe callback data queue has been disabled
-21454520170x801F000FDo not attach the filter to the volume at this time
-21454520160x801F0010Do not detach the filter from the volume at this time
-21454520150x801F0011An instance already exists at this altitude on the volume specified
-21454520140x801F0012An instance already exists with this name on the volume specified
-21454520130x801F0013The system could not find the filter specified
-21454520120x801F0014The system could not find the volume specified
-21454520110x801F0015The system could not find the instance specified
-21454520100x801F0016No registered context allocation definition was found for the given request
-21454520090x801F0017An invalid parameter was specified during context registration
-21454520080x801F0018The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system
-21454520070x801F0019The requested device object does not exist for the given volume
-21454520060x801F001AThe specified volume is already mounted
-21454520050x801F001BThe specified Transaction Context is already enlisted in a transaction
-21454520040x801F001CThe specifiec context is already attached to another object
-21454520000x801F0020No waiter is present for the filter's reply to this message
-21454519970x801F0023The filesystem database resource is in use. Registration cannot complete at this time
-21449932790x80260001{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
-21449809910x80263001{Desktop composition is disabled} The operation could not be completed because desktop composition is disabled
-21449809900x80263002{Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session
-21449809890x80263003{No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present
-21449809880x80263004{DWM is not queuing presents for the specified window} The window specified is not currently using queued presents
-21449809870x80263005{The adapter specified by the LUID is not found} DWM can not find the adapter specified by the LUID
-21449809850x80263007{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
-21449277430x80270001The NAP SoH packet is invalid
-21449277420x80270002An SoH was missing from the NAP packet
-21449277410x80270003The entity ID conflicts with an already registered id
-21449277400x80270004No cached SoH is present
-21449277390x80270005The entity is still bound to the NAP system
-21449277380x80270006The entity is not registered with the NAP system
-21449277370x80270007The entity is not initialized with the NAP system
-21449277360x80270008The correlation id in the SoH-Request and SoH-Response do not match up
-21449277350x80270009Completion was indicated on a request that is not currently pending
-21449277340x8027000AThe NAP component's id was not found
-21449277330x8027000BThe maximum size of the connection is too small for an SoH packet
-21449277320x8027000CThe NapAgent service is not running
-21449277300x8027000EThe entity is disabled with the NapAgent service
-21449277290x8027000FGroup Policy is not configured
-21449277280x80270010Too many simultaneous calls
-21449277270x80270011SHV configuration already existed
-21449277260x80270012SHV configuration is not found
-21449277250x80270013SHV timed out on the request
-21449272000x80270220The maximum number of items for the access list has been reached. An item must be removed before another item is added
-21449271980x80270222Cannot access Homegroup. Homegroup may not be set up or may have encountered an error
-21449271520x80270250This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again
-21449271510x80270251This app can't be activated from an elevated context
-21449271500x80270252This app can't be activated when UAC is disabled
-21449271490x80270253This app can't be activated by the Built-in Administrator
-21449271480x80270254This app does not support the contract specified or is not installed
-21449271470x80270255This app has mulitple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous
-21449271460x80270256This app's package family has more than one package installed. This is not supported
-21449271450x80270257The app manager is required to activate applications, but is not running
-21449271420x8027025AThe app didn't start in the required time
-21449271410x8027025BThe app didn't start
-21449271400x8027025CThis app failed to launch because of an issue with its license. Please try again in a moment
-21449271390x8027025DThis app failed to launch because its trial license has expired
-21449271360x80270260Please choose a folder on a drive that's formatted with the NTFS file system
-21449271350x80270261This location is already being used. Please choose a different location
-21449271340x80270262This location cannot be indexed. Please choose a different location
-21449271330x80270263Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later
-21449271320x80270264Sorry, the action couldn't be completed
-21449271310x80270265This content can only be moved to a folder. To move the content to this drive, please choose or create a folder
-21448622080x80280000This is an error mask to convert TPM hardware errors to win errors
-21448622070x80280001Authentication failed
-21448622060x80280002The index to a PCR, DIR or other register is incorrect
-21448622050x80280003One or more parameter is bad
-21448622040x80280004An operation completed successfully but the auditing of that operation failed
-21448622030x80280005The clear disable flag is set and all clear operations now require physical access
-21448622020x80280006Activate the Trusted Platform Module (TPM)
-21448622010x80280007Enable the Trusted Platform Module (TPM)
-21448622000x80280008The target command has been disabled
-21448621990x80280009The operation failed
-21448621980x8028000AThe ordinal was unknown or inconsistent
-21448621970x8028000BThe ability to install an owner is disabled
-21448621960x8028000CThe key handle cannot be interpreted
-21448621950x8028000DThe key handle points to an invalid key
-21448621940x8028000EUnacceptable encryption scheme
-21448621930x8028000FMigration authorization failed
-21448621920x80280010PCR information could not be interpreted
-21448621910x80280011No room to load key
-21448621900x80280012There is no Storage Root Key (SRK) set
-21448621890x80280013An encrypted blob is invalid or was not created by this TPM
-21448621880x80280014The Trusted Platform Module (TPM) already has an owner
-21448621870x80280015The TPM has insufficient internal resources to perform the requested action
-21448621860x80280016A random string was too short
-21448621850x80280017The TPM does not have the space to perform the operation
-21448621840x80280018The named PCR value does not match the current PCR value
-21448621830x80280019The paramSize argument to the command has the incorrect value
-21448621820x8028001AThere is no existing SHA-1 thread
-21448621810x8028001BThe calculation is unable to proceed because the existing SHA-1 thread has already encountered an error
-21448621800x8028001CThe TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, check for the latest BIOS or firmware update for your TPM hardware. Consult the computer manufacturer's documentation for instructions
-21448621790x8028001DThe authorization for the second key in a 2 key function failed authorization
-21448621780x8028001EThe tag value sent to for a command is invalid
-21448621770x8028001FAn IO error occurred transmitting information to the TPM
-21448621760x80280020The encryption process had a problem
-21448621750x80280021The decryption process did not complete
-21448621740x80280022An invalid handle was used
-21448621730x80280023The TPM does not have an Endorsement Key (EK) installed
-21448621720x80280024The usage of a key is not allowed
-21448621710x80280025The submitted entity type is not allowed
-21448621700x80280026The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup
-21448621690x80280027Signed data cannot include additional DER information
-21448621680x80280028The key properties in TPM_KEY_PARMs are not supported by this TPM
-21448621670x80280029The migration properties of this key are incorrect
-21448621660x8028002AThe signature or encryption scheme for this key is incorrect or not permitted in this situation
-21448621650x8028002BThe size of the data (or blob) parameter is bad or inconsistent with the referenced key
-21448621640x8028002CA mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob
-21448621630x8028002DEither the physicalPresence or physicalPresenceLock bits have the wrong value
-21448621620x8028002EThe TPM cannot perform this version of the capability
-21448621610x8028002FThe TPM does not allow for wrapped transport sessions
-21448621600x80280030TPM audit construction failed and the underlying command was returning a failure code also
-21448621590x80280031TPM audit construction failed and the underlying command was returning success
-21448621580x80280032Attempt to reset a PCR register that does not have the resettable attribute
-21448621570x80280033Attempt to reset a PCR register that requires locality and locality modifier not part of command transport
-21448621560x80280034Make identity blob not properly typed
-21448621550x80280035When saving context identified resource type does not match actual resource
-21448621540x80280036The TPM is attempting to execute a command only available when in FIPS mode
-21448621530x80280037The command is attempting to use an invalid family ID
-21448621520x80280038The permission to manipulate the NV storage is not available
-21448621510x80280039The operation requires a signed command
-21448621500x8028003AWrong operation to load an NV key
-21448621490x8028003BNV_LoadKey blob requires both owner and blob authorization
-21448621480x8028003CThe NV area is locked and not writtable
-21448621470x8028003DThe locality is incorrect for the attempted operation
-21448621460x8028003EThe NV area is read only and can't be written to
-21448621450x8028003FThere is no protection on the write to the NV area
-21448621440x80280040The family count value does not match
-21448621430x80280041The NV area has already been written to
-21448621420x80280042The NV area attributes conflict
-21448621410x80280043The structure tag and version are invalid or inconsistent
-21448621400x80280044The key is under control of the TPM Owner and can only be evicted by the TPM Owner
-21448621390x80280045The counter handle is incorrect
-21448621380x80280046The write is not a complete write of the area
-21448621370x80280047The gap between saved context counts is too large
-21448621360x80280048The maximum number of NV writes without an owner has been exceeded
-21448621350x80280049No operator AuthData value is set
-21448621340x8028004AThe resource pointed to by context is not loaded
-21448621330x8028004BThe delegate administration is locked
-21448621320x8028004CAttempt to manage a family other then the delegated family
-21448621310x8028004DDelegation table management not enabled
-21448621300x8028004EThere was a command executed outside of an exclusive transport session
-21448621290x8028004FAttempt to context save a owner evict controlled key
-21448621280x80280050The DAA command has no resources availble to execute the command
-21448621270x80280051The consistency check on DAA parameter inputData0 has failed
-21448621260x80280052The consistency check on DAA parameter inputData1 has failed
-21448621250x80280053The consistency check on DAA_issuerSettings has failed
-21448621240x80280054The consistency check on DAA_tpmSpecific has failed
-21448621230x80280055The atomic process indicated by the submitted DAA command is not the expected process
-21448621220x80280056The issuer's validity check has detected an inconsistency
-21448621210x80280057The consistency check on w has failed
-21448621200x80280058The handle is incorrect
-21448621190x80280059Delegation is not correct
-21448621180x8028005AThe context blob is invalid
-21448621170x8028005BToo many contexts held by the TPM
-21448621160x8028005CMigration authority signature validation failure
-21448621150x8028005DMigration destination not authenticated
-21448621140x8028005EMigration source incorrect
-21448621130x8028005FIncorrect migration authority
-21448621110x80280061Attempt to revoke the EK and the EK is not revocable
-21448621100x80280062Bad signature of CMK ticket
-21448621090x80280063There is no room in the context list for additional contexts
-21448611840x80280400The command was blocked
-21448611830x80280401The specified handle was not found
-21448611820x80280402The TPM returned a duplicate handle and the command needs to be resubmitted
-21448611810x80280403The command within the transport was blocked
-21448611800x80280404The command within the transport is not supported
-21448601600x80280800The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time
-21448601590x80280801SelfTestFull has not been run
-21448601580x80280802The TPM is currently executing a full selftest
-21448601570x80280803The TPM is defending against dictionary attacks and is in a time-out period
-21448458230x80284001An internal error has occurred within the Trusted Platform Module support program
-21448458220x80284002One or more input parameters is bad
-21448458210x80284003A specified output pointer is bad
-21448458200x80284004The specified context handle does not refer to a valid context
-21448458190x80284005A specified output buffer is too small
-21448458180x80284006An error occurred while communicating with the TPM
-21448458170x80284007One or more context parameters is invalid
-21448458160x80284008The TBS service is not running and could not be started
-21448458150x80284009A new context could not be created because there are too many open contexts
-21448458140x8028400AA new virtual resource could not be created because there are too many open virtual resources
-21448458130x8028400BThe TBS service has been started but is not yet running
-21448458120x8028400CThe physical presence interface is not supported
-21448458110x8028400DThe command was canceled
-21448458100x8028400EThe input or output buffer is too large
-21448458090x8028400FA compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer
-21448458080x80284010The TBS service has been disabled
-21448458070x80284011No TCG event log is available
-21448458060x80284012The caller does not have the appropriate rights to perform the requested operation
-21448458050x80284013The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions may be required. The TPM management console (tpm.msc) action to make the TPM Ready may help. For further information, see the documentation for the Win32_Tpm WMI method 'Provision'. (The actions that may be required include importing the TPM Owner Authorization value into the system, calling the Win32_Tpm WMI method for provisioning the TPM and specifying TRUE for either 'ForceClear_Allowed' or 'PhysicalPresencePrompts_Allowed' (as indicated by the value returned in the Additional Information), or enabling the TPM in the system BIOS.)
-21448458040x80284014The Physical Presence Interface of this firmware does not support the requested method
-21448458030x80284015The requested TPM OwnerAuth value was not found
-21448458020x80284016The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information
-21447964160x80290100The command buffer is not in the correct state
-21447964150x80290101The command buffer does not contain enough data to satisfy the request
-21447964140x80290102The command buffer cannot contain any more data
-21447964130x80290103One or more output parameters was NULL or invalid
-21447964120x80290104One or more input parameters is invalid
-21447964110x80290105Not enough memory was available to satisfy the request
-21447964100x80290106The specified buffer was too small
-21447964090x80290107An internal error was detected
-21447964080x80290108The caller does not have the appropriate rights to perform the requested operation
-21447964070x80290109The specified authorization information was invalid
-21447964060x8029010AThe specified context handle was not valid
-21447964050x8029010BAn error occurred while communicating with the TBS
-21447964040x8029010CThe TPM returned an unexpected result
-21447964030x8029010DThe message was too large for the encoding scheme
-21447964020x8029010EThe encoding in the blob was not recognized
-21447964010x8029010FThe key size is not valid
-21447964000x80290110The encryption operation failed
-21447963990x80290111The key parameters structure was not valid
-21447963980x80290112The requested supplied data does not appear to be a valid migration authorization blob
-21447963970x80290113The specified PCR index was invalid
-21447963960x80290114The data given does not appear to be a valid delegate blob
-21447963950x80290115One or more of the specified context parameters was not valid
-21447963940x80290116The data given does not appear to be a valid key blob
-21447963930x80290117The specified PCR data was invalid
-21447963920x80290118The format of the owner auth data was invalid
-21447963910x80290119The random number generated did not pass FIPS RNG check
-21447963900x8029011AThe TCG Event Log does not contain any data
-21447963890x8029011BAn entry in the TCG Event Log was invalid
-21447963880x8029011CA TCG Separator was not found
-21447963870x8029011DA digest value in a TCG Log entry did not match hashed data
-21447963860x8029011EThe requested operation was blocked by current TPM policy. Please contact your system administrator for assistance
-21447961600x80290200The specified buffer was too small
-21447961590x80290201The context could not be cleaned up
-21447961580x80290202The specified context handle is invalid
-21447961570x80290203An invalid context parameter was specified
-21447961560x80290204An error occurred while communicating with the TPM
-21447961550x80290205No entry with the specified key was found
-21447961540x80290206The specified virtual handle matches a virtual handle already in use
-21447961530x80290207The pointer to the returned handle location was NULL or invalid
-21447961520x80290208One or more parameters is invalid
-21447961510x80290209The RPC subsystem could not be initialized
-21447961500x8029020AThe TBS scheduler is not running
-21447961490x8029020BThe command was canceled
-21447961480x8029020CThere was not enough memory to fulfill the request
-21447961470x8029020DThe specified list is empty, or the iteration has reached the end of the list
-21447961460x8029020EThe specified item was not found in the list
-21447961450x8029020FThe TPM does not have enough space to load the requested resource
-21447961440x80290210There are too many TPM contexts in use
-21447961430x80290211The TPM command failed
-21447961420x80290212The TBS does not recognize the specified ordinal
-21447961410x80290213The requested resource is no longer available
-21447961400x80290214The resource type did not match
-21447961390x80290215No resources can be unloaded
-21447961380x80290216No new entries can be added to the hash table
-21447961370x80290217A new TBS context could not be created because there are too many open contexts
-21447961360x80290218A new virtual resource could not be created because there are too many open virtual resources
-21447961350x80290219The physical presence interface is not supported
-21447961340x8029021ATBS is not compatible with the version of TPM found on the system
-21447961330x8029021BNo TCG event log is available
-21447959040x80290300A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command
-21447959030x80290301The user failed to confirm the TPM operation request
-21447959020x80290302The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM)
-21447959010x80290303The BIOS does not support the physical presence interface
-21447959000x80290304The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command
-21447956480x80290400This is an error mask to convert Platform Crypto Provider errors to win errors
-21447956470x80290401The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational
-21447956460x80290402The handle provided to the Platform Crypto Provider is invalid
-21447956450x80290403A parameter provided to the Platform Crypto Provider is invalid
-21447956440x80290404A provided flag to the Platform Crypto Provider is not supported
-21447956430x80290405The requested operation is not supported by this Platform Crypto Provider
-21447956420x80290406The buffer is too small to contain all data. No information has been written to the buffer
-21447956410x80290407An unexpected internal error has occurred in the Platform Crypto Provider
-21447956400x80290408The authorization to use a provider object has failed
-21447956390x80290409The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack
-21447956380x8029040AThe referenced policy was not found
-21447956370x8029040BThe referenced profile was not found
-21447956360x8029040CThe validation was not succesful
-21447311350x802A0001The object could not be created
-21447311340x802A0002Shutdown was already called on this object or the object that owns it
-21447311330x802A0003This method cannot be called during this type of callback
-21447311320x802A0004This object has been sealed, so this change is no longer allowed
-21447311310x802A0005The requested value was never set
-21447311300x802A0006The requested value cannot be determined
-21447311290x802A0007A callback returned an invalid output parameter
-21447311280x802A0008A callback returned a success code other than S_OK or S_FALSE
-21447311270x802A0009A parameter that should be owned by this object is owned by a different object
-21447311260x802A000AMore than one item matched the search criteria
-21447311250x802A000BA floating-point overflow occurred
-21447311240x802A000CThis method can only be called from the thread that created the object
-21447308790x802A0101The storyboard is currently in the schedule
-21447308780x802A0102The storyboard is not playing
-21447308770x802A0103The start keyframe might occur after the end keyframe
-21447308760x802A0104It might not be possible to determine the end keyframe time when the start keyframe is reached
-21447308750x802A0105Two repeated portions of a storyboard might overlap
-21447308740x802A0106The transition has already been added to a storyboard
-21447308730x802A0107The transition has not been added to a storyboard
-21447308720x802A0108The transition might eclipse the beginning of another transition in the storyboard
-21447308710x802A0109The given time is earlier than the time passed to the last update
-21447308700x802A010AThis client is already connected to a timer
-21447308690x802A010BThe passed dimension is invalid or does not match the object's dimension
-21447308680x802A010CThe added primitive begins at or beyond the duration of the interpolator
-21447306230x802A0201The operation cannot be completed because the window is being closed
-21443379180x80300002Data Collector Set was not found
-21443378510x80300045Unable to start Data Collector Set because there are too many folders
-21443378080x80300070Not enough free disk space to start Data Collector Set
-21443377500x803000AAThe Data Collector Set or one of its dependencies is already in use
-21443377370x803000B7Data Collector Set already exists
-21443376630x80300101Property value conflict
-21443376620x80300102The current configuration for this Data Collector Set requires that it contain exactly one Data Collector
-21443376610x80300103A user account is required in order to commit the current Data Collector Set properties
-21443376600x80300104Data Collector Set is not running
-21443376590x80300105A 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
-21443376580x80300106The executable path you have specified refers to a network share or UNC path
-21443376570x80300107The executable path you have specified is already configured for API tracing
-21443376560x80300108The executable path you have specified does not exist. Verify that the specified path is correct
-21443376550x80300109Data Collector already exists
-21443376540x8030010AThe wait for the Data Collector Set start notification has timed out
-21443376530x8030010BThe wait for the Data Collector to start has timed out
-21443376520x8030010CThe wait for the report generation tool to finish has timed out
-21443376510x8030010DDuplicate items are not allowed
-21443376500x8030010EWhen specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename
-21443376490x8030010FThe session name provided is invalid
-21443376480x80300110The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation
-21443376470x80300111The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation
-21443376460x80300112The execution of the Rules Manager failed
-21443376450x80300113An error occurred while attempting to compress or extract the data
-21442723840x80310000This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel
-21442723830x80310001This drive is not encrypted
-21442723820x80310002The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions
-21442723810x80310003The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions
-21442723800x80310004A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date
-21442723790x80310005The 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)
-21442723780x80310006The 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)
-21442723770x80310007At least one secure key protector is required for this operation to be performed
-21442723760x80310008BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker
-21442723750x80310009BitLocker 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
-21442723740x8031000AThe 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
-21442723730x8031000BThe type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted
-21442723720x8031000CThe size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted
-21442723710x8031000DThe attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted
-21442723700x8031000EThe 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
-21442723690x8031000FThe 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
-21442723680x80310010The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access
-21442723670x80310011The 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
-21442723660x80310012The 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
-21442723650x80310013The drive cannot be encrypted because the file system is not supported
-21442723640x80310014The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition
-21442723630x80310015This drive cannot be encrypted
-21442723620x80310016The data is not valid
-21442723610x80310017The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically
-21442723600x80310018You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption
-21442723590x80310019The operation attempted cannot be performed on an operating system drive
-21442723580x8031001AThe buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again
-21442723570x8031001BA read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker
-21442723560x8031001CA write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker
-21442723550x8031001DOne or more BitLocker key protectors are required. You cannot delete the last key on this drive
-21442723540x8031001ECluster configurations are not supported by BitLocker Drive Encryption
-21442723530x8031001FThe drive specified is already configured to be automatically unlocked on the current computer
-21442723520x80310020The operating system drive is not protected by BitLocker Drive Encryption
-21442723510x80310021BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key
-21442723500x80310022The 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
-21442723490x80310023BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive
-21442723480x80310024The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again
-21442723470x80310025The 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
-21442723460x80310026The drive encryption algorithm cannot be used on this sector size
-21442723450x80310027The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again
-21442723440x80310028The drive specified is not the operating system drive
-21442723430x80310029BitLocker 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
-21442723420x8031002AThe 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
-21442723410x8031002BBitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker
-21442723400x8031002CGroup Policy settings require that a recovery password be specified before encrypting the drive
-21442723390x8031002DThe drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker
-21442723380x8031002EBitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive
-21442723360x80310030BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker
-21442723350x80310031This key protector cannot be added. Only one key protector of this type is allowed for this drive
-21442723340x80310032The 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
-21442723330x80310033The specified key protector was not found on the drive. Try another key protector
-21442723320x80310034The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive
-21442723310x80310035The 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
-21442723300x80310036The random number generator check test failed
-21442723290x80310037The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent
-21442723280x80310038The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration
-21442723270x80310039The drive must be fully decrypted to complete this operation
-21442723260x8031003AThe key protector specified cannot be used for this operation
-21442723250x8031003BNo key protectors exist on the drive to perform the hardware test
-21442723240x8031003CThe BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions
-21442723230x8031003DThe 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
-21442723220x8031003EThe 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
-21442723210x8031003FThe Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption
-21442723200x80310040The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes
-21442723190x80310041The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem
-21442723180x80310042The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM)
-21442723170x80310043The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN
-21442723160x80310044A boot application has changed since BitLocker Drive Encryption was enabled
-21442723150x80310045The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled
-21442723140x80310046The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information
-21442723130x80310047This 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
-21442723120x80310048BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions
-21442723110x80310049This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system
-21442723100x8031004ABitLocker 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
-21442723090x8031004BThe drive cannot be locked when the drive is in use
-21442723080x8031004CThe access token associated with the current thread is not an impersonated token
-21442723070x8031004DThe BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available
-21442723060x8031004EYou must restart your computer before continuing with BitLocker Drive Encryption
-21442723050x8031004FDrive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging
-21442723040x80310050No action was taken as BitLocker Drive Encryption is in raw access mode
-21442723030x80310051BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use
-21442723020x80310052The 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
-21442723010x80310053BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments
-21442723000x80310054The auto-unlock master key was not available from the operating system drive
-21442722990x80310055The system firmware failed to enable clearing of system memory when the computer was restarted
-21442722980x80310056The hidden drive cannot be encrypted
-21442722970x80310057BitLocker encryption keys were ignored because the drive was in a transient state
-21442722960x80310058Public key based protectors are not allowed on this drive
-21442722950x80310059BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing
-21442722940x8031005AThis version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system
-21442722930x8031005BThe Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information
-21442722920x8031005CGroup Policy settings do not permit the creation of a recovery password
-21442722910x8031005DGroup Policy settings require the creation of a recovery password
-21442722900x8031005EGroup Policy settings do not permit the creation of a recovery key
-21442722890x8031005FGroup Policy settings require the creation of a recovery key
-21442722880x80310060Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option
-21442722870x80310061Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option
-21442722860x80310062Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option
-21442722850x80310063Group Policy settings require the use of a startup key. Please choose this BitLocker startup option
-21442722840x80310064Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option
-21442722830x80310065Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option
-21442722820x80310066Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option
-21442722810x80310067Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option
-21442722800x80310068The PIN provided does not meet minimum or maximum length requirements
-21442722790x80310069The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector
-21442722780x8031006AGroup Policy settings do not permit the creation of a password
-21442722770x8031006BGroup Policy settings require the creation of a password
-21442722760x8031006CThe Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information
-21442722750x8031006DA password cannot be added to the operating system drive
-21442722740x8031006EThe BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive
-21442722730x8031006FThe drive is too small to be protected using BitLocker Drive Encryption
-21442722720x80310070The 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
-21442722710x80310071The 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
-21442722700x80310072Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption
-21442722690x80310073Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption
-21442722680x80310074Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption
-21442722670x80310075Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked
-21442722660x80310076Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked
-21442722650x80310077Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives
-21442722640x80310078Group 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
-21442722630x80310079Group 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
-21442722560x80310080Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization
-21442722550x80310081Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols
-21442722540x80310082This drive cannot be encrypted because it is reserved for Windows System Recovery Options
-21442722530x80310083BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker
-21442722520x80310084BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker
-21442722510x80310085The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker
-21442722500x80310086BitLocker 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
-21442722490x80310087BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker
-21442722480x80310088BitLocker 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
-21442722470x80310089The requested virtualization size is too big
-21442722400x80310090BitLocker 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
-21442722390x80310091BitLocker 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
-21442722380x80310092BitLocker 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
-21442722370x80310093The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement
-21442722360x80310094The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid
-21442722350x80310095Removal of the data recovery agent certificate must be done using the Certificates snap-in
-21442722340x80310096This 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""
-21442722330x80310097The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive
-21442722320x80310098The 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
-21442722310x80310099The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals
-21442722300x8031009AThe requested TPM PIN contains invalid characters
-21442722290x8031009BThe management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version
-21442722280x8031009CThe feature is only supported on EFI systems
-21442722270x8031009DMore than one Network Key Protector certificate has been found on the system
-21442722260x8031009ERemoval of the Network Key Protector certificate must be done using the Certificates snap-in
-21442722250x8031009FAn invalid certificate has been found in the Network Key Protector certificate store
-21442722240x803100A0This drive isn't protected with a PIN
-21442722230x803100A1Please enter the correct current PIN
-21442722220x803100A2You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator
-21442722210x803100A3BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator
-21442722200x803100A4Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~
-21442722190x803100A5BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage
-21442722180x803100A6BitLocker Drive Encryption does not support wiping free space on thin provisioned storage
-21442722170x803100A7The required authentication key length is not supported by the drive
-21442722160x803100A8This drive isn't protected with a password
-21442722150x803100A9Please enter the correct current password
-21442722140x803100AAThe password cannot exceed 256 characters
-21442722130x803100ABA password key protector cannot be added because a TPM protector exists on the drive
-21442722120x803100ACA TPM key protector cannot be added because a password protector exists on the drive
-21442722110x803100ADThis command can only be performed from the coordinator node for the specified CSV volume
-21442722100x803100AEThis command cannot be performed on a volume when it is part of a cluster
-21442722090x803100AFBitLocker did not revert to using BitLocker software encryption due to group policy configuration
-21442722080x803100B0The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use
-21442722070x803100B1Group Policy settings do not allow the use of hardware-based encryption
-21442722060x803100B2The drive specified does not support hardware-based encryption
-21442722050x803100B3BitLocker cannot be upgraded during disk encryption or decryption
-21442722040x803100B4Discovery Volumes are not supported for volumes using hardware encryption
-21442722030x803100B5No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume
-21442722020x803100B6No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume
-21442722010x803100B7Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume
-21442722000x803100B8Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume
-21442721990x803100B9Wipe of free space is not currently taking place
-21442721980x803100BABitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled
-21442721970x803100BBBitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker
-21442721960x803100BCYour computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates
-21442721950x803100BDBitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume
-21442721940x803100BEBitLocker 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
-21442721930x803100BFThis PC's firmware is not capable of supporting hardware encryption
-21442721920x803100C0BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator
-21442721910x803100C1You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator
-21442721900x803100C2BitLocker cannot save the recovery password because the specified Microsoft account is Suspended
-21442721890x803100C3BitLocker cannot save the recovery password because the specified Microsoft account is Blocked
-21442721880x803100C4This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy
-21442721870x803100C5This PC cannot support device encryption because unencrypted fixed data volumes are present
-21442721860x803100C6This PC does not meet the hardware requirements to support device encryption
-21442721850x803100C7This PC cannot support device encryption because WinRE is not properly configured
-21442721840x803100C8Protection 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
-21442721830x803100C9This PC is not provisioned to support device encryption
-21442721820x803100CADevice Lock has been triggered due to too many incorrect password attempts
-21442721810x803100CBProtection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information
-21442721800x803100CCYour PIN can only contain numbers from 0 to 9
-21442721790x803100CDBitLocker cannot use hardware replay protection because no counter is available on your PC
-21442721780x803100CEDevice Lockout state validation failed due to counter mismatch
-21442721770x803100CFThe input buffer is too large
-21442721760x803100D0The target of an invocation does not support requested capability
-21442721750x803100D1Device encryption is currently blocked by this PC's configuration
-21442721740x803100D2This drive has been opted out of device encryption
-21442721730x803100D3Device encryption isn't available for this drive
-21442721720x803100D4The 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
-21442721710x803100D5Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator
-21442721700x803100D6Device encryption can't be turned off while this drive is being encrypted. Please try again later
-21442721690x803100D7This action isn't supported because this drive isn't automatically managed with device encryption
-21442721680x803100D8BitLocker can't be suspended on this drive until the next restart
-21442068470x80320001The callout does not exist
-21442068460x80320002The filter condition does not exist
-21442068450x80320003The filter does not exist
-21442068440x80320004The layer does not exist
-21442068430x80320005The provider does not exist
-21442068420x80320006The provider context does not exist
-21442068410x80320007The sublayer does not exist
-21442068400x80320008The object does not exist
-21442068390x80320009An object with that GUID or LUID already exists
-21442068380x8032000AThe object is referenced by other objects so cannot be deleted
-21442068370x8032000BThe call is not allowed from within a dynamic session
-21442068360x8032000CThe call was made from the wrong session so cannot be completed
-21442068350x8032000DThe call must be made from within an explicit transaction
-21442068340x8032000EThe call is not allowed from within an explicit transaction
-21442068330x8032000FThe explicit transaction has been forcibly cancelled
-21442068320x80320010The session has been cancelled
-21442068310x80320011The call is not allowed from within a read-only transaction
-21442068300x80320012The call timed out while waiting to acquire the transaction lock
-21442068290x80320013Collection of network diagnostic events is disabled
-21442068280x80320014The operation is not supported by the specified layer
-21442068270x80320015The call is allowed for kernel-mode callers only
-21442068260x80320016The call tried to associate two objects with incompatible lifetimes
-21442068250x80320017The object is built in so cannot be deleted
-21442068240x80320018The maximum number of callouts has been reached
-21442068230x80320019A notification could not be delivered because a message queue is at its maximum capacity
-21442068220x8032001AThe traffic parameters do not match those for the security association context
-21442068210x8032001BThe call is not allowed for the current security association state
-21442068200x8032001CA required pointer is null
-21442068190x8032001DAn enumerator is not valid
-21442068180x8032001EThe flags field contains an invalid value
-21442068170x8032001FA network mask is not valid
-21442068160x80320020An FWP_RANGE is not valid
-21442068150x80320021The time interval is not valid
-21442068140x80320022An array that must contain at least one element is zero length
-21442068130x80320023The displayData.name field cannot be null
-21442068120x80320024The action type is not one of the allowed action types for a filter
-21442068110x80320025The filter weight is not valid
-21442068100x80320026A filter condition contains a match type that is not compatible with the operands
-21442068090x80320027An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type
-21442068080x80320028An integer value is outside the allowed range
-21442068070x80320029A reserved field is non-zero
-21442068060x8032002AA filter cannot contain multiple conditions operating on a single field
-21442068050x8032002BA policy cannot contain the same keying module more than once
-21442068040x8032002CThe action type is not compatible with the layer
-21442068030x8032002DThe action type is not compatible with the sublayer
-21442068020x8032002EThe raw context or the provider context is not compatible with the layer
-21442068010x8032002FThe raw context or the provider context is not compatible with the callout
-21442068000x80320030The authentication method is not compatible with the policy type
-21442067990x80320031The Diffie-Hellman group is not compatible with the policy type
-21442067980x80320032An IKE policy cannot contain an Extended Mode policy
-21442067970x80320033The enumeration template or subscription will never match any objects
-21442067960x80320034The provider context is of the wrong type
-21442067950x80320035The parameter is incorrect
-21442067940x80320036The maximum number of sublayers has been reached
-21442067930x80320037The notification function for a callout returned an error
-21442067920x80320038The IPsec authentication transform is not valid
-21442067910x80320039The IPsec cipher transform is not valid
-21442067900x8032003AThe IPsec cipher transform is not compatible with the policy
-21442067890x8032003BThe combination of IPsec transform types is not valid
-21442067880x8032003CA policy cannot contain the same auth method more than once
-21442067870x8032003DA tunnel endpoint configuration is invalid
-21442067860x8032003EThe WFP MAC Layers are not ready
-21442067850x8032003FA key manager capable of key dictation is already registered
-21442067840x80320040A key manager dictated invalid keys
-21442067830x80320041The BFE IPsec Connection Tracking is disabled
-21442067820x80320042The DNS name is invalid
-21442067810x80320043The engine option is still enabled due to other configuration settings
-21442067800x80320044The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine
-21442065880x80320104The packet should be dropped, no ICMP should be sent
-21440757740x80340002The binding to the network interface is being closed
-21440757720x80340004An invalid version was specified
-21440757710x80340005An invalid characteristics table was used
-21440757700x80340006Failed to find the network interface or network interface is not ready
-21440757690x80340007Failed to open the network interface
-21440757680x80340008Network interface has encountered an internal unrecoverable failure
-21440757670x80340009The multicast list on the network interface is full
-21440757660x8034000AAn attempt was made to add a duplicate multicast address to the list
-21440757650x8034000BAt attempt was made to remove a multicast address that was never added
-21440757640x8034000CNetowork interface aborted the request
-21440757630x8034000DNetwork interface can not process the request because it is being reset
-21440757610x8034000FAn attempt was made to send an invalid packet on a network interface
-21440757600x80340010The specified request is not a valid operation for the target device
-21440757590x80340011Network interface is not ready to complete this operation
-21440757560x80340014The length of the buffer submitted for this operation is not valid
-21440757550x80340015The data used for this operation is not valid
-21440757540x80340016The length of buffer submitted for this operation is too small
-21440757530x80340017Network interface does not support this OID (Object Identifier)
-21440757520x80340018The network interface has been removed
-21440757510x80340019Network interface does not support this media type
-21440757500x8034001AAn attempt was made to remove a token ring group address that is in use by other components
-21440757490x8034001BAn attempt was made to map a file that can not be found
-21440757480x8034001CAn error occurred while NDIS tried to map the file
-21440757470x8034001DAn attempt was made to map a file that is alreay mapped
-21440757460x8034001EAn attempt to allocate a hardware resource failed because the resource is used by another component
-21440757450x8034001FThe I/O operation failed because network media is disconnected or wireless access point is out of range
-21440757420x80340022The network address used in the request is invalid
-21440757340x8034002AThe offload operation on the network interface has been paused
-21440757330x8034002BNetwork interface was not found
-21440757320x8034002CThe revision number specified in the structure is not supported
-21440757310x8034002DThe specified port does not exist on this network interface
-21440757300x8034002EThe current state of the specified port on this network interface does not support the requested operation
-21440757290x8034002FThe miniport adapter is in low power state
-21440757280x80340030This operation requires the miniport adapter to be reinitialized
-21440755890x803400BBNetword interface does not support this request
-21440675840x80342000The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation
-21440675830x80342001The wireless local area network interface is busy and can not perform the requested operation
-21440675820x80342002The wireless local area network interface is powered down and doesn't support the requested operation
-21440675810x80342003The list of wake on LAN patterns is full
-21440675800x80342004The list of low power protocol offloads is full
-21438791670x80370001A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration
-21438136310x80380001The regeneration operation was not able to copy all data from the active plexes due to bad sectors
-21438136300x80380002One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems
-21437480950x80390001Some BCD entries were not imported correctly from the BCD store
-21437480930x80390003Some BCD entries were not synchronized correctly with the firmware
-21436825590x803A0001The virtualization storage subsystem has generated an error
-21435512320x803C0100The operation was cancelled
-21435512310x803C0101An error occurred when running a PowerShell script
-21435512300x803C0102An error occurred when interacting with PowerShell runtime
-21435512290x803C0103An error occurred in the Scripted Diagnostic Managed Host
-21435512280x803C0104The troubleshooting pack does not contain a required verifier to complete the verification
-21435512260x803C0106Scripted diagnostics is disabled by group policy
-21435512250x803C0107Trust validation of the troubleshooting pack failed
-21435512240x803C0108The troubleshooting pack cannot be executed on this system
-21435512230x803C0109This version of the troubleshooting pack is not supported
-21435512220x803C010AA required resource cannot be loaded
-21435512210x803C010BThe troubleshooting pack reported information for a root cause without adding the root cause
-21434859520x803D0000The input data was not in the expected format or did not have the expected value
-21434859510x803D0001The operation could not be completed because the object is in a faulted state due to a previous error
-21434859500x803D0002The operation could not be completed because it would lead to numeric overflow
-21434859490x803D0003The operation is not allowed due to the current state of the object
-21434859480x803D0004The operation was aborted
-21434859470x803D0005Access was denied by the remote endpoint
-21434859460x803D0006The operation did not complete within the time allotted
-21434859450x803D0007The operation was abandoned
-21434859440x803D0008A quota was exceeded
-21434859430x803D0009The information was not available in the specified language
-21434859420x803D000ASecurity verification was not successful for the received data
-21434859410x803D000BThe address is already being used
-21434859400x803D000CThe address is not valid for this context
-21434859390x803D000DThe remote endpoint does not exist or could not be located
-21434859380x803D000EThe remote endpoint is not currently in service at this location
-21434859370x803D000FThe remote endpoint could not process the request
-21434859360x803D0010The remote endpoint was not reachable
-21434859350x803D0011The operation was not supported by the remote endpoint
-21434859340x803D0012The remote endpoint is unable to process the request due to being overloaded
-21434859330x803D0013A message containing a fault was received from the remote endpoint
-21434859320x803D0014The connection with the remote endpoint was terminated
-21434859310x803D0015The HTTP proxy server could not process the request
-21434859300x803D0016Access was denied by the HTTP proxy server
-21434859290x803D0017The requested feature is not available on this platform
-21434859280x803D0018The HTTP proxy server requires HTTP authentication scheme 'basic'
-21434859270x803D0019The HTTP proxy server requires HTTP authentication scheme 'digest'
-21434859260x803D001AThe HTTP proxy server requires HTTP authentication scheme 'NTLM'
-21434859250x803D001BThe HTTP proxy server requires HTTP authentication scheme 'negotiate'
-21434859240x803D001CThe remote endpoint requires HTTP authentication scheme 'basic'
-21434859230x803D001DThe remote endpoint requires HTTP authentication scheme 'digest'
-21434859220x803D001EThe remote endpoint requires HTTP authentication scheme 'NTLM'
-21434859210x803D001FThe remote endpoint requires HTTP authentication scheme 'negotiate'
-21434859200x803D0020The endpoint address URL is invalid
-21434859190x803D0021Unrecognized error occurred in the Windows Web Services framework
-21434859180x803D0022A security token was rejected by the server because it has expired
-21434859170x803D0023A security operation failed in the Windows Web Services framework
-21434201600x803E0100The notification channel has already been closed
-21434201590x803E0101The notification channel request did not complete successfully
-21434201580x803E0102The application identifier provided is invalid
-21434201570x803E0103A notification channel request for the provided application identifier is in progress
-21434201560x803E0104The channel identifier is already tied to another application endpoint
-21434201550x803E0105The notification platform is unavailable
-21434201540x803E0106The notification has already been posted
-21434201530x803E0107The notification has already been hidden
-21434201520x803E0108The notification cannot be hidden until it has been shown
-21434201510x803E0109Cloud notifications have been turned off
-21434201440x803E0110The application does not have the cloud notification capability
-21434201430x803E0111Settings prevent the notification from being delivered
-21434201420x803E0112Application capabilities prevent the notification from being delivered
-21434201410x803E0113The application does not have the internet access capability
-21434201400x803E0114Settings prevent the notification type from being delivered
-21434201390x803E0115The size of the notification content is too large
-21434201380x803E0116The size of the notification tag is too large
-21434201370x803E0117The notification platform doesn't have appropriate privilege on resources
-21434201360x803E0118The notification platform found application is already registered
-21434201350x803E0119The application background task does not have the push notification capability
-21434201340x803E011AThe notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service
-21434201330x803E011BThe notification platform is unable to connect to the cloud notification service
-21434201320x803E011CThe notification platform is unable to initialize a callback for lock screen updates
-21434201280x803E0120The size of the developer id for scheduled notification is too large
-21434201180x803E012AThe notification tag is not alphanumeric
-21434201170x803E012BThe notification platform has received invalid HTTP status code other than 2xx for polling
-21434199040x803E0200The notification platform has run out of presentation layer sessions
-21434199030x803E0201The notification platform rejects image download request due to system in power save mode
-21434199020x803E0202The notification platform doesn't have the requested image in its cache
-21434199010x803E0203The notification platform cannot complete all of requested image
-21434199000x803E0204A cloud image downloaded from the notification platform is invalid
-21434198990x803E0205Notification Id provided as filter is matched with what the notification platform maintains
-21434198980x803E0206Notification callback interface is already registered
-21434198970x803E0207Toast Notification was dropped without being displayed to the user
-21434198960x803E0208The notification platform does not have the proper privileges to complete the request
-21434198950x803E0209The size of the notification group is too large
-21434198940x803E020AThe notification group is not alphanumeric
-21434198930x803E020BCloud notifications have been disabled for the application due to a policy setting
-21432893440x80400000Input data cannot be processed in the non-chronological order
-21432893430x80400001Requested operation cannot be performed inside the callback or event handler
-21432893420x80400002Input cannot be processed because there is ongoing interaction with another pointer type
-21432893410x80400003One or more fields in the input packet are invalid
-21432893400x80400004Packets in the frame are inconsistent. Either pointer ids are not unique or there is a discrepancy in timestamps, frame ids, pointer types or source devices
-21432893390x80400005The history of frames is inconsistent. Pointer ids, types, source devices don't match, or frame ids are not unique, or timestamps are out of order
-21432893380x80400006Failed to retrieve information about the input device
-21432893370x80400007Coordinate system transformation failed to transform the data
-21432893360x80400008The property is not supported or not reported correctly by the input device
-21419453430x80548201Context is not activated
-21419453420x80548202Bad SIM is inserted
-21419453410x80548203Requested data class is not avaialable
-21419453400x80548204Access point name (APN) or Access string is incorrect
-21419453390x80548205Max activated contexts have reached
-21419453380x80548206Device is in packet detach state
-21419453370x80548207Provider is not visible
-21419453360x80548208Radio is powered off
-21419453350x80548209MBN subscription is not activated
-21419453340x8054820ASIM is not inserted
-21419453330x8054820BVoice call in progress
-21419453320x8054820CVisible provider cache is invalid
-21419453310x8054820DDevice is not registered
-21419453300x8054820EProviders not found
-21419453290x8054820FPin is not supported
-21419453280x80548210Pin is required
-21419453270x80548211PIN is disabled
-21419453260x80548212Generic Failure
-21419453200x80548218Profile is invalid
-21419453190x80548219Default profile exist
-21419453120x80548220SMS encoding is not supported
-21419453110x80548221SMS filter is not supported
-21419453100x80548222Invalid SMS memory index is used
-21419453090x80548223SMS language is not supported
-21419453080x80548224SMS memory failure occurred
-21419453070x80548225SMS network timeout happened
-21419453060x80548226Unknown SMSC address is used
-21419453050x80548227SMS format is not supported
-21419453040x80548228SMS operation is not allowed
-21419453030x80548229Device SMS memory is full
-21419130870x80550001Windows cannot evaluate this EAS policy since this is not managed by the operating system
-21419130860x80550002The system can be made compliant to this EAS policy if certain actions are performed by the user
-21419130850x80550003The EAS policy being evaluated cannot be enforced by the system
-21419130840x80550004EAS password policies for the user cannot be evaluated as the user has a blank password
-21419130830x80550005EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system
-21419130820x80550006The user is not allowed to change her password
-21419130810x80550007EAS password policies cannot be evaluated as one or more admins have blank passwords
-21419130800x80550008One or more admins are not allowed to change their password
-21419130790x80550009There are other standard users present who are not allowed to change their password
-21419130780x8055000AThe EAS password policy cannot be enforced by the connected account provider of at least one administrator
-21419130770x8055000BThere is at least one administrator whose connected account password needs to be changed for EAS password policy compliance
-21419130760x8055000CThe EAS password policy cannot be enforced by the connected account provider of the current user
-21419130750x8055000DThe connected account password of the current user needs to be changed for EAS password policy compliance
-21409955830x80630001The IPv6 protocol is not installed
-21409955820x80630002The compoment has not been initialized
-21409955810x80630003The required service canot be started
-21409955800x80630004The P2P protocol is not licensed to run on this OS
-21409955680x80630010The graph handle is invalid
-21409955670x80630011The graph database name has changed
-21409955660x80630012A graph with the same ID already exists
-21409955650x80630013The graph is not ready
-21409955640x80630014The graph is shutting down
-21409955630x80630015The graph is still in use
-21409955620x80630016The graph database is corrupt
-21409955610x80630017Too many attributes have been used
-21409953250x80630103The connection can not be found
-21409953220x80630106The peer attempted to connect to itself
-21409953210x80630107The peer is already listening for connections
-21409953200x80630108The node was not found
-21409953190x80630109The Connection attempt failed
-21409953180x8063010AThe peer connection could not be authenticated
-21409953170x8063010BThe connection was refused
-21409950710x80630201The peer name classifier is too long
-21409950700x80630202The maximum number of identities have been created
-21409950690x80630203Unable to access a key
-21409950680x80630204The group already exists
-21409948150x80630301The requested record could not be found
-21409948140x80630302Access to the database was denied
-21409948130x80630303The Database could not be initialized
-21409948120x80630304The record is too big
-21409948110x80630305The database already exists
-21409948100x80630306The database could not be found
-21409945590x80630401The identity could not be found
-21409943030x80630501The event handle could not be found
-21409940470x80630601Invalid search
-21409940460x80630602The search atributes are invalid
-21409937910x80630701The invitiation is not trusted
-21409937890x80630703The certchain is too long
-21409937870x80630705The time period is invalid
-21409937860x80630706A circular cert chain was detected
-21409935350x80630801The certstore is corrupted
-21409914870x80631001The specified PNRP cloud deos not exist
-21409914830x80631005The cloud name is ambiguous
-21409873760x80632010The record is invlaid
-21409873600x80632020Not authorized
-21409873590x80632021The password does not meet policy requirements
-21409873440x80632030The record validation has been defered
-21409873280x80632040The group properies are invalid
-21409873120x80632050The peername is invalid
-21409872960x80632060The classifier is invalid
-21409872800x80632070The friendly name is invalid
-21409872790x80632071Invalid role property
-21409872780x80632072Invalid classifer property
-21409872640x80632080Invlaid record expiration
-21409872630x80632081Invlaid credential info
-21409872620x80632082Invalid credential
-21409872610x80632083Invalid record size
-21409872480x80632090Unsupported version
-21409872470x80632091The group is not ready
-21409872460x80632092The group is still in use
-21409872450x80632093The group is invalid
-21409872440x80632094No members were found
-21409872430x80632095There are no member connections
-21409872420x80632096Unable to listen
-21409872320x806320A0The identity does not exist
-21409872310x806320A1The service is not availible
-21409791990x80634001The peername could not be converted to a DNS pnrp name
-21409791980x80634002Invalid peer host name
-21409791970x80634003No more data could be found
-21409791950x80634005The existing peer name is already registered
-21409710070x80636001THe contact could not be found
-21409669120x80637000The app invite request was cancelled by the user
-21409669110x80637001No response of the invite was received
-21409669090x80637003User is not signed into serverless presence
-21409669080x80637004The user declined the privacy policy prompt
-21409669070x80637005A timeout occurred
-21409669050x80637007The address is invalid
-21409669040x80637008A required firewall exception is disabled
-21409669030x80637009The service is blocked by a firewall policy
-21409669020x8063700AFirewall exceptions are disabled
-21409669010x8063700BThe user declined to enable the firewall exceptions
-21408645110x80650001The attribute handle given was not valid on this server
-21408645100x80650002The attribute cannot be read
-21408645090x80650003The attribute cannot be written
-21408645080x80650004The attribute PDU was invalid
-21408645070x80650005The attribute requires authentication before it can be read or written
-21408645060x80650006Attribute server does not support the request received from the client
-21408645050x80650007Offset specified was past the end of the attribute
-21408645040x80650008The attribute requires authorization before it can be read or written
-21408645030x80650009Too many prepare writes have been queued
-21408645020x8065000ANo attribute found within the given attribute handle range
-21408645010x8065000BThe attribute cannot be read or written using the Read Blob Request
-21408645000x8065000CThe Encryption Key Size used for encrypting this link is insufficient
-21408644990x8065000DThe attribute value length is invalid for the operation
-21408644980x8065000EThe attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested
-21408644970x8065000FThe attribute requires encryption before it can be read or written
-21408644960x80650010The attribute type is not a supported grouping attribute as defined by a higher layer specification
-21408644950x80650011Insufficient Resources to complete the request
-21408604160x80651000An error that lies in the reserved range has been received
-21407989750x80660001PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode
-21407989740x80660002HD Audio widget encountered an unexpected empty connection list
-21407989730x80660003HD Audio widget does not support the connection list parameter
-21407989720x80660004No HD Audio subdevices were successfully created
-21407989710x80660005An unexpected NULL pointer was encountered in a linked list
-21407334390x80670001Optimistic locking failure. Data cannot be updated if it has changed since it was read
-21407334380x80670002A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits
-21407334370x80670003The StateRepository configuration is not valid
-21407334360x80670004The StateRepository schema version is not known
-21407334350x80670005A StateRepository dictionary is not valid
-21407334340x80670006The request failed because the StateRepository is actively blocking requests
-21407334330x80670007The database file is locked. The request will be retried
-21407334320x80670008The database file is locked because another process is busy recovering the database. The request will be retried
-21407334310x80670009A table in the database is locked. The request will be retried
-21407334300x8067000AThe shared cache for the database is locked by another connection. The request will be retried
-21389639670x80820001The bootfile is too small to support persistent snapshots
-21388984310x80830001The specified volume does not support storage tiers
-21388984300x80830002The Storage Tiers Management service detected that the specified volume is in the process of being dismounted
-21388984290x80830003The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid
-21388984280x80830004The file identifier specified is not valid on the volume
-21388984270x80830005Storage tier operations must be called on the clustering node that owns the metadata volume
-21388984260x80830006The Storage Tiers Management service is already optimizing the storage tiers on the specified volume
-21388984250x80830007The requested object type cannot be assigned to a storage tier
-21387018230x80860001Authentication target is invalid or not configured correctly
-21387018220x80860002Your application cannot get the Online Id properties due to the Terms of Use accepted by the user
-21387018210x80860003The application requesting authentication tokens is either disabled or incorrectly configured
-21387018200x80860004Online Id password must be updated before signin
-21387018190x80860005Online Id account properties must be updated before signin
-21387018180x80860006To help protect your Online Id account you must signin again
-21387018170x80860007Online Id account was locked because there have been too many attempts to sign in
-21387018160x80860008Online Id account requires parental consent before proceeding
-21387018150x80860009Online Id signin name is not yet verified. Email verification is required before signin
-21387018140x8086000AWe have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account
-21387018130x8086000BWe detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account
-21387018120x8086000CUser interaction is required for authentication
-21387018110x8086000DUser has reached the maximum device associations per user limit
-21387018100x8086000ECannot sign out from the application since the user account is connected
-21387018090x8086000FUser authentication is required for this operation
-21387018080x80860010We want to make sure this is you. User interaction is required for authentication
-21359493110x80B00001Could not create new process from ARM architecture device
-21359493100x80B00002Could not attach to the application process from ARM architecture device
-21359493090x80B00003Could not connect to dbgsrv server from ARM architecture device
-21359493080x80B00004Could not start dbgsrv server from ARM architecture device
-21323448310x80E70001The specified fault domain type or combination of minimum / maximum fault domain type is not valid
-21323448300x80E70002A Storage Spaces internal error occurred
-21323448290x80E70003The specified resiliency type is not valid
-21323448280x80E70004The physical disk's sector size is not supported by the storage pool
-21323448260x80E70006The requested redundancy is outside of the supported range of values
-21323448250x80E70007The number of data copies requested is outside of the supported range of values
-21323448240x80E70008The value for ParityLayout is outside of the supported range of values
-21323448230x80E70009The value for interleave length is outside of the supported range of values or is not a power of 2
-21323448220x80E7000AThe number of columns specified is outside of the supported range of values
-21323448210x80E7000BThere were not enough physical disks to complete the requested operation
-21323448200x80E7000CExtended error information is available
-21323448190x80E7000DThe specified provisioning type is not valid
-21323448180x80E7000EThe allocation size is outside of the supported range of values
-21323448170x80E7000FEnclosure awareness is not supported for this virtual disk
-21323448160x80E70010The write cache size is outside of the supported range of values
-21323448150x80E70011The value for number of groups is outside of the supported range of values
-21323448140x80E70012The OperationalState of the physical disk is invalid for this operation
-20894842870x83750001Unsupported format
-20894842860x83750002Invalid XML
-20894842850x83750003Missing required element
-20894842840x83750004Missing required attribute
-20894842830x83750005Unexpected content
-20894842820x83750006Resource too large
-20894842810x83750007Invalid JSON string
-20894842800x83750008Invalid JSON number
-20894842790x83750009JSON value not found
-20894187510x83760001Invalid operation performed by the protocol
-20894187500x83760002Invalid data format for the specific protocol operation
-20894187490x83760003Protocol extensions are not supported
-20894187480x83760004Subrotocol is not supported
-20894187470x83760005Incorrect protocol version
-20185743350x87AF0001SQL error or missing database
-20185743340x87AF0002Internal logic error in SQLite
-20185743330x87AF0003Access permission denied
-20185743320x87AF0004Callback routine requested an abort
-20185743310x87AF0005The database file is locked
-20185743300x87AF0006A table in the database is locked
-20185743290x87AF0007A malloc() failed
-20185743280x87AF0008Attempt to write a readonly database
-20185743270x87AF0009Operation terminated by sqlite3_interrupt()
-20185743260x87AF000ASome kind of disk I/O error occurred
-20185743250x87AF000BThe database disk image is malformed
-20185743240x87AF000CUnknown opcode in sqlite3_file_control()
-20185743230x87AF000DInsertion failed because database is full
-20185743220x87AF000EUnable to open the database file
-20185743210x87AF000FDatabase lock protocol error
-20185743200x87AF0010Database is empty
-20185743190x87AF0011The database schema changed
-20185743180x87AF0012String or BLOB exceeds size limit
-20185743170x87AF0013Abort due to constraint violation
-20185743160x87AF0014Data type mismatch
-20185743150x87AF0015Library used incorrectly
-20185743140x87AF0016Uses OS features not supported on host
-20185743130x87AF0017Authorization denied
-20185743120x87AF0018Auxiliary database format error
-20185743110x87AF00192nd parameter to sqlite3_bind out of range
-20185743100x87AF001AFile opened that is not a database file
-20185743090x87AF001BNotifications from sqlite3_log()
-20185743080x87AF001CWarnings from sqlite3_log()
-20185742360x87AF0064sqlite3_step() has another row ready
-20185742350x87AF0065sqlite3_step() has finished executing
-20185740790x87AF0101SQLITE_IOERR_READ
-20185740750x87AF0105SQLITE_BUSY_RECOVERY
-20185740740x87AF0106SQLITE_LOCKED_SHAREDCACHE
-20185740720x87AF0108SQLITE_READONLY_RECOVERY
-20185740690x87AF010BSQLITE_CORRUPT_VTAB
-20185740660x87AF010ESQLITE_CANTOPEN_NOTEMPDIR
-20185740610x87AF0113SQLITE_CONSTRAINT_CHECK
-20185740530x87AF011BSQLITE_NOTICE_RECOVER_WAL
-20185740520x87AF011CSQLITE_WARNING_AUTOINDEX
-20185738230x87AF0201SQLITE_IOERR_SHORT_READ
-20185738200x87AF0204SQLITE_ABORT_ROLLBACK
-20185738190x87AF0205SQLITE_BUSY_SNAPSHOT
-20185738160x87AF0208SQLITE_READONLY_CANTLOCK
-20185738100x87AF020ESQLITE_CANTOPEN_ISDIR
-20185738050x87AF0213SQLITE_CONSTRAINT_COMMITHOOK
-20185737970x87AF021BSQLITE_NOTICE_RECOVER_ROLLBACK
-20185735670x87AF0301SQLITE_IOERR_WRITE
-20185735600x87AF0308SQLITE_READONLY_ROLLBACK
-20185735540x87AF030ESQLITE_CANTOPEN_FULLPATH
-20185735490x87AF0313SQLITE_CONSTRAINT_FOREIGNKEY
-20185733110x87AF0401SQLITE_IOERR_FSYNC
-20185733040x87AF0408SQLITE_READONLY_DBMOVED
-20185732980x87AF040ESQLITE_CANTOPEN_CONVPATH
-20185732930x87AF0413SQLITE_CONSTRAINT_FUNCTION
-20185730550x87AF0501SQLITE_IOERR_DIR_FSYNC
-20185730370x87AF0513SQLITE_CONSTRAINT_NOTNULL
-20185727990x87AF0601SQLITE_IOERR_TRUNCATE
-20185727810x87AF0613SQLITE_CONSTRAINT_PRIMARYKEY
-20185725430x87AF0701SQLITE_IOERR_FSTAT
-20185725250x87AF0713SQLITE_CONSTRAINT_TRIGGER
-20185722870x87AF0801SQLITE_IOERR_UNLOCK
-20185722690x87AF0813SQLITE_CONSTRAINT_UNIQUE
-20185720310x87AF0901SQLITE_IOERR_RDLOCK
-20185720130x87AF0913SQLITE_CONSTRAINT_VTAB
-20185717750x87AF0A01SQLITE_IOERR_DELETE
-20185717570x87AF0A13SQLITE_CONSTRAINT_ROWID
-20185715190x87AF0B01SQLITE_IOERR_BLOCKED
-20185712630x87AF0C01SQLITE_IOERR_NOMEM
-20185710070x87AF0D01SQLITE_IOERR_ACCESS
-20185707510x87AF0E01SQLITE_IOERR_CHECKRESERVEDLOCK
-20185704950x87AF0F01SQLITE_IOERR_LOCK
-20185702390x87AF1001SQLITE_IOERR_CLOSE
-20185699830x87AF1101SQLITE_IOERR_DIR_CLOSE
-20185697270x87AF1201SQLITE_IOERR_SHMOPEN
-20185694710x87AF1301SQLITE_IOERR_SHMSIZE
-20185692150x87AF1401SQLITE_IOERR_SHMLOCK
-20185689590x87AF1501SQLITE_IOERR_SHMMAP
-20185687030x87AF1601SQLITE_IOERR_SEEK
-20185684470x87AF1701SQLITE_IOERR_DELETE_NOENT
-20185681910x87AF1801SQLITE_IOERR_MMAP
-20185679350x87AF1901SQLITE_IOERR_GETTEMPPATH
-20185676790x87AF1A01SQLITE_IOERR_CONVPATH
-20171284470x87C51001Toggle (alternative) trace started
-20171284460x87C51002Cannot pre-empt running trace: The current trace has a higher priority
-20171284450x87C51003The always-on-trace is not running
-20171284440x87C51004RunScriptAction contains an invalid script type
-20171284430x87C51005Requested scenario definition cannot be found
-20171284420x87C51006Requested trace profile cannot be found
-20171284410x87C51007Trigger forwarder is already enabled
-20171284400x87C51008Trigger forwarder is already disabled
-20171284390x87C51009Cannot parse EventLog XML: The entry is malformed
-20171284380x87C5100A node contains a schemaversion which is not compatible with this client
-20171284370x87C5100BRunScriptAction was forced to terminate a script
-20171284360x87C5100CToggleTraceWithCustomFilterAction contains an invalid custom filter
-20171284350x87C5100DThe trace is not running
-20171284340x87C5100EA scenario failed to escalate: This scenario has escalated too recently
-20171284330x87C5100FA scenario failed to escalate: This scenario is already running an escalation
-20171284320x87C51010Cannot start tracing: PerfTrack component is already tracing
-20171284310x87C51011A scenario failed to escalate: This scenario has reached max escalations for this escalation type
-20171284300x87C51012Cannot update forwarder: The forwarder passed to the function is of a different type
-20171284290x87C51013RunScriptAction failed intentionally to force this escalation to terminate
-20171284280x87C51014Failed to initialize SQM logger
-20171284270x87C51015Failed to initialize WER logger: This system does not support WER for UTC
-20171284260x87C51016The TraceManager has attempted to take a tracing action without initializing tracers
-20171284250x87C51017WinRT initialization failed
-20171284240x87C51018 node contains a schemaversion that is not compatible with this client
-20171284230x87C51019Scenario contains an invalid filter that can never be satisfied
-20171284220x87C5101ARunExeWithArgsAction was forced to terminate a running executable
-20171284210x87C5101BEscalation for scenario failed due to insufficient permissions
-20171284200x87C5101CSetup for scenario failed due to insufficient permissions
-20171284190x87C5101DA process launched by UTC failed with a non-zero exit code
-20171284160x87C51020Escalation for scenario has timed out
-20171284150x87C51021Setup for scenario has timed out
-20171284140x87C51022The given trigger does not match the expected trigger type
-20171284130x87C51023Requested trigger cannot be found
-20171284120x87C51024SIF is not supported on the machine
-20171284110x87C51025The delay action was terminated
-20171284100x87C51026The device ticket was not obtained
-20171284090x87C51027The trace profile needs more memory than is available for tracing
-20132003830x88010001One 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
-20132003820x88010002This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption
-20132003810x88010003This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider
-20132003800x88010004This computer cannot support device encryption because the requisites for the device lock feature are not configured
-20132003790x88010005Protection is enabled on this volume but is not in the active state
-20132003780x88010006The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated
-20132003770x88010007The operating system drive is not protected by 3rd party drive encryption
-20132003760x88010008Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin
-20132003750x88010009The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large
-20130897910x8802B001The file size is larger than supported by the sync engine
-20130897900x8802B002The file cannot be uploaded because it doesn't fit in the user's available service provided storage space
-20130897890x8802B003The file name contains invalid characters
-20130897880x8802B004The maximum file count has been reached for this folder in the sync engine
-20130897870x8802B005The file sync has been delegated to another program and has run into an issue
-20130897860x8802B006Sync has been delayed due to a throttling request from the service
-20130856940x8802C002We can't seem to find that file. Please try again later
-20130856930x8802C003The account you're signed in with doesn't have permission to open this file
-20130856920x8802C004There was a problem connecting to the service. Please try again later
-20130856910x8802C005Sorry, there was a problem downloading the file
-20130856900x8802C006We're having trouble downloading the file right now. Please try again later
-20130856890x8802C007We're having trouble downloading the file right now. Please try again later
-20130815990x8802D001The sync engine does not have permissions to access a local folder under the sync root
-20130815980x8802D002The folder name contains invalid characters
-20130815970x8802D003The sync engine is not allowed to run in your current market
-20130815960x8802D004All files and folders can't be uploaded because a path of a file or folder is too long
-20130815950x8802D005All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit
-20130815940x8802D006Updates are needed in order to use the sync engine
-20130815930x8802D007The sync engine needs to authenticate with a proxy server
-20130815920x8802D008There was a problem setting up the storage services for the account
-20130815910x8802D009Files can't be uploaded because there's an unsupported reparse point
-20130815900x8802D00AThe service has blocked your account from accessing the storage service
-20130815890x8802D00BThe action can't be performed right now because this folder is being moved. Please try again later
-20053360630x88790001The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1
-20053360620x88790002The specified file was not found
-20052705270x887A0001The 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
-20052705260x887A0002The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal
-20052705250x887A0003The caller did not supply a sufficiently large buffer
-20052705240x887A0004The specified device interface or feature level is not supported on this system
-20052705230x887A0005The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action
-20052705220x887A0006The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application
-20052705210x887A0007The GPU will not respond to more commands, most likely because some other application submitted invalid commands. The calling application should re-create the device and continue
-20052705180x887A000AThe GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled
-20052705170x887A000BAn event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should be considered invalid
-20052705160x887A000CFullscreen mode could not be achieved because the specified output was already in use
-20052704960x887A0020An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect, and the application should not continue
-20052704950x887A0021A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time
-20052704940x887A0022A resource is not available at the time of the call, but may become available later
-20052704930x887A0023The 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
-20052704920x887A0024The device has been removed during a remote session because the remote computer ran out of memory
-20052704910x887A0025An on-going mode change prevented completion of the call. The call may succeed if attempted later
-20052704900x887A0026The keyed mutex was abandoned
-20052704890x887A0027The timeout value has elapsed and the resource is not yet available
-20052704880x887A0028The output duplication has been turned off because the Windows session ended or was disconnected. This happens when a remote user disconnects, or when switch user"" is used locally""
-20052704870x887A0029The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed
-20052704860x887A002ADXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver, or by the application using a swapchain that is incompatible with content protection
-20052704850x887A002BThe 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
-20052704840x887A002CThe application is trying to create a shared handle using a name that is already associated with some other resource
-20052704830x887A002DThe application requested an operation that depends on an SDK component that is missing or mismatched
-20052704820x887A002EThe DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed
-20052704800x887A0030Insufficient HW protected memory exits for proper function
-20052049910x887B0001The GPU was busy when the operation was requested
-20052049900x887B0002The driver has rejected the creation of this resource
-20052049890x887B0003The GPU counter was in use by another process or d3d device when application requested access to it
-20051394550x887C0001The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1
-20051394540x887C0002The specified file was not found
-20051394530x887C0003The 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
-20051394520x887C0004The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD
-20050083830x887E0001The blob provided does not match the adapter that the device was created on
-20050083820x887E0002The blob provided was created for a different version of the driver, and must be re-created
-20033044470x88980001MILERR_OBJECTBUSY
-20033044460x88980002MILERR_INSUFFICIENTBUFFER
-20033044450x88980003MILERR_WIN32ERROR
-20033044440x88980004MILERR_SCANNER_FAILED
-20033044430x88980005MILERR_SCREENACCESSDENIED
-20033044420x88980006MILERR_DISPLAYSTATEINVALID
-20033044410x88980007MILERR_NONINVERTIBLEMATRIX
-20033044400x88980008MILERR_ZEROVECTOR
-20033044390x88980009MILERR_TERMINATED
-20033044380x8898000AMILERR_BADNUMBER
-20033043200x88980080An internal error (MIL bug) occurred. On checked builds, an assert would be raised
-20033043160x88980084The display format we need to render is not supported by the hardware device
-20033043150x88980085A call to this method is invalid
-20033043140x88980086Lock attempted on an already locked object
-20033043130x88980087Unlock attempted on an unlocked object
-20033043120x88980088No algorithm avaliable to render text with this device
-20033043110x88980089Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache
-20033043100x8898008ASome glyph bitmaps in glyph cache are unexpectedly big
-20033043090x8898008BMarker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred, but still unwind the stack in the correct location
-20033043080x8898008CGuideline coordinates are not sorted properly or contain NaNs
-20033043070x8898008DNo HW rendering device is available for this operation
-20033043060x8898008EThere has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. There are two known case for this: 1) D3D Driver Internal error 2) D3D E_FAIL 2a) Unknown root cause b) When resizing too quickly for DWM and D3D stay in sync
-20033043050x8898008FThe object has already been initialized
-20033043040x88980090The size of the object does not match the expected size
-20033043030x88980091No Redirection surface available
-20033043020x88980092Remoting of this content is not supported
-20033043010x88980093Queued Presents are not supported
-20033043000x88980094Queued Presents are not being used
-20033042990x88980095No redirection surface was available. Caller should retry the call
-20033042980x88980096Shader construction failed because it was too complex
-20033042970x88980097MROW attempt to get a read lock failed
-20033042960x88980098MROW attempt to update the data failed because another update was outstanding
-20033042950x88980099Shader compilation failed
-20033042940x8898009ARequested DX redirection surface size exceeded maximum texture size
-20033042930x8898009BQueryPerformanceCounter returned a time in the past
-20033042910x8898009DPrimary Display device returned an invalid refresh rate
-20033042900x8898009EDWM can not find the adapter specified by the LUID
-20033042890x8898009FThe requested bitmap color space is not supported
-20033042880x889800A0The requested bitmap pre-filtering state is not supported
-20033042870x889800A1Access is denied to the requested bitmap for the specified display id
-20033034240x88980400UCEERR_INVALIDPACKETHEADER
-20033034230x88980401UCEERR_UNKNOWNPACKET
-20033034220x88980402UCEERR_ILLEGALPACKET
-20033034210x88980403UCEERR_MALFORMEDPACKET
-20033034200x88980404UCEERR_ILLEGALHANDLE
-20033034190x88980405UCEERR_HANDLELOOKUPFAILED
-20033034180x88980406UCEERR_RENDERTHREADFAILURE
-20033034170x88980407UCEERR_CTXSTACKFRSTTARGETNULL
-20033034160x88980408UCEERR_CONNECTIONIDLOOKUPFAILED
-20033034150x88980409UCEERR_BLOCKSFULL
-20033034140x8898040AUCEERR_MEMORYFAILURE
-20033034130x8898040BUCEERR_PACKETRECORDOUTOFRANGE
-20033034120x8898040CUCEERR_ILLEGALRECORDTYPE
-20033034110x8898040DUCEERR_OUTOFHANDLES
-20033034100x8898040EUCEERR_UNCHANGABLE_UPDATE_ATTEMPTED
-20033034090x8898040FUCEERR_NO_MULTIPLE_WORKER_THREADS
-20033034080x88980410UCEERR_REMOTINGNOTSUPPORTED
-20033034070x88980411UCEERR_MISSINGENDCOMMAND
-20033034060x88980412UCEERR_MISSINGBEGINCOMMAND
-20033034050x88980413UCEERR_CHANNELSYNCTIMEDOUT
-20033034040x88980414UCEERR_CHANNELSYNCABANDONED
-20033034030x88980415UCEERR_UNSUPPORTEDTRANSPORTVERSION
-20033034020x88980416UCEERR_TRANSPORTUNAVAILABLE
-20033034010x88980417UCEERR_FEEDBACK_UNSUPPORTED
-20033034000x88980418UCEERR_COMMANDTRANSPORTDENIED
-20033033990x88980419UCEERR_GRAPHICSSTREAMUNAVAILABLE
-20033033920x88980420UCEERR_GRAPHICSSTREAMALREADYOPEN
-20033033910x88980421UCEERR_TRANSPORTDISCONNECTED
-20033033900x88980422UCEERR_TRANSPORTOVERLOADED
-20033033890x88980423UCEERR_PARTITION_ZOMBIED
-20033031680x88980500MILAVERR_NOCLOCK
-20033031670x88980501MILAVERR_NOMEDIATYPE
-20033031660x88980502MILAVERR_NOVIDEOMIXER
-20033031650x88980503MILAVERR_NOVIDEOPRESENTER
-20033031640x88980504MILAVERR_NOREADYFRAMES
-20033031630x88980505MILAVERR_MODULENOTLOADED
-20033031620x88980506MILAVERR_WMPFACTORYNOTREGISTERED
-20033031610x88980507MILAVERR_INVALIDWMPVERSION
-20033031600x88980508MILAVERR_INSUFFICIENTVIDEORESOURCES
-20033031590x88980509MILAVERR_VIDEOACCELERATIONNOTAVAILABLE
-20033031580x8898050AMILAVERR_REQUESTEDTEXTURETOOBIG
-20033031570x8898050BMILAVERR_SEEKFAILED
-20033031560x8898050CMILAVERR_UNEXPECTEDWMPFAILURE
-20033031550x8898050DMILAVERR_MEDIAPLAYERCLOSED
-20033031540x8898050EMILAVERR_UNKNOWNHARDWAREERROR
-20033028980x8898060EMILEFFECTSERR_UNKNOWNPROPERTY
-20033028970x8898060FMILEFFECTSERR_EFFECTNOTPARTOFGROUP
-20033028960x88980610MILEFFECTSERR_NOINPUTSOURCEATTACHED
-20033028950x88980611MILEFFECTSERR_CONNECTORNOTCONNECTED
-20033028940x88980612MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT
-20033028930x88980613MILEFFECTSERR_RESERVED
-20033028920x88980614MILEFFECTSERR_CYCLEDETECTED
-20033028910x88980615MILEFFECTSERR_EFFECTINMORETHANONEGRAPH
-20033028900x88980616MILEFFECTSERR_EFFECTALREADYINAGRAPH
-20033028890x88980617MILEFFECTSERR_EFFECTHASNOCHILDREN
-20033028880x88980618MILEFFECTSERR_ALREADYATTACHEDTOLISTENER
-20033028870x88980619MILEFFECTSERR_NOTAFFINETRANSFORM
-20033028860x8898061AMILEFFECTSERR_EMPTYBOUNDS
-20033028850x8898061BMILEFFECTSERR_OUTPUTSIZETOOLARGE
-20033026560x88980700DWMERR_STATE_TRANSITION_FAILED
-20033026550x88980701DWMERR_THEME_FAILED
-20033026540x88980702DWMERR_CATASTROPHIC_FAILURE
-20033024000x88980800DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED
-20033023990x88980801DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED
-20033023980x88980802DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED
-20032924120x88982F04The codec is in the wrong state
-20032924110x88982F05The value is out of range
-20032924090x88982F07The image format is unknown
-20032924050x88982F0BThe SDK version is unsupported
-20032924040x88982F0CThe component is not initialized
-20032924030x88982F0DThere is already an outstanding read or write lock
-20032923520x88982F40The specified bitmap property cannot be found
-20032923510x88982F41The bitmap codec does not support the bitmap property
-20032923500x88982F42The bitmap property size is invalid
-20032923490x88982F43An unknown error has occurred
-20032923480x88982F44The bitmap codec does not support a thumbnail
-20032923470x88982F45The bitmap palette is unavailable
-20032923460x88982F46Too many scanlines were requested
-20032923440x88982F48An internal error occurred
-20032923430x88982F49The bitmap bounds do not match the bitmap dimensions
-20032923360x88982F50The component cannot be found
-20032923350x88982F51The bitmap size is outside the valid range
-20032923340x88982F52There is too much metadata to be written to the bitmap
-20032923200x88982F60The image is unrecognized
-20032923190x88982F61The image header is unrecognized
-20032923180x88982F62The bitmap frame is missing
-20032923170x88982F63The image metadata header is unrecognized
-20032923040x88982F70The stream data is unrecognized
-20032923030x88982F71Failed to write to the stream
-20032923020x88982F72Failed to read from the stream
-20032923010x88982F73The stream is not available
-20032922880x88982F80The bitmap pixel format is unsupported
-20032922870x88982F81The operation is unsupported
-20032922780x88982F8AThe component registration is invalid
-20032922770x88982F8BThe component initialization has failed
-20032922760x88982F8CThe buffer allocated is insufficient
-20032922750x88982F8DDuplicate metadata is present
-20032922740x88982F8EThe bitmap property type is unexpected
-20032922730x88982F8FThe size is unexpected
-20032922720x88982F90The property query is invalid
-20032922710x88982F91The metadata type is unexpected
-20032922700x88982F92The specified bitmap property is only valid at root level
-20032922690x88982F93The query string contains an invalid character
-20032922680x88982F94Windows Codecs received an error from the Win32 system
-20032922670x88982F95The requested level of detail is not present
-20032922660x88982F96The scan index is invalid
-20032839680x88985000Indicates an error in an input file such as a font file
-20032839670x88985001Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from
-20032839660x88985002Indicates the specified font does not exist
-20032839650x88985003A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable
-20032839640x88985004A font file exists but could not be opened due to access denied, sharing violation, or similar error
-20032839630x88985005A font collection is obsolete due to changes in the system
-20032839620x88985006The given interface is already registered
-20032839610x88985007The font cache contains invalid data
-20032839600x88985008A font cache file corresponds to a different version of DirectWrite
-20032839590x88985009The operation is not supported for this type of font
-20032839580x8898500AThe version of the text renderer interface is not compatible
-20032839570x8898500BThe flow direction conflicts with the reading direction. They must be perpendicular to each other
-20032839560x8898500CThe font or glyph run does not contain any colored glyphs
-20032389110x88990001The object was not in the correct state to process the method
-20032389100x88990002The object has not yet been initialized
-20032389090x88990003The requested operation is not supported
-20032389080x88990004The geometry scanner failed to process the data
-20032389070x88990005Direct2D could not access the screen
-20032389060x88990006A valid display state could not be determined
-20032389050x88990007The supplied vector is zero
-20032389040x88990008An internal error (Direct2D bug) occurred. On checked builds, we would assert. The application should close this instance of Direct2D and should consider restarting its process
-20032389030x88990009The display format Direct2D needs to render is not supported by the hardware device
-20032389020x8899000AA call to this method is invalid
-20032389010x8899000BNo hardware rendering device is available for this operation
-20032389000x8899000CThere has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present
-20032388990x8899000DShader construction failed because it was too complex
-20032388980x8899000EShader compilation failed
-20032388970x8899000FRequested DirectX surface size exceeded maximum texture size
-20032388960x88990010The requested Direct2D version is not supported
-20032388950x88990011Invalid number
-20032388940x88990012Objects used together must be created from the same factory instance
-20032388930x88990013A layer resource can only be in use once at any point in time
-20032388920x88990014The pop call did not match the corresponding push call
-20032388910x88990015The resource was realized on the wrong render target
-20032388900x88990016The push and pop calls were unbalanced
-20032388890x88990017Attempt to copy from a render target while a layer or clip rect is applied
-20032388880x88990018The brush types are incompatible for the call
-20032388870x88990019An unknown win32 failure occurred
-20032388860x8899001AThe render target is not compatible with GDI
-20032388850x8899001BA text client drawing effect object is of the wrong type
-20032388840x8899001CThe application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid
-20032388830x8899001DThe requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level
-20032388820x8899001EThere was a configuration error in the graph
-20032388810x8899001FThere was a internal configuration error in the graph
-20032388800x88990020There was a cycle in the graph
-20032388790x88990021Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option
-20032388780x88990022The operation cannot complete while there are outstanding references to the target bitmap
-20032388770x88990023The operation failed because the original target is not currently bound as a target
-20032388760x88990024Cannot 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
-20032388750x88990025Cannot draw with a bitmap that is currently bound as the target bitmap
-20032388740x88990026D3D Device does not have sufficient capabilities to perform the requested action
-20032388730x88990027The graph could not be rendered with the context's current tiling settings
-20032388720x88990028The CLSID provided to Unregister did not correspond to a registered effect
-20032388710x88990029The specified property does not exist
-20032388700x8899002AThe specified sub-property does not exist
-20032388690x8899002BAddPage or Close called after print job is already closed
-20032388680x8899002CError during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control
-20032388670x8899002DAn effect attempted to use a transform with too many inputs
-19964231670x89010001The operation was preempted by a higher priority operation. It must be resumed later
-19963576310x89020001Function could not execute because it was deleted or garbage collected
-10731519990xC0090001The specified event is currently not being audited
-10731519980xC0090002The SID filtering operation removed all SIDs
-10731519970xC0090003Business rule scripts are disabled for the calling application
-10728758560xC00D36B0Platform not initialized. Please call MFStartup()
-10728758550xC00D36B1The buffer was too small to carry out the requested action
-10728758540xC00D36B2The request is invalid in the current state
-10728758530xC00D36B3The stream number provided was invalid
-10728758520xC00D36B4The data specified for the media type is invalid, inconsistent, or not supported by this object
-10728758510xC00D36B5The callee is currently not accepting further input
-10728758500xC00D36B6This object needs to be initialized before the requested operation can be carried out
-10728758490xC00D36B7The requested representation is not supported by this object
-10728758470xC00D36B9An object ran out of media types to suggest therefore the requested chain of streaming objects cannot be completed
-10728758460xC00D36BAThe object does not support the specified service
-10728758450xC00D36BBAn unexpected error has occurred in the operation requested
-10728758440xC00D36BCInvalid name
-10728758430xC00D36BDInvalid type
-10728758420xC00D36BEThe file does not conform to the relevant file format specification
-10728758410xC00D36BFInvalid index
-10728758400xC00D36C0An invalid timestamp was given
-10728758370xC00D36C3The scheme of the given URL is unsupported
-10728758360xC00D36C4The byte stream type of the given URL is unsupported
-10728758350xC00D36C5The given time format is unsupported
-10728758320xC00D36C8The Media Sample does not have a timestamp
-10728758310xC00D36C9The Media Sample does not have a duration
-10728758290xC00D36CBThe request failed because the data in the stream is corrupt
-10728758250xC00D36CFReal time services are not available
-10728758240xC00D36D0The specified rate is not supported
-10728758230xC00D36D1This component does not support stream-thinning
-10728758220xC00D36D2The call failed because no reverse playback rates are available
-10728758210xC00D36D3The requested rate transition cannot occur in the current state
-10728758200xC00D36D4The requested rate change has been pre-empted and will not occur
-10728758190xC00D36D5The specified object or value does not exist
-10728758180xC00D36D6The requested value is not available
-10728758170xC00D36D7The specified operation requires a clock and no clock is available
-10728758150xC00D36D9This callback has already been passed in to this event generator
-10728758140xC00D36DASome component is already listening to events on this event generator
-10728758130xC00D36DBThis timer was orphaned before its callback time arrived
-10728758120xC00D36DCA state transition is already pending
-10728758110xC00D36DDThe requested state transition is unsupported
-10728758100xC00D36DEAn unrecoverable error has occurred
-10728758090xC00D36DFThe provided sample has too many buffers
-10728758080xC00D36E0The provided sample is not writable
-10728758060xC00D36E2The specified key is not valid
-10728758050xC00D36E3You are calling MFStartup with the wrong MF_VERSION. Mismatched bits?
-10728758040xC00D36E4The caption of the given URL is unsupported
-10728758030xC00D36E5The operation on the current offset is not permitted
-10728758020xC00D36E6The requested attribute was not found
-10728758010xC00D36E7The specified property type is not allowed in this context
-10728758000xC00D36E8The specified property type is not supported
-10728757990xC00D36E9The specified property is empty
-10728757980xC00D36EAThe specified property is not empty
-10728757970xC00D36EBThe vector property specified is not allowed in this context
-10728757960xC00D36ECA vector property is required in this context
-10728757950xC00D36EDThe operation is cancelled
-10728757940xC00D36EEThe provided bytestream was expected to be seekable and it is not
-10728757930xC00D36EFThe Media Foundation platform is disabled when the system is running in Safe Mode
-10728757920xC00D36F0The Media Source could not parse the byte stream
-10728757910xC00D36F1Mutually exclusive flags have been specified to source resolver. This flag combination is invalid
-10728757900xC00D36F2MediaProc is in the wrong state
-10728757890xC00D36F3Real time I/O service can not provide requested throughput
-10728757880xC00D36F4The workqueue cannot be registered with more classes
-10728757870xC00D36F5This operation cannot succeed because another thread owns this object
-10728757860xC00D36F6Internal. Bitpump not found
-10728757850xC00D36F7No more RT memory available
-10728757840xC00D36F8An MMCSS class has not been set for this work queue
-10728757820xC00D36FAActivate failed to create mediasink. Call OutputNode::GetUINT32(MF_TOPONODE_MAJORTYPE) for more information
-10728757810xC00D36FBThe length of the provided bytestream is unknown
-10728757800xC00D36FCThe media session cannot pause from a stopped state
-10728757780xC00D36FEThe data specified for the media type is supported, but would require a format change, which is not supported by this object
-10728757770xC00D36FFThe operation failed because an invalid combination of workqueue ID and flags was specified
-10728757760xC00D3700No DRM support is available
-10728757750xC00D3701This operation is not authorized
-10728757740xC00D3702The value is not in the specified or valid range
-10728757730xC00D3703The registered codec merit is not valid
-10728757720xC00D3704Hardware MFT failed to start streaming due to lack of hardware resources
-10728757710xC00D3705The operation is already in progress
-10728757700xC00D3706No Hardware DRM support is available
-10728748560xC00D3A98Not enough data have been parsed to carry out the requested action
-10728748550xC00D3A99There is a gap in the ASF data provided
-10728748540xC00D3A9AThe data provided are not valid ASF
-10728748530xC00D3A9BThe packet is opaque, so the requested information cannot be returned
-10728748520xC00D3A9CThe requested operation failed since there is no appropriate ASF index
-10728748510xC00D3A9DThe value supplied is out of range for this operation
-10728748500xC00D3A9EThe index entry requested needs to be loaded before it can be available
-10728748490xC00D3A9FThe packet has reached the maximum number of payloads
-10728748480xC00D3AA0Stream type is not supported
-10728748470xC00D3AA1One or more ASF packets were dropped
-10728738560xC00D3E80There are no events available in the queue
-10728738540xC00D3E82A media source cannot go from the stopped state to the paused state
-10728738520xC00D3E84The media stream cannot process any more samples because there are no more samples in the stream
-10728738510xC00D3E85The request is invalid because Shutdown() has been called
-10728738500xC00D3E86The MP3 object was not found
-10728738490xC00D3E87The MP3 parser ran out of data before finding the MP3 object
-10728738480xC00D3E88The file is not really a MP3 file
-10728738470xC00D3E89The MP3 file is not supported
-10728738460xC00D3E8AThe Media stream has no duration
-10728738440xC00D3E8CThe Media format is recognized but is invalid
-10728738430xC00D3E8DThe property requested was not found
-10728738420xC00D3E8EThe property is read only
-10728738410xC00D3E8FThe specified property is not allowed in this context
-10728738390xC00D3E91The media source is not started
-10728738320xC00D3E98The Media format is recognized but not supported
-10728738310xC00D3E99The MPEG frame has bad CRC
-10728738300xC00D3E9AThe file is not protected
-10728738290xC00D3E9BThe media source is in the wrong state
-10728738280xC00D3E9CNo streams are selected in source presentation descriptor
-10728738270xC00D3E9DNo key frame sample was found
-10728738260xC00D3E9EThe characteristics of the media source are not supported
-10728738250xC00D3E9FNo audio recording device was found
-10728738240xC00D3EA0The requested audio recording device is currently in use
-10728738230xC00D3EA1The audio recording device is no longer present
-10728738220xC00D3EA2The video recording device is no longer present
-10728738210xC00D3EA3The video recording device is preempted by another immersive application
-10728728560xC00D4268An attempt to acquire a network resource failed
-10728728550xC00D4269Error writing to the network
-10728728540xC00D426AError reading from the network
-10728728530xC00D426BInternal. Entry cannot complete operation without network
-10728728520xC00D426CInternal. Async op is required
-10728728510xC00D426DInternal. Bandwidth levels are not supported
-10728728500xC00D426EInternal. Stream groups are not supported
-10728728490xC00D426FManual stream selection is not supported
-10728728480xC00D4270Invalid presentation descriptor
-10728728470xC00D4271Cannot find cache stream
-10728728440xC00D4274Internal. Entry cannot complete operation without input
-10728728430xC00D4275The client redirected to another server
-10728728420xC00D4276The client is redirected to a proxy server
-10728728410xC00D4277The client reached maximum redirection limit
-10728728400xC00D4278The server, a computer set up to offer multimedia content to other computers, could not handle your request for multimedia content in a timely manner. Please try again later
-10728728390xC00D4279The control socket is closed by the client
-10728728380xC00D427AThe server received invalid data from the client on the control connection
-10728728370xC00D427BThe server is not a compatible streaming media server
-10728728360xC00D427CUrl
-10728728350xC00D427DData is not available
-10728728340xC00D427EEnd of line
-10728728330xC00D427FThe request could not be understood by the server
-10728728320xC00D4280The server encountered an unexpected condition which prevented it from fulfilling the request
-10728728310xC00D4281Session not found
-10728728300xC00D4282There is no connection established with the Windows Media server. The operation failed
-10728728290xC00D4283The network connection has failed
-10728728280xC00D4284The 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
-10728728270xC00D4285The Windows Media server is denying access. The username and/or password might be incorrect
-10728728260xC00D4286The proxy server is denying access. The username and/or password might be incorrect
-10728728250xC00D4287Unable to establish a connection to the server
-10728728240xC00D4288The specified push template is invalid
-10728728230xC00D4289The specified push publishing point is invalid
-10728728220xC00D428AThe requested resource is in use
-10728728210xC00D428BThe Publishing Point or file on the Windows Media Server is no longer available
-10728728200xC00D428CThe proxy experienced an error while attempting to contact the media server
-10728728190xC00D428DThe proxy did not receive a timely response while attempting to contact the media server
-10728728180xC00D428EThe server is currently unable to handle the request due to a temporary overloading or maintenance of the server
-10728728170xC00D428FThe encoding process was unable to keep up with the amount of supplied data
-10728728160xC00D4290Session not found
-10728728150xC00D4291The requested URL is not available in offline mode
-10728728140xC00D4292A device in the network is blocking UDP traffic
-10728728130xC00D4293The specified configuration value is not supported
-10728728120xC00D4294The networking protocol is disabled
-10728728110xC00D4295The companion driver asked the OS to disconnect from the receiver
-10728718560xC00D4650This object has already been initialized and cannot be re-initialized at this time
-10728718550xC00D4651The amount of data passed in exceeds the given bitrate and buffer window
-10728718540xC00D4652The sample was passed in too late to be correctly processed
-10728718530xC00D4653The requested action cannot be carried out until the object is flushed and the queue is emptied
-10728718520xC00D4654The profile is invalid
-10728718510xC00D4655The index that is being generated needs to be committed before the requested action can be carried out
-10728718500xC00D4656The index that is necessary for the requested action is not found
-10728718490xC00D4657The requested index cannot be added in-place to the specified ASF content
-10728718480xC00D4658The ASF leaky bucket parameters must be specified in order to carry out this request
-10728718470xC00D4659The stream id is invalid. The valid range for ASF stream id is from 1 to 127
-10728708560xC00D4A38The requested Stream Sink has been removed and cannot be used
-10728708540xC00D4A3AThe various Stream Sinks in this Media Sink are too far out of sync for the requested action to take place
-10728708530xC00D4A3BStream Sinks cannot be added to or removed from this Media Sink because its set of streams is fixed
-10728708520xC00D4A3CThe given Stream Sink already exists
-10728708510xC00D4A3DSample allocations have been canceled
-10728708500xC00D4A3EThe sample allocator is currently empty, due to outstanding requests
-10728708490xC00D4A3FWhen we try to stop a stream sink, it is already stopped
-10728708480xC00D4A40The ASF file sink could not reserve AVIO because the bitrate is unknown
-10728708470xC00D4A41No streams are selected in sink presentation descriptor
-10728708450xC00D4A43A metadata item was too long to write to the output container
-10728708440xC00D4A44The operation failed because no samples were processed by the sink
-10728708430xC00D4A45Sink could not create valid output file because required headers were not provided to the sink
-10728698560xC00D4E20There is no available procamp hardware with which to perform color correction
-10728698550xC00D4E21There is no available deinterlacing hardware with which to deinterlace the video stream
-10728698540xC00D4E22A video stream requires copy protection to be enabled, but there was a failure in attempting to enable copy protection
-10728698530xC00D4E23A component is attempting to access a surface for sharing that is not shared
-10728698520xC00D4E24A component is attempting to access a shared device that is already locked by another component
-10728698510xC00D4E25The device is no longer available. The handle should be closed and a new one opened
-10728698500xC00D4E26A video sample is not currently queued on a stream that is required for mixing
-10728697560xC00D4E84No audio playback device was found
-10728697550xC00D4E85The requested audio playback device is currently in use
-10728697540xC00D4E86The audio playback device is no longer present
-10728697530xC00D4E87The audio service is not running
-10728688500xC00D520EThe 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
-10728688470xC00D5211No suitable transform was found to decrypt the content
-10728688460xC00D5212No suitable transform was found to encode or decode the content
-10728688450xC00D5213Unable to find a way to connect nodes
-10728688440xC00D5214Unsupported operations in topoloader
-10728688430xC00D5215The topology or its nodes contain incorrectly set time attributes
-10728688420xC00D5216The topology contains loops, which are unsupported in media foundation topologies
-10728688410xC00D5217A source stream node in the topology does not have a presentation descriptor
-10728688400xC00D5218A source stream node in the topology does not have a stream descriptor
-10728688390xC00D5219A stream descriptor was set on a source stream node but it was not selected on the presentation descriptor
-10728688380xC00D521AA source stream node in the topology does not have a source
-10728688370xC00D521BThe topology loader does not support sink activates on output nodes
-10728648520xC00D61ACThe sequencer cannot find a segment with the given ID
-10728648500xC00D61AECannot find source in source cache
-10728618560xC00D6D60A valid type has not been set for this stream or a stream that it depends on
-10728618550xC00D6D61A stream change has occurred. Output cannot be produced until the streams have been renegotiated
-10728618540xC00D6D62The transform cannot take the requested action until all of the input data it currently holds is processed or flushed
-10728618530xC00D6D63The transform requires a profile but no profile was supplied or found
-10728618520xC00D6D64The transform requires a profile but the supplied profile was invalid or corrupt
-10728618510xC00D6D65The transform requires a profile but the supplied profile ended unexpectedly while parsing
-10728618500xC00D6D66The property ID does not match any property supported by the transform
-10728618490xC00D6D67The variant does not have the type expected for this property ID
-10728618480xC00D6D68An attempt was made to set the value on a read-only property
-10728618470xC00D6D69The array property value has an unexpected number of dimensions
-10728618460xC00D6D6AThe array or blob property value has an unexpected size
-10728618450xC00D6D6BThe property value is out of range for this transform
-10728618440xC00D6D6CThe property value is incompatible with some other property or mediatype set on the transform
-10728618430xC00D6D6DThe requested operation is not supported for the currently set output mediatype
-10728618420xC00D6D6EThe requested operation is not supported for the currently set input mediatype
-10728618410xC00D6D6FThe requested operation is not supported for the currently set combination of mediatypes
-10728618400xC00D6D70The requested feature is not supported in combination with some other currently enabled feature
-10728618380xC00D6D72The transform cannot produce output until it gets more input samples
-10728618370xC00D6D73The requested operation is not supported for the current speaker configuration
-10728618360xC00D6D74The transform cannot accept mediatype changes in the middle of processing
-10728618340xC00D6D76The input type is not supported for D3D device
-10728618330xC00D6D77The caller does not appear to support this transform's asynchronous capabilities
-10728618320xC00D6D78An audio compression manager driver could not be initialized by the transform
-10728608560xC00D7148You are not allowed to open this file. Contact the content provider for further assistance
-10728608550xC00D7149The license for this media file has expired. Get a new license or contact the content provider for further assistance
-10728608540xC00D714AYou need a license to perform the requested operation on this media file
-10728608530xC00D714BThe licenses for your media files are corrupted. Contact Microsoft product support
-10728608520xC00D714CThe APP needs to provide IMFContentProtectionManager callback to access the protected media file
-10728608510xC00D714DClient does not have rights to restore licenses
-10728608500xC00D714ELicenses are restricted and hence can not be backed up
-10728608490xC00D714FLicense restore requires machine to be individualized
-10728608470xC00D7151Component is revoked
-10728608460xC00D7152Trusted functionality is currently disabled on this component
-10728608450xC00D7153No Action is set on WMDRM Output Trust Authority
-10728608440xC00D7154Action is already set on WMDRM Output Trust Authority
-10728608430xC00D7155DRM Heaader is not available
-10728608420xC00D7156Current encryption scheme is not supported
-10728608410xC00D7157Action does not match with current configuration
-10728608400xC00D7158Invalid policy for WMDRM Output Trust Authority
-10728608390xC00D7159The policies that the Input Trust Authority requires to be enforced are unsupported by the outputs
-10728608380xC00D715AThe OPL that the license requires to be enforced are not supported by the Input Trust Authority
-10728608370xC00D715BThe topology could not be successfully verified
-10728608360xC00D715CSignature verification could not be completed successfully for this component
-10728608350xC00D715DRunning this process under a debugger while using protected content is not allowed
-10728608340xC00D715EMF component has expired
-10728608330xC00D715FThe current GRL on the machine does not meet the minimum version requirements
-10728608320xC00D7160The current GRL on the machine does not contain any renewal entries for the specified revocation
-10728608310xC00D7161The current GRL on the machine does not contain any extensible entries for the specified extension GUID
-10728608300xC00D7162The kernel isn't secure for high security level content
-10728608290xC00D7163The response from protected environment driver isn't valid
-10728608270xC00D7165A non-PE process tried to talk to PEAuth
-10728608250xC00D7167We need to reboot the machine
-10728608220xC00D716AThe GRL file is not correctly formed, it may have been corrupted or overwritten
-10728608210xC00D716BThe GRL file is in a format newer than those recognized by this GRL Reader
-10728608200xC00D716CThe GRL was reloaded and required all processes that can run protected media to restart
-10728608190xC00D716DThe GRL was reloaded and the current process needs to restart
-10728608180xC00D716EThe user space is untrusted for protected content play
-10728608170xC00D716FPEAuth communication session hasn't been started
-10728608160xC00D7170Insufficient memory for response
-10728608150xC00D7171PEAuth's public key is revoked
-10728608140xC00D7172The GRL is absent
-10728608120xC00D7174The Protected Environment is untrusted
-10728608110xC00D7175The Protected Environment Authorization service (PEAUTH) has not been started
-10728608100xC00D7176The sample protection algorithms supported by components are not compatible
-10728608090xC00D7177No more protected environment sessions can be supported
-10728608080xC00D7178WMDRM ITA does not allow protected content with high security level for this release
-10728608070xC00D7179WMDRM ITA cannot allow the requested action for the content as one or more components is not properly signed
-10728608060xC00D717AWMDRM ITA does not support the requested action
-10728608050xC00D717BWMDRM ITA encountered an error in parsing the Secure Audio Path parameters
-10728608040xC00D717CThe Policy Manager action passed in is invalid
-10728608030xC00D717DThe structure specifying Output Protection Level is not the correct format
-10728608020xC00D717EWMDRM ITA does not recognize the Explicite Analog Video Output Protection guid specified in the license
-10728608010xC00D717FIMFPMPHost object not available
-10728608000xC00D7180WMDRM ITA could not initialize the Output Protection Level data
-10728607990xC00D7181WMDRM ITA does not recognize the Analog Video Output specified by the OTA
-10728607980xC00D7182WMDRM ITA does not recognize the Digital Video Output specified by the OTA
-10728607970xC00D7183The protected stream cannot be resolved without the callback PKEY_PMP_Creation_Callback in the configuration property store
-10728607960xC00D7184A valid hostname and port number could not be found in the DTCP parameters
-10728607950xC00D7185The content protection system was not enabled by the application
-10728607940xC00D7186The content protection system is not supported
-10728607930xC00D7187DRM migration is not supported for the content
-10728607920xC00D7188Authentication of the HDCP link failed
-10728607910xC00D7189The HDCP link failed after being established
-10728498560xC00D9C40The continuity key supplied is not currently valid
-10728498550xC00D9C41No Presentation Time Source has been specified
-10728498540xC00D9C42The clock is already in the requested state
-10728498530xC00D9C43The clock has too many advanced features to carry out the request
-10728488560xC00DA028The component does not support any more drop modes
-10728488550xC00DA029The component does not support any more quality levels
-10728488540xC00DA02AThe component does not support drop time functionality
-10728488530xC00DA02BQuality Manager needs to wait longer before bumping the Quality Level up
-10728488520xC00DA02CQuality Manager is in an invalid state. Quality Management is off at this moment
-10728478560xC00DA410No transcode output container type is specified
-10728478550xC00DA411The profile does not have a media type configuration for any selected source streams
-10728478540xC00DA412Cannot find an encoder MFT that accepts the user preferred output type
-10728478530xC00DA413The profile is invalid
-10728468560xC00DA7F8Memory allocator is not initialized
-10728468550xC00DA7F9Memory allocator is not committed yet
-10728468540xC00DA7FAMemory allocator has already been committed
-10728468530xC00DA7FBAn error occurred in media stream
-10728468520xC00DA7FCStream is not in a state to handle the request
-10728468510xC00DA7FDHardware stream is not connected yet
-10728458560xC00DABE0No capture devices are available
-10728458550xC00DABE1No output was set for recording
-10728458540xC00DABE2The current capture sink configuration does not support mirroring
-10728458530xC00DABE3The current capture sink configuration does not support rotation
-10728458520xC00DABE4The op is invalid
-10728458510xC00DABE5The effects previously added were incompatible with the new topology which caused all effects to be removed
-10728458500xC00DABE6The current capture source does not have an independent photo stream
-10728458490xC00DABE7The current capture source does not have a video stream
-10728458480xC00DABE8The current capture source does not have an audio stream
-10728458470xC00DABE9The capture source device has an asynchronous extended property operation in progress
-10728458460xC00DABEAA property cannot be set because a photo or photo sequence is in progress
-10728458450xC00DABEBNo more samples in queue
-10728458440xC00DABECHardware accelerated thumbnail generation is not supported for the currently selected mediatype on the mediacapture stream
-10712499440xC02605E8The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote
-10712473570xC0261003Checksum of the obtained monitor descriptor is invalid
-10712473560xC0261004Monitor descriptor contains an invalid standard timing block
-10712473550xC0261005WMI data block registration failed for one of the MSMonitorClass WMI subclasses
-10712473540xC0261006Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number
-10712473530xC0261007Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name
-10712473520xC0261008There is no monitor descriptor data at the specified (offset, size) region
-10712473510xC0261009Monitor descriptor contains an invalid detailed timing block
-10712473500xC026100AMonitor descriptor contains invalid manufacture date
-10712432640xC0262000Exclusive mode ownership is needed to create unmanaged primary allocation
-10712432630xC0262001The driver needs more DMA buffer space in order to complete the requested operation
-10712432620xC0262002Specified display adapter handle is invalid
-10712432610xC0262003Specified display adapter and all of its state has been reset
-10712432600xC0262004The driver stack doesn't match the expected driver model
-10712432590xC0262005Present happened but ended up into the changed desktop mode
-10712432580xC0262006Nothing to present due to desktop occlusion
-10712432570xC0262007Not able to present due to denial of desktop access
-10712432560xC0262008Not able to present with color convertion
-10712432550xC0262009The kernel driver detected a version mismatch between it and the user mode driver
-10712432530xC026200BPresent redirection is disabled (desktop windowing management subsystem is off)
-10712432520xC026200CPrevious exclusive VidPn source owner has released its ownership
-10712432510xC026200DWindow DC is not available for presentation
-10712432500xC026200EWindowless present is disabled (desktop windowing management subsystem is off)
-10712430080xC0262100Not enough video memory available to complete the operation
-10712430070xC0262101Couldn't probe and lock the underlying memory of an allocation
-10712430060xC0262102The allocation is currently busy
-10712430050xC0262103An object being referenced has reach the maximum reference count already and can't be reference further
-10712430040xC0262104A problem couldn't be solved due to some currently existing condition. The problem should be tried again later
-10712430030xC0262105A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately
-10712430020xC0262106The allocation is invalid
-10712430010xC0262107No more unswizzling aperture are currently available
-10712430000xC0262108The current allocation can't be unswizzled by an aperture
-10712429990xC0262109The request failed because a pinned allocation can't be evicted
-10712429920xC0262110The allocation can't be used from its current segment location for the specified operation
-10712429910xC0262111A locked allocation can't be used in the current command buffer
-10712429900xC0262112The allocation being referenced has been closed permanently
-10712429890xC0262113An invalid allocation instance is being referenced
-10712429880xC0262114An invalid allocation handle is being referenced
-10712429870xC0262115The allocation being referenced doesn't belong to the current device
-10712429860xC0262116The specified allocation lost its content
-10712427520xC0262200GPU exception is detected on the given device. The device is not able to be scheduled
-10712424960xC0262300Specified VidPN topology is invalid
-10712424950xC0262301Specified VidPN topology is valid but is not supported by this model of the display adapter
-10712424940xC0262302Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources
-10712424930xC0262303Specified VidPN handle is invalid
-10712424920xC0262304Specified video present source is invalid
-10712424910xC0262305Specified video present target is invalid
-10712424900xC0262306Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional)
-10712424880xC0262308Specified VidPN source mode set is invalid
-10712424870xC0262309Specified VidPN target mode set is invalid
-10712424860xC026230ASpecified video signal frequency is invalid
-10712424850xC026230BSpecified video signal active region is invalid
-10712424840xC026230CSpecified video signal total region is invalid
-10712424800xC0262310Specified video present source mode is invalid
-10712424790xC0262311Specified video present target mode is invalid
-10712424780xC0262312Pinned mode must remain in the set on VidPN's cofunctional modality enumeration
-10712424770xC0262313Specified video present path is already in VidPN's topology
-10712424760xC0262314Specified mode is already in the mode set
-10712424750xC0262315Specified video present source set is invalid
-10712424740xC0262316Specified video present target set is invalid
-10712424730xC0262317Specified video present source is already in the video present source set
-10712424720xC0262318Specified video present target is already in the video present target set
-10712424710xC0262319Specified VidPN present path is invalid
-10712424700xC026231AMiniport has no recommendation for augmentation of the specified VidPN's topology
-10712424690xC026231BSpecified monitor frequency range set is invalid
-10712424680xC026231CSpecified monitor frequency range is invalid
-10712424670xC026231DSpecified frequency range is not in the specified monitor frequency range set
-10712424650xC026231FSpecified frequency range is already in the specified monitor frequency range set
-10712424640xC0262320Specified mode set is stale. Please reacquire the new mode set
-10712424630xC0262321Specified monitor source mode set is invalid
-10712424620xC0262322Specified monitor source mode is invalid
-10712424610xC0262323Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration
-10712424600xC0262324ID of the specified mode is already used by another mode in the set
-10712424590xC0262325System failed to determine a mode that is supported by both the display adapter and the monitor connected to it
-10712424580xC0262326Number of video present targets must be greater than or equal to the number of video present sources
-10712424570xC0262327Specified present path is not in VidPN's topology
-10712424560xC0262328Display adapter must have at least one video present source
-10712424550xC0262329Display adapter must have at least one video present target
-10712424540xC026232ASpecified monitor descriptor set is invalid
-10712424530xC026232BSpecified monitor descriptor is invalid
-10712424520xC026232CSpecified descriptor is not in the specified monitor descriptor set
-10712424510xC026232DSpecified descriptor is already in the specified monitor descriptor set
-10712424500xC026232EID of the specified monitor descriptor is already used by another descriptor in the set
-10712424490xC026232FSpecified video present target subset type is invalid
-10712424480xC0262330Two or more of the specified resources are not related to each other, as defined by the interface semantics
-10712424470xC0262331ID of the specified video present source is already used by another source in the set
-10712424460xC0262332ID of the specified video present target is already used by another target in the set
-10712424450xC0262333Specified VidPN source cannot be used because there is no available VidPN target to connect it to
-10712424440xC0262334Newly arrived monitor could not be associated with a display adapter
-10712424430xC0262335Display adapter in question does not have an associated VidPN manager
-10712424420xC0262336VidPN manager of the display adapter in question does not have an active VidPN
-10712424410xC0262337Specified VidPN topology is stale. Please reacquire the new topology
-10712424400xC0262338There is no monitor connected on the specified video present target
-10712424390xC0262339Specified source is not part of the specified VidPN's topology
-10712424380xC026233ASpecified primary surface size is invalid
-10712424370xC026233BSpecified visible region size is invalid
-10712424360xC026233CSpecified stride is invalid
-10712424350xC026233DSpecified pixel format is invalid
-10712424340xC026233ESpecified color basis is invalid
-10712424330xC026233FSpecified pixel value access mode is invalid
-10712424320xC0262340Specified target is not part of the specified VidPN's topology
-10712424310xC0262341Failed to acquire display mode management interface
-10712424300xC0262342Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it
-10712424290xC0262343Specified VidPN is active and cannot be accessed
-10712424280xC0262344Specified VidPN present path importance ordinal is invalid
-10712424270xC0262345Specified VidPN present path content geometry transformation is invalid
-10712424260xC0262346Specified content geometry transformation is not supported on the respective VidPN present path
-10712424250xC0262347Specified gamma ramp is invalid
-10712424240xC0262348Specified gamma ramp is not supported on the respective VidPN present path
-10712424230xC0262349Multi-sampling is not supported on the respective VidPN present path
-10712424220xC026234ASpecified mode is not in the specified mode set
-10712424190xC026234DSpecified VidPN topology recommendation reason is invalid
-10712424180xC026234ESpecified VidPN present path content type is invalid
-10712424170xC026234FSpecified VidPN present path copy protection type is invalid
-10712424160xC0262350No more than one unassigned mode set can exist at any given time for a given VidPN source/target
-10712424140xC0262352Specified scanline ordering type is invalid
-10712424130xC0262353Topology changes are not allowed for the specified VidPN
-10712424120xC0262354All available importance ordinals are already used in specified topology
-10712424110xC0262355Specified primary surface has a different private format attribute than the current primary surface
-10712424100xC0262356Specified mode pruning algorithm is invalid
-10712424090xC0262357Specified monitor capability origin is invalid
-10712424080xC0262358Specified monitor frequency range constraint is invalid
-10712424070xC0262359Maximum supported number of present paths has been reached
-10712424060xC026235AMiniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology
-10712424050xC026235BSpecified client type was not recognized
-10712424040xC026235CClient VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet)
-10712422400xC0262400Specified display adapter child device already has an external device connected to it
-10712422390xC0262401Specified display adapter child device does not support descriptor exposure
-10712421920xC0262430The display adapter is not linked to any other adapters
-10712421910xC0262431Lead adapter in a linked configuration was not enumerated yet
-10712421900xC0262432Some chain adapters in a linked configuration were not enumerated yet
-10712421890xC0262433The chain of linked adapters is not ready to start because of an unknown failure
-10712421880xC0262434An attempt was made to start a lead link display adapter when the chain links were not started yet
-10712421870xC0262435An attempt was made to power up a lead link display adapter when the chain links were powered down
-10712421860xC0262436The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state
-10712421840xC0262438The driver trying to start is not the same as the driver for the POSTed display adapter
-10712421810xC026243BAn operation is being attempted that requires the display adapter to be in a quiescent state
-10712419840xC0262500The driver does not support OPM
-10712419830xC0262501The driver does not support COPP
-10712419820xC0262502The driver does not support UAB
-10712419810xC0262503The specified encrypted parameters are invalid
-10712419790xC0262505The GDI display device passed to this function does not have any active video outputs
-10712419730xC026250BAn internal error caused this operation to fail
-10712419720xC026250CThe function failed because the caller passed in an invalid OPM user mode handle
-10712419700xC026250EA certificate could not be returned because the certificate buffer passed to the function was too small
-10712419690xC026250FA video output could not be created because the frame buffer is in spanning mode
-10712419680xC0262510A video output could not be created because the frame buffer is in theater mode
-10712419670xC0262511The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware
-10712419660xC0262512The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification
-10712419650xC0262513The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP
-10712419640xC0262514The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP
-10712419630xC0262515The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A
-10712419620xC0262516The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output
-10712419610xC0262517The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high
-10712419600xC0262518The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs
-10712419580xC026251AThe operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop
-10712419570xC026251BThe method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote
-10712419560xC026251CEither the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only
-10712419550xC026251DThe 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
-10712419540xC026251EThe method failed because an unexpected error occurred inside of a display driver
-10712419530xC026251FEither the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only
-10712419520xC0262520The 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
-10712419510xC0262521The 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
-10712418560xC0262580The monitor connected to the specified video output does not have an I2C bus
-10712418550xC0262581No device on the I2C bus has the specified address
-10712418540xC0262582An error occurred while transmitting data to the device on the I2C bus
-10712418530xC0262583An error occurred while receiving data from the device on the I2C bus
-10712418520xC0262584The monitor does not support the specified VCP code
-10712418510xC0262585The data received from the monitor is invalid
-10712418500xC0262586The 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
-10712418490xC0262587The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification
-10712418480xC0262588An internal Monitor Configuration API error occurred
-10712418470xC0262589An operation failed because a DDC/CI message had an invalid value in its command field
-10712418460xC026258AAn error occurred because the field length of a DDC/CI message contained an invalid value
-10712418450xC026258BAn 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
-10712418440xC026258CThis function failed because an invalid monitor handle was passed to it
-10712418430xC026258DThe operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications
-10712417680xC02625D8A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value
-10712417670xC02625D9The monitor's VCP Version (0xDF) VCP code returned an invalid version value
-10712417660xC02625DAThe monitor does not comply with the MCCS specification it claims to support
-10712417650xC02625DBThe 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
-10712417640xC02625DCThe Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification
-10712417620xC02625DEThe monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification
-10712417610xC02625DFSetMonitorColorTemperature()'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
-10712417600xC02625E0This 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
-10712417590xC02625E1This function cannot find an actual GDI display device which corresponds to the specified GDI display device name
-10712417580xC02625E2The function failed because the specified GDI display device was not attached to the Windows desktop
-10712417570xC02625E3This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them
-10712417560xC02625E4The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned
-10712417550xC02625E5The function failed because the specified GDI device did not have any monitors associated with it
-10712417540xC02625E6An array passed to the function cannot hold all of the data that the function must copy into the array
-10712417530xC02625E7An internal error caused an operation to fail
-10703298410xC034100FThe TCP connection is not offloadable because of a local policy setting
-10703298380xC0341012The TCP connection is not offloadable by the Chimney Offload target
-10703298370xC0341013The IP Path object is not in an offloadable state
-10702684140xC0350002The hypervisor does not support the operation because the specified hypercall code is not supported
-10702684130xC0350003The hypervisor does not support the operation because the encoding for the hypercall input register is not supported
-10702684120xC0350004The hypervisor could not perform the operation beacuse a parameter has an invalid alignment
-10702684110xC0350005The hypervisor could not perform the operation beacuse an invalid parameter was specified
-10702684100xC0350006Access to the specified object was denied
-10702684090xC0350007The hypervisor could not perform the operation because the partition is entering or in an invalid state
-10702684080xC0350008The operation is not allowed in the current state
-10702684070xC0350009The hypervisor does not recognize the specified partition property
-10702684060xC035000AThe specified value of a partition property is out of range or violates an invariant
-10702684050xC035000BThere is not enough memory in the hypervisor pool to complete the operation
-10702684040xC035000CThe maximum partition depth has been exceeded for the partition hierarchy
-10702684030xC035000DA partition with the specified partition Id does not exist
-10702684020xC035000EThe hypervisor could not perform the operation because the specified VP index is invalid
-10702683990xC0350011The hypervisor could not perform the operation because the specified port identifier is invalid
-10702683980xC0350012The hypervisor could not perform the operation because the specified connection identifier is invalid
-10702683970xC0350013Not enough buffers were supplied to send a message
-10702683960xC0350014The previous virtual interrupt has not been acknowledged
-10702683940xC0350016The previous virtual interrupt has already been acknowledged
-10702683930xC0350017The indicated partition is not in a valid state for saving or restoring
-10702683920xC0350018The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled
-10702683910xC0350019The 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
-10702683900xC035001AThe proximity domain information is invalid
-10702683890xC035001BAn attempt to retrieve debugging data failed because none was available
-10702683880xC035001CThe physical connection being used for debuggging has not recorded any receive activity since the last operation
-10702683870xC035001DThere are not enough resources to complete the operation
-10702683860xC035001EA hypervisor feature is not available to the user
-10702683650xC0350033The specified buffer was too small to contain all of the requested data
-10702683600xC0350038The 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
-10702683560xC035003CValidation of CPUID data of the processor failed
-10702683550xC035003DValidation of XSAVE CPUID data of the processor failed
-10702683540xC035003EProcessor did not respond within the timeout period
-10702683530xC035003FSMX has been enabled in the BIOS
-10702683510xC0350041The hypervisor could not perform the operation because the specified LP index is invalid
-10702683360xC0350050The supplied register value is invalid
-10702683350xC0350051The supplied virtual trust level is not in the correct state to perform the requested operation
-10702683310xC0350055No execute feature (NX) is not present or not enabled in the BIOS
-10702683290xC0350057The supplied device ID is invalid
-10702683280xC0350058The operation is not allowed in the current device state
-10702683200xC0350060The supplied page request specifies a memory access that the guest does not have permissions to perform
-10702643200xC0351000No hypervisor is present on this system
-10701373430xC0370001The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373420xC0370002The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373410xC0370003The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373400xC0370004No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373390xC0370005The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373380xC0370006The partition name of the virtualization infrastructure driver exceeds the maximum
-10701373370xC0370007The message queue name of the virtualization infrastructure driver exceeds the maximum
-10701373360xC0370008Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists
-10701373350xC0370009The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373340xC037000AThe virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373330xC037000BA message queue with the same name already exists for the virtualization infrastructure driver
-10701373320xC037000CThe memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373310xC037000DThe memory block for the virtualization infrastructure driver is still being used and cannot be destroyed
-10701373300xC037000ECannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373290xC037000FThe non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration
-10701373280xC0370010The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology
-10701373270xC0370011The memory block for the virtualization infrastructure driver is already associated with a message queue
-10701373260xC0370012The handle is not a valid memory block handle for the virtualization infrastructure driver
-10701373250xC0370013The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373240xC0370014The handle is not a valid message queue handle for the virtualization infrastructure driver
-10701373230xC0370015The handle is not a valid page range handle for the virtualization infrastructure driver
-10701373220xC0370016Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block
-10701373210xC0370017The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373200xC0370018The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver
-10701373190xC0370019Notifications cannot be created on the memory block because it is use
-10701373180xC037001AThe message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373170xC037001BCannot add a virtual processor to the partition because the maximum has been reached
-10701373160xC037001CCannot stop the virtual processor immediately because of a pending intercept
-10701373150xC037001DInvalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373140xC037001EThe maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373130xC037001FThis kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373120xC0370020Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373110xC0370021The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373100xC0370022The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373090xC0370023Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373080xC0370024The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373070xC0370025Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373060xC0370026Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer
-10701373050xC0370027Cannot 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
-10701373040xC0370028Cannot 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
-10701373030xC0370029Cannot 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
-10700718070xC0380001The configuration database is full
-10700718060xC0380002The configuration data on the disk is corrupted
-10700718050xC0380003The configuration on the disk is not insync with the in-memory configuration
-10700718040xC0380004A majority of disks failed to be updated with the new configuration
-10700718030xC0380005The disk contains non-simple volumes
-10700718020xC0380006The same disk was specified more than once in the migration list
-10700718010xC0380007The disk is already dynamic
-10700718000xC0380008The specified disk id is invalid. There are no disks with the specified disk id
-10700717990xC0380009The specified disk is an invalid disk. Operation cannot complete on an invalid disk
-10700717980xC038000AThe specified disk(s) cannot be removed since it is the last remaining voter
-10700717970xC038000BThe specified disk has an invalid disk layout
-10700717960xC038000CThe disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout
-10700717950xC038000DThe disk layout contains partitions which are not cylinder aligned
-10700717940xC038000EThe disk layout contains partitions which are samller than the minimum size
-10700717930xC038000FThe disk layout contains primary partitions in between logical drives. This is an invalid disk layout
-10700717920xC0380010The disk layout contains more than the maximum number of supported partitions
-10700717910xC0380011The specified disk is missing. The operation cannot complete on a missing disk
-10700717900xC0380012The specified disk is not empty
-10700717890xC0380013There is not enough usable space for this operation
-10700717880xC0380014The force revectoring of bad sectors failed
-10700717870xC0380015The specified disk has an invalid sector size
-10700717860xC0380016The specified disk set contains volumes which exist on disks outside of the set
-10700717850xC0380017A disk in the volume layout provides extents to more than one member of a plex
-10700717840xC0380018A disk in the volume layout provides extents to more than one plex
-10700717830xC0380019Dynamic disks are not supported on this system
-10700717820xC038001AThe specified extent is already used by other volumes
-10700717810xC038001BThe 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
-10700717800xC038001CThe specified volume extent is not within the public region of the disk
-10700717790xC038001DThe specifed volume extent is not sector aligned
-10700717780xC038001EThe specified parition overlaps an EBR (the first track of an extended partition on a MBR disks)
-10700717770xC038001FThe specified extent lengths cannot be used to construct a volume with specified length
-10700717760xC0380020The system does not support fault tolerant volumes
-10700717750xC0380021The specified interleave length is invalid
-10700717740xC0380022There is already a maximum number of registered users
-10700717730xC0380023The specified member is already in-sync with the other active members. It does not need to be regenerated
-10700717720xC0380024The same member index was specified more than once
-10700717710xC0380025The specified member index is greater or equal than the number of members in the volume plex
-10700717700xC0380026The specified member is missing. It cannot be regenerated
-10700717690xC0380027The specified member is not detached. Cannot replace a member which is not detached
-10700717680xC0380028The specified member is already regenerating
-10700717670xC0380029All disks belonging to the pack failed
-10700717660xC038002AThere are currently no registered users for notifications. The task number is irrelevant unless there are registered users
-10700717650xC038002BThe specified notification user does not exist. Failed to unregister user for notifications
-10700717640xC038002CThe notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications
-10700717630xC038002DThe specified number of members is invalid
-10700717620xC038002EThe specified number of plexes is invalid
-10700717610xC038002FThe specified source and target packs are identical
-10700717600xC0380030The specified pack id is invalid. There are no packs with the specified pack id
-10700717590xC0380031The specified pack is the invalid pack. The operation cannot complete with the invalid pack
-10700717580xC0380032The specified pack name is invalid
-10700717570xC0380033The specified pack is offline
-10700717560xC0380034The specified pack already has a quorum of healthy disks
-10700717550xC0380035The pack does not have a quorum of healthy disks
-10700717540xC0380036The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported
-10700717530xC0380037Failed to update the disk's partition layout
-10700717520xC0380038The specified plex is already in-sync with the other active plexes. It does not need to be regenerated
-10700717510xC0380039The same plex index was specified more than once
-10700717500xC038003AThe specified plex index is greater or equal than the number of plexes in the volume
-10700717490xC038003BThe specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline
-10700717480xC038003CThe specified plex is missing
-10700717470xC038003DThe specified plex is currently regenerating
-10700717460xC038003EThe specified plex type is invalid
-10700717450xC038003FThe operation is only supported on RAID-5 plexes
-10700717440xC0380040The operation is only supported on simple plexes
-10700717430xC0380041The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set
-10700717420xC0380042There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications
-10700717410xC0380043There is currently a transaction in process
-10700717400xC0380044An unexpected layout change occurred outside of the volume manager
-10700717390xC0380045The specified volume contains a missing disk
-10700717380xC0380046The specified volume id is invalid. There are no volumes with the specified volume id
-10700717370xC0380047The specified volume length is invalid
-10700717360xC0380048The specified size for the volume is not a multiple of the sector size
-10700717350xC0380049The operation is only supported on mirrored volumes
-10700717340xC038004AThe specified volume does not have a retain partition
-10700717330xC038004BThe specified volume is offline
-10700717320xC038004CThe specified volume already has a retain partition
-10700717310xC038004DThe specified number of extents is invalid
-10700717300xC038004EAll disks participating to the volume must have the same sector size
-10700717290xC038004FThe boot disk experienced failures
-10700717280xC0380050The configuration of the pack is offline
-10700717270xC0380051The configuration of the pack is online
-10700717260xC0380052The specified pack is not the primary pack
-10700717250xC0380053All disks failed to be updated with the new content of the log
-10700717240xC0380054The specified number of disks in a plex is invalid
-10700717230xC0380055The specified number of disks in a plex member is invalid
-10700717220xC0380056The operation is not supported on mirrored volumes
-10700717210xC0380057The operation is only supported on simple and spanned plexes
-10700717200xC0380058The pack has no valid log copies
-10700717190xC0380059A primary pack is already present
-10700717180xC038005AThe specified number of disks is invalid
-10700717170xC038005BThe system does not support mirrored volumes
-10700717160xC038005CThe system does not support RAID-5 volumes
-10700062700xC0390002Entries enumerated have exceeded the allowed threshold
-10699407350xC03A0001The virtual hard disk is corrupted. The virtual hard disk drive footer is missing
-10699407340xC03A0002The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum
-10699407330xC03A0003The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted
-10699407320xC03A0004The system does not recognize the file format of this virtual hard disk
-10699407310xC03A0005The version does not support this version of the file format
-10699407300xC03A0006The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum
-10699407290xC03A0007The system does not support this version of the virtual hard disk.This version of the sparse header is not supported
-10699407280xC03A0008The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt
-10699407270xC03A0009Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk
-10699407260xC03A000AThe virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt
-10699407250xC03A000BThe system does not support this version of the virtual hard disk. The block size is invalid
-10699407240xC03A000CThe virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk
-10699407230xC03A000DThe chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk
-10699407220xC03A000EThe chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk
-10699407210xC03A000FThe 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
-10699407200xC03A0010Failed to read the metadata of the virtual hard disk
-10699407190xC03A0011Failed to write to the metadata of the virtual hard disk
-10699407180xC03A0012The size of the virtual hard disk is not valid
-10699407170xC03A0013The file size of this virtual hard disk is not valid
-10699407160xC03A0014A virtual disk support provider for the specified file was not found
-10699407150xC03A0015The specified disk is not a virtual disk
-10699407140xC03A0016The 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
-10699407130xC03A0017The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk
-10699407120xC03A0018The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain
-10699407110xC03A0019The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain
-10699407100xC03A001AThe requested operation could not be completed due to a virtual disk system limitation. On NTFS, virtual hard disk files must be uncompressed and unencrypted. On ReFS, virtual hard disk files must not have the integrity bit set
-10699407090xC03A001BThe requested operation cannot be performed on a virtual disk of this type
-10699407080xC03A001CThe requested operation cannot be performed on the virtual disk in its current state
-10699407070xC03A001DThe sector size of the physical disk on which the virtual disk resides is not supported
-10699407060xC03A001EThe disk is already owned by a different owner
-10699407050xC03A001FThe disk must be offline or read-only
-10699407040xC03A0020Change Tracking is not initialized for this virtual disk
-10699407030xC03A0021Size of change tracking file exceeded the maximum size limit
-10699407020xC03A0022VHD file is changed due to compaction, expansion, or offline updates
-10699407010xC03A0023Change 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
-10699407000xC03A0024Change Tracking file for the virtual disk is not in a valid state
-10699406990xC03A0025The requested resize operation could not be completed because it might truncate user data residing on the virtual disk
-10699406980xC03A0026The 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
-10699406970xC03A0027The requested operation could not be completed because the virtual disk's size cannot be safely reduced further
-10699406960xC03A0028There is not enough space in the virtual disk file for the provided metadata item
-10699406950xC03A0029The specified change tracking identifier is not valid
-10699406940xC03A002AChange tracking is disabled for the specified virtual hard disk, so no change tracking information is available
-10699406880xC03A0030There is no change tracking data available associated with the specified change tracking identifier
-10677125120xC05C0000The proper error code with sense data was stored on server side
-10676472320xC05CFF00The requested error data is not available on the server
-10676472310xC05CFF01Unit Attention data is available for the initiator to query
-10676472300xC05CFF02The data capacity of the device has changed, resulting in a Unit Attention condition
-10676472290xC05CFF03A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition
-10676472280xC05CFF04A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition
-10676472270xC05CFF05A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition
-10676472260xC05CFF06The data storage format of the device has changed, resulting in a Unit Attention condition
-10676472250xC05CFF07The current initiator is not allowed to perform the SCSI command because of a reservation conflict
-10676472240xC05CFF08Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks
-10676472230xC05CFF09The server version does not match the requested version
-10676472220xC05CFF0AThe requested operation cannot be performed on the virtual disk as it is currently used in shared mode
-10676472210xC05CFF0BInvalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures
-10676472200xC05CFF0CThe requested operation failed due to a missing backing storage file
-10676469760xC05D0000Failed to negotiate a preauthentication integrity hash function
-10676469750xC05D0001The current cluster functional level does not support this SMB dialect
-10676469740xC05D0002Your PC's security settings don't allow you to access shared folders as a guest. Contact your system administrator for more information
-10585374720xC0E80000The command was not recognized by the security core
-10584063990xC0EA0001No applicable app licenses found
-10584063980xC0EA0002CLiP license not found
-10584063970xC0EA0003CLiP device license not found
-10584063960xC0EA0004CLiP license has an invalid signature
-10584063950xC0EA0005CLiP keyholder license is invalid or missing
-10584063940xC0EA0006CLiP license has expired
-10584063930xC0EA0007CLiP license is signed by an unknown source
-10584063920xC0EA0008CLiP license is not signed
-10584063910xC0EA0009CLiP license hardware ID is out of tolerance
-10584063900xC0EA000ACLiP license device ID does not match the device ID in the bound device license
00x00000000The operation completed successfully
10x00000001Incorrect function
20x00000002The system cannot find the file specified
30x00000003The system cannot find the path specified
40x00000004The system cannot open the file
50x00000005Access is denied
60x00000006The handle is invalid
70x00000007The storage control blocks were destroyed
80x00000008Not enough storage is available to process this command
90x00000009The storage control block address is invalid
100x0000000AThe environment is incorrect
110x0000000BAn attempt was made to load a program with an incorrect format
120x0000000CThe access code is invalid
130x0000000DThe data is invalid
140x0000000ENot enough storage is available to complete this operation
150x0000000FThe system cannot find the drive specified
160x00000010The directory cannot be removed
170x00000011The system cannot move the file to a different disk drive
180x00000012There are no more files
190x00000013The media is write protected
200x00000014The system cannot find the device specified
210x00000015The device is not ready
220x00000016The device does not recognize the command
230x00000017Data error (cyclic redundancy check)
240x00000018The program issued a command but the command length is incorrect
250x00000019The drive cannot locate a specific area or track on the disk
260x0000001AThe specified disk or diskette cannot be accessed
270x0000001BThe drive cannot find the sector requested
280x0000001CThe printer is out of paper
290x0000001DThe system cannot write to the specified device
300x0000001EThe system cannot read from the specified device
310x0000001FA device attached to the system is not functioning
320x00000020The process cannot access the file because it is being used by another process
330x00000021The process cannot access the file because another process has locked a portion of the file
340x00000022The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1
360x00000024Too many files opened for sharing
380x00000026Reached the end of the file
390x00000027The disk is full
500x00000032The request is not supported
510x00000033Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator
520x00000034You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name
530x00000035The network path was not found
540x00000036The network is busy
550x00000037The specified network resource or device is no longer available
560x00000038The network BIOS command limit has been reached
570x00000039A network adapter hardware error occurred
580x0000003AThe specified server cannot perform the requested operation
590x0000003BAn unexpected network error occurred
600x0000003CThe remote adapter is not compatible
610x0000003DThe printer queue is full
620x0000003ESpace to store the file waiting to be printed is not available on the server
630x0000003FYour file waiting to be printed was deleted
640x00000040The specified network name is no longer available
650x00000041Network access is denied
660x00000042The network resource type is not correct
670x00000043The network name cannot be found
680x00000044The name limit for the local computer network adapter card was exceeded
690x00000045The network BIOS session limit was exceeded
700x00000046The remote server has been paused or is in the process of being started
710x00000047No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept
720x00000048The specified printer or disk device has been paused
800x00000050The file exists
820x00000052The directory or file cannot be created
830x00000053Fail on INT 24
840x00000054Storage to process this request is not available
850x00000055The local device name is already in use
860x00000056The specified network password is not correct
870x00000057The parameter is incorrect
880x00000058A write fault occurred on the network
890x00000059The system cannot start another process at this time
1000x00000064Cannot create another system semaphore
1010x00000065The exclusive semaphore is owned by another process
1020x00000066The semaphore is set and cannot be closed
1030x00000067The semaphore cannot be set again
1040x00000068Cannot request exclusive semaphores at interrupt time
1050x00000069The previous ownership of this semaphore has ended
1060x0000006AInsert the diskette for drive %1
1070x0000006BThe program stopped because an alternate diskette was not inserted
1080x0000006CThe disk is in use or locked by another process
1090x0000006DThe pipe has been ended
1100x0000006EThe system cannot open the device or file specified
1110x0000006FThe file name is too long
1120x00000070There is not enough space on the disk
1130x00000071No more internal file identifiers available
1140x00000072The target internal file identifier is incorrect
1170x00000075The IOCTL call made by the application program is not correct
1180x00000076The verify-on-write switch parameter value is not correct
1190x00000077The system does not support the command requested
1200x00000078This function is not supported on this system
1210x00000079The semaphore timeout period has expired
1220x0000007AThe data area passed to a system call is too small
1230x0000007BThe filename, directory name, or volume label syntax is incorrect
1240x0000007CThe system call level is not correct
1250x0000007DThe disk has no volume label
1260x0000007EThe specified module could not be found
1270x0000007FThe specified procedure could not be found
1280x00000080There are no child processes to wait for
1290x00000081The %1 application cannot be run in Win32 mode
1300x00000082Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O
1310x00000083An attempt was made to move the file pointer before the beginning of the file
1320x00000084The file pointer cannot be set on the specified device or file
1330x00000085A JOIN or SUBST command cannot be used for a drive that contains previously joined drives
1340x00000086An attempt was made to use a JOIN or SUBST command on a drive that has already been joined
1350x00000087An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted
1360x00000088The system tried to delete the JOIN of a drive that is not joined
1370x00000089The system tried to delete the substitution of a drive that is not substituted
1380x0000008AThe system tried to join a drive to a directory on a joined drive
1390x0000008BThe system tried to substitute a drive to a directory on a substituted drive
1400x0000008CThe system tried to join a drive to a directory on a substituted drive
1410x0000008DThe system tried to SUBST a drive to a directory on a joined drive
1420x0000008EThe system cannot perform a JOIN or SUBST at this time
1430x0000008FThe system cannot join or substitute a drive to or for a directory on the same drive
1440x00000090The directory is not a subdirectory of the root directory
1450x00000091The directory is not empty
1460x00000092The path specified is being used in a substitute
1470x00000093Not enough resources are available to process this command
1480x00000094The path specified cannot be used at this time
1490x00000095An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute
1500x00000096System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed
1510x00000097The number of specified semaphore events for DosMuxSemWait is not correct
1520x00000098DosMuxSemWait did not execute; too many semaphores are already set
1530x00000099The DosMuxSemWait list is not correct
1540x0000009AThe volume label you entered exceeds the label character limit of the target file system
1550x0000009BCannot create another thread
1560x0000009CThe recipient process has refused the signal
1570x0000009DThe segment is already discarded and cannot be locked
1580x0000009EThe segment is already unlocked
1590x0000009FThe address for the thread ID is not correct
1600x000000A0One or more arguments are not correct
1610x000000A1The specified path is invalid
1620x000000A2A signal is already pending
1640x000000A4No more threads can be created in the system
1670x000000A7Unable to lock a region of a file
1700x000000AAThe requested resource is in use
1710x000000ABDevice's command support detection is in progress
1730x000000ADA lock request was not outstanding for the supplied cancel region
1740x000000AEThe file system does not support atomic changes to the lock type
1800x000000B4The system detected a segment number that was not correct
1820x000000B6The operating system cannot run %1
1830x000000B7Cannot create a file when that file already exists
1860x000000BAThe flag passed is not correct
1870x000000BBThe specified system semaphore name was not found
1880x000000BCThe operating system cannot run %1
1890x000000BDThe operating system cannot run %1
1900x000000BEThe operating system cannot run %1
1910x000000BFCannot run %1 in Win32 mode
1920x000000C0The operating system cannot run %1
1930x000000C1%1 is not a valid Win32 application
1940x000000C2The operating system cannot run %1
1950x000000C3The operating system cannot run %1
1960x000000C4The operating system cannot run this application program
1970x000000C5The operating system is not presently configured to run this application
1980x000000C6The operating system cannot run %1
1990x000000C7The operating system cannot run this application program
2000x000000C8The code segment cannot be greater than or equal to 64K
2010x000000C9The operating system cannot run %1
2020x000000CAThe operating system cannot run %1
2030x000000CBThe system could not find the environment option that was entered
2050x000000CDNo process in the command subtree has a signal handler
2060x000000CEThe filename or extension is too long
2070x000000CFThe ring 2 stack is in use
2080x000000D0The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified
2090x000000D1The signal being posted is not correct
2100x000000D2The signal handler cannot be set
2120x000000D4The segment is locked and cannot be reallocated
2140x000000D6Too many dynamic-link modules are attached to this program or dynamic-link module
2150x000000D7Cannot nest calls to LoadModule
2160x000000D8This 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
2170x000000D9The image file %1 is signed, unable to modify
2180x000000DAThe image file %1 is strong signed, unable to modify
2200x000000DCThis file is checked out or locked for editing by another user
2210x000000DDThe file must be checked out before saving changes
2220x000000DEThe file type being saved or retrieved has been blocked
2230x000000DFThe file size exceeds the limit allowed and cannot be saved
2240x000000E0Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically
2250x000000E1Operation did not complete successfully because the file contains a virus or potentially unwanted software
2260x000000E2This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location
2290x000000E5The pipe is local
2300x000000E6The pipe state is invalid
2310x000000E7All pipe instances are busy
2320x000000E8The pipe is being closed
2330x000000E9No process is on the other end of the pipe
2340x000000EAMore data is available
2400x000000F0The session was canceled
2540x000000FEThe specified extended attribute name was invalid
2550x000000FFThe extended attributes are inconsistent
2580x00000102The wait operation timed out
2590x00000103No more data is available
2660x0000010AThe copy functions cannot be used
2670x0000010BThe directory name is invalid
2750x00000113The extended attributes did not fit in the buffer
2760x00000114The extended attribute file on the mounted file system is corrupt
2770x00000115The extended attribute table file is full
2780x00000116The specified extended attribute handle is invalid
2820x0000011AThe mounted file system does not support extended attributes
2880x00000120Attempt to release mutex not owned by caller
2980x0000012AToo many posts were made to a semaphore
2990x0000012BOnly part of a ReadProcessMemory or WriteProcessMemory request was completed
3000x0000012CThe oplock request is denied
3010x0000012DAn invalid oplock acknowledgment was received by the system
3020x0000012EThe volume is too fragmented to complete this operation
3030x0000012FThe file cannot be opened because it is in the process of being deleted
3040x00000130Short name settings may not be changed on this volume due to the global registry setting
3050x00000131Short names are not enabled on this volume
3060x00000132The security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume
3070x00000133A requested file lock operation cannot be processed due to an invalid byte range
3080x00000134The subsystem needed to support the image type is not present
3090x00000135The specified file already has a notification GUID associated with it
3100x00000136An invalid exception handler routine has been detected
3110x00000137Duplicate privileges were specified for the token
3120x00000138No ranges for the specified operation were able to be processed
3130x00000139Operation is not allowed on a file system internal file
3140x0000013AThe physical resources of this disk have been exhausted
3150x0000013BThe token representing the data is invalid
3160x0000013CThe device does not support the command feature
3170x0000013DThe system cannot find message text for message number 0x%1 in the message file for %2
3180x0000013EThe scope specified was not found
3190x0000013FThe Central Access Policy specified is not defined on the target machine
3200x00000140The Central Access Policy obtained from Active Directory is invalid
3210x00000141The device is unreachable
3220x00000142The target device has insufficient resources to complete the operation
3230x00000143A data integrity checksum error occurred. Data in the file stream is corrupt
3240x00000144An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation
3260x00000146Device does not support file-level TRIM
3270x00000147The command specified a data offset that does not align to the device's granularity/alignment
3280x00000148The command specified an invalid field in its parameter list
3290x00000149An operation is currently in progress with the device
3300x0000014AAn attempt was made to send down the command via an invalid path to the target device
3310x0000014BThe command specified a number of descriptors that exceeded the maximum supported by the device
3320x0000014CScrub is disabled on the specified file
3330x0000014DThe storage device does not provide redundancy
3340x0000014EAn operation is not supported on a resident file
3350x0000014FAn operation is not supported on a compressed file
3360x00000150An operation is not supported on a directory
3370x00000151The specified copy of the requested data could not be read
3380x00000152The specified data could not be written to any of the copies
3390x00000153One 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
3400x00000154The supplied kernel information version is invalid
3410x00000155The supplied PEP information version is invalid
3420x00000156This object is not externally backed by any provider
3430x00000157The external backing provider is not recognized
3440x00000158Compressing this object would not save space
3450x00000159The request failed due to a storage topology ID mismatch
3460x0000015AThe operation was blocked by parental controls
3470x0000015BA file system block being referenced has already reached the maximum reference count and can't be referenced any further
3500x0000015ENo action was taken as a system reboot is required
3510x0000015FThe shutdown operation failed
3520x00000160The restart operation failed
3530x00000161The maximum number of sessions has been reached
4000x00000190The thread is already in background processing mode
4010x00000191The thread is not in background processing mode
4020x00000192The process is already in background processing mode
4030x00000193The process is not in background processing mode
4830x000001E3The request failed due to a fatal device hardware error
4870x000001E7Attempt to access invalid address
5000x000001F4User profile cannot be loaded
5340x00000216Arithmetic result exceeded 32 bits
5350x00000217There is a process on other end of the pipe
5360x00000218Waiting for a process to open the other end of the pipe
5370x00000219Application verifier has found an error in the current process
5380x0000021AAn error occurred in the ABIOS subsystem
5390x0000021BA warning occurred in the WX86 subsystem
5400x0000021CAn error occurred in the WX86 subsystem
5410x0000021DAn 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
5420x0000021EUnwind exception code
5430x0000021FAn invalid or unaligned stack was encountered during an unwind operation
5440x00000220An invalid unwind target was encountered during an unwind operation
5450x00000221Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort
5460x00000222Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port
5470x00000223An attempt was made to lower a quota limit below the current usage
5480x00000224An attempt was made to attach to a device that was already attached to another device
5490x00000225An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references
5500x00000226Profiling not started
5510x00000227Profiling not stopped
5520x00000228The passed ACL did not contain the minimum required information
5530x00000229The number of active profiling objects is at the maximum and no more may be started
5540x0000022AUsed to indicate that an operation cannot continue without blocking for I/O
5550x0000022BIndicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process
5560x0000022CIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
5570x0000022DIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
5580x0000022EIf an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception
5590x0000022FA malformed function table was encountered during an unwind operation
5600x00000230Indicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system. This causes the protection attempt to fail, which may cause a file creation attempt to fail
5610x00000231Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors
5630x00000233Indicates that the starting value for the LDT information was not an integral multiple of the selector size
5640x00000234Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors
5650x00000235Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads
5660x00000236An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified
5670x00000237Page file quota was exceeded
5680x00000238The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role
5690x00000239The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required
5700x0000023AThe NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines
5710x0000023B{Privilege Failed} The I/O permissions for the process could not be changed
5720x0000023C{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C
5730x0000023D{Missing System File} The required system file %hs is bad or missing
5740x0000023E{Application Error} The exception %s (0x
5750x0000023F{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application
5760x00000240{Unable to Create Paging File} The creation of the paging file %hs failed (%lx). The requested size was %ld
5770x00000241Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source
5780x00000242{No Paging File Specified} No paging file was specified in the system configuration
5790x00000243{EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present
5800x00000244An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread
5810x00000245A Windows Server has an incorrect configuration
5820x00000246An 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
5830x00000247The Unicode character is not defined in the Unicode character set installed on the system
5840x00000248The paging file cannot be created on a floppy diskette
5850x00000249The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected
5860x0000024AThis operation is only allowed for the Primary Domain Controller of the domain
5870x0000024BAn attempt was made to acquire a mutant such that its maximum count would have been exceeded
5880x0000024CA volume has been accessed for which a file system driver is required that has not yet been loaded
5890x0000024D{Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable
5900x0000024E{Unexpected Failure in DebugActiveProcess} An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error
5910x0000024F{Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x
5920x00000250{Data Not Accepted} The TDI client could not handle the data received during an indication
5930x00000251NTVDM encountered a hard error
5940x00000252{Cancel Timeout} The driver %hs failed to complete a cancelled I/O request in the allotted time
5950x00000253{Reply Message Mismatch} An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message
5960x00000254{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
5970x00000255The 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
5980x00000256The stream is not a tiny stream
5990x00000257The request must be handled by the stack overflow code
6000x00000258Internal 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
6010x00000259The 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
6020x0000025AThe bucket array must be grown. Retry transaction after doing so
6030x0000025BThe user/kernel marshalling buffer has overflowed
6040x0000025CThe supplied variant structure contains invalid data
6050x0000025DThe specified buffer contains ill-formed data
6060x0000025E{Audit Failed} An attempt to generate a security audit failed
6070x0000025FThe timer resolution was not previously set by the current process
6080x00000260There is insufficient account information to log you on
6090x00000261{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
6100x00000262{Invalid Service Callback Entrypoint} The %hs service is not written correctly. The stack pointer has been left in an inconsistent state. The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly
6110x00000263There is an IP address conflict with another system on the network
6120x00000264There is an IP address conflict with another system on the network
6130x00000265{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
6140x00000266A callback return system service cannot be executed when no callback is active
6150x00000267The password provided is too short to meet the policy of your user account. Please choose a longer password
6160x00000268The policy of your user account does not allow you to change passwords too frequently. This is done to prevent users from changing back to a familiar, but potentially discovered, password. If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned
6170x00000269You 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
6180x0000026AThe specified compression format is unsupported
6190x0000026BThe specified hardware profile configuration is invalid
6200x0000026CThe specified Plug and Play registry device path is invalid
6210x0000026DThe specified quota list is internally inconsistent with its descriptor
6220x0000026E{Windows Evaluation Notification} The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product
6230x0000026F{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
6240x00000270{DLL Initialization Failed} The application failed to initialize because the window station is shutting down
6250x00000271The validation process needs to continue on to the next step
6260x00000272There are no more matches for the current index enumeration
6270x00000273The range could not be added to the range list because of a conflict
6280x00000274The server process is running under a SID different than that required by client
6290x00000275A group marked use for deny only cannot be enabled
6300x00000276{EXCEPTION} Multiple floating point faults
6310x00000277{EXCEPTION} Multiple floating point traps
6320x00000278The requested interface is not supported
6330x00000279{System Standby Failed} The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode
6340x0000027AThe system file %1 has become corrupt and has been replaced
6350x0000027B{Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help
6360x0000027CA device was removed so enumeration must be restarted
6370x0000027D{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
6380x0000027EDevice will not start without a reboot
6390x0000027FThere is not enough power to complete the requested operation
6400x00000280ERROR_MULTIPLE_FAULT_VIOLATION
6410x00000281The system is in the process of shutting down
6420x00000282An attempt to remove a processes DebugPort was made, but a port was not already associated with the process
6430x00000283This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller
6440x00000284The specified range could not be found in the range list
6460x00000286The driver was not loaded because the system is booting into safe mode
6470x00000287The driver was not loaded because it failed its initialization call
6480x00000288The %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""
6490x00000289The 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
6500x0000028AThe device object parameter is either not a valid device object or is not attached to the volume specified by the file name
6510x0000028BA Machine Check Error has occurred. Please check the system eventlog for additional information
6520x0000028CThere was error [%2] processing the driver database
6530x0000028DSystem hive size has exceeded its limit
6540x0000028EThe driver could not be loaded because a previous version of the driver is still in memory
6550x0000028F{Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation
6560x00000290The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted
6570x00000291The password provided is too long to meet the policy of your user account. Please choose a shorter password
6650x00000299The requested operation could not be completed due to a file system limitation
6680x0000029CAn assertion failure has occurred
6690x0000029DAn error occurred in the ACPI subsystem
6700x0000029EWOW Assertion Error
6710x0000029FA device is missing in the system BIOS MPS table. This device will not be used. Please contact your system vendor for system BIOS update
6720x000002A0A translator failed to translate resources
6730x000002A1A IRQ translator failed to translate resources
6740x000002A2Driver %2 returned invalid ID for a child device (%3)
6750x000002A3{Kernel Debugger Awakened} the system debugger was awakened by an interrupt
6760x000002A4{Handles Closed} Handles to objects have been automatically closed as a result of the requested operation
6770x000002A5{Too Much Information} The specified access control list (ACL) contained more information than was expected
6780x000002A6This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired)
6790x000002A7{Media Changed} The media may have changed
6800x000002A8{GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended
6810x000002A9The create operation stopped after reaching a symbolic link
6820x000002AAA long jump has been executed
6830x000002ABThe Plug and Play query operation was not successful
6840x000002ACA frame consolidation has been executed
6850x000002AD{Registry Hive Recovered} Registry hive (file): %hs was corrupted and it has been recovered. Some data might have been lost
6860x000002AEThe application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs?
6870x000002AFThe application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs?
6880x000002B0Debugger did not handle the exception
6890x000002B1Debugger will reply later
6900x000002B2Debugger cannot provide handle
6910x000002B3Debugger terminated thread
6920x000002B4Debugger terminated process
6930x000002B5Debugger got control C
6940x000002B6Debugger printed exception on control C
6950x000002B7Debugger received RIP exception
6960x000002B8Debugger received control break
6970x000002B9Debugger command communication exception
6980x000002BA{Object Exists} An attempt was made to create an object and the object name already existed
6990x000002BB{Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded
7000x000002BC{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
7010x000002BDThis informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created
7020x000002BE{Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments
7030x000002BF{Invalid Current Directory} The process cannot switch to the startup current directory %hs. Select OK to set current directory to %hs, or select CANCEL to exit
7040x000002C0{Redundant Read} To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device
7050x000002C1{Redundant Write} To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device
7060x000002C2{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load
7070x000002C3{Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later
7080x000002C4{Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system
7090x000002C5{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
7100x000002C6{TDI Event Done} The TDI indication has completed successfully
7110x000002C7{TDI Event Pending} The TDI indication has entered the pending state
7120x000002C8Checking file system on %wZ
7130x000002C9{Fatal Application Exit} %hs
7140x000002CAThe specified registry key is referenced by a predefined handle
7150x000002CB{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
7160x000002CC%hs
7170x000002CD{Page Locked} One of the pages to lock was already locked
7180x000002CEApplication popup: %1 : %2
7190x000002CFERROR_ALREADY_WIN32
7200x000002D0{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine
7210x000002D1A yield execution was performed and no thread was available to run
7220x000002D2The resumable flag to a timer API was ignored
7230x000002D3The arbiter has deferred arbitration of these resources to its parent
7240x000002D4The inserted CardBus device cannot be started because of a configuration error on %hs""""
7250x000002D5The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported
7260x000002D6The system was put into hibernation
7270x000002D7The system was resumed from hibernation
7280x000002D8Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]
7290x000002D9A 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
7300x000002DAThe system has awoken
7310x000002DBERROR_WAIT_1
7320x000002DCERROR_WAIT_2
7330x000002DDERROR_WAIT_3
7340x000002DEERROR_WAIT_63
7350x000002DFERROR_ABANDONED_WAIT_0
7360x000002E0ERROR_ABANDONED_WAIT_63
7370x000002E1ERROR_USER_APC
7380x000002E2ERROR_KERNEL_APC
7390x000002E3ERROR_ALERTED
7400x000002E4The requested operation requires elevation
7410x000002E5A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
7420x000002E6An open/create operation completed while an oplock break is underway
7430x000002E7A new volume has been mounted by a file system
7440x000002E8This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed
7450x000002E9This indicates that a notify change request has been completed due to closing the handle which made the notify change request
7460x000002EA{Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport
7470x000002EBPage fault was a transition fault
7480x000002ECPage fault was a demand zero fault
7490x000002EDPage fault was a demand zero fault
7500x000002EEPage fault was a demand zero fault
7510x000002EFPage fault was satisfied by reading from a secondary storage device
7520x000002F0Cached page was locked during operation
7530x000002F1Crash dump exists in paging file
7540x000002F2Specified buffer contains all zeros
7550x000002F3A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link
7560x000002F4The device has succeeded a query-stop and its resource requirements have changed
7570x000002F5The translator has translated these resources into the global space and no further translations should be performed
7580x000002F6A process being terminated has no threads to terminate
7590x000002F7The specified process is not part of a job
7600x000002F8The specified process is part of a job
7610x000002F9{Volume Shadow Copy Service} The system is now ready for hibernation
7620x000002FAA file system or file system filter driver has successfully completed an FsFilter operation
7630x000002FBThe specified interrupt vector was already connected
7640x000002FCThe specified interrupt vector is still connected
7650x000002FDAn operation is blocked waiting for an oplock
7660x000002FEDebugger handled exception
7670x000002FFDebugger continued
7680x00000300An exception occurred in a user mode callback and the kernel callback frame should be removed
7690x00000301Compression is disabled for this volume
7700x00000302The data provider cannot fetch backwards through a result set
7710x00000303The data provider cannot scroll backwards through a result set
7720x00000304The data provider requires that previously fetched data is released before asking for more data
7730x00000305The data provider was not able to interpret the flags set for a column binding in an accessor
7740x00000306One or more errors occurred while processing the request
7750x00000307The implementation is not capable of performing the request
7760x00000308The client of a component requested an operation which is not valid given the state of the component instance
7770x00000309A version number could not be parsed
7780x0000030AThe iterator's start position is invalid
7790x0000030BThe hardware has reported an uncorrectable memory error
7800x0000030CThe attempted operation required self healing to be enabled
7810x0000030DThe Desktop heap encountered an error while allocating session memory. There is more information in the system event log
7820x0000030EThe system power state is transitioning from %2 to %3
7830x0000030FThe system power state is transitioning from %2 to %3 but could enter %4
7840x00000310A thread is getting dispatched with MCA EXCEPTION because of MCA
7850x00000311Access to %1 is monitored by policy rule %2
7860x00000312Access to %1 has been restricted by your Administrator by policy rule %2
7870x00000313A valid hibernation file has been invalidated and should be abandoned
7880x00000314{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
7890x00000315{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
7900x00000316{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
7910x00000317The resources required for this device conflict with the MCFG table
7920x00000318The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired
7930x00000319The volume repair was not successful
7940x0000031AOne of the volume corruption logs is full. Further corruptions that may be detected won't be logged
7950x0000031BOne of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned
7960x0000031COne of the volume corruption logs is unavailable for being operated on
7970x0000031DOne of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned
7980x0000031EOne of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions
7990x0000031FOrphaned 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
8000x00000320The oplock that was associated with this handle is now associated with a different handle
8010x00000321An oplock of the requested level cannot be granted. An oplock of a lower level may be available
8020x00000322The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken
8030x00000323The handle with which this oplock was associated has been closed. The oplock is now broken
8040x00000324The specified access control entry (ACE) does not contain a condition
8050x00000325The specified access control entry (ACE) contains an invalid condition
8060x00000326Access to the specified file handle has been revoked
8070x00000327{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
8080x00000328The read or write operation to an encrypted file could not be completed because the file has not been opened for data access
8090x00000329File metadata optimization is already in progress
8100x0000032AThe requested operation failed due to quota operation is still in progress
8110x0000032BAccess to the specified handle has been revoked
8120x0000032CThe callback function must be invoked inline
8130x0000032DThe specified CPU Set IDs are invalid
9940x000003E2Access to the extended attribute was denied
9950x000003E3The I/O operation has been aborted because of either a thread exit or an application request
9960x000003E4Overlapped I/O event is not in a signaled state
9970x000003E5Overlapped I/O operation is in progress
9980x000003E6Invalid access to memory location
9990x000003E7Error performing inpage operation
10010x000003E9Recursion too deep; the stack overflowed
10020x000003EAThe window cannot act on the sent message
10030x000003EBCannot complete this function
10040x000003ECInvalid flags
10050x000003EDThe 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
10060x000003EEThe volume for a file has been externally altered so that the opened file is no longer valid
10070x000003EFThe requested operation cannot be performed in full-screen mode
10080x000003F0An attempt was made to reference a token that does not exist
10090x000003F1The configuration registry database is corrupt
10100x000003F2The configuration registry key is invalid
10110x000003F3The configuration registry key could not be opened
10120x000003F4The configuration registry key could not be read
10130x000003F5The configuration registry key could not be written
10140x000003F6One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful
10150x000003F7The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted
10160x000003F8An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry
10170x000003F9The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format
10180x000003FAIllegal operation attempted on a registry key that has been marked for deletion
10190x000003FBSystem could not allocate the required space in a registry log
10200x000003FCCannot create a symbolic link in a registry key that already has subkeys or values
10210x000003FDCannot create a stable subkey under a volatile parent key
10220x000003FEA 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
10510x0000041BA stop control has been sent to a service that other running services are dependent on
10520x0000041CThe requested control is not valid for this service
10530x0000041DThe service did not respond to the start or control request in a timely fashion
10540x0000041EA thread could not be created for the service
10550x0000041FThe service database is locked
10560x00000420An instance of the service is already running
10570x00000421The account name is invalid or does not exist, or the password is invalid for the account name specified
10580x00000422The service cannot be started, either because it is disabled or because it has no enabled devices associated with it
10590x00000423Circular service dependency was specified
10600x00000424The specified service does not exist as an installed service
10610x00000425The service cannot accept control messages at this time
10620x00000426The service has not been started
10630x00000427The service process could not connect to the service controller
10640x00000428An exception occurred in the service when handling the control request
10650x00000429The database specified does not exist
10660x0000042AThe service has returned a service-specific error code
10670x0000042BThe process terminated unexpectedly
10680x0000042CThe dependency service or group failed to start
10690x0000042DThe service did not start due to a logon failure
10700x0000042EAfter starting, the service hung in a start-pending state
10710x0000042FThe specified service database lock is invalid
10720x00000430The specified service has been marked for deletion
10730x00000431The specified service already exists
10740x00000432The system is currently running with the last-known-good configuration
10750x00000433The dependency service does not exist or has been marked for deletion
10760x00000434The current boot has already been accepted for use as the last-known-good control set
10770x00000435No attempts to start the service have been made since the last boot
10780x00000436The name is already in use as either a service name or a service display name
10790x00000437The account specified for this service is different from the account specified for other services running in the same process
10800x00000438Failure actions can only be set for Win32 services, not for drivers
10810x00000439This service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service's process terminates unexpectedly
10820x0000043ANo recovery program has been configured for this service
10830x0000043BThe executable program that this service is configured to run in does not implement the service
10840x0000043CThis service cannot be started in Safe Mode
11000x0000044CThe physical end of the tape has been reached
11010x0000044DA tape access reached a filemark
11020x0000044EThe beginning of the tape or a partition was encountered
11030x0000044FA tape access reached the end of a set of files
11040x00000450No more data is on the tape
11050x00000451Tape could not be partitioned
11060x00000452When accessing a new tape of a multivolume partition, the current block size is incorrect
11070x00000453Tape partition information could not be found when loading a tape
11080x00000454Unable to lock the media eject mechanism
11090x00000455Unable to unload the media
11100x00000456The media in the drive may have changed
11110x00000457The I/O bus was reset
11120x00000458No media in drive
11130x00000459No mapping for the Unicode character exists in the target multi-byte code page
11140x0000045AA dynamic link library (DLL) initialization routine failed
11150x0000045BA system shutdown is in progress
11160x0000045CUnable to abort the system shutdown because no shutdown was in progress
11170x0000045DThe request could not be performed because of an I/O device error
11180x0000045ENo serial device was successfully initialized. The serial driver will unload
11190x0000045FUnable 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
11200x00000460A serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.)
11210x00000461A serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.)
11220x00000462No ID address mark was found on the floppy disk
11230x00000463Mismatch between the floppy disk sector ID field and the floppy disk controller track address
11240x00000464The floppy disk controller reported an error that is not recognized by the floppy disk driver
11250x00000465The floppy disk controller returned inconsistent results in its registers
11260x00000466While accessing the hard disk, a recalibrate operation failed, even after retries
11270x00000467While accessing the hard disk, a disk operation failed even after retries
11280x00000468While accessing the hard disk, a disk controller reset was needed, but even that failed
11290x00000469Physical end of tape encountered
11300x0000046ANot enough server storage is available to process this command
11310x0000046BA potential deadlock condition has been detected
11320x0000046CThe base address or the file offset specified does not have the proper alignment
11400x00000474An attempt to change the system power state was vetoed by another application or driver
11410x00000475The system BIOS failed an attempt to change the system power state
11420x00000476An attempt was made to create more links on a file than the file system supports
11500x0000047EThe specified program requires a newer version of Windows
11510x0000047FThe specified program is not a Windows or MS-DOS program
11520x00000480Cannot start more than one instance of the specified program
11530x00000481The specified program was written for an earlier version of Windows
11540x00000482One of the library files needed to run this application is damaged
11550x00000483No application is associated with the specified file for this operation
11560x00000484An error occurred in sending the command to the application
11570x00000485One of the library files needed to run this application cannot be found
11580x00000486The current process has used all of its system allowance of handles for Window Manager objects
11590x00000487The message can be used only with synchronous operations
11600x00000488The indicated source element has no media
11610x00000489The indicated destination element already contains media
11620x0000048AThe indicated element does not exist
11630x0000048BThe indicated element is part of a magazine that is not present
11640x0000048CThe indicated device requires reinitialization due to hardware errors
11650x0000048DThe device has indicated that cleaning is required before further operations are attempted
11660x0000048EThe device has indicated that its door is open
11670x0000048FThe device is not connected
11680x00000490Element not found
11690x00000491There was no match for the specified key in the index
11700x00000492The property set specified does not exist on the object
11710x00000493The point passed to GetMouseMovePoints is not in the buffer
11720x00000494The tracking (workstation) service is not running
11730x00000495The Volume ID could not be found
11750x00000497Unable to remove the file to be replaced
11760x00000498Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name
11770x00000499Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name
11780x0000049AThe volume change journal is being deleted
11790x0000049BThe volume change journal is not active
11800x0000049CA file was found, but it may not be the correct file
11810x0000049DThe journal entry has been deleted from the journal
11900x000004A6A system shutdown has already been scheduled
11910x000004A7The system shutdown cannot be initiated because there are other users logged on to the computer
12000x000004B0The specified device name is invalid
12010x000004B1The device is not currently connected but it is a remembered connection
12020x000004B2The local device name has a remembered connection to another network resource
12030x000004B3The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator
12040x000004B4The specified network provider name is invalid
12050x000004B5Unable to open the network connection profile
12060x000004B6The network connection profile is corrupted
12070x000004B7Cannot enumerate a noncontainer
12080x000004B8An extended error has occurred
12090x000004B9The format of the specified group name is invalid
12100x000004BAThe format of the specified computer name is invalid
12110x000004BBThe format of the specified event name is invalid
12120x000004BCThe format of the specified domain name is invalid
12130x000004BDThe format of the specified service name is invalid
12140x000004BEThe format of the specified network name is invalid
12150x000004BFThe format of the specified share name is invalid
12160x000004C0The format of the specified password is invalid
12170x000004C1The format of the specified message name is invalid
12180x000004C2The format of the specified message destination is invalid
12190x000004C3Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again
12200x000004C4An attempt was made to establish a session to a network server, but there are already too many sessions established to that server
12210x000004C5The workgroup or domain name is already in use by another computer on the network
12220x000004C6The network is not present or not started
12230x000004C7The operation was canceled by the user
12240x000004C8The requested operation cannot be performed on a file with a user-mapped section open
12250x000004C9The remote computer refused the network connection
12260x000004CAThe network connection was gracefully closed
12270x000004CBThe network transport endpoint already has an address associated with it
12280x000004CCAn address has not yet been associated with the network endpoint
12290x000004CDAn operation was attempted on a nonexistent network connection
12300x000004CEAn invalid operation was attempted on an active network connection
12310x000004CFThe network location cannot be reached. For information about network troubleshooting, see Windows Help
12320x000004D0The network location cannot be reached. For information about network troubleshooting, see Windows Help
12330x000004D1The network location cannot be reached. For information about network troubleshooting, see Windows Help
12340x000004D2No service is operating at the destination network endpoint on the remote system
12350x000004D3The request was aborted
12360x000004D4The network connection was aborted by the local system
12370x000004D5The operation could not be completed. A retry should be performed
12380x000004D6A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached
12390x000004D7Attempting to log in during an unauthorized time of day for this account
12400x000004D8The account is not authorized to log in from this station
12410x000004D9The network address could not be used for the operation requested
12420x000004DAThe service is already registered
12430x000004DBThe specified service does not exist
12440x000004DCThe operation being requested was not performed because the user has not been authenticated
12450x000004DDThe operation being requested was not performed because the user has not logged on to the network. The specified service does not exist
12460x000004DEContinue with work in progress
12470x000004DFAn attempt was made to perform an initialization operation when initialization has already been completed
12480x000004E0No more local devices
12490x000004E1The specified site does not exist
12500x000004E2A domain controller with the specified name already exists
12510x000004E3This operation is supported only when you are connected to the server
12520x000004E4The group policy framework should call the extension even if there are no changes
12530x000004E5The specified user does not have a valid profile
12540x000004E6This operation is not supported on a computer running Windows Server 2003 for Small Business Server
12550x000004E7The server machine is shutting down
12560x000004E8The remote system is not available. For information about network troubleshooting, see Windows Help
12570x000004E9The security identifier provided is not from an account domain
12580x000004EAThe security identifier provided does not have a domain component
12590x000004EBAppHelp dialog canceled thus preventing the application from starting
12600x000004ECThis program is blocked by group policy. For more information, contact your system administrator
12610x000004EDA program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific
12620x000004EEThe share is currently offline or does not exist
12630x000004EFThe Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log
12640x000004F0The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem
12650x000004F1The system cannot contact a domain controller to service the authentication request. Please try again later
12710x000004F7The machine is locked and cannot be shut down without the force option
12730x000004F9An application-defined callback gave invalid data when called
12740x000004FAThe group policy framework should call the extension in the synchronous foreground policy refresh
12750x000004FBThis driver has been blocked from loading
12760x000004FCA dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image
12770x000004FDWindows cannot open this program since it has been disabled
12780x000004FEWindows cannot open this program because the license enforcement system has been tampered with or become corrupted
12790x000004FFA transaction recover failed
12800x00000500The current thread has already been converted to a fiber
12810x00000501The current thread has already been converted from a fiber
12820x00000502The 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
12830x00000503Data present in one of the parameters is more than the function can operate on
12840x00000504An attempt to do an operation on a debug object failed because the object is in the process of being deleted
12850x00000505An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed
12860x00000506%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator
12870x00000507Insufficient information exists to identify the cause of failure
12880x00000508The parameter passed to a C runtime function is incorrect
12890x00000509The operation occurred beyond the valid data length of the file
12900x0000050AThe service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service
12910x0000050BThe process hosting the driver for this device has been terminated
12920x0000050CAn operation attempted to exceed an implementation-defined limit
12930x0000050DEither the target process, or the target thread's containing process, is a protected process
12940x0000050EThe service notification client is lagging too far behind the current state of services in the machine
12950x0000050FThe requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator
12960x00000510The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator
12970x00000511A 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
12980x00000512A thread involved in this operation appears to be unresponsive
12990x00000513Indicates a particular Security ID may not be assigned as the label of an object
13000x00000514Not all privileges or groups referenced are assigned to the caller
13010x00000515Some mapping between account names and security IDs was not done
13020x00000516No system quota limits are specifically set for this account
13030x00000517No encryption key is available. A well-known encryption key was returned
13040x00000518The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string
13050x00000519The revision level is unknown
13060x0000051AIndicates two revision levels are incompatible
13070x0000051BThis security ID may not be assigned as the owner of this object
13080x0000051CThis security ID may not be assigned as the primary group of an object
13090x0000051DAn attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client
13100x0000051EThe group may not be disabled
13110x0000051FThere are currently no logon servers available to service the logon request
13120x00000520A specified logon session does not exist. It may already have been terminated
13130x00000521A specified privilege does not exist
13140x00000522A required privilege is not held by the client
13150x00000523The name provided is not a properly formed account name
13160x00000524The specified account already exists
13170x00000525The specified account does not exist
13180x00000526The specified group already exists
13190x00000527The specified group does not exist
13200x00000528Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member
13210x00000529The specified user account is not a member of the specified group account
13220x0000052AThis operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon
13230x0000052BUnable to update the password. The value provided as the current password is incorrect
13240x0000052CUnable to update the password. The value provided for the new password contains values that are not allowed in passwords
13250x0000052DUnable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain
13260x0000052EThe user name or password is incorrect
13270x0000052FAccount restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced
13280x00000530Your account has time restrictions that keep you from signing in right now
13290x00000531This user isn't allowed to sign in to this computer
13300x00000532The password for this account has expired
13310x00000533This user can't sign in because this account is currently disabled
13320x00000534No mapping between account names and security IDs was done
13330x00000535Too many local user identifiers (LUIDs) were requested at one time
13340x00000536No more local user identifiers (LUIDs) are available
13350x00000537The subauthority part of a security ID is invalid for this particular use
13360x00000538The access control list (ACL) structure is invalid
13370x00000539The security ID structure is invalid
13380x0000053AThe security descriptor structure is invalid
13400x0000053CThe inherited access control list (ACL) or access control entry (ACE) could not be built
13410x0000053DThe server is currently disabled
13420x0000053EThe server is currently enabled
13430x0000053FThe value provided was an invalid value for an identifier authority
13440x00000540No more memory is available for security information updates
13450x00000541The specified attributes are invalid, or incompatible with the attributes for the group as a whole
13460x00000542Either a required impersonation level was not provided, or the provided impersonation level is invalid
13470x00000543Cannot open an anonymous level security token
13480x00000544The validation information class requested was invalid
13490x00000545The type of the token is inappropriate for its attempted use
13500x00000546Unable to perform a security operation on an object that has no associated security
13510x00000547Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied
13520x00000548The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation
13530x00000549The domain was in the wrong state to perform the security operation
13540x0000054AThis operation is only allowed for the Primary Domain Controller of the domain
13550x0000054BThe specified domain either does not exist or could not be contacted
13560x0000054CThe specified domain already exists
13570x0000054DAn attempt was made to exceed the limit on the number of domains per server
13580x0000054EUnable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk
13590x0000054FAn internal error occurred
13600x00000550Generic access types were contained in an access mask which should already be mapped to nongeneric types
13610x00000551A security descriptor is not in the right format (absolute or self-relative)
13620x00000552The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process
13630x00000553Cannot start a new logon session with an ID that is already in use
13640x00000554A specified authentication package is unknown
13650x00000555The logon session is not in a state that is consistent with the requested operation
13660x00000556The logon session ID is already in use
13670x00000557A logon request contained an invalid logon type value
13680x00000558Unable to impersonate using a named pipe until data has been read from that pipe
13690x00000559The transaction state of a registry subtree is incompatible with the requested operation
13700x0000055AAn internal security database corruption has been encountered
13710x0000055BCannot perform this operation on built-in accounts
13720x0000055CCannot perform this operation on this built-in special group
13730x0000055DCannot perform this operation on this built-in special user
13740x0000055EThe user cannot be removed from a group because the group is currently the user's primary group
13750x0000055FThe token is already in use as a primary token
13760x00000560The specified local group does not exist
13770x00000561The specified account name is not a member of the group
13780x00000562The specified account name is already a member of the group
13790x00000563The specified local group already exists
13800x00000564Logon failure: the user has not been granted the requested logon type at