MZÿÿ¸@¸º´ Í!¸LÍ!This program cannot be run in DOS mode. $ÑRØ•3}‹•3}‹•3}‹HÌ´‹”3}‹H̱‹”3}‹Rich•3}‹PELà!  ^ p n» @@\ .rsrc` ^ @@è€(€ @€X€p€ˆ€ € ¸ È Øð°ä üV äœh ¤äMUIÍþÍþ°ã”kcMëϼžÛÔ컶˜4L?¬µ°Íl\ÆU΃Ո˜  MUI en-US"Ü$$d&&'´&2H$'PP¸3RYä3dr¤6u¢h<¤¤˜S§§üSª«LT­®U´´$V¶·¤VºËdWÍÒ$^ÔÔÌ`ÖÚ8aÜâ`dåꀀl? € €P@€ € @€€àDd€m€@K€€èM€€pO@€@€œPP€V€ÌP`€a€¸Rd€p€ S€€€ [ €¡€˜[À€Æ€\ЀԀ4_à€ÿ€D`€€Äh€€8i€€$p€€ˆp€€q"€#€”q2€3€€r5€:€¤sA€A€w €€Èw€$€&€)€œ…0€0€È‡Ð€,Ѐ0ˆ€Ð€…Ѐì¨Ñ€Ñ€(ªà€à€Ì² à€ à€0·à€à€¬·!à€1à€P¸€€<Å€€¤ÅW€W€ÐÅá.€/€Æ/€/€ðÑ/€/€4Ù/€/€ˆÙv/€Œ/€`ÚŽ/€/€”〠€l䀀|瀀Pè€ €,ꀀpð €5 €Ðð € €4 € €”   €" €ø $ €) €  0 €C €\E €I €ÐP €[ €¨ ] €_ €|0a €c €l2e €e €4g €g €`4 € €L5 € €ì< €- €ÀF0 €.0 €$P1 €1 €a31 €41 €De2 €2 €°e@ €@ €€?€è F€Q€t W€]€Ø& r€u€è+ €€†€„- €€è0 €€œ5 € €D6 €€08 €$€°9 €€ D €€äD ,€1€F 3€3€ G €¡€\G ô€ù€hK €€€€ÐL €€ÄN € €da #€#€èa &€&€ b &€&€èd 0&€0&€äe 0&€0&€°j '€ '€ˆl '€'€€q '€ '€Ts "'€"'€Lt P'€W'€u Z'€]'€Dz `'€e'€(| (€_(€€ a(€c(€ ® (€(€\¯ (€(€`± @(€@(€ ³ )€)€Ä )€)€ Ñ )€)€@Ý )€ )€”á *€ *€ é *€ *€¨î *€*€Ìô 0€0€`õ E0€E0€¬õ p0€p0€Dö ª0€ª0€¼ö ·0€·0€P÷ 0€0€ ÷ 1€.1€ 01€y1€d7 €1€‰1€ „ 1€Ø1€™ 2€D2€´á 2€2€|ÿ 4€4€ðÿ 4€ 4€d 4€4€$ 4€4€Ì "4€"4€x *4€04€è »4€»4€˜ 4€ 4€ 7€7€€ 8€8€° 9€9€˜ 9€9€$ :€:€´ <€<€8 <€ <€¬ =€#=€¤ >€ >€t2 >€>€7 >€ >€Ø> *>€+>€l? >€>€ˆ@ @€@€F ‚T€‚T€ˆL ‚T€‚T€ Q ‚T€)‚T€tQ U€ U€(T c€c€ ^ c€c€|_ c€c€Àa c€ c€ b c€c€øc c€c€0e c€c€üf c€c€Hg c€c€œg c€c€h c€c€Xh c€c€˜h c€c€(i c€c€hi c€c€Äi  c€ c€j c€! c€@j 0 c€0 c€Ðj @ c€@ c€(k P c€P c€tk ` c€` c€°k p c€r c€ðk € c€ƒ c€¬l c€– c€Œm   c€¡ c€o @c€@c€¤o @c€@c€˜p `c€`c€üp pc€pc€Dq pc€pc€r pc€ pc€s e€e€¼t e€e€°} f€f€0~ ‚€‚€, ƒ€ƒ€¬ †€†€€† °€°€Ô ç€ç€ü’ ç€ ç€ð“ uƒ uƒ¬— vƒvƒx™ ˆ ˆ4› °ˆ°ˆ<£ ÀˆÀˆÔ¦ Ј Ј@ª yˆyˆ± zˆzˆ|² zˆ zˆ`¹ zˆ-zˆ¼ {ˆ{ˆhÊ |ˆ|ˆ$Ì ˜ˆ ˜ˆ¤Ï €˜ˆ€˜ˆ¬Ñ „˜ˆ›˜ˆ\Ò ˜ˆ¡˜ˆà ˜ˆ˜ˆâ ˜ˆ#˜ˆôè ˜ˆ˜ˆê ˜ˆ˜ˆ¸í ˜ˆ˜ˆìñ ˜ˆ˜ˆ¤ò /˜ˆ/˜ˆÄó /˜ˆ/˜ˆPô /˜ˆ /˜ˆ”ô @/˜ˆF/˜ˆ˜õ H/˜ˆI/˜ˆø P/˜ˆR/˜ˆÐø `/˜ˆc/˜ˆðù p/˜ˆs/˜ˆ û €/˜ˆ/˜ˆ@ü Š/˜ˆ•/˜ˆÜü P˜ˆ P˜ˆ ™ˆ-™ˆì ‰‰€" ‰‰4#  À ÀÌ# è&Àè&À(% &À &Àø& &À &Àð+ &À &À1 !&À !&ÀH3 !&À!&À9 "&À"&À¸< #&À#&Àp= #&À #&ÀˆA #&À#&À€C #&ÀJ#&ÀtJ M#&ÀP#&ÀDc R#&À\#&Àˆe $&À$&ÀÈk 0$&À6$&À$m 8$&À8$&Àôq ;$&À;$&À°r %&À%&Àts %&À%&ÀÀt %&À %&Àxu %&À%&Àv %&À!%&Àt €%&À%&Àø Ø%&ÀÜ%&À„ Þ%&Àç%&Àp¢ 4À4À,® 4À4ÀÈ® 5À5À̯ 5À5Àˆ¸ 5À5À» 35À35À”Á 85À85À0 A5ÀA5À„à 5À5À@Ä 7À)7ÀœÄ 8À\8À0ü 9À9Àh- :À(:Àà- \À\ÀèM ÿ\À ÿ\ÀtN TThe operation completed successfully. 0Incorrect function. `The system cannot find the file specified. `The system cannot find the path specified. LThe system cannot open the file. ,Access is denied. 8The handle is invalid. `The storage control blocks were destroyed. |Not enough storage is available to process this command. dThe storage control block address is invalid. DThe environment is incorrect. ˆAn attempt was made to load a program with an incorrect format. @The access code is invalid. 4The data is invalid. €Not enough storage is available to complete this operation. `The system cannot find the drive specified. LThe directory cannot be removed. €The system cannot move the file to a different disk drive. <There are no more files. DThe media is write protected. dThe system cannot find the device specified. <The device is not ready. `The device does not recognize the command. TData error (cyclic redundancy check). ŒThe program issued a command but the command length is incorrect. „The drive cannot locate a specific area or track on the disk. pThe specified disk or diskette cannot be accessed. `The drive cannot find the sector requested. DThe printer is out of paper. lThe system cannot write to the specified device. lThe system cannot read from the specified device. pA device attached to the system is not functioning. ¨The process cannot access the file because it is being used by another process. ÄThe process cannot access the file because another process has locked a portion of the file. ¼The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1. PToo many files opened for sharing. DReached the end of the file. ,The disk is full. DThe request is not supported. ¼Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator. ÀYou were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name. HThe network path was not found. 4The network is busy. ŒThe specified network resource or device is no longer available. lThe network BIOS command limit has been reached. `A network adapter hardware error occurred. „The specified server cannot perform the requested operation. TAn unexpected network error occurred. TThe remote adapter is not compatible. @The printer queue is full. ¤Space to store the file waiting to be printed is not available on the server. dYour file waiting to be printed was deleted. pThe specified network name is no longer available. <Network access is denied. \The network resource type is not correct. LThe network name cannot be found. œThe name limit for the local computer network adapter card was exceeded. dThe network BIOS session limit was exceeded. œThe remote server has been paused or is in the process of being started. (No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. tThe specified printer or disk device has been paused. ,The file exists. \The directory or file cannot be created. (Fail on INT 24. lStorage to process this request is not available. \The local device name is already in use. hThe specified network password is not correct. @The parameter is incorrect. XA write fault occurred on the network. tThe system cannot start another process at this time. XCannot create another system semaphore. tThe exclusive semaphore is owned by another process. `The semaphore is set and cannot be closed. PThe semaphore cannot be set again. xCannot request exclusive semaphores at interrupt time. pThe previous ownership of this semaphore has ended. LInsert the diskette for drive %1. The program stopped because an alternate diskette was not inserted. lThe disk is in use or locked by another process. <The pipe has been ended. tThe system cannot open the device or file specified. @The file name is too long. XThere is not enough space on the disk. dNo more internal file identifiers available. lThe target internal file identifier is incorrect. ˆThe IOCTL call made by the application program is not correct. €The verify-on-write switch parameter value is not correct. pThe system does not support the command requested. hThis function is not supported on this system. \The semaphore timeout period has expired. pThe data area passed to a system call is too small. The filename, directory name, or volume label syntax is incorrect. TThe system call level is not correct. DThe disk has no volume label. \The specified module could not be found. `The specified procedure could not be found. \There are no child processes to wait for. hThe %1 application cannot be run in Win32 mode. ÌAttempt to use a file handle to an open disk partition for an operation other than raw disk I/O. ¨An attempt was made to move the file pointer before the beginning of the file. ˆThe file pointer cannot be set on the specified device or file. ÀA JOIN or SUBST command cannot be used for a drive that contains previously joined drives. ÀAn attempt was made to use a JOIN or SUBST command on a drive that has already been joined. ÌAn attempt was made to use a JOIN or SUBST command on a drive that has already been substituted. The system tried to delete the JOIN of a drive that is not joined. ¨The system tried to delete the substitution of a drive that is not substituted. The system tried to join a drive to a directory on a joined drive. ¤The system tried to substitute a drive to a directory on a substituted drive. ˜The system tried to join a drive to a directory on a substituted drive. The system tried to SUBST a drive to a directory on a joined drive. xThe system cannot perform a JOIN or SUBST at this time. ´The system cannot join or substitute a drive to or for a directory on the same drive. €The directory is not a subdirectory of the root directory. @The directory is not empty. lThe path specified is being used in a substitute. €Not enough resources are available to process this command. hThe path specified cannot be used at this time. An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. ÄSystem trace information was not specified in your CONFIG.SYS file, or tracing is disallowed.  The number of specified semaphore events for DosMuxSemWait is not correct. DosMuxSemWait did not execute; too many semaphores are already set. XThe DosMuxSemWait list is not correct. ¼The volume label you entered exceeds the label character limit of the target file system. DCannot create another thread. dThe recipient process has refused the signal. xThe segment is already discarded and cannot be locked. LThe segment is already unlocked. dThe address for the thread ID is not correct. XOne or more arguments are not correct. HThe specified path is invalid. DA signal is already pending. dNo more threads can be created in the system. PUnable to lock a region of a file. LThe requested resource is in use. pDevice's command support detection is in progress. A lock request was not outstanding for the supplied cancel region. ŒThe file system does not support atomic changes to the lock type. €The system detected a segment number that was not correct. PThe operating system cannot run %1. pCannot create a file when that file already exists. HThe flag passed is not correct. pThe specified system semaphore name was not found. PThe operating system cannot run %1. PThe operating system cannot run %1. PThe operating system cannot run %1. DCannot run %1 in Win32 mode. PThe operating system cannot run %1. T%1 is not a valid Win32 application. PThe operating system cannot run %1. PThe operating system cannot run %1. |The operating system cannot run this application program. œThe operating system is not presently configured to run this application. PThe operating system cannot run %1. |The operating system cannot run this application program. |The code segment cannot be greater than or equal to 64K. PThe operating system cannot run %1. PThe operating system cannot run %1. The system could not find the environment option that was entered. xNo process in the command subtree has a signal handler. XThe filename or extension is too long. @The ring 2 stack is in use. ôThe global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified. XThe signal being posted is not correct. LThe signal handler cannot be set. lThe segment is locked and cannot be reallocated. °Too many dynamic-link modules are attached to this program or dynamic-link module. LCannot nest calls to LoadModule. PThis version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher. hThe image file %1 is signed, unable to modify. tThe image file %1 is strong signed, unable to modify. ˆThis file is checked out or locked for editing by another user. pThe file must be checked out before saving changes. |The file type being saved or retrieved has been blocked. „The file size exceeds the limit allowed and cannot be saved. xAccess Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically. àOperation did not complete successfully because the file contains a virus or potentially unwanted software. ŒThis file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location. 0The pipe is local. @The pipe state is invalid. DAll pipe instances are busy. <The pipe is being closed. `No process is on the other end of the pipe. 8More data is available. <The session was canceled. pThe specified extended attribute name was invalid. \The extended attributes are inconsistent. DThe wait operation timed out. @No more data is available. PThe copy functions cannot be used. HThe directory name is invalid. pThe extended attributes did not fit in the buffer. The extended attribute file on the mounted file system is corrupt. `The extended attribute table file is full. pThe specified extended attribute handle is invalid. „The mounted file system does not support extended attributes. dAttempt to release mutex not owned by caller. \Too many posts were made to a semaphore. ¤Only part of a ReadProcessMemory or WriteProcessMemory request was completed. DThe oplock request is denied. „An invalid oplock acknowledgment was received by the system. |The volume is too fragmented to complete this operation. œThe file cannot be opened because it is in the process of being deleted. ¼Short name settings may not be changed on this volume due to the global registry setting. `Short names are not enabled on this volume. ØThe security stream for the given volume is in an inconsistent state. Please run CHKDSK on the volume. ¬A requested file lock operation cannot be processed due to an invalid byte range. ˆThe subsystem needed to support the image type is not present. ˜The specified file already has a notification GUID associated with it. xAn invalid exception handler routine has been detected. pDuplicate privileges were specified for the token. ŒNo ranges for the specified operation were able to be processed. |Operation is not allowed on a file system internal file. |The physical resources of this disk have been exhausted. `The token representing the data is invalid. lThe device does not support the command feature. ¸The system cannot find message text for message number 0x%1 in the message file for %2. PThe scope specified was not found. œThe Central Access Policy specified is not defined on the target machine. ”The Central Access Policy obtained from Active Directory is invalid. @The device is unreachable. ˜The target device has insufficient resources to complete the operation. ¤A data integrity checksum error occurred. Data in the file stream is corrupt. ÔAn attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. \Device does not support file-level TRIM. ÈThe command specified a data offset that does not align to the device's granularity/alignment. „The command specified an invalid field in its parameter list. xAn operation is currently in progress with the device. ¸An attempt was made to send down the command via an invalid path to the target device. ÌThe command specified a number of descriptors that exceeded the maximum supported by the device. \Scrub is disabled on the specified file. hThe storage device does not provide redundancy. lAn operation is not supported on a resident file. pAn operation is not supported on a compressed file. dAn operation is not supported on a directory. €The specified copy of the requested data could not be read. „The specified data could not be written to any of the copies. One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed. pThe supplied kernel information version is invalid. lThe supplied PEP information version is invalid. tThis object is not externally backed by any provider. lThe external backing provider is not recognized. pNo action was taken as a system reboot is required. HThe shutdown operation failed. DThe restart operation failed. lThe maximum number of sessions has been reached. tThe thread is already in background processing mode. lThe thread is not in background processing mode. tThe process is already in background processing mode. lThe process is not in background processing mode. |The request failed due to a fatal device hardware error. PAttempt to access invalid address. HUser profile cannot be loaded. PArithmetic result exceeded 32 bits. dThere is a process on other end of the pipe. |Waiting for a process to open the other end of the pipe. ˆApplication verifier has found an error in the current process. \An error occurred in the ABIOS subsystem. \A warning occurred in the WX86 subsystem. \An error occurred in the WX86 subsystem. hAn attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine. 8Unwind exception code. œAn invalid or unaligned stack was encountered during an unwind operation. ”An invalid unwind target was encountered during an unwind operation. ÜInvalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. An attempt was made to lower a quota limit below the current usage. ¸An attempt was made to attach to a device that was already attached to another device. $An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. 8Profiling not started. 8Profiling not stopped. ŒThe passed ACL did not contain the minimum required information. ´The number of active profiling objects is at the maximum and no more may be started. ¤Used to indicate that an operation cannot continue without blocking for I/O. <Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process. If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. ˜A malformed function table was encountered during an unwind operation. tIndicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system. This causes the protection attempt to fail, which may cause a file creation attempt to fail. Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors. äIndicates that the starting value for the LDT information was not an integral multiple of the selector size. ÄIndicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. pIndicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads. An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. DPage file quota was exceeded. The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. DThe SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required. ˆThe NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines. ¤{Privilege Failed} The I/O permissions for the process could not be changed. ¬{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C. ˜{Missing System File} The required system file %hs is bad or missing. Ì{Application Error} The exception %s (0x%08lx) occurred in the application at location 0x%08lx. è{Application Error} The application was unable to start correctly (0x%lx). Click OK to close the application. ä{Unable to Create Paging File} The creation of the paging file %hs failed (%lx). The requested size was %ld. ÈWindows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. ´{No Paging File Specified} No paging file was specified in the system configuration. ô{EXCEPTION} A real-mode application issued a floating-point instruction and floating-point hardware is not present. \An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread. lA Windows Server has an incorrect configuration. ¤An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE. ÀThe Unicode character is not defined in the Unicode character set installed on the system. xThe paging file cannot be created on a floppy diskette. äThe system BIOS failed to connect a system interrupt to the device or bus for which the device is connected. ¨This operation is only allowed for the Primary Domain Controller of the domain. ÄAn attempt was made to acquire a mutant such that its maximum count would have been exceeded. ÐA volume has been accessed for which a file system driver is required that has not yet been loaded. {Registry File Failure} The registry cannot load the hive (file): %hs or its log or alternate. It is corrupt, absent, or not writable. œ{Unexpected Failure in DebugActiveProcess} An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error. ${Fatal System Error} The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x). The system has been shut down. Ä{Data Not Accepted} The TDI client could not handle the data received during an indication. HNTVDM encountered a hard error. Ì{Cancel Timeout} The driver %hs failed to complete a cancelled I/O request in the allotted time. P{Reply Message Mismatch} An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message. Ü{Delayed Write Failed} Windows was unable to save all the data for the file %hs. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. @The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window. LThe stream is not a tiny stream. xThe request must be handled by the stack overflow code. €Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream. $The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation. ŒThe bucket array must be grown. Retry transaction after doing so. pThe user/kernel marshalling buffer has overflowed. tThe supplied variant structure contains invalid data. hThe specified buffer contains ill-formed data. ˆ{Audit Failed} An attempt to generate a security audit failed. The timer resolution was not previously set by the current process. |There is insufficient account information to log you on. ”{Invalid DLL Entrypoint} The dynamic link library %hs is not written correctly. The stack pointer has been left in an inconsistent state. The entrypoint should be declared as WINAPI or STDCALL. Select YES to fail the DLL load. Select NO to continue execution. Selecting NO may cause the application to operate incorrectly. „{Invalid Service Callback Entrypoint} The %hs service is not written correctly. The stack pointer has been left in an inconsistent state. The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly. There is an IP address conflict with another system on the network There is an IP address conflict with another system on the network @{Low On Registry Space} The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored. ¨A callback return system service cannot be executed when no callback is active. äThe password provided is too short to meet the policy of your user account. Please choose a longer password. „The policy of your user account does not allow you to change passwords too frequently. This is done to prevent users from changing back to a familiar, but potentially discovered, password. If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned. You have attempted to change your password to one that you have used in the past. The policy of your user account does not allow this. Please select a password that you have not previously used. lThe specified compression format is unsupported. |The specified hardware profile configuration is invalid. „The specified Plug and Play registry device path is invalid. œThe specified quota list is internally inconsistent with its descriptor. ({Windows Evaluation Notification} The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product. D{Illegal System DLL Relocation} The system DLL %hs was relocated in memory. The application will not run properly. The relocation occurred because the DLL %hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. è{DLL Initialization Failed} The application failed to initialize because the window station is shutting down. „The validation process needs to continue on to the next step. „There are no more matches for the current index enumeration. ”The range could not be added to the range list because of a conflict. ¬The server process is running under a SID different than that required by client. pA group marked use for deny only cannot be enabled. d{EXCEPTION} Multiple floating point faults. `{EXCEPTION} Multiple floating point traps. \The requested interface is not supported. {System Standby Failed} The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. „The system file %1 has become corrupt and has been replaced. ô{Virtual Memory Minimum Too Low} Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file. During this process, memory requests for some applications may be denied. For more information, see Help. xA device was removed so enumeration must be restarted. 0{Fatal System Error} The system image %s is not properly signed. The file has been replaced with the signed file. The system has been shut down. XDevice will not start without a reboot. ˆThere is not enough power to complete the requested operation. HERROR_MULTIPLE_FAULT_VIOLATION hThe system is in the process of shutting down. äAn attempt to remove a processes DebugPort was made, but a port was not already associated with the process. ôThis version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |The specified range could not be found in the range list. ˜The driver was not loaded because the system is booting into safe mode. ”The driver was not loaded because it failed its initialization call. PThe "%hs" encountered an error while applying power or reading the device configuration. This may be caused by a failure of your hardware or by a poor connection. LThe create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached. The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. ÌA Machine Check Error has occurred. Please check the system eventlog for additional information. tThere was error [%2] processing the driver database. \System hive size has exceeded its limit. ÀThe driver could not be loaded because a previous version of the driver is still in memory. ð{Volume Shadow Copy Service} Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. øThe system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. äThe password provided is too long to meet the policy of your user account. Please choose a shorter password. ¨The requested operation could not be completed due to a file system limitation PAn assertion failure has occurred. \An error occurred in the ACPI subsystem. 4WOW Assertion Error. A device is missing in the system BIOS MPS table. This device will not be used. Please contact your system vendor for system BIOS update. `A translator failed to translate resources. hA IRQ translator failed to translate resources. xDriver %2 returned invalid ID for a child device (%3). ¤{Kernel Debugger Awakened} the system debugger was awakened by an interrupt. à{Handles Closed} Handles to objects have been automatically closed as a result of the requested operation. ä{Too Much Information} The specified access control list (ACL) contained more information than was expected. ,This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired). d{Media Changed} The media may have changed. \{GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. €The create operation stopped after reaching a symbolic link HA long jump has been executed. tThe Plug and Play query operation was not successful. \A frame consolidation has been executed. {Registry Hive Recovered} Registry hive (file): %hs was corrupted and it has been recovered. Some data might have been lost. tThe application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs? äThe application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs? XDebugger did not handle the exception. @Debugger will reply later. HDebugger cannot provide handle. @Debugger terminated thread. DDebugger terminated process. 8Debugger got control C. \Debugger printed exception on control C. LDebugger received RIP exception. LDebugger received control break. \Debugger command communication exception. Ä{Object Exists} An attempt was made to create an object and the object name already existed. {Thread Suspended} A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. ({Image Relocated} An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image. This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. ä{Segment Load} A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image. An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments. P{Invalid Current Directory} The process cannot switch to the startup current directory %hs. Select OK to set current directory to %hs, or select CANCEL to exit. d{Redundant Read} To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device. d{Redundant Write} To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information. This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device. X{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load. {Partial Data Received} The network transport returned partial data to its client. The remaining data will be sent later. {Expedited Data Received} The network transport returned data to its client that was marked as expedited by the remote system. ˆ{Partial Expedited Data Received} The network transport returned partial data to its client and this data was marked as expedited by the remote system. The remaining data will be sent later. Œ{TDI Event Done} The TDI indication has completed successfully. ˜{TDI Event Pending} The TDI indication has entered the pending state. @Checking file system on %wZ D{Fatal Application Exit} %hs ŒThe specified registry key is referenced by a predefined handle. ${Page Unlocked} The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process. %hs €{Page Locked} One of the pages to lock was already locked. @Application popup: %1 : %2 0ERROR_ALREADY_WIN32 è{Machine Type Mismatch} The image file %hs is valid, but is for a machine type other than the current machine. A yield execution was performed and no thread was available to run. hThe resumable flag to a timer API was ignored. ”The arbiter has deferred arbitration of these resources to its parent ¼The inserted CardBus device cannot be started because of a configuration error on "%hs". |The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported. TThe system was put into hibernation. \The system was resumed from hibernation. üWindows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. LA device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit. 4The system has awoken $ERROR_WAIT_1 $ERROR_WAIT_2 $ERROR_WAIT_3 $ERROR_WAIT_63 8ERROR_ABANDONED_WAIT_0 8ERROR_ABANDONED_WAIT_63 (ERROR_USER_APC ,ERROR_KERNEL_APC $ERROR_ALERTED `The requested operation requires elevation. àA reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. ”An open/create operation completed while an oplock break is underway. hA new volume has been mounted by a file system. This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted. The commit has now been completed. This indicates that a notify change request has been completed due to closing the handle which made the notify change request. ¬{Connect Failure on Primary Transport} An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed. The computer WAS able to connect on a secondary transport. PPage fault was a transition fault. PPage fault was a demand zero fault. PPage fault was a demand zero fault. PPage fault was a demand zero fault. ”Page fault was satisfied by reading from a secondary storage device. \Cached page was locked during operation. LCrash dump exists in paging file. TSpecified buffer contains all zeros. àA reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. ¬The device has succeeded a query-stop and its resource requirements have changed. ôThe translator has translated these resources into the global space and no further translations should be performed. xA process being terminated has no threads to terminate. `The specified process is not part of a job. XThe specified process is part of a job. ˜{Volume Shadow Copy Service} The system is now ready for hibernation. ÄA file system or file system filter driver has successfully completed an FsFilter operation. tThe specified interrupt vector was already connected. pThe specified interrupt vector is still connected. hAn operation is blocked waiting for an oplock. @Debugger handled exception 0Debugger continued ÈAn exception occurred in a user mode callback and the kernel callback frame should be removed. \Compression is disabled for this volume. ˆThe data provider cannot fetch backwards through a result set. ˆThe data provider cannot scroll backwards through a result set. ÌThe data provider requires that previously fetched data is released before asking for more data. ÈThe data provider was not able to interpret the flags set for a column binding in an accessor. |One or more errors occurred while processing the request. „The implementation is not capable of performing the request. èThe client of a component requested an operation which is not valid given the state of the component instance. TA version number could not be parsed. \The iterator's start position is invalid. |The hardware has reported an uncorrectable memory error. „The attempted operation required self healing to be enabled. üThe Desktop heap encountered an error while allocating session memory. There is more information in the system event log. xThe system power state is transitioning from %2 to %3. œThe system power state is transitioning from %2 to %3 but could enter %4. ŒA thread is getting dispatched with MCA EXCEPTION because of MCA. dAccess to %1 is monitored by policy rule %2. œAccess to %1 has been restricted by your Administrator by policy rule %2. ˜A valid hibernation file has been invalidated and should be abandoned.  {Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere. °{Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error was returned by the server on which the file exists. Please try to save this file elsewhere. {Delayed Write Failed} Windows was unable to save all the data for the file %hs; the data has been lost. This error may be caused if the device has been removed or the media is write-protected. ”The resources required for this device conflict with the MCFG table. The volume repair could not be performed while it is online. Please schedule to take the volume offline so that it can be repaired. TThe volume repair was not successful. ÔOne of the volume corruption logs is full. Further corruptions that may be detected won't be logged. 8One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. ˜One of the volume corruption logs is unavailable for being operated on. @One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. ÌOne of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. tOrphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory. ÀThe oplock that was associated with this handle is now associated with a different handle. ÌAn oplock of the requested level cannot be granted. An oplock of a lower level may be available. <The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken. ÄThe handle with which this oplock was associated has been closed. The oplock is now broken. ˜The specified access control entry (ACE) does not contain a condition. ˜The specified access control entry (ACE) contains an invalid condition. tAccess to the specified file handle has been revoked. `{Image Relocated} An image file was mapped at a different address from the one specified in the image file but fixups will still be automatically performed on the image. The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. dAccess to the extended attribute was denied. ÄThe I/O operation has been aborted because of either a thread exit or an application request. lOverlapped I/O event is not in a signaled state. \Overlapped I/O operation is in progress. PInvalid access to memory location. PError performing inpage operation. \Recursion too deep; the stack overflowed. `The window cannot act on the sent message. HCannot complete this function. (Invalid flags. HThe volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted. ÄThe volume for a file has been externally altered so that the opened file is no longer valid. ŒThe requested operation cannot be performed in full-screen mode. „An attempt was made to reference a token that does not exist. hThe configuration registry database is corrupt. `The configuration registry key is invalid. pThe configuration registry key could not be opened. lThe configuration registry key could not be read. tThe configuration registry key could not be written. One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. üThe registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted. €An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry. The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format. ¬Illegal operation attempted on a registry key that has been marked for deletion. ˆSystem could not allocate the required space in a registry log. °Cannot create a symbolic link in a registry key that already has subkeys or values. €Cannot create a stable subkey under a volatile parent key. dA notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes. ¸A stop control has been sent to a service that other running services are dependent on. tThe requested control is not valid for this service. ¬The service did not respond to the start or control request in a timely fashion. hA thread could not be created for the service. HThe service database is locked. hAn instance of the service is already running. ÜThe account name is invalid or does not exist, or the password is invalid for the account name specified. ôThe service cannot be started, either because it is disabled or because it has no enabled devices associated with it. `Circular service dependency was specified. „The specified service does not exist as an installed service. |The service cannot accept control messages at this time. LThe service has not been started. ŒThe service process could not connect to the service controller. ˜An exception occurred in the service when handling the control request. XThe database specified does not exist. xThe service has returned a service-specific error code. TThe process terminated unexpectedly. lThe dependency service or group failed to start. lThe service did not start due to a logon failure. €After starting, the service hung in a start-pending state. hThe specified service database lock is invalid. pThe specified service has been marked for deletion. TThe specified service already exists. ˜The system is currently running with the last-known-good configuration. ˜The dependency service does not exist or has been marked for deletion. ¸The current boot has already been accepted for use as the last-known-good control set. ”No attempts to start the service have been made since the last boot. ¨The name is already in use as either a service name or a service display name. The account specified for this service is different from the account specified for other services running in the same process. ”Failure actions can only be set for Win32 services, not for drivers. pThis service runs in the same process as the service control manager. Therefore, the service control manager cannot take action if this service's process terminates unexpectedly. |No recovery program has been configured for this service. ÌThe executable program that this service is configured to run in does not implement the service. `This service cannot be started in Safe Mode hThe physical end of the tape has been reached. LA tape access reached a filemark. |The beginning of the tape or a partition was encountered. lA tape access reached the end of a set of files. DNo more data is on the tape. HTape could not be partitioned. ÀWhen accessing a new tape of a multivolume partition, the current block size is incorrect. Tape partition information could not be found when loading a tape. \Unable to lock the media eject mechanism. @Unable to unload the media. \The media in the drive may have changed. 8The I/O bus was reset. 0No media in drive. ¨No mapping for the Unicode character exists in the target multi-byte code page. €A dynamic link library (DLL) initialization routine failed. LA system shutdown is in progress. œUnable to abort the system shutdown because no shutdown was in progress. The request could not be performed because of an I/O device error. ¤No serial device was successfully initialized. The serial driver will unload. <Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened. üA serial I/O operation was completed by another write to the serial port. (The IOCTL_SERIAL_XOFF_COUNTER reached zero.) üA serial I/O operation completed because the timeout period expired. (The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.) lNo ID address mark was found on the floppy disk. ÈMismatch between the floppy disk sector ID field and the floppy disk controller track address. ÈThe floppy disk controller reported an error that is not recognized by the floppy disk driver.  The floppy disk controller returned inconsistent results in its registers. °While accessing the hard disk, a recalibrate operation failed, even after retries.  While accessing the hard disk, a disk operation failed even after retries. ¼While accessing the hard disk, a disk controller reset was needed, but even that failed. LPhysical end of tape encountered. ˆNot enough server storage is available to process this command. lA potential deadlock condition has been detected. ¬The base address or the file offset specified does not have the proper alignment. ¼An attempt to change the system power state was vetoed by another application or driver. The system BIOS failed an attempt to change the system power state. ¬An attempt was made to create more links on a file than the file system supports. €The specified program requires a newer version of Windows. |The specified program is not a Windows or MS-DOS program. „Cannot start more than one instance of the specified program. ”The specified program was written for an earlier version of Windows. One of the library files needed to run this application is damaged. œNo application is associated with the specified file for this operation. „An error occurred in sending the command to the application. œOne of the library files needed to run this application cannot be found. ÈThe current process has used all of its system allowance of handles for Window Manager objects. |The message can be used only with synchronous operations. `The indicated source element has no media. |The indicated destination element already contains media. TThe indicated element does not exist. ŒThe indicated element is part of a magazine that is not present. ˜The indicated device requires reinitialization due to hardware errors. ÀThe device has indicated that cleaning is required before further operations are attempted. hThe device has indicated that its door is open. DThe device is not connected. 0Element not found. xThere was no match for the specified key in the index. |The property set specified does not exist on the object. „The point passed to GetMouseMovePoints is not in the buffer. pThe tracking (workstation) service is not running. LThe Volume ID could not be found. \Unable to remove the file to be replaced. øUnable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name. Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name. `The volume change journal is being deleted. \The volume change journal is not active. tA file was found, but it may not be the correct file. tThe journal entry has been deleted from the journal. dA system shutdown has already been scheduled. ÌThe system shutdown cannot be initiated because there are other users logged on to the computer. TThe specified device name is invalid. œThe device is not currently connected but it is a remembered connection. ¨The local device name has a remembered connection to another network resource. xThe network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator. hThe specified network provider name is invalid. hUnable to open the network connection profile. dThe network connection profile is corrupted. LCannot enumerate a noncontainer. HAn extended error has occurred. pThe format of the specified group name is invalid. tThe format of the specified computer name is invalid. pThe format of the specified event name is invalid. pThe format of the specified domain name is invalid. tThe format of the specified service name is invalid. tThe format of the specified network name is invalid. pThe format of the specified share name is invalid. lThe format of the specified password is invalid. tThe format of the specified message name is invalid. €The format of the specified message destination is invalid. œMultiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. °The workgroup or domain name is already in use by another computer on the network. `The network is not present or not started. XThe operation was canceled by the user. ¸The requested operation cannot be performed on a file with a user-mapped section open. pThe remote computer refused the network connection. dThe network connection was gracefully closed. œThe network transport endpoint already has an address associated with it. ŒAn address has not yet been associated with the network endpoint. ˆAn operation was attempted on a nonexistent network connection. An invalid operation was attempted on an active network connection. ÜThe network location cannot be reached. For information about network troubleshooting, see Windows Help. ÜThe network location cannot be reached. For information about network troubleshooting, see Windows Help. ÜThe network location cannot be reached. For information about network troubleshooting, see Windows Help. ¬No service is operating at the destination network endpoint on the remote system. <The request was aborted. xThe network connection was aborted by the local system. The operation could not be completed. A retry should be performed. A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. œAttempting to log in during an unauthorized time of day for this account. €The account is not authorized to log in from this station. The network address could not be used for the operation requested. PThe service is already registered. TThe specified service does not exist. ÄThe operation being requested was not performed because the user has not been authenticated. The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. HContinue with work in progress. àAn attempt was made to perform an initialization operation when initialization has already been completed. 8No more local devices. PThe specified site does not exist. €A domain controller with the specified name already exists. ˜This operation is supported only when you are connected to the server. °The group policy framework should call the extension even if there are no changes. lThe specified user does not have a valid profile. ÐThis operation is not supported on a computer running Windows Server 2003 for Small Business Server TThe server machine is shutting down. ÔThe remote system is not available. For information about network troubleshooting, see Windows Help. ˆThe security identifier provided is not from an account domain. The security identifier provided does not have a domain component. ˜AppHelp dialog canceled thus preventing the application from starting. ÌThis program is blocked by group policy. For more information, contact your system administrator. A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific. lThe share is currently offline or does not exist. @The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log. ÈThe Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. äThe system cannot contact a domain controller to service the authentication request. Please try again later. ˜The machine is locked and cannot be shut down without the force option. ˆAn application-defined callback gave invalid data when called. ÐThe group policy framework should call the extension in the synchronous foreground policy refresh. \This driver has been blocked from loading àA dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. „Windows cannot open this program since it has been disabled. ðWindows cannot open this program because the license enforcement system has been tampered with or become corrupted. DA transaction recover failed. |The current thread has already been converted to a fiber. €The current thread has already been converted from a fiber. XThe system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. ¨Data present in one of the parameters is more than the function can operate on. äAn attempt to do an operation on a debug object failed because the object is in the process of being deleted. ¼An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. (%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. ŒInsufficient information exists to identify the cause of failure. €The parameter passed to a C runtime function is incorrect. ŒThe operation occurred beyond the valid data length of the file. The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. The process hosting the driver for this device has been terminated. ŒAn operation attempted to exceed an implementation-defined limit. ÄEither the target process, or the target thread's containing process, is a protected process. ØThe service notification client is lagging too far behind the current state of services in the machine. ÄThe requested file operation failed because the storage quota was exceeded. To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator. ,The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. „A privilege that the service requires to function properly does not exist in the service account configuration. You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration. ˆA thread involved in this operation appears to be unresponsive. ¬Indicates a particular Security ID may not be assigned as the label of an object. Not all privileges or groups referenced are assigned to the caller. ŒSome mapping between account names and security IDs was not done. „No system quota limits are specifically set for this account. œNo encryption key is available. A well-known encryption key was returned. The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. HThe revision level is unknown. hIndicates two revision levels are incompatible. ŒThis security ID may not be assigned as the owner of this object. ˜This security ID may not be assigned as the primary group of an object. øAn attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. HThe group may not be disabled. ¤There are currently no logon servers available to service the logon request. ¨A specified logon session does not exist. It may already have been terminated. TA specified privilege does not exist. hA required privilege is not held by the client. |The name provided is not a properly formed account name. TThe specified account already exists. TThe specified account does not exist. PThe specified group already exists. PThe specified group does not exist. 4Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member.  The specified user account is not a member of the specified group account. üThis operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon. ¸Unable to update the password. The value provided as the current password is incorrect. üUnable to update the password. The value provided for the new password contains values that are not allowed in passwords. 0Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. XThe user name or password is incorrect. lAccount restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.  Your account has time restrictions that keep you from signing in right now. tThis user isn't allowed to sign in to this computer. `The password for this account has expired. This user can't sign in because this account is currently disabled. €No mapping between account names and security IDs was done. Too many local user identifiers (LUIDs) were requested at one time. tNo more local user identifiers (LUIDs) are available.  The subauthority part of a security ID is invalid for this particular use. pThe access control list (ACL) structure is invalid. TThe security ID structure is invalid. dThe security descriptor structure is invalid. ¼The inherited access control list (ACL) or access control entry (ACE) could not be built. LThe server is currently disabled. LThe server is currently enabled. ”The value provided was an invalid value for an identifier authority. „No more memory is available for security information updates. ÐThe specified attributes are invalid, or incompatible with the attributes for the group as a whole. ØEither a required impersonation level was not provided, or the provided impersonation level is invalid. hCannot open an anonymous level security token. xThe validation information class requested was invalid. „The type of the token is inappropriate for its attempted use. ´Unable to perform a security operation on an object that has no associated security. $Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. ”The domain was in the wrong state to perform the security operation. ¨This operation is only allowed for the Primary Domain Controller of the domain. ”The specified domain either does not exist or could not be contacted. TThe specified domain already exists. ¤An attempt was made to exceed the limit on the number of domains per server. Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk. @An internal error occurred. ÜGeneric access types were contained in an access mask which should already be mapped to nongeneric types. ¤A security descriptor is not in the right format (absolute or self-relative). The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. Cannot start a new logon session with an ID that is already in use. hA specified authentication package is unknown. ´The logon session is not in a state that is consistent with the requested operation. XThe logon session ID is already in use. xA logon request contained an invalid logon type value. ¬Unable to impersonate using a named pipe until data has been read from that pipe. ¼The transaction state of a registry subtree is incompatible with the requested operation. ˆAn internal security database corruption has been encountered. pCannot perform this operation on built-in accounts. „Cannot perform this operation on this built-in special group. „Cannot perform this operation on this built-in special user. ÌThe user cannot be removed from a group because the group is currently the user's primary group. hThe token is already in use as a primary token. \The specified local group does not exist. |The specified account name is not a member of the group. „The specified account name is already a member of the group. \The specified local group already exists. ¸Logon failure: the user has not been granted the requested logon type at this computer. ¸The maximum number of secrets that may be stored in a single system has been exceeded. €The length of a secret exceeds the maximum length allowed. œThe local security authority database contains an internal inconsistency. ¸During a logon attempt, the user's security context accumulated too many security IDs. ¸Logon failure: the user has not been granted the requested logon type at this computer. A cross-encrypted password is necessary to change a user password. ÌA member could not be added to or removed from the local group because the member does not exist. ÈA new member could not be added to a local group because the member has the wrong account type. `Too many security IDs have been specified. ”A cross-encrypted password is necessary to change this user password. tIndicates an ACL contains no inheritable components. pThe file or directory is corrupted and unreadable. hThe disk structure is corrupted and unreadable. „There is no user session key for the specified logon session. °The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept. TThe target account name is incorrect. ÄMutual Authentication failed. The server's password is out of date at the domain controller. ”There is a time and/or date difference between the client and server. |This operation cannot be performed on the current domain. 8Invalid window handle. 4Invalid menu handle. 8Invalid cursor handle. LInvalid accelerator table handle. 4Invalid hook handle. xInvalid handle to a multiple-window position structure. XCannot create a top-level child window. <Cannot find window class. `Invalid window; it belongs to other thread. HHot key is already registered. 4Class already exists. 4Class does not exist. DClass still has open windows. (Invalid index. 4Invalid icon handle. PUsing private DIALOG window words. XThe list box identifier was not found. <No wildcards were found. XThread does not have a clipboard open. @Hot key is not registered. \The window is not a valid dialog window. 4Control ID not found. œInvalid message for a combo box because it does not have an edit control. HThe window is not a combo box. DHeight must be less than 256. PInvalid device context (DC) handle. DInvalid hook procedure type. 8Invalid hook procedure. lCannot set nonlocal hook without a module handle. dThis hook procedure can only be set globally. lThe journal hook procedure is already installed. TThe hook procedure is not installed. hInvalid message for single-selection list box. XLB_SETCOUNT sent to non-lazy list box. \This list box does not support tab stops. lCannot destroy object created by another thread. LChild windows cannot have menus. XThe window does not have a system menu. @Invalid message box style. XInvalid system-wide (SPI_*) parameter. 8Screen already locked. ¼All handles to windows in a multiple-window position structure must have the same parent. LThe window is not a child window. 4Invalid GW_* command. @Invalid thread identifier. ÈCannot process a message from a window that is not a multiple document interface (MDI) window. @Popup menu already active. TThe window does not have scroll bars. lScroll bar range cannot be greater than MAXLONG. xCannot show or remove the window in the way specified. ˜Insufficient system resources exist to complete the requested service. ˜Insufficient system resources exist to complete the requested service. ˜Insufficient system resources exist to complete the requested service. tInsufficient quota to complete the requested service. tInsufficient quota to complete the requested service. „The paging file is too small for this operation to complete. @A menu item was not found. HInvalid keyboard layout handle. 8Hook type not allowed. xThis operation requires an interactive window station. €This operation returned because the timeout period expired. 8Invalid monitor handle. <Incorrect size argument. The symbolic link cannot be followed because its type is disabled.  This application does not support the current operation on symbolic links. pWindows was unable to parse the requested XML data. An error was encountered while processing an XML digital signature. PThis application must be restarted. œThe caller made the connection request in the wrong routing compartment.  There was an AuthIP failure when attempting to connect to the remote host. ÌInsufficient NVRAM resources exist to complete the requested service. A reboot might be required. ÄUnable to finish the requested operation because the specified process is not a GUI process. LThe event log file is corrupted. ¨No event log file could be opened, so the event logging service did not start. @The event log file is full. xThe event log file has changed between read operations. PThe specified task name is invalid. TThe specified task index is invalid. hThe specified thread is already joining a task. XThe Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance. DUser cancelled installation. LFatal error during installation. PInstallation suspended, incomplete. ”This action is only valid for products that are currently installed. @Feature ID not registered. DComponent ID not registered. ,Unknown property. HHandle is in an invalid state. °The configuration data for this product is corrupt. Contact your support personnel. LComponent qualifier not present. ôThe installation source for this product is not available. Verify that the source exists and that you can access it. xThis installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. 8Product is uninstalled. \SQL query syntax invalid or unsupported. DRecord field does not exist. DThe device has been removed. äAnother installation is already in progress. Complete that installation before proceeding with this install. ”This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. ÜThere was an error starting the Windows Installer service user interface. Contact your support personnel. ôError opening installation log file. Verify that the specified log file location exists and that you can write to it.  The language of this installation package is not supported by your system. ¨Error applying transforms. Verify that the specified transform paths are valid. °This installation is forbidden by system policy. Contact your system administrator. HFunction could not be executed. LFunction failed during execution. PInvalid or unknown table specified. HData supplied is of wrong type. PData of this type is not supported. ¨The Windows Installer service failed to start. Contact your support personnel. 8The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. ÈThis installation package is not supported by this processor type. Contact your product vendor. TComponent not used on this computer. ¤This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package. This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package. lThis update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. ¨Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. ÌInvalid command line argument. Consult the Windows Installer SDK for detailed command line help. ÀOnly administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator. äThe requested operation completed successfully. The system will be restarted so the changes can take effect. 8The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade. The update package is not permitted by software restriction policy. ¤One or more customizations are not permitted by software restriction policy. ´The Windows Installer does not permit installation from a Remote Desktop Connection. xUninstallation of the update package is not supported. `The update is not applied to this product. |No valid sequence could be found for the set of updates. \Update removal was disallowed by policy. HThe XML update data is invalid. DWindows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update. ”The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state. øA fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. ¨The app that you are trying to run is not supported on this version of Windows.  The operation was blocked as the process prohibits dynamic code generation. HThe string binding is invalid. `The binding handle is not the correct type. HThe binding handle is invalid. `The RPC protocol sequence is not supported. TThe RPC protocol sequence is invalid. |The string universal unique identifier (UUID) is invalid. HThe endpoint format is invalid. HThe network address is invalid. 8No endpoint was found. DThe timeout value is invalid. „The object universal unique identifier (UUID) was not found.  The object universal unique identifier (UUID) has already been registered. œThe type universal unique identifier (UUID) has already been registered. TThe RPC server is already listening. `No protocol sequences have been registered. LThe RPC server is not listening. DThe manager type is unknown. <The interface is unknown. 8There are no bindings. LThere are no protocol sequences. HThe endpoint cannot be created. ˆNot enough resources are available to complete this operation. HThe RPC server is unavailable. xThe RPC server is too busy to complete this operation. LThe network options are invalid. €There are no remote procedure calls active on this thread. LThe remote procedure call failed. tThe remote procedure call failed and did not execute. xA remote procedure call (RPC) protocol error occurred. PAccess to the HTTP proxy is denied. xThe transfer syntax is not supported by the RPC server. „The universal unique identifier (UUID) type is not supported. 0The tag is invalid. DThe array bounds are invalid. `The binding does not contain an entry name. @The name syntax is invalid. LThe name syntax is not supported. ¼No network address is available to use to construct a universal unique identifier (UUID). DThe endpoint is a duplicate. PThe authentication type is unknown. \The maximum number of calls is too small. 8The string is too long. \The RPC protocol sequence was not found. TThe procedure number is out of range. „The binding does not contain any authentication information. XThe authentication service is unknown. TThe authentication level is unknown. LThe security context is invalid. TThe authorization service is unknown. 4The entry is invalid. lThe server endpoint cannot perform the operation. ˆThere are no more endpoints available from the endpoint mapper. LNo interfaces have been exported. DThe entry name is incomplete. HThe version option is invalid. @There are no more members. DThere is nothing to unexport. DThe interface was not found. <The entry already exists. 8The entry is not found. LThe name service is unavailable. XThe network address family is invalid. \The requested operation is not supported. |No security context is available to allow impersonation. „An internal error occurred in a remote procedure call (RPC). tThe RPC server attempted an integer division by zero. hAn addressing error occurred in the RPC server. ˜A floating-point operation at the RPC server caused a division by zero. xA floating-point underflow occurred at the RPC server. tA floating-point overflow occurred at the RPC server. ´The list of RPC servers available for the binding of auto handles has been exhausted. tUnable to open the character translation table file. ¤The file containing the character translation table has fewer than 512 bytes. ÄA null context handle was passed from the client to the host during a remote procedure call. €The context handle changed during a remote procedure call. The binding handles passed to a remote procedure call do not match. €The stub is unable to get the remote procedure call handle. lA null reference pointer was passed to the stub. XThe enumeration value is out of range. DThe byte count is too small. @The stub received bad data. The supplied user buffer is not valid for the requested operation. €The disk media is not recognized. It may not be formatted. dThe workstation does not have a trust secret. äThe security database on the server does not have a computer account for this workstation trust relationship. ¬The trust relationship between the primary domain and the trusted domain failed. ¨The trust relationship between this workstation and the primary domain failed. <The network logon failed. ˆA remote procedure call is already in progress for this thread. ¤An attempt was made to logon, but the network logon service was not started. HThe user's account has expired. lThe redirector is in use and cannot be unloaded. pThe specified printer driver is already installed. HThe specified port is unknown. HThe printer driver is unknown. HThe print processor is unknown. \The specified separator file is invalid. PThe specified priority is invalid. DThe printer name is invalid. @The printer already exists. HThe printer command is invalid. PThe specified datatype is invalid. TThe environment specified is invalid. @There are no more bindings. The account used is an interdomain trust account. Use your global user account or local user account to access this server. ìThe account used is a computer account. Use your global user account or local user account to access this server. ôThe account used is a server trust account. Use your global user account or local user account to access this server. ìThe name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain. dThe server is in use and cannot be unloaded. „The specified image file did not contain a resource section. ˆThe specified resource type cannot be found in the image file. ˆThe specified resource name cannot be found in the image file. ”The specified resource language ID cannot be found in the image file. xNot enough quota is available to process this command. PNo interfaces have been registered. \The remote procedure call was cancelled. „The binding handle does not contain all required information. ŒA communications failure occurred during a remote procedure call. tThe requested authentication level is not supported. DNo principal name registered. €The error specified is not a valid Windows RPC error code. ˆA UUID that is valid only on this computer has been allocated. `A security package specific error occurred. 8Thread is not canceled. pInvalid operation on the encoding/decoding handle. lIncompatible version of the serializing package. TIncompatible version of the RPC stub. dThe RPC pipe object is invalid or corrupted. |An invalid operation was attempted on an RPC pipe object. DUnsupported RPC pipe version. °HTTP proxy server rejected the connection because the cookie authentication failed. HThe group member was not found. |The endpoint mapper database entry could not be created. ˆThe object universal unique identifier (UUID) is the nil UUID. HThe specified time is invalid. PThe specified form name is invalid. PThe specified form size is invalid. xThe specified printer handle is already being waited on XThe specified printer has been deleted. TThe state of the printer is invalid. xThe user's password must be changed before signing in. tCould not find the domain controller for this domain.  The referenced account is currently locked out and may not be logged on to. dThe object exporter specified was not found. PThe object specified was not found. lThe object resolver set specified was not found. pSome data remains to be sent in the request buffer. pInvalid asynchronous remote procedure call handle. |Invalid asynchronous RPC call handle for this operation. dThe RPC pipe object has already been closed. xThe RPC call completed before all pipes were processed. dNo more data is available from the RPC pipe. `No site name is available for this machine. `The file cannot be accessed by the system. xThe name of the file cannot be resolved by the system. XThe entry is not of the expected type. ˆNot all object UUIDs could be exported to the specified entry. xInterface could not be exported to the specified entry. hThe specified profile entry could not be added. lThe specified profile element could not be added. pThe specified profile element could not be removed. TThe group element could not be added. XThe group element could not be removed. ØThe printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers. pThe context has expired and can no longer be used. ”The current user's delegated trust creation quota has been exceeded. €The total delegated trust creation quota has been exceeded. ”The current user's delegated trust deletion quota has been exceeded. 0The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer. ´Remote connections to the Print Spooler are blocked by a policy set on your machine. ”Authentication failed because NTLM authentication has been disabled. èLogon Failure: EAS policy requires that the user change their password before this operation can be performed. DThe pixel format is invalid. LThe specified driver is invalid. The window style or class attribute is invalid for this operation. pThe requested metafile operation is not supported. |The requested transformation operation is not supported. pThe requested clipping operation is not supported. lThe specified color management module is invalid. XThe specified color profile is invalid. LThe specified tag was not found. HA required tag is not present. TThe specified tag is already present. œThe specified color profile is not associated with the specified device. `The specified color profile was not found. TThe specified color space is invalid. XImage Color Management is not enabled. xThere was an error while deleting the color transform. \The specified color transform is invalid. ŒThe specified transform does not match the bitmap's color space. ˆThe specified named color index is not present in the profile. ÄThe specified profile is intended for a device of a different type than the specified device. The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified. ˜The network connection was made successfully using default credentials. PThe specified username is invalid. XThis network connection does not exist. €This network connection has files open or requests pending. HActive connections still exist. ”The device is in use by an active process and cannot be disconnected. XThe specified print monitor is unknown. lThe specified printer driver is currently in use. DThe spool file was not found. XA StartDocPrinter call was not issued. HAn AddJob call was not issued. |The specified print processor has already been installed. xThe specified print monitor has already been installed. ŒThe specified print monitor does not have the required functions. lThe specified print monitor is currently in use. ¬The requested operation is not allowed when there are jobs queued to the printer. ÐThe requested operation is successful. Changes will not be effective until the system is rebooted. ÔThe requested operation is successful. Changes will not be effective until the service is restarted. 8No printers were found. dThe printer driver is known to be unreliable. hThe printer driver is known to harm the system. |The specified printer driver package is currently in use. ´Unable to find a core driver package that is required by the printer driver package. ¸The requested operation failed. A system reboot is required to roll back changes made. ÄThe requested operation failed. A system reboot has been initiated to roll back changes made. ´The specified printer driver was not found on the system and needs to be downloaded. ØThe requested print job has failed to print. A print system update requires the job to be resubmitted. ´The printer driver does not contain a valid manifest, or contains too many manifests. XThe specified printer cannot be shared. <The operation was paused. tReissue the given operation as a cached IO operation xWINS encountered an error while processing the command. LThe local WINS cannot be deleted. TThe importation from the file failed. lThe backup failed. Was a full backup done before? ¤The backup failed. Check the directory to which you are backing the database. dThe name does not exist in the WINS database. |Replication with a nonconfigured partner is not allowed. ŒThe version of the supplied content information is not supported. hThe supplied content information is malformed. €The requested data cannot be found in local or peer caches. XNo more data is available or required. dThe supplied object has not been initialized. lThe supplied object has already been initialized. dA shutdown operation is already in progress. lThe supplied object has already been invalidated. hAn element already exists and was not replaced. œCan not cancel the requested operation as it has already been completed. ¨Can not perform the reqested operation because it has already been carried out. €An operation accessed data beyond the bounds of valid data. XThe requested version is not supported. LA configuration value is invalid. <The SKU is not licensed. ”PeerDist Service is still initializing and will be available shortly. ÀCommunication with one or more computers will be temporarily blocked due to recent errors. XThe DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address. The GUID passed was not recognized as valid by a WMI data provider. ¤The instance name passed was not recognized as valid by a WMI data provider.  The data item ID passed was not recognized as valid by a WMI data provider. „The WMI request could not be completed and should be retried. `The WMI data provider could not be located. ¨The WMI data provider references an instance set that has not been registered. The WMI data block or event notification has already been enabled. `The WMI data block is no longer available. XThe WMI data service is not available. xThe WMI data provider failed to carry out the request. TThe WMI MOF information is not valid. hThe WMI registration information is not valid. The WMI data block or event notification has already been disabled. dThe WMI data item or data block is read only. tThe WMI data item or data block could not be changed. ŒThis operation is only valid in the context of an app container. ŒThis application can only run in the context of an app container. ˜This functionality is not supported in the context of an app container. ¤The length of the SID supplied is not a valid length for app container SIDs. xThe media identifier does not represent a valid medium. €The library identifier does not represent a valid library. ŒThe media pool identifier does not represent a valid media pool. œThe drive and medium are not compatible or exist in different libraries. ÈThe medium currently exists in an offline library and must be online to perform this operation. |The operation cannot be performed on an offline library. `The library, drive, or media pool is empty.  The library, drive, or media pool must be empty to perform this operation. ˆNo media is currently available in this media pool or library. pA resource required for this operation is disabled. |The media identifier does not represent a valid cleaner. |The drive cannot be cleaned or does not support cleaning. |The object identifier does not represent a valid object. dUnable to read from or write to the database. 4The database is full. €The medium is not compatible with the device or media pool. |The resource required for this operation does not exist. XThe operation identifier is not valid. `The media is not mounted or ready for use. LThe device is not ready for use. xThe operator or administrator has refused the request. xThe drive identifier does not represent a valid drive. hLibrary is full. No slot is available for use. XThe transport cannot access the medium. \Unable to load the medium into the drive. TUnable to retrieve the drive status. PUnable to retrieve the slot status. hUnable to retrieve status about the transport. xCannot use the transport because it is already in use. hUnable to open or close the inject/eject port. tUnable to eject the medium because it is in a drive. PA cleaner slot is already reserved. HA cleaner slot is not reserved.  The cleaner cartridge has performed the maximum number of drive cleanings. LUnexpected on-medium identifier. ”The last remaining item in this group or resource cannot be deleted. œThe message provided exceeds the maximum size allowed for this parameter. `The volume contains system or paging files. The media type cannot be removed from this library since at least one drive in the library reports it can support this media type. àThis offline media cannot be mounted on this system since no enabled drives are present which can be used. pA cleaner cartridge is present in the tape library. |Cannot use the inject/eject port because it is not empty. ˆThis file is currently not available for use on this computer. €The remote storage service is not operational at this time. tThe remote storage service encountered a media error. dThe file or directory is not a reparse point. ÀThe reparse point attribute cannot be set because it conflicts with an existing attribute. |The data present in the reparse point buffer is invalid. xThe tag present in the reparse point buffer is invalid. ÜThere is a mismatch between the tag specified in the request and the tag present in the reparse point. @Fast Cache data not found. <Fast Cache data expired. <Fast Cache data corrupt. ŒFast Cache data has exceeded its max size and cannot be updated.  Fast Cache has been ReArmed and requires a reboot until it can be updated. œSecure Boot detected that rollback of protected data has been attempted. ¨The value is protected by Secure Boot policy and cannot be modified or deleted. PThe Secure Boot policy is invalid. °A new Secure Boot policy did not contain the current publisher on its update list. ¬The Secure Boot policy is either not signed or is signed by a non-trusted signer. `Secure Boot is not enabled on this machine. ÈSecure Boot requires that certain files and drivers are not replaced by other files or drivers. „The copy offload read operation is not supported by a filter. ˆThe copy offload write operation is not supported by a filter. ˆThe copy offload read operation is not supported for the file. ˆThe copy offload write operation is not supported for the file. |Single Instance Storage is not available on this volume. ¼The operation cannot be completed because other resources are dependent on this resource. lThe cluster resource dependency cannot be found. ÜThe cluster resource cannot be made dependent on the specified resource because it is already dependent. PThe cluster resource is not online. pA cluster node is not available for this operation. XThe cluster resource is not available. \The cluster resource could not be found. HThe cluster is being shut down. ÌA cluster node cannot be evicted from the cluster unless the node is down or it is the last node. @The object already exists. PThe object is already in the list. |The cluster group is not available for any new requests. TThe cluster group could not be found. ¤The operation could not be completed because the cluster group is not online. 4The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. (The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group. ¤The cluster resource could not be created in the specified resource monitor. œThe cluster resource could not be brought online by the resource monitor. ¤The operation could not be completed because the cluster resource is online. ÈThe cluster resource could not be deleted or brought offline because it is the quorum resource. üThe cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. XThe cluster software is shutting down. ´The group or resource is not in the correct state to perform the requested operation. ðThe properties were stored but not all changes will take effect until the next time the resource is brought online. üThe cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. ˜The cluster resource could not be deleted since it is a core resource. `The quorum resource failed to come online. „The quorum log could not be created or mounted successfully. @The cluster log is corrupt. ´The record could not be written to the cluster log since it exceeds the maximum size. \The cluster log exceeds its maximum size. pNo checkpoint record was found in the cluster log. ”The minimum required disk space needed for logging is not available. ôThe cluster node failed to take control of the quorum resource because the resource is owned by another active node. xA cluster network is not available for this operation. pA cluster node is not available for this operation. „All cluster nodes must be running to perform this operation. @A cluster resource failed. HThe cluster node is not valid. LThe cluster node already exists. lA node is in the process of joining the cluster. HThe cluster node was not found. lThe cluster local node information was not found. PThe cluster network already exists. PThe cluster network was not found. dThe cluster network interface already exists. dThe cluster network interface was not found. lThe cluster request is not valid for this object. `The cluster network provider is not valid. <The cluster node is down. PThe cluster node is not reachable. lThe cluster node is not a member of the cluster. dA cluster join operation is not in progress. LThe cluster network is not valid. 8The cluster node is up. \The cluster IP address is already in use. HThe cluster node is not paused. \No cluster security context is available. œThe cluster network is not configured for internal cluster communication. HThe cluster node is already up. LThe cluster node is already down. XThe cluster network is already online. XThe cluster network is already offline. tThe cluster node is already a member of the cluster. ”The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network. 0One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network. ÌThis operation cannot currently be performed on the cluster group containing the quorum resource. ”The cluster quorum resource is not allowed to have any dependencies. @The cluster node is paused. ¸The cluster resource cannot be brought online. The owner node cannot run this resource. ŒThe cluster node is not ready to perform the requested operation. PThe cluster node is shutting down. XThe cluster join operation was aborted. ìThe cluster join operation failed due to incompatible software versions between the joining node and its sponsor. ôThis resource cannot be created because the cluster has reached the limit on the number of resources it can monitor. ðThe system configuration changed during the cluster join or form operation. The join or form operation was aborted. `The specified resource type was not found. HThe specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node. The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL. No authentication package could be registered with the RPC server. TYou cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group. ¼The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join. \The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state. ¨A non locker code got a request to reserve the lock for making global updates. „The quorum disk could not be located by the cluster service. pThe backed up cluster database is possibly corrupt. hA DFS root already exists in this cluster node. ÔAn attempt to modify a resource property failed because it conflicts with another existing property. °This operation is not supported on a cluster without an Administrator Access Point. ÈAn operation was attempted that is incompatible with the current membership state of the node. tThe quorum resource does not contain the quorum log. ¤The membership engine requested shutdown of the cluster service on this node. The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node.  A matching cluster network for the specified IP address could not be found. ÀThe actual data type of the property did not match the expected data type of the property. ÄThe cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer. °Two or more parameter values specified for a resource's properties are in conflict. pThis computer cannot be made a member of a cluster. ôThis computer cannot be made a member of a cluster because it does not have the correct version of Windows installed. 0A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster. „The cluster configuration action has already been committed. €The cluster configuration action could not be rolled back. The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node. ØOne or more nodes in the cluster are running a version of Windows that does not support this operation. ÌThe name of the corresponding computer account doesn't match the Network Name for this resource. PNo network adapters are available. PThe cluster node has been poisoned. ¤The group is unable to accept the request since it is moving to another node. ÀThe resource type cannot accept the request since is too busy performing another operation. hThe call to the cluster resource DLL timed out. \The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted. ¬An internal cluster error occurred. A call to an invalid function was attempted. dA parameter value is out of acceptable range. A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required. tAn invalid cluster registry operation was attempted. |An input string of characters is not properly terminated. °An input string of characters is not in a valid format for the data it represents. An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress. An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress. ˜An internal cluster error occurred. Data was not properly initialized. ÐAn error occurred while reading from a stream of data. An unexpected number of bytes was returned. ØAn error occurred while writing to a stream of data. The required number of bytes could not be written. ˆAn error occurred while deserializing a stream of cluster data. One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s). „A quorum of cluster nodes was not present to form a cluster. àThe cluster network is not valid for an IPv6 Address resource, or it does not match the configured address. @The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends. „Quorum resource cannot reside in the Available Storage group. |The dependencies for this resource are nested too deeply. „The call into the resource DLL raised an unhandled exception. TThe RHS process failed to initialize. ˆThe Failover Clustering feature is not installed on this node. ŒThe resources must be online on the same node for this operation ¼A new node can not be added since this cluster is already at its maximum number of nodes. ØThis cluster can not be created since the specified number of nodes exceeds the maximum allowed limit. An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain. This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed. äFile share associated with file share witness resource cannot be hosted by this cluster or any of its nodes. œEviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown. If it is the last node in the cluster, destroy cluster command should be used. Only one instance of this resource type is allowed in the cluster. ˜Only one instance of this resource type is allowed per resource group. ¼The resource failed to come online due to the failure of one or more provider resources. The resource has indicated that it cannot come online on any node. ”The current operation cannot be performed on this group at this time. ŒThe directory or file is not located on a cluster shared volume. ”The Security Descriptor does not meet the requirements for a cluster. HThere is one or more shared volumes resources configured in the cluster. Those resources must be moved to available storage in order for operation to succeed. äThis group or resource cannot be directly manipulated. Use shared volume APIs to perform desired operation. ÄBack up is in progress. Please wait for backup completion before trying this operation again. tThe path does not belong to a cluster shared volume. ˆThe cluster shared volume is not locally mounted on this node. TThe cluster watchdog is terminating. œA resource vetoed a move between two nodes because they are incompatible. ¤The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements. DThe resource vetoed the call. ¼Resource could not start or run because it could not reserve sufficient system resources. A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation.  A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation. Ä The requested operation can not be completed because the group is queued for an operation. ´ The requested operation can not be completed because a resource has locked status. Ì The resource cannot move to another node because a cluster shared volume vetoed the operation. X A node drain is already in progress. l Clustered storage is not connected to the node.  The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS. ° The resource must be part of the Available Storage group to complete this action. | CSVFS failed operation as volume is in redirected mode. „ CSVFS failed operation as volume is not in redirected mode. t Cluster properties cannot be returned at this time. ô The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes. ¬ The operation cannot be completed because the resource is in maintenance mode. œ The operation cannot be completed because of cluster affinity conflicts ¸ The operation cannot be completed because the resource is a replica virtual machine. `The specified file could not be encrypted. `The specified file could not be decrypted. ´The specified file is encrypted and the user does not have the ability to decrypt it. œThere is no valid encryption recovery policy configured for this system. „The required encryption driver is not loaded for this system. °The file was encrypted with a different encryption driver than is currently loaded. `There are no EFS keys defined for the user. TThe specified file is not encrypted. €The specified file is not in the defined EFS export format. LThe specified file is read only. hThe directory has been disabled for encryption. €The server is not trusted for remote encryption operation. ¬Recovery policy configured for this system contains invalid recovery certificate. ìThe encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file. tThe disk partition does not support file encryption. dThis machine is disabled for file encryption. €A newer system is required to decrypt this encrypted file. ÈThe remote server sent an invalid response for a file being opened with Client Side Encryption. ÌClient Side Encryption is not supported by the remote server even though it claims to support it. ˜File is encrypted and should be opened in Client Side Encryption mode. ˜A new encrypted file is being created and a $EFS needs to be provided. xThe SMB client requested a CSE FSCTL on a non-CSE file. ØThe requested operation was blocked by policy. For more information, contact your system administrator. ŒThe list of servers for this workgroup is not currently available DThe Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts. hLog service encountered an invalid log sector. ˆLog service encountered a log sector with invalid block parity. hLog service encountered a remapped log sector. €Log service encountered a partial or incomplete log block. ¤Log service encountered an attempt access data outside the active log range. pLog service user marshalling buffers are exhausted. ÄLog service encountered an attempt read from a marshalling area with an invalid read context. tLog service encountered an invalid log restart area. tLog service encountered an invalid log block version. dLog service encountered an invalid log block. ¤Log service encountered an attempt to read the log with an invalid read mode. €Log service encountered a log stream with no restart area. pLog service encountered a corrupted metadata file. ¼Log service encountered a metadata file that could not be created by the log file system. ˆLog service encountered a metadata file with inconsistent data. ¸Log service encountered an attempt to erroneous allocate or dispose reservation space. „Log service cannot delete log file or file system container. ¬Log service has reached the maximum allowable containers allocated to a log file. ¨Log service has attempted to read or write backward past the start of the log. ¸Log policy could not be installed because a policy of the same type is already present. ”Log policy in question was not installed at the time of the request. tThe installed set of policies on the log is invalid. œA policy on the log in question prevented the operation from completing. ¤Log space cannot be reclaimed because the log is pinned by the archive tail. `Log record is not a record in the log file. ÐNumber of reserved log records or the adjustment of the number of reserved log records is invalid. ŒReserved log space or the adjustment of the log space is invalid. ”An new or existing archive tail or base of the active log is invalid. 8Log space is exhausted. hThe log could not be set to the requested size. ”Log is multiplexed, no direct writes to the physical log is allowed. |The operation failed because the log is a dedicated log. `The operation requires an archive context. DLog archival is in progress. ”The operation requires a non-ephemeral log, but the log is ephemeral. °The log must have at least two containers before it can be read from or written to. pA log client has already registered on the stream. pA log client has not been registered on the stream. ŒA request has already been made to handle the log full condition. ¨Log service encountered an error when attempting to read from a log container. ¤Log service encountered an error when attempting to write to a log container. ˜Log service encountered an error when attempting open a log container. ¸Log service encountered an invalid container state when attempting a requested action. ˜Log service is not in the correct state to perform a requested action. |Log space cannot be reclaimed because the log is pinned. @Log metadata flush failed. xSecurity on the log and its containers is inconsistent. ÔRecords were appended to the log or reservation changes were made, but the log could not be flushed. üThe log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. The transaction handle associated with this operation is not valid. ÀThe requested operation was made in the context of a transaction that is no longer active. ´The requested operation is not valid on the Transaction object in its current state. $The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller. ÐIt is too late to perform the requested operation, since the Transaction has already been aborted. ÔIt is too late to perform the requested operation, since the Transaction has already been committed. àThe Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. ÌThe specified ResourceManager made no changes or updates to the resource under this transaction. ÌThe resource manager has attempted to prepare a transaction that it has not successfully joined. pThe Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow. |The RM tried to register a protocol that already exists. lThe attempt to propagate the Transaction failed. ˆThe requested propagation protocol was not registered as a CRM. ´The buffer passed in to PushTransaction or PullTransaction is not in a valid format. ÜThe current transaction context associated with the thread is not a valid handle to a transaction object. ¨The specified Transaction object could not be opened, because it was not found. °The specified ResourceManager object could not be opened, because it was not found. ¨The specified Enlistment object could not be opened, because it was not found. ¸The specified TransactionManager object could not be opened, because it was not found. LThe object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline. \The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover. The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior. èBecause the associated transaction manager or resource manager has been closed, the handle is no longer valid. xThe specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask. XThe specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long. XImplicit transaction are not supported. àThe kernel transaction manager had to abort or forget the transaction because it blocked forward progress. øThe TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. ÀThe transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed. tThe transaction does not have a superior enlistment. ÈThe attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data. ´The function attempted to use a name that is reserved for use by another transaction. àTransaction support within the specified resource manager is not started or was shut down due to an error. ”The metadata of the RM has been corrupted. The RM will not function. „The specified directory does not contain a resource manager. ˜The remote server or share does not support transacted file operations. PThe requested log size is invalid. ìThe object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback.  The specified file miniversion was not found for this transacted file open. üThe specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. °A miniversion may only be opened in the context of the transaction that created it. „It is not possible to open a miniversion with modify access. It is not possible to create any more miniversions for this stream. ÄThe remote server sent mismatching version number or Fid for a file opened with transactions. „The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint. dThere is no transaction metadata on the file. <The log data is corrupt. ˜The file can't be recovered because there is a handle still open on it. ÜThe transaction outcome is unavailable because the resource manager responsible for it has disconnected. ¼The request was rejected because the enlistment in question is not a superior enlistment. ¬The transactional resource manager is already consistent. Recovery is not needed. „The transactional resource manager has already been started. ôThe file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. The operation cannot be performed because another transaction is depending on the fact that this property will not change. ìThe operation would involve a single file with two transactional resource managers and is therefore not allowed. ˆThe $Txf directory must be empty for this operation to succeed. ìThe operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. ¼The operation could not be completed because the transaction manager does not have a log. A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. ¼The transactional metadata attribute on the file or directory is corrupt and unreadable. ¬The encryption operation could not be completed because a transaction is active. |This object is not allowed to be opened in a transaction. An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. ÈMemory mapping (creating a mapped section) a remote file under a transaction is not supported. ¨Transaction metadata is already present on this file and cannot be superseded. ÄA transaction scope could not be entered because the scope handler has not been initialized. ôPromotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. ÜThe request to thaw frozen transactions was ignored because transactions had not previously been frozen. ˜Transactions cannot be frozen because a freeze is already in progress. àThe target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. ÌThe savepoint operation failed because files are open on the transaction. This is not permitted. ìWindows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred. ¼The sparse operation could not be completed because a transaction is active on the file. TThe call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument. üI/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. <The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. ŒThe operation could not be completed due to bad clusters on disk. ÄThe compression operation could not be completed because a transaction is active on the file. ÐThe operation could not be completed because the volume is dirty. Please run chkdsk and try again. °The link tracking operation could not be completed because a transaction is active. tThis operation cannot be performed in a transaction. ´The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one. èThe specified operation could not be performed because the resource manager is not enlisted in the transaction. XThe specified session name is invalid. \The specified protocol driver is invalid. ˆThe specified protocol driver was not found in the system path.  The specified terminal connection driver was not found in the system path. ˜A registry key for event logging could not be created for this session. €A service with the same name already exists on the system. dA close operation is pending on the session. `There are no free output buffers available. LThe MODEM.INF file was not found. `The modem name was not found in MODEM.INF. ðThe modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem. äThe modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on. œCarrier detect has failed or carrier has been dropped due to disconnect. ìDial tone not detected within the required time. Verify that the phone cable is properly attached and functional. lBusy signal detected at remote site on callback. `Voice detected at remote site on callback. 8Transport driver error XThe specified session cannot be found. dThe specified session name is already in use. pThe task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on. ÜAn attempt has been made to connect to a session whose video mode is not supported by the current client. ÀThe application attempted to enable DOS graphics mode. DOS graphics mode is not supported. ¸Your interactive logon privilege has been disabled. Please contact your administrator. DThe requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access. €The client failed to respond to the server connect message. pDisconnecting the console session is not supported. ”Reconnecting a disconnected session to the console is not supported. €The request to control another session remotely was denied. XThe requested session access is denied. tThe specified terminal connection driver is invalid. 0The requested session cannot be controlled remotely. This may be because the session is disconnected or does not currently have a user logged on. ŒThe requested session is not configured to allow remote control. ÈYour request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number. ¼Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator. @The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator. ÀThe client you are using is not licensed to use this system. Your logon request is denied. „The system license has expired. Your logon request is denied. ìRemote control could not be terminated because the specified session is not currently being remotely controlled. HThe remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported. Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared. TRemote logins are currently disabled. You do not have the proper encryption level to access this Session. The user %s\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer. tThe user %s\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\%s and have them log off. xUnable to log you on because of an account restriction. ØThe RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. ˜The Client Drive Mapping Service Has Connected on Terminal Connection. œThe Client Drive Mapping Service Has Disconnected on Terminal Connection. äThe Terminal Server security layer detected an error in the protocol stream and has disconnected the client. „The target session is incompatible with the current session. lWindows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance. |The file replication service API was called incorrectly. hThe file replication service cannot be started. hThe file replication service cannot be stopped. ÌThe file replication service API terminated the request. The event log may have more information. ÄThe file replication service terminated the request. The event log may have more information. ÀThe file replication service cannot be contacted. The event log may have more information. (The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information. $The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information. XThe file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information. TThe file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information. 4The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information. TThe file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information. The file replication service cannot populate the system volume because of an internal error. The event log may have more information. The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information. àThe file replication service cannot process the request. The system volume is busy with a previous request. $The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information. €The file replication service detected an invalid parameter. ÐAn error occurred while installing the directory service. For more information, see the event log. €The directory service evaluated group memberships locally. The specified directory service attribute or value does not exist. The attribute syntax specified to the directory service is invalid. ”The attribute type specified to the directory service is not defined. The specified directory service attribute or value already exists. HThe directory service is busy. TThe directory service is unavailable. The directory service was unable to allocate a relative identifier. ”The directory service has exhausted the pool of relative identifiers. The requested operation could not be performed because the directory service is not the master for that type of operation. ÌThe directory service was unable to initialize the subsystem that allocates relative identifiers. ÜThe requested operation did not satisfy one or more constraints associated with the class of the object. ¬The directory service can perform the requested operation only on a leaf object. ÈThe directory service cannot perform the requested operation on the RDN attribute of an object. °The directory service detected an attempt to modify the object class of an object. ŒThe requested cross-domain move operation could not be performed. dUnable to contact the global catalog server. ŒThe policy object is shared and can only be modified at the root. LThe policy object does not exist. The requested policy information is only in the directory service. pA domain controller promotion is currently active. tA domain controller promotion is not currently active DAn operations error occurred. @A protocol error occurred. dThe time limit for this request was exceeded. dThe size limit for this request was exceeded. xThe administrative limit for this request was exceeded. HThe compare response was false. HThe compare response was true. The requested authentication method is not supported by the server. ŒA more secure authentication method is required for this server. DInappropriate authentication. \The authentication mechanism is unknown. \A referral was returned from the server. „The server does not support the requested critical extension. `This request requires a secure connection. 8Inappropriate matching. LA constraint violation occurred. XThere is no such object on the server. @There is an alias problem. \An invalid dn syntax has been specified. DThe object is a leaf object. \There is an alias dereferencing problem. hThe server is unwilling to process the request. <A loop has been detected. DThere is a naming violation. DThe result set is too large. PThe operation affects multiple DSAs HThe server is not operational. @A local error has occurred. HAn encoding error has occurred. HA decoding error has occurred. XThe search filter cannot be recognized. POne or more parameters are illegal. XThe specified method is not supported. <No results were returned. tThe specified control is not supported by the server. `A referral loop was detected by the client. XThe preset referral limit was exceeded. PThe search requires a SORT control. tThe search results exceed the offset range specified. øThe directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation. ÜThe root object must be the head of a naming context. The root object cannot have an instantiated parent. ðThe add replica operation cannot be performed. The naming context must be writeable in order to create the replica. ˜A reference to an attribute that is not defined in the schema occurred. lThe maximum size of an object has been exceeded. ¼An attempt was made to add an object to the directory with a name that is already in use. ÌAn attempt was made to add an object of a class that does not have an RDN defined in the schema. ÄAn attempt was made to add an object using an RDN that is not the RDN defined in the schema. €None of the requested attributes were found on the objects. DThe user buffer is too small. ˜The attribute specified in the operation is not present on the object.  Illegal modify operation. Some aspect of the modification is not permitted. PThe specified object is too large. \The specified instance type is not valid. lThe operation must be performed at a master DSA. dThe object class attribute must be specified. LA required attribute is missing. ÌAn attempt was made to modify an object to include an attribute that is not legal for its class. |The specified attribute is already present on the object. |The specified attribute is not present, or has no values. ¤Multiple values were specified for an attribute that can have only one value. ”A value for the attribute was not in the acceptable range of values. PThe specified value already exists. œThe attribute cannot be removed because it is not present on the object. ¨The attribute value cannot be removed because it is not present on the object. dThe specified root object cannot be a subref. @Chaining is not permitted. TChained evaluation is not permitted. ÔThe operation could not be performed because the object's parent is either uninstantiated or deleted. ¤Having a parent that is an alias is not permitted. Aliases are leaf objects. ´The object and parent must be of the same type, either both masters or both replicas. ôThe operation cannot be performed because child objects exist. This operation can only be performed on a leaf object. @Directory object not found. HThe aliased object is missing. HThe object name has bad syntax. €It is not permitted for an alias to refer to another alias. LThe alias cannot be dereferenced. HThe operation is out of scope. ´The operation cannot continue because the object is in the process of being removed. LThe DSA object cannot be deleted. XA directory service error has occurred. ”The operation can only be performed on an internal master DSA object. LThe object must be of class DSA. tInsufficient access rights to perform the operation. ¸The object cannot be added because the parent is not on the list of possible superiors. èAccess to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM). DThe name has too many parts. 4The name is too long. @The name value is too long. €The directory service encountered an error parsing a name. ˆThe directory service cannot get the attribute type for a name. ”The name does not identify an object; the name identifies a phantom. TThe security descriptor is too short. PThe security descriptor is invalid. \Failed to create name for deleted object. XThe parent of a new subref must exist. TThe object must be a naming context. ”It is not permitted to add an attribute which is owned by the system. ´The class of the object must be structural; you cannot instantiate an abstract class. TThe schema object could not be found. „A local object with this GUID (dead or alive) already exists. lThe operation cannot be performed on a back link. œThe cross reference for the specified naming context could not be found. ´The operation could not be performed because the directory service is shutting down. \The directory service request is invalid. `The role owner attribute could not be read. ´The requested FSMO operation failed. The current FSMO holder could not be contacted. ˆModification of a DN across a naming context is not permitted. The attribute cannot be modified because it is owned by the system. hOnly the replicator can perform this function. PThe specified class is not defined. XThe specified class is not a subclass. HThe name reference is invalid. LA cross reference already exists. xIt is not permitted to delete a master cross reference. tSubtree notifications are only supported on NC heads. PNotification filter is too complex. TSchema update failed: duplicate RDN. TSchema update failed: duplicate OID. lSchema update failed: duplicate MAPI identifier. hSchema update failed: duplicate schema-id GUID. pSchema update failed: duplicate LDAP display name. |Schema update failed: range-lower less than range upper. XSchema update failed: syntax mismatch. €Schema deletion failed: attribute is used in must-contain. |Schema deletion failed: attribute is used in may-contain. ˆSchema update failed: attribute in may-contain does not exist. ˆSchema update failed: attribute in must-contain does not exist. ÀSchema update failed: class in aux-class list does not exist or is not an auxiliary class. „Schema update failed: class in poss-superiors does not exist. ÐSchema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules. pSchema update failed: Rdn-Att-Id has wrong syntax. |Schema deletion failed: class is used as auxiliary class. pSchema deletion failed: class is used as sub class. xSchema deletion failed: class is used as poss superior. xSchema update failed in recalculating validation cache. ÌThe tree deletion is not finished. The request must be made again to continue deleting the tree. xThe requested delete operation could not be performed. ˆCannot read the governs class identifier for the schema record. TThe attribute schema has bad syntax. PThe attribute could not be cached. HThe class could not be cached. pThe attribute could not be removed from the cache. hThe class could not be removed from the cache. pThe distinguished name attribute could not be read. LNo superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest. pThe instance type attribute could not be retrieved. HAn internal error has occurred. HA database error has occurred. PThe attribute GOVERNSID is missing. LAn expected attribute is missing. €The specified naming context is missing a cross reference. XA security checking error has occurred. <The schema is not loaded. ¨Schema allocation failed. Please check if the machine is running low on memory. ˆFailed to obtain the required syntax for the attribute schema. TThe global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available. ÀThe replication operation failed because of a schema mismatch between the servers involved. PThe DSA object could not be found. XThe naming context could not be found. pThe naming context could not be found in the cache. \The child object could not be retrieved. |The modification was not permitted for security reasons. hThe operation cannot replace the hidden record. HThe hierarchy file is invalid. lThe attempt to build the hierarchy table failed. The directory configuration parameter is missing from the registry. tThe attempt to count the address book indices failed. dThe allocation of the hierarchy table failed. xThe directory service encountered an internal failure. tThe directory service encountered an unknown failure. \A root object requires a class of 'top'. ìThis directory server is shutting down, and cannot take ownership of new floating single-master operation roles. <The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles. The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers. LThe replication operation failed. An invalid parameter was specified for this replication operation. ´The directory service is too busy to complete the replication operation at this time.  The distinguished name specified for this replication operation is invalid. ˜The naming context specified for this replication operation is invalid. ¨The distinguished name specified for this replication operation already exists. tThe replication system encountered an internal error. ˆThe replication operation encountered a database inconsistency.  The server specified for this replication operation could not be contacted. ¨The replication operation encountered an object with an invalid instance type. tThe replication operation failed to allocate memory. ”The replication operation encountered an error with the mail system.  The replication reference information for the target server already exists.  The replication reference information for the target server does not exist. ¬The naming context cannot be removed because it is replicated to another server. xThe replication operation encountered a database error. ÔThe naming context is in the process of being removed or is not replicated from the specified server. HReplication access was denied. °The requested operation is not supported by this version of the directory service. tThe replication remote procedure call was cancelled. ˆThe source server is currently rejecting replication requests. The destination server is currently rejecting replication requests. ”The replication operation failed due to a collision of object names. dThe replication source has been reinstalled. ¤The replication operation failed because a required parent object is missing. \The replication operation was preempted. °The replication synchronization attempt was abandoned because of a lack of updates. ¤The replication operation was terminated because the system is shutting down. hSynchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set. ìThe replication synchronization attempt failed because a master replica attempted to sync from a partial replica. HThe server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation. The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer. ¬Schema update failed: An attribute with the same link identifier already exists. `Name translation: Generic processing error. ¤Name translation: Could not find the name or insufficient right to see name. ŒName translation: Input name mapped to more than one output name. œName translation: Input name found, but not the associated output format.  Name translation: Unable to resolve completely, only the domain was found. àName translation: Unable to perform purely syntactical mapping at the client without going out to the wire. xModification of a constructed attribute is not allowed. ¸The OM-Object-Class specified is incorrect for an attribute with the specified syntax. €The replication request has been posted; waiting for reply. ¤The requested operation requires a directory service, and none was available. ¨The LDAP display name of the class or attribute contains non-ASCII characters. The requested search operation is only supported for base searches. €The search failed to retrieve attributes from the database. àThe schema update operation tried to add a backward link attribute that has no corresponding forward link. TSource and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object. TSource and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object. <Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation. ”Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container. ÀDestination of a cross-domain move is not authoritative for the destination naming context. tSource and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object. TObject being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object. ¼Another operation which requires exclusive access to the PDC FSMO is already in progress. ÈA cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state. ÔThis object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move. ¨Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry. àA naming context head must be the immediate child of another naming context head, not of an interior node. The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters) `Destination domain must be in native mode. üThe operation cannot be performed because the server does not have an infrastructure container in the domain of interest. „Cross-domain move of non-empty account groups is not allowed. ˆCross-domain move of non-empty resource groups is not allowed. øThe search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings. ÀTree deletions starting at an object which has an NC head as a descendant are not allowed. àThe directory service failed to lock a tree in preparation for a tree deletion because the tree was in use. ÜThe directory service failed to identify the list of objects to delete while attempting a tree deletion. ÜSecurity Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. ¬Only an administrator can modify the membership list of an administrative group. Cannot change the primary group ID of a domain controller account. dAn attempt is made to modify the base schema. lAdding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed. ¼Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner. HAn object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container. ÔThe replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it. $The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory. TThe specified group type is invalid. ¬You cannot nest global groups in a mixed domain if the group is security-enabled. ¬You cannot nest local groups in a mixed domain if the group is security-enabled. tA global group cannot have a local group as a member. |A global group cannot have a universal group as a member. |A universal group cannot have a local group as a member. lA global group cannot have a cross-domain member. ˜A local group cannot have another cross domain local group as a member. œA group with primary members cannot change to a security-disabled group. ¸The schema cache load failed to convert the string default SD on a class-schema object. 8Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers) ˜The DSA operation is unable to proceed because of a DNS lookup failure. While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync. tThe Security Descriptor attribute could not be read.  The object requested was not found, but an object with that key was found. `The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1 |Security Account Manager needs to get the boot password. ”Security Account Manager needs to get the boot key from floppy disk. HDirectory Service cannot start. PDirectory Services could not start.  The connection between client and server requires packet privacy or better. ˆThe source domain may not be in the same forest as destination. dThe destination domain must be in the forest. The operation requires that destination domain auditing be enabled. |The operation couldn't locate a DC for the source domain. `The source object must be a group or user. „The source object's SID already exists in destination forest. €The source and destination object must be of the same type. °Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information. ”Schema information could not be included in the replication request. ¬The replication operation could not be completed due to a schema incompatibility. ÀThe replication operation could not be completed due to a previous schema incompatibility. \The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation. äThe requested domain could not be deleted because there exist domain controllers that still host this domain. œThe requested operation can be performed only on a global catalog server. ¤A local group can only be a member of other local groups in the same domain. Foreign security principals cannot be members of universal groups. ´The attribute is not allowed to be replicated to the GC because of security reasons. èThe checkpoint with the PDC could not be taken because there too many modifications being processed currently. ˆThe operation requires that source domain auditing be enabled. ¤Security principal objects can only be created inside domain naming contexts. ôA Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format. tA Filter was passed that uses constructed attributes. ŒThe unicodePwd attribute value must be enclosed in double quotes. ÄYour computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased. ˜For security reasons, the operation must be run on the destination DC. ˆFor security reasons, the source DC must be NT4SP4 or greater. $Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed. ”Directory Services could not start because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. ¬Security Accounts Manager initialization failed because of the following error: %1. Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. ¨The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set. ÐThe version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain. üThe version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set. ÌThe version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain. The version of the operating system installed on this server is incompatible with the functional level of the domain or forest. ¸The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level. ÄThe forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level. `The sort order requested is not supported. |The requested name already exists as a unique identifier.  The machine account was created pre-NT4. The account needs to be recreated. TThe database is out of version store. ¤Unable to continue operation because multiple conflicting controls were used. ¨Unable to find a valid security descriptor reference domain for this partition. xSchema update failed: The link identifier is reserved. ˆSchema update failed: There are no link identifiers available. €An account group cannot have a universal group as a member. ¸Rename or move operations on naming context heads or read-only objects are not allowed. œMove operations on objects in the schema naming context are not allowed. ÈA system flag has been set on the object and does not allow the object to be moved or renamed. ,This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers. œUnable to resolve completely, a referral to another forest is generated. |The requested action is not supported on standard server. <Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question. äThe directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master. hThe thread limit for this request was exceeded. tThe Global catalog server is not in the closest site. ¤The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute. xThe Directory Service failed to enter single user mode. œThe Directory Service cannot parse the script because of a syntax error. ”The Directory Service cannot process the script because of an error. ŒThe directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress). ÜThe directory service binding must be renegotiated due to a change in the server extensions information. hOperation not allowed on a disabled cross ref. „Schema update failed: No values for msDS-IntId are available. ŒSchema update failed: Duplicate msDS-INtId. Retry the operation. xSchema deletion failed: attribute is used in rDNAttID. xThe directory service failed to authorize the request. ˜The Directory Service cannot process the script because it is invalid. The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data. xA cross reference is in use locally with the same name. XThe DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest. dWriteable NCs prevent this DC from demoting. œThe requested object has a non-unique identifier and cannot be retrieved. ,Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected. ¼The group cannot be converted due to attribute restrictions on the requested group type. ˜Cross-domain move of non-empty basic application groups is not allowed. ¤Cross-domain move of non-empty query based application groups is not allowed. 4The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner. èThe target container for a redirection of a well known object container cannot already be a special container. èThe Directory Service cannot perform the requested operation because a domain rename operation is in progress. 0The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method. <The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. ¨The requested operation is not allowed on an object under the system container. The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected. The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency. tAt this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies. ˆThe site settings object for the specified site does not exist. °The local account store does not contain secret material for the specified account. €Could not find a writable domain controller in the domain. €The server object for the domain controller does not exist. The NTDS Settings object for the domain controller does not exist. ŒThe requested search operation is not supported for ASQ searches. ŒA required audit event could not be generated for the operation. ìThe search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes. ðThe search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings. ¤The address books are nested too deeply. Failed to build the hierarchy table. lThe specified up-to-date-ness vector is corrupt. `The request to replicate secrets is denied. xSchema update failed: The MAPI identifier is reserved. ˆSchema update failed: There are no MAPI identifiers available. ÜThe replication operation failed because the required attributes of the local krbtgt object are missing. The domain name of the trusted domain already exists in the forest. ŒThe flat name of the trusted domain already exists in the forest. \The User Principal Name (UPN) is invalid. XOID mapped groups cannot have members. PThe specified OID cannot be found. ÌThe replication operation failed because the target object referred by a link value is recycled. The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller. ÈThe functional level of the AD LDS configuration set cannot be lowered to the requested value. ¼The functional level of the domain (or forest) cannot be lowered to the requested value. ŒThe functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level. ÔThe domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information. HThe undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object. øThe system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site. ÔThe operation failed because SPN value provided for addition/modification is not unique forest-wide. ÔThe operation failed because UPN value provided for addition/modification is not unique forest-wide. XDNS server unable to interpret format. 0DNS server failure. <DNS name does not exist. \DNS request not supported by name server. 8DNS operation refused. `DNS name that ought not exist, does exist. dDNS RR set that ought not exist, does exist. hDNS RR set that ought to exist, does not exist. XDNS server not authoritative for zone. dDNS name in update or prereq is not in zone. HDNS signature failed to verify. $DNS bad key. HDNS signature validity expired. ´Only the DNS server acting as the key master for the zone may perform this operation.  This operation is not allowed on a zone that is signed or has signing keys. ÈNSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC. The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK). \The specified algorithm is not supported. \The specified key size is not supported. 0One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved. (The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved. èAn unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved. äAn unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved. The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved. ˜The specified key service provider cannot be opened by the DNS server. ìThe DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone. \The specified rollover period is invalid. lThe specified initial rollover offset is invalid. ”The specified signing key is already in process of rolling over keys. ŒThe specified signing key does not have a standby key to revoke. €This operation is not allowed on a zone signing key (ZSK). xThis operation is not allowed on an active signing key. |The specified signing key is already queued for rollover. pThis operation is not allowed on an unsigned zone. üThis operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role. pThe specified signature validity period is invalid. ØThe specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone. ,This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server. ÜThis operation could not be completed because the XML stream received is empty or syntactically invalid. ˆThis operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days. ŒThe specified signing key is not waiting for parental DS update. @Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again. ÔNSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3. TNo records found for given DNS query. (Bad DNS packet. (No DNS packet. 8DNS error, check rcode. 4Unsecured DNS packet. DDNS query request is pending. ,Invalid DNS type. 0Invalid IP address. ,Invalid property. HTry DNS operation again later. dRecord for given name and type is not unique. lDNS name does not comply with RFC specifications. XDNS name is a fully-qualified DNS name. LDNS name is dotted (multi-label). HDNS name is a single-part name. XDNS name contains an invalid character. DDNS name is entirely numeric. ˆThe operation requested is not permitted on a DNS root server. äThe record could not be created because this part of the DNS namespace has been delegated to another server. pThe DNS server could not find a set of root hints. ¬The DNS server found root hints but they were not consistent across all adapters. tThe specified value is too small for this parameter. tThe specified value is too large for this parameter. èThis operation is not allowed while the DNS server is loading zones in the background. Please try again later. ÀThe operation requested is not permitted on against a DNS server running on a read-only DC. xNo data is allowed to exist underneath a DNAME record. hThis operation requires credentials delegation. Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. <DNS zone does not exist. PDNS zone information not available. HInvalid operation for DNS zone. HInvalid DNS zone configuration. lDNS zone has no start of authority (SOA) record. \DNS zone has no Name Server (NS) record. 0DNS zone is locked. <DNS zone creation failed. <DNS zone already exists. PDNS automatic zone already exists. 8Invalid DNS zone type. hSecondary DNS zone requires master IP address. 8DNS zone not secondary. @Need secondary IP address. @WINS initialization failed. 0Need WINS servers. PNBTSTAT initialization call failed. `Invalid delete of start of authority (SOA) €A conditional forwarding zone already exists for that name. ¤This zone must be configured with one or more master DNS server IP addresses. ŒThe operation cannot be performed because this zone is shut down. ØThis operation cannot be performed because the zone is currently being signed. Please try again later. PPrimary DNS zone requires datafile. PInvalid datafile name for DNS zone. TFailed to open datafile for DNS zone. XFailed to write datafile for DNS zone. dFailure while reading datafile for DNS zone. @DNS record does not exist. <DNS record format error. DNode creation failure in DNS. <Unknown DNS record type. 4DNS record timed out. 4Name not in DNS zone. 4CNAME loop detected. @Node is a CNAME DNS record. dA CNAME record already exists for given name. DRecord only at DNS zone root. @DNS record already exists. HSecondary DNS zone data error. LCould not create DNS cache data. <DNS name does not exist. XCould not create pointer (PTR) record. <DNS domain was undeleted. TThe directory service is unavailable. lDNS zone already exists in the directory service. ÈDNS server not creating or reading the boot file for the directory service integrated DNS zone. @Node is a DNAME DNS record. dA DNAME record already exists for given name. An alias loop has been detected with either CNAME or DNAME records. PDNS AXFR (zone transfer) complete. <DNS zone transfer failed. <Added local WINS server. tSecure update call needs to continue update request. XTCP/IP network protocol not installed. `No DNS servers configured for local system. lThe specified directory partition does not exist. lThe specified directory partition already exists. ”This DNS server is not enlisted in the specified directory partition. œThis DNS server is already enlisted in the specified directory partition. ÈThe directory partition is not available at this time. Please wait a few minutes and try again. èThe operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later. XThe scope already exists for the zone. XThe scope does not exist for the zone. lThe scope is the same as the default zone scope. `The scope name contains invalid characters. hOperation not allowed when the zone has scopes. @Failed to load zone scope. ÄFailed to write data file for DNS zone scope. Please verify the file exists and is writable. `The scope name contains invalid characters. <The scope does not exist. `The scope is the same as the default scope. XThe operation is invalid on the scope. 4The scope is locked. <The scope already exists. œA blocking operation was interrupted by a call to WSACancelBlockingCall. XThe file handle supplied is not valid. ´An attempt was made to access a socket in a way forbidden by its access permissions. ÌThe system detected an invalid pointer address in attempting to use a pointer argument in a call. LAn invalid argument was supplied. 8Too many open sockets. A non-blocking socket operation could not be completed immediately. dA blocking operation is currently executing. ÈAn operation was attempted on a non-blocking socket that already had an operation in progress. „An operation was attempted on something that is not a socket. „A required address was omitted from an operation on a socket. ŒA message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. øA protocol was specified in the socket function call that does not support the semantics of the socket type requested. ÔAn unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call. ÐThe requested protocol has not been configured into the system, or no implementation for it exists. ¬The support for the specified socket type does not exist in this address family.  The attempted operation is not supported for the type of object referenced. ÈThe protocol family has not been configured into the system or no implementation for it exists. „An address incompatible with the requested protocol was used. ÄOnly one usage of each socket address (protocol/network address/port) is normally permitted. pThe requested address is not valid in its context. hA socket operation encountered a dead network. €A socket operation was attempted to an unreachable network. ðThe connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.  An established connection was aborted by the software in your host machine. ˆAn existing connection was forcibly closed by the remote host. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. €A connect request was made on an already connected socket. \A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. (A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. `Too many references to some kernel object. xA connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.  No connection could be made because the target machine actively refused it. 8Cannot translate name. TName component or name was too long. ŒA socket operation failed because the destination host was down. |A socket operation was attempted to an unreachable host. dCannot remove a directory that is not empty. èA Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. ,Ran out of quota. 8Ran out of disk quota. dFile handle reference is no longer available. HItem is not available locally. WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. xThe Windows Sockets version requested is not supported. ˜Either the application has not called WSAStartup, or WSAStartup failed. àReturned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence. |No more results can be returned by WSALookupServiceNext. ÜA call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. TThe procedure call table is invalid. `The requested service provider is invalid. The requested service provider could not be loaded or initialized. <A system call has failed. °No such service is known. The service cannot be found in the specified name space. PThe specified class was not found. |No more results can be returned by WSALookupServiceNext. ÜA call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. |A database query failed because it was actively refused. 8No such host is known. 4This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. €A non-recoverable error occurred during a database lookup. œThe requested name is valid, but no data of the requested type was found. LAt least one reserve has arrived. HAt least one path has arrived. 4There are no senders. 8There are no receivers. @Reserve has been confirmed. HError due to lack of resources. xRejected for administrative reasons - bad credentials. DUnknown or conflicting style. ¨Problem with some part of the filterspec or providerspecific buffer in general. XProblem with some part of the flowspec. 0General QOS error. An invalid or unrecognized service type was found in the flowspec. An invalid or inconsistent flowspec was found in the QOS structure. TInvalid QOS provider-specific buffer. TAn invalid QOS filter style was used. TAn invalid QOS filter type was used. ¤An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR. ÈAn object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.  An incorrect number of flow descriptors was specified in the QOS structure. ”An unrecognized object was found in the QOS provider-specific buffer. ˜An invalid policy object was found in the QOS provider-specific buffer. ”An invalid QOS flow descriptor was found in the flow descriptor list. °An invalid or inconsistent flowspec was found in the QOS provider specific buffer. ”An invalid FILTERSPEC was found in the QOS provider-specific buffer. °An invalid shape discard mode object was found in the QOS provider specific buffer. ¤An invalid shaping rate object was found in the QOS provider-specific buffer. œA reserved policy element was found in the QOS provider-specific buffer. HNo such host is known securely. `Name based IPSEC policy could not be added. hThe specified quick mode policy already exists. hThe specified quick mode policy was not found. hThe specified quick mode policy is being used. hThe specified main mode policy already exists. dThe specified main mode policy was not found dThe specified main mode policy is being used. hThe specified main mode filter already exists. dThe specified main mode filter was not found. pThe specified transport mode filter already exists. pThe specified transport mode filter does not exist. pThe specified main mode authentication list exists. €The specified main mode authentication list was not found. €The specified main mode authentication list is being used. tThe specified default main mode policy was not found. The specified default main mode authentication list was not found. xThe specified default quick mode policy was not found. \The specified tunnel mode filter exists. hThe specified tunnel mode filter was not found. \The Main Mode filter is pending deletion. \The transport filter is pending deletion. XThe tunnel filter is pending deletion. \The Main Mode policy is pending deletion. |The Main Mode authentication bundle is pending deletion. `The Quick Mode policy is pending deletion. ÌThe Main Mode policy was successfully added, but some of the requested offers are not supported. ÌThe Quick Mode policy was successfully added, but some of the requested offers are not supported. LERROR_IPSEC_IKE_NEG_STATUS_BEGIN hIKE authentication credentials are unacceptable \IKE security attributes are unacceptable @IKE Negotiation in progress <General processing error 4Negotiation timed out TIKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store. tIKE SA deleted by peer before establishment completed dIKE SA deleted before establishment completed \Negotiation request sat in Queue too long \Negotiation request sat in Queue too long \Negotiation request sat in Queue too long \Negotiation request sat in Queue too long 4No response from peer <Negotiation took too long <Negotiation took too long 8Unknown error occurred PCertificate Revocation Check failed DInvalid certificate key usage <Invalid certificate type ÜIKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key. PSimultaneous rekeys were detected. TFailure in Diffie-Hellman computation `Don't know how to process critical payload (Invalid header 4No policy configured @Failed to verify signature TFailed to authenticate using Kerberos dPeer's certificate did not have a public key HError processing error payload @Error processing SA payload LError processing Proposal payload PError processing Transform payload @Error processing KE payload @Error processing ID payload DError processing Cert payload dError processing Certificate Request payload DError processing Hash payload PError processing Signature payload HError processing Nonce payload HError processing Notify payload HError processing Delete Payload LError processing VendorId payload <Invalid payload received (Soft SA loaded ,Soft SA torn down <Invalid cookie received. dPeer failed to send valid machine certificate €Certification Revocation check of peer's certificate failed lNew policy invalidated SAs formed with old policy `There is no available Main Mode IKE policy. LFailed to enabled TCB privilege. DFailed to load SECURITY.DLL. ”Failed to obtain security function table dispatch address from SSPI. €Failed to query Kerberos package to obtain max token size. ôFailed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup. ÜFailed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes). €Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters. 8Given filter is invalid <Memory allocation failed. œFailed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine. (Invalid policy Invalid DOI ,Invalid situation 8Diffie-Hellman failure DInvalid Diffie-Hellman group <Error encrypting payload <Error decrypting payload 0Policy match error (Unsupported ID <Hash verification failed 8Invalid hash algorithm ,Invalid hash size DInvalid encryption algorithm LInvalid authentication algorithm DInvalid certificate signature Load failed 4Deleted via RPC call ¬Temporary state created to perform reinitialization. This is not a real failure. @The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine. The recipient cannot handle version of IKE specified in the header. ¤Key length in certificate is too small for configured security requirements. pMax number of established MM SAs to peer exceeded. lIKE received a policy that disables negotiation. °Reached maximum quick mode limit for the main mode. New main mode will be started. ˆMain mode SA lifetime expired or peer sent a main mode delete. Main mode SA assumed to be invalid because peer stopped responding. „Certificate doesn't chain to a trusted root in IPsec policy. HReceived unexpected message ID. XReceived invalid authentication offers. TSent DoS cookie notify to initiator. DIKE service is shutting down. „Could not verify binding between CGA address and certificate. HError processing NatOA payload. „Parameters of the main mode are invalid for this quick mode. `Quick mode SA was expired by IPsec driver. |Too many dynamically added IKEEXT filters were detected. HERROR_IPSEC_IKE_NEG_STATUS_END ŒNAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel. ŒError in assigning inner IP address to initiator in tunnel mode. XRequire configuration payload missing. ¼A negotiation running as the security principle who issued the connection is in progress ˆSA was deleted due to IKEv1/AuthIP co-existence suppress check. ”Incoming SA request was dropped due to peer IP address rate limiting. DPeer does not support MOBIKE. PSA establishment is not authorized. ØSA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. ìSA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard. pSA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA. XERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END xThe SPI in the packet does not match a valid IPsec SA. ˆPacket was received on an IPsec SA whose lifetime has expired. °Packet was received on an IPsec SA that does not match the packet characteristics. `Packet sequence number replay check failed. tIPsec header and/or trailer in the packet is invalid. DIPsec integrity check failed. PIPsec dropped a clear text packet. ¼IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. dIPsec dropped a packet due to DoS throttling. tIPsec DoS Protection matched an explicit block rule. ¸IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. ˆIPsec DoS Protection received an incorrectly formatted packet. dIPsec DoS Protection failed to look up state. ôIPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. äIPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. `IPsec DoS Protection has not been enabled. ,IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached. ŒThe requested section was not present in the activation context. |The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. hThe application binding data format is invalid. |The referenced assembly is not installed on your system. ¨The manifest file does not begin with the required tag and format information. tThe manifest file contains one or more syntax errors. ”The application attempted to activate a disabled activation context. œThe requested lookup key was not found in any active activation context. ÜA component version required by the application conflicts with another component version already active. ¬The type requested activation context section does not match the query API used. äLack of system resources has required isolated activation to be disabled for the current thread of execution. An attempt to set the process default activation context failed because the process default activation context was already set. €The encoding group identifier specified is not recognized. \The encoding requested is not recognized. tThe manifest contains a reference to an invalid URI. ÄThe application manifest contains a reference to a dependent assembly which is not installed ðThe manifest for an assembly used by the application has a reference to a dependent assembly which is not installed ¬The manifest contains an attribute for the assembly identity which is not valid. ÄThe manifest is missing the required default namespace specification on the assembly element. The manifest has a default namespace specified on the assembly element but its value is not "urn:schemas-microsoft-com:asm.v1". ¬The private manifest probed has crossed a path with an unsupported reparse point. ìTwo or more components referenced directly or indirectly by the application manifest have files by the same name. Two or more components referenced directly or indirectly by the application manifest have window classes with the same name. ôTwo or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs. Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs. Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs. èTwo or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs. <Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted. ÌA component's file does not match the verification information present in the component manifest. xThe policy manifest contains one or more syntax errors. ÈManifest Parse Error : A string literal was expected, but no opening quote character was found. ˆManifest Parse Error : Incorrect syntax was used in a comment. ”Manifest Parse Error : A name was started with an invalid character. „Manifest Parse Error : A name contained an invalid character. ˜Manifest Parse Error : A string literal contained an invalid character. „Manifest Parse Error : Invalid syntax for an xml declaration. ˜Manifest Parse Error : An Invalid character was found in text content. |Manifest Parse Error : Required white space was missing. xManifest Parse Error : The character '>' 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. 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 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_INFO½ïþ)G€%)G€%?StringFileInfoÞ040904B0LCompanyNameMicrosoft CorporationfFileDescriptionWindows NT BASE API Client DLLt*FileVersion6.3.9600.18217 (winblue_ltsb.160124-0053)2 InternalNamekernel32€.LegalCopyright© Microsoft Corporation. All rights reserved.: OriginalFilenamekernel32j%ProductNameMicrosoft® Windows® Operating SystemBProductVersion6.3.9600.18217DVarFileInfo$Translation °PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING