MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!   P@, .rsrc@@ 0H E(@Xp     0H`x 8Ph !"#$%(&@'X(p)*+,-./001H2`3x456789: ;8<P=h>?@ABCD E( @ X  p                        0  @  P  `  p                        0  @  P  `  p                        0  @  P  `  p                        0  @  P  `  p               h ,"#h%.H&D'P)b*,H-f001f@3f4D67nh9V:p0<,>?ACEGIZLM QR@50930 (IBM EBCDIC - Japanese (Katakana) Extended and Japanese)+50931 (IBM EBCDIC - US/Canada and Japanese)/50933 (IBM EBCDIC - Korean Extended and Korean)'50935 (IBM EBCDIC - Simplified Chinese)650937 (IBM EBCDIC - US/Canada and Traditional Chinese);50939 (IBM EBCDIC - Japanese (Latin) Extended and Japanese)PA51932 (EUC-Japanese)51936 (EUC-Simplified Chinese)51949 (EUC-Korean)51950 (EUC-Traditional Chinese)$52936 (HZ-GB2312 Simplified Chinese)"54936 (GB18030 Simplified Chinese)57002 (ISCII - Devanagari)57003 (ISCII - Bengali)57004 (ISCII - Tamil)57005 (ISCII - Telugu)57006 (ISCII - Assamese)57007 (ISCII - Odia (Oriya))57008 (ISCII - Kannada)57009 (ISCII - Malayalam)57010 (ISCII - Gujarati)"57011 (ISCII - Punjabi (Gurmukhi))PA 65000 (UTF-7) 65001 (UTF-8) South SudanThe Republic of South SudanEnglish (Philippines)"Central Atlas Tamazight (Tifinagh)Quichua Chinese (Traditional, Macao SAR) Macao SARTsonga Shona (Latin)BurmeseGuaraniOromoSomaliSouthern Sotho (South Africa)Tsonga (South Africa)Shona (Latin, Zimbabwe)Javanese (Indonesia)Oromo (Ethiopia)Somali (Somalia) Urdu (India)Nepali (India)MalagasyFrench (Runion)RunionFrench (Congo [DRC]) Congo [DRC]French (Senegal)French (Cameroon)French (Ivory Coast) Ivory Coast French (Mali)French (Morocco)English (Hong Kong) Hong KongFrench (Haiti)Spanish (Latin America) Latin AmericaJavaneseStandard Morrocan TamazightN'ko N'ko (Guinea)Romanian (Moldova)Malagasy (Madagascar)Shona&Standard Morrocan Tamazight (Tifinagh)/Standard Morrocan Tamazight (Tifinagh, Morocco)Unknown LocaleUnknown LanguageUnknown RegionPortuguese (Angola)PA" $$&&'&,,T'2H'PP4RY4drt7u8=hTTUUVtW4X^ab0e kllm   nnp   q*DpqFW^aHp<13\P(T]_<oLltv~HHx8:<$>?Aw@hitv)(jTIJ@<=@<a b d d \  nnXhv<T&*04DJX[XT5pHs88ȁ,KYinqD{{L}~ dAQ  \ G ,m ~ < !G!!4)#2#58#:#8##9%"%xQO%d%R%%\%%d%%Df&&$mI&I&m{&|&`n&&o&&s''|x''y''py&'&'z('('<{3'W't{k'm'u''*+L22 5^6e6l667::6::9::Q:;U;;Y;;t];+;]`;g;c;;l;;m;;xo(<-<s<<dx< =,yT=Y=T==L====XLD00@@8prpdRT`4x%%x |P  0  \  ! ̹# # H\ \ Ȼ` ` dd d мf f   | #&#&8#&#&K#&L#&DQ#&Q#&0&0& ' 'X'Y'00l44<<<==cccc c ct`c`czzz z &@ &@"&@"&@/$&@/$&@`7$&@7$&@9$&@:$&@P@+@0@5@h=?@H((8)h),-'/@.0ňƈ0ψψl11JJ223 5@6607 !8PP8WW8pp8t9 9?@A  $B tBFdmMODQ@@pRPVR`aTdpT\l]]abj kq\rr"#hs23Tt5:xuAAx y$&)p00,  !1$xWW.///////\v//4//h @P$ D 5     h   " $ ) t0 C 0E I P [ |"] _ P2a c @4e e 5g g 46  7  > - H0 .0 Q1 1 b31 41 g2 2 g@ @ hH H zP P ` ` ` ` ` ` ` ` p p Ęp p ԝ       $  ܺhLԿT4er     X  #. 00 39 ;<(! >?! FQH" W]( ru- X/ 2 p7  8 : $; tF F ,1G 33H 0I  >5 >>|: > >DB *>+>B >>C @@I TTO TTxT T)TT U UW ccxa ccb cc,e c cxe ccdg cch cchj ccj cck cc|k cck ccl ccl ccl cc0m  c ctm c! cm 0 c0 c' was expected. Manifest Parse Error : A semi colon character was expected. hManifest Parse Error : Unbalanced parentheses. XManifest Parse Error : Internal error. Manifest Parse Error : Whitespace is not allowed at this location. Manifest Parse Error : End of file reached in invalid state for current encoding. `Manifest Parse Error : Missing parenthesis. Manifest Parse Error : A single or double closing quote character (\' or \") is missing. Manifest Parse Error : Multiple colons are not allowed in a name. Manifest Parse Error : Invalid character for decimal digit. Manifest Parse Error : Invalid character for hexadecimal digit. Manifest Parse Error : Invalid unicode character value for this platform. pManifest Parse Error : Expecting whitespace or '?'. Manifest Parse Error : End tag was not expected at this location. Manifest Parse Error : The following tags were not closed: %1. `Manifest Parse Error : Duplicate attribute. Manifest Parse Error : Only one top level element is allowed in an XML document. Manifest Parse Error : Invalid at the top level of the document. hManifest Parse Error : Invalid xml declaration. Manifest Parse Error : XML document must have a top level element. hManifest Parse Error : Unexpected end of file. Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset. hManifest Parse Error : Element was not closed. Manifest Parse Error : End element was missing the character '>'. xManifest Parse Error : A string literal was not closed. lManifest Parse Error : A comment was not closed. tManifest Parse Error : A declaration was not closed. xManifest Parse Error : A CDATA section was not closed. Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string "xml". Manifest Parse Error : System does not support the specified encoding. Manifest Parse Error : Switch from current encoding to specified encoding not supported. Manifest Parse Error : The name 'xml' is reserved and must be lower case. Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'. Manifest Parse Error : The standalone attribute cannot be used in external entities. hManifest Parse Error : Invalid version number. Manifest Parse Error : Missing equals sign between attribute and attribute value. Assembly Protection Error : Unable to recover the specified assembly. Assembly Protection Error : The public key for an assembly was too short to be allowed. Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest. An HRESULT could not be translated to a corresponding Win32 error code. Assembly Protection Error : The catalog for an assembly is missing. The supplied assembly identity is missing one or more attributes which must be present in this context. The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names. `The referenced assembly could not be found. The activation context activation stack for the running thread of execution is corrupt. The application isolation metadata for this process or thread has become corrupt. The activation context being deactivated is not the most recently activated one. The activation context being deactivated is not active for the current thread of execution. The activation context being deactivated has already been deactivated. A component used by the isolation facility has requested to terminate the process. A kernel mode component is releasing a reference on an activation context. The activation context of system default assembly could not be generated. The value of an attribute in an identity is not within the legal range. The name of an attribute in an identity is not within the legal range. An identity contains two definitions for the same attribute. @The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value. A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found. The public key token does not correspond to the public key specified. TA substitution string had no mapping. xThe component must be locked before making the request. XThe component store has been corrupted. xAn advanced installer failed during setup or servicing. The character encoding in the XML declaration did not match the encoding used in the document. The identities of the manifests are identical but their contents are different. XThe component identities are different. LThe assembly is not a deployment. XThe file is not a part of the assembly. tThe size of the manifest exceeds the maximum allowed. HThe setting is not registered. One or more required members of the transaction are not present. The SMI primitive installer failed during setup or servicing. A generic command executable returned a result that indicates failure. A component is missing file verification information in its manifest. XThe specified channel path is invalid. HThe specified query is invalid. xThe publisher metadata cannot be found in the resource. The template for an event definition cannot be found in the resource (error = %1). \The specified publisher name is invalid. The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest The specified channel could not be found. Check channel configuration. The specified xml text was not well-formed. See Extended Error for more details. LThe 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. 4Configuration error. The 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. lQuery result is currently at an invalid position. dRegistered MSXML doesn't support validation. XAn 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. Can't perform a step operation from a term that does not represent an element set. Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants. A 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. \This data type is currently unsupported. \A syntax error occurred at position %1!d! This operator is unsupported by this implementation of the filter. TThe token encountered was unexpected. <The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation. PChannel property %1!s! 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. XPublisher property %1!s! 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. HThe channel fails to activate. The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions. the message resource is present but the message is not found in the string/message table The message id for the desired message could not be found. The substitution string for insert index (%1) could not be found. The description string for parameter reference (%1) could not be found. tThe maximum number of replacements has been reached. The event definition could not be found for event id (%1). The locale specific resource for the desired message is not present. \The resource is too old to be compatible. \The resource is too new to be compatible. |The channel at index %1!d! of the query can't be opened. DThe 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. Attempted to create a numeric type that is outside of its valid range. PThe subscription fails to activate. PThe 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. When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription. The credential store that is used to save credentials is full. The credential used by this subscription can't be found in credential store. \No active channel is found for the query. dThe resource loader failed to find MUI file. The resource loader failed to load MUI file because the file fail to pass validation. The RC Manifest is corrupted with garbage data or unsupported version or missing required item. \The RC Manifest has invalid culture name. pThe RC Manifest has invalid ultimatefallback name. |The resource loader cache doesn't have loaded MUI entry. PUser stopped resource enumeration. LUI language installation failed. @Locale installation failed. pA resource does not have default or neutral value. <Invalid PRI config file. 0Invalid file type. 0Unknown qualifier. <Invalid qualifier value. 0No Candidate found. The ResourceMap or NamedResource has an item that does not have default or neutral resource.. HInvalid ResourceCandidate type. 8Duplicate Resource Map. ,Duplicate Entry. DInvalid Resource Identifier. 0Filepath too long. @Unsupported directory type. ,Invalid PRI File. <NamedResource Not Found. 8ResourceMap Not Found. DUnsupported MRT profile type. @Invalid qualifier operator. Unable to determine qualifier value or qualifier value has not been set. TAutomerge is enabled in the PRI file. XToo many resources defined for package. pResource File can not be used for merge operation. Load/UnloadPriFiles cannot be used with resource packages. Resource Contexts may not be created on threads that do not have a CoreWindow. The singleton Resource Manager with different profile is already created. xThe system component cannot operate given API operation The resource is a direct reference to a non-default resource candidate. Resource Map has been re-generated and the query string is not valid anymore. $The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification. The monitor's VCP Version (0xDF) VCP code returned an invalid version value. The monitor does not comply with the MCCS specification it claims to support. 4The 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. LThe 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. tAn internal Monitor Configuration API error occurred. The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. $The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. dThe requested system device cannot be found. Hash generation for the specified hash version and hash type is not enabled on the server. The hash requested from the server is not available or no longer valid. The secondary interrupt controller instance that manages the specified interrupt is not registered. The information supplied by the GPIO client driver is invalid. The version specified by the GPIO client driver is not supported. The registration packet supplied by the GPIO client driver is not valid. The requested operation is not suppported for the specified handle. The requested connect mode conflicts with an existing mode on one or more of the specified pins. tThe interrupt requested to be unmasked is not masked. The requested run level switch cannot be completed successfully. The service has an invalid run level setting. The run level for a service must not be higher than the run level of its dependent services. 0The requested run level switch cannot be completed successfully since one or more services will not stop or restart within the specified timeout. A run level switch agent did not respond within the specified timeout. dA run level switch is currently in progress. One or more services failed to start during the service startup phase of a run level switch. The task stop request cannot be completed immediately since task needs more time to shutdown. DPackage could not be opened. 8Package was not found. <Package data is invalid. Package failed updates, dependency or conflict validation. There is not enough disk space on your computer. Please free up some space and try again. dThere was a problem downloading your product. LPackage could not be registered. PPackage could not be unregistered. PUser cancelled the install request. tInstall failed. Please contact your software vendor. tRemoval failed. Please contact your software vendor. ,The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. The application cannot be started. Try reinstalling the application to fix the problem. tA Prerequisite for an install could not be satisfied. TThe package repository is corrupted. To install this application you need either a Windows developer license or a sideloading-enabled system. The application cannot be started because it is currently updating. The package deployment operation is blocked by policy. Please contact your system administrator. The package could not be installed because resources it modifies are currently in use. The package could not be recovered because necessary data for recovery have been corrupted. The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present. An error occurred while deleting the package's previously existing application data. The package could not be installed because a higher version of this package is already installed. An error in a system binary was detected. Try refreshing the PC to fix the problem. xA corrupted CLR NGEN binary was detected on the system. The operation could not be resumed because necessary data for recovery have been corrupted. The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again. TThe process has no package identity. dThe package runtime information is corrupted. PThe package identity is corrupted. \The process has no application identity. POne 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. DOne or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log. HLoading the state store failed. |Retrieving the state version for the application failed. tSetting the state version for the application failed. |Resetting the structured state of the application failed. `State Manager failed to open the container. dState Manager failed to create the container. dState Manager failed to delete the container. \State Manager failed to read the setting. `State Manager failed to write the setting. `State Manager failed to delete the setting. `State Manager failed to query the setting. pState Manager failed to read the composite setting. tState Manager failed to write the composite setting. lState Manager failed to enumerate the containers. hState Manager failed to enumerate the settings. The size of the state manager composite setting value has exceeded the limit. The size of the state manager setting value has exceeded the limit. The length of the state manager setting name has exceeded the limit. The length of the state manager container name has exceeded the limit. This API cannot be used in the context of the caller's application type. This PC does not have a valid license for the application or product. The authenticated user does not have a valid license for the application or product. The commerce transaction associated with this license is still pending verification. `The license has been revoked for this user. The underlying file was converted to compound file format. The storage operation should block until more data is available. hThe storage operation should retry immediately. The notified event sink will not influence the storage operation. |Multiple opens prevent consolidated. (commit succeeded). Consolidation of the storage file failed. (commit succeeded). Consolidation of the storage file is inappropriate. (commit succeeded). Use the registry database to provide the requested information 0Success, but static @Macintosh clipboard format @Successful drop took place DDrag-drop operation canceled 8Use the default cursor 8Data has same FORMATETC 8View is already frozen 8FORMATETC not supported Same cache <Some cache(s) not updated @Invalid verb for OLE object lVerb number is valid but verb cannot be done now DInvalid window handle passed Message is too long; some of it had to be truncated before displaying XUnable to convert OLESTREAM to IStorage <Moniker reduced to itself DCommon prefix is this moniker HCommon prefix is input moniker HCommon prefix is both monikers tMoniker is already registered in running object table An event was able to invoke some but not all of the subscribers tAn event was delivered but there were no subscribers lTabletPC inking error code. String was truncated TabletPC inking error code. Recognition or training was interrupted TabletPC inking error code. No personalization update to the recognizer because no training data found tThe task is ready to run at its next scheduled time. HThe task is currently running. The task will not run at the scheduled times because it has been disabled. <The task has not yet run. hThere are no more runs scheduled for this task. One or more of the properties that are needed to run this task on a schedule have not been set. tThe last run of the task was terminated by the user. Either the task has no triggers or the existing triggers are disabled or not set. \Event triggers don't have set run times. The task is registered, but not all specified triggers will start the task, check task scheduler event log for detailed information. The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal. tThe Task Scheduler service has asked the task to run. An asynchronous operation was specified. The operation has begun, but its outcome is not known yet. $XACT_S_DEFECT The method call succeeded because the transaction was read-only. The transaction was successfully aborted. However, this is a coordinated transaction, and some number of enlisted resources were aborted outright because they could not support abort-retaining semantics No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes. The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call. xThe sink is for the moment and wishes the transaction to proceed, but if other changes are made following this return by other event sinks then this sink wants another chance to look The transaction was successfully aborted. However, the abort was non-retaining. `An abort operation was already in progress. The resource manager has performed a single-phase commit of the transaction. XThe local transaction has not aborted. The resource manager has requested to be the coordinator (last resource manager) for the transaction. hNot all the requested interfaces were available xThe specified machine name was not found in the cache. The function completed successfully, but must be called again to complete the context The function completed successfully, but CompleteToken must be called The function completed successfully, but both CompleteToken and this function must be called to complete the context The logon was completed, but no network authority was available. The logon was made using locally known information pThe context has expired and can no longer be used. The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context. tThe context data must be renegotiated with the peer. There is no LSA mode context associated with this context. A signature operation must be performed before the user can authenticate. lThe recipient rejected the renegotiation request. The returned buffer is only a fragment of the message. More fragments need to be returned. The function completed successfully, but must be called again to complete the context. Early start can be used. dThe protected data needs to be re-protected. 8Debugger was attached. 4Report was uploaded. 0Report was queued. 8Reporting was disabled. TReporting was temporarily suspended. lReport was not queued to queueing being disabled. Report was uploaded, but not archived due to archiving being disabled. Reporting was successfully spun off as an asynchronous operation. @The assertion was handled. The assertion was handled and added to a permanent ignore list. XThe assertion was resumed as unhandled. 4Report was throttled. LThe IO was completed by a filter. xNo mode is pinned on the specified VidPN source/target. Specified mode set does not specify preference for one of its modes. Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. Specified content transformation is not pinned on the specified VidPN present path. {GDI redirection surface was returned} GDI redirection surface of the top level window was returned. pA certificate is already present in the cert store. The Store was launched instead of the specified app because the app's package was in an invalid state. This app failed to launch, but the error was handled with a dialog. HProperty value will be ignored. The request will be completed later by NDIS status indication. The troubleshooting pack cannot be executed on this system. hThe function call is completing asynchronously. tThere are no more messages available on the channel. @The graph data was created. DThere is not more event data. ,No connectivity. ,Already a member. DThe graph is already connect. LThe subscription already exists. The storage pool was deleted by the driver. The object cache should be updated. lThe Present operation was invisible to the user. The Present operation was partially invisible to the user. The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager. The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del). The Present operation was not visible because the target monitor was being used for some other purpose. The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation. The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time. TThe swapchain has become unoccluded. 8The adapter did not have access to the required resources to complete the Desktop Duplication Present() call, the Present() call needs to be made again Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific). Skip preparation of allocations referenced by the DMA buffer. lChild device presence was not reliably detected. Starting the leadlink adapter has been deferred temporarily. The display adapter is being polled for children too frequently at the same polling level. pStarting the adapter has been deferred temporarily. (Not implemented ,Ran out of memory LOne or more arguments are invalid @No such interface supported (Invalid pointer (Invalid handle ,Operation aborted ,Unspecified error @General access denied error The data necessary to complete this operation is not yet available. The operation attempted to access data outside the valid range A concurrent or interleaved operation changed the state of the object, invalidating this operation. XAn illegal state change was requested. `A method was called at an unexpected time. tTypename or Namespace was not found in metadata file. tName is an existing namespace rather than a typename. HTypename has an invalid format. XMetadata file is invalid or corrupted. @The object has been closed. Only one thread may access the object during a write operation. pOperation is prohibited during change notification. The text associated with this error code could not be found. @String not null terminated. \A delegate was assigned when not allowed. dAn async operation was not properly started. The application is exiting and cannot service this request The application view is exiting and cannot service this request pThe object must support the IAgileObject interface Activating a single-threaded class from MTA is not supported HThe object has been committed. tA 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. (Not implemented @No such interface supported (Invalid pointer ,Operation aborted ,Unspecified error DThread local storage failure PGet shared memory allocator failure DGet memory allocator failure LUnable to initialize class cache LUnable to initialize RPC services hCannot set thread local storage channel control xCould not allocate thread local storage channel control pThe user supplied memory allocator is unacceptable TThe OLE service mutex already exists `The OLE service file mapping already exists `Unable to map view of file for OLE service \Failure attempting to launch OLE service There was an attempt to call CoInitialize a second time while single threaded tA Remote activation was necessary but was not allowed A Remote activation was necessary but the server name provided was invalid The class is configured to run as a security id different from the caller xUse of Ole1 services requiring DDE windows is disabled A RunAs specification must be <domain name>\<user name> or simply <user name> The server process could not be started. The pathname may be incorrect. The server process could not be started as the configured identity. The pathname may be incorrect or unavailable. The server process could not be started because the configured identity is incorrect. Check the username and password. lThe client is not allowed to launch this server. xThe service providing this server could not be started. This computer was unable to communicate with the computer providing the server. lThe server did not respond after being launched. The registration information for this server is inconsistent or incomplete. The registration information for this interface is inconsistent or incomplete. \The operation attempted is not supported. 4A dll must be loaded. tA Microsoft Software Installer error was encountered. The specified activation could not occur in the client context as specified. TActivations on the server are paused. \Activations on the server are not paused. The component or application containing the component has been disabled. dThe common language runtime is not available |The thread-pool rejected the submitted asynchronous work. The server started, but did not finish initializing in a timely fashion. Unable to complete the call since there is no COM+ security context inside IObjectControl.Activate. dThe provided tracker configuration is invalid lThe provided thread pool configuration is invalid pThe provided side-by-side configuration is invalid The server principal name (SPN) obtained during security negotiation is malformed. The caller failed to revoke a per-apartment registration before apartment shutdown. The object has been rundown by the stub manager while there are external clients. 4Catastrophic failure DCall was rejected by callee. \Call was canceled by the message filter. The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage. The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call. xIt is illegal to call out while inside message filter. The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid. The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. The caller (client) disappeared while the callee (server) was processing a call. The data packet with the marshalled parameter data is incorrect. The call was not transmitted properly; the message queue was full and was not emptied after yielding. The client (caller) cannot marshall the parameter data - low memory, etc. The client (caller) cannot unmarshall the return data - low memory, etc. The server (callee) cannot marshall the return data - low memory, etc. The server (callee) cannot unmarshall the parameter data - low memory, etc. |Received data is invalid; could be server or client data. A particular parameter is invalid and cannot be (un)marshalled. There is no second outgoing call on same channel in DDE conversation. The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute. 0System call failed. Could not allocate some required resource (memory, events, ...) Attempted to make calls on more than one thread in single threaded mode. The requested interface is not registered on the server object. RPC could not call the server or could not return the results of calling the server. HThe server threw an exception. `Cannot change thread mode after it is set. hThe method called does not exist on the server. tThe object invoked has disconnected from its clients. The object invoked chose not to process the call now. Try again later. The message filter indicated that the application is busy. TThe message filter rejected the call. xA call control interfaces was called with invalid data. An outgoing call cannot be made since the application is dispatching an input-synchronous call. The application called an interface that was marshalled for a different thread. xCoInitialize has not been called on the current thread. The version of OLE on the client and server machines does not match. dOLE received a packet with an invalid header. lOLE received a packet with an invalid extension. lThe requested object or interface does not exist. TThe requested object does not exist. pOLE has sent a request and is waiting for a reply. \OLE is waiting before retrying a request. tCall context cannot be accessed after call completed. hImpersonate on unsecure calls is not supported. Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized. @No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server. ,Access is denied. hRemote calls are not allowed for this process. The marshaled interface data packet (OBJREF) has an invalid or unknown format. No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call. This operation returned because the timeout period expired. dThere are no synchronize objects to wait on. Full subject issuer chain SSL principal name expected from the server. \Principal name is not a valid MSSTD name. LUnable to impersonate DCOM client `Unable to obtain server's security context tUnable to open the access token of the current thread hUnable to obtain user info from an access token The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method hUnable to obtain the client's security blanket Unable to set a discretionary ACL into a security descriptor lThe system function, AccessCheck, returned false Either NetAccessDel or NetAccessAdd returned an error code. One of the trustee strings provided by the user did not conform to the <Domain>\<Name> syntax and it was not the "*" string One of the security identifiers provided by the user was invalid Unable to convert a wide character trustee string to a multibyte trustee string Unable to find a security identifier that corresponds to a trustee string provided by the user dThe system function, LookupAccountSID, failed Unable to find a trustee name that corresponds to a security identifier provided by the user hThe system function, LookupAccountName, failed dUnable to set or reset a serialization handle XUnable to obtain the Windows directory $Path too long @Unable to generate a uuid. 4Unable to create file |Unable to close a serialization handle or a file handle. xThe number of ACEs in an ACL exceeds the system limit. Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream. The version of ACL format in the stream is not supported by this implementation of IAccessControl tUnable to open the access token of the server process Unable to decode the ACL in the stream provided by the user lThe COM IAccessControl object is not initialized DCall Cancellation is disabled @An internal error occurred. 0Unknown interface. ,Member not found. 4Parameter not found. (Type mismatch. $Unknown name. 0No named arguments. 0Bad variable type. 0Exception occurred. 4Out of present range. (Invalid index. ,Unknown language. ,Memory is locked. DInvalid number of parameters. 8Parameter not optional. (Invalid callee. HDoes not support a collection. ,Division by zero. ,Buffer too small ,Buffer too small. TField name not defined in the record. POld format or invalid type library. POld format or invalid type library. LError accessing the OLE registry. 8Library not registered. 8Bound to unknown type. @Qualified name disallowed. Invalid forward reference, or reference to uncompiled type. (Type mismatch. 0Element not found. (Ambiguous name. PName already exists in the library. $Unknown LCID. XFunction not defined in specified DLL. TWrong module kind for the operation. <Size may not exceed 64K. XDuplicate ID in inheritance hierarchy. tIncorrect inheritance depth in standard OLE hmember. (Type mismatch. DInvalid number of arguments. I/O Error. HError creating unique tmp file. HError loading type library/DLL. LInconsistent property functions. `Circular dependency between types/modules. XUnable to perform requested operation. 8%1 could not be found. HThe path %1 could not be found. xThere are insufficient resources to open another file. (Access Denied. dAttempted an operation on an invalid object. There is insufficient memory available to complete operation. 8Invalid pointer error. TThere are no more entries to return. <Disk is write-protected. `An error occurred during a seek operation. hA disk error occurred during a write operation. hA disk error occurred during a read operation. HA share violation has occurred. HA lock violation has occurred. 0%1 already exists. <Invalid parameter error. xThere is insufficient disk space to complete operation. Illegal write of non-simple property to simple property set. HAn API call exited abnormally. \The file %1 is not a valid compound file. <The name %1 is not valid. DAn unexpected error occurred. LThat function is not implemented. 0Invalid flag error. \Attempted to use an object that is busy. pThe storage has been changed since the last commit. tAttempted to use an object that has ceased to exist. Can't save. The compound file %1 was produced with an incompatible version of storage. The compound file %1 was produced with a newer version of storage. pShare.exe or equivalent is required for operation. pIllegal operation called on non-file based storage. Illegal operation called on object with extant marshallings. HThe docfile has been corrupted. hOLE32.DLL has been loaded at the wrong address. The compound file is too large for the current implementation The compound file was not created with the STGM_SIMPLE flag The file download was aborted abnormally. The file is incomplete. XThe file download has been terminated. PThe storage device is unresponsive. HGeneric Copy Protection Error. xCopy Protection Error - DVD CSS Authentication failed. Copy Protection Error - The given sector does not have a valid CSS key. |Copy Protection Error - DVD session key not established. Copy Protection Error - The read failed because the sector is encrypted. Copy Protection Error - The current DVD's region does not correspond to the region setting of the drive. Copy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted. <Invalid OLEVERB structure 4Invalid advise flags Can't enumerate any more, because the associated data is missing \This implementation doesn't take advises dThere is no connection for this connection ID lNeed to run the object to perform this operation HThere is no cache to operate on 4Uninitialized object \Linked object's source class has changed \Not able to get the moniker of the object HNot able to bind to the source XObject is static; operation not allowed LUser canceled out of save dialog ,Invalid rectangle pcompobj.dll is too old for the ole2.dll initialized 4Invalid window handle lObject is not in any of the inplace active states @Not able to convert object Not able to perform the operation because object is not given storage yet @Invalid FORMATETC structure LInvalid DVTARGETDEVICE structure DInvalid STDGMEDIUM structure @Invalid STATDATA structure (Invalid lindex $Invalid tymed <Invalid clipboard format ,Invalid aspect(s) tdSize parameter of the DVTARGETDEVICE structure is invalid dObject doesn't support IViewObject interface Trying to revoke a drop target that has not been registered |This window has already been registered as a drop target 4Invalid window handle XA drag operation is already in progress Class does not support aggregation (or class object is remote) `ClassFactory cannot supply requested class DClass is not licensed for use 0Error drawing view LCould not read key from registry HCould not write key to registry XCould not find the key in the registry @Invalid value for registry 4Class not registered <Interface not registered PThreading model entry is not valid 4CATID does not exist 4Description not found No package in the software installation data in the Active Directory meets this criteria. Deleting this will break the referential integrity of the software installation data in the Active Directory. The CLSID was not found in the software installation data in the Active Directory. The software installation data in the Active Directory is corrupt. There is no software installation data in the Active Directory. There is no software installation data object in the Active Directory. The software installation data object in the Active Directory already exists. The path to the software installation data in the Active Directory is not correct. `A network error interrupted the operation. The size of this object exceeds the maximum size set by the Administrator. The schema for the software installation data in the Active Directory does not match the required schema. An error occurred in the software installation data in the Active Directory. ,Cache not updated 8No verbs for OLE object @Invalid verb for OLE object 4Undo is not available LSpace for tools is not available @OLESTREAM Get method failed @OLESTREAM Put method failed hContents of the OLESTREAM not in correct format There was an error in a Windows GDI call while converting the bitmap to a DIB hContents of the IStorage not in correct format Contents of IStorage is missing one of the standard streams There was an error in a Windows GDI call while converting the DIB to a bitmap. 4OpenClipboard Failed 4EmptyClipboard Failed 0SetClipboard Failed DData on clipboard is invalid 4CloseClipboard Failed XMoniker needs to be connected manually @Operation exceeded deadline @Moniker needs to be generic 4Operation unavailable (Invalid syntax 4No object for moniker 8Bad extension for file DIntermediate operation failed 8Moniker is not bindable 4Moniker is not bound <Moniker cannot open file dUser input required for operation to succeed DMoniker class has no inverse LMoniker does not refer to storage ,No common prefix HMoniker could not be enumerated LCoInitialize has not been called. TCoInitialize has already been called. TClass of object cannot be determined 4Invalid class string <Invalid interface string 4Application not found \Application cannot be run more than once LSome error in application program 8DLL for class not found ,Error in the DLL XWrong OS or OS version for application <Object is not registered DObject is already registered LObject is not connected to server Application was launched but it didn't register a class factory <Object has been released tAn event was unable to invoke any of the subscribers |A syntax error occurred trying to evaluate a query string lAn invalid field name was used in a query string PAn unexpected exception was raised \An unexpected internal error was detected xThe owner SID on a per-user subscription doesn't exist A user-supplied component or subscriber raised an exception tAn interface has too many methods to fire events from A subscription cannot be stored unless its event class already exists hNot all the objects requested could be removed |COM+ is required for this operation, but is not installed Cannot modify or delete an object that was not added using the COM+ Admin SDK Cannot modify or delete an object that was added using the COM+ Admin SDK The event class for this subscription is in an invalid partition The owner of the PerUser subscription is not logged on to the system specified dTabletPC inking error code. No default tablet TabletPC inking error code. An invalid input rectangle was specified xTabletPC inking error code. Unknown property specified |TabletPC inking error code. The stroke object was deleted pTabletPC inking error code. Initialization failure TabletPC inking error code. The data required for the operation was not supplied xTabletPC inking error code. Invalid packet description TabletPC inking error code. There are no handwriting recognizers registered TabletPC inking error code. User does not have the necessary rights to read recognizer information TabletPC inking error code. API calls were made in an incorrect order \TabletPC inking error code. Queue is full TabletPC inking error code. RtpEnabled called multiple times TabletPC inking error code. A recognizer returned invalid data TabletPC inking error code. The property was not found, or supported by the recognizer 0Trigger not found. One or more of the properties that are needed to run this task have not been set. \There is no running instance of the task. The Task Scheduler Service is not installed on this computer. TThe task object could not be opened. The object is either an invalid task object or is not a task object. No account information could be found in the Task Scheduler security database for the task indicated. xUnable to establish existence of the account specified. Corruption was detected in the Task Scheduler security database; the database has been reset. Task Scheduler security services are available only on Windows NT. |The task object version is either unsupported or invalid. The task has been configured with an unsupported combination of account settings and run time options. `The Task Scheduler Service is not running. \The task XML contains an unexpected node. The task XML contains an element or attribute from an unexpected namespace. The task XML contains a value which is incorrectly formatted or out of range. |The task XML is missing a required element or attribute. @The task XML is malformed. xThe task XML contains too many nodes of the same type. The task cannot be started after the trigger's end boundary. dAn instance of this task is already running. |The task will not run because the user is not logged on. tThe task image is corrupt or has been tampered with. dThe Task Scheduler service is not available. The Task Scheduler service is too busy to handle your request. Please try again later. The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. 4The task is disabled. The task has properties that are not compatible with previous versions of Windows. The task settings do not allow the task to start on demand. The combination of properties that task is using is not compatible with the scheduling engine. hThe task definition uses a deprecated feature. Another single phase resource manager has already been enlisted in this transaction. dA retaining commit or abort is not supported The transaction failed to commit for an unknown reason. The transaction was aborted. Cannot call commit on this transaction object because the calling application did not initiate the transaction. Instead of committing, the resource heuristically aborted. Instead of aborting, the resource heuristically committed. Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions. Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions. |The requested isolation level is not valid or supported. The transaction manager doesn't support an asynchronous operation for this method. TUnable to enlist in the transaction. |The requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero. There is no resource presently associated with this enlistment The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers. The transaction has already been implicitly or explicitly committed or aborted dAn invalid combination of flags was specified The resource manager id is not associated with this transaction or the transaction manager. \This method was called in the wrong state The indicated unit of work does not match the unit of work expected by the resource manager. hAn enlistment in a transaction already exists. |An import object for the transaction could not be found. PThe transaction cookie is invalid. The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed A time-out was specified, but time-outs are not supported. The requested operation is already in progress for the transaction. \The transaction has already been aborted. pThe Transaction Manager returned a log full error. \The Transaction Manager is not available. pA connection with the transaction manager was lost. A request to establish a connection with the transaction manager was denied. Resource manager reenlistment to determine transaction status timed out. This transaction manager failed to establish a connection with another TIP transaction manager. This transaction manager encountered a protocol error with another TIP transaction manager. This transaction manager could not propagate a transaction from another TIP transaction manager. The Transaction Manager on the destination machine is not available. |The Transaction Manager has disabled its support for TIP. The transaction manager has disabled its support for remote/network transactions. The partner transaction manager has disabled its support for remote/network transactions. The transaction manager has disabled its support for XA transactions. xMSDTC was unable to read its configuration information. `MSDTC was unable to load the dtc proxy dll. PThe local transaction has aborted. The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions. 4XACT_E_CLERKNOTFOUND 0XACT_E_CLERKEXISTS <XACT_E_RECOVERYINPROGRESS <XACT_E_TRANSACTIONCLOSED ,XACT_E_INVALIDLSN 4XACT_E_REPLAYREQUEST The request to connect to the specified transaction coordinator was denied. The maximum number of enlistments for the specified transaction has been reached. A resource manager with the same identifier is already registered with the specified transaction coordinator. The prepare request given was not eligible for single phase optimizations. RecoveryComplete has already been called for the given resource manager. The interface call made was incorrect for the current state of the protocol. \xa_open call failed for the XA resource. `xa_recover call failed for the XA resource. pThe Logical Unit of Work specified cannot be found. pThe specified Logical Unit of Work already exists. Subordinate creation failed. The specified Logical Unit of Work was not connected. xA transaction with the given identifier already exists. 8The resource is in use. LThe LU Recovery process is down. DThe remote session was lost. TThe resource is currently recovering. \There was a mismatch in driving recovery. XAn error occurred with the XA resource. The root transaction wanted to commit, but transaction aborted You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. HThere is no MTS object context The component is configured to use synchronization and this method call would cause a deadlock to occur. The component is configured to use synchronization and a thread has timed out waiting to enter the context. You made a method call on a COM+ component that has a transaction that has already committed or aborted. |The specified role was not configured for the application COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator tAn unexpected error occurred during COM+ Activation. COM+ Activation failed. Check the event log for more information COM+ Activation failed due to a catalog or configuration error. COM+ activation failed because the activation could not be completed in the specified amount of time. COM+ Activation failed because an initialization function failed. Check the event log for more information. The requested operation requires that JIT be in the current context and it is not The requested operation requires that the current context have a Transaction, and it does not The components threading model has changed after install into a COM+ Application. Please re-install component. xIIS intrinsics not available. Start your work with IIS. TAn attempt to write a cookie failed. An attempt to use a database generated a database specific error. The COM+ component you created must use object pooling to work. The COM+ component you created must use object construction to work correctly. The COM+ component requires synchronization, and it is not configured for it. dThe TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the "root" component for the transaction. The creation failed. The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope. The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning. @General access denied error (Invalid handle ,Ran out of memory LOne or more arguments are invalid \No more Internet handles can be allocated 8The operation timed out \The server returned extended information An internal error occurred in the Microsoft Internet extensions 0The URL is invalid `The URL does not use a recognized protocol lThe server name or address could not be resolved xA protocol with the required capabilities was not found 4The option is invalid `The length is incorrect for the option type HThe option value cannot be set xMicrosoft Internet Extension support has been shut down DThe user name was not allowed DThe password was not allowed DThe login request was denied PThe requested operation is invalid HThe operation has been canceled The supplied handle is the wrong type for the requested operation The handle is in the wrong state for the requested operation dThe request cannot be made on a Proxy session TThe registry value could not be found PThe registry parameter is incorrect XDirect Internet access is not available DNo context value was supplied HNo status callback was supplied HThere are outstanding requests PThe information format is incorrect TThe requested item could not be found tA connection with the server could not be established |The connection with the server was terminated abnormally \The connection with the server was reset @The action must be retried DThe proxy request is invalid xUser interaction is required to complete the operation <The handle already exists tThe date in the certificate is invalid or has expired The host name in the certificate is invalid or does not match A redirect request will change a non-secure to a secure connection A redirect request will change a secure to a non-secure connection XMixed secure and non-secure connections @Changing to non-secure post hData is being posted on a non-secure connection A certificate is required to complete client authentication lThe certificate authority is invalid or incorrect xClient authentication has not been correctly installed An error has occurred in a Wininet asynchronous thread. You may need to restart The protocol scheme has changed during a redirect operaiton PThere are operations awaiting retry DThe operation must be retried LThere are no new cache containers A security zone check indicates the operation must be retried TThe SSL certificate contains errors. It was not possible to connect to the revocation server or a definitive response could not be obtained. PThe requested header was not found |The server does not support the requested protocol level xThe server returned an invalid or unrecognized response PThe supplied HTTP header is invalid \The request for a HTTP header is invalid HThe HTTP header already exists LThe HTTP redirect request failed hAn error occurred in the secure channel support `The file could not be written to the cache dThe TCP/IP protocol is not installed properly PThe HTTP request was not redirected xA cookie from the server must be confirmed by the user tA cookie from the server has been declined acceptance dThe computer is disconnected from the network <The server is unreachable HThe proxy server is unreachable hThe proxy auto-configuration script is in error Could not download the proxy auto-configuration script file xThe HTTP redirect request must be confirmed by the user PThe supplied certificate is invalid \The supplied certificate has been revoked The Dialup failed because file sharing was turned on and a failure was requested if security check was needed pInitialization of the WinINet API has not occurred Login failed and the client should display the entity body to the user @Content decoding has failed XAttempt to create a class object failed LOLE service could not bind object \RPC communication failed with OLE service 0Bad path to object 8Server execution failed |OLE service could not communicate with the object server TMoniker path could not be normalized xObject server is stopping when OLE service contacts it `An invalid root block pointer was specified tAn allocation chain contained an invalid link pointer `The requested allocation size was too large The activation requires a display name to be present under the CLSID key. The activation requires that the RunAs value for the application is Activate As Activator. The class is not configured to support Elevated activation. tAppx packaging API has encountered an internal error. The file is not a valid Appx package because its contents are interleaved. The file is not a valid Appx package because it contains OPC relationships. <The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present. XThe Appx package's manifest is invalid. \The Appx package's block map is invalid. The Appx package's content cannot be read because it is corrupt. The computed hash value of the block does not match the one stored in the block map. The requested byte range is over 4GB when translated to byte range of blocks. The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data. `The background task activation is spurious. Bad UID. Bad Hash. Bad Key. Bad Length. Bad Data. 0Invalid Signature. <Bad Version of provider. DInvalid algorithm specified. <Invalid flags specified. 8Invalid type specified. \Key not valid for use in specified state. `Hash not valid for use in specified state. 0Key does not exist. lInsufficient memory available for the operation. 8Object already exists. (Access denied. 4Object was not found. 8Data already encrypted. @Invalid provider specified. LInvalid provider type specified. LProvider's public key is invalid. 4Keyset does not exist @Provider type not defined. XProvider type as registered is invalid. @The keyset is not defined. LKeyset as registered is invalid. hProvider type does not match registered value. XThe digital signature file is corrupt. dProvider DLL failed to initialize correctly. LProvider DLL could not be found. LThe Keyset parameter is invalid. @An internal error occurred. 8A base error occurred. Provider could not perform the action since the context was acquired as silent. The security token does not have storage space available for an additional container. lThe profile for the user is a temporary profile. The key parameters could not be set because the CSP uses fixed parameters. HThe supplied handle is invalid. @The parameter is incorrect. lThe buffer supplied to a function was too small. \The requested operation is not supported. @No more data is available. \The supplied buffers overlap incorrectly. `The specified data could not be decrypted. TAn internal consistency check failed. dThis operation requires input from the user. lThe cryptographic provider does not support HMAC. The device that is required by this cryptographic provider is not ready for use. The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. The validation of the provided data failed the integrity or signature validation. 0Incorrect password. 0Encryption failed. The device that is required by this cryptographic provider is not found on this platform. xNot enough memory is available to complete this request HThe handle specified is invalid XThe function requested is not supported hThe specified target is unknown or unreachable lThe Local Security Authority cannot be contacted dThe requested security package does not exist xThe caller is not the owner of the desired credentials The security package failed to initialize, and cannot be installed dThe token supplied to the function is invalid The security package is not able to marshall the logon buffer, so the logon attempt has failed The per-message Quality of Protection is not supported by the security package The security context does not allow impersonation of the client <The logon attempt failed The credentials supplied to the package were not recognized tNo credentials are available in the security package The message or signature supplied for verification has been altered |The message supplied for verification is out of sequence pNo authority could be contacted for authentication. dThe requested security package does not exist pThe context has expired and can no longer be used. The supplied message is incomplete. The signature was not verified. The credentials supplied were not complete, and could not be verified. The context could not be initialized. lThe buffers supplied to a function was too small. XThe target principal name is incorrect. |The clocks on the client and server machines are skewed. The certificate chain was issued by an authority that is not trusted. xThe message received was unexpected or badly formatted. An unknown error occurred while processing the certificate. TThe received certificate has expired. `The specified data could not be encrypted. dThe specified data could not be decrypted. The client and server cannot communicate, because they do not possess a common algorithm. (The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation). A security context was deleted before the context was completed. This is considered a logon failure. The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. Unable to accomplish the requested task because the local machine does not have any IP addresses. The supplied credential handle does not match the credential associated with the security context. The crypto system or checksum function is invalid because a required function is unavailable. |The number of maximum ticket referrals has been exceeded. The local machine must be a Kerberos KDC (domain controller) and it is not. The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. tThe KDC reply contained more than one principal name. Expected to find PA data for a hint of what etype to use, but it was not found. (The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator. dSmartcard logon is required and was not used. LA system shutdown is in progress. XAn invalid request was sent to the KDC. The KDC was unable to generate a referral for the service requested. The encryption type requested is not supported by the KDC. An unsupported preauthentication mechanism was presented to the Kerberos package. DThe requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. xClient's supplied SSPI channel bindings were incorrect. |The received certificate was mapped to multiple accounts. ,SEC_E_NO_KERB_KEY tThe certificate is not valid for the requested usage. The system cannot contact a domain controller to service the authentication request. Please try again later. PThe smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. DAn untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator. $The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator. The smartcard certificate used for authentication was not trusted. Please contact your system administrator. The smartcard certificate used for authentication has expired. Please contact your system administrator. HThe Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user. An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator. The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator. An untrusted certificate authority was detected while processing the domain controller certificate used for authentication. There is additional information in the system event log. Please contact your system administrator. DThe domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log. LThe domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log. One or more of the parameters passed to the function was invalid. Client policy does not allow credential delegation to target server. Client policy does not allow credential delegation to target server with NLTM only authentication. dThe required security context does not exist. The PKU2U protocol encountered an error while attempting to utilize the associated certificates. The identity of the server computer could not be verified. DOnly https scheme is allowed. No common application protocol exists between the client and the server. Application protocol negotiation failed. An error occurred while performing an operation on a cryptographic message. LUnknown cryptographic algorithm. `The object identifier is poorly formatted. PInvalid cryptographic message type. `Unexpected cryptographic message encoding. The cryptographic message does not contain an expected authenticated attribute. HThe hash value is not correct. DThe index value is not valid. The content of the cryptographic message has already been decrypted. The content of the cryptographic message has not been decrypted yet. The enveloped-data message does not contain the specified recipient. 4Invalid control type. TInvalid issuer and/or serial number. LCannot find the original signer. The cryptographic message does not contain all of the requested attributes. The streamed cryptographic message is not ready to return data. The streamed cryptographic message requires more data to complete the decode operation. The length specified for the output data was insufficient. tAn error occurred during encode or decode operation. tAn error occurred while reading or writing to a file. HCannot find object or property. XThe object or property already exists. pNo provider was specified for the store or object. \The specified certificate is self signed. tThe previous certificate or CRL context was deleted. LCannot find the requested object. The certificate does not have a property that references a private key. Cannot find the certificate and private key for decryption. Cannot find the certificate and private key to use for decryption. Not a cryptographic message or the cryptographic message is not formatted correctly. The signed cryptographic message does not have a signer for the specified signer index. Final closure is pending until additional frees or closes. @The certificate is revoked. No Dll or exported function was found to verify revocation. The revocation function was unable to check revocation for the certificate. The revocation function was unable to check revocation because the revocation server was offline. The certificate is not in the revocation server's database. dThe string contains a non-numeric character. hThe string contains a non-printable character. The string contains a character not in the 7 bit ASCII character set. The string contains an invalid X500 name attribute key, oid, value or delimiter. 8The 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. @The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done. The cryptographic operation failed due to a local security option setting. No DLL or exported function was found to verify subject usage. The called function was unable to do a usage check on the subject. Since the server was offline, the called function was unable to complete the usage check. The subject was not found in a Certificate Trust List (CTL). None of the signers of the cryptographic message or certificate trust list is trusted. pThe public key's algorithm parameters are missing. An object could not be located using the object locator infrastructure with the given name. LOSS 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. dOSS ASN.1 Error: Output Buffer is too small. OSS ASN.1 Error: Signed integer is encoded as a unsigned integer. \OSS ASN.1 Error: Unknown ASN.1 data type. OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated. HOSS ASN.1 Error: Invalid data. POSS ASN.1 Error: Invalid argument. lOSS ASN.1 Error: Encode/Decode version mismatch. HOSS ASN.1 Error: Out of memory. TOSS ASN.1 Error: Encode/Decode Error. LOSS ASN.1 Error: Internal Error. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. OSS ASN.1 Error: Unsupported BER indefinite-length encoding. POSS ASN.1 Error: Access violation. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. LOSS ASN.1 Error: Internal Error. `OSS ASN.1 Error: Multi-threading conflict. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. |OSS ASN.1 Error: Encode/Decode function not implemented. POSS ASN.1 Error: Trace file error. `OSS ASN.1 Error: Function not implemented. TOSS ASN.1 Error: Program link error. POSS ASN.1 Error: Trace file error. POSS ASN.1 Error: Trace file error. HOSS ASN.1 Error: Invalid data. HOSS ASN.1 Error: Invalid data. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. TOSS ASN.1 Error: Program link error. XOSS ASN.1 Error: System resource error. POSS ASN.1 Error: Trace file error. ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR. TASN1 internal encode or decode error. DASN1 unexpected end of data. 4ASN1 corrupted data. 4ASN1 value too large. <ASN1 constraint violated. 0ASN1 out of memory. 4ASN1 buffer overflow. \ASN1 function not supported for this PDU. TASN1 bad arguments to function call. 4ASN1 bad real value. 8ASN1 bad tag value met. 8ASN1 bad choice value. 8ASN1 bad encoding rule. <ASN1 bad unicode (UTF8). 0ASN1 bad PDU type. <ASN1 not yet implemented. PASN1 skipped unknown extension(s). <ASN1 end of data expected lThe request subject name is invalid or too long. @The request does not exist. The request's current status does not allow this operation. XThe requested property value is empty. The certification authority's certificate contains invalid data. Certificate service has been suspended for a database restore operation. The certificate contains an encoded length that is potentially incompatible with older enrollment software. The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation. $The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester. Cannot archive private key. The certification authority is not configured for key archival. Cannot archive private key. The certification authority could not verify one or more key recovery certificates. The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature. At least one security principal must have the permission to manage this CA. The request contains an invalid renewal certificate attribute. An attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions. lA memory reference caused a data alignment fault. The permissions on this certification authority do not allow the current user to enroll for certificates. The permissions on the certificate template do not allow the current user to enroll for this type of certificate. `The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access. The request was denied by a certificate manager or CA administrator. hAn enrollment policy server cannot be located. A signature algorithm or public key length does not meet the system's minimum required strength. ,Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation. \No encryption certificate was specified. The requested certificate template is not supported by this CA. |The request contains no certificate template information. xThe request contains conflicting template information. The request is missing a required Subject Alternate name extension. The request is missing a required private key for archival by the server. The request is missing a required SMIME capabilities extension. `The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request. The request template version is newer than the supported template version. The template is missing a required signature policy attribute. The request is missing required signature policy information. xThe request is missing one or more required signatures. 0One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures. The request is missing one or more required signature issuance policies. The UPN is unavailable and cannot be added to the Subject Alternate name. The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name. The DNS name is unavailable and cannot be added to the Subject Alternate name. The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template. The public key does not meet the minimum size required by the specified certificate template. The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name. One or more certificate templates to be enabled on this certification authority could not be found. @The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed. The certificate template requires too many RA signatures. Only one RA signature is allowed. The certificate template requires renewal with the same public key, but the request uses a different public key. 0The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent. The certification authority cannot validate the Attestation Identity Key Id Binding. The certification authority cannot validate the private key attestation data. The request does not support private key attestation as defined in the certificate template. The request public key is not consistent with the private key attestation data. 0The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable. The attestation response could not be validated. It is either unexpected or incorrect. A valid Request ID was not detected in the request attributes, or an invalid one was submitted. @The key is not exportable. You cannot add the root CA certificate into your local store. The key archival hash attribute was not found in the response. An unexpected key archival hash attribute was found in the response. There is a key archival hash mismatch between the request and the response. pSigning certificate cannot include SMIME extension. tA system-level error occurred while verifying trust. The certificate for the signer of the message is invalid or not found. `One of the counter signatures was invalid. tThe signature of the certificate cannot be verified. The timestamp signature and/or certificate could not be verified or is malformed. pThe digital signature of the object did not verify. A certificate's basic constraint extension has not been observed. The certificate does not meet or contain the Authenticode(tm) financial extensions. Tried to reference a part of the file outside the proper range. `Could not retrieve an object from the file. `Could not find the head table in the file. lThe magic number in the head table is incorrect. XThe offset table has incorrect values. xDuplicate table tags or tags out of alphabetical order. hA table does not start on a long word boundary. tFirst table does not appear after header information. @Two or more tables overlap. |Too many pad bytes between tables or pad bytes are not 0. dFile is too small to contain the last table. HA table checksum is incorrect. HThe file checksum is incorrect. The signature does not have the correct attributes for the policy. XThe file did not pass the hints check. LThe file is not an OpenType file. tFailed on a file operation (open, map, read, write). XA call to a CryptoAPI function failed. `There is a bad version number in the file. dThe structure of the DSIG table is incorrect. dA check failed in a partially constant table. HSome kind of structural error. hThe requested credential requires confirmation. 8Unknown trust provider. The trust verification action specified is not supported by the specified trust provider. The form specified for the subject is not one supported or known by the specified trust provider. tThe subject is not trusted for the specified action. hError due to problem in ASN.1 encoding process. hError due to problem in ASN.1 decoding process. Reading / writing Extensions where Attributes are appropriate, and vice versa. PUnspecified cryptographic failure. dThe size of the data could not be determined. The size of the indefinite-sized data could not be determined. tThis object does not read and write self-sizing data. \No signature was present in the subject. $A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. The validity periods of the certification chain do not nest correctly. A certificate that can only be used as an end-entity is being used as a CA or vice versa. A path length constraint in the certification chain has been violated. A certificate contains an unknown extension that is marked 'critical'. A certificate being used for a purpose other than the ones specified by its CA. A parent of a given certificate in fact did not issue that child certificate. A certificate is missing or has an empty value for an important field, such as a subject or issuer name. A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. A certificate chain could not be built to a trusted root authority. 8Generic trust failure. pA certificate was explicitly revoked by its issuer. The certification path terminates with the test root which is not trusted with the current policy settings. The revocation process could not continue - the certificate(s) could not be checked. The certificate's CN name does not match the passed value. tThe certificate is not valid for the requested usage. The certificate was explicitly marked as untrusted by the user. A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider. PThe certificate has invalid policy. The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded. 0The URL is invalid. \No Internet session has been established. XUnable to connect to the target server. lThe system cannot locate the resource specified. hThe system cannot locate the object specified. lNo data is available for the requested resource. pThe download of the specified resource has failed. pAuthentication is required to access this resource. xThe server could not recognize the provided mime type. DThe operation was timed out. The server did not understand the request, or the request was invalid. PThe specified protocol is unknown. DA security problem occurred. dThe system could not load the persisted data. LUnable to instantiate the object. HA redirection problem occurred. pThe requested resource is a directory, not a file. Security certificate required to access this resource is invalid. A non-empty line was encountered in the INF before the start of a section. A section name marker in the INF is not complete, or does not exist on a line by itself. An INF section was encountered whose name exceeds the maximum section name length. LThe syntax of the INF is invalid. The style of the INF is different than what was requested. hThe required section was not found in the INF. `The required line was not found in the INF. The files affected by the installation of this file queue have not been backed up for uninstall. The INF or the device information set or element does not have an associated install class. The INF or the device information set or element does not match the specified install class. An existing device was found that is a duplicate of the device being manually installed. There is no driver selected for the device information set or element. lThe requested device registry key does not exist. TThe device instance name is invalid. hThe install class is not present or is invalid. The device instance cannot be created because it already exists. The operation cannot be performed on a device information element that has not been registered. TThe device property code is invalid. The INF from which a driver list is to be built does not exist. |The device instance does not exist in the hardware tree. The icon representing this install class cannot be loaded. hThe class installer registry entry is invalid. The class installer has indicated that the default action should be performed for this installation request. xThe operation does not require any files to be copied. hThe specified hardware profile does not exist. There is no device information element currently selected for this device information set. The operation cannot be performed because the device information set is locked. The operation cannot be performed because the device information element is locked. The specified path does not contain any applicable device INFs. No class installer parameters have been set for the device information set or element. The operation cannot be performed because the file queue is locked. xA service installation section in this INF is invalid. There is no class driver list for the device information element. The installation failed because a function driver was not specified for this device instance. There is presently no default device interface designated for this interface class. The operation cannot be performed because the device interface is currently active. The operation cannot be performed because the device interface has been removed from the system. |An interface installation section in this INF is invalid. pThis interface class does not exist in the system. The reference string supplied for this interface device is invalid. The specified machine name does not conform to UNC naming conventions. hA general remote communication error occurred. The machine selected for remote communication is not available at this time. The Plug and Play service is not available on the remote machine. tThe property page provider registry entry is invalid. The requested device interface is not present in the system. The device's co-installer has additional work to perform after installation is complete. TThe device's co-installer is invalid. lThere are no compatible drivers for this device. There is no icon that represents this device or device type. |A logical configuration specified in this INF is invalid. The class installer has denied the request to install or upgrade this device. One of the filter drivers installed for this device is invalid. The driver selected for this device does not support this version of Windows. The driver selected for this device does not support Windows. The third-party INF does not contain digital signature information. An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms. HThe device cannot be disabled. dThe device could not be dynamically removed. LCannot copy to specified target. \Driver is not intended for this platform. HOperation not allowed in WOW64. The operation involving unsigned file copying was rolled back, so that a system restore point could be set. An INF was copied into the Windows INF directory in an improper manner. The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product. TAn unknown exception was encountered. A problem was encountered when accessing the Plug and Play registry database. The requested operation is not supported for a remote machine. hThe specified file is not an installed OEM INF. One or more devices are presently installed using the specified INF. pThe requested device install operation is obsolete. A file could not be verified because it does not have an associated catalog signed via Authenticode(tm). Authenticode(tm) signature verification is not supported for the specified INF. The INF was signed with an Authenticode(tm) catalog from a trusted publisher. The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. The publisher of an Authenticode(tm) signed catalog was not established as trusted. 4The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version. The file may only be validated by a catalog signed via Authenticode(tm). One of the installers for this device cannot perform the installation at this time. A problem was encountered while attempting to add the driver to the store. The installation of this device is forbidden by system policy. Contact your system administrator. The installation of this driver is forbidden by system policy. Contact your system administrator. xThe specified INF is the wrong type for this operation. The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. A problem was encountered while attempting to delete the driver from the store. lAn unrecoverable stack overflow was encountered. XNo installed components were detected. TAn internal consistency check failed. pThe action was cancelled by an SCardCancel request. LThe supplied handle was invalid. One or more of the supplied parameters could not be properly interpreted. pRegistry startup information is missing or invalid. tNot enough memory available to complete this command. `An internal consistency timer has expired. The data buffer to receive returned data is too small for the returned data. dThe specified reader name is not recognized. dThe user-specified timeout value has expired. The smart card cannot be accessed because of other connections outstanding. The operation requires a smart card, but no smart card is currently in the device. lThe specified smart card name is not recognized. The system could not dispose of the media in the requested manner. The requested protocols are incompatible with the protocol currently in use with the smart card. |The reader or smart card is not ready to accept commands. One or more of the supplied parameters values could not be properly interpreted. The action was cancelled by the system, presumably to log off or shut down. pAn internal communications error has been detected. An internal error has been detected, but the source is unknown. An ATR obtained from the registry is not a valid ATR string. xAn attempt was made to end a non-existent transaction. |The specified reader is not currently available for use. The operation has been aborted to allow the server application to exit. TThe PCI Receive buffer was too small. The reader driver does not meet minimal requirements for support. xThe reader driver did not produce a unique reader name. The smart card does not meet minimal requirements for support. hThe Smart Card Resource Manager is not running. hThe Smart Card Resource Manager has shut down. XAn unexpected card error has occurred. tNo Primary Provider can be found for the smart card. |The requested order of object creation is not supported. xThis smart card does not support the requested feature. The identified directory does not exist in the smart card. tThe identified file does not exist in the smart card. The supplied path does not represent a smart card directory. xThe supplied path does not represent a smart card file. HAccess is denied to this file. The smart card does not have enough memory to store the information. There was an error trying to set the smart card file object pointer. HThe supplied PIN is incorrect. An unrecognized error code was returned from a layered component. \The requested certificate does not exist. lThe requested certificate could not be obtained. LCannot find a smart card reader. A communications error with the smart card has been detected. Retry the operation. The requested key container does not exist on the smart card. The Smart Card Resource Manager is too busy to complete this operation. TThe smart card PIN cache has expired. TThe smart card PIN cannot be cached. tThe smart card is read only and cannot be written to. The reader cannot communicate with the smart card, due to ATR configuration conflicts. dThe smart card is not responding to a reset. Power has been removed from the smart card, so that further communication is not possible. The smart card has been reset, so any shared state information is invalid. The smart card has been removed, so that further communication is not possible. pAccess was denied because of a security violation. The card cannot be accessed because the wrong PIN was presented. The card cannot be accessed because the maximum number of PIN entry attempts has been reached. lThe end of the smart card file has been reached. TThe action was cancelled by the user. XNo PIN was presented to the smart card. pThe requested item could not be found in the cache. The requested cache item is too old and was deleted from the cache. The new cache item exceeds the maximum per-item size defined for the cache. Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail One or more of the object's properties are missing or invalid XThe object was not found in the catalog LThe object is already registered hError occurred writing to the application file `Error occurred reading the application file `Invalid version number in application file <The file path is invalid TThe application is already installed 8The role already exists PAn error occurred copying the file HOne or more users are not valid xOne or more users in the application file are not valid `The component's CLSID is missing or corrupt dThe component's progID is missing or corrupt Unable to set required authentication level for update request The identity or password set on the application is not valid Application file CLSIDs or IIDs do not match corresponding DLLs pInterface information is either missing or changed dDllRegisterServer failed on component install HNo server file share available 8DLL could not be loaded XThe registered TypeLib ID is not valid XApplication install directory not found lErrors occurred while in the component registrar 8The file does not exist @The DLL could not be loaded LGetClassObject failed in the DLL The DLL does not support the components listed in the TypeLib HThe TypeLib could not be loaded The file does not contain components or component information Changes to this object and its sub-objects have been disabled tThe delete function has been disabled for this object `The server catalog version is not supported 0The component move was disallowed, because the source or destination application is either a system application or currently locked against changes The component move failed because the destination application no longer exists dThe system was unable to register the TypeLib This operation cannot be performed on the system application The component registrar referenced in this file is not available lA component in the same DLL is already installed DThe service is not installed One or more property settings are either invalid or in conflict with each other The object you are attempting to add or rename already exists DThe component already exists LThe registration file is corrupt HThe property value is too large LObject was not found in registry @This object is not poolable A CLSID with the same GUID as the new application ID is already installed on this machine A role assigned to a component, interface, or method did not exist in the application You must have components in an application in order to start the application hThis operation is not enabled on this platform PApplication Proxy is not exportable Failed to start application because it is either a library application or an application proxy TSystem application is not exportable Cannot subscribe to this component (the component may have been imported) tAn event class cannot also be a subscriber component Library applications and application proxies are incompatible pThis function is valid for the base partition only xYou cannot start an application that has been disabled The specified partition name is already in use on this computer The specified partition name is invalid. Check that the name contains at least one visible character The partition cannot be deleted because it is the default partition for one or more users The partition cannot be exported, because one or more components in the partition have the same file name Applications that contain one or more imported components cannot be installed into a non-base partition The application name is not unique and cannot be resolved to an application id The partition name is not unique and cannot be resolved to a partition id pThe COM+ registry database has not been initialized XThe COM+ registry database is not open pThe COM+ registry database detected a system error dThe COM+ registry database is already running This version of the COM+ registry database cannot be migrated The schema version to be migrated could not be found in the COM+ registry database `There was a type mismatch between binaries lA binary of unknown or invalid type was provided There was a type mismatch between a binary and an application `The application cannot be paused or resumed The COM+ Catalog Server threw an exception during execution Only COM+ Applications marked "queued" can be invoked using the "queue" moniker At least one interface must be marked "queued" in order to create a queued component instance with the "queue" moniker MSMQ is required for the requested operation and is not installed Unable to marshal an interface that does not support IPersistStream The message is improperly formatted or was damaged in transit An unauthenticated message was received by an application that accepts only authenticated messages The message was requeued or moved by a user not in the "QC Trusted User" role Cannot create a duplicate resource of type Distributed Transaction Coordinator One of the objects being inserted or updated does not belong to a valid parent collection dOne of the specified objects cannot be found pThe specified application is not currently running \The partition(s) specified are not valid. COM+ applications that run as NT service may not be pooled or recycled One or more users are already assigned to a local partition set. \Library applications may not be recycled. |Applications running as NT services may not be recycled. XThe process has already been recycled. TA paused process may not be recycled. dLibrary applications may not be NT services. The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID. The partition specified as default is not a member of the partition set. TA recycled process may not be paused. dAccess to the specified partition is denied. Only Application Files (*.MSI files) can be installed into partitions. Applications containing one or more legacy components may not be exported to 1.0 format. xLegacy components may not exist in non-base partitions. A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application A private component cannot be moved (or copied) to a library application or to the base partition The Base Application Partition exists in all partition sets and cannot be removed. hAlas, Event Class components cannot be aliased. pAccess is denied because the component is private. TThe specified SAFER level is invalid. xThe specified user cannot write to the system registry XCOM+ partitions are currently disabled. DUnexpected HTTP status code. \Unexpected redirection status code (3xx). `Unexpected client error status code (4xx). `Unexpected server error status code (5xx). 8Multiple choices (300). <Moved permanently (301). $Found (302). ,See Other (303). 0Not modified (304). ,Use proxy (305). <Temporary redirect (307). 0Bad request (400). 0Unauthorized (401). 8Payment required (402). ,Forbidden (403). ,Not found (404). <Method not allowed (405). 4Not acceptable (406). TProxy authentication required (407). 8Request timeout (408). (Conflict (409). Gone (410). 8Length required (411). @Precondition failed (412). HRequest entity too large (413). @Request-URI too long (414). DUnsupported media type (415). XRequested range not satisfiable (416). <Expectation failed (417). DInternal server error (500). 8Not implemented (501). 0Bad gateway (502). @Service unavailable (503). 8Gateway timeout (504). DVersion not supported (505). 8Crash reporting failed. XReport aborted due to user cancelation. XReport aborted due to network failure. 8Report not initialized. Reporting is already in progress for the specified process. TDump not generated due to a throttle. A handler was not defined by the filter for this operation. dA context is already defined for this object. xAsynchronous requests are not valid for this operation. dDisallow the Fast IO path for this operation. An invalid name request was made. The name requested cannot be retrieved at this time. Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). XThe filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers. The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback. The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. tNon-paged pool must be used for this type of context. A duplicate handler definition has been provided for an operation. `The callback data queue has been disabled. tDo not attach the filter to the volume at this time. xDo not detach the filter from the volume at this time. An instance already exists at this altitude on the volume specified. An instance already exists with this name on the volume specified. hThe system could not find the filter specified. hThe system could not find the volume specified. lThe system could not find the instance specified. No registered context allocation definition was found for the given request. An invalid parameter was specified during context registration. The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. The requested device object does not exist for the given volume. \The specified volume is already mounted. The specified Transaction Context is already enlisted in a transaction The specifiec context is already attached to another object No waiter is present for the filter's reply to this message. The filesystem database resource is in use. Registration cannot complete at this time. H{Display Driver Stopped Responding} The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft. \Monitor descriptor could not be obtained. Format of the obtained monitor descriptor is not supported by this release. {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. {Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session. {No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present. {DWM is not queuing presents for the specified window} The window specified is not currently using queued presents. {The adapter specified by the LUID is not found} DWM can not find the adapter specified by the LUID. {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. HThe NAP SoH packet is invalid. XAn SoH was missing from the NAP packet. xThe entity ID conflicts with an already registered id. <No cached SoH is present. dThe entity is still bound to the NAP system. lThe entity is not registered with the NAP system. pThe entity is not initialized with the NAP system. The correlation id in the SoH-Request and SoH-Response do not match up. Completion was indicated on a request that is not currently pending. TThe NAP component's id was not found. The maximum size of the connection is too small for an SoH packet. TThe NapAgent service is not running. lThe entity is disabled with the NapAgent service. HGroup Policy is not configured. DToo many simultaneous calls. PSHV configuration already existed. HSHV configuration is not found. DSHV timed out on the request. The maximum number of items for the access list has been reached. An item must be removed before another item is added. Cannot access Homegroup. Homegroup may not be set up or may have encountered an error. This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again. tThis app can't be activated from an elevated context. lThis app can't be activated when UAC is disabled. This app can't be activated by the Built-in Administrator. This app does not support the contract specified or is not installed. This app has mulitple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous. This app's package family has more than one package installed. This is not supported. The app manager is required to activate applications, but is not running. `The app didn't start in the required time. 4The app didn't start. This app failed to launch because of an issue with its license. Please try again in a moment. This app failed to launch because its trial license has expired. Please choose a folder on a drive that's formatted with the NTFS file system. This location is already being used. Please choose a different location. This location cannot be indexed. Please choose a different location. Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later. \Sorry, the action couldn't be completed. This content can only be moved to a folder. To move the content to this drive, please choose or create a folder. This is an error mask to convert TPM hardware errors to win errors. 8Authentication failed. xThe index to a PCR, DIR or other register is incorrect. DOne or more parameter is bad. An operation completed successfully but the auditing of that operation failed. The clear disable flag is set and all clear operations now require physical access. `Activate the Trusted Platform Module (TPM). \Enable the Trusted Platform Module (TPM). TThe target command has been disabled. 4The operation failed. \The ordinal was unknown or inconsistent. dThe ability to install an owner is disabled. TThe key handle cannot be interpreted. \The key handle points to an invalid key. HUnacceptable encryption scheme. HMigration authorization failed. \PCR information could not be interpreted. 4No room to load key. XThere is no Storage Root Key (SRK) set. An encrypted blob is invalid or was not created by this TPM. xThe Trusted Platform Module (TPM) already has an owner. The TPM has insufficient internal resources to perform the requested action. HA random string was too short. |The TPM does not have the space to perform the operation. |The named PCR value does not match the current PCR value. The paramSize argument to the command has the incorrect value . PThere is no existing SHA-1 thread. The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. HThe 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. The authorization for the second key in a 2 key function failed authorization. hThe tag value sent to for a command is invalid. |An IO error occurred transmitting information to the TPM. TThe encryption process had a problem. \The decryption process did not complete. @An invalid handle was used. |The TPM does not have an Endorsement Key (EK) installed. PThe usage of a key is not allowed. \The submitted entity type is not allowed. The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. xSigned data cannot include additional DER information. The key properties in TPM_KEY_PARMs are not supported by this TPM. pThe migration properties of this key are incorrect. The signature or encryption scheme for this key is incorrect or not permitted in this situation. The size of the data (or blob) parameter is bad or inconsistent with the referenced key. hA mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob. Either the physicalPresence or physicalPresenceLock bits have the wrong value. xThe TPM cannot perform this version of the capability. xThe TPM does not allow for wrapped transport sessions. TPM audit construction failed and the underlying command was returning a failure code also. TPM audit construction failed and the underlying command was returning success. Attempt to reset a PCR register that does not have the resettable attribute. Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. XMake identity blob not properly typed. When saving context identified resource type does not match actual resource. The TPM is attempting to execute a command only available when in FIPS mode. xThe command is attempting to use an invalid family ID. The permission to manipulate the NV storage is not available. \The operation requires a signed command. PWrong operation to load an NV key. NV_LoadKey blob requires both owner and blob authorization. \The NV area is locked and not writtable. xThe locality is incorrect for the attempted operation. lThe NV area is read only and can't be written to. pThere is no protection on the write to the NV area. XThe family count value does not match. \The NV area has already been written to. LThe NV area attributes conflict. The structure tag and version are invalid or inconsistent. The key is under control of the TPM Owner and can only be evicted by the TPM Owner. LThe counter handle is incorrect. hThe write is not a complete write of the area. pThe gap between saved context counts is too large. The maximum number of NV writes without an owner has been exceeded. PNo operator AuthData value is set. lThe resource pointed to by context is not loaded. XThe delegate administration is locked. Attempt to manage a family other then the delegated family. \Delegation table management not enabled. There was a command executed outside of an exclusive transport session. tAttempt to context save a owner evict controlled key. The DAA command has no resources availble to execute the command. The consistency check on DAA parameter inputData0 has failed. The consistency check on DAA parameter inputData1 has failed. xThe consistency check on DAA_issuerSettings has failed. tThe consistency check on DAA_tpmSpecific has failed. The atomic process indicated by the submitted DAA command is not the expected process. The issuer's validity check has detected an inconsistency. XThe consistency check on w has failed. <The handle is incorrect. @Delegation is not correct. DThe context blob is invalid. PToo many contexts held by the TPM. lMigration authority signature validation failure. \Migration destination not authenticated. @Migration source incorrect. HIncorrect migration authority. tAttempt to revoke the EK and the EK is not revocable. DBad signature of CMK ticket. There is no room in the context list for additional contexts. <The command was blocked. PThe specified handle was not found. The TPM returned a duplicate handle and the command needs to be resubmitted. dThe command within the transport was blocked. pThe command within the transport is not supported. The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. HSelfTestFull has not been run. hThe TPM is currently executing a full selftest. The TPM is defending against dictionary attacks and is in a time-out period. An internal error has occurred within the Trusted Platform Module support program. TOne or more input parameters is bad. PA specified output pointer is bad. The specified context handle does not refer to a valid context. XA specified output buffer is too small. pAn error occurred while communicating with the TPM. `One or more context parameters is invalid. |The TBS service is not running and could not be started. A new context could not be created because there are too many open contexts. A new virtual resource could not be created because there are too many open virtual resources. |The TBS service has been started but is not yet running. lThe physical presence interface is not supported. <The command was canceled. \The input or output buffer is too large. A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer. PThe TBS service has been disabled. HNo TCG event log is available. The caller does not have the appropriate rights to perform the requested operation. DThe 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.) The Physical Presence Interface of this firmware does not support the requested method. lThe requested TPM OwnerAuth value was not found. The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information. hThe command buffer is not in the correct state. The command buffer does not contain enough data to satisfy the request. lThe command buffer cannot contain any more data. pOne or more output parameters was NULL or invalid. \One or more input parameters is invalid. xNot enough memory was available to satisfy the request. PThe specified buffer was too small. HAn internal error was detected. The caller does not have the appropriate rights to perform the requested operation. tThe specified authorization information was invalid. `The specified context handle was not valid. pAn error occurred while communicating with the TBS. XThe TPM returned an unexpected result. pThe message was too large for the encoding scheme. dThe encoding in the blob was not recognized. @The key size is not valid. LThe encryption operation failed. `The key parameters structure was not valid The requested supplied data does not appear to be a valid migration authorization blob. PThe specified PCR index was invalid The data given does not appear to be a valid delegate blob. One or more of the specified context parameters was not valid. tThe data given does not appear to be a valid key blob PThe specified PCR data was invalid. hThe format of the owner auth data was invalid. |The random number generated did not pass FIPS RNG check. dThe TCG Event Log does not contain any data. `An entry in the TCG Event Log was invalid. HA TCG Separator was not found. A digest value in a TCG Log entry did not match hashed data. The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance. PThe specified buffer was too small. TThe context could not be cleaned up. \The specified context handle is invalid. `An invalid context parameter was specified. pAn error occurred while communicating with the TPM `No entry with the specified key was found. The specified virtual handle matches a virtual handle already in use. The pointer to the returned handle location was NULL or invalid LOne or more parameters is invalid `The RPC subsystem could not be initialized. LThe TBS scheduler is not running. <The command was canceled. pThere was not enough memory to fulfill the request The specified list is empty, or the iteration has reached the end of the list. dThe specified item was not found in the list. The TPM does not have enough space to load the requested resource. XThere are too many TPM contexts in use. 8The TPM command failed. lThe TBS does not recognize the specified ordinal. hThe requested resource is no longer available. LThe resource type did not match. DNo resources can be unloaded. hNo new entries can be added to the hash table. A new TBS context could not be created because there are too many open contexts. A new virtual resource could not be created because there are too many open virtual resources. lThe physical presence interface is not supported. TBS is not compatible with the version of TPM found on the system. HNo TCG event log is available. A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command. tThe user failed to confirm the TPM operation request. HThe BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM). The BIOS does not support the physical presence interface. 8The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command. This is an error mask to convert Platform Crypto Provider errors to win errors. The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. The handle provided to the Platform Crypto Provider is invalid. A parameter provided to the Platform Crypto Provider is invalid. A provided flag to the Platform Crypto Provider is not supported. The requested operation is not supported by this Platform Crypto Provider. The buffer is too small to contain all data. No information has been written to the buffer. An unexpected internal error has occurred in the Platform Crypto Provider. xThe authorization to use a provider object has failed. The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. TThe referenced policy was not found. TThe referenced profile was not found. LThe validation was not succesful. The RSA key creation is blocked on this TPM due to known security vulnerabilities. LThe object could not be created. Shutdown was already called on this object or the object that owns it. This method cannot be called during this type of callback. This object has been sealed, so this change is no longer allowed. PThe requested value was never set. \The requested value cannot be determined. lA callback returned an invalid output parameter. A callback returned a success code other than S_OK or S_FALSE. A parameter that should be owned by this object is owned by a different object. hMore than one item matched the search criteria. PA floating-point overflow occurred. This method can only be called from the thread that created the object. dThe storyboard is currently in the schedule. HThe storyboard is not playing. xThe start keyframe might occur after the end keyframe. It might not be possible to determine the end keyframe time when the start keyframe is reached. tTwo repeated portions of a storyboard might overlap. xThe transition has already been added to a storyboard. pThe transition has not been added to a storyboard. The transition might eclipse the beginning of another transition in the storyboard. The given time is earlier than the time passed to the last update. dThis client is already connected to a timer. The passed dimension is invalid or does not match the object's dimension. The added primitive begins at or beyond the duration of the interpolator. The operation cannot be completed because the window is being closed. LData Collector Set was not found. Unable to start Data Collector Set because there are too many folders. xNot enough free disk space to start Data Collector Set. The Data Collector Set or one of its dependencies is already in use. PData Collector Set already exists. <Property value conflict. The current configuration for this Data Collector Set requires that it contain exactly one Data Collector. A user account is required in order to commit the current Data Collector Set properties. PData Collector Set is not running. A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list. The executable path you have specified refers to a network share or UNC path. The executable path you have specified is already configured for API tracing. The executable path you have specified does not exist. Verify that the specified path is correct. HData Collector already exists. The wait for the Data Collector Set start notification has timed out. xThe wait for the Data Collector to start has timed out. The wait for the report generation tool to finish has timed out. LDuplicate items are not allowed. When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename. TThe session name provided is invalid. The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation. The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation. `The execution of the Rules Manager failed. An error occurred while attempting to compress or extract the data. This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel. DThis drive is not encrypted. (The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions. The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions. A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date. The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR). The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR). At least one secure key protector is required for this operation to be performed. BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker. |BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again. `The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed. The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted. 4The 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. The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed. The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access. XThe 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. (The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive. The drive cannot be encrypted because the file system is not supported. The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition. HThis drive cannot be encrypted. 8The data is not valid. The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically. You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption. The operation attempted cannot be performed on an operating system drive. $The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again. A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. One or more BitLocker key protectors are required. You cannot delete the last key on this drive. Cluster configurations are not supported by BitLocker Drive Encryption. The drive specified is already configured to be automatically unlocked on the current computer. The operating system drive is not protected by BitLocker Drive Encryption. BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key. The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive. ,BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive. 8The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again. The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker. The drive encryption algorithm cannot be used on this sector size. The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again. xThe drive specified is not the operating system drive. BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer. The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector. hBitLocker 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. Group Policy settings require that a recovery password be specified before encrypting the drive. The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker. 4BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive. 8BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker. This key protector cannot be added. Only one key protector of this type is allowed for this drive. The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path. The specified key protector was not found on the drive. Try another key protector. The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive. pThe 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. hThe random number generator check test failed. lThe 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. The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration. The drive must be fully decrypted to complete this operation. The key protector specified cannot be used for this operation. No key protectors exist on the drive to perform the hardware test. The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions. \The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again. `The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again. TThe 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. The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes. The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem. The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM). The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN. A boot application has changed since BitLocker Drive Encryption was enabled. The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled. The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information. \This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again. $BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions. $This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system. hBitLocker 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. tThe drive cannot be locked when the drive is in use. The access token associated with the current thread is not an impersonated token. The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available. You must restart your computer before continuing with BitLocker Drive Encryption. Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging. No action was taken as BitLocker Drive Encryption is in raw access mode. BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use. The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again. TBitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments. The auto-unlock master key was not available from the operating system drive. The system firmware failed to enable clearing of system memory when the computer was restarted. TThe hidden drive cannot be encrypted. BitLocker encryption keys were ignored because the drive was in a transient state. Public key based protectors are not allowed on this drive. BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing. This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system. 8The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information. Group Policy settings do not permit the creation of a recovery password. Group Policy settings require the creation of a recovery password. Group Policy settings do not permit the creation of a recovery key. Group Policy settings require the creation of a recovery key. Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option. Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option. Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option. Group Policy settings require the use of a startup key. Please choose this BitLocker startup option. Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option. Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option. Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option. Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option. The PIN provided does not meet minimum or maximum length requirements. 0The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector. Group Policy settings do not permit the creation of a password. |Group Policy settings require the creation of a password. PThe Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information. |A password cannot be added to the operating system drive. The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive. The drive is too small to be protected using BitLocker Drive Encryption. HThe 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. The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go. Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption. Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption. Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption. Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked. Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked. Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives. pGroup 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. lGroup 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. Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization. @Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols. This drive cannot be encrypted because it is reserved for Windows System Recovery Options. dBitLocker 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. tBitLocker 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. The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker. BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker. BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. |BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected. dThe requested virtualization size is too big. @BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. 4BitLocker 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. <BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. (The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement. lThe private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid. Removal of the data recovery agent certificate must be done using the Certificates snap-in. This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the "manage-bde -upgrade" command. $The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive. The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments. 4The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals. pThe requested TPM PIN contains invalid characters. XThe management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version. dThe feature is only supported on EFI systems. More than one Network Key Protector certificate has been found on the system. Removal of the Network Key Protector certificate must be done using the Certificates snap-in. An invalid certificate has been found in the Network Key Protector certificate store. XThis drive isn't protected with a PIN. TPlease enter the correct current PIN. You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator. BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator. Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ . BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. The required authentication key length is not supported by the drive. `This drive isn't protected with a password. `Please enter the correct current password. `The password cannot exceed 256 characters. A password key protector cannot be added because a TPM protector exists on the drive. A TPM key protector cannot be added because a password protector exists on the drive. This command can only be performed from the coordinator node for the specified CSV volume. This command cannot be performed on a volume when it is part of a cluster. BitLocker did not revert to using BitLocker software encryption due to group policy configuration. The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use. Group Policy settings do not allow the use of hardware-based encryption. The drive specified does not support hardware-based encryption. BitLocker cannot be upgraded during disk encryption or decryption. Discovery Volumes are not supported for volumes using hardware encryption. No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume. No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume. Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume. Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume. lWipe of free space is not currently taking place. BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled. BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker. Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. ,BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume. BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker. This PC's firmware is not capable of supporting hardware encryption. BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator. You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator. BitLocker cannot save the recovery password because the specified Microsoft account is Suspended. BitLocker cannot save the recovery password because the specified Microsoft account is Blocked. This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy. This PC cannot support device encryption because unencrypted fixed data volumes are present. This PC does not meet the hardware requirements to support device encryption. This PC cannot support device encryption because WinRE is not properly configured. `Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot. |This PC is not provisioned to support device encryption. Device Lock has been triggered due to too many incorrect password attempts. Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information. hYour PIN can only contain numbers from 0 to 9. BitLocker cannot use hardware replay protection because no counter is available on your PC. Device Lockout state validation failed due to counter mismatch. HThe input buffer is too large. The target of an invocation does not support requested capability. Device encryption is currently blocked by this PC's configuration. pThis drive has been opted out of device encryption. lDevice encryption isn't available for this drive. 8The 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. @Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator. Device encryption can't be turned off while this drive is being encrypted. Please try again later. This action isn't supported because this drive isn't automatically managed with device encryption. BitLocker can't be suspended on this drive until the next restart. The Secure Boot update was not applied due to a known incompatibility with the current BitLocker configuration. @The callout does not exist. TThe filter condition does not exist. @The filter does not exist. <The layer does not exist. DThe provider does not exist. TThe provider context does not exist. DThe sublayer does not exist. @The object does not exist. lAn object with that GUID or LUID already exists. The object is referenced by other objects so cannot be deleted. xThe call is not allowed from within a dynamic session. The call was made from the wrong session so cannot be completed. The call must be made from within an explicit transaction. The call is not allowed from within an explicit transaction. tThe explicit transaction has been forcibly cancelled. HThe session has been cancelled. The call is not allowed from within a read-only transaction. The call timed out while waiting to acquire the transaction lock. tCollection of network diagnostic events is disabled. xThe operation is not supported by the specified layer. lThe call is allowed for kernel-mode callers only. The call tried to associate two objects with incompatible lifetimes. dThe object is built in so cannot be deleted. lThe maximum number of callouts has been reached. A notification could not be delivered because a message queue is at its maximum capacity. The traffic parameters do not match those for the security association context. The call is not allowed for the current security association state. @A required pointer is null. @An enumerator is not valid. `The flags field contains an invalid value. DA network mask is not valid. @An FWP_RANGE is not valid. HThe time interval is not valid. An array that must contain at least one element is zero length. `The displayData.name field cannot be null. The action type is not one of the allowed action types for a filter. HThe filter weight is not valid. A filter condition contains a match type that is not compatible with the operands. An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. hAn integer value is outside the allowed range. DA reserved field is non-zero. A filter cannot contain multiple conditions operating on a single field. A policy cannot contain the same keying module more than once. lThe action type is not compatible with the layer. tThe action type is not compatible with the sublayer. The raw context or the provider context is not compatible with the layer. The raw context or the provider context is not compatible with the callout. The authentication method is not compatible with the policy type. The Diffie-Hellman group is not compatible with the policy type. tAn IKE policy cannot contain an Extended Mode policy. The enumeration template or subscription will never match any objects. `The provider context is of the wrong type. @The parameter is incorrect. lThe maximum number of sublayers has been reached. The notification function for a callout returned an error. lThe IPsec authentication transform is not valid. \The IPsec cipher transform is not valid. The IPsec cipher transform is not compatible with the policy. xThe combination of IPsec transform types is not valid. A policy cannot contain the same auth method more than once. `A tunnel endpoint configuration is invalid. LThe WFP MAC Layers are not ready. A key manager capable of key dictation is already registered PA key manager dictated invalid keys hThe BFE IPsec Connection Tracking is disabled. <The DNS name is invalid. The engine option is still enabled due to other configuration settings. The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. tThe packet should be dropped, no ICMP should be sent. tThe binding to the network interface is being closed. LAn invalid version was specified. `An invalid characteristics table was used. Failed to find the network interface or network interface is not ready. TFailed to open the network interface. Network interface has encountered an internal unrecoverable failure. tThe multicast list on the network interface is full. An attempt was made to add a duplicate multicast address to the list. At attempt was made to remove a multicast address that was never added. XNetowork interface aborted the request. Network interface can not process the request because it is being reset. An attempt was made to send an invalid packet on a network interface. The specified request is not a valid operation for the target device. Network interface is not ready to complete this operation. The length of the buffer submitted for this operation is not valid. hThe data used for this operation is not valid. The length of buffer submitted for this operation is too small. Network interface does not support this OID (Object Identifier) XThe network interface has been removed. pNetwork interface does not support this media type. An attempt was made to remove a token ring group address that is in use by other components. |An attempt was made to map a file that can not be found. pAn error occurred while NDIS tried to map the file. |An attempt was made to map a file that is alreay mapped. An attempt to allocate a hardware resource failed because the resource is used by another component. The I/O operation failed because network media is disconnected or wireless access point is out of range. pThe network address used in the request is invalid. The offload operation on the network interface has been paused. LNetwork interface was not found. The revision number specified in the structure is not supported. The specified port does not exist on this network interface. The current state of the specified port on this network interface does not support the requested operation. `The miniport adapter is in low power state. This operation requires the miniport adapter to be reinitialized. lNetword interface does not support this request. The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. The wireless local area network interface is busy and can not perform the requested operation. The wireless local area network interface is powered down and doesn't support the requested operation. \The list of wake on LAN patterns is full. lThe list of low power protocol offloads is full. 0A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration. The regeneration operation was not able to copy all data from the active plexes due to bad sectors. One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems. Some BCD entries were not imported correctly from the BCD store. Some BCD entries were not synchronized correctly with the firmware. The virtualization storage subsystem has generated an error. DThe operation was cancelled. pAn error occurred when running a PowerShell script. An error occurred when interacting with PowerShell runtime. An error occurred in the Scripted Diagnostic Managed Host. The troubleshooting pack does not contain a required verifier to complete the verification. lScripted diagnostics is disabled by group policy. tTrust validation of the troubleshooting pack failed. The troubleshooting pack cannot be executed on this system. This version of the troubleshooting pack is not supported. TA required resource cannot be loaded. The troubleshooting pack reported information for a root cause without adding the root cause. The input data was not in the expected format or did not have the expected value. The operation could not be completed because the object is in a faulted state due to a previous error. The operation could not be completed because it would lead to numeric overflow. The operation is not allowed due to the current state of the object. @The operation was aborted. \Access was denied by the remote endpoint. |The operation did not complete within the time allotted. DThe operation was abandoned. 4A quota was exceeded. The information was not available in the specified language. Security verification was not successful for the received data. PThe address is already being used. `The address is not valid for this context. The remote endpoint does not exist or could not be located. The remote endpoint is not currently in service at this location. pThe remote endpoint could not process the request. XThe remote endpoint was not reachable. xThe operation was not supported by the remote endpoint. The remote endpoint is unable to process the request due to being overloaded. A message containing a fault was received from the remote endpoint. xThe connection with the remote endpoint was terminated. tThe HTTP proxy server could not process the request. `Access was denied by the HTTP proxy server. |The requested feature is not available on this platform. The HTTP proxy server requires HTTP authentication scheme 'basic'. The HTTP proxy server requires HTTP authentication scheme 'digest'. The HTTP proxy server requires HTTP authentication scheme 'NTLM'. The HTTP proxy server requires HTTP authentication scheme 'negotiate'. The remote endpoint requires HTTP authentication scheme 'basic'. The remote endpoint requires HTTP authentication scheme 'digest'. The remote endpoint requires HTTP authentication scheme 'NTLM'. The remote endpoint requires HTTP authentication scheme 'negotiate'. TThe endpoint address URL is invalid. Unrecognized error occurred in the Windows Web Services framework. A security token was rejected by the server because it has expired. A security operation failed in the Windows Web Services framework. lThe notification channel has already been closed. The notification channel request did not complete successfully. hThe application identifier provided is invalid. A notification channel request for the provided application identifier is in progress. The channel identifier is already tied to another application endpoint. \The notification platform is unavailable. \The notification has already been posted. \The notification has already been hidden. The notification cannot be hidden until it has been shown. \Cloud notifications have been turned off. The application does not have the cloud notification capability. xSettings prevent the notification from being delivered. Application capabilities prevent the notification from being delivered. The application does not have the internet access capability. Settings prevent the notification type from being delivered. pThe size of the notification content is too large. hThe size of the notification tag is too large. The notification platform doesn't have appropriate privilege on resources. The notification platform found application is already registered. The application background task does not have the push notification capability. The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. The notification platform is unable to connect to the cloud notification service. The notification platform is unable to initialize a callback for lock screen updates. The size of the developer id for scheduled notification is too large. \The notification tag is not alphanumeric. The notification platform has received invalid HTTP status code other than 2xx for polling. The notification platform has run out of presentation layer sessions. The notification platform rejects image download request due to system in power save mode. The notification platform doesn't have the requested image in its cache. The notification platform cannot complete all of requested image. A cloud image downloaded from the notification platform is invalid. Notification Id provided as filter is matched with what the notification platform maintains. xNotification callback interface is already registered. Toast Notification was dropped without being displayed to the user. The notification platform does not have the proper privileges to complete the request. Input data cannot be processed in the non-chronological order. Requested operation cannot be performed inside the callback or event handler. Input cannot be processed because there is ongoing interaction with another pointer type. pOne or more fields in the input packet are invalid. DPackets 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. 0The 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. xFailed to retrieve information about the input device. Coordinate system transformation failed to transform the data. The property is not supported or not reported correctly by the input device. <Context is not activated. 4Bad SIM is inserted. XRequested data class is not avaialable. xAccess point name (APN) or Access string is incorrect. TMax activated contexts have reached. LDevice is in packet detach state. <Provider is not visible. 4Radio is powered off. PMBN subscription is not activated. 4SIM is not inserted. 8Voice call in progress. PVisible provider cache is invalid. <Device is not registered. 4Providers not found. 4Pin is not supported. ,Pin is required. ,PIN is disabled. ,Generic Failure. 0Profile is invalid. 8Default profile exist. HSMS encoding is not supported. DSMS filter is not supported. LInvalid SMS memory index is used. HSMS language is not supported. DSMS memory failure occurred. DSMS network timeout happened. DUnknown SMSC address is used. DSMS format is not supported. DSMS operation is not allowed. @Device SMS memory is full. Windows cannot evaluate this EAS policy since this is not managed by the operating system. The system can be made compliant to this EAS policy if certain actions are performed by the user. The EAS policy being evaluated cannot be enforced by the system. EAS password policies for the user cannot be evaluated as the user has a blank password. ,EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system. hThe user is not allowed to change her password. EAS password policies cannot be evaluated as one or more admins have blank passwords. One or more admins are not allowed to change their password. There are other standard users present who are not allowed to change their password. The EAS password policy cannot be enforced by the connected account provider of at least one administrator. There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance. The EAS password policy cannot be enforced by the connected account provider of the current user. The connected account password of the current user needs to be changed for EAS password policy compliance. PThe IPv6 protocol is not installed. XThe compoment has not been initialized. XThe required service canot be started. pThe P2P protocol is not licensed to run on this OS. DThe graph handle is invalid. TThe graph database name has changed. \A graph with the same ID already exists. 8The graph is not ready. @The graph is shutting down. @The graph is still in use. HThe graph database is corrupt. PToo many attributes have been used. LThe connection can not be found. \The peer attempted to connect to itself. hThe peer is already listening for connections. 8The node was not found. HThe Connection attempt failed. hThe peer connection could not be authenticated. @The connection was refused. TThe peer name classifier is too long. pThe maximum number of identities have been created. 8Unable to access a key. <The group already exists. \The requested record could not be found. PAccess to the database was denied. XThe Database could not be initialized. 8The record is too big. DThe database already exists. LThe database could not be found. LThe identity could not be found. TThe event handle could not be found. (Invalid search. LThe search atributes are invalid. HThe invitiation is not trusted. @The certchain is too long. @The time period is invalid. PA circular cert chain was detected. @The certstore is corrupted. \The specified PNRP cloud deos not exist. DThe cloud name is ambiguous. 8The record is invlaid. (Not authorized. hThe password does not meet policy requirements. XThe record validation has been defered. LThe group properies are invalid. <The peername is invalid. @The classifier is invalid. DThe friendly name is invalid. 8Invalid role property. @Invalid classifer property. @Invlaid record expiration. <Invlaid credential info. 0Invalid credential. 4Invalid record size. 4Unsupported version. 8The group is not ready. @The group is still in use. 4The group is invalid. 8No members were found. LThere are no member connections. ,Unable to listen. DThe identity does not exist. DThe service is not availible. xThe peername could not be converted to a DNS pnrp name. 8Invalid peer host name. DNo more data could be found. dThe existing peer name is already registered. HTHe contact could not be found. lThe app invite request was cancelled by the user. XNo response of the invite was received. dUser is not signed into serverless presence. dThe user declined the privacy policy prompt. 0A timeout occurred. 8The address is invalid. `A required firewall exception is disabled. dThe service is blocked by a firewall policy. LFirewall exceptions are disabled. tThe user declined to enable the firewall exceptions. |The attribute handle given was not valid on this server. DThe attribute cannot be read. LThe attribute cannot be written. HThe attribute PDU was invalid. The attribute requires authentication before it can be read or written. Attribute server does not support the request received from the client. pOffset specified was past the end of the attribute. The attribute requires authorization before it can be read or written. \Too many prepare writes have been queued. No attribute found within the given attribute handle range. The attribute cannot be read or written using the Read Blob Request. The Encryption Key Size used for encrypting this link is insufficient. |The attribute value length is invalid for the operation. The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. The attribute requires encryption before it can be read or written. The attribute type is not a supported grouping attribute as defined by a higher layer specification. hInsufficient Resources to complete the request. An error that lies in the reserved range has been received. PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. HD Audio widget encountered an unexpected empty connection list. HD Audio widget does not support the connection list parameter. lNo HD Audio subdevices were successfully created. An unexpected NULL pointer was encountered in a linked list. The bootfile is too small to support persistent snapshots. tThe specified volume does not support storage tiers. The Storage Tiers Management service detected that the specified volume is in the process of being dismounted. The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid. |The file identifier specified is not valid on the volume. Storage tier operations must be called on the clustering node that owns the metadata volume. The Storage Tiers Management service is already optimizing the storage tiers on the specified volume. The requested object type cannot be assigned to a storage tier. Authentication target is invalid or not configured correctly. Your application cannot get the Online Id properties due to the Terms of Use accepted by the user. The application requesting authentication tokens is either disabled or incorrectly configured. lOnline Id password must be updated before signin. Online Id account properties must be updated before signin. To help protect your Online Id account you must signin again. Online Id account was locked because there have been too many attempts to sign in. Online Id account requires parental consent before proceeding. Online Id signin name is not yet verified. Email verification is required before signin. We have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account. We detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account. lUser interaction is required for authentication. User has reached the maximum device associations per user limit. Cannot sign out from the application since the user account is connected. pUser authentication is required for this operation. We want to make sure this is you. User interaction is required for authentication. Could not create new process from ARM architecture device. Could not attach to the application process from ARM architecture device. Could not connect to dbgsrv server from ARM architecture device. Could not start dbgsrv server from ARM architecture device. `The specified resiliency type is not valid. The physical disk's sector size is not supported by the storage pool. The requested redundancy is outside of the supported range of values. The number of data copies requested is outside of the supported range of values. The value for ParityLayout is outside of the supported range of values. The value for interleave length is outside of the supported range of values. The number of columns specified is outside of the supported range of values. There were not enough physical disks to complete the requested operation. 0Unsupported format. $Invalid XML. <Missing required element. @Missing required attribute. 0Unexpected content. 0Resource too large. 4Invalid JSON string. 4Invalid JSON number. 4JSON value not found. dInvalid operation performed by the protocol. |Invalid data format for the specific protocol operation. XProtocol extensions are not supported. DSubrotocol is not supported. @Incorrect protocol version. |One or more fixed volumes are not provisioned with the 3rd party encryption providers to support device encryption. Enable encryption with the 3rd party provider to comply with policy. This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption. This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider. This computer cannot support device encryption because the requisites for the device lock feature are not configured. Protection is enabled on this volume but is not in the active state. The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated. The operating system drive is not protected by 3rd party drive encryption. Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin. The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large. The file size is larger than supported by the sync engine. The file cannot be uploaded because it doesn't fit in the user's available service provided storage space. `The file name contains invalid characters. The maximum file count has been reached for this folder in the sync engine. The file sync has been delegated to another program and has run into an issue. Sync has been delayed due to a throttling request from the service. |We can't seem to find that file. Please try again later. The account you're signed in with doesn't have permission to open this file. There was a problem connecting to the service. Please try again later. lSorry, there was a problem downloading the file. We're having trouble downloading the file right now. Please try again later. We're having trouble downloading the file right now. Please try again later. The sync engine does not have permissions to access a local folder under the sync root. dThe folder name contains invalid characters. The sync engine is not allowed to run in your current market. All files and folders can't be uploaded because a path of a file or folder is too long. All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit. pUpdates are needed in order to use the sync engine. The sync engine needs to authenticate with a proxy server. There was a problem setting up the storage services for the account. Files can't be uploaded because there's an unsupported reparse point. The service has blocked your account from accessing the storage service. The action can't be performed right now because this folder is being moved. Please try again later. (The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1. LThe specified file was not found. The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect. Enable the D3D debug layer in order to see details via debug messages. The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal. xThe caller did not supply a sufficiently large buffer. The specified device interface or feature level is not supported on this system. The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. tThe 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. The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled. An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should be considered invalid. Fullscreen mode could not be achieved because the specified output was already in use. PAn internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect, and the application should not continue. A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time. A resource is not available at the time of the call, but may become available later. The application's remote device has been removed due to session disconnect or network disconnect. The application should call IDXGIFactory1::IsCurrent to find out when the remote device becomes available again. The device has been removed during a remote session because the remote computer ran out of memory. An on-going mode change prevented completion of the call. The call may succeed if attempted later. HThe keyed mutex was abandoned. The timeout value has elapsed and the resource is not yet available. xThe 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. The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed. DXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver, or by the application using a swapchain that is incompatible with content protection. The application is trying to use a resource to which it does not have the required access privileges. This is most commonly caused by writing to a shared resource with read-only access. The application is trying to create a shared handle using a name that is already associated with some other resource. The application requested an operation that depends on an SDK component that is missing or mismatched. pThe GPU was busy when the operation was requested. xThe driver has rejected the creation of this resource. The GPU counter was in use by another process or d3d device when application requested access to it. (The application has exceeded the maximum number of unique state objects per Direct3D device. The limit is 4096 for feature levels up to 11.1. LThe specified file was not found. $The application has exceeded the maximum number of unique view objects per Direct3D device. The limit is 2^20 for feature levels up to 11.1. The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD. ,MILERR_OBJECTBUSY <MILERR_INSUFFICIENTBUFFER ,MILERR_WIN32ERROR 4MILERR_SCANNER_FAILED <MILERR_SCREENACCESSDENIED @MILERR_DISPLAYSTATEINVALID @MILERR_NONINVERTIBLEMATRIX ,MILERR_ZEROVECTOR ,MILERR_TERMINATED ,MILERR_BADNUMBER An internal error (MIL bug) occurred. On checked builds, an assert would be raised. The display format we need to render is not supported by the hardware device. LA call to this method is invalid. `Lock attempted on an already locked object. XUnlock attempted on an unlocked object. xNo algorithm avaliable to render text with this device Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache. xSome glyph bitmaps in glyph cache are unexpectedly big. Marker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred, but still unwind the stack in the correct location. Guideline coordinates are not sorted properly or contain NaNs. xNo HW rendering device is available for this operation. dThere 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 \The object has already been initialized. |The size of the object does not match the expected size. LNo Redirection surface available. `Remoting of this content is not supported. PQueued Presents are not supported. PQueued Presents are not being used. No redirection surface was available. Caller should retry the call. xShader construction failed because it was too complex. XMROW attempt to get a read lock failed. MROW attempt to update the data failed because another update was outstanding. @Shader compilation failed. Requested DX redirection surface size exceeded maximum texture size. tQueryPerformanceCounter returned a time in the past. |Primary Display device returned an invalid refresh rate. pDWM can not find the adapter specified by the LUID. pThe requested bitmap color space is not supported. The requested bitmap pre-filtering state is not supported. Access is denied to the requested bitmap for the specified display id. @UCEERR_INVALIDPACKETHEADER 4UCEERR_UNKNOWNPACKET 4UCEERR_ILLEGALPACKET 8UCEERR_MALFORMEDPACKET 4UCEERR_ILLEGALHANDLE <UCEERR_HANDLELOOKUPFAILED @UCEERR_RENDERTHREADFAILURE DUCEERR_CTXSTACKFRSTTARGETNULL HUCEERR_CONNECTIONIDLOOKUPFAILED ,UCEERR_BLOCKSFULL 4UCEERR_MEMORYFAILURE DUCEERR_PACKETRECORDOUTOFRANGE <UCEERR_ILLEGALRECORDTYPE 0UCEERR_OUTOFHANDLES PUCEERR_UNCHANGABLE_UPDATE_ATTEMPTED LUCEERR_NO_MULTIPLE_WORKER_THREADS @UCEERR_REMOTINGNOTSUPPORTED <UCEERR_MISSINGENDCOMMAND @UCEERR_MISSINGBEGINCOMMAND @UCEERR_CHANNELSYNCTIMEDOUT @UCEERR_CHANNELSYNCABANDONED PUCEERR_UNSUPPORTEDTRANSPORTVERSION @UCEERR_TRANSPORTUNAVAILABLE @UCEERR_FEEDBACK_UNSUPPORTED DUCEERR_COMMANDTRANSPORTDENIED LUCEERR_GRAPHICSSTREAMUNAVAILABLE LUCEERR_GRAPHICSSTREAMALREADYOPEN DUCEERR_TRANSPORTDISCONNECTED @UCEERR_TRANSPORTOVERLOADED <UCEERR_PARTITION_ZOMBIED ,MILAVERR_NOCLOCK 4MILAVERR_NOMEDIATYPE 4MILAVERR_NOVIDEOMIXER <MILAVERR_NOVIDEOPRESENTER 8MILAVERR_NOREADYFRAMES <MILAVERR_MODULENOTLOADED LMILAVERR_WMPFACTORYNOTREGISTERED @MILAVERR_INVALIDWMPVERSION PMILAVERR_INSUFFICIENTVIDEORESOURCES XMILAVERR_VIDEOACCELERATIONNOTAVAILABLE HMILAVERR_REQUESTEDTEXTURETOOBIG 0MILAVERR_SEEKFAILED DMILAVERR_UNEXPECTEDWMPFAILURE @MILAVERR_MEDIAPLAYERCLOSED DMILAVERR_UNKNOWNHARDWAREERROR DMILEFFECTSERR_UNKNOWNPROPERTY PMILEFFECTSERR_EFFECTNOTPARTOFGROUP PMILEFFECTSERR_NOINPUTSOURCEATTACHED PMILEFFECTSERR_CONNECTORNOTCONNECTED hMILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT 8MILEFFECTSERR_RESERVED @MILEFFECTSERR_CYCLEDETECTED XMILEFFECTSERR_EFFECTINMORETHANONEGRAPH PMILEFFECTSERR_EFFECTALREADYINAGRAPH LMILEFFECTSERR_EFFECTHASNOCHILDREN XMILEFFECTSERR_ALREADYATTACHEDTOLISTENER LMILEFFECTSERR_NOTAFFINETRANSFORM <MILEFFECTSERR_EMPTYBOUNDS LMILEFFECTSERR_OUTPUTSIZETOOLARGE HDWMERR_STATE_TRANSITION_FAILED 0DWMERR_THEME_FAILED @DWMERR_CATASTROPHIC_FAILURE `DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED \DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED dDCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED LThe codec is in the wrong state. @The value is out of range. DThe image format is unknown. HThe SDK version is unsupported. LThe component is not initialized. pThere is already an outstanding read or write lock. hThe specified bitmap property cannot be found. xThe bitmap codec does not support the bitmap property. TThe bitmap property size is invalid. HAn unknown error has occurred. hThe bitmap codec does not support a thumbnail. PThe bitmap palette is unavailable. PToo many scanlines were requested. @An internal error occurred. tThe bitmap bounds do not match the bitmap dimensions. HThe component cannot be found. `The bitmap size is outside the valid range. xThere is too much metadata to be written to the bitmap. @The image is unrecognized. LThe image header is unrecognized. DThe bitmap frame is missing. `The image metadata header is unrecognized. LThe stream data is unrecognized. HFailed to write to the stream. HFailed to read from the stream. DThe stream is not available. XThe bitmap pixel format is unsupported. DThe operation is unsupported. XThe component registration is invalid. \The component initialization has failed. TThe buffer allocated is insufficient. HDuplicate metadata is present. XThe bitmap property type is unexpected. 8The size is unexpected. HThe property query is invalid. LThe metadata type is unexpected. The specified bitmap property is only valid at root level. hThe query string contains an invalid character. xWindows Codecs received an error from the Win32 system. dThe requested level of detail is not present. |Indicates an error in an input file such as a font file. Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from. dIndicates the specified font does not exist. ,A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable. A font file exists but could not be opened due to access denied, sharing violation, or similar error. A font collection is obsolete due to changes in the system. `The given interface is already registered. TThe font cache contains invalid data. A font cache file corresponds to a different version of DirectWrite. tThe operation is not supported for this type of font. The version of the text renderer interface is not compatible. The flow direction conflicts with the reading direction. They must be perpendicular to each other. The font or glyph run does not contain any colored glyphs. The object was not in the correct state to process the method. \The object has not yet been initialized. \The requested operation is not supported. lThe geometry scanner failed to process the data. TDirect2D could not access the screen. hA valid display state could not be determined. DThe supplied vector is zero. lAn 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. The display format Direct2D needs to render is not supported by the hardware device. LA call to this method is invalid. No hardware rendering device is available for this operation. $There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. xShader construction failed because it was too complex. @Shader compilation failed. Requested DirectX surface size exceeded maximum texture size. lThe requested Direct2D version is not supported. (Invalid number. Objects used together must be created from the same factory instance. A layer resource can only be in use once at any point in time. xThe pop call did not match the corresponding push call. tThe resource was realized on the wrong render target. XThe push and pop calls were unbalanced. Attempt to copy from a render target while a layer or clip rect is applied. hThe brush types are incompatible for the call. PAn unknown win32 failure occurred. dThe render target is not compatible with GDI. |A text client drawing effect object is of the wrong type. The application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid. The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level. dThere was a configuration error in the graph. xThere was a internal configuration error in the graph. HThere was a cycle in the graph. Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option. The operation cannot complete while there are outstanding references to the target bitmap. The operation failed because the original target is not currently bound as a target. Cannot set the image as a target because it is either an effect or is a bitmap that does not have the D2D1_BITMAP_OPTIONS_TARGET flag set. Cannot draw with a bitmap that is currently bound as the target bitmap. D3D Device does not have sufficient capabilities to perform the requested action. The graph could not be rendered with the context's current tiling settings. The CLSID provided to Unregister did not correspond to a registered effect. XThe specified property does not exist. `The specified sub-property does not exist. AddPage or Close called after print job is already closed. DError during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control. An effect attempted to use a transform with too many inputs. The operation was preempted by a higher priority operation. It must be resumed later. Function could not execute because it was deleted or garbage collected. pThe specified event is currently not being audited. dThe SID filtering operation removed all SIDs. Business rule scripts are disabled for the calling application. The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote. xChecksum of the obtained monitor descriptor is invalid. Monitor descriptor contains an invalid standard timing block. WMI data block registration failed for one of the MSMonitorClass WMI subclasses. Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. There is no monitor descriptor data at the specified (offset, size) region. Monitor descriptor contains an invalid detailed timing block. tMonitor descriptor contains invalid manufacture date. Exclusive mode ownership is needed to create unmanaged primary allocation. The driver needs more DMA buffer space in order to complete the requested operation. dSpecified display adapter handle is invalid. Specified display adapter and all of its state has been reset. |The driver stack doesn't match the expected driver model. Present happened but ended up into the changed desktop mode `Nothing to present due to desktop occlusion pNot able to present due to denial of desktop access \Not able to present with color convertion The kernel driver detected a version mismatch between it and the user mode driver. Present redirection is disabled (desktop windowing management subsystem is off). Previous exclusive VidPn source owner has released its ownership `Window DC is not available for presentation Windowless present is disabled (desktop windowing management subsystem is off). Not enough video memory available to complete the operation. Couldn't probe and lock the underlying memory of an allocation. LThe allocation is currently busy. An object being referenced has reach the maximum reference count already and can't be reference further. A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. @The allocation is invalid. tNo more unswizzling aperture are currently available. The current allocation can't be unswizzled by an aperture. The request failed because a pinned allocation can't be evicted. The allocation can't be used from its current segment location for the specified operation. A locked allocation can't be used in the current command buffer. The allocation being referenced has been closed permanently. pAn invalid allocation instance is being referenced. lAn invalid allocation handle is being referenced. The allocation being referenced doesn't belong to the current device. `The specified allocation lost its content. GPU exception is detected on the given device. The device is not able to be scheduled. TSpecified VidPN topology is invalid. Specified VidPN topology is valid but is not supported by this model of the display adapter. Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. PSpecified VidPN handle is invalid. `Specified video present source is invalid. `Specified video present target is invalid. Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). `Specified VidPN source mode set is invalid. `Specified VidPN target mode set is invalid. dSpecified video signal frequency is invalid. lSpecified video signal active region is invalid. hSpecified video signal total region is invalid. hSpecified video present source mode is invalid. hSpecified video present target mode is invalid. Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. Specified video present path is already in VidPN's topology. `Specified mode is already in the mode set. hSpecified video present source set is invalid. hSpecified video present target set is invalid. Specified video present source is already in the video present source set. Specified video present target is already in the video present target set. \Specified VidPN present path is invalid. Miniport has no recommendation for augmentation of the specified VidPN's topology. lSpecified monitor frequency range set is invalid. dSpecified monitor frequency range is invalid. Specified frequency range is not in the specified monitor frequency range set. Specified frequency range is already in the specified monitor frequency range set. Specified mode set is stale. Please reacquire the new mode set. dSpecified monitor source mode set is invalid. \Specified monitor source mode is invalid. (Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. ID of the specified mode is already used by another mode in the set. System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. Number of video present targets must be greater than or equal to the number of video present sources. pSpecified present path is not in VidPN's topology. Display adapter must have at least one video present source. Display adapter must have at least one video present target. dSpecified monitor descriptor set is invalid. \Specified monitor descriptor is invalid. Specified descriptor is not in the specified monitor descriptor set. Specified descriptor is already in the specified monitor descriptor set. ID of the specified monitor descriptor is already used by another descriptor in the set. xSpecified video present target subset type is invalid. Two or more of the specified resources are not related to each other, as defined by the interface semantics. ID of the specified video present source is already used by another source in the set. ID of the specified video present target is already used by another target in the set. Specified VidPN source cannot be used because there is no available VidPN target to connect it to. Newly arrived monitor could not be associated with a display adapter. Display adapter in question does not have an associated VidPN manager. VidPN manager of the display adapter in question does not have an active VidPN. Specified VidPN topology is stale. Please reacquire the new topology. There is no monitor connected on the specified video present target. Specified source is not part of the specified VidPN's topology. `Specified primary surface size is invalid. \Specified visible region size is invalid. DSpecified stride is invalid. PSpecified pixel format is invalid. LSpecified color basis is invalid. dSpecified pixel value access mode is invalid. Specified target is not part of the specified VidPN's topology. tFailed to acquire display mode management interface. Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. lSpecified VidPN is active and cannot be accessed. Specified VidPN present path importance ordinal is invalid. Specified VidPN present path content geometry transformation is invalid. Specified content geometry transformation is not supported on the respective VidPN present path. LSpecified gamma ramp is invalid. Specified gamma ramp is not supported on the respective VidPN present path. Multi-sampling is not supported on the respective VidPN present path. lSpecified mode is not in the specified mode set. Specified VidPN topology recommendation reason is invalid. tSpecified VidPN present path content type is invalid. Specified VidPN present path copy protection type is invalid. No more than one unassigned mode set can exist at any given time for a given VidPN source/target. dSpecified scanline ordering type is invalid. |Topology changes are not allowed for the specified VidPN. All available importance ordinals are already used in specified topology. Specified primary surface has a different private format attribute than the current primary surface `Specified mode pruning algorithm is invalid hSpecified monitor capability origin is invalid. |Specified monitor frequency range constraint is invalid. Maximum supported number of present paths has been reached. Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. \Specified client type was not recognized. Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). Specified display adapter child device already has an external device connected to it. Specified display adapter child device does not support descriptor exposure. |The display adapter is not linked to any other adapters. Lead adapter in a linked configuration was not enumerated yet. Some chain adapters in a linked configuration were not enumerated yet. The chain of linked adapters is not ready to start because of an unknown failure. An attempt was made to start a lead link display adapter when the chain links were not started yet. An attempt was made to power up a lead link display adapter when the chain links were powered down. The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. The driver trying to start is not the same as the driver for the POSTed display adapter. An operation is being attempted that requires the display adapter to be in a quiescent state. LThe driver does not support OPM. LThe driver does not support COPP. LThe driver does not support UAB. hThe specified encrypted parameters are invalid. The GDI display device passed to this function does not have any active video outputs. lAn internal error caused this operation to fail. The function failed because the caller passed in an invalid OPM user mode handle. A certificate could not be returned because the certificate buffer passed to the function was too small. A video output could not be created because the frame buffer is in spanning mode. A video output could not be created because the frame buffer is in theater mode. The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification. The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. 0The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. \The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output. 0The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high. 4The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. The operating system asynchronously destroyed this OPM 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. The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote. Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only. The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid. The method failed because an unexpected error occurred inside of a display driver. Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only. The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs. dThe 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. The monitor connected to the specified video output does not have an I2C bus. pNo device on the I2C bus has the specified address. An error occurred while transmitting data to the device on the I2C bus. An error occurred while receiving data from the device on the I2C bus. tThe monitor does not support the specified VCP code. hThe data received from the monitor is invalid. The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor. (The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification. tAn internal Monitor Configuration API error occurred. An operation failed because a DDC/CI message had an invalid value in its command field. An error occurred because the field length of a DDC/CI message contained an invalid value. An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer. This function failed because an invalid monitor handle was passed to it. TThe operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications. $A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value. The monitor's VCP Version (0xDF) VCP code returned an invalid version value. The monitor does not comply with the MCCS specification it claims to support. 4The 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. LThe 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. The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session. This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. The function failed because the specified GDI display device was not attached to the Windows desktop. @This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned. The function failed because the specified GDI device did not have any monitors associated with it. An array passed to the function cannot hold all of the data that the function must copy into the array. hAn internal error caused an operation to fail. The TCP connection is not offloadable because of a local policy setting. The TCP connection is not offloadable by the Chimney Offload target. pThe IP Path object is not in an offloadable state. The hypervisor does not support the operation because the specified hypercall code is not supported. The hypervisor does not support the operation because the encoding for the hypercall input register is not supported. The hypervisor could not perform the operation beacuse a parameter has an invalid alignment. The hypervisor could not perform the operation beacuse an invalid parameter was specified. `Access to the specified object was denied. The hypervisor could not perform the operation because the partition is entering or in an invalid state. pThe operation is not allowed in the current state. The hypervisor does not recognize the specified partition property. The specified value of a partition property is out of range or violates an invariant. There is not enough memory in the hypervisor pool to complete the operation. The maximum partition depth has been exceeded for the partition hierarchy. A partition with the specified partition Id does not exist. The hypervisor could not perform the operation because the specified VP index is invalid. The hypervisor could not perform the operation because the specified port identifier is invalid. The hypervisor could not perform the operation because the specified connection identifier is invalid. pNot enough buffers were supplied to send a message. |The previous virtual interrupt has not been acknowledged. The previous virtual interrupt has already been acknowledged. The indicated partition is not in a valid state for saving or restoring. The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled. lThe hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation. dThe proximity domain information is invalid. An attempt to retrieve debugging data failed because none was available. The physical connection being used for debuggging has not recorded any receive activity since the last operation. |There are not enough resources to complete the operation. pA hypervisor feature is not available to the user. The specified buffer was too small to contain all of the requested data. TThe maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition. The hypervisor could not perform the operation because the specified LP index is invalid. \No hypervisor is present on this system. The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The partition name of the virtualization infrastructure driver exceeds the maximum. The message queue name of the virtualization infrastructure driver exceeds the maximum. Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists. The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. A message queue with the same name already exists for the virtualization infrastructure driver. The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed. Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. lThe non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration. The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology. The memory block for the virtualization infrastructure driver is already associated with a message queue. The handle is not a valid memory block handle for the virtualization infrastructure driver. The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The handle is not a valid message queue handle for the virtualization infrastructure driver. The handle is not a valid page range handle for the virtualization infrastructure driver. (Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block. The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver. Notifications cannot be created on the memory block because it is use. The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. Cannot add a virtual processor to the partition because the maximum has been reached. Cannot stop the virtual processor immediately because of a pending intercept. @Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. hThe memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. 8Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. dCannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine. TCannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine. PThe configuration database is full. lThe configuration data on the disk is corrupted. The configuration on the disk is not insync with the in-memory configuration. A majority of disks failed to be updated with the new configuration. TThe disk contains non-simple volumes. The same disk was specified more than once in the migration list. DThe disk is already dynamic. The specified disk id is invalid. There are no disks with the specified disk id. The specified disk is an invalid disk. Operation cannot complete on an invalid disk. The specified disk(s) cannot be removed since it is the last remaining voter. hThe specified disk has an invalid disk layout. The disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout. The disk layout contains partitions which are not cylinder aligned. The disk layout contains partitions which are samller than the minimum size. The disk layout contains primary partitions in between logical drives. This is an invalid disk layout. The disk layout contains more than the maximum number of supported partitions. The specified disk is missing. The operation cannot complete on a missing disk. LThe specified disk is not empty. tThere is not enough usable space for this operation. dThe force revectoring of bad sectors failed. hThe specified disk has an invalid sector size. The specified disk set contains volumes which exist on disks outside of the set. A disk in the volume layout provides extents to more than one member of a plex. A disk in the volume layout provides extents to more than one plex. hDynamic disks are not supported on this system. xThe specified extent is already used by other volumes. \The specified volume is retained and can only be extended into a contiguous extent. The specified extent to grow the volume is not contiguous with the specified volume. The specified volume extent is not within the public region of the disk. lThe specifed volume extent is not sector aligned. The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks). The specified extent lengths cannot be used to construct a volume with specified length. pThe system does not support fault tolerant volumes. `The specified interleave length is invalid. xThere is already a maximum number of registered users. The specified member is already in-sync with the other active members. It does not need to be regenerated. pThe same member index was specified more than once. The specified member index is greater or equal than the number of members in the volume plex. The specified member is missing. It cannot be regenerated. The specified member is not detached. Cannot replace a member which is not detached. dThe specified member is already regenerating. XAll disks belonging to the pack failed. There are currently no registered users for notifications. The task number is irrelevant unless there are registered users. The specified notification user does not exist. Failed to unregister user for notifications. The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications. `The specified number of members is invalid. `The specified number of plexes is invalid. tThe specified source and target packs are identical. The specified pack id is invalid. There are no packs with the specified pack id. The specified pack is the invalid pack. The operation cannot complete with the invalid pack. PThe specified pack name is invalid. HThe specified pack is offline. |The specified pack already has a quorum of healthy disks. lThe pack does not have a quorum of healthy disks. The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported. dFailed to update the disk's partition layout. The specified plex is already in-sync with the other active plexes. It does not need to be regenerated. lThe same plex index was specified more than once. The specified plex index is greater or equal than the number of plexes in the volume. The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. HThe specified plex is missing. dThe specified plex is currently regenerating. PThe specified plex type is invalid. lThe operation is only supported on RAID-5 plexes. lThe operation is only supported on simple plexes. The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set. There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications. dThere is currently a transaction in process. An unexpected layout change occurred outside of the volume manager. dThe specified volume contains a missing disk. The specified volume id is invalid. There are no volumes with the specified volume id. XThe specified volume length is invalid. The specified size for the volume is not a multiple of the sector size. tThe operation is only supported on mirrored volumes. xThe specified volume does not have a retain partition. LThe specified volume is offline. tThe specified volume already has a retain partition. `The specified number of extents is invalid. All disks participating to the volume must have the same sector size. PThe boot disk experienced failures. \The configuration of the pack is offline. \The configuration of the pack is online. `The specified pack is not the primary pack. All disks failed to be updated with the new content of the log. pThe specified number of disks in a plex is invalid. The specified number of disks in a plex member is invalid. pThe operation is not supported on mirrored volumes. The operation is only supported on simple and spanned plexes. LThe pack has no valid log copies. PA primary pack is already present. \The specified number of disks is invalid. dThe system does not support mirrored volumes. `The system does not support RAID-5 volumes. xEntries enumerated have exceeded the allowed threshold. The virtual hard disk is corrupted. The virtual hard disk drive footer is missing. The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum. The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted. The system does not recognize the file format of this virtual hard disk. The version does not support this version of the file format. The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum. The system does not support this version of the virtual hard disk.This version of the sparse header is not supported. The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt. Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt. The system does not support this version of the virtual hard disk. The block size is invalid. The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk. The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. 4The chain of virtual hard disks is corrupted. The time stamp of the parent virtual hard disk does not match the time stamp of the differencing disk. tFailed to read the metadata of the virtual hard disk. |Failed to write to the metadata of the virtual hard disk. hThe size of the virtual hard disk is not valid. tThe file size of this virtual hard disk is not valid. A virtual disk support provider for the specified file was not found. \The specified disk is not a virtual disk. @The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk. $The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. The 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. The requested operation cannot be performed on a virtual disk of this type. The requested operation cannot be performed on the virtual disk in its current state. The sector size of the physical disk on which the virtual disk resides is not supported. hThe disk is already owned by a different owner. XThe disk must be offline or read-only. |Change Tracking is not initialized for this virtual disk. Size of change tracking file exceeded the maximum size limit. VHD file is changed due to compaction, expansion, or offline updates. HChange Tracking for the virtual disk is not in a valid state to perform this request. Change tracking could be discontinued or already in the requested state. Change Tracking file for the virtual disk is not in a valid state. The requested resize operation could not be completed because it might truncate user data residing on the virtual disk. hThe 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. The requested operation could not be completed because the virtual disk's size cannot be safely reduced further. There is not enough space in the virtual disk file for the provided metadata item. The proper error code with sense data was stored on server side. |The requested error data is not available on the server. Unit Attention data is available for the initiator to query. The data capacity of the device has changed, resulting in a Unit Attention condition. A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. The data storage format of the device has changed, resulting in a Unit Attention condition. The current initiator is not allowed to perform the SCSI command because of a reservation conflict. Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks. |The server version does not match the requested version. The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. 4VS_VERSION_INFOnO%nO%?2StringFileInfo040904B0LCompanyNameMicrosoft CorporationfFileDescriptionWindows NT BASE API Client DLL1FileVersion6.3.9600.20334 (winblue_ltsb_escrow.220324-1651)>InternalNameKernelbase.dll.LegalCopyright Microsoft Corporation. All rights reserved.NOriginalFilenameKernelbase.dll.muij%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.20334DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD